Payment Gateway Reconciliation: How to Match Settlement Reports to Your Books

Payment gateway reconciliation is the process of matching the transactions in your gateway's settlement reports against your internal order records and the deposits that land in your bank account, then explaining every difference — fees, refunds, chargebacks, FX conversion, timing, and the occasional genuine error. The numbers will never match line-for-line on their own, because a gateway settles in batches, nets its fees out before paying you, and runs on a settlement cycle measured in days. This guide is written from the gateway's side of the ledger: what a settlement report actually contains, a five-step reconciliation process, a worked example showing exactly where $115.30 of a $2,000 batch goes, and a template you can copy into a spreadsheet today.

Why your gateway report never matches your bank deposit line for line

Most mismatches aren't errors — they're the normal mechanics of card processing, and three structural facts explain the majority of them.

First, a card payment is three events, not one. Authorization reserves funds on the cardholder's card. Capture tells the network to actually move the money — possibly for less than the authorized amount, a partial capture (Stripe's authorization-and-capture documentation, accessed 2026-08-12). Settlement is when captured funds, minus fees, are paid out to you. Your order system records the sale at capture; your bank records money at settlement, days later — which is why a clean revenue month can pair with a messy cash month.

Second, gateways settle in batches, net of fees. Three hundred orders don't arrive as 300 deposits — they arrive as one transfer covering a settlement batch, with fees, refunds, and adjustments already deducted. A single bank line has to be exploded back into its component transactions before you can reconcile anything.

Third, settlement runs on a cycle. Cross-border card settlement commonly runs several days behind capture. HaiPay settles international card payments typically at T+5 (calendar days) — calendar days, not business days, so weekends count toward the clock — and as fast as T+1 (calendar days) on local payment methods in selected markets, with your exact timeline confirmed in your quote. Transactions captured near a period's end settle in the next one — the single largest source of apparent mismatch, and one that resolves itself once your process accounts for it.

What a settlement report actually contains

The settlement report is the gateway-produced document that makes reconciliation possible. Here are the fields that matter and what each is for:

Reconciliation lives or dies on the order-reference field: without your own order ID echoed back, every match becomes fuzzy matching on amount and timestamp — which breaks exactly when you need it most, two same-priced orders in the same minute. Prefer machine-readable reports (CSV or API) over PDFs; you will join this data against your own tables every cycle.

The five-step reconciliation process

1. Pull the three sources for the period. Gateway settlement report, internal order/invoice records, and the bank statement showing actual deposits. All three, every cycle — gateway-to-books alone misses payout failures; books-to-bank alone can't explain fees.
2. Match each bank deposit to a settlement batch. Confirm the deposit equals the batch's net total (after any per-transfer fee — see the worked example below). This is the industry-standard check: Adyen documents it as net credits minus net debits equalling the batch payout, and PayPal as tracing the Transfer ID to the bank line (Adyen, PayPal, both accessed 2026-08-12). If a whole batch is missing, check the settlement cycle before assuming a problem: a batch captured Thursday on a five-calendar-day cycle isn't late until the following Tuesday.
3. Match transactions inside the batch to internal orders. Join on your order reference. Every gateway line should find an order, and vice versa. Work the exceptions list, not the matched list.
4. Explain every residual difference. Each gets a category: fee, refund, chargeback, FX conversion, timing (will settle next batch), or genuine error (duplicate, missing, wrong amount). "Unexplained" is the only unacceptable category.
5. Record, adjust, and escalate. Post fee and FX entries to your ledger, roll timing items forward to next cycle's expected list, and raise genuine errors with the gateway while the detail is fresh. Close the period with a short written summary — the artifact your auditor will ask for.

Run this on a cadence matched to your settlement cycle — daily at high volume, weekly at minimum. The cost of reconciliation grows nonlinearly with the gap since you last did it.

Worked example: where $115.30 of a $2,000 batch goes

