What reconciliation means in accounting
In accounting, to reconcile is to check that two records of the same activity agree and to explain every amount that keeps them apart. The two records are usually produced independently: a cash ledger and a bank statement, a customer balance and the invoices behind it, an internal sales report and a processor’s settlement file. When both describe the same activity, any gap between them is information about a missing entry, an error or a timing item.
A reconciliation ends with a status, not only with a total. Each item is matched, explained by a supported adjustment, or left open with an owner and a next step. That is why accountants talk about an account being reconciled: the balance has been tested against another source, and the remaining differences are known.
Why reconciliation matters
A balance can look reasonable while still containing duplicate entries, omitted transactions, posting errors, or activity recorded in different periods. Reconciliation tests a record against another source that represents the same activity. That comparison helps finance and operations teams find discrepancies before those differences flow into reporting, settlement, cash management, or the accounting close.
A completed reconciliation also creates a clear account of what matched, what changed, and what still needs attention. It does not prove that every underlying transaction is valid. The strength of the control depends on the records compared, the matching criteria, the review performed, and the treatment of exceptions.
How to reconcile: the reconciliation process
The reconciliation process runs in four steps, whatever the account or the pair of records. Some guides split it into five or seven stages, usually by separating the review and sign-off, but the sequence is the same.
- Define the scope. Choose the account, process, entity, period, and two records that should represent the same activity. Examples include a general ledger account and a subledger, an internal cash record and a bank statement, or sales records and payment settlements.
- Prepare the records. Bring both records into a comparable form. Check that dates, amounts, currencies, identifiers, signs, and period boundaries are interpreted consistently before matching begins.
- Compare and investigate. Match corresponding items and isolate differences. Determine whether each difference comes from timing, an unrecorded item, a duplicate, a classification problem, a data issue, or another explainable cause.
- Adjust, document, and review. Correct supported recording errors, record valid adjustments, document outstanding items, and compare the updated balances again. Unresolved exceptions remain visible for follow-up and review.
Reconciliation example: a bank account at month end
Suppose a company’s cash ledger shows $100,000, while its bank statement shows $101,250. The team finds a $1,500 deposit recorded in the ledger that has not yet reached the bank, $3,000 in issued checks that have not yet cleared, and a $250 bank fee missing from the ledger.
| Bank side | Amount | Ledger side | Amount |
|---|---|---|---|
| Balance per bank statement | $101,250 | Balance per cash ledger | $100,000 |
| Add: deposit in transit | $1,500 | Less: bank fee not yet recorded | $250 |
| Less: checks not yet cleared | $3,000 | ||
| Adjusted bank balance | $99,750 | Adjusted ledger balance | $99,750 |
The adjusted bank balance is $101,250 + $1,500 – $3,000 = $99,750. After recording the bank fee, the adjusted ledger balance is $100,000 – $250 = $99,750. The adjusted balances agree, while the deposit and checks remain documented as timing items until they clear. Only the fee needed an entry; the timing items correct themselves once the bank processes them.
This is the most familiar case, bank reconciliation, but the same logic applies to any pair of records. The blog collects account reconciliation examples by account type.
Types of reconciliation
There is no single official list of reconciliation types. A practical way to group them is by what the control checks, because each layer answers a different question and relies on different evidence.
| Layer | Question it answers | Example |
|---|---|---|
| Operational reconciliation | Do internal records and a provider’s records reflect the same operations? | Internal sales compared with the acquirer’s transaction report. |
| Financial reconciliation | Are the amounts and economic terms of those operations consistent? | Fees, withholdings, refunds or settlements checked against agreed rules. |
| Accounting reconciliation | Is the recorded balance supported by evidence for the period? | A ledger balance compared with its support, with each difference explained and reviewed. |
The operational layer works record by record and is often called transaction reconciliation. The broader finance discipline that spans these comparisons is described under financial reconciliation. Grouped by the records compared, the common types are bank, accounts receivable, accounts payable, intercompany, inventory, payment and settlement reconciliations, and general ledger reconciliation of subledgers against the ledger. In each case, the records must describe comparable activity and use a clearly defined scope.
Common causes of reconciliation differences
A reconciliation difference is the amount by which two records of the same activity disagree before it is explained. Most differences come from a short list of causes:
- Timing differences, such as a payment recorded internally before it settles externally.
- Missing or duplicated transactions in one record.
- Incorrect amounts, dates, signs, currencies, or account classifications.
- Fees, credits, reversals, or adjustments recorded by only one party.
- Different identifiers or data formats that prevent corresponding items from matching.
Reconciled, unreconciled and pending items
Each item in a reconciliation carries a status, and systems label them in slightly different ways. A reconciled item has matched its counterpart, or its difference has been explained and supported. An unreconciled item has no counterpart yet, or its difference has no explanation, so it stays open as an exception. A pending item has been received but not yet matched, often because the other record arrives later, as with a settlement that lands after the cut-off. Pending is usually a timing status; it becomes a real exception only if the counterpart never arrives.
Manual and automated reconciliation
Manual reconciliation may be practical when the data set is small and the comparison is simple. As volume, sources, entities, or rule complexity increase, software can apply configured matching logic consistently and separate matched items from exceptions. Human review is still needed to assess unusual differences, support adjustments, and decide how unresolved items should be handled. Automation does not remove the need for sound rules, complete records, and accountable review.
How Simetrik supports reconciliation
Simetrik, an AI-native financial control platform, runs reconciliation as a configured control. Its matching engine is deterministic by design: with the same inputs and the same rules, it produces the same result, traceable from the raw record to the final status. A control that changes its answer is not a control, so in Simetrik AI works around that core and never decides whether an item is reconciled. The approach is described on the reconciliation software page.
Teams define the rules: one-to-one, one-to-many or many-to-many sequences, and the tolerance a difference may have before it counts as an exception. Simetrik applies those configurable matching rules and tolerances, closes what matches with its trace and surfaces unmatched records or exceptions for review. Its main focus is the operational and financial layers, on transaction and operational data from banks, processors and internal systems before it feeds the ledger.
Sources rarely share a structure, so data preparation comes first: Simetrik’s AI suggests how to map equivalent columns between them and proposes matching rules based on good practice and historical patterns. The team reviews and approves those suggestions before they run, and keeps the responsibility for the accounting decisions behind each adjustment.