Common Reconciliation Errors

The fastest way to find which one is to walk the running balance row by row. The first line where your figure and the bank's diverge is where the error lives — you don't have to re-check the whole statement, just the rows from there.

The errors that break a reconciliation most often

Here are the ones we see again and again, roughly in order of how often they're the real cause.

1. Wrong opening balance. The opening balance on a statement must equal the previous period's closing balance. When it doesn't — usually because a prior period was never properly closed, or a brought-forward figure was keyed by hand — every later total is off by the same amount. This one is sneaky because the *new* period can still balance internally while being wrong overall.
2. A missing transaction. A payment that never made it into your records. It might have been skipped during data entry, lost when a multi-page PDF was copied, or dropped off the bottom of a page. The ledger looks complete; it isn't. The running balance is the only check that reliably catches an entry you never saw.
3. A duplicated transaction. The opposite problem — the same payment entered twice. Common when a statement is imported once, then imported again "to be safe", or when a manual entry and an automatic one overlap. Two 120 direct debits where there should be one will throw the closing balance out by exactly 120.
4. Transposed digits. 54 keyed as 45, or 1,290 as 1,209. The amount looks plausible, so the eye skates over it. The tell is a difference that's divisible by 9 — a classic transposition signature. The running balance still won't reconcile, which is what flushes it out.
5. Timing differences. Cheques you've written but the bank hasn't cleared, deposits in transit, or a payment that left your account on the 31st but cleared the bank on the 1st. These are legitimate reconciling items, not mistakes — but treat them as mistakes and you'll chase a difference that was never an error. List them; don't post them away.
6. Uncleared and bank-only items. Fees, interest, standing orders, and direct debits often hit the statement before they're in your books. Miss them and your side is short. They're easy to fix once spotted: post them, then re-check the running balance.
7. Miscategorised entries. Putting a transaction in the wrong account or the wrong period. This usually doesn't break the closing balance — the maths still ties — which is exactly why it's dangerous. It passes the balance check but distorts your reporting, VAT, and any later analysis.

Why most of these hide until the running balance catches them

Matching transactions one by one feels thorough, and it catches plenty. But matching only checks the entries you already have. It can't tell you about an entry that isn't there. You can tick off every line in front of you and still be missing a payment — and a missing payment is the single hardest error for a person to notice, because there's nothing on the page to draw your eye to it.

The running balance fixes that. The bank prints a balance after every transaction. If you take the opening figure and apply each transaction in date order, your total should match the bank's running balance at every row. The first row where it stops matching is the error. We've reconciled statements that looked immaculate until row 41, where a 2,300 transfer had quietly gone missing — eyeballing the list would never have found it, but the running balance flagged it on the first pass.

A difference that's divisible by 9 usually points to a transposition. A difference equal to a single transaction amount usually means that line is missing or duplicated. A difference that's exactly your opening figure means the brought-forward balance is wrong. The size and shape of the gap tells you which error you're chasing before you've found it.

How errors creep in when the statement starts as a PDF

If your statement arrived as a PDF, a scan, or a phone photo, every error above still applies — and extraction adds one more layer. A character misread (a 3 read as an 8), a wrapped description split across two rows, or a column shifted by one will break the maths without changing how the spreadsheet looks. A miscount during copy-paste produces a missing or duplicated line by accident.

Here's the honest workflow we'd recommend. Export Bank Statement converts the PDF — including scanned and photographed statements, via OCR — into clean Excel or CSV. The part that matters for reconciliation is what happens next: it runs the running-balance check for you, recomputing opening balance + transactions against the printed closing balance and flagging any statement that doesn't reconcile. So a misread digit or a dropped line shows up before you trust the numbers, not after you've posted a month of entries.

Getting it into your accounting software is convert, then import the CSV. The tool exports in the native bank-import format for Xero, QuickBooks, and Zoho Books, so the lines arrive as reconcilable statement lines. It does not push transactions through a live bank-feed API — that's a separate, certified integration — so treat it as producing a verified import file, not a one-click sync. For the errors that originate in extraction specifically, why extracted transactions don't reconcile goes deeper.

A quick reference: error, signature, fix

The signatures in the middle column are the useful part: once you know the shape of the difference, you usually know the error before you've found the exact row.

A worked example

Say a statement opens at 4,000 and closes at 6,150, and your records close at 6,060 — a 90 gap. 90 isn't divisible by 9 cleanly in a way that suggests a single transposition, and it doesn't equal any one transaction, so it's likely two issues. Walking the running balance, your figure first diverges at a 45 supplier payment you'd entered as 54 (a 9 transposition that the eye missed), and again at a 81 card fee the bank charged that never made it into your books. Correct the 45 and post the 81, re-run the balance, and it reconciles to zero. The point isn't the arithmetic — it's that the running balance told you *where* both errors were, instead of leaving you to re-check sixty rows by hand.