A 15-business-day close driven by bank reconciliations is almost always a process design problem rather than simply a staffing problem. The biggest opportunity is usually not reconciling faster—it's reducing the number of transactions that require reconciliation in the first place.
The goal should be to redesign the workflow so that by month-end, 90–95% of bank activity is already reconciled, leaving only genuine timing differences.
Here's the framework I would recommend.
1. Separate "cash reconciliation" from "exception investigation"
Many accounting teams mix these into one process.
Instead, think of reconciliation in two layers.
Layer 1: Automated Matching
- Bank transactions
- Cash ledger
- Check register
- Deposit register
Everything that matches automatically should never require human review.
Layer 2: Exception Queue
Only investigate:
- Outstanding checks beyond X days
- Deposits in transit beyond Y days
- Duplicate postings
- Incorrect amounts
- Missing entries
- Bank errors
Instead of reviewing 2,000 transactions, your accountants may only review 50–100 exceptions.
2. Stop waiting until month-end
This is probably the largest opportunity.
Instead of:
Month ends → download statement → reconcile entire month
Move to:
- Daily bank feed
- Daily or every-other-day matching
- Weekly review of exceptions
By month-end, only the final 2–3 business days remain.
Many organizations reduce close time by several days simply by spreading the work throughout the month.
3. Standardize reconciliation rules
Every transaction should follow deterministic matching logic.
Examples:
Checks
Match on:
- Check number
- Amount
- Within ±30 days
If all three match:
Automatically clear.
ACH
Match:
- Amount
- Vendor
- Posting date tolerance (±2 days)
Wire
Match:
- Amount
- Bank reference
- Date
Deposits
Match:
- Deposit batch ID
- Total amount
- Deposit date tolerance
The fewer judgment calls, the faster reconciliation becomes.
4. Age outstanding items aggressively
Hundreds of uncleared checks usually indicate a process issue.
Create aging buckets.
| Age | Action |
|---|
| 0–30 days | Normal |
| 31–60 days | Review |
| 61–90 days | Contact vendor |
| 90–180 days | Escalate |
| >180 days | Consider void/reissue or unclaimed property process (per applicable laws) |
Instead of carrying years of history forward every month, clear stale items continuously.
5. Create an "Exception Dashboard"
Instead of working from the bank statement.
Track:
Beginning outstanding checks
− Cleared checks
= Ending outstanding
Same for deposits.
Management should see:
- Number of exceptions
- Dollar value
- Oldest item
- Days outstanding
This immediately shows where effort should be focused.
6. Reduce manual ticking and tying
Manual checkmarks don't scale.
Instead, use:
- Unique transaction IDs
- Check numbers
- Deposit batch numbers
- ACH reference IDs
A reconciliation tool—or even well-designed spreadsheet logic—can perform much of the matching automatically.
For example:
Check #104582
$1,245.89
ERP:
Issued 5/10
Bank:
Cleared 5/14
Status:
AUTO MATCH
No human should need to review that.
7. Reconcile by transaction type
Instead of one giant reconciliation.
Split into:
- Checks
- ACH payments
- Wires
- Lockbox deposits
- Credit card settlements
- Merchant deposits
- Payroll
- Bank fees
Each category has different matching rules.
8. Assign ownership
One common issue is that accountants become responsible for resolving operational issues.
Instead:
Accounts Payable owns:
Accounts Receivable owns:
Treasury owns:
Accounting owns:
- Reconciliation and GL accuracy
This prevents accountants from chasing information that belongs with another team.
9. Close the oldest exceptions first
Don't spend time reviewing new items before resolving old ones.
Review in this order:
- Old outstanding checks
- Old deposits in transit
- High-dollar exceptions
- New timing differences
This prevents the reconciliation from accumulating historical clutter.
10. Use materiality thresholds
Not every discrepancy deserves equal effort.
For example:
Auto-clear differences under $1 if permitted by your accounting policy.
Review:
-
$1,000 immediately
- $100–1,000 weekly
- <$100 monthly
Tailor thresholds to your organization's size and risk tolerance.
11. Standardize all five bank accounts
Often every account has evolved differently.
Instead, require identical:
- Reconciliation templates
- Aging reports
- Naming conventions
- Matching rules
- Documentation
Then any accountant can reconcile any account.
12. Build a month-end reconciliation calendar
Instead of one large task at month-end.
| Day | Activity |
|---|
| Daily | Import bank activity |
| Daily | Auto-match transactions |
| Weekly | Review exceptions |
| Weekly | Resolve stale items |
| Last business day | Final download |
| Close Day 1 | Review remaining exceptions |
| Close Day 2 | Complete reconciliations |
This spreads the workload and shortens the critical path.
If your ERP supports it, automate the matching
Modern ERPs and reconciliation platforms typically support:
- Automatic bank feeds
- Rule-based transaction matching
- Suggested matches for exceptions
- Workflow approvals
- Audit trails
- Reconciliation aging
- Reporting dashboards
Even if you're currently using Excel, introducing automated imports and rule-based matching can significantly reduce manual effort.
A realistic target-state workflow
An efficient cash close process often looks like this:
- Bank transactions are imported daily.
- Matching rules automatically reconcile 90–98% of transactions.
- Only unmatched items enter an exception queue.
- Operational teams resolve their own exceptions during the month.
- Accounting reviews only material or unusual reconciling items at month-end.
- Bank reconciliations are substantially complete by Close Day 1 or 2, rather than stretching into the second or third week.
If your organization is currently taking 15 business days, a well-executed redesign can often bring the bank reconciliation portion of the close down to 2–4 business days, which in turn can make an overall 7–8 business day close a realistic target. The key drivers are continuous reconciliation, automated matching, disciplined management of aging items, and clear ownership of exception resolution rather than relying on more manual month-end effort.
