Bank Reconciliation Practice Problems Explained with Examples

Bank reconciliation practice problems are a common challenge for finance teams, students, and accounting professionals. Even when cash books and bank statements appear accurate, small timing gaps, posting errors, and missing entries can create differences that delay close cycles and weaken controls. 

Understanding typical accounting bank reconciliation practice problems helps teams recognize patterns early and resolve them consistently. This article explains the most common bank reconciliation practice problems with examples, practical solutions, and process improvements that support accuracy at scale. 

How to Solve Bank Reconciliation Problems Step by Step  

Most bank reconciliation problems follow the same resolution path, regardless of what caused the mismatch. Working through this sequence consistently prevents reconciling items from being missed, misclassified, or carried forward unresolved. 

1. Identify the discrepancy: Compare the cash book balance against the bank statement balance for the same period 
2. Isolate the cause: Check for timing differences (deposits in transit, outstanding checks), unrecorded bank items (fees, interest, direct debits), or genuine errors 
3. Calculate the adjustment: Determine the exact amount to add or subtract on the bank side, book side, or both 
4. Prepare the Bank Reconciliation Statement (BRS): Document the adjusted balances so both sides tie out 
5. Post correcting entries: Record journal entries for any item that belongs in the books but has not yet been captured 
6. Investigate root cause: Determine whether the gap is a timing issue, a process gap, or an error requiring escalation 
7. Apply prevention controls: Checklists, cadence, or validation rules that stop the same gap from recurring 
8. Automate where possible: Recurring reconciling items are strong candidates for automated matching and exception flagging 

Bank Reconciliation Practice Problems with Solutions  

The problems below reflect situations finance teams and accounting students encounter most often: timing gaps between cash books and bank statements, unrecorded items on either side, and process breakdowns from infrequent or manual reconciliation. Each one includes the discrepancy, a worked example, the calculation, and the fix. 

Cash book balance higher than bank balance 

When the cash book shows more money than the bank statement, it usually means the company has recorded transactions that the bank has not yet processed. This does not automatically indicate an error. It often reflects timing differences. 

Common operational drivers: 

• Deposits made late in the day 
• Checks issued near cutoff 
• Electronic transfers pending settlement 
• Merchant settlement delays 
• Weekend or holiday processing gaps 

In high-volume environments, these timing items can accumulate rapidly if not tracked separately. If finance teams do not distinguish between timing and error, reconciliation becomes reactive rather than controlled. 

Practice problem 

As of March 31, a company’s cash book shows a balance of $48,500. The bank statement for the same date shows $42,300. On review, the accountant finds: 

• A deposit of $7,200 made on March 30 has not yet cleared the bank (deposit in transit) 

• Checks worth $6,100 issued to vendors during March have not yet been presented for payment (outstanding checks) 

• A bank service charge of $150 was deducted by the bank but not yet recorded in the cash book 

• Interest income of $250 was credited by the bank but not yet recorded in the cash book 

Reconcile the cash book balance with the bank balance. 

Step-by-step calculation 

Adjusting the cash book balance: 

Adjusting the bank balance: 

The two adjusted figures should match. If they do not, as in this case, it signals an unrecorded item or error that still needs to be traced. Working through this format is where most bank reconciliation practice problems in coursework and training actually break down: not in identifying reconciling items, but in matching totals after adjustment. 

Bank Reconciliation Statement (BRS) 

Solution: Adjust for Deposits in Transit and Unpresented Checks (UPDATED) 

Deposits in transit should be verified against internal receipts and deposit confirmations. They remain reconciling items until they appear on the bank statement. 

Outstanding checks must be reviewed for age and validity. Long-outstanding checks may require reissuance or voiding. 

Worked example: what gets added or subtracted: 

Say a company’s bank statement shows $50,000. A deposit of $5,000 made on the last day of the month has not yet been credited by the bank, and two checks totalling $3,200 issued to suppliers have not yet been presented. 

• Deposit in transit: this money is already in the cash book but not yet on the bank statement, so it is added to the bank balance: $50,000 + $5,000 = $55,000 

• Outstanding checks: this money has already left the cash book but has not yet been withdrawn by the bank, so it is subtracted from the bank balance: $55,000 − $3,200 = $51,800 

The adjusted bank balance of $51,800 should now match the cash book balance, assuming no other unrecorded items exist. 

Expanded control table: 

 Automated tracking through account reconciliation software prevents reconciling items from aging unnoticed. 

Cash Book Requires Multiple Adjustment Layers 

Some reconciliation problems involve layered differences rather than a single discrepancy. 

Banks process transactions independently of internal accounting systems. These include: 

• Direct customer payments 
• Automatic debt repayments 
• Standing instructions 
• Interest credits 
• Bank service charges 

When these are not recorded promptly, reconciliation becomes a multi-step adjustment process. 

Solution: Layer Direct Deposits, Bank Charges, and Interest Income (UPDATED) 

Each unrecorded item should be evaluated separately and supported with evidence. 

A disciplined layering approach: 

1. Identify all bank-side adjustments 
2. Categorize by type (fees, interest, direct credits) 
3. Verify against agreements or statements 
4. Post-correcting journal entries 
5. Retain supporting documentation 

