Payment reconciliation glossary
Short, plain definitions of the terms used in multi-provider payment reconciliation. Each entry explains the term with a small synthetic example, why it matters to a finance team and how to spot it in your own data, and links to the related terms.
Reconciliation basics
- Payment reconciliation — checking every payment in your records against what each provider reported and booked.
- Two-way reconciliation — your log against the provider’s statement.
- Three-way reconciliation — your log, the provider’s notifications and the provider’s statement.
- Match rate — the share a reconciliation pairs; meaningless without its denominator.
- Record balance — every input record is parsed, skipped by rule or quarantined.
- Discrepancy queue — the work list of payments that did not reconcile, each with a reason.
- Claim candidate — discrepancies with one provider, grouped with evidence, ready to send.
Outcomes and discrepancies
- Reversed outcome — declined for the merchant, successful at the provider — or the other way round.
- Statement-only payment — a statement line with no record in your log.
- Nothing to reconcile against — no statement, none for the currency, or an incomplete one — named, not hidden.
- Incomplete statement — a statement that covers the period but holds only part of the payments.
- No final status — the provider has not reported success or failure yet.
- Day edge — payments around midnight that appear in the neighbouring day’s statement.
- Timing difference — a gap caused by when a payment was recorded, not by what happened.
Sources of payment data
- Merchant log — your own record of requests, responses and statuses.
- Callback — the provider’s notification about a payment’s status.
- Provider statement — the provider’s periodic list of what it processed.
- Statement coverage — which providers, periods and currencies your statements actually cover.
- Duplicate notification — the same payment event reported more than once.
- Idempotency key — a unique value that makes a repeated request count once.
Providers and payment flow
- Payment service provider — the company that accepts payments on your behalf.
- Acquirer — the institution that accepts card payments for the merchant.
- Payment orchestrator — one integration that routes payments to many providers.
- End provider — the provider that actually settles money behind an orchestrator.
- Settlement — the provider books a payment as final and transfers the funds.
- Decline reason — a refusal cause in one shared dictionary instead of each provider’s codes.
Data translation
- Normalisation — translating every provider’s messages into one model.
- Message shape — the structure of a provider message, regardless of its values.
- Canonical status — one shared meaning that replaces each provider’s status words.
- Minor units — amounts as integers in the smallest currency unit; mixing units is a hundredfold error.
- Quarantine — records that cannot be translated, kept with the stage and the reason.
- Canonical payment model — one shared language for every provider’s messages and statements.
Data protection and audit
- Anonymisation — personal data removed or masked before anything leaves the merchant.
- Encoding table — the private key that links codes back to real values; it stays with you.
- Tamper-evident audit trail — a log in which every entry carries the fingerprint of the previous one.
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