Bank statements

Should you review transactions before importing? Yes, and here is the checklist

A forum-style answer for India on why reviewing statement rows before saving matters, with a rupee example of duplicates and a flipped refund.

Editorial illustration for Should you review transactions before importing? Yes, and here is the checklist

The question: is it worth reading through the rows before I import a statement into my expense tracker, or can I just let it load? Yes, read them first. A few minutes on the review screen is far cheaper than hunting for a wrong total three months later.

What goes wrong when you skip the review

Statement files are messy. Dates can be read the wrong way round, a refund may show up as spending, a row that appears twice in the file will be counted twice, and a merchant name such as a payment gateway may hide the shop you actually paid. Once those rows are saved, every report built on them carries the error.

A rupee example

Say you import a card statement of 142 rows and your own totals say you spent ₹64,200. After import, the tracker shows ₹69,138. That is ₹4,938 more. The review would have caught both of the causes.

ProblemRowsEffect on total
Duplicates of ₹499, ₹1,250, ₹320 and ₹1,0714+₹3,140
A ₹899 refund read as a purchase instead of a credit1+₹1,798 (the ₹899 credit is lost, then ₹899 is added)
Total overstatement5₹4,938

You can check the arithmetic: 3,140 + 1,798 = ₹4,938, and 64,200 + 4,938 = ₹69,138. When a mismatch has a clean explanation like this, the review has done its job.

How should I review?

  1. Check the first and last dates on the review screen against the statement period.
  2. Compare the row count and the total of debits with the numbers printed on the statement, if it has them.
  3. Sort by amount and look at the largest rows; most damage hides there.
  4. Look for the same amount to the same merchant on the same or the next day.
  5. Check that every credit, such as a refund or reversal, is treated as money coming back, not as spending.
  6. Scan merchant names and fix any category that is clearly wrong before saving.

What does SpendixAI do here?

SpendixAI shows the rows for review before they are saved, flags possible duplicate imports and has a 'Possible duplicate charges' report for the same amount to the same merchant within two days. Deleted transactions go to a recycle bin for 30 days, so a wrong deletion is not final.

A related habit is to import small and often. A month of rows is easy to review in one sitting; a year of rows is not, and mistakes hide in the volume. If you are loading old history for the first time, do it one month at a time, check each month's totals against the statement, and only then move to the next one.

Be careful with UPI rows in particular. A single payment can show up as a debit in your bank file with a long reference string, and the same payment might be repeated in a wallet statement if you import both. Decide which account is the source of truth for each payment and skip the other.

How long should it take?

For a month of normal use, five to ten minutes. If you review every month, the corrections you make teach the categories and your rules, so later reviews get faster. Skipping the check saves the time once and costs it back many times over.

  • Do the review on the day you import, while the statement is open in front of you.
  • Fix the cause where you can, for example a recurring merchant name, not only the single row.
  • If a file has far more rows than you expect, stop and check that it is the right account and period.
SPENDIXAI JOURNAL

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

Explore your reports