Two-way reconciliation
Two-way payment reconciliation compares two sources for every payment, usually the merchant’s own log and the provider’s statement. It shows whether a payment appears in both and whether the amounts agree. It does not read the provider’s callbacks, so it cannot see disagreements between what the provider reported and what it booked.
How it works
Two-way reconciliation joins the merchant log with the provider statement on a shared ID. Each pair is then compared on amount and status. Illustrative, synthetic example:
log PAY-8E2A Provider R CUR-5 amount: 300 status: success
statement PAY-8E2A amount: 300 status: settled -> found, amounts agree
Two-way payment reconciliation is not procurement “two-way matching”. In accounts payable, two-way matching compares a purchase order with a supplier invoice. Payment reconciliation compares records of incoming payments, not bills.
Why it matters
Two-way reconciliation is often the spreadsheet default, and it looks better than it is. “Found” is not the same as “reconciled”. 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 in amount, status or currency. Adding callbacks as a third source shows why the provider’s story changed.
How to spot it
- Check which sources your process reads: two files or three.
- Look for payments marked “found” whose final status differs between sources.
- Ask how a callback that said declined is handled when the statement says settled.
Related terms
Three-way reconciliation · Payment reconciliation · Match rate · Callback · 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