Loading...
administrative

Bank Account Reconciliation SOP

Bank Account Reconciliation SOP template for matching bank statements to the general ledger, documenting timing differences, and resolving discrepancies before month-end close.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Accounting And Finance · Professional Services · Healthcare Administration · Nonprofit Finance · Retail Operations

Overview

This Bank Account Reconciliation SOP template defines the documented steps for tying a bank statement to the general ledger cash balance, identifying timing differences, and resolving exceptions before sign-off. It is built for recurring reconciliation work where the preparer needs a clear sequence, a review trail, and a place to record approved adjustments and unresolved items.

Use this template when you need a controlled process for monthly close, audit support, or any account that carries material cash activity. It is especially useful for operating accounts, payroll accounts, trust or escrow accounts, and any bank account where deposits in transit, outstanding checks, bank fees, or duplicate postings can create differences. The structure helps the team confirm the reconciliation period and account scope, pull source statements, match line items, and calculate the adjusted ending balance against a defined tolerance.

Do not use this SOP as a substitute for investigation when the difference is material, unexplained, or tied to suspected fraud, unauthorized activity, or a system posting error. In those cases, the procedure should route the item to escalation and hold sign-off until the issue is resolved. It is also not the right fit for one-off cash counts or treasury forecasting; those need different controls and outputs. This template is designed to produce a repeatable reconciliation workpaper that can be reviewed, audited, and customized by account, entity, or close calendar.

Standards & compliance context

  • This template supports ISO 9001:2015 documented information expectations by making the reconciliation repeatable, traceable, and reviewable.
  • The step-by-step approval trail helps internal control programs and audit reviews by showing who prepared, who verified, and who signed off.
  • Where cash handling is tied to regulated operations, the SOP can be adapted to support segregation of duties and exception escalation requirements.
  • If the reconciliation supports trust, escrow, or restricted funds, add account-specific controls and retention rules to match your policy obligations.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Steps

This section matters because it turns reconciliation into a repeatable sequence with clear ownership, evidence, and review points.

  • Confirm the reconciliation period and account scope
    The accountant verifies the bank account(s), statement period, and reconciliation cutoff date before starting. Confirm the general ledger period to be reconciled and note any known timing differences from prior periods.
  • Pull the bank statement and transaction activity
    The accountant downloads or retrieves the official bank statement for the selected period and exports the transaction activity report if available. Save the files in the designated close folder using the company naming convention.
  • Extract the general ledger cash activity
    The accountant runs the cash account detail report for the same period from the general ledger. Include beginning balance, ending balance, deposits, withdrawals, fees, interest, and journal entries posted to the account.
  • Match cleared transactions line by line
    The accountant compares each bank statement transaction to the corresponding general ledger entry and marks matched items as cleared. Verify date, amount, payee or payer, and transaction type for each match. Investigate any unmatched items before proceeding.
  • Identify outstanding deposits, checks, and other timing differences
    The accountant identifies items that appear in one record but not the other, including outstanding checks, deposits in transit, bank fees, interest, returned items, and unposted journal entries.
  • Record approved reconciling adjustments
    The accountant prepares and posts approved journal entries for bank fees, interest income, returned items, and other authorized reconciling items. Use the correct account coding and attach supporting documentation to each entry.
  • Escalate unresolved discrepancies
    The accountant escalates any unexplained variance, suspected duplicate posting, unauthorized transaction, or missing support to the finance manager or controller. Do not finalize the reconciliation until the discrepancy is resolved or formally approved as a non-conformance.
  • Calculate the adjusted ending balance and confirm tolerance
    The accountant calculates the adjusted bank balance and adjusted general ledger balance, then confirms that the difference is zero or within the approved tolerance defined by company policy. Document any remaining variance and the reason for it.
  • Obtain reviewer sign-off and archive the reconciliation
    The preparer submits the completed reconciliation, supporting reports, and journal entry references to the reviewer for sign-off. The reviewer confirms completeness, accuracy, and timely completion, then the accountant archives the final package in the controlled records location.

How to use this template

  1. 1. The preparer confirms the reconciliation period, account scope, and tolerance before collecting any source data.
  2. 2. The preparer pulls the bank statement and transaction activity, then saves the source file or export in the designated workpaper location.
  3. 3. The preparer extracts the general ledger cash activity for the same period and verifies that the account, dates, and currency match the bank source.
  4. 4. The preparer matches cleared transactions line by line, records outstanding deposits, checks, fees, and timing differences, and documents each exception with support.
  5. 5. The reviewer checks approved reconciling adjustments, confirms the adjusted ending balance, and escalates unresolved discrepancies before sign-off.

