A payment can appear successful in one system while remaining missing, duplicated or incomplete in another. Reconciliation is the control process that compares those records and explains the difference.
One payment creates several records
A payment may produce a customer instruction, a network message, an authorization or status response, a settlement entry and postings to customer and general-ledger accounts. Connected systems may record those events at different times.
Reconciliation brings the relevant records together so the bank can confirm that what it instructed, processed, settled and posted is consistent.
Systems match common details
Automated routines compare identifiers, amounts, dates, currencies, counterparties and payment statuses. A complete match supports straight-through processing and provides evidence that the transaction followed its expected path.
Structured payment data can improve matching because each field has a defined meaning. Inconsistent or incomplete data increases the chance that a legitimate transaction will require manual research.
Unmatched items become exceptions
An exception can arise from a timing difference, duplicate message, rejected instruction, missing posting, incorrect amount or a file that did not arrive. An exception is a signal to investigate—not proof that money was lost or fraud occurred.
The bank may compare additional reports, trace the transaction through connected systems, contact another participant or wait for a known timing difference to clear.
Resolution must correct the right record
Once the cause is understood, an authorized employee or automated control can repair the missing entry, reverse a duplicate, resubmit an eligible message or document why no adjustment is needed.
Changing the wrong side of the difference can create a second error. Approval limits, segregation of duties and an audit trail help ensure that adjustments are valid and traceable.
Trends reveal weaknesses in the process
A single exception may be routine. Repeated exceptions of the same type can reveal poor data, a faulty interface, unclear procedures or a control that is not operating as intended.
Banks therefore monitor aged items, volumes, root causes and resolution times. The aim is not merely to clear today’s queue, but to reduce the chance that the same break returns tomorrow.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.