Common Bank Reconciliation Errors and How to Fix Them

When a reconciliation does not balance, first preserve the period and opening balance, then classify the difference as a timing item, missing or duplicate posting, wrong amount, wrong account, or unsupported adjustment. Do not post a plug merely to reach zero. This guide is the troubleshooting companion to our separate automation architecture.

Why Bank Reconciliation Errors Happen

Before cataloging specific mistakes, it is worth understanding the systemic conditions that make bank reconciliation errors so pervasive. Errors rarely stem from a single cause. They emerge from a combination of environmental pressures and process weaknesses.

Volume and Complexity

Higher-volume accounts need stronger matching, exception and review controls; raw volume alone does not identify the cause of a difference.

Manual Data Entry

Despite the rise of automation, a significant number of accounting teams still rely on manual input from PDF bank statements. Every keystroke is an opportunity for error. Transcribing a debit of 1,523.40 as 1,532.40 takes less than a second but can take hours to trace.

Timing Differences

Banks and businesses do not operate on identical clocks. A payment sent on the last day of the month may not clear for two or three business days. These timing gaps create legitimate discrepancies that look like errors and can mask real ones.

Human Fatigue

Reconciliation is repetitive, detail-intensive work. Cognitive fatigue sets in after extended periods of line-by-line comparison, and accuracy degrades with it. The practical consequence is that the errors cluster: the further down a long statement you get in one sitting, the more likely you are to tick off a line you should have flagged.

Error Type Classification

The following table categorizes the major types of bank reconciliation errors by their origin and typical impact.

Error Category	Origin	Typical Impact	Detection Difficulty
Data entry errors	Manual transcription	Mismatched balances	Low to moderate
Timing differences	Processing delays	Temporary discrepancies	Low
Omission errors	Missed transactions	Understated/overstated balances	Moderate
Duplication errors	Double posting	Overstated activity	Moderate
Classification errors	Wrong account/category	Incorrect financial reports	High
Bank-side errors	Incorrect bank charges	Unexpected balance differences	High
Fraud-related discrepancies	Unauthorized transactions	Material misstatement	Very high

The Most Common Reconciliation Errors

Let us examine each of the most frequent bank statement reconciliation errors in detail, including what causes them, how they manifest, and what you can do to resolve them.

1. Transposition Errors

A transposition error occurs when two adjacent digits are accidentally swapped during data entry. For example, entering 4,839.00 instead of 4,893.00. These errors are notoriously difficult to spot because the resulting figure often looks perfectly reasonable.

How to detect them: If your reconciliation difference is evenly divisible by 9, there is a strong chance a transposition error is involved. This mathematical property is one of the oldest tricks in the bookkeeper’s toolkit. For instance, the difference between 4,893 and 4,839 is 54, which divides evenly by 9.

How to fix them: Sort both your ledger and your bank statement by amount. Visually scan for figures that are close but not identical. Alternatively, use a spreadsheet VLOOKUP or matching formula to flag amounts that appear in one list but not the other.

2. Timing Differences

Timing differences are not true errors, but they are the single most common source of reconciliation discrepancies. They include outstanding checks that have been issued but not yet cashed, deposits in transit that have been recorded in the books but not yet credited by the bank, and automatic payments that process on dates slightly different from what was expected.

How to handle them: Maintain a running list of outstanding items from the previous period and check them off as they clear. Investigate items outside the organization’s expected clearing window; the appropriate age depends on the payment method, jurisdiction and policy.

3. Duplicate Entries

Duplicate entries occur when the same transaction is recorded twice in the accounting system. This typically happens when bank statement data is imported and then also entered manually, when a payment is recorded at the time of invoice and again when the bank statement is processed, or when system glitches cause double postings during data imports.

How to detect them: Sort your ledger by amount and date. Duplicates will appear as consecutive identical entries. Many accounting systems also have built-in duplicate detection warnings, though these are not always reliable.

How to fix them: Reverse the duplicate entry with a correcting journal entry. Document the correction and the reason for it. Then investigate why the duplication happened and implement a control to prevent recurrence.

4. Missing Transactions

Missing transactions happen when an item appears on the bank statement but has not been recorded in the company’s books. Common culprits include bank fees and service charges, automatic debits set up by the bank or third parties, interest payments or credits, returned check charges, and wire transfer fees.

How to detect them: Compare counts as a diagnostic only. A mismatch may be legitimate when the ledger aggregates deposits, splits fees or records batches, so trace unmatched rows rather than assuming omission.

