VAT and sales-tax engines handle consumer transactions. They don't touch the gaming-specific duty waterfall — applied per jurisdiction, on GGR, NGR or turnover, with rules that change by effective date — that actually decides what you owe regulators. We build that logic into NetSuite, inside the revenue pipeline.
Tell us your jurisdictions. We'll come back with a written read on where duty is modelled by hand today — and what that's costing you in risk and time.
The tools built for VAT and sales tax do that one job well. But gaming duty is a different problem entirely — a separate tax, with its own base, its own rate and its own filing rules in every market you operate. Model it by hand and you carry both the risk and the close-time cost every single month.
Duty lands on GGR in one jurisdiction, NGR in another, turnover in a third. A single rate field can't represent that.
Rate rises and regime changes apply from a date — sometimes mid-period. Manual models break exactly when the stakes are highest.
Duty calculated in spreadsheets, then journaled in. No lineage, no audit trail, and provision figures nobody can quickly defend.
This is the matrix a single VAT rate can't hold — and the one we model natively inside NetSuite, with each rule date-effective and every figure traceable back to source.
Illustrative. Bases, treatments and rates are configured to current regulations for your licensed markets and updated as regimes change.
Not a bolt-on connector — a calculation inside the GGR → NGR → revenue pipeline, so the number that hits the ledger is the number you can defend.
Gaming duty on GGR, NGR or turnover — whichever the regulator uses — modelled market by market within one chart of accounts.
Rate changes and regime shifts apply from their effective date. Re-runs are clean and idempotent; mid-period changes don't break the model.
Tax provision reporting and the figures regulatory filings need, produced from posted transactions — not reconstructed after the fact.
Every duty figure traces back to source data. Clean lineage and regulator-ready exports turn audit prep from a project into a posture.
"Gaming duty isn't a tax-tool problem. It's a revenue-pipeline problem — which is exactly where it belongs in the ERP."
Yours to keep, whether or not you ever work with us. We earn the next conversation.
Request a review →