Reconciliation in accounting is one of the most time-consuming and critical steps in the close process. Ask any accountant what eats the most time during close, and reconciliation will be near the top of every list. Not because the concept is difficult. Comparing two sets of records and making sure they agree is simple in theory. What makes reconciliation in accounting painful is everything around it: the exports, the formatting, the line-by-line matching, and the inevitable exceptions that do not quite tie.

Reconciliation in accounting is the process of comparing two independent records of the same account to ensure they agree, investigating any differences, and documenting adjustments required to bring them into alignment.

This guide goes beyond the textbook definition. It covers the types of reconciliation every accounting team should be running, what a reconciliation statement actually looks like with real numbers, and the “almost matching” patterns that quietly consume hours every close cycle, along with the support documentation auditors expect and what changes when month-end hits

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 account reconciliation 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 in accounting goes well beyond cash. It applies to every account where an independent source of truth exists. Bank statements for cash. Sub-ledgers for accounts receivable, accounts payable, and payroll. Counterparty confirmations for intercompany balances. Revenue schedules for deferred revenue. If two systems track the same balance, they need to be reconciled.

This matters because reconciliation is not just a verification step. It is a control activity, and a foundational one. 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. Reconciliation is how you prove they have been.

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 account reconciliation process for each type helps teams prioritize effort and structure their month-end reconciliation checklist around the areas most likely to break.

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

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

Accounts receivable reconciliation

Accounts receivable recon often stumbles on unapplied cash. A customer sends a payment, but the remittance amount doesn't match any single open invoice. Maybe they paid two invoices together minus a discount they took without authorization. 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

Accounts payable is the mirror image, with its own twist. The most common AP recon issue is unrecorded liabilities: goods or services received before month-end but the invoice hasn't 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, which is typically 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 entry in the AP sub-ledger, creating a reconciling difference that needs to be documented and explained. 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. This sub-ledger reconciliation means tying out each component: wages expense per the payroll register to wages expense per the GL, tax liabilities per the payroll system to tax liabilities per the GL, and so on. Timing adds another layer. If payroll runs on a biweekly cycle, the pay periods rarely align cleanly with month-end, creating accrual calculations for partial periods.

Intercompany reconciliation

Intercompany reconciliation is where complexity multiplies. 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 doesn't 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 will need 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 wasn't updated, or a partial delivery triggered recognition that the GL hasn't reflected yet. 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 (an asset was placed in service but not yet added to the sub-ledger), disposals that were physically retired but never removed from the books, and transfers from construction-in-progress (CIP) to a depreciable asset class that change the depreciation run mid-period. Companies running multiple depreciation books for GAAP and tax purposes 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 some reconciliations, especially 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.

Here is a worked bank reconciliation example:

Bank reconciliation statement (March 31)

Both adjusted balances = $284,650 ✓

The critical principle here: 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 (customer’s payment bounced):

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 is reversed: AR goes back up (the customer still owes you), and Cash goes back down (the money was never actually collected).

3. Record interest earned:

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

Textbook reconciliation is clean. Real-world reconciliation in accounting 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 don't quite tie. They almost match, but not exactly, and the accountant has to figure out why.

Here are six patterns that show up constantly in practice:

1. Partial Matches

A vendor invoice for $12,500 was paid in two installments: $7,500 on March 10 and $5,000 on March 22. The AP sub-ledger shows one liability of $12,500 that was cleared. The bank statement shows two separate debits on different dates. Neither bank debit matches the invoice amount one-to-one. Someone has to manually trace both payments back to the original invoice, confirm the total agrees, and document the match. 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 $38,000 for shared IT services. Rather than two separate intercompany payments, they settle with a single net transfer of $7,000 from A to B. This is standard intercompany netting. The problem arises when the two sides record it differently. Subsidiary A records both transactions at gross: a $45,000 payable to B and a $38,000 receivable from B. Subsidiary B, however, records only the net settlement: a single $7,000 receivable from A. When you run the intercompany reconciliation and compare A's payable to B ($45,000) against B's receivable from A ($7,000), the recon shows a $38,000 difference.

That difference is not a real economic gap. Both entities agree on the net position. The discrepancy is purely a recording methodology mismatch. The fix is not a correcting entry but getting both entities to agree on a consistent method for recording the settlement, which often means coordinating across different accounting teams, different ERP instances, and sometimes different time zones.

3. FX Rate Movements

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

Journal entry for the UK subsidiary’s month-end FX remeasurement:

The US parent’s receivable remains $100,000 in USD. The UK subsidiary’s payable is now £81,000 in GBP. Both sides are correct under their respective reporting currencies, but the intercompany reconciliation will show a discrepancy in reporting currency until the FX adjustment is booked and the elimination entry at consolidation accounts for the translation difference.

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

4. Timing Differences

Payroll was processed on March 29, a Friday. The GL recorded the wage expense, tax liabilities, and net pay liability on March 29. But the bank debit for the net payroll amount did not clear until April 1, the following Monday. The GL shows the cash outflow in March (because the payment was initiated). The bank statement shows it in April (because the funds did not leave the account until Monday). The bank reconciliation is out by the full net payroll amount, and it will stay that way until someone identifies the item as a timing difference and marks it as an outstanding disbursement. For a company running biweekly payroll for 500 employees, a single payroll run can be $800,000 or more. That is a large outstanding item to track.

5. Batched Payments

