Our revenue engine works out what gaming revenue is — GGR to NGR to revenue, partner share, bonuses, duty. Advanced Revenue Management is the layer that decides when and how much of it lands on the P&L, under ASC 606 and IFRS 15. For a B2B provider with multi-element deals and variable consideration, that's not a spreadsheet job.
Advanced Revenue Management turns your revenue contracts into scheduled, compliant recognition — built into the same ledger that holds everything else, not bolted on beside it.
Recognition applied automatically under the five-step model — performance obligations, allocation and timing — instead of being re-interpreted in a spreadsheet for every contract.
Allocate consideration across performance obligations by SSP — a fixed value or a formula driven by other elements — so the right revenue lands on the right component.
Reusable rules trigger revenue plans — over time, on fulfilment, on billing, on a project event — and schedule each amount to the period it belongs in.
Revenue-share, rebates and bonuses are textbook variable consideration. Model them once and ARM recognises, defers and trues-up as the reported numbers arrive.
Real-time deferred-revenue waterfalls and roll-forwards that update as actuals post — every figure drillable back to its source sales document or transaction.
Multi-Book Accounting posts the same transaction under local GAAP and IFRS concurrently — book-specific rules, SSPs and currency, with no second close and no re-keyed entry.
It's worth being precise, because the two are easily confused. The revenue engine works out the number — what each partner is owed, what NGR became revenue, what bonuses net off, what duty applies. Advanced Revenue Management decides how that number lands on the P&L: over what period, against which performance obligation, under which standard. The engine feeds revenue elements into ARM; ARM schedules, allocates and recognises them. Together they carry gaming revenue from raw operator data to an audited, compliant figure.
The hardest part of ASC 606 — variable consideration — is the everyday reality of gaming. Revenue-share that depends on next month's NGR. Bonuses and free bets that reduce revenue. Minimum guarantees and tiered rates. A setup or integration fee bundled with ongoing licensing and a share of play. A B2B provider's contract is a multi-element arrangement with moving parts — precisely what spreadsheets get wrong, and precisely what ARM is built to schedule, allocate and re-estimate without a manual rebuild each month.
A day-one close depends on getting deferred and accrued revenue right before the reported figures land. ARM automates the contract-liability and contract-asset side, posts to the general ledger on your schedule, and keeps every recognised amount traceable to its source. That's the auditable revenue an investor, auditor or regulator expects — and the clean, granular, fully-allocated data an AI layer can actually use. It's also distinct from the two taxes we model elsewhere: gaming duty is an operating tax inside the engine (see gaming tax), and corporate income tax is its own reporting layer (see corporate tax reporting). Recognition is about revenue itself.
A short call on your revenue contracts — revenue-share, bonuses, guarantees, bundled fees — and where recognition eats time or risk today. We'll show ASC 606 / IFRS 15 automated on NetSuite.
Independent, objective advice. We reply within one business day.