Three-way reconciliation
Three-way payment reconciliation matches three independent sources for every payment: the merchant’s own log, the provider’s real-time notifications (callbacks and status responses) and the provider’s statement. A payment is matched only when all three agree on identity, amount, currency and final status; otherwise the disagreement is named as an outcome with a reason.
How it works
Three-way reconciliation joins three records of one payment. The merchant log says what the merchant believed. The callback says what the provider reported at the time. The provider statement says what the provider finally booked. Illustrative, synthetic example:
log PAY-2C9D Provider F CUR-1 amount: 4200 status: success
callback PAY-2C9D status: approved
statement PAY-2C9D amount: 4200 status: settled -> matched
Three-way payment reconciliation is not procurement “three-way matching”. In accounts payable, three-way matching compares a purchase order, a goods receipt and a supplier invoice before paying a bill. Payment reconciliation checks incoming payments against provider data instead.
Why it matters
Three-way reconciliation catches what a two-way check hides. Matching the log against the statement alone misses cases where the notification and the statement disagree, such as a callback that said “declined” for a payment the statement shows as settled. On one anonymised merchant day, a spreadsheet join found 75.5% of lines, but only 74.4% were truly reconciled. 690 lines were found but wrong.
How to spot it
- Check whether your process reads callbacks at all, or only the log and the statement.
- Ask what happens when two sources agree and the third does not.
- Count outcomes: a three-way process names more than “matched” and “missing”.
Related terms
Two-way reconciliation · Payment reconciliation · Reversed outcome · Match rate · Two-way vs three-way
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated