Bank Reconciliation Discrepancies: 10 Common Causes and How to Fix Each One
When your bank statement and your accounting records disagree, the difference almost always falls into one of ten categories. Diagnose which one, apply the matching fix, and the reconciliation closes.
Start with the assumption that the difference is explainable
Most reconciliation discrepancies are not evidence of fraud, collapse, or incompetence. They are usually the predictable result of timing, duplication, omitted fees, mispostings, or badly handled imports. The real cost comes from not having a repeatable way to test those causes in the right order.
The useful mindset is simple: treat the difference as a clue, not a crisis. Once you classify the type of mismatch, the fix is normally much faster than the initial panic suggests. This guide is the diagnostic spoke of our broader UK bank reconciliation pillar: head there for the full 7-step process, and use this guide when something on that process is not closing cleanly.
Quick answer
Bank reconciliation discrepancies almost always fall into one of ten categories: timing differences (uncleared cheques, deposits in transit), bank fees and interest not yet posted, transposed digits, duplicate entries, missing entries, batched payments (Stripe / PayPal / merchant settlements), period mismatch (book and bank cover different date windows), opening balance drift from a previous period, FX rate slip on foreign currency transactions, and posting reversals (e.g. failed direct debit then re-tried). Diagnose by amount: an exactly £0.45 difference is usually a transposed-digit or fee issue; a difference equal to a single bank line is usually a missing entry or duplicate. The fix follows the diagnosis, not the other way round.
Why Bank Reconciliation Discrepancies Happen to Everyone
Bank reconciliation discrepancies occur when the transactions in your accounting records do not match those on your bank statement. Even professional bookkeepers regularly face these mismatches during bank reconciliation, as the AAT's professional resources acknowledge. The difference is they have efficient systems to identify reconciliation causes and fix reconciliation errors before they snowball.
Whether you're handling your own books or working with an accountant who's asked you to "fix the reconciliation issues," understanding the common causes of bank reconciliation discrepancies is the first step toward resolving them more efficiently. ACCA's technical guidance on bank reconciliations covers the fundamentals in detail.
Sound familiar?
A pattern repeated across small business owners and bookkeepers we have spoken to: the work itself is rarely the problem. It is the chase for one missing entry throwing everything off, and the absence of a structured way to test what type of mismatch you are dealing with.
The 10 most common reconciliation discrepancies (and how to fix each one)
The fastest way to close a reconciliation is to recognise which type of discrepancy you have, then apply the matching fix. Each cause below has a diagnostic clue (what the difference looks like) and a concrete fix.
Timing differences (uncleared cheques, deposits in transit)
Diagnostic clue: the unmatched item appears in your books but not on the bank statement (or vice versa), with a transaction date close to the period end.
Fix: document the item in your reconciling-items schedule. No journal needed; the item will clear in the next period. Maintain a running list of outstanding cheques and deposits so they do not get re-investigated each month.
Bank fees and interest not yet posted
Diagnostic clue: the bank statement shows a small charge or interest credit (typically £1-£100 range) that does not appear in your books.
Fix: post the fee to Bank Charges nominal (typically 7900 in Sage, similar in Xero / QBO / Pandle). Post interest to Interest Received income. Set a monthly recurring journal if the fee structure is predictable.
Transposed digits
Diagnostic clue: the difference between books and bank is exactly divisible by 9. Example: a difference of £45 indicates the difference between £1,583 and £1,538 (digits 8 and 3 swapped).
Fix: grep your accounting records for the difference figure (or 1/9 of it). Find the entry with swapped digits. Post a correcting journal: debit/credit the same nominal as the original entry, with the correction amount.
Duplicate entries
Diagnostic clue: two identical-amount lines in the books with the same date or similar dates. Common when both a manual entry and an automatic bank feed import the same transaction.
Fix: identify the duplicate (often the later-dated one). Reverse it with an opposite journal. Add a unique reference field discipline so duplicates are flagged at entry-time in future.
Missing entries
Diagnostic clue: a bank line with no matching books entry. Common for direct debits, standing orders, or any payment processed outside the manual entry workflow.
Fix: post the missing entry with the correct nominal code, contact, and VAT treatment. Set up a bank rule so the same payment auto-categorises next time.
Batched payments (Stripe, PayPal, merchant settlements)
Diagnostic clue: the bank statement shows one deposit but the books show multiple individual sales. The bank deposit is typically lower than the sales total because the payment processor deducted fees.
Fix: treat the payment processor as a separate clearing account. Record gross sales as income, fees as Bank Charges or Selling Fees, refunds as credit notes, and the net deposit as a transfer from the clearing account to the bank. Bank Reconciler’s merchant parsers handle eBay / Amazon / PayPal automatically.
Period mismatch (book and bank cover different date windows)
Diagnostic clue: a substantial unexplained difference, often exactly equal to the activity for one or two days.
Fix: verify both data sets cover the exact same period (e.g. 1-31 March, not 1-30 March on one side and 1-31 on the other). Re-export with matching date ranges and re-run the reconciliation.
Opening balance drift from a previous period
Diagnostic clue: the closing balance on each side individually looks correct, but the running balance does not tie. Indicates the reconciliation is built on top of a previously unresolved discrepancy.
Fix: walk back through prior reconciliations until you find the period where the opening balance ceased to match. Resolve that period first, then re-do downstream months. Painful but unavoidable: skipping the historical fix means the books are permanently misstated.
FX rate slip on foreign currency transactions
Diagnostic clue: small, consistent differences (a few pounds per transaction) on accounts with USD or EUR activity. The accounting software used one rate, the bank used another.
Fix: post the variance to a dedicated FX Variance nominal. For high-volume FX accounts, set a per-transaction tolerance (e.g. write off anything below £2 automatically). For VAT, use HMRC monthly published rates regardless of what the bank applied. See our multi-currency reconciliation guide for the full FRS 102 treatment.
Posting reversals (failed direct debit then retried)
Diagnostic clue: three bank lines for the same amount: the original payment, a reversal, and a successful retry. Two cancel out, one is real, but the books may have only the original.
Fix: post the reversal as a credit, then re-post the successful retry as a fresh expense. The net P&L impact is the same (one expense), but the trail matches the bank movements.
Traditional vs. Modern Approaches to Fixing Reconciliation Discrepancies
For the full reconciliation process
This guide is the discrepancy-diagnosis spoke. The complete 7-step bank reconciliation process (preparing data, comparing opening balances, matching transactions, posting adjustments, and signing off) sits in the canonical pillar:
Bank Reconciliation UK: 7-Step Guide for 2026
Step-by-step process, common mistakes, frequency guidance, business-type variants (sole trader, limited company, charity, construction), and platform-specific notes. Use this guide for the running process; come back to the discrepancy guide above when something does not close cleanly.
The Technology Revolution in Reconciliation
Traditionally, tracking down bank reconciliation discrepancies has been viewed as a necessary but painful chore. Today's technology has fundamentally changed how businesses identify reconciliation causes and fix reconciliation errors:
Pattern Recognition
Modern reconciliation algorithms can identify transaction patterns invisible to humans who are comparing entries line-by-line. This includes recognising transposed digits, decimal errors, and split/batched payments.
Description Matching
Banks often truncate or modify transaction descriptions. Advanced tools can match transactions with different descriptions but identical amounts and approximate dates.
Speed & Scale
Computers can compare thousands of transactions in seconds, making reconciliation time largely independent of transaction volume. This enables more frequent reconciliation for better financial control.
Error Categorisation
Beyond just identifying mismatches, modern tools categorise discrepancies by type (timing, missing entry, potential error), helping you focus attention where it's needed most.
Best Practices for Efficient Reconciliation
Once you understand common discrepancy causes and have a systematic process, advancing to bank reconciliation mastery means refining your workflow with these efficiency practices:
- Reconcile more frequently. Monthly is standard, but with automated tools, weekly or bi-weekly reconciliation becomes practical and helps catch issues sooner. HMRC's guidance on keeping business records underscores why regular checks matter.
- Create a reconciliation schedule. Set recurring calendar appointments to ensure this critical task doesn't get overlooked during busy periods.
- Maintain consistent transaction descriptions. When entering transactions manually, use consistent naming conventions to make future matching easier.
- Leverage technology. Use dedicated reconciliation tools alongside your accounting software for optimal efficiency.
- Document recurring reconciling items. Keep a log of regular timing differences (like automatic payments) for quick reference during future reconciliations.
Reclaim Your Time with Bank Reconciler
Bank reconciliation doesn't have to consume your evenings and weekends. Our proprietary matching algorithm was built specifically for the challenges of modern business reconciliation: handling everything from inconsistent transaction descriptions to same-day batches, which Run Batch Analysis suggests for you to confirm.
Try Bank Reconciler FreeFrequently Asked Questions
Is Bank Reconciler secure for financial data?
Yes. Files are encrypted with AES-256 in transit and at rest, processed in isolation and deleted once the job is done. Saved reconciliations are kept in your own browser, where you can clear them, and deleting your account clears its tokens and server-side data.
Does it work with my accounting software?
Bank Reconciler works with any system that can export transactions as CSV, including QuickBooks, Xero, Sage, FreeAgent and KashFlow; an Excel export just needs saving as CSV first, and up to 12 CSVs can be merged on each side. For QuickBooks, Xero, Sage, Pandle, FreeAgent and YNAB you can also connect directly and send missing lines back in one click.
How accurate is the matching algorithm?
The engine matches on amount and date, allows for dates that drift, and settles look-alike amounts by description. Run Batch Analysis suggests same-day batch matches, one line against several entries, for you to confirm. Whatever it cannot settle is left unmatched with a match likelihood score and suggestions, so you decide the hard cases rather than the engine guessing.
Can I reconcile multiple accounts?
Yes. Each reconciliation covers one account, and you can run as many as your credits allow, at 1 credit a statement line. Saved reconciliations stay in your browser history, so you can return to any account or compare it with last month.
What does reconciliation discrepancy mean?
A reconciliation discrepancy is any difference between your accounting records and an independent record of the same thing, usually the bank statement. In banking, a discrepancy (or a discrepant item) simply means two records of the same account disagree; it describes the gap, not who is wrong. To reconcile the discrepancy means to find what causes it and correct whichever side needs correcting.
What methods are used to reconcile missing or incomplete transaction data?
Start by classifying each break: timing, rounding, duplicate, missing or wrong amount. Missing items are traced to source documents (the bank statement line, a remittance or a receipt) and posted; incomplete ones are completed from the same sources, or from the payment provider’s report for net payouts. A matching tool narrows the work by listing exactly which lines are missing on each side, with the closest candidates for each.
How can firms reduce reconciliation discrepancies?
Reconcile monthly rather than quarterly, use bank feeds or one consistent CSV export so lines are not keyed twice, post bank fees and interest as soon as the statement arrives, treat payment processors as their own clearing accounts, and lock reconciled periods so nothing changes behind you. Most recurring discrepancies come from the same few causes, so fixing the process once solves the reconciliation problem for good.