Payment Reconciliation: A Practical Guide for Merchants
By PayEurasia Team · 2 October 2026 · 6 min read
Last updated 2 October 2026
How to match your ledger, the provider settlement file and the bank statement every day — and what to do with the breaks that remain.
Reconciliation is the control that turns a payments integration into a financial system. Without it, you have a dashboard and a hope. This guide describes a three-way daily reconciliation that scales from hundreds to hundreds of thousands of transactions.
What this guide covers
- The three sources of truth
- Getting the ledger right first
- Automating the match
- Break categories worth tracking
- Handling refunds, chargebacks and reversals
- Payout-side reconciliation
- Controls, ownership and escalation
- What good looks like
The three sources of truth
You have an internal ledger of what you believe happened, a provider settlement file of what the provider says happened, and a bank statement of what money actually moved. Reconciliation is matching these three, in that order, every day.
Matching only two of the three is the usual shortcut and the usual failure. Ledger-to-provider catches integration bugs; provider-to-bank catches settlement problems. Skipping either leaves a class of error invisible.
Getting the ledger right first
Record amounts in minor units as integers, never floating point. Store the currency alongside every amount, record fees as their own entries rather than netting them into the transaction, and make the ledger append-only.
Every entry needs both your reference and the provider reference. Missing provider references are the single most common reason automated matching drops to manual work.
Automating the match
Match on provider reference first, then on a composite of amount, date window and method for anything left. Anything still unmatched after both passes goes into an exceptions queue with a category, not into an inbox.
Run it daily and unattended. A weekly reconciliation means a problem can be six days old before anyone sees it, and provider support conversations get harder the further you are from the event.
Break categories worth tracking
Timing breaks — captured today, settled tomorrow — are normal and should clear themselves; alert only when they age beyond the expected cycle. Fee breaks mean your fee model does not match what is being charged and deserve immediate investigation.
Missing-in-ledger breaks mean money moved without your system knowing, usually a dropped webhook. Missing-at-provider breaks mean your system recorded something that never happened, usually an optimistic status update. Both are bugs, not admin.
Handling refunds, chargebacks and reversals
These arrive after the original settlement and must be linked to the original transaction, not booked as standalone negatives. Unlinked adjustments make dispute rates unmeasurable and distort the revenue picture.
Reserve movements need the same treatment: withheld and released amounts are transfers, not income or cost, and mixing them into revenue lines produces a P&L that nobody can explain.
Payout-side reconciliation
Outbound money needs the same three-way discipline: instruction, provider confirmation, bank debit. Returned credits must reopen the original instruction rather than appearing as mystery income.
Where collections and payouts net against each other, reconcile both legs before the net figure. Netting first hides which side is wrong.
Controls, ownership and escalation
Give reconciliation a named owner, a daily completion deadline and an escalation path for aged breaks. A queue with no owner grows quietly until an auditor finds it.
Set thresholds: anything above a value or older than a number of days is escalated. Investigating every small break to the last unit costs more than it recovers; ignoring large ones costs far more.
What good looks like
A healthy operation reconciles automatically overnight, clears well over ninety-five percent of items without a human, ages the remainder in a visible queue, and closes the month without a reconstruction exercise.
The measurable outcome is time-to-answer. When finance asks where a specific payment is, the answer should take a search, not an investigation.
Frequently asked questions
How often should reconciliation run?
Daily and automatically. Manual monthly reconciliation finds problems far too late to resolve them with the provider.
What match rate is realistic?
Above ninety-five percent automatic on provider reference alone is achievable when both references are stored on every entry.
Do small breaks matter?
Individually no, as a trend yes. A persistent small break usually indicates a fee or rounding model error that scales with volume.
Who should own reconciliation?
Finance owns the outcome; engineering owns the data quality that makes it possible. Both need to be named.
What if the provider file and the bank disagree?
Raise it with the provider immediately with references and amounts. The bank statement is the authoritative record of money movement.
Where PayEurasia fits
PayEurasia runs local collections and payouts across Bangladesh, India, Pakistan and Nepal behind a single API, one reconciliation model and one settlement relationship. Provider redundancy sits behind that API, so an acquirer outage degrades approval rates instead of stopping money movement.
If you are scoping an integration, the API overview explains the object model and the API documentation covers authentication, webhooks and error handling. Merchant onboarding lists the documents needed before a live account is issued, and Compliance sets out the KYC and AML framework applied to every merchant.
Related guides
Talk to PayEurasia
Working in a high-risk vertical across South Asia? We can probably help.
Request integration →