Settlement & Finance

Payment Reconciliation

What Is Payment Reconciliation? Definition and How It Works

Definition

Payment reconciliation is the accounting process of matching payment transactions recorded in a merchant's internal systems against the settlement funds received from the acquirer or payment provider, identifying and resolving discrepancies between what was sold, what was authorised, what was captured, and what was settled. It ensures that the merchant's financial records accurately reflect actual funds received and outstanding amounts.

How it works

Payment reconciliation compares data from multiple sources: the merchant's order management or ERP system (what orders were placed and at what amounts), the payment gateway or PSP (what transactions were authorised and captured), and the acquirer or bank settlement files (what funds were received and when, net of fees). Discrepancies between these data sets represent either errors that need correction or expected differences (timing, fees) that need to be accounted for.

A typical reconciliation workflow processes settlement files from the payment provider, which contain a record of each transaction settled, the gross transaction amount, the fees deducted (interchange, scheme fees, processing fees), the net settlement amount, and any adjustments for refunds, chargebacks, or reserve movements. These records are matched against the merchant's transaction records by reference number or transaction ID.

Common reconciliation discrepancies include: transactions captured but not yet settled (timing differences); refunds or chargebacks reducing the net settlement below expected; fee calculations that differ from contractual rates; transactions in one system but missing from another due to system errors; and currency conversion differences on multi-currency transactions.

Manual reconciliation is time-consuming and error-prone at scale. Automated reconciliation tools ingest settlement files from multiple payment providers, match them against order records using configurable matching logic, and flag exceptions for human review. The goal is a fully automated reconciliation for the majority of transactions, with human effort focused only on genuine discrepancies.

Why it matters

Inaccurate payment reconciliation creates financial reporting errors, missed dispute deadlines, and undetected revenue leakage. A merchant that fails to identify that a settlement batch is short by 0.3% due to an acquirer fee calculation error will not reclaim that amount; across large transaction volumes, these small discrepancies compound. Similarly, failing to match chargebacks against the correct order records makes dispute evidence preparation difficult and increases representment failure rates.

Payment reconciliation complexity grows with payment infrastructure complexity. A merchant using a single acquirer and payment method has a relatively simple reconciliation problem. A merchant using multiple acquirers, multiple payment methods (cards, bank transfers, digital wallets), multiple currencies, and split-payment or marketplace mechanics has a reconciliation challenge that requires purpose-built infrastructure to manage efficiently.

For finance teams, payment reconciliation feeds into accounts receivable and revenue recognition. Accurate reconciliation data is required for correct financial close, tax compliance, and audit evidence. Payment reconciliation failures that persist into the month-end close create restatement risk and audit findings.

With PXP

PXP provides settlement files and reporting with itemised fees and adjustments, plus webhooks for real-time reconciliation. Talk to our team about how PXP can support your reconciliation and reporting.

Talk to a payments specialist

Frequently asked questions

What is the difference between payment reconciliation and bank reconciliation?

Bank reconciliation matches a company's internal accounting records against its bank statement to confirm that cash balances are consistent. Payment reconciliation is more specific: it matches payment transaction records (from the gateway, PSP, or acquiring system) against order records and settlement funds received, identifying discrepancies at the individual transaction level. Payment reconciliation typically feeds into bank reconciliation: the net settlement amounts from payment reconciliation should match the credits appearing in the bank statement.

How often should payment reconciliation be performed?

Best practice is daily reconciliation or near-real-time reconciliation using webhook-based event matching. Daily settlement files from acquirers allow same-day identification of discrepancies. For merchants with high transaction volumes, continuous reconciliation using event streaming is more effective than batch processing because it identifies discrepancies immediately rather than at end-of-day. Monthly reconciliation is insufficient for most merchant scales: disputes have time-limited representation windows, and delayed discrepancy identification increases the cost of resolution.

What are the most common causes of reconciliation discrepancies?

Common causes include: settlement timing differences (transactions captured one day but settled the next, creating apparent discrepancies in daily matching); fee variances (actual fees differ from expected due to rate changes, downgrade adjustments, or minimum fee application); refund and chargeback processing (adjustments from earlier periods appearing in current settlement files); multi-currency rounding differences; and system-level errors such as duplicate transaction records or missing capture confirmations.