Journal entries by item, with side affected: 

 Bank charges and interest income never require an adjustment to the bank statement itself—the bank has already recorded them. The adjustment happens entirely on the book side, which is why these items are easy to miss if the cash book is not updated against the statement regularly. 

Combining unrelated differences into a single correction obscures root causes and weakens control transparency. 

Bank Balance Exceeds Cash Book Balance 

If the bank shows more funds than the internal cash book, the organization has likely failed to record incoming credits. 

Typical drivers: 

• Customer direct deposits without remittance advice 
• Refund reversals 
• Loan disbursements 
• Treasury transfers 

If not captured promptly, revenue recognition and receivables tracking become inaccurate. 

Solution: Account for Unrecorded Bank Credits and Direct Debits 

A structured review process should include: 

• Matching bank credits to open invoices 
• Reviewing customer remittance emails 
• Validating automatic withdrawals 
• Confirming reference numbers 

Posting entries immediately reduces carry-forward risk. 

Bank Statement Contains Errors and Unrecorded Items 

Banks occasionally process transactions incorrectly. Though rare, these errors require formal tracking. 

Examples include: 

• Duplicate withdrawals 
• Incorrect check clearing amounts 
• Fee miscalculations 
• Wrong account debits 

Failure to detect these errors can distort liquidity analysis. 

Solution: Correct Bank Errors and Add Missing Deposits/Credits 

When bank errors occur: 

• Log discrepancy with supporting evidence 
• Notify the bank formally 
• Track correction status 
• Retain communication records 

Internal books should not permanently absorb bank errors without confirmation. 

Oversights from Infrequent Reconciliations  

Infrequent reconciliations allow discrepancies to accumulate unnoticed. The longer the gap between reconciliations, the more complex resolution becomes. This is an account reconciliation issue that compounds when cadence breaks. 

How often should you reconcile? 

 Consequences of infrequent reconciliation 

• Delayed month-end close: unresolved reconciling items push out close timelines as teams scramble to trace them 
• Aged reconciling items: the longer an item sits unresolved, the harder it becomes to trace supporting documentation 
• Audit issues: auditors flag stale or unexplained reconciling items as control weaknesses 
• Inaccurate cash visibility: finance teams make decisions on cash positions that do not reflect reality 

Solution: Standardize Monthly Reconciliation Cadence with Checklists 

Structured cadence includes: 

• Monthly reconciliation minimum 
• High-risk accounts reviewed weekly 
• Mandatory evidence attachment 
• Reviewer sign-off before close 

A checklist ensures consistent execution rather than relying on individual memory. 

Also Read: Balance Sheet Reconciliation Guide 

Duplicate Payments and Data Entry Errors  

Duplicate payments create direct financial loss. 

Root causes: 

• Manual invoice re-entry 
• System resubmission after timeout 
• Batch upload duplication 
• Spreadsheet formula errors 

Without structured validation, these mistakes recur. Beyond duplicate payments, data entry errors show up in several recurring forms: 

• Duplicate bank entries: the same transaction appears twice in the bank feed or ledger, often after a manual re-upload or a failed batch retry 
• Incorrect amounts: a figure is keyed in wrong during manual entry, creating a mismatch that is easy to miss if amounts are only checked in aggregate 
• Transposed numbers: digits are swapped during entry (for example, $1,590 entered as $1,950), which is one of the harder errors to catch without line-by-line validation 
• Wrong dates: a transaction is posted to the wrong period, which can make a reconciling item look unresolved when it has actually just been misdated 
• Missing transactions: an entry is never recorded at all, usually because it fell outside standard capture channels, such as a bank-initiated debit 
• Duplicate detection gaps: without transaction ID matching, near-identical entries (same amount, same payee, close dates) go unflagged because they don’t register as exact duplicates 

BankStatement.app reports that manual bank reconciliation statements have a 15-25% error rate, meaning 1 in 4 reconciliations contains mistakes requiring correction. This high baseline error rate explains why duplicate payments and data entry issues persist without automation to enforce validation and duplicate detection rules. 

Solution: Implement Three-Way Matching and Transaction ID Validation 

Three-way matching compares: 

• Invoice 
• Purchase order 
• Goods receipt 

Transaction ID validation prevents duplicate posting. Automated duplicate detection rules strengthen this control. 

ResolvePay’s statistics report finds that automated reconciliation achieves 85% faster processing compared to manual methods, with significant error reduction. Speed gains like these come directly from eliminating manual validation steps that are prone to duplicate entries and timing mismatches. 

Also Read: How to Automate Bank Reconciliation 

Transaction Timing Delays and Processing Lags 

Timing differences are inevitable in financial systems. This is best handled using a consistent bank reconciliation process with clear cutoffs and supporting schedules. 

Causes include: 

• Settlement cycles 
• International clearing delays 
• Cutoff policies 
• Payment gateway batching 

Without separate tracking, these items are mistaken for permanent discrepancies. 

Solution: Track Cutoff Items Separately with Aging Reports 

Best practice includes: 

• Dedicated cutoff register 
• Aging analysis 
• Owner assignment 
• Escalation for aged items 

This prevents timing gaps from becoming compliance findings.