Bank statements

Why you should review imported rows before they hit your books

A salaried employee's guide to checking imported bank rows before saving: the five errors that quietly distort a month and how a review step catches them.

Editorial illustration for Why you should review imported rows before they hit your books

Review imported rows before saving because an import is a guess about what each line means, and a wrong guess changes your totals for every month after it. A two-minute check on direction, category and duplicates is far cheaper than hunting for a mismatch three months later.

What can go wrong in an import?

A statement is made for a banker, not a budget. The importer has to decide whether each amount is money in or out, what to call the merchant, and which month the line belongs to. For someone on a monthly salary, the common slips are tidy-looking but expensive.

  • A salary credit read as a refund or lost because of an odd narration.
  • An EMI or SIP debit counted twice because it appears in both the bank and card statements.
  • A reimbursement from your employer counted as income instead of a reversal of a work cost.
  • A card bill payment counted as spending on top of the card purchases it already covers.
  • A date misread, putting a late-March debit in April.

How much damage can three bad rows do?

Take a hypothetical month. Salary is ₹85,000 and true spending is ₹52,000, so you saved ₹33,000. Now suppose the import adds a ₹18,000 card bill payment as spending even though the purchases behind it are already in the list, and counts a ₹6,000 reimbursement as extra income. Spending now reads ₹70,000 and income ₹91,000, so the month appears to save ₹21,000. The real figure is ₹33,000. A ₹12,000 error from two rows changes how the month feels, and might lead you to cut something you did not need to cut.

ItemTruthAfter a bad import
Income₹85,000₹91,000
Spending₹52,000₹70,000
Saved₹33,000₹21,000

Notice that neither of those mistakes shows up as an obviously odd row. They hide in plain sight.

What should you check on a review screen?

  1. Direction. Are credits really credits and debits really debits? Glance down the sign or the in and out columns.
  2. Own-account movements. Card bill payments and transfers between your accounts should be marked as transfers.
  3. Category. Look at the largest rows first; a wrong category on a ₹14,000 line matters more than ten on ₹60 lines.
  4. Duplicates. A repeated amount to the same merchant on adjacent days deserves a second look.
  5. Dates. Make sure the first and last dates on the screen match the statement period.

Why not fix it after the import instead?

You can, but it costs more. After saving, a bad row has already shaped budgets, reports and any alerts that depend on them. Searching for it means remembering that something looked wrong. At the review stage the row is in front of you with the original text, and fixing it takes one click. A rule you create there also applies to the next month's rows.

How does this work in SpendixAI?

SpendixAI always shows a review screen before imported rows are committed. You choose the account first, upload the PDF, CSV or Excel statement, and check the parsed rows before saving. Possible duplicate imports are flagged, and a Possible duplicate charges report lists the same amount to the same merchant within two days. Your own rules come first in categorisation, then your history, and any correction you make becomes history, so repeated review gets lighter over time. If an import fails, there is an Import failed notification and an import history showing the status.

A short routine for salary day

  • Import the previous month's statements once the salary has credited.
  • Check the top fifteen rows by amount.
  • Mark card payments and own-account transfers.
  • Compare the totals with the bank's summary before you save.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports