A bank reconciliation sign off should show who prepared the reconciliation and when, who reviewed it and when, and what the reviewer actually checked. The reviewer's notes on open items and questions asked matter more than the signature. A bare initial in a corner proves only that someone touched the page.
What should a bank reconciliation sign off show?
A bank reconciliation sign off should show five things: the preparer's name and completion date, the reviewer's name and review date, the account and period covered, the specific checks the reviewer performed, and any follow-up the review raised. Together they let a third party see that review happened and what it covered.
A sign-off block to copy
The block below goes at the foot of each reconciliation. The values are examples.
| Field | Example entry |
|---|---|
| Account and period | Operating checking ending 2210, March 2026 |
| Prepared by, date | R. Ortiz, 2026-04-06 |
| Statement balance agreed to bank PDF | Yes, 48,215.60 |
| Book balance agreed to general ledger | Yes, 47,902.15 |
| Reconciling items traced to support | 6 of 6, outstanding checks to register, deposit to April statement |
| Items over 60 days old | 1 check, 212.00, payee contacted 2026-04-07 |
| Unexplained difference | None |
| Reviewed by, date | L. Chen, 2026-04-09 |
| Reviewer notes | Asked about transfer of 5,000.00 on 03-22; savings funding, agreed to savings statement |
The rows between the two signatures are the evidence. They record what the reviewer looked at, which turns a signature into a statement of work.
Why is a bare initial weak evidence of bank reconciliation review?
A bare initial is weak evidence of bank reconciliation review because it cannot show what the reviewer looked at, how long they spent or whether they asked anything. An auditor testing the control sees the same initials on a careful review and on a five-second glance. With nothing else on the page, the reviewer cannot prove the difference either.
Three gaps make an initial alone unconvincing:
- No date. Without a review date, nobody can tell whether review happened before the books closed or months later.
- No scope. An initial does not say whether the reviewer agreed the balances to source or just glanced at the bottom line.
- No trail. If the reviewer asked about an item and got an answer, that exchange is invisible.
The fix is cheap. Add the date, tick each line of the sign-off block, and write one sentence for every question asked. That record also protects the reviewer if a problem surfaces later.
Electronic bank reconciliation sign-off in software and spreadsheets
An electronic bank reconciliation sign-off counts as evidence when the system records who signed and when, and the signer could not easily edit that record afterward. A click in accounting software that logs the user and timestamp is usually stronger than a typed name in a spreadsheet cell, because anyone with the file can type any name.
For spreadsheets, a few habits close the gap:
- Save the finished reconciliation as a PDF and store it with the statement, so later edits do not change the signed version.
- Have the reviewer sign the PDF, or add a comment from their own account in a shared file, so the record carries their identity.
- Keep the version history of the workbook switched on in shared storage.
Software sign-off has its own trap. If the preparer and the reviewer share a login, the system records one user for both steps, and the separation exists only on paper. Each person needs their own credentials.
Tools that build the reconciliation from the statement add more evidence. PreciseBankFlow produces an exception report that lists each difference, duplicate and gap with its source line, ready for a reviewer to sign, so the record of what was checked comes with the reconciliation rather than being written afterward.
Reconciliation sign-off in nonprofits, churches and law firm trust accounts
Reconciliation sign-off in nonprofits, churches and law firm trust accounts follows the same rule, a reviewer independent of the preparer, but the reviewer is often a board member, treasurer or managing partner rather than a manager. The sign-off block should name their role, because it shows whose oversight the organization relies on.
Nonprofits and churches
Small nonprofits often have a volunteer treasurer who both records and reconciles. In that case, a board member or finance committee member should review and sign the reconciliation each month, with the bank statement in hand. Nonprofit cash controls for small organizations covers how board oversight fits with volunteers. In a church, the weekly count sheets feed the deposits on the reconciliation, so the reviewer should trace a sample of deposits back to the signed count; church offering counting procedures explains the count sheet and the two-counter rule.
Law firm trust accounts
Trust accounts that hold client money usually need a reconciliation of the bank, the trust ledger and the individual client ledgers, and the rules of the firm's state bar decide how often and who must sign. Software built for this work records each sign-off against the reconciliation; what trust accounting software for law firms must do lists the reports a bar auditor expects.
Backdated and pre-signed reconciliation sign-offs
Backdated and pre-signed reconciliation sign-offs are the mistake that turns a review control into a false record. A reviewer who signs before the work is done, or dates a late signature to look on time, makes the file say something that did not happen. That is worse than a missing signature, because it hides the gap.
The common forms are easy to spot once you look:
- Sign-off dates that fall before the statement was available from the bank.
- The reviewer's date identical to the preparer's on every month, including weekends.
- A run of months signed in the same pen on the same day during year-end cleanup.
- Signature blocks printed with the reviewer's name already typed in.
When review is late, sign with the real date and add a note giving the reason. A reviewer who catches up three months at once should say so on each page. An honest late date shows a control that slipped and recovered; a false date shows a control that cannot be trusted at all.