Month end close for iGaming demands more than a checklist. Build a controlled revenue, duty, PSP, and partner process that stands up to scrutiny on time.
← All insights
A late close in iGaming is rarely caused by one missed journal. It is usually the visible result of a deeper problem: finance is attempting to prove the economics of the business after the fact. A credible month end close for iGaming starts with a system that understands how money is actually earned, withheld, shared, settled, and reported across markets.
For an online casino or sportsbook, the close is not simply a process of posting expenses and comparing bank balances. Finance must move from player activity to gross gaming revenue, net gaming revenue, recognized revenue, gaming duty, affiliate costs, supplier revenue shares, payment-service-provider fees, and statutory reporting. If that logic lives across spreadsheets, data extracts, and tribal knowledge, the close will remain fragile no matter how disciplined the team is.
Generic ERP implementations often treat revenue as a straightforward sales transaction. That is the wrong starting point for gaming. An iGaming operator needs a controlled revenue waterfall that preserves the path from wagering data through to the ledger.
The relevant questions are operational and financial at the same time. What was staked? What was won? Which bonuses altered the effective gaming result? Which amounts are subject to gaming duty in each jurisdiction? What is owed to a game supplier, odds provider, or white-label partner? At what point does the resulting balance become recognized revenue under the operator's accounting policy?
These questions cannot be answered reliably with a single top-line GGR journal at month end. That may produce a number, but it does not produce an auditable explanation of the number. A finance team should be able to trace reported revenue back to defined source data, governed calculation rules, and approved adjustments.
GGR may be the commercial headline, but it is not automatically the figure finance should recognize as revenue. NGR can include deductions for bonuses, gaming duty, supplier costs, and other commercial arrangements, depending on the jurisdiction, contract, and reporting purpose. Recognized revenue may then follow a separate accounting-policy assessment.
That distinction matters at close. When GGR, NGR, and recognized revenue are calculated in disconnected files, teams spend days debating which version applies to which report. When the definitions and posting logic are configured in the ERP, close activity becomes validation rather than reconstruction.
Gaming duty is not VAT. It is not a standard sales-tax workflow with a different label. Its basis, thresholds, deductions, filing requirements, and timing can vary materially by jurisdiction and product type.
A controlled close separates three related but different activities: calculating duty from the applicable gaming base, accruing the liability correctly, and preparing a report that supports the filing. Combining these into one manual journal creates avoidable risk. It also makes it difficult to explain why a duty payable balance differs from a management P&L view of NGR.
The practical test is simple: can finance produce the calculation by market, entity, product, and period without rebuilding it? If the answer depends on a particular analyst’s spreadsheet, the process is not ready for expansion, transaction diligence, or an audit challenge.
PSP reconciliation is often the most labor-intensive part of the iGaming close because the transaction lifecycle is not cleanly aligned to the bank statement. Deposits, withdrawals, chargebacks, fees, reserves, rolling settlements, failed transactions, and timing differences all need a home in the ledger.
A bank balance alone does not establish that player cash, PSP clearing accounts, and payment fees are correct. Finance needs a controlled reconciliation between platform activity, PSP settlement data, bank movements, and the general ledger. Exceptions must be visible, assigned, and resolved rather than netted into an unexplained balance.
This is also where the trade-off between speed and precision becomes real. A high-growth operator may accept a defined materiality threshold for late PSP files, provided it books a transparent accrual and reverses it when settlement data arrives. That is very different from posting a broad plug to force the account to reconcile. The first approach preserves control. The second only shortens the calendar.
Affiliate commissions, game-supplier fees, odds and data costs, platform charges, and revenue-sharing arrangements frequently create the most commercially sensitive accruals. They affect margin, but their calculations can sit outside the financial system because contracts are complex and data is fragmented.
That creates an uncomfortable delay: commercial teams may know the estimated economics, while finance waits for an invoice or a manually prepared calculation. By the time the true cost arrives, management has already made decisions using incomplete profitability.
The answer is not to accrue every partner cost from a crude percentage. The answer is to model the relevant agreement logic with enough detail to calculate or estimate the cost consistently. Some arrangements are based on GGR, some on NGR, some include minimum guarantees, tiers, clawbacks, or market-specific exclusions. The ERP must support that complexity without turning each month into a bespoke exercise.
A good close does not ask people to check every transaction manually. It identifies where the economics depart from expected rules. That requires clear ownership, cutoffs, tolerances, and evidence.
For iGaming finance teams, the most useful exception views typically focus on four areas:
These are not merely control reports for auditors. They are the management signals that reveal a change in player behavior, promotional strategy, payment performance, supplier economics, or reporting logic. A close that surfaces exceptions early gives leadership a more accurate picture of margin while there is still time to act.
Most finance teams already have a calendar: day one for preliminary data, day two for reconciliations, day three for review, and so on. The calendar is necessary, but it cannot compensate for fragmented source data and poorly defined accounting logic.
The stronger approach is to build repeatable controls before the close date arrives. Daily interfaces should be monitored. Calculation rules should be version-controlled. Reconciliations should carry forward open items and ownership. Approval workflows should distinguish routine postings from high-risk manual adjustments. Consolidation should eliminate intercompany activity without requiring a separate reporting exercise.
For operators with multiple entities and regulated markets, multi-book accounting can also be decisive. Management reporting, local statutory requirements, and group accounting policy may require different treatment or presentation. Trying to manage those distinctions through end-of-month spreadsheet adjustments increases both effort and error risk.
The objective is not simply to announce results earlier. A faster, controlled close changes the quality of decisions available to the business. CFOs can see market and product profitability before the next promotional cycle. Tax and legal leaders can review gaming-duty exposure with evidence behind it. Commercial leaders can assess partner economics before renegotiations. CEOs and investors can rely on numbers that reconcile to the underlying operating model.
That is why Artio configures NetSuite around the iGaming revenue waterfall rather than asking operators to adapt their economics to generic financial workflows. The value is not another dashboard. It is a ledger and close process that can explain the business at the level regulators, auditors, boards, and management teams actually require.
The most useful question for the next close is not, “Can we finish two days earlier?” It is, “Can we explain every material revenue, duty, PSP, and partner balance without opening a rescue spreadsheet?” When the answer becomes yes, speed tends to follow.
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.