Reconciliations in accounting: the definitive guide

If you have ever spent the last two days of close chasing a $400 difference across three systems, you already know what reconciliation costs when it is not done well. This guide covers everything: what reconciliation is, how to do it step by step, why it matters, how often to run it, and where the process breaks down at scale.

What is reconciliation in accounting?

Reconciliation is the process of comparing two independent sets of records for the same account or balance and confirming they agree. In practice, accountants often call this a "tie-out": pulling the GL balance, pulling the sub-ledger or external source, and verifying the two numbers match. When they don't, the process continues: identify the discrepancy, investigate the root cause, record any necessary adjusting entries, and document the results.

Most people think of bank reconciliation when they hear the word, but reconciliation goes well beyond cash. It applies to every account where an independent source of truth exists: bank statements for cash, sub-ledgers for AR, AP, and payroll, counterparty confirmations for intercompany balances, revenue schedules for deferred revenue. If two systems track the same balance, they need to be reconciled.

Reconciliation is not just a verification step. It is a control activity. Under SOX Section 404, management must assess the effectiveness of internal controls over financial reporting. PCAOB AS 2201 goes further: a material weakness can exist even when the financial statements are not materially misstated. No single ASC standard mandates reconciliation by name, but you cannot reliably apply ASC 310, ASC 606, ASC 830, or any other reporting standard if the balances underneath have not been verified.

How to perform reconciliations in accounting

The process is consistent regardless of account type. What changes is the source data and the nature of the reconciling items. Here is the standard sequence from start to sign-off.

1. Gather source records. Pull the GL account balance and the independent source: bank statement, sub-ledger report, payroll register, or counterparty confirmation. Both records must reflect the same period-end date. A cutoff mismatch at this stage creates false discrepancies throughout the rest of the process.

2. Compare opening balances. Confirm the opening balance on the current reconciliation agrees to the closing balance from the prior period. If it does not, the prior reconciliation was either incomplete or a prior-period entry was posted after sign-off. Resolve this before proceeding.

3. Match transactions line by line. Work through each transaction on both sides. Exact matches on amount, date, and reference clear first. Partial matches, batched payments, and timing items require more investigation. Flag anything unmatched on either side.

4. Classify unmatched items. For every unmatched item, determine the cause. Timing differences (outstanding checks, deposits in transit) are expected and will resolve next period. Errors require correcting entries. Unrecorded transactions require adjusting entries.

5. Post adjusting journal entries. Record any entries needed to correct the books: bank fees, NSF reversals, interest income, accruals, FX remeasurements. Each entry needs a clear description and supporting documentation before posting.

6. Confirm adjusted balances agree. After entries are posted, rerun the comparison. Both sides should agree, or remaining differences should be documented timing items with a clear expected resolution date.

7. Assemble support documentation. Attach source records, the reconciliation workbook, journal entry backup, and exception explanations. The file should be self-explanatory: a reviewer should be able to follow the logic without asking the preparer a single question.

8. Submit for review and sign-off. Route the completed reconciliation to the appropriate reviewer. Under SOX, segregation of duties requires the preparer and reviewer to be different individuals. Track open items with aging so stale exceptions surface at the next close rather than getting carried forward silently.

Why reconciliations in accounting matter

Reconciliation is often framed as a compliance requirement. It is that, but the operational benefits are just as significant.

• Balance sheet accuracy. Every unreconciled account is an unverified balance. Errors compound across periods when not caught early. An NSF check that is not reversed leaves cash overstated and AR understated until someone catches it.

• Fraud detection. Reconciliation is one of the primary controls for detecting unauthorized transactions, duplicate payments, and fictitious entries. A vendor payment on the bank statement with no corresponding AP invoice is exactly the kind of anomaly reconciliation surfaces.

• Audit readiness. Auditors test reconciliations as part of their assessment of internal controls. A file that shows two balances, every reconciling item, supporting documentation, and a reviewer sign-off is audit-ready. A spreadsheet with a note that says "agrees per review" is not.

• Faster close. Teams that reconcile continuously during the month walk into close with most accounts already prepared. Spreading the work reduces compression and the errors that come with it.

• Better forecasting. Reconciled balances are reliable inputs. Cash flow forecasts built on unreconciled bank balances, or revenue projections built on unreconciled deferred revenue schedules, carry embedded errors that compound downstream.

Types of reconciliation (and what makes each one different)

Not all reconciliations are created equal. A bank recon for a single operating account is a different exercise from reconciling intercompany balances across 15 entities in three currencies. Understanding the process for each type helps teams prioritize effort and structure their month-end checklist around the areas most likely to break.

