Reconciliation
Reconciliation is the matching of a company's own record of payments — orders, payouts, refunds, fees — against what its providers report and what actually arrived in its bank accounts, transaction by transaction, so every euro is accounted for and every difference explained. In a payments company it is also the daily proof that client money equals customer balances; everywhere it is where lost money surfaces.
- Also known as
- Payment reconciliation, Settlement reconciliation, Three-way matching
- Used at
- every merchant with more than one payment method, every marketplace, every payments and e-money company (where daily safeguarding reconciliation is a regulatory duty), and treasury generally
- Binding
- for payment and e-money institutions, the safeguarding rules require daily reconciliation of client funds; accounting standards and audit require the rest; the schemes' dispute timelines make unreconciled chargebacks expensive
- Typical layers
- transaction-level (each order to each settled item, by ARN or PSP reference), settlement-level (each provider's payout to its report), and bank-level (each payout to the bank statement); fees, refunds, chargebacks, reserves and FX explain the differences
- Typical tooling
- spreadsheets at small scale; reconciliation platforms (specialist vendors, or modules in the PSP or the ERP) matching millions of items with rules and tolerances; exceptions routed to analysts
- Parties
- the finance and payments-operations teams, the PSPs and acquirers (whose reports are one side), the banks (the other), the auditors, and for a regulated fintech the regulator reading the safeguarding reconciliation
How reconciliation works in practice
A retailer sells 12,000 orders on Monday through three PSPs and two local payment methods. On Wednesday the PSPs pay out: five bank credits, each a net figure — sales less fees, refunds, chargebacks and reserve holdbacks — for a mix of days. The reconciliation engine takes the PSPs' settlement files (every item with its reference, amount, fee and date), matches each item to an order in the retailer's system, sums the items per payout and matches the sum to the bank credit. Where everything matches, nothing happens. Where it does not — an order with no settled item (a failed capture), a settled item with no order (a duplicate), a fee that differs from the contract, a chargeback nobody logged, a payout short by €3,000 because a reserve was taken — an exception is raised and someone looks.
The exceptions are the value: a failed capture is revenue lost silently; a fee discrepancy compounds monthly; a reserve nobody expected is a cash-flow surprise; a duplicate is a customer complaint in waiting. At a payments company the discipline is stricter and daily: the balances customers see must equal the funds in the safeguarding accounts plus items in transit, proven every morning, because the regulator will ask and a shortfall is a breach.
For a buyer, the reconciliation function is where the target's financial control is tested: a company that reconciles at item level with few ageing exceptions knows its numbers; one that reconciles totals monthly is guessing between.
Example
A marketplace reconciles monthly, at total level: PSP payouts against bank credits, with a "reconciling items" line that has grown to €410,000. A new finance lead implements item-level daily matching. Month one findings: €62,000 of orders captured on the platform but never settled (a webhook failure marked them paid); €28,000 of fees above the contracted rate on one PSP, backdated eight months; 140 chargebacks debited and never logged, so never represented — €19,000 unrecoverable; a €150,000 reserve the acquirer had imposed and told an account manager who left; and €31,000 of duplicate payouts to sellers. The €410,000 line is explained inside six weeks, €120,000 of it recovered, and the CFO's board report has an exceptions-ageing chart for the first time.
Common mistakes
- Reconciling totals and calling the difference "timing". - No transaction-level references stored, so items cannot be matched. - Fees assumed correct because the contract says so. - Payments companies whose safeguarding reconciliation is weekly, discovered by an inspector. - Treating reconciliation as bookkeeping when it is the control that finds lost money.