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.
Simetrik supports reconciliation by applying configured transaction matching rules and surfacing unmatched records or exceptions for review. Its deterministic control core produces repeatable results from the same inputs and rules, while traceability around configured controls and actions supports the investigation of exceptions.
How reconciliation works
- 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.
Bank reconciliation example
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. 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.
What can be reconciled?
Reconciliation is broader than bank reconciliation. Businesses may reconcile accounts receivable to customer activity, accounts payable to vendor records, subledgers to the general ledger, intercompany balances between entities, inventory records to physical or operational counts, and payment or settlement data across systems. In each case, the records must describe comparable activity and use a clearly defined scope.
Common causes of reconciliation differences
- 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.
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.