Your bank statement says one amount. Your accounting software says another. The gap might be an uncleared payment, a missing fee, a duplicate entry or something that needs investigation. Reconciliation is the process that explains the difference instead of hiding it with a convenient adjustment.
Reconciliation in accounting means comparing an account’s records with another relevant record, explaining differences and making supported corrections where needed. Bank reconciliation compares the cash account with the bank’s records. Other reconciliations compare customer or supplier detail with the general ledger, or support balances such as inventory and loans. The aim is a balance you can explain, not merely two totals that happen to match.
This guide covers the workflow, a worked bank example, common mistakes and a practical review checklist. Sources were checked on October 12, 2026. Examples use invented amounts for teaching, not a real company’s records. This is general education, not accounting, tax or legal advice for your business. AI-generated illustrations show the workflow, not real software screens.
1. What is reconciliation in accounting?
A business records transactions in its books. Banks, payment processors, suppliers and internal systems may hold related records. Reconciliation checks that those records tell a consistent story for the same account and period. It also documents why legitimate differences exist.
Suppose you record a supplier payment on the last day of the month, but the bank processes it the following day. The two closing balances can differ even when both records are accurate. A reconciliation identifies that timing difference and carries it forward for follow-up. It should not record the payment again just to remove the gap.
Other differences are genuine errors or missing entries. A bank charge might appear on the statement before anyone records it in the ledger. A payment might have been entered twice. The right response depends on the evidence: record a missing transaction, correct an error or explain an item awaiting settlement.
OpenStax’s accounting text explains bank reconciliation through separate adjustments to the bank and book balances. That distinction is the foundation of the worked example below. An adjustment on a reconciliation schedule is not automatically a journal entry in the company’s books.
Reconciliation is a control, not a guarantee
A completed reconciliation can help find omissions and unusual activity. It cannot prove that every purchase was authorized, every invoice was genuine or every accounting judgment was correct. Two incorrect records can agree. Review the underlying transactions as well as the closing balance.
Our accounting software directory is a starting point for exploring tools, but software does not replace the explanation. The person preparing the reconciliation should be able to describe which records were compared, what changed and what remains unresolved.
2. Bank reconciliation and other account reconciliations
Bank reconciliation is often the first example people learn, but reconciliation is broader than cash. Different accounts need different supporting evidence. A bank statement is useful for checking cash; it cannot establish the value of all inventory or whether every customer balance is collectible.
Bank and credit card accounts
For a bank account, compare the ledger’s cash activity and balance with the statement for the same period. Identify outstanding payments, deposits in transit, fees, interest and errors. For a credit card, compare recorded purchases, refunds, charges and payments with the issuer’s statement, while remembering that a card balance is a liability rather than cash in the bank.
Receivables and payables
A subledger contains detailed transactions for an area such as customer invoices or supplier bills. The general ledger holds the corresponding account balance. Reconcile the detail to that balance so an unposted batch, manual journal or missing transaction does not quietly separate the two.
Oracle’s account reconciliation documentation describes comparing payables and receivables subledgers with the general ledger for a given period. It identifies incomplete accounting and manual ledger journals among possible exceptions. Those are useful examples, not a claim that every application follows Oracle’s process.
Other balance-sheet accounts
Inventory may need quantity records, valuation reports and count evidence. Loans need lender statements and schedules that distinguish principal from interest. Prepayments need a schedule showing what remains unexpired. The support should answer why the balance exists, not simply repeat the balance from another report.
Our inventory management guide covers the stock-record side of that job. The enterprise application versus ERP explanation helps frame why purchasing, stock and finance records can be connected without being interchangeable.
3. What you need before you start
Start by defining the account, entity, currency and cut-off date. A statement ending on September 30 should not be compared with an unrestricted ledger report that includes October transactions. If several businesses share a finance system, make sure the report belongs to the right legal entity.
Collect the statement, the relevant ledger activity, the previous completed reconciliation and support for open items. Depending on the account, support may include deposit receipts, invoices, payment confirmations, credit notes, settlement reports or loan schedules. Keep an untouched source copy and work from a controlled reconciliation file.
Check the starting point
The beginning balance should connect to the prior period’s closing position and outstanding items. If it does not, investigate before matching this month’s activity. An old transaction may have been edited, deleted or imported again. A clean current-month report cannot repair a broken opening balance by itself.
Intuit’s first-reconciliation guidance identifies an incorrect opening balance as a possible cause of a first-time mismatch. Its instructions are specific to QuickBooks Online. The wider lesson is to verify the starting date and balance rather than guessing a number that makes the screen look right.
Agree on ownership and evidence
Name the preparer, reviewer and person who can approve corrections. State where supporting documents belong and how unresolved items are escalated. A folder full of screenshots is less useful when nobody can tell which account, period or transaction each screenshot supports.
The document management directory offers tools to consider for storing records. A short month-end meeting agenda can help a small team settle responsibilities and review open exceptions. Choose the workflow before choosing another application.
4. How to reconcile an account step by step
The exact screens vary, but the reasoning stays consistent. Compare like with like, follow the evidence and preserve a record of the result. Do not treat the final balancing calculation as the entire process.
- Confirm the scope. Select the account, period, entity and currency, and verify the opening position.
- Gather complete records. Obtain the statement or supporting schedule and the relevant ledger detail.
- Match transactions. Compare amounts, references, dates and counterparties. Check grouped settlements and split payments carefully.
- List unmatched items. Separate timing differences, missing entries, errors and items requiring investigation.
- Investigate and correct. Use source evidence, obtain approval where required and record supported entries.
- Recalculate the position. Confirm that the adjusted balances agree and that the transaction activity is explained.
- Review and retain. Save the reconciliation, support, corrections and reviewer sign-off, with open items assigned for follow-up.
Matching amounts is only the beginning
Two payments of the same value can belong to different suppliers. A single bank deposit can combine many customer payments after processor fees. A payment date can differ from the accounting date. Use references and supporting records instead of marking the first similar amount as matched.
For grouped settlements, explain the gross amount, deductions and net amount deposited. Do not label every bank deposit as sales revenue. Transfers between accounts, loan proceeds and owner contributions have different accounting meanings. Ask the accountant when the correct treatment is unclear.
Xero’s reconciliation guide outlines record collection, matching and discrepancy checks. Its automation discussion is vendor guidance, not proof that an automatic match is correct. Our application integration guide provides context for keeping identifiers and data flows consistent between systems.
For supplier payments, retain the link to the order, bill and payment without confusing their roles. The purchase order explanation shows why an approved order is not evidence that an invoice was paid or goods arrived.
5. A worked bank reconciliation example
Consider a fictional business at September 30. Its bank statement closes at $8,250. Its cash ledger closes at $8,640. A $600 deposit was recorded in the books but has not appeared on the statement. Payments totaling $250 were recorded but have not cleared. The statement includes a $50 bank fee and $10 interest that are not yet recorded in the books.
Keep the two sides separate. The deposit and outstanding payments explain the bank-side timing differences. The fee and interest require supported book entries because they have not yet been recorded. Here is the comparison:
| Reconciliation side | Starting balance | Supported adjustments | Adjusted balance |
|---|---|---|---|
| Bank statement | $8,250 | Add $600 deposit in transit; subtract $250 outstanding payments | $8,600 |
| Cash ledger | $8,640 | Subtract $50 bank fee; add $10 interest | $8,600 |
On a small screen, swipe the table sideways to read every column.
Check the arithmetic and the evidence
The bank-side calculation is $8,250 + $600 – $250 = $8,600. The book-side calculation is $8,640 – $50 + $10 = $8,600. The totals agree, but that only completes the calculation. The preparer still needs evidence for the deposit, the outstanding payments and the statement entries.
The next-period statement should help confirm that the timing items cleared. If they remain open, investigate rather than carrying them forward forever. A payment that never settles may need a different explanation from one simply awaiting processing.
Nothing in this example says the bank’s actual displayed balance changes to $8,600 at the cut-off. The adjusted bank balance is a reconciliation calculation. Likewise, the business should not claim $8,600 is immediately available to spend without considering the bank’s actual available balance and pending commitments.
For larger systems, Oracle’s ledger reconciliation report documentation also stresses importing transactions and posting journals before comparing reports. A report run before posting can produce a different problem from the timing differences in this bank example.
6. Timing differences versus journal entries
A reconciling item is a reason two records differ. A journal entry changes the accounting records. Confusing the two can create duplicates and make the next month harder to reconcile.
In the example, the $600 deposit and $250 payments were already recorded correctly in the books. They explain the bank-side difference, so they do not need another cash entry merely because the bank has not processed them. Track them on the reconciliation and check subsequent settlement.
The unrecorded $50 fee and $10 interest are different. For this simplified example, recording the fee would debit bank charges expense and credit cash by $50. Recording interest would debit cash and credit interest income by $10. The account names and treatment should follow the business’s chart of accounts and the actual transaction.
Correct errors without inventing an explanation
If a transaction was entered twice, identify the duplicate and correct it through the supported process. If a payment was recorded at the wrong amount, compare it with the original document. If the bank made an error, contact the bank and track its correction instead of booking an unrelated expense to absorb it.
Principles of Accounting’s bank reconciliation chapter distinguishes book-side entries from timing items and describes independent review. It also explains why examining only ending balances can miss activity during the period.
Do not change a prior closed period casually. Corrections can affect reports, tax work and previously reviewed balances. Ask the responsible accountant how the correction should be dated, approved and documented. This guide cannot choose a prior-period accounting treatment for a real business.
The ERP benefits guide explains the value of connected records, while the ERP drawbacks guide covers setup and complexity. Neither eliminates the need to understand what an entry changes.
7. Common reconciliation mistakes and warning signs
A zero difference is useful only when the path to it is supported. Watch for these recurring mistakes:
- Wrong period or account: reports cover different cut-off dates, currencies or entities.
- Duplicate imports: the same bank transaction arrives through a feed and a manual upload.
- Missing charges: fees, interest, refunds or automatic payments were not recorded.
- False matches: equal amounts are linked despite different references or counterparties.
- Unexplained adjustments: an entry clears the difference without identifying the cause.
- Stale open items: old payments or deposits are carried forward without follow-up.
- Changed history: a previously reconciled transaction was edited or deleted.
Give unresolved items an owner
An exception list should show the amount, date, reference, explanation, supporting evidence and next step. Name the person investigating it. Distinguish confirmed timing items from unexplained differences. Calling everything a timing issue does not make it one.
Age matters. A deposit expected to clear tomorrow is different from a deposit outstanding for several months. Review old items against subsequent statements, supplier or customer communications and the accounting records. Do not assume an old payment can simply be cancelled without checking its status and obligations.
The Washington State Auditor’s bank reconciliation guidance emphasizes following up on differences and reviewing activity as well as balances. Its mandatory monthly requirements apply to the governments within that guidance, not automatically to every private business.
Set a frequency appropriate to transaction volume and risk, with period-end completion built into the close. Higher-volume accounts may need more frequent checks. There is no universal time estimate for a reconciliation: ten simple transactions and thousands of processor settlements are different jobs.
Keep permissions limited and retain the review trail. Our cybersecurity and digital transformation guide provides broader access-control context. Financial records should not be shared casually just because someone is helping with a spreadsheet.
8. When software and automation help
Software can import transactions, suggest matches and organize exceptions. It can also repeat a bad rule quickly. Before relying on automation, establish which record owns the account balance, how the feed is checked for completeness and who approves corrections.
A bank feed is useful working data, but verify the reconciliation against the relevant statement and period. A disconnected feed, missing date range or duplicated import can leave a tidy-looking screen with incomplete records. Keep settlement and ledger references so a reviewer can trace a match.
Evaluate the workflow, not the dashboard
Look for transaction history, permissions, exception tracking, document links, export options and support for your accounts and currencies. Ask how the system handles one deposit matched to many invoices, partial payments, bank fees and corrections to reviewed transactions. Test those situations before changing your close process.
Our accounting software comparison and finance app directory are discovery routes, not proof that every listed tool fits your reconciliation needs. The ERP selection guide is more useful when several connected processes need attention than when one small account needs a clearer checklist.
The workflow automation guide explains repeatable tasks, and our AI in finance overview adds context for assisted analysis. Treat suggested matches and explanations as items to verify, not evidence created by the tool itself.
Before giving an assistant access to financial systems, define what it may read, suggest and change. The AI authority-map guide explains why an ability to propose an entry should not quietly become permission to post one.
A short close checklist
Before signing off, check that the account identifier and period are visible on the file. Confirm the opening balance, complete statement coverage and ledger report date. Verify that corrections were actually posted, not left in an unsaved draft. Check that every open item has an explanation, evidence and a follow-up owner. Save the reviewed version so later changes can be distinguished from what was approved.
For a migration, retain the old system reports and the opening-balance mapping. Agree a cut-over date, then check that transactions were neither omitted nor imported twice. A successful software installation is not evidence that the account carried over correctly. The ERP implementation guide gives wider project context; the reconciliation itself needs transaction-level evidence.
Keep the review proportionate. A reviewer should understand significant and unusual items, inspect support and question recurring unexplained adjustments. Merely checking the total or clicking an approval button does not provide that review. If the preparer finds a new issue after sign-off, record the change, notify the reviewer and preserve the earlier version rather than silently replacing it.
9. Reconciliation questions businesses ask
Is reconciliation the same as bookkeeping?
No. Bookkeeping records transactions; reconciliation checks records against relevant support and explains differences. The tasks connect, because reconciliation can reveal entries that need correction. Recording every transaction is not proof the account was reconciled, and reconciling a bank account does not complete all bookkeeping or financial reporting work.
Do the original bank and book balances have to match?
Not necessarily. Legitimate timing differences can make them different at the cut-off. The adjusted balances should agree once supported reconciling items and needed book corrections are considered. Keep the explanation and evidence. Do not force the original totals to match by deleting accurate transactions or recording the same payment twice.
Does a zero difference prove there is no fraud?
No. Matching closing totals can miss unauthorized activity, offsetting errors or incorrect classifications. Review transactions, approvals and unusual movements as well as the ending balance. Reconciliation is one control within a wider process. If activity is suspicious, preserve the evidence and involve the appropriate finance or security contact rather than making unsupported accusations.
Can a small business reconcile in a spreadsheet?
Yes, if the records are complete, the method is clear and versions are controlled. Keep separate bank and book calculations, a matching record and an exception list. Save source statements and correction support. Move to software when volume or complexity makes the manual process unreliable, not simply because a dashboard looks more professional.
Who should prepare and review a reconciliation?
Assign someone who understands the account and can access its supporting records. Independent review helps, especially where the preparer also handles payments. Small teams may need an owner or outside accountant to review higher-risk accounts. Document that review and resolve conflicts in responsibilities rather than treating a signature as a substitute for checking.
What if I cannot explain the difference?
Keep the item open and investigate the starting balance, date filters, duplicates, fees, missing transactions and changed history. Escalate it with the amount and evidence. Do not label the account fully reconciled or create an unsupported balancing entry. A clearly documented unresolved difference is more honest and useful than a zero achieved by guessing.
A useful finish: another person can trace the balance to its support, understand every adjustment and see who owns each remaining exception. That is what makes reconciliation dependable when the original preparer is not available.
