# Payment reconciliation guides

These guides explain how to reconcile payments across many payment providers, in plain language and without naming vendors. They cover the method, the difference between two-way and three-way reconciliation, what a match rate hides, and the questions to ask before buying. Examples are synthetic; figures come from one anonymised merchant day.

## Guides

Reconora Research writes these guides for finance, payments and treasury teams at merchants who accept money through many providers. Each guide is vendor-neutral first. Where a guide mentions Reconora, it says so plainly.

- [How to reconcile payments across dozens of payment providers](https://reconora.com/guides/multi-provider-reconciliation) — the full method: three sources of truth, one common format, matching on several identifiers, four outcomes, a taxonomy of reasons a payment does not match, a worked synthetic example and a daily checklist.
- [Two-way vs three-way payment reconciliation](https://reconora.com/guides/two-way-vs-three-way) — what each approach catches and misses, why notifications are the third source, how payment reconciliation differs from procurement three-way matching, and how to move from one to the other.
- [What a `99.9%` match rate hides](https://reconora.com/guides/match-rate) — why “found” is not the same as “reconciled”, what the denominator of a match rate leaves out, and how to read a headline figure critically.
- [5 questions to ask any reconciliation vendor](https://reconora.com/guides/vendor-questions) — short questions that separate a real reconciliation from a lookup, covering amount and outcome checks, missing statements, evidence and customer data.
- [Payment reconciliation: questions buyers ask](https://reconora.com/guides/buyer-questions) — self-contained answers on statements, orchestrators, reversed outcomes, daily effort, software checklists and what a first test needs.
- [Payment status mapping: a practical guide](https://reconora.com/guides/payment-status-mapping) — why providers report the same outcome in different words and places, what a good mapping does, how to build and version one, common mistakes and a synthetic example.
- [Why part of the day is always awaiting a statement](https://reconora.com/guides/awaiting-a-statement) — why statements lag behind payments, how the day edge works, why awaiting is neither a discrepancy nor a match, and how to report it.
- [Offline anonymisation for payment data](https://reconora.com/guides/offline-anonymisation) — what to remove, what to keep as shape-preserving hashes, why the key stays with the data owner, how to test with planted markers and why to publish weak spots.

## Tools and reference

The guides link to reference pages and interactive tools that work on your own figures or on synthetic data.

- [Glossary](https://reconora.com/glossary) — plain definitions of reconciliation terms, from acquirer to tamper-evident audit trail.
- [Reconciliation maturity check](https://reconora.com/tools/maturity-check) — a short yes-or-no self-assessment of your current process.
- [Exposure calculator](https://reconora.com/tools/exposure-calculator) — estimates how much turnover may sit unverified, using shares from one measured day.
- [Reconcile a day](https://reconora.com/tools/reconcile-a-day) — an in-browser sandbox that reconciles a synthetic day so you can see each outcome.
- [Payment chaos report](https://reconora.com/payment-chaos) — how 96 providers described the same payment on one anonymised merchant day.
- [Methodology](https://reconora.com/methodology) — how every number on this site is measured, scoped and checked.

[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 · Updated 2026-10-18
