Understand the iGaming accrual accounting process, from GGR and gaming duty to partner costs, PSP timing, close control, and auditable reporting at scale.
← All insights
A sportsbook can report a strong final weekend of the month while its bank receipts arrive in the next month, affiliate invoices land after close, and gaming duty is calculated on a jurisdiction-specific basis. If finance waits for every invoice, statement, and settlement file before posting the period, the close never truly closes. If it estimates without a clear basis, the numbers may close quickly but fail under audit.
That is why the iGaming accrual accounting process is not a standard accounts-payable exercise. It is the control framework that brings wagering activity, revenue waterfalls, statutory obligations, and commercial partner costs into the right accounting period - even when the underlying cash and documentation move later.
For operators across multiple brands and markets, accruals determine whether management reporting reflects the economics of the business or merely the timing of supplier paperwork. They affect NGR, margin by market, gaming-duty liabilities, affiliate profitability, and the credibility of every board pack built on top of them.
Accrual accounting recognizes income when earned and expenses when incurred, rather than when cash is received or paid. That definition is simple. Applying it to iGaming is not.
The core challenge is that a player's staking activity, the settlement of a wager, a payment service provider's cash movement, and a supplier's invoice can all occur on different dates. Those events must be distinguished rather than collapsed into a single revenue or cost entry.
A controlled process starts with the gaming transaction layer. For casino, that may include stakes, wins, bonuses, reversals, jackpot contributions, and jackpot payouts. For sportsbook, it must account for unsettled bets, voids, cash-outs, late event settlements, and bet corrections. The objective is to calculate GGR accurately for the reporting period before finance applies deductions such as gaming duty, revenue share, affiliate commission, and other direct costs to arrive at a meaningful view of NGR.
This is where generic ERP design often fails. Posting a single monthly revenue journal from a data warehouse may produce a headline revenue number, but it does not necessarily preserve the logic needed to explain the number by legal entity, brand, product, country, license, or tax treatment. In iGaming, that granularity is the accounting.
An accrual should never be a substitute for a defined revenue waterfall. Finance needs a governed sequence that answers three questions: what happened in the period, what does the operator owe because of it, and what amount is still unbilled or unpaid at close?
Start with settled gaming activity and calculate GGR according to the operator's accounting policy and market rules. Then identify deductions that are variable consequences of that activity. Gaming duty is one of the most material. It is not VAT, and it should not be treated as a generic sales-tax calculation. The tax base, rate, thresholds, credits, and filing cadence can differ materially between jurisdictions.
Next come commercial arrangements. An affiliate agreement may pay a fixed CPA, a share of NGR, a hybrid fee, or a tiered amount based on player value or volume. A game supplier may receive a percentage of GGR, NGR, or a specifically defined adjusted measure. A platform provider may charge minimum commitments, usage-based fees, or revenue share. Each arrangement needs its own calculation rules, effective dates, exclusions, and entity allocation.
Only after those rules are applied can finance determine the accrual. The journal is the accounting expression of a commercial and regulatory calculation. It is not the calculation itself.
The timing of revenue recognition depends on the product and the operator's policy. A settled casino game may be recognized immediately, while an open sportsbook bet represents a position that requires specific treatment until the underlying event settles. Bonuses, free bets, and promotional credits add another layer, particularly when their accounting treatment differs by product or jurisdiction.
The practical point is consistency. Finance should not recognize a favorable outcome early while delaying an unfavorable adjustment until a later close. A documented cut-off policy, supported by source-system timestamps and controlled exception handling, protects both the P&L and the audit trail.
Gaming duty is usually calculated from source data before the statutory return is finalized. That does not make the accrual optional. The operator has incurred the obligation through its gaming activity and needs to recognize it in the same period as the related GGR. When final returns differ from estimates, finance should post a transparent true-up and investigate material variances.
Affiliate commissions deserve the same rigor. A late affiliate invoice does not mean the cost belongs in the following month. If player activity generated the commission in the current period, the current period should carry the expense and accrued liability. The same principle applies to supplier revenue share, game royalties, odds and data fees, and platform charges where the value has been consumed but the invoice has not yet arrived.
Payment processing is more nuanced. PSP fees may be charged at authorization, deposit, withdrawal, settlement, or payout, depending on the commercial agreement and payment method. Chargebacks, reserves, rolling holds, and foreign-exchange effects can further separate reported cash from the underlying economics. An operator that books PSP costs only from bank statements will routinely misstate both period expense and cash clearing balances.
There is also a trade-off. A highly detailed daily accrual model may provide precision, but it can become expensive to maintain if source data is unstable or contract logic is poorly governed. For some costs, a monthly calculation using validated operational data is sufficient. The right level of detail depends on materiality, volatility, contract complexity, and the reporting decisions the operator needs to make.
A credible close process begins before month-end. Finance, commercial, tax, and operations need agreed ownership of the data and rules that feed each material accrual. If affiliate terms sit in emails, gaming-duty assumptions sit with external advisers, and settlement data sits in separate product systems, the close depends on individual memory. That is not a control environment.
The most effective operating model creates a defined accrual register for each material category. It records the calculation owner, data source, contract or statutory basis, accounting treatment, posting entity, approval threshold, and expected reversal or true-up date. This gives controllers a practical way to see what has been booked, what remains estimated, and where risk sits.
At close, source data should be locked to an agreed cut-off. Finance calculates or imports the accrual, compares it with prior periods and operational drivers, and routes material movements for review. Variance analysis should be commercially literate. A movement in affiliate accrual could reflect better player acquisition, a change in deal mix, a tracking issue, or an incorrect NGR definition. The journal alone cannot answer that question.
After posting, balance-sheet accounts require reconciliation. Accrued gaming duty should reconcile to draft returns or tax calculations. Affiliate and supplier accruals should reconcile to contract-level schedules and subsequent invoices. PSP clearing and fee accruals should reconcile to processor reports, settlement files, and bank activity. This is how finance prevents the accrual ledger from becoming a collection of aged estimates that nobody owns.
Scaling operators need to establish which legal entity earns the revenue, incurs the duty, contracts with the supplier, and pays the liability. Those answers do not always align. A shared-services entity may pay a vendor while an operating entity consumes the service. A brand may span markets with different tax bases. Intercompany charges may be needed, but they should follow the underlying economics rather than act as a late-close balancing mechanism.
A properly configured ERP can retain these dimensions in the transaction and accrual logic: entity, subsidiary, market, brand, product, license, cost category, and tax treatment. With multi-book accounting where required, finance can also support local statutory reporting alongside group reporting without rebuilding the same calculations in spreadsheets.
That is the difference between automation and controlled automation. Importing journals faster does not solve an unclear revenue definition. A system configured around how iGaming makes money can calculate, post, reverse, reconcile, and report using the same governed rules.
A mature iGaming accrual process does not eliminate estimates. It makes them visible, repeatable, supportable, and easy to true up. The close becomes faster because finance is no longer chasing fragmented files, yet controls improve because every material number has a source, rule, owner, and review trail.
For leadership, the payoff is more than cleaner compliance. Market-level profitability becomes credible enough to guide bonus strategy, affiliate terms, PSP routing, supplier negotiations, and expansion decisions. Artio configures NetSuite around that financial reality: GGR to NGR, recognized revenue, statutory liabilities, and the commercial costs that determine actual margin.
The useful test is simple: when a board member asks why NGR moved in a market, can finance trace the answer from the reported number back to settled play, contractual terms, tax logic, and reconciled liabilities? If the answer still requires a spreadsheet hunt, the accrual process has work left to do.
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.