iGaming revenue share accounting needs more than a partner payable. Build auditable NGR, tax, settlement, and profitability logic across markets globally.
← All insights
A revenue-share deal can look simple on a commercial term sheet: calculate NGR, apply a percentage, settle the balance. In an iGaming finance function, that apparent simplicity disappears quickly. iGaming revenue share accounting sits downstream of the full revenue waterfall, yet it can change reported profitability, accrued liabilities, tax positions, partner trust, and the speed of month-end close.
The failure point is rarely the percentage itself. It is the absence of a controlled definition of the revenue base, applied consistently across player activity, bonuses, gaming duty, payment costs, market rules, and partner contracts. A generic ERP can record a payable. That is not the same as accounting for the commercial economics that produced it.
Revenue share is often treated as a single calculation when it is actually a set of policy decisions. Is the agreement based on GGR, NGR, deposits, first-time depositors, or a hybrid model? Are bonuses deducted before the revenue-share percentage is applied? Does the contract permit gaming duty, jackpot contributions, chargebacks, fraud losses, or payment-service-provider fees to reduce the base?
Those questions are not administrative detail. They determine who bears the cost of a market and whether finance, commercial, and the partner are using the same number when they discuss performance.
Take an affiliate agreement based on NGR. If NGR is defined as GGR less bonuses and gaming duty, the calculation may be straightforward in one jurisdiction. Move into a market with a different duty basis, a local jackpot levy, or a distinct promotional treatment, and a global spreadsheet formula can quietly become wrong. The result may be an overstated affiliate liability, an under-accrual, or a dispute weeks after the period has closed.
The same applies to platform, game studio, white-label, and strategic distribution arrangements. Each can use a different revenue base, settlement currency, reporting cadence, minimum guarantee, or adjustment process. Treating them as variations of accounts payable creates a finance operation that is busy but not controlled.
A defensible revenue-share model begins with the underlying revenue waterfall. For most operators, that means establishing a traceable path from wagers and wins through GGR, deductions, NGR, partner share, and recognized revenue or expense treatment where applicable.
The exact sequence depends on the operator's contracts and accounting policies. It should never be copied from a generic template. Gaming duty is not VAT, and an affiliate commission is not automatically the same kind of cost as a game supplier's contractual share of gaming proceeds. The legal arrangement, the economic substance, and the applicable reporting framework matter.
At a minimum, the ERP should preserve the components of the calculation rather than importing one net settlement number. Finance needs to see the gross activity, eligible deductions, contractual rate, calculated share, manual adjustments, prior-period true-ups, invoices or self-bills, payments, and remaining balance. Without that lineage, there is no efficient way to explain a movement to an auditor, a commercial lead, or the counterparty.
There is no universal NGR. There are only contractual definitions of NGR, shaped by market-specific operating economics.
One partner may share in GGR less bonuses and duty. Another may exclude certain player segments, use a negative carryover provision, or cap deductible acquisition costs. A third may earn a tiered rate based on monthly volume, with a retrospective rate change once a threshold is reached.
These definitions should be configured at the contract level, with effective dates and clear version control. If a rate changes on July 1, finance should not need to remember which worksheet tab applied before and after the amendment. The system should retain the original agreement logic, apply the new logic prospectively or retrospectively as required, and produce a calculation that can be reconstructed later.
That discipline also protects commercial teams. A partner manager should be able to assess the margin effect of a proposed deal before signing it, not discover after launch that a seemingly attractive rate applies to a broader NGR base than expected.
These are related workflows, but they are not the same thing. The calculation determines what is economically owed for a period. The accrual records the obligation in the appropriate accounting period. Settlement handles the invoice, self-bill, credit note, payment, offset, and any dispute.
Combining all three in one manual process is a common source of close delays. The team waits for partner documentation before recording an accrual, even though the underlying player and transaction data already supports a reasonable estimate. Or it books an invoice without reconciling it to the operator's own calculation, allowing differences to accumulate in suspense accounts.
A better model records an automated or controlled accrual from the period's activity, then reverses or clears that accrual as approved partner documentation is received. Variances should be visible by partner, market, product, and accounting period. Small rounding differences may be routine. A recurring variance driven by bonus treatment or duty timing is a process issue that needs resolution.
CFOs need more than an accurate monthly payable. They need to know whether a market, channel, game vertical, or partnership is profitable after the costs that genuinely belong to it.
That requires revenue-share accounting to retain commercial dimensions. If a supplier share is posted only to one consolidated expense account, the finance team may know total cost but not which casino brand, jurisdiction, game category, or acquisition channel generated it. The operator loses the ability to compare contribution margin across markets or price deals with confidence.
A well-designed chart of accounts and dimensional model can attribute partner share to the right legal entity, market, brand, product, channel, and contract. This does create a trade-off: more dimensions bring more reporting power, but uncontrolled dimensionality makes maintenance painful. The answer is not to strip out the detail. It is to define a small set of dimensions that align with how leadership actually makes decisions.
For a multi-market operator, jurisdiction is usually non-negotiable. Brand and product often are too. Campaign-level tagging may be valuable for affiliate programs, but only if source data is reliable enough to support it. Accounting design should follow the decision model, not a theoretical desire to report on everything.
Auditability does not mean making finance document every click. It means the calculation can be explained, reproduced, and approved without relying on one person's local knowledge.
The strongest controls are built into the process. Source data should be reconciled to the gaming platform and, where relevant, to PSP and player-liability movements. Contract rules should have effective dates, owners, and approval workflows. Calculation outputs should be locked once posted, with later changes recorded as adjustments rather than overwritten history.
Exception reporting is equally valuable. Finance should be able to identify a partner with an unusual rate movement, negative NGR, a missing data feed, an accrual that differs materially from settlement, or a contract approaching a guaranteed minimum. These are the exceptions that deserve review. A controller should not have to inspect every agreement manually to find them.
Multi-book requirements add another layer. The operational calculation may be common across the group, while statutory reporting, currency treatment, intercompany entries, and presentation differ by entity or reporting basis. A scalable ERP architecture keeps the economic event consistent while supporting the accounting outputs each book requires.
Most ERP platforms can process journal entries, vendor bills, and allocations. The problem begins when the configuration assumes that iGaming revenue is conventional sales revenue and that partner economics belong in a generic procurement workflow.
That approach pushes the hard work outside the ledger. NGR logic lives in spreadsheets. Gaming duty is handled through manual journals. Partner reports arrive as PDFs or exports that cannot be matched to the internal calculation. Finance spends the first week of every month explaining numbers instead of analyzing them.
The cost is not limited to labor. Fragmented logic makes diligence harder during an acquisition, weakens confidence in market profitability, and slows decisions on commercial terms. It can also leave legal, tax, and finance teams arguing from different versions of the same metric.
Artio's position is deliberately narrow: iGaming is not a vertical to be adapted to after implementation. The revenue waterfall, gaming-duty treatment, revenue-sharing rules, and settlement controls should be native to how the NetSuite environment is configured from the start.
The right design does not assume every future market will use the same deal mechanics. It makes change controlled. New jurisdictions, suppliers, affiliate models, currencies, and reporting obligations should be added through governed configuration, not a new spreadsheet workaround.
Start with the contracts that create the greatest financial exposure or close burden. Define their revenue bases precisely, map the required source data, agree the accounting treatment, and build a repeatable accrual-to-settlement process. Then use those patterns to bring the rest of the portfolio under control.
The practical test is simple: when a partner challenges a statement, when a tax authority asks how duty affected NGR, or when leadership asks which market actually generated margin, finance should be able to answer from the system of record. That is when revenue share stops being a monthly reconciliation exercise and becomes dependable commercial intelligence.
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.