# Two-way vs three-way payment reconciliation

Two-way payment reconciliation compares the merchant’s log with the provider’s statement. Three-way reconciliation adds a third source: the provider’s real-time notifications. The third source catches payments whose outcome changed between the notification and the statement, and payments a provider confirmed but never settled — cases two-way matching cannot see.

## What is two-way payment reconciliation?

Two-way payment reconciliation compares two records of the same payments: the merchant’s own log and the provider’s statement. For each payment in the log, the team looks for a matching line in the statement and compares amount, currency and status. Payments found on both sides with equal values are reconciled. The rest become exceptions to investigate. [Two-way reconciliation](https://reconora.com/glossary/two-way-reconciliation) is the most common starting point because both files are easy to obtain. The log already exists, and most providers send a statement. The method works well when there are few providers, statements are complete, and the log status is trustworthy. The weakness is hidden in the last condition. The merchant log usually records the outcome reported by the provider’s notification. When the log and the statement disagree, two-way matching cannot say which side is wrong, or whether the provider changed its mind after the notification was sent.

## What is three-way payment reconciliation?

Three-way payment reconciliation matches three independent sources for every payment. The sources are the merchant log, the provider’s notifications and the provider’s statement. Notifications are the real-time messages a provider sends while a payment is in progress: callbacks, webhooks and status responses to polling. Treating notifications as a separate source changes what can be proven. The team can see what the provider said at the time, what the merchant recorded, and what the provider finally settled. A disagreement now has a location. Either the merchant recorded the notification wrongly, or the provider reported one outcome and settled another. [Three-way reconciliation](https://reconora.com/glossary/three-way-reconciliation) needs one extra step before matching. Notifications from many providers arrive in different shapes, units and status words, and they repeat. They must be translated into one format and folded into one event per fact before they can be compared.

## How do two-way and three-way compare?

Two-way and three-way reconciliation differ mainly in what they can explain, not only in what they can find.

| Situation | Two-way (log × statement) | Three-way (log × notifications × statement) |
|---|---|---|
| Amount differs between log and statement | Caught | Caught, with the side that changed |
| Payment in the statement, absent from the log | Caught only if you look from the statement side | Caught, with the notification trail if one exists |
| Notification declined, statement settled | Seen as a mismatch with no explanation | Caught as a reversed outcome |
| Notification successful, payment absent from the statement | Looks like a debt or a timing gap | Caught as confirmed but not settled |
| Merchant recorded the notification wrongly | Hidden behind a log–statement mismatch | Isolated as an internal error |
| Duplicate notifications | Not visible | Folded and counted |
| No statement at all | Payment marked unmatched | Named as nothing to reconcile against |

## Which cases does two-way reconciliation miss?

Two-way reconciliation misses the cases where the provider’s own records disagree with each other. The first is the [reversed outcome](https://reconora.com/glossary/reversed-outcome). A callback says “declined”, the merchant does not credit the customer, and the statement later shows the payment as settled. The customer was charged but not credited. In two-way matching, the line looks like a statement-only payment or a status mismatch with no explanation. On one anonymised merchant day, Reconora found 320 payments of this kind and 61 of the opposite kind. These figures describe one day only, not an industry rate. The second case is a payment confirmed by callback that never appears in a complete statement. Two-way matching reports it as missing, and a team often books it as a timing gap. Three-way matching shows that the provider confirmed the payment in writing at the time. That confirmation is the evidence a claim needs.

## What does a three-way check look like on one payment?

A three-way check on one payment reads three answers to the same question. Take a synthetic, illustrative payment `PAY-5E6F` taken through Provider B in `CUR-1`. The merchant log records “declined”, so the customer was not credited. The provider’s callback, received at `14:02`, also says “declined”. The provider’s statement for the day lists the same payment as settled for `75.00`. Two-way matching sees a log line and a statement line with different statuses. It cannot say whether the merchant recorded the callback wrongly or the provider changed the outcome. Three-way matching can. The log agrees with the callback, so the merchant’s records are faithful. The provider reported one outcome and settled another. The payment is a reversed outcome, and the callback is the evidence. The customer should be credited, and the provider should be asked why no corrected notification was sent. Without the callback, the same line would wait in an exception list with no owner.

## Is payment three-way reconciliation the same as three-way matching in accounts payable?

Payment three-way reconciliation is not the same as three-way matching in accounts payable. Procurement three-way matching compares a purchase order, a goods receipt and a supplier invoice. The goal is to pay a supplier only for goods that were ordered and delivered, at the agreed price. The work belongs to accounts payable and runs per invoice. Payment three-way reconciliation compares the merchant log, the provider’s notifications and the provider’s statement. The goal is to confirm that customer payments taken through payment providers ended the way the merchant recorded them. The work belongs to payments operations or treasury and runs per payment, usually daily. The two share a name and a principle: three independent documents must agree before money is trusted. They share no documents, no systems and no team. Search results often mix them, so it helps to say “payment” or “PSP” explicitly when discussing the second.

## When is two-way reconciliation enough?

Two-way reconciliation is enough when the merchant log is a reliable copy of what providers reported, and statements are complete. In practice that usually means a small number of providers, each sending a full daily statement. It also means notifications are recorded exactly as received, and reversed outcomes are rare enough to investigate by hand. Two-way is also a sensible first stage when a team has never reconciled systematically. A log-to-statement match, done from both sides, already finds missing payments and amount differences. The signs that two-way is no longer enough are practical ones. Mismatches arrive without an explanation. Customer complaints about uncredited payments do not appear in the reconciliation. Claims to providers are rejected for lack of evidence. The team cannot tell an internal recording error from a provider error. A further sign is growth. Each new provider brings its own notification format and statement layout. Once a team works with many providers, reversed outcomes can become a daily category rather than a rare exception. At that point, the cost of keeping notifications as a third source is lower than the cost of investigating unexplained mismatches one by one.

## How do you move from two-way to three-way reconciliation?

Moving from two-way to three-way reconciliation is mostly a data task, not a process overhaul.

1. **Keep raw notifications.** Store every callback and status response as received, with the time of arrival.
2. **Translate them into one format.** Normalise amount units, time zones and status words across providers.
3. **Fold repeats.** Reduce repeated notifications of the same fact to one event per payment and status.
4. **Match on several identifiers.** Use your ID, the order ID and the provider’s ID, including the end provider behind an orchestrator.
5. **Compare outcomes, not only presence.** Check what each of the three sources says happened.
6. **Name what cannot be checked.** Record providers or currencies with no statement instead of marking them unmatched.

The [multi-provider reconciliation guide](https://reconora.com/guides/multi-provider-reconciliation) covers the full method and a daily checklist. The [reconciliation product page](https://reconora.com/product/reconciliation) shows how Reconora applies it.

[Start a free pilot](https://reconora.com/pilot) · [Book a 20-min call](https://calendar.google.com/calendar/appointments/schedules/AcZssZ2qcg1D27PGeYQ91fuYaSo7oy6D4tQ0onTGhC2mSdAWZpCuMUozMxIan4qYWtSk56H-hZTTZAC7)

---
Source: https://reconora.com/guides/two-way-vs-three-way · Updated 2026-10-18
