Guides

Why a Converted Bank Statement Does Not Balance — and How to Fix It

So the check failed. The rows you got do not add up to the closing balance printed on the statement. Do not panic, and do not shrug and download anyway. A difference is a clue, and it usually points at its own cause. This guide lists the six reasons we see again and again, shows how the size of the difference names the culprit, and gives you a short routine to find and fix the bad row.

First, know what 'does not balance' means

A statement prints an opening balance and a closing balance. Between them, money came in and money went out. The math has to hold:

Opening balance + money in − money out = closing balance.

When a converter reads the statement, it rebuilds that math from the rows it found. If the rebuilt closing balance differs from the printed one, something in the row set is wrong: a row missing, a row doubled, or a row with a wrong amount or the wrong sign. The converter shows you the difference and flags the rows that could explain it. Your job is detective work, and the difference is the first witness.

Read the difference like a detective

Before you look at a single row, look at the number itself. Differences have shapes, and shapes have causes:

The sign trick deserves its own line, because it feels like magic the first time. If a $42.10 payment is counted as money in instead of money out, the total is wrong by $84.20 — the amount was added where it should have been taken away. So when the difference is an even, clean double of some row you can see, you have found your row. Flip its side, or delete one copy if it was doubled, and re-check.

The six usual causes

1. A row was read twice

Some PDFs print a page's last row again at the top of the next page as a carry-over. Some banks list a fee in a summary box and again in the transaction table. Either way, one real transaction becomes two rows. The difference equals that row's amount. Delete the copy.

2. A row was missed

A row printed in an odd place — a footnote area, a second small table, the back of the last page — can escape the main table. The difference equals the missing amount. Add the row by hand in the editor: date, text, amount. The check will confirm you got it right.

3. A sign is flipped

Statements that print one Amount column rely on signs or on section headings ('Electronic Debits') to say which way money moved. A refund among payments, or a reversal, can be read the wrong way. The difference is twice the row. Move the amount to the other column.

4. A summary line was read as a transaction

Lines like 'Total fees this period' or 'Interest paid year to date' are summaries, not transactions. If one slips into the rows, the difference is usually round or equals a total printed elsewhere on the page. Delete the summary row; the real transactions are already there.

5. The statement covers more than one account

Combined statements — a checking account and a savings account in one PDF, common at credit unions — carry two opening balances and two closing balances. Rows from both accounts in one pot cannot balance against either. Convert, then split the rows by account, checking each against its own summary. Our bank pages note which banks love this layout.

6. The PDF itself is damaged or degraded

Scans with a text layer added later, or files with broken font encoding, can produce rows that look fine and numbers that are quietly wrong — an 8 read as a 3. If the difference is small and shapeless and nothing else fits, compare a few rows digit by digit against the PDF. If the file is a scan, the real fix is a better file: download the digital original from the bank, as our guide on scanned and digital statements explains.

The fix-it routine, in order

1. Write down the difference. Check it against the shapes in the table above.
2. Look at the flagged rows first — the converter marks rows equal to the difference, likely doubles, and the row where the running balance chain breaks.
3. If your statement prints a running Balance column, scan it in the result table: the chain should move by exactly each row's amount. The row where it jumps wrong is your row. Our guide on checking a conversion shows this scan in detail.
4. Compare the section totals. Many statements print totals per section (deposits, checks, fees). The section whose total disagrees is the section to search.
5. Fix in the editor — delete a double, add a missing row, move an amount to the other column — and save. The check re-runs at once.
6. If you reach a difference of a few cents with clean rows everywhere, look for a fee or interest line that exists both in a summary and in the table, and remove the summary copy.

What not to do

Do not 'fix' a difference by adding a fake row called 'adjustment' to force the total. You have made the math quiet and the record wrong. That row will sit in the books until an auditor, a lender or the tax office asks what it was — and nobody will know. A difference you cannot explain is information: it means the file or the statement reading needs one more look. Keep the PDF, note the difference, and if the layout truly beats the reader, send it to support. Layout reports fix readers; fake rows fix nothing.

Also do not assume the bank is wrong. Banks do make mistakes, but they are rare, and a statement that was re-issued or corrected will say so. Ninety-nine times in a hundred, a difference is a reading problem — doubled, missed, flipped or merged rows — and reading problems have row-level fixes.

Why this work is worth ten minutes

