Bank Reconciliation Statement: Complete Guide + Examples For Controllers (2026)
.png)
When cash doesn't tie, everything else slows down. Reviewers lose confidence, close timelines stretch, and audit support becomes harder than it needs to be. The bank balance says one thing, the GL says another, and someone needs a documented explanation fast.
A bank reconciliation statement is that explanation. It's the finished document that shows how you got from two different numbers to one reconciled cash position, with every difference accounted for and supported.
This guide covers how to prepare a complete bank reconciliation statement, what it should look like, the journal entries it generates, and how to run the process well every month.
What Is A Bank Reconciliation Statement?
A bank reconciliation statement is the completed document that reconciles the bank statement ending balance to the company's cash balance in the books and accounts for every difference between the two.
This isn't just a record of what matched. Instead, it's a formal schedule showing balances, reconciling items, adjusted balances, and supporting notes.
Its purpose is twofold:
- To confirm cash accuracy for financial reporting.
- To create a documented control artifact that holds up to reviewer scrutiny and audit requests.
Cash is high-risk, high-frequency, and heavily relied upon in close reporting. That's what makes this document particularly important for Controllers and accounting managers: a weak bank rec is a weak control, and auditors know it.
Bank Statement Vs. Bank Reconciliation Vs. Bank Reconciliation Statement
These three terms get used interchangeably all the time, even by experienced accountants. They're not the same thing, and mixing them up creates confusion about what you're actually being asked to prepare or review.
- Bank statement: The external record from the bank showing activity and ending balance for the period.
- **Bank reconciliation:** The process of comparing bank activity to the company's internal records to identify differences.
- Bank reconciliation statement: The formal, documented schedule that shows how both balances were adjusted to agree (aka, the output of the bank reconciliation process).
Why It Matters To Accountants And Controllers
A strong bank reconciliation statement does more than just confirm the math. It improves confidence in reported cash, which flows directly into the balance sheet, cash flow analysis, and downstream decision-making. It's also a core internal control for detecting unauthorized activity, duplicate transactions, omissions, and posting errors.
The close-process angle matters too.
Poor bank recs create last-minute fire drills, requiring your team to reconcile items that were never investigated, journal entries that weren't posted, reviewer questions that can't be answered quickly. Strong bank recs reduce all of that friction and make audit support a matter of pulling a file instead of reconstructing a process. As part of a modern month-end close process, bank recs are no longer just a checklist item — they're a signal of close maturity.
How To Prepare A Bank Reconciliation Statement Step By Step
The steps below cover the full process from gathering documents to signing off on a completed statement. Follow them in order, as each step builds on the one before it and skipping ahead is how things get missed.
Step 1: Gather The Right Documents And Confirm The Period
Before matching a single transaction, make sure you have everything in front of you:
- Bank statement for the period
- GL cash detail or trial balance
- Prior-period reconciliation
- Outstanding items tracker
- Any processor or treasury support needed for specific transaction types
The reconciliation only works if everything aligns to the same reporting period and account. Confirm the opening balance agrees to the prior-period closing reconciliation before moving forward. That's the first control, and skipping it is how errors carry forward undetected.
Step 2: Match Transactions And Identify Unmatched Items
Work through the bank statement and internal records side by side, ticking off deposits, withdrawals, checks, fees, and transfers that appear in both. What's left — items that appear in one place but not the other — becomes your reconciling item list.
Categorize unmatched items immediately rather than leaving them in a generic "difference" bucket:
- Timing difference: Already recorded on one side, not yet reflected on the other.
- Unrecorded bank item: The bank has activity the books don't know about yet.
- Posting error: Something hit the wrong account, wrong amount, or wrong period.
- Duplicate: The same transaction recorded twice.
- Unknown exception: Needs investigation before it can be classified.
In higher-volume environments, transaction-level visibility makes this step significantly faster. Manually ticking through hundreds of lines in a spreadsheet is where errors get missed and time gets wasted.
Step 3: Adjust The Bank Side
The bank side starts with the bank statement ending balance, then gets adjusted for items the company has already recorded that the bank hasn't yet reflected:
Adjusted Bank Balance = Bank Statement Ending Balance + Deposits in Transit − Outstanding Checks
Deposits in transit are receipts the company recorded before the bank processed them. Outstanding checks are payments the company issued that haven't cleared the bank yet. Neither requires a journal entry, as the books already reflect them.
Step 4: Adjust The Book Side
The book side is updated for items that show up on the bank statement but haven't yet been recorded in the GL. These typically include:
- Bank service charges and wire fees: The bank deducted them; the books don't reflect them yet.
- Interest earned: Credited by the bank; needs to be recorded as income.
- ACH withdrawals: Automated payments that hit the bank before anyone booked them.
- NSF items: A customer check bounced; the cash receipt needs to be reversed.
- Corrections: Errors identified through the reconciliation process.
Bank-side adjustments are timing items — the books already reflect them. Book-side adjustments require a journal entry before the reconciliation is considered complete.
Step 5: Record Journal Entries
The reconciliation identifies the differences. Journal entries are what actually correct the books. Until those entries are posted, the GL cash balance doesn't match the reconciled position.
Common entries and their logic are covered in the journal entries section below. What matters here is the workflow: each book-side item identified in step 4 should flow directly into a journal entry that gets prepared, reviewed, and posted, instead of being left as a note on a spreadsheet.
Linking each entry back to its reconciliation support is what makes the process auditable.
Step 6: Verify Adjusted Balances Match
The reconciliation is complete when:
Adjusted Bank Balance = Adjusted Book Balance
If they don't match, resist the urge to assume something complex. Start with the basics: check cutoff dates, look for duplicate entries, verify that data imports pulled correctly, and confirm the outstanding items rollforward from the prior period was done accurately. Most reconciliation breaks have mundane causes.
Step 7: Document, Review, And Sign Off
This is where a mathematically correct reconciliation becomes an audit-ready one. The finished statement should include:
- Preparer name and date
- Reviewer name and date
- All reconciling items with descriptions and amounts
- References to supporting documentation for each item
- Explanations for anything unusual or aged
- Signoff fields that are actually completed
Modern close platforms can centralize this workflow — comments, approvals, activity logs, and attached support — so the documentation process doesn't become its own project. Numeric's Close Management gives teams a single place to manage reconciliation tasks, attach support, and track reviewer sign off in real time.
Bank Reconciliation Statement Format
Knowing how to prepare a bank rec is one thing. Knowing what the finished document should look like is another. If you want a ready-made starting point, Numeric's bank reconciliation template has everything you need built in.
Required Fields In The Statement
A complete bank reconciliation statement should include the following:
- Account name and number
- Legal entity
- Reporting period
- Bank name
- Preparer and reviewer names
- Preparation and review dates
- Beginning and ending balances
- Reconciling items with descriptions and amounts
- Adjusted bank balance
- Adjusted book balance
- Reference numbers linking to supporting documentation
A clean format helps both internal reviewers and external auditors follow the logic without back-and-forth questions.
Standard Layout To Recommend
The clearest bank reconciliation statement format is a two-sided layout: bank side on one side, book side on the other, both arriving at the same adjusted balance. You can have a separate section or appendix that handles outstanding checks, deposits in transit, and the journal entries required for book-side items.
Keep supporting documentation — including bank statements, source schedules, exception explanations — attached to or referenced from the statement so reviewers can trace every number without digging through shared drives.
What Makes A Statement Audit-Ready
Audit-ready means more than correct math. It requires the following:
- Version control
- Evidence retention
- Reviewer traceability
- A documented resolution for every open item
An auditor sampling cash transactions should be able to pull the bank reconciliation statement and trace any reconciling item to its source and resolution without asking a single follow-up question.
For teams using Numeric, month-end reconciliation workflows include timestamps, comments, reviewer workflows, and centralized support. That way, the audit trail builds itself as the work gets done.
Bank Reconciliation Statement Examples
The format of a bank reconciliation statement is easier to understand with actual numbers in front of you. The two examples below cover opposite ends of the complexity spectrum — a clean, straightforward rec and a messier one that more closely resembles real close conditions.
Example 1: Simple Bank Reconciliation Statement
Here's a straightforward bank reconciliation statement example to quickly demonstrate the format:
Both sides land at $43,900, so the reconciliation is complete. The deposit in transit and outstanding check are timing differences, which means no journal entries needed. The bank service charge and interest require book-side entries.
Example 2: Controller-Level Example With Modern Cash Activity
Real close conditions are messier. Here's a more realistic scenario:
One item — a $500 ACH debit from a vendor — remains unresolved. The amount doesn't match any open PO, and the bank description is ambiguous. It stays open, gets documented with a note, and carries into the next period's outstanding items tracker for follow-up.
Keep in mind that deposits in transit and outstanding checks don't generate new journal entries, as the books already reflect them. Book-side items, however, do.
Common Journal Entries From Bank Reconciliations
Every bank reconciliation generates at least a few journal entries. The ones below cover the most common scenarios, so bookmark this section and come back to it during close.
Bank Fees, Interest, And Direct Bank Activity
These are the most routine book-side entries — items the bank processes automatically that don't hit the books until the reconciliation.
The logic is straightforward: the bank already moved the money, so the entry simply catches the books up to what already happened.
NSF Checks, ACH Returns, And Error Corrections
Unlike bank fees and interest, these entries depend on the specifics of what happened. The same category of item can require different treatment depending on the fact pattern.
- NSF check: When a customer's check bounces, the cash receipt that was previously recorded needs to be reversed and the receivable reopened; the money didn't actually arrive.
- Duplicate entry: If the same transaction was recorded twice, reverse the second entry. Don't just net them — trace back to the original and correct it cleanly.
- Omitted entry: A transaction cleared the bank but was never booked. Record it now, and reference the reconciliation support in the entry description so the trail is clear.
- Amount correction: The entry posted at the wrong amount. Depending on how it was caught, either reverse and repost the correct amount, or record a correcting entry for the difference.
In all of these cases, the entry should be posted before the period closes. An identified error that doesn't make it into the books leaves the GL in a reconciled-but-wrong state.
Posting And Review Considerations
Journal entries should be posted promptly enough to keep the GL aligned with the reconciled cash position. Each entry should reference the reconciliation support it came from, and each should go through a preparer-reviewer workflow before posting.
Want to automate part of the process? Numeric's Journal Entry Automation supports drafting, batch posting, and preparer-reviewer controls. That way, the entries that come out of a bank rec follow the same approval process as everything else in the close.
.png)
Common Problems And How To Investigate Them
Bank reconciliations fail less because the concept is difficult, and more because exceptions pile up and don't get resolved. Here's how to triage the most common ones.
Unmatched Transactions
When a transaction doesn't match, work through a short checklist before escalating:
- Cutoff timing: Does the item fall just inside or outside the period? Check whether it should be in this rec or the next.
- Duplicates: Is the same transaction recorded twice on either side?
- Missing imports: Did all bank data pull into the system correctly?
- Wrong account: Did a payment post to the right bank account in the GL?
- Unbooked activity: Did the bank process something the company hasn't recorded yet?
Group open items by root cause rather than leaving them in a single "difference" bucket. A well-organized exception log makes recurring problems easier to spot and faster to resolve. And once you've identified a common pattern, you can address it proactively, too.
Want to learn more? Check out our transaction reconciliation guide.
Stale Outstanding Checks And Deposits In Transit
Reconciling items that keep rolling forward without resolution are worth investigating, as they're often pointing at a process gap or a transaction that needs to be voided, written off, or escalated.
For example, a check that's been outstanding for 90 days probably isn't clearing. It may need to be voided, re-issued, or written off depending on company policy and jurisdiction. And a deposit in transit aging past 30 days needs investigation.
Controllers should establish aging thresholds and make stale items visible to reviewers. Items buried in old worksheets that never get followed up are a frequent audit finding when it comes to common bank reconciliation errors, and are a sign of a process that needs tightening.
Reconciliation Breaks That Keep Coming Back
Recurring breaks aren't bad luck. In many cases, they're process signals that are telling you something.
Common causes of reconciliation breaks include:
- Treasury process gaps: Cash activity isn't being communicated to accounting in time.
- Payment processor delays: Settlement timing creates consistent differences that need a documented policy.
- Manual upload errors: Data isn't pulling cleanly from bank feeds or processor reports.
- Wrong account mapping: A bank account isn't mapped correctly in the ERP.
- Cut-off failures: Transactions are posting to the wrong period consistently.
Each recurring break should feed into a process improvement, instead of just getting cleaned up at month-end and forgotten. Numeric's Cash Matching surfaces exceptions, supports aging alerts, and provides transaction-level drill-down. That way, recurring patterns are visible and can be addressed quickly.
.png)
Best Practices For Accountants And Controllers
Getting the reconciliation done is the baseline, but running it well every month is the differentiator. Here's how to do exactly that.
Set The Right Reconciliation Frequency
Monthly reconciliation is the minimum, but it's not always enough. High-volume cash accounts, payment processor accounts, and concentration accounts may need weekly or even daily attention.
The goal is catching issues while there's still time to resolve them instead of discovering everything after month-end when options are limited.
Frequency decisions should be based on volume, materiality, and risk. A low-activity account with a few transactions a month is a different situation than a merchant account processing hundreds of settlements daily. For a deeper look at how this fits into the broader close, see our account reconciliation guide.
Standardize Policies Across Accounts And Entities
Inconsistent policies across accounts or entities are one of the most common sources of delay and audit friction. This is particularly common in multi-entity environments where different teams may be doing bank recs differently.
Standardize the following for smoother sailing:
- Naming conventions
- Bank reconciliation templates
- Sign off requirements
- Aging rules
- Materiality thresholds
When every reconciliation follows the same format and the same process, reviewers can work faster, training is easier, and audit support is more consistent. This is a powerful shift in processes once it takes effect, so don't underestimate it.
Strengthen Controls Without Slowing The Team Down
Strong controls and a fast close aren't mutually exclusive. The key is making the right things easy.
Segregation of duties between cash handling, reconciliation preparation, and review is a foundational control — the person posting cash shouldn't be the person reconciling it.
Reviewer checklists matter, too. Sign off should mean something more than "looks fine," as reviewers should be checking for the following before approving:
- Aging items
- Missing support
- Unresolved exceptions
- Journal entry completion
Build the checklist into your review template so it gets completed every time as part of your completed workflow.
How Numeric Helps With Bank Reconciliations And Bank Reconciliation Statements
Numeric sits at the intersection of reconciliation, close management, and accounting intelligence. This means we don't act as a standalone bank-feed tool, but instead as a platform that ties your whole workflow together — including your AI model, via Numeric's MCP.
For accounting teams that have outgrown spreadsheet-based bank recs, here's where Numeric fits in:
- Statement handling: Numeric's Cash Management platform extracts balances from bank statements and compares them against GL or workpaper totals, reducing manual data entry and the errors that come with it.
- Exception investigation: Numeric provides transaction-level visibility, exception surfacing, and real-time ERP data make it faster to identify what's causing a break and trace it to its source.
- Audit readiness: Preparer-reviewer workflows, centralized support, comments, timestamps, and downloadable audit trails mean the documentation builds as the work happens — not after the fact.
Teams see a real difference fast. Kyle, a Controller at Brex, put it this way after switching to Numeric's cash module:
"The months that we've been reconciling in Numeric have been the months I've spent the least amount of time investigating variances in our cash accounts."
Brex went from a 30% auto-match rate to 90%+ in their first month, compressing their close timeline from 6 business days to 4.
Numeric is built for accounting teams that want more than a checklist, as we offer true bank reconciliation automation. If bank reconciliations are a recurring pain point in your close, see what the workflow looks like inside our platform.
Wrapping Up
A bank reconciliation statement that's done well does three things:
- It gets the math right.
- It stands up to reviewer scrutiny.
- It supports audit requests without anyone having to reconstruct the process from scratch.
The mechanics aren't complicated. What separates teams that run this well from teams that scramble through it every month is process maturity. You need consistent documentation, real aging policies, reviewer workflows that actually mean something, and exceptions that get resolved rather than rolled.
Here's what that involves:
- Get the mechanics right: Understand the bank side versus the book side, know which items require journal entries, and verify that adjusted balances agree before signing off.
- Build documentation into the process: Audit-ready doesn't happen at the end; it happens when support is attached, exceptions are explained, and reviewers can follow the logic without asking questions.
- Treat recurring exceptions as process signals: Every break that keeps coming back is pointing at something upstream that needs to be fixed and ideally proactively prevented with real-time reconciliation.
Get those three things right consistently, and the bank reconciliation statement stops being a close-week stressor and starts being one of the cleaner parts of your process.
Ready to centralize your bank reconciliations, manage exceptions, and shorten your close with bank reconciliation automation? See how Numeric can help.
Frequently Asked Questions
Related Content
Bank Reconciliation Statement: Complete Guide + Examples For Controllers (2026)
Learn what a bank reconciliation statement is, step by step preparation, examples, and best practices for accountants and controllers.
.png)
Accounting Journal Entries: A Complete Guide for Finance Teams
Learn how to record accounting journal entries step by step, understand every entry type, handle recurring entries, prevent errors, and connect JEs to your month-end close.
.png)
Cash Flow Management in 2026: Complete Guide for Controllers and CFOs
Learn what cash flow management is, why it matters, the strategies and accounting workflows that drive it, and how tools support real-time control over cash.