Bank Reconciliation Off? How to Find the Difference
When your reconciliation doesn't balance, work through the gap in a specific order: do the quick math checks first, then compare line by line against the statement, then check dates and cleared status. Most discrepancies come down to one missed entry, one transposed number, or one transaction marked cleared by mistake. A systematic pass usually finds it faster than re-adding everything from scratch.
Reconciliation discrepancies feel bigger than they usually are. A $14.32 difference can mean you're missing a $14.32 transaction, or it can mean two unrelated errors that happen to net out to that number. The fastest way through it is to stop guessing and work a checklist, narrowing the possibilities until only one explanation is left standing.
Start with the common culprits
Before you re-check every line, test the difference amount against a few patterns that explain most reconciliation gaps:
- A single missed transaction: the difference exactly matches one purchase, fee, or deposit you haven't entered yet.
- A transposed number: if the difference is evenly divisible by 9 (like $9.00, $18.00, $45.00), that's a classic sign of a transposed digit, such as entering $52.00 instead of $25.00.
- A duplicate entry: you logged a transaction twice, or entered it once and it also came in through a CSV import.
- A decimal or rounding slip: $45.00 entered as $450.00, or a transaction entered in whole dollars that actually had cents.
If the difference matches a specific transaction amount on your statement, check your register for that exact entry first. That's usually the fastest find of the whole process.
Check for transactions entered on the wrong side
Not every gap comes from a missing entry, though. A deposit entered as an expense (or an expense entered as income) throws off the balance by double the transaction amount, not the transaction amount itself. So if your difference is $60 and you can't find a $60 entry, check whether there's a $30 transaction entered with the wrong sign. A $30 deposit mistakenly logged as a $30 expense creates a $60 swing.
Transfers run into the same problem. If you moved money between two of your own accounts and recorded it as a regular expense in one account instead of a transfer, the linked side never posted, and both registers will be off.
Verify every statement transaction has a matching entry, and vice versa
This is the line-by-line part, and there's no shortcut around it. Go down your bank statement and, for each transaction, find the matching entry in your register. Then flip it around: go down your register's cleared transactions and confirm each one actually appears on the statement.
You're checking for two different failure modes at once: something on the statement that never made it into your register, and something in your register marked cleared that the bank never actually processed.
Pay close attention to small, easy-to-miss items: bank fees, interest earned, ATM surcharges, and any automatic payments that post without a reminder. These are the entries people forget to log because nothing prompted them to.
Look for transactions outside the statement period
Dates cause their own category of errors. Transactions dated after your statement's closing date shouldn't be marked cleared yet. If one is, it's inflating or deflating your reconciled total for a period it doesn't belong to. Similarly, check for anything dated before your statement's opening date that's marked cleared in this reconciliation but was actually cleared on a previous one.
Date-range mistakes are easy to make when you're reconciling multiple months back to back, and they're easy to miss unless you specifically check the date against the statement period.
Narrow the gap using the running difference
The checklist above doesn't always surface the answer, but your reconciliation tool's running difference can help narrow things down further. Use it actively as you check off items, rather than just watching the final number. Uncheck everything, then clear items back in a handful at a time, watching how the difference moves.
When checking off a batch of five transactions doesn't change the gap at all, the error isn't in that batch. Move on. A difference that jumps unexpectedly when you clear one particular transaction points straight at your suspect.
This divide-and-check approach turns a long list of transactions into a much smaller set to inspect closely. For the full step-by-step process of matching a statement from scratch, see how to reconcile a bank statement step by step.
It also helps to understand what cleared and uncleared actually mean before you start chasing a number. A transaction your bank shows as pending isn't the same as one that's posted and cleared, and mixing those up during reconciliation creates differences that look like errors but aren't. See cleared vs pending on a bank account for that distinction.
If you still can't find it
Sometimes the difference isn't one error. It's two or more that happen to combine into a number that looks like a single mistake. If you've gone through the checklist above and nothing matches, try reconciling against an earlier statement where you know the numbers were correct, then work forward one statement at a time. This isolates which period introduced the problem instead of searching your entire register at once.
Where this fits in a checkbook register app
In LedgerFlow, reconciling an account works by entering your statement's ending balance and ticking off the transactions that cleared, with a running difference shown as you go. That supports the narrowing process described above instead of doing the math by hand.
Selecting and clearing multiple transactions at once (or unclearing them to re-check) is free. Entering a statement balance and saving reconciliation history is part of LedgerFlow Pro, along with reports, recurring transactions, and CSV import.
FAQ
Why does my reconciliation show a difference even though I've checked every transaction?
Double-check the statement period dates on anything you've marked cleared. A transaction cleared slightly before or after the statement's date range is a common cause that's easy to miss on a first pass, since the transaction itself is accurate and just dated wrong relative to this statement.
Is a small difference, like a few cents, worth tracking down?
A few cents is usually a rounding or data-entry slip rather than a real missing transaction, but it's still worth a quick look, since unresolved small differences tend to compound across future reconciliations if the underlying entry error isn't fixed.
What's the difference between my running balance and the reconciled balance?
Your running balance reflects every transaction you've entered, cleared or not; the reconciled balance only reflects what the bank has actually processed as of the statement date. For more on that distinction, see running balance vs. available balance.
Should I just force the balance to match by adjusting an entry?
It's better to find the actual cause than to plug an adjustment, since a forced match hides a real error that will likely resurface. If you truly can't locate it after a thorough check, note it and verify against your next statement instead of guessing at a fix.
For a broader rundown of what commonly throws off a register balance in the first place, 9 checkbook register mistakes that throw off your balance covers the patterns worth watching for going forward.
If you want a reconciliation view with a running difference and bulk clearing built in, LedgerFlow has that. Download LedgerFlow free on iOS and Android to keep a running balance across all your accounts, reconcile against your statement, and always know what you can actually spend.
Track it all in one place
LedgerFlow keeps a running balance across every account — free on iPhone and Android.