Merchant Reconciliation
Pronunciation: MUR-chunt rek-un-sil-ee-AY-shun
Definition
Merchant reconciliation compares a merchant's orders, payment transactions, fees, refunds, chargebacks, conversions, settlements, payouts, and accounting entries. It proves how gross customer payments became the net amount credited or paid to the merchant. The principal failure modes are missing records, reused references, cutoff mismatches, duplicate matches, wrong currencies, hidden fees, unresolved suspense, forced balancing, partial refunds, late settlement changes, and corrections without approval evidence.
Overview
Meaning and scope
Merchant reconciliation compares a merchant’s orders, payment transactions, fees, refunds, chargebacks, conversions, settlements, payouts, and accounting entries. It proves how gross customer payments became the net amount credited or paid to the merchant. The principal failure modes are missing records, reused references, cutoff mismatches, duplicate matches, wrong currencies, hidden fees, unresolved suspense, forced balancing, partial refunds, late settlement changes, and corrections without approval evidence.
Mechanism and operation
Merchant reconciliation proves that a store’s commercial orders correspond to genuine payment receipts and correct accounting postings. It joins order IDs, payment gateway invoice IDs, network transaction evidence, fees, settlement destinations and refunds. The merchant must distinguish orders created from orders paid, and callbacks received from money actually settled. Differences can arise from partial crypto payments, duplicate events, returns, conversion changes and provider outages. Daily totals alone are insufficient because offsetting errors can conceal an unpaid order and an overcredited order. A robust workflow identifies exceptions, preserves source evidence, assigns investigation owners and posts controlled adjustments.
Practical payment example
A store reconciles paid orders to provider invoice IDs and observed asset receipts, identifying one overpayment and one missing callback.
Operational checks
Compare each commercial order to one or more valid payment records and separately reconcile net proceeds. For Merchant Reconciliation, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Changes affecting Merchant Reconciliation should be versioned, tested under normal and degraded conditions, and reconciled after incidents or manual intervention. Access to manual changes for Merchant Reconciliation should be restricted, logged, and periodically reviewed, with reconciliation required after any intervention that changes financial or customer-facing state.
Distinctions and limits
Merchant reconciliation connects commerce and money; provider reconciliation may cover internal processing without proving the merchant’s books are complete.
Related reading
Related definitions: reconciliation, Reconciliation Exception.
Example
A store reconciles paid orders to provider invoice IDs and observed asset receipts, identifying one overpayment and one missing callback.
Comparison
Merchant Reconciliation should remain distinct from Reconciliation and Reconciliation Exception, because each can represent a different stage, record, control, or financial outcome. Important failure modes include missing records, duplicate matches, timing differences, hidden fees, currency mismatches, stale files, and adjustments that force balances to agree without explaining the cause.
Key Takeaway
Merchant reconciliation compares a merchant's orders, payment transactions, fees, refunds, chargebacks, conversions, settlements, payouts, and accounting entries. Its matching scope, cutoff, exceptions, and resolution evidence must be explicit.
Sources
- Principles for Financial Market Infrastructures — BIS CPMI-IOSCO (2026-08-01)
- Conceptual Framework for Financial Reporting — IFRS Foundation (2026-08-01)