Reconciliation Discrepancies: Common Causes and How to Fix Them
July 2026 · Reconciler
Try it while you read
This is the tie-out board Reconciler gives you: both sides side by side, matches explained in plain English, exceptions flagged. Read-only, and it never moves money.
Read-only ยท Never moves money
Reconciliation discrepancies almost always trace to one of a handful of causes: timing differences between when a transaction hits the bank and when it hits your books, unrecorded bank or processor fees, duplicate entries, transposed numbers, miscoded transactions, and payments applied to the wrong invoice. Find which one you are looking at and the fix is usually quick.
Last updated July 2026.
A reconciliation that does not balance is not a mystery, even when it feels like one at 6pm on the last day of the close. The difference between your general ledger balance and the statement in front of you was created by a specific event, and that event belongs to a short list. This is the list, with how to spot each one and how to clear it.
Why does my reconciliation not balance?
Your reconciliation does not balance because at least one transaction is recorded on one side but not the other, or is recorded differently on the two sides. That is the whole of it. Either the bank knows about something your ledger does not, your ledger knows about something the bank has not processed yet, or the same transaction was entered twice or with the wrong amount. Every reconciling item you will ever chase is a version of one of those three situations.
The reason it feels harder than that is volume. When one line is off by $12.40 inside a statement with 400 transactions, the difference is easy to state and slow to locate. The skill is not understanding the causes, it is finding which line among hundreds carries the one you are hunting.
What are the most common reconciliation discrepancies?
These are the causes that produce the large majority of real reconciliation differences, roughly in the order you will meet them.
| Cause | What it looks like | How to fix it |
|---|---|---|
| Timing difference | A check you wrote or a deposit you made has not cleared the bank yet | Leave it as a reconciling item and expect it to clear next period |
| Unrecorded fee | A bank charge, wire fee, or processor fee the bank took but you never booked | Post the fee to the right expense account and re-run |
| Duplicate entry | The same transaction imported or keyed twice, often from a bank feed plus a manual entry | Delete or void the duplicate, keep one |
| Transposition error | A number entered with two digits swapped, so the difference divides evenly by 9 | Correct the amount to match the source document |
| Miscoded transaction | The amount is right but it landed in the wrong account, so the account you are reconciling is off | Reclassify to the correct account |
| Unapplied or misapplied payment | A customer payment sitting unapplied, or applied to the wrong invoice | Apply it to the correct open invoice |
| Netted processor fee | A Stripe or PayPal payout booked net, so gross sales and fees never separate | Split the payout into gross sales, refunds, and fees |
| Reversed sign or wrong side | A refund booked as a charge, or a debit entered as a credit | Correct the direction of the entry |
What causes a bank reconciliation to be off by a small amount?
A small, stubborn difference is nearly always a fee, a rounding or transposition slip, or a single duplicated line. Start with fees, because they are the most common: a $30.00 wire fee or a $2.15 card processing charge that the bank deducted and your ledger never recorded. Next, test for a transposition by dividing the difference by 9. If it divides evenly, two digits were almost certainly swapped somewhere, for example $54.00 entered as $45.00 leaves a $9.00 gap. If neither fits, scan for a line that appears twice.
The classic bank-side reconciling items that are not errors at all are deposits in transit and outstanding checks: money that is real and recorded in your books but has not yet moved through the bank. Those belong on the reconciliation as open items, not corrections, and they clear on their own.
How do you find a reconciliation discrepancy?
To find a reconciliation discrepancy, work the difference from largest signal to smallest. First note the exact amount you are off and its sign, because the number itself is a clue. Then work this order:
- Check the difference against known patterns. Divisible by 9 points to a transposition. A round number like $30.00 points to a fee. A difference that equals a specific transaction on the statement points to a missing or duplicated entry.
- Compare counts. If the statement has 212 lines and your ledger has 213 for the period, you are carrying a duplicate. If it is the other way, something is unrecorded.
- Sort both sides by amount and scan. Matching lines cancel visually, and the odd one out tends to jump.
- Isolate by date. If last month tied and this month does not, the culprit was created this month, which shrinks the search.
This manual pass is exactly the work that automated discrepancy detection removes. Instead of sorting and scanning, you get the unmatched lines named and grouped by why they did not tie, so the search step disappears and you are left only with the decision.
How do you fix a reconciliation discrepancy?
Fix a reconciliation discrepancy by correcting the record that is wrong, never by forcing the balance. Once you have identified the cause, the fix follows from it: post the missing fee, delete the duplicate, reclass the miscoded line, apply the stray payment, or split the netted payout. Then re-run the reconciliation and confirm the difference is $0.00.
The one thing never to do is plug the difference with a manual journal entry to a suspense or "reconciliation" account just to make it balance. A plug hides the cause, and the same discrepancy comes back next month plus whatever new one arrives with it. If you genuinely cannot locate a small difference before a deadline, park it in a clearly labeled clearing account, document it, and resolve it in the following period rather than burying it in the account you just reconciled. A clean audit trail that shows why each item was moved is worth far more at year end than a balance that ties for reasons no one can explain.
Why do the same discrepancies keep coming back?
Recurring discrepancies usually mean the cause lives upstream of the reconciliation, in how transactions get recorded in the first place. Payouts that always post net will always need splitting. A corporate card whose charges land in the wrong account will miscode every month until the coding is fixed at the source. When card charges keep drifting into the wrong category or a receipt never makes it into the books, tightening how you capture and code every expense as it happens removes the discrepancy before it reaches the close instead of after.
The structural fixes that actually reduce the recurring load are worth more than getting faster at the hunt:
- Reconcile more often. A weekly or even daily pass keeps the search space small, so a difference surfaces while you still remember the transaction that caused it.
- Fix coding at the source. If the same vendor lands in the wrong account every month, correct the default, not the symptom.
- Separate payouts on the way in. Book processor deposits as gross sales, refunds, and fees so the netting difference never forms.
- Match automatically. Software that scores every candidate pair on amount, date, memo, and reference catches duplicates and misapplications the moment they appear, rather than at month end.
This is where an automated layer earns its place. Transaction matching that runs across your bank, cards, and processors ties the confident pairs on its own and surfaces only the exceptions, each with a plain English reason it did not match. If your books live in a specific ledger, the same approach applies through a read-only connection: teams on Dynamics 365 Business Central, NetSuite, or QuickBooks reconcile against their bank and processor data without maintaining a wall of match rules, and drive the month-end close down from an evening of ticking rows to a review of the handful of lines that genuinely need a person.
The short version
A reconciliation that will not balance is a solvable problem with a short list of causes: timing, fees, duplicates, transpositions, miscoding, and misapplied or netted payments. Read the difference for clues, compare the two sides methodically, correct the wrong record rather than plugging the gap, and fix the ones that recur at their source. Do that consistently and the tie-out stops being the part of the close everyone dreads.
See your accounts tie out to $0.00
Connect your bank, processors and ledger read-only. Reconciler matches transactions, flags what does not add up, and explains every match, so your books close faster. Read-only, never moves money.