← All guides
Accounting15 Sept 2026 · 6 min read

Matching Your Bank Statement to Your Books

Most small businesses treat reconciliation as something the accountant does at year end. It is actually the only routine check that answers a question you care about every month: is there money that moved and never reached my books?

Why the two never agree on their own

Your books record what you entered. The bank records what happened. Those are different lists for boring reasons — a customer paid and you were not told, a standing instruction went out, the bank took a charge nobody announced, a cheque was written on Monday and cleared on Thursday.

None of that is an error. The error is never comparing the two, so a payment that was received but not recorded sits in the customer's outstanding balance for months and someone eventually chases a customer who has already paid.

You do not need a bank feed to do this

A live bank connection in India needs a paid Account-Aggregator licence, and most small-business software does not have one. It does not matter. Every bank's net banking exports a statement as CSV, and every one of those exports has the three columns that matter: date, description, amount.

That file is enough. Download it once a month, and the comparison can be done against what you have already recorded.

What matching actually means

Most lines match themselves. A payment you recorded on the 12th for ₹18,000 and a credit on the statement on the 13th for ₹18,000 are the same event, and software should pair them without asking you.

The pairing needs a little tolerance to be useful, because the two dates are rarely identical and amounts occasionally differ by rounding. A few days either side, and a rupee of slack, matches the great majority of lines. Anything stricter leaves you clearing everything by hand; anything looser starts pairing things that are not the same event.

The unmatched lines are the whole point

When the easy pairs are gone, what is left is short and it is the reason to do this at all:

  • Credits with nothing behind them — money received and never recorded. Usually a customer payment.
  • Debits with nothing behind them — bank charges, a standing instruction, an expense paid from the phone and forgotten.
  • Entries in your books with nothing on the statement — recorded but never actually banked, or a cheque still in transit.

Each of those is a small fix, and each one is a real correction to your books. A month with no unmatched lines is a month you can close.

The related job: turning the statement into expenses

The same file is also the easiest way to record expenses you would otherwise never enter. Debit lines can be categorised once — the keyword in the description mapped to a category — and remembered, so the second month's import is mostly already sorted and the third is nearly automatic.

This is worth doing even if you never reconcile, because expenses paid by UPI and card are exactly the ones that get lost, and a profit figure built only on the expenses you remembered to type is flattering and wrong.

How often

Monthly, when the statement is available, and before anyone looks at a profit figure for that month. Reconciling at year end tells you what went wrong across twelve months at the point when it is hardest to remember any of it.

What this article does not cover

How any of this is treated for tax, what records must be retained and for how long. Those are set by rules that change, and the sources are the GST portal, the Income Tax portal and your accountant. What is above is about your books matching reality, which is a separate and simpler thing.

Stay GST-compliant without the hassle

BizGST Pro creates compliant invoices with the correct tax split automatically, tracks payments, and keeps your GSTR-1 ready. Free forever to start.

Create free account →