Reconciliation is not fussiness invented by accountants. It is the same idea banks themselves are held to: a statement must account for every cent between two balances, and regulators spell out what a statement has to show (our sources include the US rule). When your converted file reconciles, you hold proof — not hope — that the rows are complete. That proof is what lets you import into QuickBooks, hand the file to a client, or file it for taxes and move on with your day.

If your statement balanced first try, this guide was a pleasant read. If it did not — you now have a short list, a shape table and a routine. Work it from the top. The row is in there, and the difference already told you its name.

A worked example: the case of the $84.20

A bookkeeper converts a café's April statement. The check fails: difference $84.20. She does not open the PDF. First she reads the number. $84.20 is even and clean, so she halves it: $42.10. Then she searches the result table for 42.10 and finds it — a card payment to a food wholesaler. On the statement, that row sits in the Electronic Debits section: money out. In the converted file it landed as money in, because the row was a refund-style line ('REVERSAL — WHOLESALE MART') whose heading context was lost at a page break.

She moves the amount to the debit column and saves. New difference: $0.00. Reconciled. Total time: under two minutes, most of it spent reading the difference instead of hunting rows at random. File this story away for your own failed check: the difference is rarely the enemy. It is the first, best clue — and it usually names its own cause, if you know the shapes.

When the difference is added later, by the next tool

Sometimes the converted file reconciles perfectly, and the imbalance appears after import into another program. The usual suspects live at that border. A CSV import with the amount sign convention flipped turns the whole statement inside out — every debit a credit — which produces a huge difference, twice the money out. A spreadsheet in a country that uses commas for decimals can read 1,200.00 as text or as 1.2, quietly shrinking big rows. And an import limited by rows or file size can cut a long statement short, dropping its tail.

The defence is order of operations: prove the file first (it reconciles against the statement), then import, then reconcile again inside the destination. If step two disagrees with step one, the fault is in the import settings, and you will find it in the mapping screen — not by re-checking 200 innocent rows.

Keep a note when you fix one

When you find and fix a bad row, leave a one-line note with the file: 'April: one reversal row moved to debits, difference cleared.' It takes ten seconds and it is the difference between a record and a riddle when a client, an auditor or future-you asks why the downloaded file differs from a fresh conversion of the same PDF. Corrections are normal professional work. Unexplained corrections look like something else.

The rare case: two errors that cancel out

Honesty requires one caveat. Two errors can hide each other: a $50 row missed and a different $50 row doubled leave the totals perfect and the rows wrong. It is genuinely rare — the two mistakes must match to the cent — but it is why the pros do not stop at the equation. Section totals shrink the hiding place (both errors must fall in the same section to stay hidden), and the row-count check shrinks it further (a missed row and a doubled row keep the count right only if both happen together). If your statement carries counts and section totals, use them; that is what they are printed for. Our full checking routine layers all three.

How long this should take — and when to hand it over

Most differences fall in five minutes: read the difference, match its shape, fix one row, re-check. Budget fifteen before changing strategy. If the difference survives the shapes table, the section totals and the chain scan, the file itself may be the problem — a damaged text layer or an unusual layout. That is the moment to write to support with four facts: the bank, the statement month, the size of the difference, and what you already tried. Those four facts turn a support exchange from a week of questions into one useful answer — and reports like yours are literally how the reader learns the layout that beat it.

One more hiding place deserves a mention before we close: the statement that spans a product change. When an account is migrated — a merger, a new card number, a plan change — the bank may print two summaries in one document, one per sub-period. Each half balances on its own numbers, and neither half matches the whole file. If your difference equals the smaller summary's totals, you have found this case: split the file at the change, check each half separately, and note the split alongside the file.

Sources and further reading

• What is a bank reconciliation? — University of Central Florida (graduate studies guide, PDF)
• Regulation E, §1005.9: what a periodic statement must show — Consumer Financial Protection Bureau
• What kind of records should I keep? — Internal Revenue Service (IRS)

More guides

How to Convert a Bank Statement PDF to CSV · How to Convert a Bank Statement PDF to Excel · How to Import Bank Statements into QuickBooks (QBO Files) · OFX vs. QBO vs. QIF: Which Format Should You Download? · How to Check a Converted Bank Statement Is Correct · Scanned vs. Digital Bank Statements: Why One Converts and the Other Does Not · How to Convert a Password-Protected Bank Statement PDF · How to Convert Many Bank Statements at Once (and Merge Them Cleanly) · Is It Safe to Convert Bank Statements Online? A Privacy Checklist