The table below breaks down the seven most common types, what you are comparing, what typically goes wrong, and how often you should be doing it.

How often should reconciliations in accounting be performed?

Cadence should be driven by three factors: transaction volume, account risk, and materiality. A high-volume cash account that processes hundreds of transactions daily needs different treatment than a prepaid expense account that moves once a quarter.

The practical rule: if an account can develop a material error between reconciliations that you would not catch any other way, the cadence is too infrequent. The goal is not to reconcile everything constantly. It is to match frequency to the risk profile of each account.

The types are straightforward. What is less obvious is why each one breaks in different ways.

Accounts receivable reconciliation

AR recon often stumbles on unapplied cash. A customer sends a payment, but the remittance amount does not match any single open invoice. The cash hits the bank, the deposit is recorded, but the AR sub-ledger still shows the invoices as outstanding because no one has applied the payment. Until someone manually matches the payment to the right invoices, the GL and sub-ledger will disagree.

Accounts payable reconciliation

The most common AP recon issue is unrecorded liabilities: goods or services received before month-end but the invoice has not arrived yet. The expense belongs in the current period, but without the invoice, the AP sub-ledger has no record of the obligation. The fix is an accrual posted as a journal entry to the GL rather than through the normal AP invoice workflow. This means the accrual increases the GL balance without a corresponding sub-ledger entry, creating a reconciling difference that needs to be documented. Miss the accrual entirely, and you understate both expenses and liabilities for the period.

Payroll reconciliation

Payroll recon is deceptively complex because the payroll system tracks gross pay, tax withholdings, employer taxes, benefit deductions, and net pay as separate line items, while the GL may aggregate them differently. Timing adds another layer. If payroll runs biweekly, the pay periods rarely align cleanly with month-end, creating accrual calculations for partial periods.

Intercompany reconciliation

Two entities within the same corporate group should show mirror-image balances: one records a receivable, the other records a payable for the same amount. In practice, mismatches are constant. The most common is one entity booking an invoice in March while the counterparty does not record it until April. The transaction is real, the amounts are correct, but the timing is off by one period and the consolidated recon shows a discrepancy that needs to be investigated and explained.

Deferred revenue reconciliation

Deferred revenue recon requires matching the revenue sub-ledger or schedule to the GL deferred revenue balance. Discrepancies typically arise from recognition timing: a contract modification was recorded in the billing system but the revenue schedule was not updated, or a partial delivery triggered recognition the GL has not yet reflected. For companies with significant subscription or contract revenue under ASC 606, this is one of the highest-risk reconciliations because errors directly affect recognized revenue.

Fixed assets reconciliation

Fixed assets reconciliation means tying the asset sub-ledger (gross cost, accumulated depreciation, and net book value) to the corresponding GL accounts. The most common issues are late capitalizations, disposals that were physically retired but never removed from the books, and CIP transfers that change the depreciation run mid-period. Companies running multiple depreciation books for GAAP and tax are effectively reconciling two parallel schedules for the same set of assets.

What a reconciliation statement actually looks like

A reconciliation statement is the formal output document that shows what was compared, the reconciling items identified, and the conclusion reached. In bank reconciliations, it starts with unadjusted balances on both sides and ends with matching adjusted balances. In others, it ties a sub-ledger or supporting report to a GL balance and explains the remaining differences.

Bank reconciliation statement (March 31)

Both adjusted balances = $284,650 ✓

Items on the book side require adjusting journal entries because they represent transactions the company has not yet recorded. Items on the bank side do not require entries because the company has already recorded them; they simply have not cleared the bank yet.

Journal entries resulting from this reconciliation

1. Record bank service fees:

2. Reverse the NSF check:

The customer's original payment was recorded as a debit to Cash and a credit to AR. When the bank returns the check as non-sufficient funds, the entry reverses: AR goes back up, and Cash goes back down.

3. Record interest earned:

The "almost matching" problem: where reconciliation actually eats hours

Textbook reconciliation is clean. Real-world reconciliation almost never is. The scenarios that consume the most time are not the ones where transactions are missing entirely. They are the ones where transactions are present on both sides but do not quite tie.

Common causes of reconciliation discrepancies

The six patterns below show how these causes play out in practice.

1. Partial matches

A vendor invoice for 12,500 was paid in two installments: 5,000 on March 22. The AP sub-ledger shows one liability of 12,500 cleared. The bank statement shows two separate debits on different dates. Neither bank debit matches the invoice amount one-to-one. With a handful of split payments, this is manageable. With dozens across multiple vendors, it becomes a significant time sink.

2. Intercompany netting

