A gaming group across several jurisdictions has to satisfy local GAAP, a group IFRS view, tax and management reporting — often from the very same transaction. Done with duplicate entries and month-end spreadsheets, it's slow and error-prone. NetSuite Multi-Book posts each transaction to every book at once, each under its own rules, currency and chart of accounts.
Multi-Book Accounting keeps multiple sets of financial records in parallel and posts to all of them simultaneously — no duplicate entry, no month-end reconciliation between them. (Requires NetSuite OneWorld.)
Apply different accounting treatments — revenue recognition, depreciation, amortisation, eliminations — to a single transaction, one per book, by rule.
A transaction entered in the primary book posts to every secondary book at the same time, based on predefined rules. No re-keying for each standard.
Automatic conversion at current rates so each book carries the right functional currency — and realised/unrealised FX gain and loss are recorded correctly per book.
Each book can run its own chart of accounts at region, country or subsidiary level; a posting to a secondary book maps automatically to the right account.
Works across the OneWorld group — many subsidiaries with separate general ledgers in a single instance, with real-time visibility from consolidated down to the transaction.
Model the impact of a proposed accounting-standard change with before-and-after reports, so you can brief stakeholders before adopting it — not after.
Operators and B2B providers rarely live in one accounting world. You report locally under each market's GAAP, you roll the group up under IFRS, and you have tax and regulatory bases on top. The same revenue-share settlement, bonus accrual or duty charge has to land correctly in each of those views. The old answer is to enter it once, then re-key or adjust it into the others at month end — which is slow, and every re-key is a chance to be wrong. Multi-Book records the event once and lets each book treat it its own way, automatically.
Concurrent posting is what removes the month-end re-entry and manual adjustment that delays closing. That's a direct enabler of the day-one close we aim for in gaming finance: there's no separate pass to reconcile the books to each other because they were never out of step. It pairs with close & consolidation above it and financial management beneath it.
Book-specific revenue recognition is part of this story. The Revenue Share Engine calculates gaming revenue; Advanced Revenue Management recognises it under the standard; Multi-Book posts that recognition to local GAAP and group IFRS concurrently, each with its own rules and SSPs. The same applies to book-specific depreciation for fixed assets and to FX. One event, every standard, no second close.
A short call on the jurisdictions and standards your group reports under, and how much of the close goes on reconciling the books to each other. We'll show Multi-Book posting once, correctly, on NetSuite.
Independent, objective advice. We reply within one business day.