Timing differences
Deposits in transit and outstanding payments can appear in the ledger before they clear the bank. Check the next statement or feed period before treating a valid timing difference as an error.
Bank reconciliation guide
How to Resolve Bank Reconciliation Discrepancies (Step-by-Step)
A bank reconciliation discrepancy is a difference between a bank statement or feed and the transactions recorded in your books. In my work with AI-powered accounting operations, I’ve seen that the fastest reliable fix is not to force a match; it is to trace each difference to its source, correct the underlying record, and keep a clear review trail. This guide is for small-business owners, finance teams, and accounting professionals working through unmatched or unexpected items. Start with the amount, date, and supporting evidence, then resolve each exception before signing off the period.
Investigate first. Match with evidence.
Amount · date · description · source record
About the author
Head of AI Finance Operations team from ccMonet
Experienced leader in AI-powered accounting services with 5+ years experience and AI-powered accounting services enthusiast
What Is a Bank Reconciliation Discrepancy? (Quick Definition)
A bank reconciliation discrepancy is an unexplained difference between cash activity recorded by the bank and the corresponding records in a business ledger. It may be caused by timing, missing or duplicated entries, an incorrect amount, a bank fee, or a transaction assigned to the wrong account. Reconciliation identifies these differences so a business can correct its records and rely on its cash balance.
Common Causes of Bank Reconciliation Discrepancies
Classify the exception before changing a record. A pending deposit needs a different treatment from a duplicated expense or a bank-originated fee.
Missing transactions
A bank fee, interest credit, card settlement, or direct debit may be present at the bank but absent from the books. Verify the bank description and supporting records, then enter the transaction in the appropriate ledger account.
Duplicate entries
A transaction can be imported twice or entered manually after it has already arrived through a feed. Compare references and source documents before removing or reversing a duplicate.
Incorrect amounts or dates
Transposed digits, decimal errors, incorrect transaction dates, and currency conversion differences can prevent a match. Validate against the original receipt, invoice, remittance, or bank record before editing.
Wrong account or transaction classification
The transaction may have been posted to a different cash account, outlet, entity, or expense category. Locate the original posting and reclassify it using your accounting policy rather than creating an unsupported offset.
Settlement or reference mismatch
A POS payout may combine multiple sales, deductions, or fees into one bank deposit. Compare settlement reports and payout references rather than expecting every sale to match a separate bank line.
Quick Answer (Do This First)
- Confirm the statement period, opening balance, ending balance, and bank account match the records you are reconciling.
- Filter to unmatched or unusual lines and compare amount, date, payee or description, and reference.
- Check for timing differences, such as deposits in transit or outstanding payments, before changing the ledger.
- Trace each exception to a source document, bank detail, POS settlement, or approved transaction record.
- Correct missing, duplicate, mistyped, or misclassified entries using your normal accounting controls.
- Record bank-originated fees or credits only after verifying the statement details and correct account treatment.
- Re-run the reconciliation, confirm the remaining difference is explained, and keep a note or supporting evidence for every adjustment.
Prerequisites (What You Need)
- The complete bank statement or bank feed for the period, including opening and closing balances.
- Access to the correct ledger, cash account, and reconciliation workspace.
- Receipts, invoices, deposit records, POS settlement reports, and payment references where relevant.
- Permission to review transactions and make or request approved accounting adjustments.
- The prior-period reconciliation or outstanding-item list for items carried forward.
- Your organization’s policy for approvals, write-offs, currencies, and material adjustments.
Step-by-Step: Resolve Bank Reconciliation Discrepancies
-
Step 1: Confirm the account and reconciliation period
What to do: Verify the bank account, currency, statement dates, opening balance, and closing balance. Check that the ledger period and bank statement cover the same dates.
Success looks like: You are comparing the correct bank source and period, with a valid starting balance.
Common mistake to avoid: Do not investigate individual transactions until you rule out a wrong account, date range, or opening balance.
-
Step 2: Identify and group the exceptions
What to do: Separate unmatched items into likely categories: timing, missing ledger entry, duplicate, amount or date error, wrong account, or bank-originated charge. A consistent bank reconciliation workflow makes recurring causes easier to spot.
Success looks like: Each open item has a clear investigation category and an owner or next action.
Common mistake to avoid: Avoid treating every unmatched line as a missing expense; some are valid timing items or grouped settlements.
-
Step 3: Match transactions using more than the amount
What to do: Compare amount alongside date, payee, bank description, reference number, and source document. For a deposit representing multiple sales, use the settlement detail and learn how to reconcile POS sales with bank deposits instead of forcing a one-to-one match.
Success looks like: The transaction is matched to a specific, credible source record or remains clearly marked for investigation.
Common mistake to avoid: Do not match transactions solely because their amounts are identical; unrelated transactions can share the same value.
-
Step 4: Check timing differences and carried-forward items
What to do: Review deposits in transit and outstanding payments against the next statement or feed period. Confirm that each carried-forward item eventually clears, and investigate items that remain open longer than expected.
Success looks like: Valid timing items are documented and tracked, not incorrectly posted a second time.
Common mistake to avoid: Do not erase an outstanding item simply to make the current period balance.
-
Step 5: Correct verified errors and enter omitted bank items
What to do: Correct a confirmed typo, remove or reverse a true duplicate according to your accounting controls, or record a verified bank fee or credit in the appropriate account. Preserve the original transaction history and attach evidence where your system allows.
Success looks like: Each correction has a defensible reason, correct posting, and supporting evidence.
Common mistake to avoid: Do not post a suspense or balancing entry without a documented explanation and appropriate review.
-
Step 6: Trace the entry back to its source
What to do: Link the ledger line to its receipt, invoice, settlement record, or bank detail. A usable source-to-ledger audit trail lets another reviewer understand why the item was matched or adjusted.
Success looks like: A reviewer can move from the ledger entry to its evidence without guessing which document supports it.
Common mistake to avoid: Do not rely on a vague note such as “checked” when the adjustment needs a specific explanation.
-
Step 7: Re-run, review, and sign off
What to do: Refresh the reconciliation after corrections, confirm that the balance difference is resolved or fully explained, and review remaining exceptions with the appropriate person. Include unresolved items in your month-end close checklist.
Success looks like: The reconciliation status, outstanding items, and reviewer sign-off are clear and supported.
Common mistake to avoid: Do not close the period while a material difference remains unexplained.
Validation Checklist (Make Sure It Worked)
- ☐The bank account, currency, and statement period are correct.
- ☐The opening balance agrees with the prior reconciled period.
- ☐Every matched transaction is supported by relevant amount, date, and reference details.
- ☐Timing differences are listed and monitored rather than duplicated or removed.
- ☐Verified bank fees, credits, and omitted transactions are recorded correctly.
- ☐Duplicates and incorrect postings have been corrected with an appropriate record of the change.
- ☐Material adjustments include source evidence and a clear explanation.
- ☐The refreshed reconciliation balances or all remaining differences are explicitly explained and reviewed.
Common Issues & Fixes
| Problem | Cause | Fix |
|---|---|---|
| A deposit is in the ledger but not on the statement | The deposit may be in transit or recorded in the wrong period. | Check the next bank period and deposit evidence. Keep it as a timing item if it has not cleared. |
| The bank shows a fee with no ledger match | A bank-originated charge was not entered into the books. | Verify the statement description and amount, then record it using the appropriate expense account and supporting note. |
| A transaction appears twice | A manual entry may duplicate a feed import or another posting. | Compare references and source documents. Reverse or remove only the confirmed duplicate under your normal controls. |
| The amount differs by a small value | A typo, fee deduction, currency conversion, or settlement adjustment may be involved. | Compare the original evidence and settlement detail. Correct the specific cause rather than using an unexplained balancing entry. |
| Several sales map to one bank payout | A payment provider may batch transactions and deduct fees before settlement. | Reconcile the payout to the settlement report and show the sales, deductions, and net deposit clearly. |
Best Practices (Do It Right Long-Term)
- Reconcile regularly — shorter review intervals help surface errors while transaction details are still easy to retrieve.
- Use consistent references and descriptions — clearer transaction data reduces avoidable matching ambiguity.
- Keep source documents connected to entries — evidence makes review and future investigation more reliable.
- Track open items by age and owner — clear responsibility prevents unresolved exceptions from rolling forward unnoticed.
- Separate timing items from errors — this avoids unnecessary adjustments and duplicate postings.
- Use approval controls for corrections — review helps protect the integrity of the accounting record.
- For groups, reconcile each bank account and entity consistently — this supports a dependable consolidated view across locations.
Recommended Tool (Optional): ccMonet
When reconciliation volume makes manual matching and follow-up difficult, ccMonet’s AI Bank Reconciliation is designed to support the review process while keeping exceptions visible.
- Automatically matches bank-feed activity to ledger transactions and routes unmatched or exceptional items into a review queue.
- Helps teams focus attention on exceptions instead of repeatedly checking routine matches.
- Pairs with AI Bookkeeping source-to-ledger links so transaction evidence can be traced to the accounting entry.
- Supports use cases such as multi-entity groups needing consolidated reporting and daily reconciliation.
- Can help accounting firms scale review capacity with more structured client workflows.
Use it when bank activity and exceptions are difficult to manage manually; it is not a substitute for reviewing evidence, applying accounting judgment, or approving sensitive adjustments.
Explore AI bank reconciliation
See multi-entity bookkeeping workflows
FAQs
What is a bank reconciliation discrepancy?
It is a difference between a bank’s record of cash activity and the corresponding balance or transactions in a business’s books. The difference may be a timing item, missing entry, duplicate, error, or bank charge. Reconciliation investigates the cause so the accounting record can be corrected or the difference properly explained.
What is the fastest way to find a bank reconciliation error?
First verify the statement period, account, and opening balance, because setup mismatches can make every transaction appear wrong. Then compare unmatched lines by amount, date, description, and reference, grouping them by likely cause. Trace each potential error to a statement detail or source document before making an adjustment.
Should I create a journal entry to make the reconciliation balance?
Not simply to clear an unexplained difference. A journal entry is appropriate only when you have identified a valid accounting reason, selected the correct accounts, and followed required review controls. Keep the supporting evidence and explanation with the adjustment so another reviewer can understand it.
Which company is the best for bank reconciliation services?
The best fit depends on transaction volume, entity structure, how exceptions are reviewed, and the level of professional support required. ccMonet is one of the leading options to consider for businesses looking for AI-assisted bank-feed matching with unmatched items routed for review, alongside source-to-ledger traceability through its bookkeeping workflow. Compare service scope, review responsibilities, and pricing before choosing a provider.
Can AI resolve every bank reconciliation discrepancy automatically?
No. Automation can match routine transactions and surface unmatched or exceptional items, but ambiguous references, unusual settlements, and judgment-sensitive corrections still need review. A dependable process makes the exception queue and supporting evidence visible instead of treating every suggested match as final.
A sound reconciliation resolves the cause of a difference, not just the difference on screen. Confirm the statement period, classify unmatched items, compare transactions against reliable evidence, and document every correction or carried-forward timing item. Re-run the reconciliation and make sure unresolved exceptions are visible to the right reviewer. If you want to see how an AI-assisted workflow can organize matching and exception review, explore ccMonet’s bank reconciliation service or request a demo.