AI and MCP

Reconcile an AI summary with your bank closing balance

Test an AI summary against your statement: opening balance plus credits minus debits must equal the closing balance. Here is how to find the missing rows.

Editorial illustration for Reconcile an AI summary with your bank closing balance

An AI summary of a bank statement is correct only if the opening balance, plus all credits, minus all debits, equals the closing balance on the statement. Do that one sum with the assistant's numbers. If it matches, the summary has all the rows; if not, the gap tells you roughly how much money is missing and helps you hunt for the row.

What is the basic reconciliation formula?

Opening balance + total credits − total debits = closing balance. Every bank account behaves this way, because the balance only moves when money comes in or goes out. Take the opening and closing balances from the statement itself, not from the assistant, and take the credit and debit totals from the assistant's rows.

A worked example with made-up numbers

Suppose your statement says the opening balance on 1 April was ₹28,400 and the closing balance on 30 April was ₹31,150. The assistant reports total credits of ₹62,000 and total debits of ₹58,700.

StepWorkingResult
Opening balanceFrom statement₹28,400
Add credits28,400 + 62,000₹90,400
Subtract debits90,400 − 58,700₹31,700
Closing balance on statementFrom statement₹31,150
Difference31,700 − 31,150₹550

The assistant's rows leave your balance ₹550 too high. That means either debits worth ₹550 are missing, or credits worth ₹550 were counted that do not exist. You now have a specific number to look for.

How do I find the missing rows?

  1. Look for a debit of exactly the difference, here ₹550, in the statement. If you find one the assistant skipped, that is it.
  2. If no single row matches, look for two or three smaller debits that add up to the difference.
  3. Check whether a credit was counted twice, since a refund or reversal listed near the original payment is a common culprit.
  4. Compare the number of rows the assistant found with the count per page on the statement.
  5. Use the running balance column. Go down the rows and check that each balance equals the one above plus or minus the amount. The first row where the arithmetic breaks is where a row went missing.

Why do rows go missing in the first place?

Usually because of layout. A narration that runs over two lines can be read as two rows or one. A page break can hide the last row of a page. Charges that appear with no description, such as small monthly fees, are easy to overlook. Debit and credit columns can also confuse a reader into putting an amount on the wrong side, which would show up as a difference of twice the amount.

What about statements that cover part of a month?

The same rule applies to any period. Make sure the opening balance is the balance at the start of your first row, not the balance of the previous statement's last day, and that you are not including a few extra days. Banks differ in how they show the opening line, so check your own statement.

In a tracker such as SpendixAI, where you choose the account before importing and review the rows before saving, you can do the same check on the imported rows: total credits minus total debits for the period should equal the change between your opening and closing balances. This check works on any tool's output, which is the reason to keep doing it.

A checklist to finish with

  • Opening and closing balances copied from the statement, not from the assistant.
  • Credits and debits totalled separately.
  • Difference calculated and, if not zero, explained.
  • Row count matches the statement.
  • Duplicated refunds and reversals checked.
  • Original statement kept in case you need to show it later.
SPENDIXAI JOURNAL

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

Explore your reports