How to Verify Bank Statement Accuracy

Most tools hand you a spreadsheet and leave that verification to you. The reconciliation step is the one that actually proves the data is complete, and it's the one most converters skip. Export Bank Statement runs it on every file and flags any statement that doesn't reconcile.

What "accurate" actually means here

A converted bank statement is accurate when the Excel or CSV file is a faithful copy of the PDF — every transaction present, every figure correct, every debit and credit on the right side. That's narrower than "are these the right transactions for my books", and it's the one to settle first; you can't trust categorisation, VAT, or a reconciliation in Xero if the rows drifted during conversion. Verification checks the conversion, not the bank: the PDF is your source of truth, and your job is to prove the extracted file matches it. Two things go wrong — a line goes missing or gets duplicated, or a figure gets misread — and the four checks below catch both.

Step 1: Re-derive the running balance (opening to closing)

This is the test that earns its place at the front, because it's the check that catches a transaction that isn't there.

Take the opening balance printed on the statement. Add every credit, subtract every debit, in date order. The number you finish on must equal the closing balance printed on the statement. If it matches, nothing was dropped, doubled, or misread badly enough to move the total. If it doesn't, a line is wrong, and you've caught it before importing anything.

A worked example. Say the statement opens at 3,210.00. The credits over the month come to 8,940.00 and the debits to 7,615.50, a net movement of 1,324.50. Opening plus net movement gives 4,534.50. If that's the closing balance on the PDF, the conversion held. If the file closes at 4,489.50 instead, you're 45.00 short, so go hunting for a single missing or misread 45.00 line.

The gap itself often names the error. A difference equal to one transaction means a line is missing or duplicated. A difference divisible by 9 — 54.00 read as 45.00 — points to transposed digits. A difference equal to the opening figure means the brought-forward balance came in wrong. You frequently know the *type* of mistake before you've found the row.

On a 200-line statement, re-deriving the balance by hand is slow and error-prone in its own right. Export Bank Statement recomputes opening plus transactions against the printed closing figure the moment a file converts, marks it reconciled or flags it, and points you at roughly where it broke, so you're not eyeballing a wall of numbers hoping the odd one out jumps at you.

Step 2: Count the rows against the statement

Count the transactions on the PDF. Count the rows in your spreadsheet. They must be equal.

It sounds too simple to bother with, but a row count catches what a balance check hides. If a transaction was read twice and another was dropped, the totals still net out. The running balance ties, yet the detail is wrong. The count exposes that in seconds. One row too many usually means a duplicate; one too few means a dropped line, most often near a page break where extraction slips. On a long statement, count per page so you know exactly where to look.

Step 3: Tie out the printed totals

Many statements print a total of money in and money out for the period, sometimes with a transaction count. Use them. Sum your extracted credits, sum your extracted debits, and check each against the printed totals separately, not just the net, because the net only repeats the running-balance test. Checking the two sides independently catches an error that's offset by another: a 200.00 credit misread into the debit column shifts both totals while leaving the net untouched. Tie out each side and that mistake has nowhere to hide.

Step 4: Spot-check a sample against the PDF

The running balance and the totals prove the figures add up. Now confirm individual lines actually say what the statement says.

• Pull five or six lines from across the period — not all from page one. Spread them out so a systematic fault has a chance to show.
• Always include the anchors: the first and last transaction on each page, plus the opening and closing balance. Page edges are where extraction slips cluster.
• Match four fields per line, not one. Check the date, the description or payee, the amount, and the debit-or-credit direction against the PDF. People check the amount and stop; the direction and the date are exactly where a quiet error sits.
• If two sampled lines fail, it's a pattern, not a fluke. Widen the sample, work out what the converter is getting wrong — wrapped descriptions, a signed-amount column, low-quality scan pages — and fix the source rather than patching rows one by one.

Six lines take a minute or two and catch the errors reconciliation masks: a date pushed into the wrong month, a garbled payee, a credit booked as a debit on a single signed-amount layout.

Watch for OCR digit slips on scanned statements

If your statement is a scan or a phone photo rather than a digital PDF, the transactions come out through OCR, which adds its own class of error: character misreads. A 3 read as an 8, an 8 as a 6, a 0 and an O swapped, a stray comma turning 1,500 into 1,50. The figure still looks plausible, which is exactly why it slides past a quick glance.

A misread digit changes a value without changing the row count, so it surfaces in the running balance (if it moves the total) and in the spot-check (always). Weight your sample towards the lowest-quality pages — faint print, skewed scans, tight fonts — because that's where misreads bunch up. Export Bank Statement handles scanned and photographed statements via OCR and runs the same reconciliation check on the result, so a digit slip that moves the balance gets flagged like any other error.

A quick reference: the four checks

Where the converter fits — convert, verify, then import

Verifying accuracy confirms the conversion is faithful to the statement. It does not move anything into your accounting software, and that distinction matters. With Export Bank Statement the path is convert, verify, then import the CSV into Xero, QuickBooks or Zoho Books yourself. There's no live bank-feed API quietly syncing in the background, since that's a separate, certified integration. You produce a clean, reconciled file and import it as statement lines you can trust.

What changes is the starting point. Instead of a spreadsheet with no clue whether it's complete, step one — the running-balance check — is already done and any non-reconciling statement is flagged before you open it. If it reconciles, go straight to the quick checks; if it's flagged, you know which file needs your eyes first. For the errors that start in extraction, common reconciliation errors and how to reconcile bank statements go deeper, the accountants and bookkeepers hub collects the rest, and region-specific guidance lives on the UK hub.