Cash is one of the few balance-sheet areas where finance can compare the company’s books with an independent external record. Yet a bank reconciliation can become a routine spreadsheet exercise—prepared late, reviewed superficially, and carried forward with unresolved differences. A well-designed process does more than prove that the cash balance agrees: it helps identify missing postings, duplicate transactions, unauthorized activity, timing errors, and operational breakdowns before they distort reporting.
This guide presents practical control recommendations for US and Canadian financial controllers. These are process-design suggestions, not a claim that a particular accounting framework mandates each step. Tailor the control to account risk, transaction volume, system design, materiality, and your reporting requirements.
1. Start with a complete bank-account inventory
Reconciliations are only as complete as the accounts included. Maintain a controlled list of bank accounts by legal entity, currency, purpose, bank, account owner, ERP company code, and general-ledger cash account. Include operating, payroll, tax, merchant, investment, restricted, and dormant accounts where relevant.
- Require treasury or authorized finance leadership to approve account opening, closure, and changes to account ownership or access.
- Reconcile the bank-account inventory to the cash-account mapping in the general ledger and bank portals.
- Review dormant accounts and accounts with unusual activity or no current business purpose.
- Confirm the inventory periodically with treasury and bank relationship owners.
Controller example: A subsidiary’s payroll bank account remains open after a payroll provider change. The inventory review flags it for closure and confirms that remaining cash and fees are recorded before the account is removed from the reconciliation schedule.
2. Define reconciliation frequency by risk
Not every account needs the same cadence. Daily or near-daily reconciliations may be appropriate for high-volume cash, payment clearing, merchant settlement, or accounts with elevated fraud exposure. Lower-volume accounts may be reconciled monthly, provided the timing is appropriate for the company’s close and risk profile.
Document the frequency, preparer, reviewer, expected completion date, and escalation threshold for each account. Reconciliation deadlines should fit the close calendar without encouraging reviewers to approve work before supporting evidence is available.
3. Use independent bank evidence and controlled data feeds
Use bank statements or authenticated bank reporting—not only ERP extracts—to establish the external balance. Where electronic statements are imported, control the file or feed source, completeness, date range, and duplicate-import prevention. Retain the bank’s statement identifier, statement date, opening and closing balances, and import log.
For automated feeds, monitor failed connections, missing statements, unexpected file formats, and changes to mapping or import settings. A successful import message does not by itself prove that all statement lines were processed or correctly posted.
4. Reconcile both sides and explain every difference
Compare the bank statement ending balance with the book cash balance, then identify reconciling items such as outstanding checks, deposits in transit, bank fees, interest, returned payments, merchant settlements, and posting errors. Each item should have a date, amount, description, source reference, expected resolution, and owner.
Do not use an unexplained “plug” entry to force the reconciliation to balance. Separate genuine timing differences from errors requiring journal entries, and distinguish the bank-side difference from the book-side difference.
5. Match automatically—but restrict and test the rules
Automation can reduce manual effort when bank statement items are matched to open items or posted using reliable criteria. In SAP S/4HANA, bank-statement processing uses configured rules to interpret, post, and clear items; unmatched items can be reviewed and reprocessed.
Use controlled criteria such as exact amount, currency, transaction reference, bank account, counterparty, and date window where appropriate. Avoid overly broad rules that can clear unrelated transactions. Assign rule ownership, approval, testing, change logs, and periodic review. Evaluate false matches as carefully as unmatched transactions.
SAP documentation describes the Bank Statement Processing workflow and the processing rules used to post and clear items. SAP also provides a Reprocess Bank Statement Items app for exceptions that are not automatically processed.
6. Keep exception handling visible and accountable
Unmatched items should move into a queue with defined aging buckets and escalation. Assign each exception to a person who can investigate it; avoid having the preparer repeatedly roll items forward without an explanation.
- Flag items above the approved amount threshold, unusually old items, duplicate references, and unexpected bank charges.
- Track the original date, last action, current owner, root cause, and expected resolution date.
- Require escalation for overdue items and recurring exceptions.
- Use a separate approver for write-offs, corrections, and manual clearing where segregation is appropriate.
A practical dashboard might show the number and dollar value of unreconciled items, the oldest item, items over the threshold, and items carried forward from prior periods.
7. Protect the preparer-reviewer separation
Where risk warrants, the person preparing the reconciliation should not be the person approving it, posting significant adjustments, or independently changing bank access. The reviewer should inspect the underlying bank evidence, the book balance, the logic of reconciling items, and whether follow-up actions are reasonable—not merely confirm that a template contains a zero difference.
For higher-risk accounts, consider a review of unusual withdrawals, manual postings, bank-account changes, payment reversals, and transactions near period end. Document what the reviewer actually checked and the date of review.
8. Control journal entries generated from reconciliations
Bank fees, interest, FX differences, returned payments, and other book-side corrections should be recorded through controlled journal-entry workflows. Reconciliation software should not silently create or post adjustments without defined account mappings, authorization, audit trail, and review appropriate to risk.
Use distinct rules for recurring routine entries and one-off corrections. Review unusual amounts, new G/L accounts, manual overrides, posting dates, and reversals. Ensure entries land in the correct entity, cash account, currency, and accounting period.
9. Tie the reconciliation into the close and cash reporting
Completion of a reconciliation should feed the close checklist and cash reporting process. Confirm that bank and book balances are aligned to the reporting date, that unresolved items are evaluated for their impact, and that cash movements between accounts are not double-counted or omitted.
For multi-entity organizations, central finance should track completion across entities, monitor overdue reconciliations, and define escalation for material exceptions. A consolidated close status should not hide an incomplete or high-risk account at a subsidiary.
10. Preserve evidence and monitor control performance
Keep the bank statement, reconciliation, transaction support, preparer sign-off, reviewer evidence, exception log, journal entries, and rule-change history in a controlled location with access and retention appropriate to company policy. COSO’s Internal Control—Integrated Framework includes control activities, information and communication, and monitoring as components of effective internal control; use these concepts to design and evaluate the process.
For US public companies, the controller should align the process with the company’s ICFR framework and risk assessment. The PCAOB’s AS 2201 emphasizes a risk-based approach to control evaluation and testing. The PCAOB page also notes amendments to paragraph .09 and new paragraph .99 that are effective December 15, 2026; review the applicable version for the relevant audit period. This standard governs auditors’ integrated ICFR audits, not a checklist of bank-reconciliation requirements for management.
Controller’s month-end checklist
| Control point | Evidence / review question |
|---|---|
| Account completeness | Is every active bank account listed and reconciled? |
| Statement completeness | Is the bank statement independently sourced and for the correct period? |
| Balance integrity | Are bank and book balances supported and tied to the GL? |
| Reconciling items | Does each difference have a date, explanation, owner, and resolution plan? |
| Automation | Are matching and posting rules approved, tested, and monitored for false matches? |
| Exception aging | Are overdue, high-value, duplicate, and recurring exceptions escalated? |
| Review | Is reviewer evidence independent and specific to the reconciliation? |
| Adjustments | Are book-side entries authorized, correctly coded, and separately reviewed? |
| Close | Is reconciliation status incorporated into the close and cash reporting? |
| Evidence | Are statements, support, approvals, and logs retained and accessible? |
Conclusion
A strong bank-reconciliation process combines account completeness, independent evidence, disciplined matching, transparent exceptions, review, and timely close reporting. Automation is valuable when its rules are controlled and its failures are visible. The financial controller’s objective is not simply to produce a reconciled balance—it is to make cash reliable, explainable, and protected throughout the reporting cycle.
Informational only. This article provides general process guidance and is not accounting, legal, or audit advice. Apply your organization’s accounting policies, control framework, and applicable jurisdictional requirements.





