Skip to main content

ERP glossary · Finance

Bank Statement

A bank statement is the bank's record of every movement into and out of an account over a period, against which a business reconciles its own books.

Also called Statement · Bank feed · Account statement · Passbook

Why it exists

Because a business's own record of its money is an assertion, and the bank's record is the independent check that makes it evidence.

What it means to the business

Reconciliation is the only routine control that tests the accounts against something outside them. Everything else in finance checks the books against the books. That independence is why the exceptions matter more than the completion: the unmatched list is the finding, and a reconciliation reported as done with nothing learned usually means the list was cleared rather than worked.

01Lifecycle — walk the states

Imported. Lines loaded, nothing matched.

State 1 of 3

02Relationships — walk the chain

Bank Statement reconciles Payment.

Open Payment
03What goes wrong — and why
  • The reconciliation completes and the discrepancy survives, now disguised. This is how genuine errors and occasionally fraud persist for months — the control ran and reported success.

Rules that must hold

  • The statement is the external record. Where it and the ledger disagree, the ledger is the one to investigate first.
  • Every statement line is either matched to a book entry, or it is an exception requiring explanation. There is no third category.
  • Reconciliation is periodic and complete. A partial reconciliation that leaves unmatched lines is a deferred problem, not a finished task.

What commonly goes wrong

It becomes a monthly ritual measured by completion rather than by findings. Unmatched lines get forced or written to a suspense account that nobody empties, and the one control capable of catching an error the books cannot see stops being capable of it.

Edge cases

  • Timing differences at period end — issued but uncleared, which are legitimate and must not be forced.
  • Bank charges and interest appearing only on the statement, needing a book entry rather than a match.
  • Bounced payments, which appear twice on the statement and must reopen the invoice rather than net to zero.
  • Multi-currency accounts, where the statement is in one currency and the books in another.

How ERPNext models it

DocTypeNote
Bank TransactionOne row per statement line. `status` moves to Reconciled only on a real match.
Bank Reconciliation ToolMatches transactions to Payment Entries. Its unmatched list is the actual output — that list is the work.
Payment EntryThe book side. A payment with no statement line is either timing or fiction.

Last reviewed 2026-08-14

Machine-readable version

See it live

Make a bank statement yourself in a real ERPNext, in your browser.

ERPNext

The bank statement matches itself

Statement lines match their invoices on their own; you only review the odd one.

Bank Transaction

Next step

We set these documents up for businesses as part of Analytics & AI; the mistakes above are the ones we see when they are skipped. Read the implementation guide, or book a demo