Gaming operator audit readiness depends on traceable revenue, duty, and settlement data - not a last-minute evidence chase across systems during close.
← All insights
An audit request rarely exposes a single broken report. It exposes the distance between how an operator makes money and how finance records it. Gaming operator audit readiness means being able to explain every material movement from player activity to the general ledger, gaming duty return, partner settlement, and statutory accounts without rebuilding the story in spreadsheets.
For an iGaming operator, that standard is higher than having a clean trial balance. Auditors, tax advisers, regulators, lenders, and prospective buyers will ask different questions, but they all need the same foundation: reliable source data, defined accounting policies, controlled calculations, and a clear trail from transaction to reported result.
Teams often treat readiness as a document-gathering exercise. Finance pulls contracts, exports platform data, reconciles payment providers, and asks commercial teams to explain exceptional deals. That may get an audit over the line, but it does not create a repeatable control environment. It also makes the close slower, more expensive, and more dependent on the few people who know where the exceptions sit.
The better test is simple: can the finance team produce evidence at the same cadence as management reporting? If revenue by market, gaming duty, affiliate cost, PSP movements, and partner revenue share are calculated in controlled workflows every month, audit support becomes a byproduct of normal operations.
This matters particularly during expansion, acquisition, or financing. A business can grow quickly while its finance architecture remains local, manual, and dependent on spreadsheet logic. That gap becomes visible when a buyer asks for profitability by license, a tax authority challenges the duty basis, or auditors request support for revenue recognition adjustments made after month-end.
The defining issue is not whether the operator has an ERP. It is whether the ERP reflects the actual economics of gaming.
Gross gaming revenue is not automatically recognized revenue. Stakes, wins, bonuses, jackpot contributions, refunds, chargebacks, and promotional mechanics may all affect the route from GGR to net gaming revenue and ultimately to the revenue recognized in the accounts. The treatment can vary by product, jurisdiction, contract structure, and accounting policy.
When that logic lives outside the ledger, finance is left importing summarized journals and reconciling them after the fact. The numbers may tie in aggregate, but the audit trail is weak. A reviewer cannot readily see why a movement occurred, whether the same treatment was applied consistently, or which source records support it.
A controlled revenue waterfall should preserve both the calculation and its provenance. That means finance can trace a reported revenue balance back to the relevant platform output, legal entity, market, period, and adjustment type. It also means management can distinguish a change in player behavior from a change caused by accounting treatment, bonus strategy, or data correction.
The right treatment depends on the operator's facts. A sportsbook, casino, B2B arrangement, and managed-service model do not necessarily recognize revenue in the same way. Nor should a revenue-share agreement be forced into a standard template because a generic ERP was configured around a retail or SaaS model.
Audit-ready operators document the policy, then configure the rule. They define the recognized revenue basis, the treatment of unsettled activity and post-period adjustments, the ownership of review, and the evidence retained for each material judgment. The critical point is consistency between the policy, the transaction logic, and the journals posted to the ledger.
Gaming duty is often one of the clearest tests of whether an operator's finance stack understands iGaming. It can be calculated on different bases across jurisdictions, with distinct treatment for bonuses, free bets, player taxes, carry-forward losses, product categories, and filing periods. A tax figure that appears reasonable at group level can still be wrong market by market.
Treating gaming duty as a generic tax workflow creates avoidable risk. Finance may calculate it in a separate workbook, book a month-end accrual, and only reconcile the final return after submission. That creates timing differences that are difficult to explain and makes it harder to prove that the liability in the accounts reflects the underlying statutory position.
Instead, duty logic should be visible within the financial model. Each calculation should identify the jurisdiction, reporting period, taxable basis, rate, adjustments, and settlement status. Finance and tax leaders need the ability to reconcile the duty return to operational data and the general ledger without translating between several versions of the truth.
There is a trade-off. Centralizing calculation logic requires upfront design work and disciplined master data. But the alternative is usually more expensive: recurring manual review, late adjustments, and an audit process that relies on narrative explanation rather than system evidence.
A bank reconciliation confirms cash. It does not explain the full payment-service-provider position.
Gaming operators must account for deposits, withdrawals, fees, rolling reserves, chargebacks, failed transactions, wallet movements, and settlement timing. The PSP statement, player-wallet data, bank receipt, and ledger posting may each occur on different dates. If those movements are reconciled only at an aggregated level, open items can remain hidden until they become material.
An audit-ready reconciliation process identifies the lifecycle of each balance and assigns ownership for aged exceptions. Finance should be able to show why a settlement is outstanding, whether a reserve is recoverable, how fees are calculated, and whether chargeback exposure is accrued appropriately. The goal is not zero reconciling items. It is a controlled population of reconciling items with a known cause, age, and resolution path.
This is also where close discipline and commercial insight meet. PSP fees, settlement delays, and chargeback patterns affect margin and working capital. A process designed only to satisfy auditors misses information the CFO can use to improve payment economics.
Affiliate commissions, game-supplier shares, platform fees, white-label arrangements, and market-access agreements can all be material. They are also frequently governed by contracts with bespoke terms: tiered rates, minimum guarantees, clawbacks, exclusions, or calculations based on a defined version of NGR.
If commercial teams calculate settlements separately from finance, the business creates two risks. First, costs may be accrued late or inaccurately. Second, the definition used to pay a partner may not match the definition used in statutory reporting. Auditors will not accept “the commercial team approved it” as evidence that the accounting treatment is complete.
The control is straightforward in principle: contract terms should map to defined calculation rules, settlement output should reconcile to accrued expense or revenue, and exceptions should be approved with a documented reason. The implementation is more demanding because agreements are rarely uniform. That is precisely why generic configuration fails so often.
The details depend on the jurisdiction, audit scope, and materiality, but the recurring questions are consistent. Auditors want to understand who owns each key calculation, what data enters it, what can change after period close, and how finance knows it is complete and accurate.
They will commonly test access controls over financial postings and master data, review reconciliations and evidence of approval, inspect unusual journals, and trace reported balances to source records. They may also examine cut-off around unsettled bets, player liabilities, bonuses, PSP settlements, and gaming duty. In a group structure, they will look for consistency across entities while expecting local statutory and tax requirements to be respected.
Management should not wait for fieldwork to identify gaps. A quarterly internal review of the largest and most judgmental balances is more useful than an annual scramble. Ask whether each balance can be explained in three layers: the accounting policy, the system calculation, and the supporting transaction population. If any layer depends on one person's workbook, that is a control issue even if the number has historically been correct.
The practical starting point is a finance-process map, not a software feature list. Follow the major flows from player activity through revenue, duty, partner settlement, cash, liabilities, and reporting. Identify every handoff where data is summarized, altered, or rekeyed. Those points are where control design matters most.
Then prioritize the balances that combine materiality, judgment, and manual effort. For many operators, that means the GGR-to-NGR waterfall, gaming duty, PSP clearing accounts, affiliate and supplier accruals, and multi-entity eliminations. Define the source of record, calculation owner, approval evidence, posting logic, and reconciliation for each one.
A specialist ERP design makes these controls part of the operating model rather than a layer of audit documentation added afterward. At Artio, that means configuring NetSuite around the revenue waterfall and jurisdictional economics that drive an iGaming operator's books, not asking finance to bend those economics around generic workflows.
The objective is not to make auditors happy through more paperwork. It is to give the CFO a ledger that can answer harder questions at speed: what was earned, what is owed, where margin moved, and what evidence proves it. When those answers are available before the audit request arrives, readiness has become a commercial advantage.
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 ›