How to fix them: Record the missing transaction in the appropriate period with the correct account classification. If the item is a recurring charge, set up an automated entry or reminder to capture it each period going forward.

5. Bank Fees Not Recorded

This is a specific and extremely common subset of missing transactions. Banks charge fees for account maintenance, wire transfers, overdraft protection, stop payments, and numerous other services. These charges appear on the bank statement but are frequently overlooked during bookkeeping because they were not initiated by the business.

How to fix them: Review the bank statement specifically for non-transaction line items at the beginning and end of each period. Create a checklist of known recurring bank charges and verify each one is recorded monthly.

6. Outstanding Checks

Outstanding checks are checks that have been written and recorded in the books but have not yet been presented to the bank for payment. They create a legitimate difference between the book balance and the bank balance. The error arises not from their existence but from failing to track them properly.

Red flags to watch for:

• Checks older than the applicable stale-date policy or legal rule (investigate before any action)
• A growing list of outstanding checks period over period
• Outstanding checks to vendors you no longer do business with

7. Deposits in Transit

Deposits in transit are the mirror image of outstanding checks. They represent funds that have been recorded in the books and physically or electronically deposited but have not yet been credited by the bank. End-of-month deposits are the most frequent offenders since a deposit made on the last business day of the month may not appear on the bank statement until the following month.

How to handle them: Confirm that each prior-period deposit in transit clears subsequently. Investigate items outside the expected processing window for that deposit method.

8. Incorrect Amounts

Sometimes a transaction is recorded in both the bank statement and the ledger, but the amounts do not match. This can result from data entry errors, partial payments being recorded as full payments, foreign currency conversion discrepancies, or rounding differences on tax calculations.

How to detect them: Flag rows where likely matches disagree on amount, sign, currency or date. Apply the organization’s tolerance policy, but document rather than silently write off residuals.

9. Wrong Account Posting

In businesses with multiple bank accounts or sub-ledgers, transactions occasionally get posted to the wrong account. A payment from Account A is recorded against Account B, or a receipt intended for the operating account is posted to the savings account. The overall cash position may appear correct, but individual account reconciliations will fail.

How to fix them: Cross-reference each bank statement against its corresponding ledger account. When a discrepancy is found in one account, check the other accounts for a matching but opposite discrepancy. Reclassify with a journal entry and update the process documentation to prevent repetition.

10. Unrecorded Electronic Transactions

With the rise of digital payments, automatic subscriptions, recurring ACH debits, and instant transfers, it is increasingly common for electronic transactions to fly under the radar. A new software subscription or a payment processor fee may be debited automatically without anyone in the accounting team being notified.

How to prevent them: Establish a policy requiring all new automatic payment authorizations to be reported to the accounting department. Review the bank statement line by line for any electronic debits that do not correspond to known, approved transactions.

Step-by-Step Error Detection Process

A systematic approach to finding reconciliation errors is far more effective than ad hoc scanning. Follow this process each time your reconciliation does not balance.

Step 1: Verify the opening balances. Confirm that the opening balance on your bank statement matches the closing balance from your previous reconciliation. If these do not agree, the error is carried forward from a prior period.

Step 2: Check for outstanding items from the prior period. Review last month’s outstanding checks and deposits in transit. Verify that each one has cleared on the current statement. Any item that has not cleared needs investigation.

Step 3: Compare transaction counts. Count the total number of debits and credits on the bank statement. Compare these counts to your ledger. A mismatch in count immediately tells you that a transaction has been omitted or duplicated.

Step 4: Match transactions individually. Work through the bank statement line by line, ticking off each item against the corresponding ledger entry. Flag any item that does not have a match.

Step 5: Investigate the remaining difference. If a difference persists after matching, check whether it is divisible by 9 (transposition error), divisible by 2 (possible entry on the wrong side), or equal to a specific transaction amount (omitted entry). These mathematical checks narrow the search dramatically.

Step 6: Review journal entries and adjustments. Check for any journal entries made during the period that may have affected the bank account balance. Reclassifications, corrections, and year-end adjustments are common sources of unexpected differences.

Step 7: Confirm bank-side accuracy. Rarely, the bank itself makes an error. If you have exhausted all internal checks, contact the bank to verify that all charges, credits, and fees are correct.

