Bank Statement Health Check

Most people skip the first part, and that's the mistake we see most. They jump straight to "how much did we spend on subscriptions" without checking that every transaction made it onto the page. If a line is missing, every total downstream is quietly wrong, and you won't feel it until something refuses to tie out weeks later.

Start with reconciliation, not the totals

Here's the order that saves you grief. Before you read a single insight from a statement, prove the statement is complete.

Banks print a running balance for a reason. After each transaction, the figure on the right is the account's true position at that moment. So you can use it as a checksum: take the opening balance, apply every credit and debit in sequence, and the result has to match the closing balance printed on the last line. If it does, the statement reconciles and you can trust what follows. If it's out by, say, 312.40, something is missing or misread — and the gap is usually exactly the size of the transaction that went astray.

We test this constantly on extracted data. A statement that has been converted from PDF is only as good as the extraction, and extraction slips in predictable places. A row vanishes in the seam between two pages. A 1,290.00 debit gets read as 1,920.00 because the digits transposed. A credit lands in the debit column on a layout where the bank uses one signed amount instead of two columns. None of these announce themselves. The running balance is the one thing that catches all of them at once.

When you run a statement through Export Bank Statement, this check runs automatically. The tool extracts every line, then walks the running balance from the opening figure to the closing one. If the totals reconcile, you get a confirmation before you download anything. If they don't, it flags the statement rather than handing you numbers that look fine and aren't. That's the part most converters don't bother with, and it's the whole reason a health check is worth running on converted data at all.

What a full health check looks at

Once the data is verified, the health check moves from "is this complete" to "is this healthy". These are the things worth reading, and they're the same signals the built-in analyser surfaces once a statement is converted.

• Cash flow shape. Not just the closing balance, but the path it took. A statement can end the month higher than it started and still have spent ten days underwater in between. Look at the lowest point, not the last line.
• Income. How much came in, how regularly, and from where. Steady, named, recurring credits read very differently from lumpy, irregular ones — that distinction matters for lending, for hiring, for knowing whether a quiet month is a blip or a trend.
• Spending by category. Where the money actually goes once you group it. Card payments, direct debits, transfers, fees. The categories tell you the structure of the outgoings; a single large line item tells you far less.
• Recurring and merchant patterns. The payments that repeat — subscriptions, standing orders, loan repayments. These are the easiest things to lose track of and the easiest to act on. A forgotten 40 monthly charge is 480 a year doing nothing.
• Anything that looks off. Round-number transfers in and straight back out, a duplicate payment, a new recurring debit you don't recognise. These don't always mean trouble, but they're worth a second look.

The analyser pulls these out automatically after conversion: cash flow, income verification, expense categories, recurring detection and an overall statement health check. The point of running it on verified data is simple — every one of those insights inherits the reconciliation that came first. You're reading patterns from figures you've already proven are complete, not from a spreadsheet you're hoping is right.

How to run a bank statement health check, step by step

You can do this entirely by hand. Most people who've reconciled a few statements know the drill: foot every page, tick the running balance, total the credits and debits, then eyeball the patterns. It works. It also takes an afternoon for a busy account, and the manual re-keying is exactly where new errors creep in.

The faster route, on data you can trust:

1. Get the statement as a PDF. Download it from online banking for the period you're checking. A scan or a phone photo of a paper statement is fine too — it'll be read by OCR.
2. Convert it. Upload the PDF at /convert. The tool reads each line — date, description, money in, money out, balance — across however many pages the statement runs to.
3. Read the reconciliation result. This is the health check's foundation. Confirm the totals reconcile before you trust anything else. If the statement is flagged, you've caught a gap that a manual skim would probably have missed.
4. Open the analyser. Review the cash flow, income, categories and recurring payments. This is where the account's story shows up.
5. Export if you need it elsewhere. Take the clean .xlsx for your own working, or the CSV in the native bank-import format if it's bound for your accounting software.

A single month is usually done in well under a minute, which changes how often you bother to check at all.

A worked example

A client account, one quarter, around 240 transactions across an eleven-page PDF. By hand, that's a genuine afternoon — and when I footed it the first time, page seven didn't tie out. Two transactions had landed on a single row during a copy-paste, so the total was understated by the second one. Easy to miss, because nothing on screen looked wrong; the numbers were just quietly short.

Run the same PDF through the converter and the reconciliation check flagged it as not balancing, pointed at roughly where the gap sat, and did it in seconds. Once that was sorted, the analyser showed the actual problem the client had come in about: a slow drift in cash flow, driven by three recurring card subscriptions that had crept up over two years and a payment cycle where money left a week before the big invoices were paid. None of that is visible from the closing balance. All of it is obvious once the data is verified and grouped.

Health check versus a full reconciliation in your ledger

Worth being precise here, because the words overlap. A bank statement health check is a read of the statement itself — proving it's complete, then understanding what it shows. Reconciliation in your accounting software is a different, later job: matching those statement lines against the transactions already recorded in your books.

Export Bank Statement handles the first and feeds the second. It converts the PDF, verifies the figures reconcile against the running balance, and exports a CSV in the native bank-import format Xero, QuickBooks and Zoho Books expect. One honest caveat, because it's easy to assume otherwise: this is a file import, not a live bank feed. The tool doesn't push transactions into your ledger through a certified bank-feed API. You convert, then you import the CSV, and it lands as reconcilable statement lines. If you're working from PDFs after the fact, that's the cleaner path anyway — you already know the file balances before it ever reaches your books.