iGaming payment reconciliation: ledger to bank
Payment reconciliation connects the player ledger, payment-provider records and bank movements. These records measure different events, so their totals will not always match immediately. The control must explain the differences and identify genuine errors or shortages.
iGaming Cyprus · Last updated:
Which records need to be connected?
A player deposit, a captured payment and a bank settlement are related but different events. Adyen’s settlement reporting illustrates transaction-level records and costs that can support reconciliation.
Define a common transaction-reference strategy and preserve provider identifiers. If finance cannot connect the player event to the provider event, manual investigation becomes slow and error-prone. Avoid relying only on amount and date where many transactions have the same value.
What are the three reconciliation layers?
Separate transaction matching from settlement matching and player-liability reconciliation. Each answers a different question.
| Layer | Question |
|---|---|
| Player to provider | Was the customer event recorded correctly on both sides? |
| Provider to bank | Did the net settlement arrive with the correct deductions? |
| Player liabilities to protected assets | Are relevant customer balances supported under the applicable arrangement? |
How should differences be classified?
Use categories with owners and resolution rules. Timing differences should remain visible until resolved rather than being permanently dismissed as normal.
- Authorised but not captured payments.
- Captured but not yet settled transactions.
- Fees and currency-conversion differences.
- Reserve withholding and releases.
- Refunds, reversals and chargeback movements.
- Duplicate, missing or incorrectly mapped events.
What does a worked example show?
Suppose a batch contains 10,000 units of settled deposits, 300 of fees, 1,000 withheld as a reserve and 500 of refunds. An illustrative net payout is 8,200 units. The 1,800 difference from gross deposits is not all an expense: its components have different accounting and liquidity implications.
The example is simplified. Use the actual provider’s report definitions, currency rules and settlement mechanics. Player liabilities also cannot be inferred directly from this payout calculation because gambling and withdrawals change the player ledger separately.
How do you make the control reliable?
Set a review frequency appropriate to the business and an ageing report for unresolved items. Use separate preparation and review responsibilities where practical, and define escalation for material or unexplained discrepancies.
Test duplicate webhooks, delayed reports and provider outages. The system should not credit a player twice because a message was retried. Preserve original events and correction history so the team can reconstruct what happened without silently editing balances.
Frequently asked questions
Not necessarily. Fees, reserves, refunds and timing can create legitimate differences that must be explained.
No. It also supports operational detection of missing events, errors and liquidity issues.
Sources and scope
This guide was prepared with AI assistance using the linked sources. It provides general information and practical preparation suggestions, not a legal opinion for a particular business. No personal professional review is claimed.
Get the right structure for your case
Book a free, no-obligation consultation. We’ll confirm the right Cyprus company + licence setup and a fixed fee for your business.