Gaming Duty and Levy Calculation
iGaming operators calculate duty and regulatory levies against gross gaming revenue, but the actual calculation is genuinely complex — different duty rates apply to different product types (sports betting, casino, poker), different jurisdictions have different tax bases and rates, and free bets, bonuses and promotional credits need specific treatment that varies by regulator. Getting this calculation slightly wrong, especially at scale across multiple licensed markets, isn't a minor bookkeeping issue — it's the kind of discrepancy regulators actively audit for, and an inconsistent or unexplainable calculation methodology is itself a compliance red flag regardless of whether the final number happens to be close to correct.
STARTING PRICE
From €799
Complex tier · Multi-system orchestration, custom logic, and higher-volume or higher-risk processing.
Get a quote →Saves roughly 1-3 days per filing period for a multi-jurisdiction operator, plus substantially reduced regulatory audit risk.
How the automation works
We build a duty and levy calculation engine that encodes the specific rules for each jurisdiction and product type you operate in — the tax base definition, applicable rate, treatment of free bets and bonuses, and any reporting-period-specific adjustments — and calculates each obligation directly from underlying gross gaming revenue transaction data with a full traceable audit trail. Every duty figure can be decomposed back to the specific bets, wins and promotional adjustments that produced it, so if a regulator queries a number, the supporting calculation is immediately available rather than requiring a manual reconstruction under audit pressure.
Process flow
- 01
Encode jurisdiction and product rules ai
Duty rates, tax base definitions and bonus/free-bet treatment rules are encoded per jurisdiction and product type, reflecting each regulator's specific requirements.
- 02
Pull GGR transaction data integration
Gross gaming revenue transaction data — stakes, wins, bonuses, free bets — is pulled from your gaming platform for the relevant reporting period.
- 03
Calculate duty by jurisdiction and product ai
Duty and levy obligations are calculated separately by jurisdiction and product type according to each regulator's specific rules, not a single blended rate.
- 04
Reconcile against platform reporting ai
Calculated figures are cross-checked against the gaming platform's own GGR reporting to catch any data or calculation discrepancy before filing.
- 05
Prepare traceable filing package output
A filing-ready duty calculation is prepared with full traceability back to underlying transactions, ready for regulatory submission and audit support.
Inputs
- Gross gaming revenue transaction data by product
- Jurisdiction-specific duty rate and tax base rules
- Free bet and bonus/promotional data
- Regulatory filing calendar and requirements
Outputs
- Traceable duty and levy calculation by jurisdiction
- Reconciliation against platform GGR reporting
- Filing-ready regulatory submission package
- Duty obligation forecast by jurisdiction
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Free bets and promotional credits have genuinely different tax treatment across regulators — some treat the cost of the free bet as deductible from taxable GGR, others don't, and applying the wrong jurisdiction's treatment is one of the most common and material calculation errors in multi-market gaming duty reporting.
- Tax base definitions differ meaningfully between jurisdictions — some calculate duty on gross stakes, others on net gaming revenue after payouts, others with specific adjustments for jackpot contributions or player bonuses — treating all jurisdictions as using the same base definition produces systematically wrong figures for whichever ones don't match your default assumption.
- A discrepancy between your internally calculated duty figure and your gaming platform's own GGR reporting needs investigation and resolution before filing, not silent acceptance of whichever number is more convenient — regulators can and do request platform-level data to cross-check submitted duty calculations.
- Product type classification (is a particular game categorized as casino or as a skill-adjacent product, is a specific bet type sports betting or a different regulatory category) directly determines which duty rate applies, and misclassification at the product level, not just at the calculation level, is a subtle but material source of error.
Frequently asked questions
Can this handle different duty rules for different jurisdictions we operate in?
Yes, this is built specifically to encode each jurisdiction's own tax base definition, rate and bonus treatment rules separately, rather than applying one generalized calculation approach across all markets.
How does this handle free bets and bonus treatment?
Free bet and promotional credit treatment is encoded per jurisdiction's specific rules, since some regulators allow deducting the cost from taxable revenue and others don't — applying the wrong treatment is a common source of material calculation error.
What happens if our calculation doesn't match the gaming platform's own reporting?
Any discrepancy is flagged and needs to be reconciled and understood before filing, rather than silently resolved by picking whichever figure looks more favorable, since regulators can and do cross-check submitted duty figures against platform-level data.
Does this file directly with the regulator?
It prepares a traceable, filing-ready calculation package; final review and actual regulatory submission goes through your compliance team, given the regulatory accountability involved in gaming duty filings.