Three-Way Reconciliation

Overview

Why checking only two systems can miss a problem

Three-way reconciliation compares three independently useful records: what the merchant sold, what the payment processor recognized and what was ultimately credited or settled. Picture an online retailer that reports 100 successful orders and 100 processor credits. Those two sets match, but the withdrawal ledger is missing money from three credits. Without the third comparison the business might wrongly conclude that its payments were fully accounted for. The third data source turns “customer paid” into “merchant can trace proceeds.”

How the underlying system works

Design the control around a clear period and a documented matching model. Order records say what customers owe; payment records say what the processor accepted; settlement records say what value became available. A payment can pass one comparison and fail another—for example, an invoice is marked paid while its settlement is still pending.

Use stable references, currencies, valuation rules, transaction details and settlement batches. The control must handle one order paid with two transfers and a provider payout combining many invoices. Unmatched items should be assigned to an exception queue, not silently removed to make totals equal. Approvals and adjustments should retain evidence of the original discrepancy.

Match one order through all three sources

Order A expects $250. The payment provider records the equivalent of $250 accepted under its stated pricing rules. The business then looks for the provider credit and its allocation to a wallet receipt or payout batch. If the customer used two transfers, both must appear as components of one invoice. If the provider settles many invoices together, the sum of individual allocations must reconcile with the batch after supported fees. Each leg has its own reference, amount, asset, timestamp and status. Missing references are exceptions, not permission to mark the row complete.

What a completed three-way match establishes

A completed match gives strong operational evidence that the sale, accepted transfer and recorded proceeds correspond. It does not automatically prove compliance with every accounting standard or tax rule, nor that a blockchain can never reorganize. Finance still chooses valuation and recognition policies, while engineering ensures that source data is reliable. Match exceptions should be traceable to a resolution note and authorized adjustment. A three-way system is useful because it makes assumptions visible: which currency was used, what fee applied and when value was actually available.

Further reading and related concepts

Reference documents: OxaPay — Payment History, OxaPay — Payout History.

Related glossary topics: Reconciliation, Transaction Reconciliation, Settlement Reconciliation.