Audit partner settlement statements with a controlled iGaming workflow that protects NGR, revenue share, gaming duty, and close confidence today.
← All insights
A partner settlement can look commercially reasonable and still be financially wrong. That is the risk when operators audit partner settlement statements from a spreadsheet, a PDF, and a late export from the player platform. By the time finance identifies a disputed deduction, duplicated player, incorrect jurisdiction, or stale commission tier, the cash may have moved and the month-end close has become a negotiation.
For iGaming operators, settlement is not a back-office payment exercise. It is the point where commercial terms, player activity, bonus treatment, gaming duty, revenue recognition, and cash control meet. A credible audit needs to prove each number from source activity through to the general ledger - without rebuilding the calculation manually every month.
Most settlement issues do not start with arithmetic. They start with ambiguous definitions and disconnected data.
An affiliate may be paid on NGR, while a white-label or content supplier has a revenue-share agreement based on a different definition of GGR. A sportsbook partner may exclude particular promotional costs. A market-access arrangement may calculate its share after gaming duty, while another is calculated before it. Each outcome can be contractually valid. The problem is allowing the calculation logic to live only in the heads of commercial staff or in an ungoverned workbook.
The second problem is timing. Player transactions, bonus releases, chargebacks, payment reversals, jackpot contributions, and manual adjustments do not always land in the same accounting period. If a statement is prepared from a snapshot with no controlled cutoff, finance cannot explain why the partner balance differs from the revenue and liability position in the ledger.
Then there is jurisdiction. Gaming duty is not VAT, and it is not a single global deduction. The applicable tax base, rate, reporting period, and treatment of bonuses can vary by market and product. A settlement model that applies one broad deduction across the portfolio may produce a plausible total while misstating partner economics in several jurisdictions.
A settlement statement should do more than present a net amount payable. It should expose the calculation path well enough for finance, commercial, tax, and an external auditor to reach the same result from the same controlled data.
At a minimum, the statement needs a clear settlement period, legal entity, jurisdiction, product, currency, partner agreement, and version of the commercial terms applied. It should identify the population of activity included and the source systems used. Those fields sound basic, but they prevent a common failure: comparing a partner’s all-market report with an internal statement limited to one licensed entity or cutoff date.
The financial bridge should move from the agreed top-line measure to the final payable or receivable amount. Depending on the agreement, that may mean GGR (stakes less player winnings) less approved bonus costs, gaming duty, payment costs, chargebacks, jackpot funding, or other specifically permitted deductions. Each deduction should be separately visible. A single line labelled “net revenue adjustment” is convenient, but it is not auditable.
The statement should also show the applicable commission or revenue-share rate, including tier thresholds and whether they are assessed monthly, quarterly, by brand, or across a group. If there is a minimum guarantee, fixed fee, carryforward loss, clawback, cap, or true-up, it needs its own calculation trail. These are often where a commercially correct agreement becomes operationally inconsistent.
Finally, every statement needs a controlled status: draft, reviewed, approved, disputed, or settled. Finance should be able to see who prepared it, who approved it, when it was locked, and what changed after initial preparation. A number is not controlled simply because it was exported from a system.
The right audit method follows the money and the accounting entry, rather than testing only the final statement total.
Build a settlement rulebook from the executed contract and any approved amendments. Define the exact revenue basis, eligible products and territories, excluded activity, tax treatment, currency conversion method, timing rules, payment terms, and dispute process.
This is not legal administration. It is the specification for the financial calculation. Where wording is unclear, finance and commercial should agree an operational interpretation before a statement is issued. Reusing last month’s formula is not evidence that the formula reflects the current agreement.
Test that the player and transaction population feeding the settlement agrees to the controlled source data. Reconcile deposits, stakes, wins, voids, bonuses, withdrawals where relevant, chargebacks, and manual adjustments according to the agreement’s definition of revenue.
The appropriate level of detail depends on materiality and contract structure. For a high-volume affiliate, an aggregated reconciliation by market, brand, and product may be practical, with transaction-level drilldown available for exceptions. For a smaller but strategically significant white-label arrangement, a deeper player-level review may be justified. The control principle is the same: every aggregate must be traceable to an immutable underlying population.
Pay particular attention to late-posting events. If a chargeback or void is recognised after settlement, determine whether the contract allows a subsequent-period adjustment, a clawback, or no recovery. That policy should be systematic, not decided partner by partner after the fact.
Once the population is complete, independently reperform the settlement waterfall. Validate the rates, tier boundaries, currency conversions, and deductions against the rulebook. Test boundary conditions: the first transaction after a tier is crossed, the first day of a new month, a player moving between jurisdictions, and a negative-NGR period.
Negative balances are especially revealing. Some agreements permit losses to carry forward against future revenue share; others reset monthly. Some cap a partner’s exposure to bonus cost or payment fees. Applying a standard rule across all partners creates avoidable disputes and can distort accrued liabilities.
The settlement outcome must reconcile to the ledger entries for revenue, gaming duty, commission expense or revenue-share expense, accrued liabilities, accounts payable or receivable, and cash settlement. If the statement says a partner is owed €500,000 but the ledger holds a €430,000 accrual, finance needs a documented explanation before close.
This is where generic ERP configuration usually falls short. Partner statements cannot sit outside the revenue waterfall as a monthly spreadsheet exercise. The rules that produce NGR and gaming duty should also feed the payable, accrual, and management reporting logic. Otherwise, each close becomes a separate reconciliation between commercial reporting and statutory accounting.
The most effective control environment combines automated rules with deliberate human review. Automation should calculate repeatable contract logic, preserve source references, route exceptions, and lock approved statements. It should not silently decide how to interpret an unclear clause or a new commercial concession.
Four controls make the largest difference:
The exact design depends on transaction volumes, partner concentration, and regulatory footprint. A growing operator may begin with structured review workflows and controlled imports. A multi-market group should usually move toward a native settlement engine that calculates partner shares from source data, where jurisdiction, product, entity, and contract dimensions are retained through the entire calculation.
An auditable statement is also a management instrument. Once the settlement logic is controlled, leaders can see profitability by partner after gaming duty, bonus cost, payment expense, and revenue share. Commercial teams can test whether a high-volume affiliate is genuinely profitable. Tax teams can isolate market-level duty exposure. Finance can forecast accruals before the statement arrives.
That visibility matters during expansion, fundraising, acquisition diligence, and any discussion about valuation. Buyers and investors do not only ask whether reported revenue is growing. They ask whether revenue is repeatable, whether liabilities are complete, and whether partner economics can be explained without a month-long forensic exercise.
Artio’s view is simple: the ERP should reflect how iGaming makes money, not force finance to reconstruct that logic after the event. When partner rules, gaming-duty treatment, revenue waterfalls, and ledger postings are connected, the statement becomes a controlled business record rather than a monthly argument.
The practical next step is to select one material partner and trace its last three settlements from contract clause to source activity, calculation, journal, and cash payment. Any break in that chain is not just an audit finding. It is a clear design requirement for the finance system you need next.
The blog is the long read. For your actual numbers — the engine, gaming duty, the close — book a short call with a partner who would configure it.
Independent, objective advice. We reply within one business day.
Prefer to talk? Email [email protected] · call us ›