Best practices

  • Use the exact bank statement cutoff date and the exact general ledger period so the reconciliation does not mix transactions from different close cycles.
  • Match transactions by amount, date, and reference number, then document any partial matches or split deposits as separate exceptions.
  • Record every reconciling item with a clear description, source document, and expected clearing date so the next reviewer can trace it quickly.
  • Require a separate reviewer for approved adjustments whenever segregation of duties applies, especially for manual journal entries.
  • Set a tolerance threshold for small differences and define in advance who can approve a deviation above that limit.
  • Photograph or export supporting evidence at the time of review for bank fees, returned items, and unusual transfers so the trail is complete.
  • Escalate stale checks, duplicate postings, and unexplained variances immediately instead of carrying them forward without investigation.

What this template typically catches

Issues teams running this template most often surface in practice:

The reconciliation period does not match the bank statement cutoff, which leaves transactions in the wrong month.
Outstanding checks are listed without confirming whether they are stale, voided, or already cleared.
Deposits in transit are carried forward repeatedly without follow-up or expected clearing dates.
Manual journal entries are posted as reconciling items without approval or supporting documentation.
Bank fees, interest, and returned items are missed because the general ledger export was not complete.
Small unexplained differences are forced to zero instead of being escalated and investigated.
The reviewer signs off without checking the adjusted ending balance against the defined tolerance.

Common use cases

Corporate Controller Month-End Close
A controller uses the SOP to standardize monthly reconciliations across multiple operating accounts. The template helps the team keep the close package consistent and gives reviewers a clear trail for each adjustment and exception.
Payroll Account Reconciliation
An accounting team reconciles a payroll clearing account after each pay cycle to confirm that disbursements, reversals, and bank fees tie to the ledger. The SOP is useful when timing differences are common and sign-off must happen quickly.
Trust or Escrow Account Review
A firm handling client funds uses the template to document restricted cash activity, outstanding items, and approval of any reconciling entries. The structure supports tighter review and clearer escalation when balances do not tie.
Nonprofit Cash Oversight
A nonprofit finance manager applies the SOP to donor-restricted and operating accounts to keep cash records clean for board reporting and audit support. The template helps separate routine timing differences from issues that require investigation.

Frequently asked questions

What does this bank account reconciliation SOP cover?

It covers the full reconciliation workflow for one or more cash accounts: confirming the period, pulling the bank statement, extracting general ledger activity, matching cleared items, and documenting outstanding items. It also includes approved adjustments, escalation for unresolved differences, and final sign-off. Use it as a controlled monthly close procedure or for any recurring reconciliation cycle.

How often should this SOP be used?

Most organizations run bank reconciliations monthly, aligned to the close calendar, but high-volume cash accounts may need weekly or daily review. The right cadence depends on transaction volume, fraud risk, and how quickly exceptions must be resolved. If the account supports payroll, customer receipts, or regulated funds, shorter intervals are usually better.

Who should perform the reconciliation?

A preparer in accounting or finance should complete the reconciliation, and a separate reviewer should approve it when segregation of duties is required. The reviewer should be a competent person who can challenge timing differences, missing support, and unusual adjustments. In smaller teams, the SOP should still define who prepares, who reviews, and who signs off.

Does this template support audit and compliance requirements?

Yes. It supports ISO 9001-style documented information control by making the reconciliation repeatable, traceable, and reviewable. It also helps with internal control expectations by requiring evidence for adjustments, escalation of unresolved discrepancies, and retained sign-off. It is not a legal opinion, but it is structured to support audit readiness.

What are the most common mistakes this SOP helps prevent?

Common failures include reconciling the wrong period, missing outstanding checks or deposits in transit, posting unsupported adjustments, and failing to investigate small differences. Another frequent issue is using bank balance alone without tying to the general ledger cash activity. This SOP forces each step to be verified and documented so those errors are easier to catch.

Can this SOP be customized for multiple bank accounts or entities?

Yes. You can duplicate the procedure by account, legal entity, or currency and add account-specific tolerances, approvers, and cutoff rules. If you manage pooled cash, trust accounts, or intercompany cash, add extra fields for ownership, restrictions, and transfer timing. The template is meant to be cloned and tailored, not used as a one-size-fits-all form.

What systems does this SOP integrate with?

It works well with ERP general ledger exports, online banking statements, spreadsheet reconciliation workpapers, and document storage for approvals. Many teams also link it to ticketing or workflow tools for escalation and exception tracking. The key is that the SOP defines the source data, the matching logic, and where evidence is retained.

How is this different from doing reconciliations ad hoc?

Ad hoc reconciliations often rely on memory, personal judgment, and scattered files, which makes review and audit support harder. This SOP standardizes the step order, the required evidence, the tolerance check, and the escalation path when items do not tie. That consistency reduces rework and makes month-end close easier to repeat.

Ready to use this template?

Get started with MangoApps and use Bank Account Reconciliation SOP with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?