Compare
Independent reconciliation vs reconciliation inside your orchestrator.
A reconciliation module inside a payment orchestrator checks the orchestrator's own routing and callbacks. An independent layer checks the same payments against what each end provider actually settled in its statement. The two answer different questions: did my router record this correctly, and did the money really arrive. Reconora reads the orchestrator's log; it does not replace it.
Who grades the orchestrator's homework?
A payment orchestrator sits between the merchant and many payment providers. The orchestrator picks a route, sends the payment, receives the provider's callback and writes the result to its log. Many orchestrators now offer a reconciliation module as well. The module compares the orchestrator's records with what the orchestrator received. That is useful work. It is also the same system checking its own output. When the orchestrator recorded a status wrongly, missed a late correction or never saw a payment at all, its own module has nothing outside itself to notice the gap. An independent layer starts from a different place. It treats the orchestrator's log as one source among three and asks each end provider what it actually settled. The question is not whether the orchestrator is good. The question is whether anyone checks it against a source it does not control.
What the orchestrator sees, and what it does not
An orchestrator sees its own routing decisions and the messages providers send back to it. Those messages are callbacks: fast, frequent and sometimes wrong. A provider may report "declined" in a callback and later settle the same payment as successful. A new callback does not always follow; the correction appears only as a line in the provider statement days later. End providers settle by statement, not by callback. A statement is the provider's own record of what it collected and what it will pay out. An orchestrator that reconciles callbacks against its log can agree with itself perfectly and still miss what the statement says. Payments the orchestrator never logged cannot appear in its module at all. On one anonymised merchant day, Reconora found 317 payments in provider statements with no trace in the merchant's log.
What an independent layer checks
Reconora reconciles three sources for every payment: the merchant log, the provider callbacks and the provider statement. That is three-way reconciliation. On top of the match itself, an independent layer looks for what a self-check cannot see.
- End-provider statements. Each payment is checked against what the end provider settled, not only against what the orchestrator recorded.
- Statement coverage. Which providers sent a statement, for which currencies, and how complete it was. On one anonymised merchant day, 26 providers sent no statement at all.
- Reversed outcomes. Payments declined in the log but successful in the statement, and the other way round. On the same day: 320 of the first kind and 61 of the second.
- Statement-only payments. Settled by a provider, absent from the log.
Every line ends in one of four outcomes, with a reason and row addresses.
Side by side
| Module inside the orchestrator | Independent reconciliation layer | |
|---|---|---|
| Source of truth | The orchestrator's own log and the callbacks it received | Three sources: merchant log, callbacks, end-provider statements |
| End-provider statements | Depends on the module | Read in each provider's native format and matched line by line |
| Blind spots named | Payments it never logged cannot appear | Providers and currencies without statements, incomplete statements, payments with nothing to reconcile against |
| Independence | Checks its own records | Checks the orchestrator against sources it does not control |
| Data handling | Inside the orchestrator's platform | Anonymised inside your perimeter; Reconora receives no personal data |
| Switching providers | History and rules stay with the orchestrator | Reconora reads whichever orchestrator log you export; the method does not depend on the orchestrator |
When the built-in module is enough
A built-in module can be the right tool. A merchant with few providers, each sending complete daily statements into the orchestrator, may find the module's view sufficient. The same is true when the orchestrator ingests end-provider statements, not only callbacks, and shows payments it did not route. If the finance team can trace a single payment back to the statement row, and the module names providers without statements, the main questions are answered. An independent layer adds most where those conditions fail: many local providers, statements in many formats, incomplete or missing statements, and corrections that arrive only by statement. On one anonymised merchant day the data held 96 providers and 35 statement formats. A merchant in that situation should put the five vendor questions to the module's supplier before relying on it.
How the two work together
Reconora does not route payments and does not replace an orchestrator. The orchestrator keeps doing what it does well: choosing routes, retrying, collecting callbacks. Reconora reads the orchestrator's log export as the merchant's side of the record. That is why the pilot asks for an orchestrator log export and a provider statement workbook, and no API integration. The log, the callbacks and the statements are anonymised at your site, reconciled, and returned with the discrepancies named. When the orchestrator recorded a payment correctly, the result simply confirms it. When it did not, the discrepancy queue shows the payment, the reason and the evidence. The payments team then decides what to raise with the provider or with the orchestrator. Nothing about routing changes. Read how reconciliation works, or compare it with a spreadsheet check.
A neutral check is a control, not a criticism
A second, independent check is a normal finance control. Auditors do not accept a ledger checked only by the person who wrote it. The same logic applies to payments. An orchestrator can be well built and still depend on what providers tell it in real time. Provider statements are slower, but they are where settlement is recorded. A layer that reads both, and names what neither covers, gives the finance team a view no single system can give about itself. The methodology page explains how every figure on this page was measured.
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.
By Reconora Research · Updated