Reconciliation

Reconciliation is the process of comparing two independent records of the same activity, typically a firm's internal ledger and the statement or report of a bank or business partner, matching the items that agree, and investigating every difference until it is explained and corrected. In accounting it is often a monthly task that ends with a signed-off balance. In payments it is a daily, often intraday, operational control whose real output is the list of unexplained differences, known as breaks, that someone must chase down.

Reconciliation is how a payment company proves that the money it thinks it holds is actually where it should be. Regulators treat it as a core control for any firm that holds customer funds, and many operational losses in payments, from duplicate payouts to undetected fraud, are first visible as reconciliation breaks.

A reconciliation cycle generally has four steps:

1. Collect the data. The firm extracts its internal transaction records and obtains the external records: bank statements, often in formats based on ISO 20022 or older SWIFT statement messages, card scheme and acquirer settlement files, payout partner reports, or blockchain transaction data.
2. Match. Records are paired using references, amounts, dates and counterparties. Matching may be one-to-one, one-to-many (one bank credit covering a batch of customer payments), or many-to-many. Automated engines apply matching rules and tolerances; the remainder goes to a person.
3. Investigate breaks. Each unmatched item is classified: timing difference, fee deduction, foreign-exchange difference, duplicate, missing record, or error.
4. Resolve and record. The cause is corrected, adjusting entries are posted where needed, and the break is closed with an explanation. Ageing reports track breaks that remain open.

• Bank or cash reconciliation: the ledger balance and movements on each bank account against the bank statement. For a cross-border firm this includes every nostro account held with correspondent banks.
• Transaction reconciliation: each customer payment in the firm's system against the confirmation from the rail or partner, checking that every pay-in was received and every payout was delivered.
• Partner and settlement reconciliation: amounts owed to and from processors, acquirers, payout partners and agents against their settlement reports, including fees and reserve holdbacks.
• Safeguarding reconciliation: for regulated firms, the amount held in segregated or safeguarding accounts against the amount owed to customers.
• Three-way reconciliation: common in payments and client-money businesses, it compares the internal ledger, the bank and the customer-level sub-ledger to confirm that individual balances add up to the pooled bank balance.

Most breaks have ordinary explanations. A payment sent late in the day appears on the bank statement the next business day. A correspondent bank deducts a fee under SHA or BEN charge codes, so the credit is smaller than expected, producing a short-paid payment. A payout is rejected and comes back days later as a returned payment, sometimes in a different amount after currency conversion. A customer pays without a reference, so the incoming funds cannot be allocated to an account. Less often, the break reveals a duplicate payout, a system error, an unauthorized transaction or fraud, which is why every break must be explained rather than written off by default.

Reconciliation is required or expected under many payment regimes. In the UK, the FCA requires payment and e-money institutions to reconcile the funds they must safeguard, known as relevant funds, against the amounts held in safeguarding accounts, and has tightened those requirements. US state regulators examine whether money transmitters can reconcile outstanding payment obligations to the permissible investments they hold, and client-money rules for investment firms contain similar requirements. A firm that cannot reconcile reliably cannot demonstrate that it holds customers' money, which is a serious supervisory finding.

A remittance company expects USD 1,250,000 to arrive in its US bank account from 4,200 customer card and bank transfers processed the previous day. The bank shows USD 1,247,815. Matching clears 4,188 transactions. The remaining difference of USD 2,185 resolves into three items: USD 1,900 in two transfers that will settle the next day, a USD 260 card payment reversed as a chargeback, and USD 25 in bank fees not yet booked. The fees are posted, the timing items are carried forward with an expected clear date, and the chargeback is passed to the disputes team.

Small firms often begin with spreadsheets, but volume quickly makes manual matching unreliable. Dedicated reconciliation software, functions inside core banking and treasury management systems, and in-house matching engines are common. The structured remittance information in ISO 20022 messages and end-to-end references such as the UETR make automated matching more accurate.