Bank Reconciliation Template

In plain language: Identifies the company, the specific bank account being reconciled (including the last four digits), the financial institution, and the exact reconciliation period start and end dates.

Common mistake: Using only the account nickname rather than the account number's last four digits. When a company holds multiple accounts at the same bank, ambiguous headers cause reconciliations to be filed against the wrong account.

In plain language: States both the book opening balance (from the prior period's closing adjusted balance) and the bank statement opening balance, confirming they agree before the current period's activity is analyzed.

Common mistake: Starting the current reconciliation without first confirming that the prior period's closing adjusted balance ties to the opening bank statement balance. An unresolved carry-forward variance corrupts every subsequent reconciliation.

In plain language: Records the closing balance shown on the bank statement for the period, which serves as the starting point for the bank-side adjustments.

Common mistake: Copying the bank balance from memory or a prior email rather than directly from the official bank statement. Even a one-digit transposition creates a false reconciling item that wastes hours to trace.

In plain language: Lists every check issued and recorded in the books during or before the period that has not yet cleared the bank, with check number, date, payee, and amount for each item.

Common mistake: Omitting checks that have been outstanding for more than 90 days on the assumption they will never clear. Stale checks occasionally clear unexpectedly, and regulators may require escheatment of long-outstanding amounts.

In plain language: Itemizes deposits recorded in the company's books before period end that do not appear on the bank statement because the bank processed them after the statement cut-off date.

Common mistake: Allowing the same deposit to appear as 'in transit' on two consecutive reconciliations without investigation. A deposit that fails to clear within 5–7 business days may indicate a processing error or a fraudulent posting.

In plain language: Documents any transactions on the bank statement that the company believes are bank errors — duplicate debits, misposted items, or fees charged in error — and the amounts the bank has agreed to correct.

Common mistake: Recording a suspected bank error as an adjusting item without first contacting the bank and obtaining written confirmation. An unconfirmed bank error is a book error until the bank acknowledges it.

In plain language: Lists every error found in the company's general ledger during reconciliation, states the correct amount, and cross-references the journal entry number used to correct the book balance.

Common mistake: Noting the error on the reconciliation form without creating and posting the corresponding journal entry. An acknowledged error that is not corrected in the ledger will reappear as a reconciling item in every future period.

In plain language: Captures bank service charges, wire fees, interest income, and NSF check reversals that appear on the bank statement but have not yet been recorded in the company's books, requiring book-side adjusting entries.

Common mistake: Recording bank interest income in the wrong period. Interest credited on the last day of the month may appear on the following month's statement depending on the bank's cut-off — verify the value date before recording.

In plain language: Presents the final adjusted bank balance and the final adjusted book balance side by side, confirming they are equal — this equality is the proof that the reconciliation is complete and correct.

Common mistake: Forcing agreement by plugging an unexplained amount into either side of the reconciliation. Any residual difference must be traced and documented in the discrepancy log before the reconciliation is certified.

In plain language: Documents who prepared the reconciliation and who reviewed and approved it, with dates and signatures, establishing the segregation-of-duties control required by most internal control frameworks.

Common mistake: Having the same person prepare and approve the reconciliation. This eliminates the independent review control, defeating the primary fraud-detection purpose of the document and violating SOX, COSO, and most audit requirements.

A bank reconciliation is a formal accounting document that compares a company's internal cash ledger balance to the closing balance on its bank statement for the same period. It identifies timing differences — such as outstanding checks and deposits in transit — and errors on either side, then produces a certified adjusted balance that both the books and the bank agree on. It is one of the most fundamental internal controls in any accounting function.

Monthly reconciliation is the standard minimum for any business with ongoing transaction activity. High-volume businesses — retailers, e-commerce companies, or any entity processing hundreds of transactions per month — should reconcile weekly or even daily for critical accounts. Auditors and lenders typically expect to see monthly reconciliations completed within 10–15 business days of the period-end close.

A signature certifies that the preparer and a separate reviewer have independently verified the reconciliation is complete and accurate. This dual-approval control is required by the Sarbanes-Oxley Act (SOX) for public companies, by most external audit standards, and by internal control frameworks such as COSO. Without a signed approval, the document is a worksheet, not an auditable internal control.

The bank balance is the ending balance shown on the bank statement — reflecting all transactions the bank has processed. The book balance is the cash balance in the company's general ledger — reflecting all transactions the company has recorded. The two differ because of timing (outstanding checks, deposits in transit) and because some items appear on the bank statement before the company records them (bank charges, NSF returns, interest). The reconciliation bridges the two.

Any residual difference after accounting for all known timing items must be investigated — not plugged. Common causes include transposition errors (e.g., recording $1,530 as $1,350), duplicate entries, missing transactions, or an unrecorded bank charge. The difference should be logged in a discrepancy register and escalated to the controller or CFO. If fraud is suspected, escalate to management and legal counsel immediately rather than attempting to resolve it internally.

A bank reconciliation signed by the preparer and an approving officer is a formal business record with legal significance. It is used as primary evidence in financial audits, tax examinations, fraud investigations, and litigation involving cash balances. Intentionally falsifying a reconciliation — for example, plugging an unexplained balance — can constitute a false record under securities law, tax regulations, and general fraud statutes in most jurisdictions.

The person who prepares the reconciliation should not have authority to initiate or record cash transactions — typically a bookkeeper or staff accountant. The approver should be someone independent of the transaction-recording function — a controller, CFO, or business owner. This segregation of duties is the single most important control in the reconciliation process and the primary defense against occupational cash fraud.

At minimum: the official bank statement for the period, the general ledger cash account detail for the same period, copies of any journal entries made to correct book errors, and written correspondence with the bank regarding any confirmed bank errors. External auditors expect the complete package — a reconciliation form without supporting documents provides minimal audit evidence.

Accounting platforms such as QuickBooks, Xero, and NetSuite automate much of the matching process and reduce manual entry errors. However, the reconciliation must still be reviewed, exceptions must be investigated, and a signed approval record must be produced — the software does not eliminate the need for human judgment or the certification requirement. This template is useful for businesses without dedicated accounting software, for supplemental documentation, or as a standalone record for auditor delivery.