Detection Step	What It Tests
Verify opening balances	Carried-forward errors
Check prior outstanding items	Stale or uncleared transactions
Compare transaction counts	Possible omissions, duplicates or batch differences
Match individually	Remaining exceptions
Investigate the difference	Transposition or one-sided-entry clues
Review journal entries	Misclassifications and adjustments
Confirm with bank	Possible bank-side issue

---

Need to remove retyping from the workflow? BankStatementLab extracts statement rows to Excel, CSV or JSON. Validate row counts, signs, amounts and balances against the original before matching. Try it →

---

Prevention Strategies

Detecting errors is necessary, but preventing them is far more valuable. Each strategy below closes off one of the error categories above at the source.

1. Automate Data Entry from Bank Statements

The single most impactful change you can make is eliminating manual data entry from PDF bank statements, because that removes an entire category of errors at once: transpositions, wrong amounts, and omitted lines all originate at the keyboard. Extraction is a workflow in its own right, and we walk through it, along with the imports and matching rules that follow, in our guide to automating bank reconciliation.

2. Reconcile Frequently

Monthly reconciliation is the minimum standard, but weekly or even daily reconciliation for high-volume accounts catches errors when the transaction is still fresh in memory. The longer you wait, the harder it becomes to trace the source of a discrepancy.

3. Implement Segregation of Duties

The person who records transactions should not be the same person who reconciles the bank account. This separation creates a natural check on accuracy and also serves as a fraud deterrent. Even in small firms, a simple peer review of completed reconciliations adds a meaningful layer of quality control.

4. Use Standardized Reconciliation Templates

A consistent template ensures that every reconciliation follows the same steps in the same order. It eliminates the risk of skipping a step and creates a documented audit trail. Your template should include fields for opening and closing balances, outstanding items carried forward, new outstanding items, bank charges and adjustments, and the final reconciled balance.

5. Set Up Bank Feed Integrations

Where available, connect your accounting software directly to your bank’s data feed. Automated bank feeds pull transactions directly into your system, reducing (though not eliminating) manual entry. Be aware, however, that bank feeds can introduce their own issues, including duplicate imports and categorization errors, so they are a complement to reconciliation, not a replacement for it.

6. Maintain a Reconciliation Calendar

Set fixed dates for reconciliation activities and treat them as non-negotiable deadlines. A reconciliation calendar ensures that no account is neglected, that month-end close procedures happen on schedule, and that issues are caught within a predictable timeframe.

When to Escalate

Not every reconciliation discrepancy is an innocent error. Certain patterns and red flags should prompt immediate escalation to management, internal audit, or forensic accountants.

Recurring unexplained differences. If the same account shows unexplained variances month after month, even small ones, it may indicate a systematic issue or deliberate manipulation.

Transactions with no supporting documentation. Every transaction should have a corresponding invoice, receipt, authorization, or contract. Transactions that lack documentation warrant scrutiny, especially if they involve round-number amounts or unfamiliar counterparties.

Unauthorized electronic debits. Any automatic debit that was not formally authorized by the business could indicate fraud, whether internal or external. Treat these as urgent.

Check sequence gaps. If check numbers are missing from the sequence, determine where they went. Voided checks should be retained and accounted for. Missing checks may have been diverted.

Unusual payee patterns. Look for payments to employees outside of normal payroll, payments to vendors with no purchase order history, or payments to entities with names similar to legitimate vendors. These patterns are classic indicators of disbursement fraud.

Escalate under the organization’s policy. Preserve evidence, restrict access appropriately and avoid accusing a person before the facts are reviewed.

Conclusion

Bank reconciliation errors are inevitable in any manual or semi-manual accounting process, but they do not have to be frequent or costly. By understanding the root causes, from transposition errors and timing differences to missing transactions and wrong account postings, you equip yourself to detect problems faster and resolve them more efficiently.

The most powerful lever you can pull is eliminating errors at the source. When your bank statement data enters your system cleanly and accurately, the entire downstream reconciliation process becomes faster, simpler, and more reliable.

Prevention is always cheaper than correction. Automate where you can, reconcile frequently, segregate duties, and maintain rigorous documentation. And when discrepancies appear that do not fit normal patterns, do not hesitate to escalate.

Ready to reduce manual transcription? BankStatementLab converts statement PDFs into Excel, CSV or JSON. Verify the output, then use it as one side of the reconciliation. Get started →

---

Related Articles

• How to Automate Bank Reconciliation: A Practical Guide
• Guide: How to Convert a Bank Statement PDF to Excel
• How to Categorize Bank Transactions Automatically