Small-ticket, high-frequency merchants feel fees hardest, so here is an illustrative batch. Say 100 international card transactions of $20 each settle in one batch, priced at HaiPay's blended rate, which starts at 2.5% + $0.30 per transaction ($0 setup, $0 monthly), with one $20 merchant-initiated refund at US$0.30 and a US$15 fee on the USD settlement transfer:

Your order system says $2,000; your bank says $1,884.70. Every dollar of the $115.30 gap is explainable from the settlement report — nothing here is an error. How fees, refunds, and transfer charges are grouped within a payout varies by setup; treat the grouping here as illustrative and reconcile against the lines your own report shows. Reconciliation also doubles as fee verification: on a $20 ticket, 2.5% + $0.30 is an effective 4%, the kind of structure-versus-rate trade-off our payment gateway fees guide breaks down. If your reconciled effective rate drifts from your contracted rate, that's a finding, not a rounding artifact.

Merchants on interchange-plus pricing should verify one level deeper: check the pass-through components, not just the total. On HaiPay's IC++ pricing (available with a minimum monthly processing volume of US$1,000 — a volume requirement, not a fee), an illustrative US$100 transaction breaks down as interchange 1.80% + scheme fee 0.20% + HaiPay processing 0.50% = 2.50% total; verify the pass-through components against your statement, not just the total — and if the components aren't itemized where you can see them, ask for that in writing. Current rate cards for both models are on the pricing page.

The seven causes of mismatch, and how to resolve each

When a difference survives batch matching, it falls into one of seven buckets:

The order matters: timing, fees, and refunds explain most differences, and genuine errors are the residue. Teams that investigate in this order close in hours, not days.

Cross-border adds two layers: currency and cycle

Reconciling a cross-border gateway adds complications that single-market guides skip entirely.

Currency. A customer pays in one currency; you settle in another. The settlement report should state the FX rate applied — recompute it, don't trust it blind — and the conversion cost belongs in your ledger as FX expense, not as vanished revenue. HaiPay's outbound FX fee runs from 1% to 2.5%, by market, with your market's rate confirmed in your quote; reconciliation should surface the effective FX cost as its own line — it is invisible in a gross-versus-deposit comparison.

Cycle and method mix. Local payment methods — bank transfers, wallets, local card schemes — settle on different cycles and fee structures than international cards (HaiPay supports 150+ local payment methods, priced from 0.8% by market and confirmed in your quote, across major emerging markets). One account can therefore produce multiple settlement streams per period, each needing its own batch matching. If the acquiring chain behind those streams is unfamiliar, the merchant acquiring guide explains who actually holds and moves the money at each hop.

A cycle quoted in calendar days is easier to reconcile than one in business days: on typical T+5 terms, a Monday capture is expected on Saturday — no weekend-and-holiday modeling across two jurisdictions. Your exact cycle is confirmed in your quote.

A reconciliation template you can copy

Here is a working column layout — one row per gateway settlement line, joined to your systems:

Add a small summary block per batch: expected net (sum of report net lines minus any transfer fee), actual bank deposit, and the difference — which should be zero before you close the period.

When a spreadsheet is enough

At one gateway, one settlement currency, and modest volume, the five-step process in a spreadsheet is a complete reconciliation system — the automation vendors ranking for this topic tend not to mention that. Three conditions change the answer: more than one gateway or payment method, multi-currency settlement, and high transaction counts at small tickets. Until one arrives, spend the tooling budget on report quality instead.

One selection-stage lesson hides in all of this: reconciliation effort is mostly determined by the gateway's report quality — order references echoed back, itemized fees, stated FX rates, a predictable calendar-day cycle. Those are questions worth asking before you integrate, not after your first messy month-end.

Sources

1. Stripe Docs — Place a hold on a payment method — separate authorization and capture; partial capture releases the remainder; authorization validity windows by card network. Accessed 2026-08-12.
2. Adyen Docs — Settlement reconciliation: transaction level — PSP reference / merchant reference as join keys; net credits minus net debits equal the batch payout. Accessed 2026-08-12.
3. PayPal Developer — Disbursement reconciliation — tracing a payout by Transfer ID; settlement amount plus fees reconciling to zero. Accessed 2026-08-12.