Guides

Payment reconciliation: questions buyers ask

Payment reconciliation confirms that every payment taken through a provider ended the way your records say, in amount and outcome. The answers below explain the terms buyers meet, the reasons statements disagree, what software should do, and what a first test needs. Each answer is vendor-neutral first, then says what Reconora does.

Buyers of payment reconciliation tools tend to ask the same questions, whatever their vertical. The answers below are written to stand alone. Each one explains the general principle first and then, where it is honest to do so, describes what Reconora does today. Figures come from one anonymised merchant day and are not an industry benchmark.

For the full method, read how to reconcile payments across dozens of providers and two-way vs three-way reconciliation. Terms are defined in the glossary.

What is payment reconciliation?
Payment reconciliation is the check that every payment taken through a payment provider ended the way your own records say. A complete check compares amount, currency and outcome, not only whether an ID appears in both files. Sources usually include the merchant’s log, the provider’s real-time notifications and the provider’s statement. Each payment ends in a named result: matched, different in money, different in facts, or impossible to check because no document covers it. Reconora runs this check across all three sources and returns every payment in one of four outcomes, each with a reason and a row address.
Why don't PSP statements match my transactions?
PSP statements rarely match transactions line for line because the two records are produced by different systems, at different times. A statement may be cut at the provider’s midnight, not yours. Amounts may be in minor units while your log uses major units. Status words differ from provider to provider. Many statement lines carry only the provider’s own ID: on one anonymised merchant day, 54.2% had no merchant ID. Some statements are incomplete, and some providers send none. Real differences, such as a reversed outcome, hide among these format differences until all records are translated into one format.
What is a settlement report (provider statement)?
A settlement report, also called a provider statement, is the provider’s own account of the payments it processed for a period, usually a day. It lists each payment with the provider’s ID, the amount, the currency, the final status and the time. Unlike a real-time notification, a statement is written after processing, so it shows what the provider finally settled. Formats vary widely: spreadsheets with headers below the first row, amounts and currency in one cell, separate date and time columns. Reconora reads statements in their native format and treats them as the third, settled source in three-way reconciliation.
How do you reconcile payments behind a payment orchestrator?
Payments behind a payment orchestrator should be reconciled against the end provider, not the orchestrator. The orchestrator routes each payment to an end provider, and that end provider’s statement is the one that settles money. The steps are: read from the orchestrator’s message which end provider handled each payment, keep the end provider’s own transaction ID, and match it against that provider’s statement. Matching only on the orchestrator’s ID often fails, because many statements never carry it. Reconora reads the end provider from orchestrator messages and reconciles each payment against the end provider’s own statement.
What is three-way reconciliation?
Three-way payment reconciliation matches three independent sources for each payment: the merchant log, the provider’s notifications such as callbacks and status responses, and the provider’s statement. The third source explains disagreements that two-way matching cannot. A callback that said declined for a payment the statement shows as settled becomes a named reversed outcome instead of an unexplained mismatch. Payment three-way reconciliation is different from procurement three-way matching, which compares a purchase order, a goods receipt and an invoice in accounts payable. Reconora performs payment three-way reconciliation; it does not handle procurement matching.
What does a 'match rate' really measure?
A match rate usually measures the share of records whose identifier was found in another file. That is not the same as the share whose amount and outcome agree. On one anonymised merchant day, a spreadsheet-style lookup found 75.5% of lines, while reconciliation on amount and outcome confirmed 74.4%. The headline numbers look similar. The difference sits in lines found but wrong, payments that exist only in a statement, and volume no document covers. When comparing match rates, ask what the denominator is, whether amount and outcome were checked, and how unverifiable volume was counted.
What is a reversed outcome?
A reversed outcome is a payment whose result differs between the merchant’s records and the provider’s statement. The common case is a payment declined for the merchant but successful at the provider: the customer was charged but not credited. The opposite case also happens. Reversed outcomes often appear because the provider corrected the result in its statement without sending a new notification. On one anonymised merchant day, Reconora found 320 payments of the first kind and 61 of the second. These figures describe that day only. Reversed outcomes involve real customer money, so they are worth reviewing first.
How long should daily reconciliation take?
Daily reconciliation should finish early enough for the team to act on the result the same morning. There is no universal target, because duration depends on the number of providers, formats and statements. Manual reconciliation tends to grow with each new provider, as every format needs its own formulas and mapping. Automated reconciliation shifts the effort from preparing data to reviewing exceptions. For reference, Reconora’s first reconciliation of a full anonymised merchant day took 63.1 minutes of machine time, including anonymisation at the merchant’s site. Review time for the discrepancy queue comes on top and depends on the day.
What should payment reconciliation software do (checklist)?
Payment reconciliation software should, at a minimum: read each provider’s notifications and statements in their native format; normalise amount units, time zones and status words; fold duplicate notifications; match on several identifiers, including the end provider behind an orchestrator; compare amount and outcome, not only presence; name payments with no statement instead of hiding them; separate day-edge timing from real discrepancies; group provable discrepancies into claims with row-level evidence; and keep a tamper-evident audit trail. Reconora does each of these for deposits today. It does not reconcile payouts or bank statements, and it does not integrate with accounting systems.
Can reconciliation run without sending customer data to a vendor?
Reconciliation can run without customer data leaving the merchant, if personal data is removed before anything is handed over. Matching needs identifiers, amounts, currencies, times and statuses. It does not need names, emails, card numbers or addresses. A consistent anonymisation step can replace sensitive values with codes while keeping matching keys stable. Reconora works this way: an anonymisation module runs inside the merchant’s perimeter, offline, using only the Python standard library. The encoding table and secret stay with the merchant, who receives the module’s full source code for audit and decodes results locally.
What happens to payments with no statement at all?
Payments with no statement at all cannot be confirmed, so they should be named as unverifiable rather than marked as reconciled or as debts. A provider may send no statement, none for a currency, or one that covers part of the day. On one anonymised merchant day, 26 providers in the reconciliation scope sent no statement, and 10.1% of turnover in scope had nothing to reconcile against. Reconora reports this volume as its own outcome, with the reason. When a statement is incomplete, it recommends requesting the full statement instead of raising a claim.
How do I start — what data is needed for a first test?
A first test of payment reconciliation needs one full day of data, not an integration. The minimum is an export of the merchant log or orchestrator log for the day, and the provider statements covering the same day. Notifications recorded in the orchestrator log make three-way checks possible. Choose a day with ordinary traffic, and include every provider you can. Reconora’s free one-day pilot works from these exports. The merchant anonymises the data on a computer with Python 3.11 or later, hands over the anonymised package, and receives the reconciled day back in codes to decode locally.

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