Affiliate commission accounting in iGaming needs auditable NGR logic, accruals, controlled settlements, tax treatment, and real partner profitability.
← All insights
Affiliate commission accounting in iGaming becomes difficult the moment a commercial deal meets the revenue waterfall. An affiliate sees a share of NGR. Finance needs to know which deductions create that NGR, when the liability arises, whether gaming duty is included or excluded, and how the charge lands by brand, market, product, and legal entity. A monthly payout report cannot answer those questions on its own.
For an operator, affiliate commissions are not simply a marketing cost. They are a variable acquisition cost tied to player behavior, jurisdictional tax rules, payment outcomes, bonuses, and contract terms. If that logic sits in spreadsheets between commercial reporting and the general ledger, month-end close becomes a reconciliation exercise rather than a controlled accounting process.
The first accounting question is commercial: what does the affiliate agreement define as net gaming revenue? There is no universal answer. One agreement may calculate commission from GGR less player winnings, bonuses, chargebacks, payment fees, gaming duty, and jackpot contributions. Another may exclude only bonus costs and gaming duty. CPA, fixed-fee, hybrid, negative carryover, and tiered agreements add further variation.
That definition must be modeled as a controlled calculation, not recreated manually for each settlement. Finance should be able to trace every commission amount back through the underlying revenue waterfall: stakes, wins, GGR, permitted deductions, contractual NGR, commission rate, and any minimum guarantee or adjustment.
This is where generic ERP configuration usually fails. A standard expense workflow can record an invoice. It cannot determine whether a 35% rev-share calculation should use NGR before or after gaming duty in Italy, whether a casino bonus is deductible under a specific agreement, or whether sportsbook turnover belongs to the same deal. iGaming is not a vertical that can be handled with a generic vendor bill template. The commercial economics have to be native to the financial model.
Gaming duty is frequently the source of the largest commission discrepancies. It may be deductible under one affiliate contract, excluded under another, and calculated from a tax base that differs from the operator's internal management view of NGR. The result is that a commercially plausible number can still be contractually wrong.
Finance, tax, and commercial teams need one approved interpretation for each market and agreement. That interpretation should identify the tax basis, the deduction order, the legal entity responsible for the liability, and the point at which the amount becomes sufficiently certain to accrue. The goal is not to force every agreement into one formula. It is to manage legitimate variation without creating uncontrolled variation.
Affiliate payments often happen after the revenue period closes. That does not mean the cost belongs in the payment month. Where players generated qualifying NGR in March, the associated affiliate commission normally needs to be accrued in March, subject to the terms of the arrangement and the reliability of the underlying data.
An effective accrual process calculates estimated commission from finalized or controlled operational data, posts the expense to the correct period, and reverses or clears the accrual against the approved affiliate settlement. The variance between accrued and settled commission should be visible, explained, and retained. A small variance caused by late chargebacks is different from a recurring gap caused by a flawed NGR definition or missing player exclusions.
The accounting design also needs to reflect the operator's reporting requirements. A group may want affiliate cost shown by acquisition channel and market for management reporting, while statutory books require posting by legal entity and local currency. Multi-book accounting can support different reporting treatments, but it cannot repair a calculation that has not been structured correctly at source.
Many affiliates self-bill, submit invoices, or accept operator-produced settlement statements. The document flow matters for accounts payable and tax compliance, but it should not dictate the timing of expense recognition. Waiting for invoices can understate acquisition cost in a high-growth month and overstate it in the following month.
The practical control is to separate the earning calculation from the payment document. First, calculate and approve the period accrual. Second, produce or receive a settlement that supports payment. Third, match the settlement against the accrued liability, with a defined workflow for disputes, manual adjustments, and carryover balances. This gives the controller a clean audit trail without turning finance into the owner of every commercial query.
An affiliate may promote several brands across multiple regulated markets, currencies, and products. A single payment can therefore cover distinct tax treatments, commission rates, and legal entities. Consolidating those amounts too early obscures the economics and makes disputes harder to resolve.
Settlement should be calculated at the level at which the obligation is actually defined: typically affiliate, agreement, brand, market, product, and period. Those dimensions should continue into the ledger. They are the difference between seeing an aggregate affiliate expense and knowing whether a partner is profitable after gaming duty, bonuses, payment costs, and commission in each jurisdiction.
That detail is commercially useful. A chief commercial officer can assess whether a tiered deal is delivering incremental value. A CFO can identify when acquisition cost is rising faster than NGR. Tax leaders can validate that gaming duty has been handled consistently. During diligence, buyers can see the source of partner liabilities and assess whether reported margins are repeatable.
There is a trade-off. Excessive segmentation can create a brittle chart of accounts and an unmanageable close. The answer is not hundreds of new nominal codes. It is a disciplined dimensional model that preserves the relevant attributes without making every journal line unreadable.
Affiliate-platform data is an input, not the accounting record. It needs to reconcile to the gaming platform, bonus engine, payment data, tax calculations, and general ledger. If an affiliate dashboard reports NGR that does not align to finance's revenue waterfall, someone must identify the permitted difference before settlement.
A strong process establishes ownership for each break. Commercial teams should own agreement interpretation and partner disputes. Finance should own period recognition, ledger posting, and settlement controls. Tax should own gaming-duty treatment. Data and operations teams should own the integrity and timeliness of source feeds. When everyone owns the number, no one does.
Exceptions deserve their own workflow. Late wagering adjustments, voided bets, fraudulent accounts, chargebacks, negative carryover, FX movements, and retroactive rate changes should not disappear into a manual journal at the end of the month. Each needs a reason code, approval path, period treatment, and link to the affected agreement. That is what makes the balance defensible under audit and manageable at scale.
Affiliate economics change quickly. Operators renegotiate rates, enter new jurisdictions, add brands, launch sportsbook alongside casino, or change bonus policy. A process built around a static spreadsheet will keep working only until the next commercial exception.
The better design treats agreements as governed accounting rules. It provides effective dates, approval controls, version history, calculation parameters, and a clear link between the rule and the resulting journal. It also keeps the operational settlement view connected to the financial view, so a commercial user and a controller are not debating two different versions of NGR.
For scaling operators, this is the real value of specialist ERP design. Artio configures NetSuite around the way iGaming makes money: from GGR through tax, recognized revenue, partner cost, and settlement. The objective is not more automation for its own sake. It is a faster close, clearer margin, and financial records that hold up when a regulator, auditor, lender, or buyer asks how the number was produced.
The next time an affiliate commission looks high or low, do not start with the payout total. Start with the contract, follow the revenue waterfall, and make sure every deduction has an owner, a rule, and a ledger consequence.
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.