The bank reconciliation was signed off with a zero difference. Two weeks later, the controller learned that one of the “outstanding checks” had been stopped at the bank before month-end but never voided in the ERP.
The reconciliation tied because the books and the schedule carried the same stale error. Cash was still understated by $25,000.
A bank reconciliation is not complete just because the adjusted balances agree. It is ready for approval only when every difference is classified, every required book adjustment is posted, and every open timing item has support and an owner. The reviewer should be able to trace the conclusion back to the underlying bank and general ledger activity.
This guide explains how to prepare a bank reconciliation statement, distinguish bank-side from book-side items, record the right journal entries, investigate breaks in the right order, and narrow month-end review to cutoff, adjustments, and unresolved exceptions.
For the broader account reconciliation process across AR, AP, payroll, intercompany, deferred revenue, and fixed assets, see Maxima’s definitive guide to reconciliations in accounting.
What is a bank reconciliation statement?
A bank reconciliation statement is the workpaper that bridges two independent views of the same cash: the balance a company has recorded in its general ledger, and the balance its bank reports at period end. It documents each item that explains the gap between them and shows both views resolving to one adjusted figure.
Three related terms are often used interchangeably, but they mean different things:
Bank statement: The external record issued by the bank, showing deposits, withdrawals, fees, transfers, and the ending bank balance for the period.
Bank reconciliation: The process of comparing bank activity with the company’s cash records, investigating differences, and recording required corrections.
Bank reconciliation statement: The completed workpaper showing the two balances, reconciling items, adjusted balances, support, and review conclusion.
The statement is more than a list of matched transactions. It is the control record of every item that did not match immediately and how it was resolved or carried forward.
A useful review standard is: A bank reconciliation is complete when there are no unexplained differences, not necessarily when there are no open items.
A recently issued check may still be outstanding at month-end. A deposit made late on the final day may still be in transit. Those can be valid open timing items. An unidentified debit labeled “ACH PAYMENT” with no owner or evidence is not.
The standard bank reconciliation statement format
A bank reconciliation statement normally presents two bridges to one adjusted cash balance.
Bank side | Book side |
|---|---|
Ending balance per bank statement | Ending cash balance per GL |
Add deposits in transit | Add bank credits not yet recorded, such as interest |
Less outstanding checks and payments | Less bank debits not yet recorded, such as fees, direct debits, and returned payments |
Add or subtract bank errors, if any | Add or subtract book errors, if any |
Adjusted bank balance | Adjusted book balance |
The adjusted balances should agree. Not every reconciliation uses every line, but the logic should remain visible: bank-side items generally explain clearing differences, while book-side items identify activity or errors that must be recorded in the GL.
The four outcomes for every bank difference
Many bank reconciliation errors begin with misclassification: a book-side omission is carried as an outstanding item, or a clearing delay triggers an unnecessary journal entry.
Every difference should end in one of four categories:
Difference category | What it means | Bank reconciliation treatment | Journal entry? | Common examples |
|---|---|---|---|---|
Valid timing item | The company recorded the transaction correctly, but the bank has not processed it by the statement date | Adjust the bank side and carry the item with support until it clears | Usually no | Outstanding checks, ACH payments in transit, deposits in transit |
Book-side item requiring an entry | The bank recorded activity that is not yet in the GL | Adjust the book side, post the entry, and refresh the GL balance | Yes | Bank fees, interest, returned customer payments, direct debits |
Error requiring correction | The bank or books contain an incorrect amount, account, date, or duplicate | Correct the record where the error occurred and document the resolution | Depends on the source of the error | Duplicate GL posting, wrong bank account, incorrect amount, bank processing error |
Unresolved exception | The item cannot yet be identified or classified | Escalate and keep it visible in the exception log, not buried in “other”; if the bank movement is confirmed, record it under policy, often to a controlled suspense or clearing account, until final classification | Sometimes | Unknown ACH debit, unexplained transfer, missing bank data |
The category determines whether the schedule changes, the GL changes, or the item requires escalation. If the books already contain a valid transaction and the bank has not cleared it, the GL usually does not change. If the bank contains valid activity missing from the books, it usually does. A bank error should remain visible as a supported bank-side reconciling item until the bank corrects it; the company should not force the GL to agree with an incorrect statement.
How to prepare a bank reconciliation statement
A reliable bank reconciliation process has six steps. The sequence matters because matching an incomplete population can produce a clean but false result.
1. Confirm the account, period, and opening balance
Verify the legal entity, bank account, currency, statement dates, and completeness of the statement or imported bank population. The beginning GL balance and rolled-forward open items should trace to the prior approved reconciliation. If they do not, investigate backdated entries, voids, deletions, or changes to previously reconciled transactions before matching anything.
2. Match bank activity to the GL
Start with exact matches using transaction number, amount, date, and reference. Then evaluate grouped relationships, such as one bank debit matched to several AP payments or one summarized GL entry matched to several bank lines. A one-to-many relationship is not an exception when the grouped amounts agree and the batch or remittance support proves the link.
3. Classify every unmatched item
Assign each remaining item to one of the four outcomes above. Avoid generic categories such as “miscellaneous,” “other,” or “timing” without a specific explanation.
4. Post required book-side entries
Record valid bank activity missing from the GL. When the cash movement is confirmed but its final classification remains open, company policy may require a controlled suspense or clearing entry. Then refresh the cash detail. The final reconciliation should tie to the posted GL, not to a worksheet balance that assumes proposed entries will be posted later.
5. Support and age open timing items
Each open item should have clear support, an age, an owner, and an expected resolution. Escalation rules should reflect payment method, bank terms, company policy, and applicable unclaimed-property requirements. A one-day-old ACH and a 90-day-old paper check should not receive the same review merely because both are outstanding.
6. Finalize and review the statement
The completed statement should show the ending bank balance, bank-side reconciling items, adjusted bank balance, GL cash balance, book-side adjustments, adjusted book balance, open-item schedule, and preparer and reviewer sign-off.
The reviewer should verify more than the arithmetic. They should confirm population completeness, inspect unusual and aged items, ensure required entries were posted, and test selected matches back to source evidence. The Washington State Auditor’s bank reconciliation guidance likewise emphasizes timely reconciliation, complete supporting detail, investigation to source, and independent review.
Worked example 1: A complete bank reconciliation statement
A company is reconciling its operating account for March 31.
Bank side
Item | Amount |
|---|---|
Bank statement ending balance | $1,286,740 |
Add: Deposit in transit from March 31 | $84,600 |
Less: Outstanding payments | ($117,450) |
Adjusted bank balance | $1,253,890 |
The deposit in transit was recorded in the GL on March 31 and appears on the bank on April 1. The outstanding payments were recorded before month-end but cleared in April. Both are valid timing items and require no March journal entry.
Book side
Item | Amount |
|---|---|
Cash balance per GL before adjustments | $1,259,365 |
Less: Bank service fees | ($620) |
Less: Returned customer payment | ($5,400) |
Add: Interest income | $545 |
Adjusted book balance | $1,253,890 |
Both adjusted balances equal $1,253,890.
Journal entries resulting from the reconciliation
1. Record bank service fees
Account | Debit | Credit |
|---|---|---|
Bank Fees Expense | $620 | |
Cash | $620 |
2. Reinstate the customer receivable for the returned payment
Account | Debit | Credit |
|---|---|---|
Accounts Receivable | $5,400 | |
Cash | $5,400 |
The customer payment previously reduced AR and increased cash. When the bank returns it, the company still has a receivable from the customer.
3. Record interest income
Account | Debit | Credit |
|---|---|---|
Cash | $545 | |
Interest Income | $545 |
After these entries post, the GL cash balance is $1,253,890 and agrees to the adjusted bank balance.
A bank reconciliation does not always generate journal entries. If every difference is a valid deposit in transit or outstanding payment and the books contain no errors or omitted bank activity, the reconciliation may require no entry at all.
Worked example 2: A reconciliation that ties but should fail review
A preparer submits the following April 30 reconciliation.
Submitted bank side
Item | Amount |
|---|---|
Bank statement ending balance | $2,498,200 |
Add: Deposit in transit | $180,000 |
Less: Outstanding payments | ($142,500) |
Adjusted bank balance | $2,535,700 |
The workpaper also shows a book balance after adjustments of $2,535,700. The difference is zero.
The reviewer does not approve it yet.
Review finding 1: The workpaper does not agree to the final GL
The April 30 GL cash balance is $2,540,900, not $2,535,700. The preparer deducted a $5,200 bank fee in the spreadsheet, but the journal entry was never posted.
The required entry is:
Account | Debit | Credit |
|---|---|---|
Bank Fees Expense | $5,200 | |
Cash | $5,200 |
After posting, cash per the GL becomes $2,535,700.
Review finding 2: One outstanding payment will never clear
The reviewer samples the outstanding-payment list and finds a $25,000 vendor check that Treasury stopped at the bank on April 25, but the AP team had not voided the payment in the ERP. The item should not remain on the outstanding list because it is no longer a valid payment in transit.
Assuming the original payment reduced accounts payable, the reversal is:
Account | Debit | Credit |
|---|---|---|
Cash | $25,000 | |
Accounts Payable | $25,000 |
Cash increases to $2,560,700. The outstanding-payment list decreases from $142,500 to $117,500.
Corrected reconciliation
Bank side | Amount |
|---|---|
Bank statement ending balance | $2,498,200 |
Add: Deposit in transit | $180,000 |
Less: Valid outstanding payments | ($117,500) |
Adjusted bank balance | $2,560,700 |
Book side | Amount |
|---|---|
GL cash balance before reconciliation entries | $2,540,900 |
Less: Bank fee posted | ($5,200) |
Add: Reversal of stopped vendor payment | $25,000 |
Adjusted and posted book balance | $2,560,700 |
The corrected reconciliation still has a zero difference, but now it deserves approval.
This example shows why a reviewer should not begin and end with the difference field. A zero can hide an unposted entry, a stale item, an unsupported plug, or two errors offsetting each other.
Common bank reconciliation breaks and what to investigate first
The fastest review is not the one that checks items in worksheet order. It checks them in risk order.
Symptom | Likely causes | First evidence to inspect | Likely resolution |
|---|---|---|---|
Unknown bank debit or transfer | Unauthorized activity, treasury transaction not communicated, unclear bank description | Bank detail, treasury confirmation, payment platform, authorized-user log | Identify and post, reclassify, or escalate immediately |
Bank balance does not agree to the statement | Missing statement page, incomplete import, wrong statement range, wrong account | Official statement, import history, account mapping | Correct the population before matching |
Opening balance does not agree to prior reconciliation | Backdated entry, void, deletion, changed prior-period transaction | Prior reconciliation, GL change log, reconciliation history | Reopen, correct, and document the prior-period change |
Bank fee, direct debit, interest, or return has no GL match | Bank activity was not recorded, was posted to another cash account, or arrived after the last import | Bank transaction detail, AP/AR, treasury support, GL activity | Post or reclassify the entry, or identify a bank error |
GL item has no bank match | Valid timing item, wrong bank account, failed payment, or posting error | Payment status, deposit support, bank portal, transaction history | Carry with support, reverse, or reclassify |
The same transaction appears twice | Duplicate GL posting, duplicated bank-feed line, or statement file imported twice | Transaction IDs, source references, import history, posting log | Reverse or remove the duplicate and retain the correction trail |
Transaction appears in the wrong period | Incorrect posting date, backdated entry, late bank processing, or wrong statement cutoff | Source initiation date, bank value date, GL posting date, statement dates | Correct the period or document a valid timing difference |
One bank amount equals several GL items | AP batch, payroll funding, grouped transfer | Batch report, payment file, payroll funding report | Complete grouped match |
Several bank lines equal one GL amount | Split settlement, multiple transfers, bank processing pattern | Remittance detail, processor report, journal support | Complete grouped match or correct summary posting |
Deposit in transit remains open beyond expected clearing | Wrong bank account, failed deposit, incorrect date, duplicate GL receipt | Deposit slip, bank portal, cash receipt detail | Reclassify, reverse, or escalate |
Outstanding payment continues aging | Lost check, rejected ACH, void not posted, payee issue | Payment status, void/reissue records, payee confirmation | Void, reissue, follow policy, or continue with evidence |
Reconciliation ties only after a manual plug | Unposted JE, hidden error, incomplete population | Final GL, adjustment log, source statements | Remove the plug and resolve the underlying difference |
Unknown cash movements and population-completeness problems should come first. Fresh, supported timing items should come last. A reviewer who spends time recasting every ordinary match before investigating an unidentified debit has the priority backward.
The bank reconciliation exception checklist
Before an exception is carried forward, confirm that the workpaper answers these questions:
What is the transaction?
On which side does it appear?
Which of the four outcomes above applies?
Does it require a journal entry?
What source evidence supports the classification?
How old is it?
Who owns the next action?
When should it clear or be resolved?
Has it appeared in a prior reconciliation?
Does it indicate a recurring upstream problem?
“Timing, will clear next month” is not enough once an item has rolled for three months. The note should identify the transaction, evidence, expected resolution, and owner.
The bank reconciliation evidence pack
A review-ready evidence pack lets a reviewer trace any reconciling item to its support. It should include:
Evidence component | What it should contain |
|---|---|
Bank statement or controlled bank extract | Correct account and period, ending balance, and evidence that the transaction population is complete |
Final GL cash detail | Cash-account export and trial-balance amount refreshed after reconciliation entries are posted |
Reconciliation summary | Bank and book balances, every reconciling item, adjusted balances, and zero unexplained difference |
Exception log | Per-item classification, age, evidence, owner, status, expected resolution, and journal-entry requirement |
Supporting schedules | Outstanding payments, deposits in transit, ACH or wire batches, processor reports, payroll funding reports, deposit support, and bank correspondence as relevant |
Journal entries and approvals | Entry, source support, approver, posting reference, and proof that it reached the GL before sign-off |
Rollforward and review history | Prior-period open items, changes after preparation, preparer and reviewer, dates, and final conclusion |
PCAOB AS 2201 does not prescribe a bank reconciliation template. It provides broader ICFR context for whether a control addresses the relevant risk and operates with sufficient precision. Within that framework, the bank reconciliation functions as a key detective control over cash: it is designed to identify errors, omissions, and unauthorized activity that other controls did not prevent. For SOX-compliant teams, the evidence pack above is what demonstrates the control operated effectively. Here, precision means complete source populations, posted corrections, supported timing items, and independent review.
How bank reconciliation works in NetSuite
NetSuite’s native bank reconciliation separates bank matching from statement reconciliation, and the controls live in the gap between them.
Matching happens on the Match Bank Data page, reached through Transactions > Bank > Match Bank Data. Imported bank lines appear in one grid and NetSuite account transactions in another after bank data arrives through a direct bank feed or file import.
Before manual matching, Oracle recommends Automated Cash Application, when applicable, to generate customer payments from imported bank lines and apply them to open invoices. Those payments are then matched and cleared automatically. This is a separate workflow: running reconciliation rules on Match Bank Data does not itself run Automated Cash Application.
Intelligent Transaction Matching then applies the account’s reconciliation rules. NetSuite includes system rules, and teams can add user-defined rules for recurring patterns. The workflow supports one-to-one, one-to-many, many-to-one, and many-to-many relationships, so one ACH batch can match several bill payments or several bank lines can match one summarized entry.
If a rule finds multiple possible matches, NetSuite does not automatically choose among them unless enriched data can distinguish the candidates. If two or more candidates remain equally plausible, the preparer must review and select the correct match. Remaining items are cleared, excluded, or created manually, and each action should have a documented reason. A match is ready to submit only when the Difference field reaches zero, and recurring one-to-one activity can be handled by an auto-create rule that the preparer still confirms.
Matched and cleared transactions move through the Review subtab to Reconcile Account Statement, where the preparer enters the statement date and ending balance and completes the reconciliation. NetSuite also offers Enriched Bank Data, which uses generative AI to help distinguish ambiguous same-amount candidates, though Oracle warns that AI-assisted results can be wrong and should be verified.
One behavior matters for control more than the rest. NetSuite removes matched or cleared status when a transaction is edited, deleted, or voided without a reversing entry, and the status can be removed from the rest of a match group as well. Previously reviewed activity can therefore reappear as unmatched after sign-off. The preparer and reviewer should confirm that:
The latest bank import is complete and the bank account, subsidiary, and currency are correctly linked
Grouped matches have real batch or remittance support, and excluded lines were excluded for a documented reason
Book-side entries posted before the final GL balance was used
Edits, voids, deletions, or undone matches have not reopened previously reviewed activity
Oracle’s bank data matching and reconciliation documentation explains the native workflow. The question it leaves open is how much investigation and evidence assembly remains after the rules run. For a broader comparison of ERP-native tools and reconciliation platforms, see Maxima’s guide to the best bank reconciliation software in 2026.
What changes with agent-prepared bank reconciliation
Cash should arrive at month-end already sorted.
Bank activity occurs throughout the month, so exact and grouped matches can be prepared as transactions arrive. Bank-only activity can be identified before cutoff, proposed entries can be queued with their source transactions, and unknown or aged items can reach an owner while the context is still current.
At month-end, the reviewer should face a narrowed population:
Transactions still unmatched at cutoff
Timing items requiring support and aging
Book-side items with drafted or posted entries
Unknown or unusual cash movements
Items changed after preparation
Prior-period exceptions still unresolved
The reviewer starts with the unresolved population, not a blank reconciliation.
Automated matching solves only the first layer. The harder work is what matching does not touch: investigating unidentified items, deciding which exceptions need entries or escalation, and keeping the support a reviewer and auditor will later need.
For teams using NetSuite’s native workflow, matching and statement reconciliation happen inside the ERP. Maxima supports a different operating model: it runs the matching itself across connected bank and accounting data while NetSuite remains the system of record.
Maxima then carries the work past the match. It connects the bank activity, the current NetSuite GL balance, and the reconciliation workpaper, prepares book-side entries with transaction-level lineage, and routes the remaining exceptions into review. Low-risk accounts within configured tolerances can be auto-signed off under an approved policy, while out-of-threshold accounts, unusual movements, and all proposed entries route to accountants for review and approval. If the GL balance changes after sign-off, the account is flagged for re-review. The same workflow can operate with the reconciliation workbooks a team already uses.
Max, Maxima’s 24/7 accounting agent, executes the cash-to-GL reconciliation as a multi-step accounting workflow. It follows the team’s configured process and policies, gathers the required context and support from connected systems, and checks in when an exception requires accounting judgment before continuing the workflow or preparing any related cash journal entry. As it prepares the work, the review trail captures the source data, applied logic, validations, exceptions, and approvals, so the evidence is attached when the reviewer opens the account rather than assembled afterward.
Rippling cut cash reconciliation time by 50% with Maxima and redeployed four FTEs from manual reconciliation to higher-value work.
Consider the stopped check that still showed as outstanding earlier in this guide. The work does not end when the balances agree. The check stays an open timing item, surfaced with its support, for the reviewer to confirm it was stopped and reverse it before sign-off.
A bank reconciliation statement should not be the place where the month’s cash activity is first understood. It should be the final proof that the activity was understood, corrected where necessary, and reviewed before cash was reported.
The reviewer’s job should be judgment, not assembly. See how Maxima continuously prepares bank reconciliations, drafts cash journal entries, and routes exceptions for approval.
Frequently asked questions
What is a bank reconciliation statement?
A bank reconciliation statement is the workpaper that proves the company’s recorded cash ties to what the bank reports. It starts with the two ending balances, documents every difference between them, classifies each one as a timing item, a required book entry, an error, or an open exception, and shows both sides resolving to the same adjusted figure. The statement is complete when no difference remains unexplained.
What is the difference between a bank statement and a bank reconciliation statement?
The bank statement is produced by the bank and records activity processed through the account. The bank reconciliation statement is produced by the company and explains the differences between the bank’s record and the company’s books.
Which bank reconciliation items require journal entries?
Bank fees, interest, returned customer payments, direct debits, missing collections, and book errors commonly require entries. Deposits in transit and outstanding payments usually do not because they are already recorded in the books and are waiting to clear the bank.
Can a bank reconciliation be complete with outstanding items?
Yes. It can be complete with valid, supported timing items such as recent outstanding checks or deposits in transit. It should not be approved with unexplained differences, unsupported aging items, or proposed book adjustments that have not been posted.
How often should bank reconciliations be performed?
Monthly is a common minimum for formal sign-off. High-volume, high-risk, or operationally critical cash accounts may need daily or weekly matching and exception review so that month-end is a cutoff review rather than a full reconstruction.
What should a bank reconciliation reviewer check?
The reviewer should confirm opening and ending balances, population completeness, the bank-versus-book classification of each difference, posted journal entries, support for open items, aging, ownership, and the absence of unexplained plugs. The reviewer should also test selected transactions back to source evidence.
Can bank reconciliation be automated?
Matching, grouping, bank-data ingestion, exception identification, and entry drafting can be automated or continuously prepared, and low-risk accounts within approved policy thresholds can be signed off automatically. Investigation of unknown activity, classification that requires judgment, approval of journal entries, stale-item decisions, and sign-off of any out-of-threshold or exception account still require accountable review.
Move closer to an audit-ready, continuous close
Request demo
Insights, news and content
The latest
See all
