Choose a NetSuite consultant who understands iGaming revenue, gaming duty, PSP reconciliations, and multi-jurisdiction reporting before the build begins.
← All insights
A NetSuite consultant can configure entities, approval workflows, and standard reports. That is not the same as building an ERP that reflects how an iGaming operator makes money. For a regulated gaming business, the difficult work begins where generic implementations tend to stop: translating GGR into NGR and recognized revenue, calculating gaming duty correctly, settling commercial partners, reconciling PSP activity, and producing a defensible close across markets.
The distinction matters because finance teams inherit the consequences of weak design. They reconcile revenue outside the ERP, maintain duty workbooks that no one fully trusts, and rebuild profitability reports every month. The system may technically be NetSuite, but it is not yet the operating model finance needs.
An operator does not recognize revenue simply because a customer deposited funds or placed a wager. The route from player activity to financial reporting can include stakes, payouts, bonuses, jackpot contributions, chargebacks, payment costs, taxes, affiliate commissions, platform fees, and revenue-share arrangements. Each item has a commercial meaning and, often, a different accounting treatment.
A consultant who starts with a standard chart of accounts and asks later about gaming economics risks hard-coding the wrong assumptions. The better starting point is the revenue waterfall: how each product, market, and legal entity moves from GGR to NGR, then to recognized revenue and contribution margin. That design should support the way management actually asks questions. Which brands are profitable after duty? What did a market contribute after affiliate costs? Are sportsbook and casino margins moving for the same reason? What is owed to a platform partner at period end?
This is where specialist judgment matters. A bonus may reduce revenue, create a marketing cost, or require a more specific treatment depending on the product, contractual terms, and accounting policy. Revenue share may be calculated on a defined NGR base that differs from the statutory reporting base. An ERP should preserve those distinctions rather than flatten them into one convenient but misleading number.
Gaming duty is not a generic indirect-tax workflow with a different label. It is a jurisdiction-specific obligation tied to gaming activity, taxable bases, rates, deductions, filing periods, and legal entities. The operational challenge is not merely posting a tax journal. It is retaining a clear path from source transactions through the duty calculation to the ledger, return, and payment.
A capable iGaming NetSuite consultant will ask which activities are taxable in each market, what reduces the duty base, whether rates are tiered, and how adjustments are handled after a period closes. They will also establish controls around tax configuration changes. A rate update or revised interpretation should be visible, approved, dated, and traceable, particularly when an operator is under audit, preparing for a transaction, or expanding into new territories.
There is no single global template for this. A multi-market group may need common reporting dimensions while retaining local duty rules and local books. The aim is consistency in control, not false uniformity in tax treatment.
Month-end close exposes whether an ERP is genuinely fit for purpose. If finance must export transactions, manipulate spreadsheets, and post large manual journals to explain the numbers, the implementation has moved work rather than removed it.
Payment-service-provider reconciliation is rarely a simple bank match. Deposits, withdrawals, fees, reserves, timing differences, chargebacks, refunds, and settlement currencies can all create breaks between player-wallet data, PSP statements, bank receipts, and the general ledger. A consultant should define the matching logic, exceptions process, clearing accounts, ownership, and evidence required for review.
Automation is valuable, but only when the source data is reliable and exceptions remain understandable. An overly ambitious matching rule can conceal errors at scale. In some cases, a controlled exception queue is more valuable than a headline automation percentage.
Affiliate commissions, game-provider charges, platform revenue shares, and marketing arrangements often arrive after the period they relate to. The ERP needs a repeatable method to estimate, accrue, reverse, and true up those costs or liabilities. That requires the consultant to understand the contract calculation, data availability, timing, and materiality - not simply create a monthly journal template.
The same principle applies to player liabilities, jackpots, and other balance-sheet exposures. Finance should be able to explain what a balance represents, why it changed, and which underlying activity supports it.
Groups operating across jurisdictions may need local statutory books, a group reporting book, and adjustments for different accounting or tax requirements. NetSuite can support that architecture, but more books are not automatically better. Each book adds governance, reconciliation, and reporting considerations.
The right design gives corporate finance a credible consolidated view without forcing local teams to manage an unnecessary level of complexity. It also keeps intercompany activity, currency translation, and eliminations visible enough to support a fast close.
A consultant can hold certifications, know SuiteScript, and still be the wrong fit for an iGaming operator. Technical capability is necessary. It is not the test.
The more useful question is whether the consultant can challenge a vague requirement using the language of your finance operation. When a CFO says, We need market profitability, the response should not be a promise to build a dashboard. It should be a discussion about revenue definitions, allocation rules, duty treatment, shared costs, reporting currency, and the decision the dashboard must support.
Likewise, a request to integrate a gaming platform should trigger questions about data grain, timing, correction events, product mappings, entity ownership, and reconciliation controls. An integration that delivers daily summarized journals may suit one operator. Another may need transaction-level detail for auditability, dispute investigation, or granular commercial reporting. It depends on risk, volumes, system maturity, and the claims management wants the numbers to support.
The strongest engagements begin with finance design, not screen configuration. Before building workflows, the consultant should map the revenue waterfall, statutory obligations, key partner settlements, source systems, close calendar, and reporting requirements by stakeholder. CFOs need control and cash visibility. Commercial leaders need reliable unit economics. Tax and legal teams need defensible treatment by jurisdiction. Operations and IT need interfaces that can be monitored and changed safely.
That discovery should produce decisions, not a collection of generic requirements. Which system is the source of truth for each measure? When is revenue considered final? Which adjustments require approval? How are late source-data changes handled after close? What reconciliation proves completeness between the gaming platform and NetSuite?
Configuration then becomes an expression of those decisions. The chart of accounts, segments, saved searches, workflows, integrations, and reporting structure work together because they were designed around the same financial model. This is the difference between a system that looks organized in a demonstration and one that remains usable when a new market, PSP, brand, or acquisition enters the group.
Artio is boutique by design because this work benefits from direct access to partners who can discuss revenue recognition, gaming duty, and system architecture in the same conversation. For an operator, that reduces the gap between what finance needs and what the build team delivers.
Ask the consultant to explain how they would model your GGR-to-NGR bridge, not just how they would configure NetSuite. Ask how PSP clearing and settlement differences would be reconciled. Ask what evidence would support a gaming-duty figure and how a late adjustment would flow through the books and reports.
Pay close attention to the questions they ask back. A specialist will want to understand market-specific tax rules, product economics, contracts, data sources, close pain points, and the reports your board relies on. A generalist may move quickly to modules, project plans, and templates before establishing what the numbers mean.
Also examine accountability after go-live. iGaming finance changes constantly: new jurisdictions, revised supplier terms, regulatory requirements, and shifting product mix all place pressure on the original design. The right relationship includes informed challenge and ongoing refinement, not a handover followed by a support queue that lacks commercial context.
The practical standard is simple: choose a consultant who can make the ERP explain the business as it is actually run. When finance can trace a reported number from player activity to ledger, tax position, partner settlement, and management decision, growth becomes easier to govern.
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.