A company pays 47 vendor invoices in a single ACH batch totaling $283,400. The bank statement shows one lump debit for $283,400. The AP sub-ledger shows 47 individual credits, each applied against a different vendor and invoice. Matching this one-to-many transaction without automation means pulling the ACH batch detail, tying each invoice to its share of the total, confirming the individual amounts sum to $283,400, and documenting the match. If even one invoice was pulled from the batch or the amount was adjusted after the batch was created, the total won't 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 not an operational transaction. It is a manual journal entry that someone posted directly to the AP control account to record a month-end accrual, bypassing the AP sub-ledger entirely. The sub-ledger has no record of it because the entry never went through the normal invoice workflow.

This is one of the most frustrating "almost matching" scenarios because 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. Manual top-side entries in control accounts are sometimes necessary (a quick accrual for goods received but not yet invoiced, for example), but when they are buried inside the control account without clear documentation, they make the GL-to-subledger reconciliation significantly harder to interpret. The reviewer cannot tell what is system-driven and what is manual without investigating each entry individually. A controller reviewing this file will usually care less that the balance ties than why it needed a manual workaround in the first place.

These "almost matching" scenarios are where the real time goes during close. They are not conceptually hard. They are operationally tedious, especially when performed manually across dozens of accounts and entities every month.

Resolving these exceptions is one half of the job. The other half is proving you resolved them correctly.

Standard support documentation by reconciliation type

Auditors, reviewers, and SOX testing teams expect specific support for each type of reconciliation in accounting. A reconciliation that says "balance agrees" without evidence is not a completed reconciliation. It is an assertion. And in practice, many reconciliation files do not fail because the number is wrong. They fail because the support was assembled backward from the answer, reverse-engineered to justify a conclusion rather than built to prove one. Incomplete documentation is one of the most common reasons reconciliations fail review and get sent back for rework.

Use this as a month-end reconciliation checklist. Common supporting documentation by reconciliation type includes:

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 (wages, taxes, benefits, employer contributions)

• 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 in the period

• Revenue sub-ledger or system report, where one exists

• Manual journal entry support where relevant

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 for the period with capitalization or retirement approvals

• Depreciation run detail showing method, useful life, and current-period expense by asset or class

• CIP transfer documentation for any 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. If any of those pieces are missing, the reconciliation is incomplete. A useful standard: 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 with reconciliation in accounting is treating it 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 and a compressed close. 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.

The principle is simple: anything that can be reconciled before the close window opens, should be. A practical rule: the harder an account is to reconstruct after the fact, the more discipline it needs during the month, even if formal sign-off only happens at close. In practice, that means high-volume cash and bank accounts get reviewed during the month, while the full balance sheet reconciliation and sign-off happens at close.

Reconciliation during close is not the same as reconciliation during the month. Several things happen simultaneously that make the process harder.

• Cutoff enforcement becomes critical. Transactions must land in the correct period. A March 31 vendor invoice recorded on April 1 distorts both months, understating March expenses and overstating April's. Reconciliation is the control that catches cutoff failures, because the sub-ledger will show the liability while the GL may not, or vice versa.

• Accrual entries create reconciling items that did not exist during the month. Expenses incurred but not yet invoiced (legal fees, utilities, contractor hours) need to be estimated and recorded. Each accrual changes account balances that are being simultaneously reconciled.

• Reclassification entries correct items posted to the wrong account, entity, or cost center during the month. 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. These eliminations are required for consolidated financial statements and are a direct output of the reconciliation process.

• Stale reconciling items deserve special attention at close. The most dangerous reconciliation is often not the one with the biggest difference. It is the one everyone has stopped questioning. A new timing difference from the last week of the month is normal and expected. A reconciling item that has been carried forward for 60 or 90 days with no clear owner, no supporting evidence, and no path to resolution is a different kind of problem. At that point, the risk is not just that the account doesn't tie neatly. The risk is that the team has normalized uncertainty inside a live balance. In many close processes, the oldest reconciling item is not the largest dollar amount on the page. It is the clearest signal that the account is being rolled forward on habit rather than on evidence.

And perhaps most importantly, reconciliation itself can surface adjusting journal entries: bank fees, interest income, NSF reversals, FX remeasurements, reclassifications. In some companies, those items are identified and posted before financial statements are finalized. In others, the formal reconciliation and sign-off happen after the books are substantially closed. Either way, reconciliation needs to fit the close calendar and review process used by the company, with enough time for any resulting entries to be reviewed, approved, and reflected in reporting.

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 around it: 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.

A single bank reconciliation for a high-volume account can take hours using this process. Multiply that by every balance sheet account, every entity, every month, and the account reconciliation process becomes one of the largest time commitments in the entire close cycle.

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, even across millions of transactions a month, accountants open to matched items already grouped and exceptions surfaced with the detail needed to investigate. They review the deltas. They resolve the genuine exceptions. 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 line-by-line matching that normally consumes hours during close is already done.

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. That is the standard worth building toward, whether the work is done in a spreadsheet or on a platform.

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

1. 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.

2. What happens if a reconciliation shows a difference?

The difference must be investigated. Common causes include timing items (which resolve on their own when the transaction clears), errors (which require correcting entries), unrecorded transactions (which require 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.

3. 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. In practice, it is a requirement for any company that needs accurate, auditable financial statements.

4. 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 bar for documentation 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, for an auditor to test, and for the financial statements to be defensible. That shift from "I know why this is off" to "I can prove why this is off" is what makes month-end reconciliation harder than mid-month reconciliation, even when the comparison itself is identical.

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

Start with the 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.