Payment reconciliation

Payment reconciliation is the check that matches the payments a business expects, from its sales records or invoices, against the money that actually reached its bank account or wallet, and explains every difference. The gaps usually come from fees, refunds, disputes and timing, because a provider pays out a batch of transactions net of its charges rather than each sale in full.

Why the deposit never matches the sales

Three card sales of $250, $100 and $40, then a refund of the smallest one: why does the bank show $337.79? Payments company Stripe’s US pricing page, read on November 12, 2026, charges 2.9% plus 30 cents on each domestic card payment. Issuing a refund costs nothing, but the processing fee on the original payment is not returned.

Line in the payout Gross Fee Net
Card payment $250.00 $7.55 $242.45
Card payment $100.00 $3.20 $96.80
Card payment $40.00 $1.46 $38.54
Refund of the $40 payment -$40.00 $0.00 -$40.00
Amount paid out $337.79

The figures are our arithmetic from those rates. Customers ended up paying $350, and the $12.21 gap is the three fees, including the one on the sale that was refunded. A chargeback adds its own line, since the same page lists a $15 fee for each dispute received.

Where you see it

The matching starts in the provider’s report. Stripe’s payout reconciliation report groups each automatic payout with the batch it settles, and its itemized export lists every transaction inside it, fees included.

Each line carries gross, fee and net columns, the automatic_payout_id of the payout and, where there is one, the original charge_id. A business can add its own metadata, such as an order number, to tie each line to its accounting records.

Two traps sit in the same documentation. The report files a payout under its estimated arrival date, not the date the bank posts the deposit, so a date range built on bank posting dates can miss it. And Stripe cannot say which transactions an instant payout contains, because the merchant picks its timing and amount, which leaves the business to reconcile instant payouts against its own history.

When customers pay in crypto

A crypto payment gateway adds on-chain steps but keeps the same logic. Crypto payments firm BitPay’s reconciliation report gives every settlement an ID that also appears in the description of the matching bank transfer. It computes the amount sent as the opening balance plus the sum of all ledger entries, minus withholdings.

BitPay codes the withholdings. W001 is a refund reserve the merchant can set, W002 covers bank fees passed on for a SWIFT wire, and W005 keeps back money for refunds still pending, so a settlement can come in below the invoices paid for reasons that are written in the report itself.

Invoices need their own check. BitPay’s invoice states mark one paidPartial when the customer sends too little, and that money is refunded to the customer automatically instead of credited to the merchant. With paidOver, only the excess goes back. An order that looks unpaid in the shop may have a refund on its way, not a missing payment.

In the UK, a daily duty

For regulated payment firms, payment reconciliation is a legal duty. The Financial Conduct Authority’s safeguarding page for payment and e-money institutions, last updated on May 7, 2026, says firms must perform internal and external safeguarding reconciliations at least once each reconciliation day.

That day excludes weekends, bank holidays and days when the relevant foreign markets are closed. The page also lists a monthly safeguarding return to the regulator, form REP027, confirming compliance with the safeguarding and reconciliation duties.

Any business can apply the same discipline by matching on the provider’s payout or settlement ID rather than on deposit dates, and by booking each fee and withholding as its own line.

Where it comes up