What transaction reconciliation means
Transaction reconciliation confirms that each line in one record has its counterpart in another record of the same activity: every sale against its settlement, every payment against its bank movement, every invoice against its receipt. Finance teams also call it line reconciliation or line-by-line reconciliation, because the line, not the balance, is the unit that has to agree. It is a form of reconciliation defined by its level of detail, and it supplies the evidence behind the balance-level checks done at close.
Transaction matching is the step inside it that pairs lines under rules. Reconciliation is the wider control: it also explains the lines that did not pair, assigns an owner and records the resolution. Outside finance, “line reconciliation” has an unrelated meaning in healthcare, where clinicians check medication or IV lines; this entry covers the accounting and payments sense.
Why a matching total does not prove the detail
A total is a sum, and a sum can hide two errors that cancel. When one line is counted twice and another line of the same amount is left out, the duplicate adds what the omission removes, so the total still agrees with the other record. A control that reads the total passes, and a control that reads the lines finds both. Reading at line level also places the fix, because a difference found on a line arrives with its reference, its date and its amount, while a difference found on a total arrives without a location.
How to reconcile transactions
- Fix the two populations. Decide which two records enter the comparison and the period they cover, so both sides describe the same activity at the same cut-off.
- Prepare both sides. Normalize dates, formats and references, so a line on one side can be paired with a line on the other.
- Pair the lines. One line against one, one against several, or several against several. The pairing and its tolerances run on the rules the team configures.
- Route what does not pair. A line with no counterpart becomes an exception with a cause and an owner, and it stays visible until it is explained.
- Resolve and record. Each exception closes with its explanation: a timing item carried forward, a correcting entry approved or more data requested from the source.
Transaction reconciliation example: the total agrees and the detail does not
The figures are illustrative and stated in US dollars. Calderway Trading closes March and reconciles its sales ledger against the settlement report for the same period. The report lists five movements, of 5,400, 3,800, 2,200, 1,200 and 1,200, so it totals USD 13,800.
The ledger also totals USD 13,800, and its detail is wrong. One of the two movements of 1,200 was posted twice, and the other was left out. On the total the two cancel: 1,200 – 1,200 = 0. The two sides therefore agree with each other: 13,800 – 13,800 = 0.
Correcting it does not move the total. Reverse the duplicate and post the missing movement, and the ledger reads 13,800 – 1,200 + 1,200 = 13,800, because what leaves as a duplicate returns as a real movement. The two records then agree line by line, and the control that matters verifies lines rather than totals: a total that agrees would have passed over both errors.
Types of transaction reconciliation and the documents behind them
The object is two records that describe the same activity, and the pairing takes three shapes: one line against one, one line against several, and several against several. The document is not fixed by the name of the term; each flow brings the records that support it.
| Flow | Records compared | Typical match shape |
|---|---|---|
| Bank | Cash ledger lines against the bank statement | One to one |
| Payments and settlements | Internal sales against processor or acquirer settlement reports, then against the bank deposit | Many to one |
| Receivables | Customer payments against open invoices | One to many |
| Payables | Supplier invoices against purchase orders and receipts | One to one or one to many |
| Intercompany | One entity’s entries against the mirror entries of the other | One to one |
Some of these flows have their own entries: bank reconciliation agrees cash against the statement, invoice matching is the payables check, and intercompany reconciliation confirms reciprocal balances between group entities. Transaction reconciliation is the level of comparison they share.
When the comparison runs
The comparison can run daily, on a schedule, when new data arrives or at period close. Its cadence follows transaction volume, risk and data availability. A reporting cut-off still matters: both populations must cover comparable activity, and a line present on only one side needs an explanation, whether the control runs during the month or at its end. Payment-heavy businesses tend to run it most often, as in PSP settlement reconciliation, merchant reconciliation and payment reconciliation for iGaming.
What happens to a line that does not match
An unmatched line is the finding, and its cause decides what follows. A timing difference is documented and carried forward with the date it is expected to clear. A real difference, such as a duplicate, a short settlement or a refund recorded on one side only, is investigated. The classification is a judgment the team makes and records. Lines that pair under the rules with no manual touch are sometimes described as straight-through reconciliation; the share that does not is where the team spends its time.
How Simetrik supports transaction reconciliation
Transaction reconciliation is the core of what Simetrik does. Simetrik, an AI-native reconciliation and financial control platform, controls transaction and operational data from banks, processors, internal systems and third parties before it feeds the ERP. Catching a one-sided refund, a settlement that arrives short because of fees or a chargeback that reverses a sale at line level is faster and easier to trace than correcting the balance later.
Simetrik prepares source records, combining sources with different structures into one dataset and enriching lines with lookups, then applies configured matching rules, tolerances and chained reconciliations. The engine runs one-to-one, one-to-many and many-to-many sequences and is deterministic: the same inputs and rules produce the same result, with a trace from the raw record to the final result. Simetrik’s AI suggests matching rules based on good practices and historical patterns, and the team approves them before they run.
In the Operation Center, teams can assign and track pending items, act on them individually or in bulk, retain supporting evidence and record their resolution. The objective is to explain the unmatched line, including whether further data or an approved adjustment is needed.