Why Your Converted Bank Statement Doesn't Balance
A diagnostic guide to reconciliation failures: what each symptom means and how to find the row causing it.
Your converted file does not reconcile. This is a diagnostic guide — each symptom points at a specific cause.
Symptom: the chain fails at one row and every row after it
Cause: one amount was misread. Everything after that row is downstream of the single error.
Find it: the first failing row is the culprit. Compare it against the PDF. The difference between the expected and actual balance is the size of the misreading, which often identifies the digit involved.
Symptom: the chain fails everywhere, randomly
Cause: almost always sorting, not data. The rows are not in the order the balance moved in.
Fix: sort by date, and on a sectioned US statement make sure sections were merged chronologically rather than in printed order.
Symptom: the chain holds but the totals do not match
Cause: rows are missing. The remaining rows chain correctly against each other, which is exactly why this failure is dangerous.
Find it: the difference between your total and the printed total is the sum of what is missing. Compare row counts per page against the PDF.
Symptom: totals are exactly double
Cause: the summary block was imported as transactions, so the printed total is being counted alongside the rows it summarises.
Find it: look for rows with an amount but no date. Those are summary lines.
Symptom: amounts are 100x too large or too small
Cause: the decimal convention was read wrongly — a decimal comma treated as a thousands separator, or vice versa.
Fix: compare one row against the PDF to confirm, then re-convert. See Santander for the mechanics.
Symptom: every transaction is a debit
Cause: a combined amount column with DR/CR markers was read as a single direction, or a sectioned statement lost its section context.
Symptom: many rows with a description and nothing else
Cause: continuation lines being emitted as separate transactions instead of being merged into the row above.
Quick reference
| Symptom | Cause |
|---|---|
| Fails at one row, then all after | One misread amount |
| Fails randomly throughout | Rows out of order — sort by date |
| Chain fine, totals short | Missing rows |
| Totals exactly double | Summary block imported as transactions |
| Amounts 100x out | Decimal convention misread |
| All debits, no credits | Combined column or lost section context |
| Rows with only a description | Continuation lines not merged |
| Dates outside the period | Date format misread |
Frequently asked questions
What if the original statement itself doesn't balance?
It happens occasionally on genuine statements, and routinely on edited ones. If the printed summary contradicts the printed rows, that is worth understanding before relying on the document.
Is a small discrepancy acceptable?
No. A few units off means a row is missing or wrong. The size of the discrepancy says nothing about the seriousness of the cause.
Related posts
- Balance-Chain Reconciliation: Prove a Statement Is Complete
- What Is a Running Balance, and Why Does It Matter?
- Bank Statement Conversion for Small Business Bookkeeping
Convert a statement now
Bank Statement PDF to Excel, or see every format. More in the guides.