Subsidiary A owes Subsidiary B 45,000 for management fees. Subsidiary B owes Subsidiary A 7,000. Subsidiary A records both transactions at gross; Subsidiary B records only the net settlement. When you compare A's payable to B (7,000), the recon shows a 38,000 difference that is not a real economic gap. The fix is not a correcting entry but getting both entities to agree on a consistent recording method, which often means coordinating across different accounting teams, ERP instances, and time zones.

3. FX rate movements

A US parent invoices its UK subsidiary $100,000 for intercompany services on March 15. The UK subsidiary records the payable at £0.79 per USD, creating a £79,000 liability. By March 31, the rate has moved to £0.81. Under ASC 830-10-45, the subsidiary must remeasure the payable at period-end rate. The liability is now £81,000.

This is not an error. It is standard FX accounting. But a reconciler who does not understand remeasurement will spend an hour investigating a variance that is completely expected.

4. Timing differences

Payroll was processed on March 29. The GL recorded the wage expense and net pay liability on March 29. The bank debit did not clear until April 1. The bank reconciliation is out by the full net payroll amount until someone identifies it as an outstanding disbursement. For a company running biweekly payroll for 500 employees, a single payroll run can be $800,000 or more.

5. Batched payments

A company pays 47 vendor invoices in a single ACH batch totaling $283,400. The bank statement shows one lump debit. The AP sub-ledger shows 47 individual credits. Matching this one-to-many transaction means pulling the ACH batch detail, tying each invoice to its share of the total, and confirming the amounts sum correctly. If even one invoice was adjusted after the batch was created, the total will not agree and the investigation begins.

6. Manual journal entries in control accounts

The AP sub-ledger shows 640,000. The AP control account in the GL shows $655,000. The 15,000 difference is a manual journal entry posted directly to the AP control account to record a month-end accrual, bypassing the sub-ledger entirely. The reconciler is not looking for a missing transaction. They are looking for an entry that exists in one system but was never supposed to flow through the other. A controller reviewing this file will usually care less that the balance ties than why it needed a manual workaround in the first place.

Standard support documentation by reconciliation type

Auditors, reviewers, and SOX testing teams expect specific support for each reconciliation type. A reconciliation that says "balance agrees" without evidence is not a completed reconciliation. It is an assertion. Incomplete documentation is one of the most common reasons reconciliations fail review and get sent back for rework.

Bank/Cash:

• Bank statement (official PDF from the institution, not a screenshot)

• Outstanding check list with check numbers, dates, and amounts

• Deposits in transit detail with dates and supporting deposit slips

• Journal entry backup for any adjusting entries booked during reconciliation

Accounts Receivable:

• Aged AR trial balance as of period end

• GL-to-subledger reconciliation

• Unapplied cash listing with aging detail

• Bad debt and write-off approvals for the period

• Credit memo detail with approval documentation

Accounts Payable:

• Aged AP trial balance as of period end

• GL-to-subledger reconciliation

• Unvouchered receipts or accrual listing

• Vendor statement comparisons for material vendors

Payroll:

• Payroll register for each pay cycle in the period

• GL-to-payroll-system reconciliation by account

• Tax deposit confirmations (Form 941, state withholding)

• Benefit remittance confirmations

Intercompany:

• Confirmation of balances between entities (both sides must agree or differences must be explained)

• Elimination entries prepared for consolidation

• FX rate documentation (rate used, rate source, rate date)

• Netting agreement detail if applicable

Deferred Revenue:

• Revenue waterfall or amortization schedule by contract or customer cohort

• Contract or billing support for balances added during the period

• Contract modification documentation for any material changes

• Revenue sub-ledger or system report where one exists

Fixed Assets:

• Fixed asset sub-ledger (gross cost, accumulated depreciation, net book value) as of period end

• GL-to-subledger reconciliation for each fixed asset GL account

• Additions and disposals report with capitalization or retirement approvals

• Depreciation run detail showing method, useful life, and current-period expense

• CIP transfer documentation for assets placed in service during the period

The pattern across all types is the same: show the two balances, show every reconciling item, show the support for each item, and show who prepared and reviewed the work. A reconciliation is review-ready only when the reviewer does not need the preparer in the room to understand what happened.

What changes at month-end, and why reconciliation should not wait for it

The biggest mistake accounting teams make is treating reconciliation as a purely month-end activity. Teams that batch all reconciliation work into days 1 through 5 of the new month are guaranteeing late nights. Teams that spread the work across the month and walk into close with 80% of reconciliations already prepared are the ones closing in three to four days.

