What is a bank statement?

A statement is a closed period. Whatever happened between the opening date and the closing date is on it, and nothing else is. That completeness is what gives it standing: unlike a spreadsheet or an app export, there is no way for something to be quietly missing without the arithmetic failing.

What every statement contains

• Header. Bank name, account holder name and address, account number (often partially masked), sort code or routing number, and the statement period.
• Opening balance. The balance carried forward from the previous statement. It must match that statement's closing figure.
• Transaction lines. Date, description, amount, and usually a running balance after each line.
• Closing balance. The figure carried into the next period.
• Summary block. Often totals of payments in and out, fees charged, and interest paid or earned.
• Page numbering. Page 2 of 6 style numbering, which is how a recipient knows nothing was removed.

Reading the description field

The description is the part people misread most. It is not the merchant's trading name; it is whatever the payment network passed through, which can include an acquiring bank prefix, a store number, a city, a reference code and a truncated name. Two visits to the same shop can produce two different strings. This is why categorization has to match patterns within the text rather than expecting clean merchant names.

Debits, credits and sign conventions

Some banks print a single signed amount column where outflows are negative. Others use two columns, one for debits and one for credits, with all values positive. Both are correct and they have to be handled differently when the statement is analyzed. Getting this wrong reverses the entire result, and the totals often still look plausible enough that nobody notices.

The built-in check

Every statement can verify itself. Opening balance, plus all credits, minus all debits, equals closing balance. If it does not, either a line was misread or a page is missing. This one calculation is the most useful thing about the format and the reason statements are trusted where an app screenshot is not.

Statement types

Checking and current account statements show day-to-day movement. Savings statements are quieter and often show interest as a single annual line. Credit card statements are a different shape: they list purchases during the period, then a payment due date and a minimum payment, and the balance runs the opposite way to a bank account. Business account statements look like personal ones but carry more fee lines and higher-volume payment references.

A description decoded

A line reading something like a payment processor prefix, a truncated merchant name, a four-digit store number and a city is a single card purchase. The prefix identifies the acquirer rather than the shop, the store number distinguishes branches, and the truncation is a character limit rather than a name. Only the middle fragment is useful for categorization, which is why rules should target that token rather than the whole string.

A missing page found by arithmetic

A set of statements supplied for a loan application reconciled for every month except one, where the closing balance was out by several thousand. The cause was a page that had not scanned. Nothing on the visible pages looked wrong; the arithmetic was the only signal.

Two-column layouts

A statement showing separate Paid Out and Paid In columns, both with positive figures, converts badly if a tool assumes a single signed column. The result is a file where every transaction increases the total. Recognizing the layout before analysis is what prevents it.

• Authoritative. Issued by the bank, accepted by lenders, accountants and tax authorities.
• Self-verifying. The balance arithmetic proves nothing was dropped or duplicated.
• Complete for the period. Unlike a filtered app view, a statement cannot silently omit a transaction.
• Durable. A PDF you have downloaded stays readable long after online access to that period ends.
• Portable. The same document works for a mortgage application, a tax return and your own analysis.

• Substituting app screenshots. They lack the header, page continuity and balances that make a statement a statement.
• Only saving PDFs. Banks often keep CSV exports available for a shorter window than PDFs. Download both while you can.
• Ignoring page numbers. A gap in the sequence means a missing page and an incomplete record.
• Assuming the description names the merchant. It names whatever the payment network passed on, which is frequently something else.
• Deleting statements after a year. Tax and lending questions arrive years later, and retrieving old statements is slow and sometimes chargeable.
• Forgetting the credit card. A current account statement shows one payment where the card statement shows the actual spending.