Payout reconciliation stops being a formality at a very specific moment: when the number of payouts passes the number a person can hold in their head. Before that, someone remembers who was paid. After it, the month simply does not close, and nobody can say exactly why.
The cause is almost never a missing payment. It is that the money moved in one system, the fee was taken in another, and part of the amount never arrived because it is being held on purpose. Reconciliation is the practice of making those three views agree.
Contents
- Why the numbers do not match
- The three views you are matching
- Reconciling outgoing payouts
- Currency: match before you convert
- A monthly close that fits on one page
- What to fix before it becomes a problem
- Signs it is already broken
- In short
Why the numbers do not match
- Settlement is not instant. With a term of T+7, a sale made in one month settles in the next. Card turnover and money received are two different figures for the same period, and both are correct.
- Part of the money is held on purpose. The rolling reserve is 10% for 180 days — your money, released on schedule. If your report treats it as a fee, every month will look wrong.
- Fees arrive separately from amounts. The rate, the 0,50 EUR per transaction and the settlement percentage may be deducted in different places or at different times.
- Refunds and disputes travel backwards. A refund costs 50,00 EUR, a chargeback 100,00 EUR, and both land in a period after the sale they relate to.
- Batches hide their contents. One outgoing payment for forty recipients appears in the bank as a single line.
What each of those lines costs is on the pricing page.
How settlement itself works is described under payment processing.
The three views you are matching
What the business sold. Orders, subscriptions, invoices — whatever your own system records.
What the provider reports. Transactions, fees, refunds, disputes and the reserve movements, by date.
What the bank shows. Money that actually arrived and left, net of everything already deducted.
Reconciliation is complete when every amount in the third view can be traced to entries in the first two. Not when the totals happen to look similar.
Reconciling outgoing payouts
This is where most of the pain lives, because a batch collapses many recipients into one line. Three habits do most of the work.
- Give every payout a reference that survives the trip. Your own identifier, present in your system and in the provider’s report — not the recipient’s name, which will not be unique for long.
- Keep the batch and its contents linked. The bank line is the batch; the reconciliation happens against the list inside it.
- Record failures as first-class events. A returned payout that quietly disappears from the report is the single most common source of a month that does not close.
How the sending side is organised — schedules, destinations, batches — is described under payouts.
The mechanics at scale are unpacked in our piece on mass payouts for high-risk businesses.
Currency: match before you convert
If you receive in one currency and pay out in another, reconcile in the currency each side actually moved and record the conversion as its own event. Converting first and reconciling afterwards makes the difference between the rate you expected and the rate you got disappear into a rounding line — which is precisely the amount worth seeing. Why that gap matters is unpacked in our piece on high currency exchange fees.
A monthly close that fits on one page
Opening balance. Money received from acceptance, gross. Fees deducted. Refunds and disputes. Reserve added this month and reserve released this month, as two separate lines. Payouts sent, with failures shown separately. Conversions. Closing balance, which must equal what the bank shows on the last day. If it does, the month is closed; if it does not, the difference is already isolated to one of those lines.
Where the balance itself sits is described under business IBAN.
What to fix before it becomes a problem
Most reconciliation disasters are not accounting failures; they are naming failures. Decide the identifier format once, use it in every system, and never let a payout leave without one. Store the provider’s report every month rather than reading it in a browser — reports get updated, and a month you closed against a page you cannot reproduce is a month you cannot defend.
And separate the reserve in your own books from day one. It is the line that most often turns a healthy business into one that looks unprofitable on paper for the first six months.
Signs it is already broken
- The month closes «about right». A tolerance means the difference is not understood, only ignored.
- Somebody explains the numbers from memory. Knowledge that lives in one head is knowledge that leaves with them.
- Failed payouts are found by the recipient. If the complaint arrives before your report does, the report is not doing its job.
- The reserve appears as an expense. It is your money on a delay, and treating it as a cost distorts every margin you calculate.
In short
A month closes when three views agree: what you sold, what the provider reported, and what the bank shows. Watch the settlement term and the reserve as separate lines, give every payout a reference that survives, treat failed payouts as events rather than absences, and reconcile before converting. Do that and the merchant account stops being a mystery at month-end and becomes a source of numbers you can act on.