How does gaming duty work? Learn how iGaming operators calculate, accrue, report, and reconcile duty across markets without distorting revenue or margin.
← All insights
A casino can report strong gross gaming revenue and still generate a disappointing contribution margin once gaming duty, bonuses, revenue share, payment costs, and affiliate commissions are applied. That is why the question, how does gaming duty work, is not just one for tax teams. It is a finance, commercial, and systems question.
Gaming duty is a jurisdiction-specific levy on gambling activity. It is generally collected from the operator, not added as a tax at checkout for the player. The calculation may look simple in a single market, but it becomes materially harder when an operator runs multiple products, brands, currencies, licenses, and legal entities. The challenge is not simply calculating a percentage. It is determining the correct tax base, tax point, rate, reporting entity, and accounting treatment - then proving each number.
The most damaging mistake is to treat gaming duty like a conventional sales tax. It is not VAT, and it does not behave like a recoverable tax charged separately to a customer.
Gaming duty is commonly assessed on a measure of gambling yield. In many regulated markets, that starts with stakes less winnings paid to players: gross gaming revenue, or GGR. Some regimes permit specific adjustments, such as certain bonuses, jackpot contributions, or approved deductions. Others do not. Sportsbook, casino, poker, bingo, and betting exchange activity can also be subject to different bases and rates within the same territory.
That distinction matters because GGR is an operational metric, while gaming duty is a statutory liability. Net gaming revenue, or NGR, is a commercial and management-reporting measure that may deduct duty alongside bonuses, payment-service-provider fees, affiliate costs, and partner revenue share. Those measures should be connected, but they should never be conflated.
If the finance team uses NGR as the starting point for every tax calculation, it can unintentionally under-accrue duty. If it presents GGR as revenue without a clear policy for duty, it can obscure the real economics of a market. The correct treatment depends on the applicable accounting framework, legal arrangements, and local tax rules.
For an iGaming operator, the cleanest model begins with transaction-level activity and moves through a controlled revenue waterfall. A typical sequence is player stakes, less winnings, producing GGR. From there, the business calculates gaming duty according to each jurisdiction's rules. It then applies the commercial deductions needed to understand NGR and contribution margin.
The order is not cosmetic. It determines what finance, tax, and commercial leadership see when they ask whether a market is profitable.
Consider an online casino product in a market where duty is calculated on monthly GGR. A player deposits, wagers $100, and receives $92 in winnings. The operator has generated $8 of GGR. If the local gaming duty rate is 20% of the qualifying tax base and no adjustments apply, the duty liability is $1.60. The remaining amount is not automatically NGR. Bonuses, progressive jackpot funding, affiliate commission, payment processing, platform fees, and license-holder revenue share may all reduce the operator's economic return further.
A generic chart of accounts can record the $1.60, but it cannot decide whether the $8 belongs in the correct market, product, entity, period, and duty return. That requires the underlying revenue architecture.
Gaming duty calculations often vary on four dimensions: what activity is taxable, where it is taxable, which deductions are permitted, and when the liability arises.
A market may tax GGR from locally located players, locally licensed operations, or activity connected to a particular regulatory authorization. The location decision may rely on player residency, geolocation, registration data, or another statutory test. A cross-border operating model can therefore create multiple duty positions from a single technology platform.
Deductions require equally careful control. Promotional credits and free bets may be deductible in one jurisdiction but excluded in another. A jackpot contribution may be treated differently from a prize payout. Taxes on a betting exchange may follow commission income rather than stakes less winnings. Assuming that one NGR formula can support every gaming duty return is how operators create silent compliance exposure.
Duty is often reported monthly, but the tax point may not align neatly with cash movement, settlement timing, or the moment a customer places a bet. Open bets, unsettled wagers, canceled bets, chargebacks, late game-round adjustments, and jackpot events can all affect the period in which activity is recognized.
For sportsbook operators, the distinction between a bet placed and a bet settled is particularly important. Recording duty when a wager is accepted can produce a different result from calculating it when the event is settled. Neither approach should be assumed. The governing legislation and regulatory guidance determine the treatment.
Finance also needs a controlled approach to cut-off. At month-end, the duty accrual should reflect taxable activity through the reporting date, including data that arrives after close where the liability relates to the closed period. Without this discipline, the tax return, management P&L, and general ledger start telling different versions of the same month.
The arithmetic is rarely the issue. Fragmented data is.
Player platforms may hold wagers and winnings. A bonus engine may hold promotional cost. Payment providers hold cash settlement data. Affiliate systems hold commission calculations. Licensing, tax, and finance teams may each maintain their own market mapping. When these sources are joined in spreadsheets, the operator can produce a number, but not necessarily an auditable calculation.
The consequences show up quickly: duty is booked late, returns require manual reconciliation, tax teams cannot explain variances, and commercial teams assess market margin using incomplete costs. A rate change or new jurisdiction then becomes a major close-cycle event rather than a controlled configuration update.
The alternative is to make jurisdiction and product logic native to the financial model. Each relevant transaction needs attributes such as brand, legal entity, license, customer market, product vertical, currency, reporting period, and tax treatment. Duty rules can then be applied consistently to the correct population rather than reconstructed after the fact.
This is where a specialist ERP design differs from generic tax workflow. An iGaming ERP should preserve a traceable path from source activity to GGR, duty calculation, ledger posting, payable balance, tax filing support, and market-level profitability reporting. Artio builds that logic around how iGaming actually makes money, rather than asking finance teams to keep the revenue waterfall alive in spreadsheets.
The presentation of gaming duty in financial statements depends on the reporting framework and the facts of the arrangement. Operators should establish a documented accounting policy with their advisers, then configure systems to apply that policy consistently.
At an operational level, finance needs distinct visibility over at least three things: GGR, gaming duty expense or deduction as required by policy, and the duty liability payable to the authority. Those records should be reconcilable to the tax calculation and separate from cash paid. A payment made after period-end settles a liability. It does not determine the expense for the month.
Multi-book accounting can be relevant where local statutory reporting, group reporting, and management reporting require different views. The objective is not to create competing numbers. It is to make the basis for each number explicit and repeatable.
A well-designed close process also distinguishes expected duty from filed duty and paid duty. Variances should be explainable: late settlements, corrected player transactions, rule changes, data adjustments, foreign-exchange effects, or a genuine error. If finance cannot identify the cause, the operator has a control problem, not merely a reporting problem.
Gaming duty needs the same level of control as revenue recognition and cash reconciliation. The strongest operating model combines automated calculation with accountable review.
First, maintain a governed rules matrix for every jurisdiction, product, and license. It should record the current rate, tax base, permitted deductions, filing frequency, tax point, effective dates, and responsible owner. This is not a spreadsheet that one tax manager understands. It is controlled master data with a clear approval process.
Second, reconcile duty calculations to operational data and the general ledger before filing. The review should identify changes in GGR, deduction rates, effective duty rates, and liability movements. A material variance may be perfectly valid, but it should never be invisible.
Third, retain the drill-down. Auditors and regulators may ask how a reported amount was produced months after the return was filed. The answer should be a reproducible calculation supported by source data, not a chain of overwritten workbooks.
Finally, give commercial leadership a margin view that includes duty. A market can look attractive before tax and structurally weak after tax. Pricing, bonus intensity, affiliate terms, and market-entry decisions are better when gaming duty is visible at the same level as product and customer economics.
The practical question is not whether your team can calculate gaming duty this month. It is whether the calculation remains accurate, explainable, and commercially useful when you add the next market, license, brand, or acquisition. That is the point at which gaming duty stops being a tax line and becomes part of the operating model.
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 ›