Anything that can be reconciled before the close window opens, should be. High-volume cash and bank accounts get reviewed during the month; the full balance sheet reconciliation and sign-off happens at close.

Several things happen simultaneously at month-end that make the process harder:

• Cutoff enforcement becomes critical. A March 31 vendor invoice recorded on April 1 distorts both months. Reconciliation is the control that catches cutoff failures.

• Accrual entries create reconciling items that did not exist during the month. Each accrual changes account balances that are being simultaneously reconciled.

• Reclassification entries correct items posted to the wrong account or entity. Each reclass changes the trial balance and may affect other reconciliations in progress.

• Elimination entries for intercompany transactions must be prepared after intercompany reconciliation confirms both sides agree.

• Stale reconciling items deserve special attention at close. A new timing difference from the last week of the month is normal. A reconciling item carried forward for 60 or 90 days with no clear owner and no path to resolution is a different problem. In many close processes, the oldest reconciling item is the clearest signal that the account is being rolled forward on habit rather than evidence.

Manual vs automated reconciliations in accounting

Manual reconciliation works at low volume. It breaks at scale. The table below shows where the two approaches diverge across the criteria that matter most during close.

For a team reconciling 10 accounts across one entity, manual is manageable. For a team reconciling 150 accounts across 20 entities with millions of transactions per month, manual is the bottleneck.

Where teams get stuck, and what a better workflow looks like

Teams usually do not get stuck on the idea of reconciliation. They get stuck in the handoffs: exports from multiple systems, manual matching in spreadsheet templates, missing support, slow responses from account owners, and reviewer questions that surface late in the close window.

The teams that close faster tend to have one thing in common: the matching and preparation work is automated before the review begins.

This is where platforms like Maxima come in. Workbooks from prior periods roll forward automatically. Reconciling items carry forward with aging, so stale exceptions surface rather than getting buried. The platform pulls data from ERPs, bank feeds, and other financial systems and matches transactions across both sides using layered rules.

High-confidence matches run first, like exact lookups on invoice numbers or payment references. Then progressively broader rules, including AI-suggested matching logic based on data patterns, handle what remains: amount matching with tolerance, date-based lookups, and many-to-many grouping for the patterns that take the longest to resolve manually.

Once the recon completes, accountants open to matched items already grouped and exceptions surfaced with the detail needed to investigate. The audit trail builds as work is performed, and controls flag when balances shift in the GL or workbooks are modified after sign-off.

The goal is not to remove accountants from reconciliation. It is to remove the manual assembly work so accountants spend their time where it matters: investigating real exceptions, explaining real variances, and making real decisions about the numbers.

A reconciliation is not finished when the preparer feels comfortable. It is finished when a reviewer can open the file, follow the logic, inspect the support, and arrive at the same conclusion without asking a single question.

Reconciliation should not be the reason your close runs late. See how Maxima automates tie-outs, transaction matching, and close workflows for accounting teams.

Frequently asked questions

What is the difference between reconciliation and matching?

Matching is comparing two records to see if they agree. Reconciliation is the full process: matching, identifying and investigating discrepancies, making adjusting entries, and documenting the results. Matching is one step within reconciliation, not a substitute for it.

What happens if a reconciliation shows a difference?

The difference must be investigated. Common causes include timing items, errors requiring correcting entries, unrecorded transactions requiring adjusting entries, classification issues, and manual entries that bypassed the sub-ledger. All differences should be documented with an explanation, regardless of whether they require a journal entry.

Is account reconciliation required by GAAP?

There is no single ASC standard that mandates reconciliation as a procedure. However, the COSO Internal Control Framework, which underpins SOX Section 404 compliance, identifies reconciliation as a core control activity. PCAOB AS 2201 further establishes that auditors must evaluate reconciliation controls as part of their assessment of internal control over financial reporting.

Why do reconciliations feel harder at month-end?

During the month, differences can sit quietly inside operational systems. At close, they surface all at once, and the documentation bar changes. It is no longer enough for the team to internally understand a difference. The balance has to be documented well enough for a reviewer to sign off and for an auditor to test. That shift from "I know why this is off" to "I can prove why this is off" is what makes month-end reconciliation harder, even when the comparison itself is identical.

What is the best way to structure a month-end reconciliation checklist?

Start with accounts that can be reconciled before close begins: high-volume bank accounts, payroll, and any sub-ledger reconciliation with predictable patterns. Reserve the close window for balance sheet reconciliation that depends on final accruals, reclassifications, and intercompany eliminations. Prioritize accounts by risk and materiality, not alphabetical order, and track aging on every open reconciling item so stale exceptions are visible to reviewers.