To check that a statement import is complete, add the imported credits to the opening balance, subtract the imported debits, and compare the answer with the closing balance printed on the statement. If the two match, every row came through. If they differ, the gap tells you roughly what is missing.
The formula in plain words
Closing balance = opening balance + credits - debits. It works because a bank account is only a running total of money in and money out. Nothing else changes the balance.
Use the figures on your own statement for the opening and closing balances. Use your tracker's totals for the credits and debits of the same period and the same account. The comparison only holds for one account at a time.
A ten-row ledger you can follow
These numbers are made up for illustration. Say the opening balance on 1 March is ₹20,000.
| Row | Description | Credit | Debit |
|---|---|---|---|
| 1 | Salary | ₹45,000 | - |
| 2 | Rent | - | ₹15,000 |
| 3 | Electricity | - | ₹1,850 |
| 4 | Grocery UPI | - | ₹2,300 |
| 5 | Refund from shop | ₹700 | - |
| 6 | Mobile recharge | - | ₹399 |
| 7 | Dinner out | - | ₹1,450 |
| 8 | FASTag top-up | - | ₹1,000 |
| 9 | Interest | ₹180 | - |
| 10 | Medicine | - | ₹620 |
Credits: 45,000 + 700 + 180 = ₹45,880. Debits: 15,000 + 1,850 + 2,300 + 399 + 1,450 + 1,000 + 620 = ₹22,619. So the expected closing balance is 20,000 + 45,880 - 22,619 = ₹43,261.
If your statement's closing balance is ₹43,261, the import is complete.
What does one missing row look like?
Now suppose the statement says ₹43,261, but your tracker only picked up nine rows and the dinner at ₹1,450 is absent. Your tracker's debits are 22,619 - 1,450 = ₹21,169, so the computed closing balance would be 20,000 + 45,880 - 21,169 = ₹44,711. That is ₹1,450 higher than the statement.
The size of the gap equals the missing row. A positive difference, where your computed balance is too high, means a debit is missing. A negative difference means a credit is missing, or an extra debit was brought in. Then search the statement for a row of exactly that amount.
What if the difference is not one row?
- A gap that equals two or three smaller rows added together: look for several skipped lines.
- A gap exactly double a transaction: a row may have been imported twice, or a footer counted.
- A gap equal to a charge dated just outside the period: the file boundary cut it off.
- A gap you cannot explain: compare the row count with the statement and check the date range.
A checklist for after every import
- Note the opening and closing balances from the statement.
- Read the credit and debit totals in the tracker for that account and period.
- Compute opening + credits - debits.
- Compare with the closing balance.
- If they differ, find the gap, fix it, and recheck.
When the formula cannot be used
The check needs the opening and closing balances, and some files do not show them. A CSV may carry only transaction lines, and a card statement describes what you owe rather than what you hold. In that case, use the running balance column, if the file has one: the balance after the last row should equal the closing figure, and the balance after the first row minus its credit plus its debit gives the opening figure. If neither is available, fall back on counting rows against the statement and checking a few large entries by eye. It is a weaker proof, but it still catches most skipped or doubled rows.
SpendixAI lets you review rows before saving, so the best moment for this test is before you confirm. If the arithmetic fails, you can fix the rows then instead of after your reports have used them.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

