Revenue Recognition & Advanced Billing in NetSuite

Bill correctly. Recognise accurately. Satisfy the auditor. Configure NetSuite revenue recognition and advanced billing — ASC 606 / IFRS 15 compliance, revenue arrangements, recognition schedules, deferred revenue, and multi-element billing. 9 hrs · 3 sessions · Advanced. Overview Revenue recognition is the accounting area most likely to generate an audit qualification on a NetSuite instance. The rules under IFRS 15 and ASC 606 require organisations to recognise revenue when performance obligations are satisfied — not when cash is received, not when an invoice is raised. NetSuite's Advanced Revenue Management module automates this compliance, but only if it is configured correctly. This course covers the complete NetSuite revenue recognition configuration: from the revenue arrangement concept through to the recognition schedule, the deferred revenue waterfall, and the management reports that give the finance director confidence that the revenue position is accurate and auditable. All scenarios are illustrated with African professional services, subscription, and project billing contexts. Learning outcomes • Configure NetSuite Advanced Revenue Management for at least three recognition schedule types • Set up revenue arrangements and standalone selling price tables for multi-element contracts • Manage the deferred revenue waterfall and review the recognition journal before period posting • Handle contract modifications using the correct NetSuite ARM modification type • Produce the revenue recognition reports that satisfy an external auditor under IFRS 15 Prerequisites • Chart of Accounts, Accounting Periods & Financial Settings course • PSA Configuration course is recommended for professional services revenue scenarios • Understanding of ASC 606 / IFRS 15 revenue recognition principles Modules 1. Revenue recognition principles, the ARM module & revenue arrangements (3 hours) IFRS 15 and ASC 606 in plain language: the five-step model (identify the contract, identify performance obligations, determine the transaction price, allocate the price to obligations, recognise revenue as each obligation is satisfied) and how it applies to the billing models used by African organisations. The difference between billing and revenue: why an invoice raised today for a six-month project does not mean six months of revenue recognised today. NetSuite Advanced Revenue Management (ARM): what it does, what it requires (a specific licence, specific item setup, specific transaction configuration), and what happens if revenue recognition is attempted without ARM. Revenue elements: the item configuration that marks an item as a revenue-bearing element, the revenue recognition rule that applies to that item, and the allocation of the transaction price when a single invoice contains multiple items with different recognition patterns. Revenue arrangements: the NetSuite record that groups all the elements of a customer contract into a single recognition view — how it is created, what it contains, and how it connects to the underlying transactions. The standalone selling price: the concept required by IFRS 15 for allocating the transaction price to multiple performance obligations, and how to configure the standalone selling price table in NetSuite. Topics: IFRS 15 five-step model; ASC 606 alignment; Billing vs revenue distinction; ARM module requirements; ARM licence; Revenue element item setup; Revenue recognition rules; Multi-element invoice; Price allocation; Revenue arrangement record; Contract grouping; Performance obligation; Standalone selling price table; Price allocation methodology 2. Recognition schedules, deferred revenue & the recognition journal (3 hours) Recognition schedule types: the four recognition schedule templates in NetSuite and when to use each — the straight-line schedule (equal amounts over a defined period, appropriate for SaaS subscriptions and retainers), the percentage of completion schedule (proportional to project completion, appropriate for fixed-price professional services), the event-based schedule (recognise on a specific date or milestone approval, appropriate for software licences and contract deliverables), and the immediate recognition schedule (recognise the full amount at the time of the transaction, appropriate for standard product sales). Configuring a straight-line recognition schedule: the duration, the start date basis (invoice date, ship date, custom field), and the proration of the first and last period. The deferred revenue waterfall: what deferred revenue is, where it sits on the balance sheet (liability), how it moves to the income statement as revenue is recognised, and the month-end deferred revenue roll-forward that satisfies the auditor. The recognition journal: the automated journal that NetSuite posts each period to transfer revenue from deferred to recognised — the accounts it debits and credits, the period it posts to, and how to review and approve the recognition batch before posting. Topics: Straight-line schedule; Percentage completion schedule; Event-based schedule; Immediate recognition; Straight-line configuration; Duration setup; Start date basis options; Period proration; Deferred revenue as liability; Revenue waterfall; Month-end roll-forward; Recognition journal automation; Debit and credit accounts; Recognition batch review and approval 3. Multi-element arrangements, modifications & revenue reporting (3 hours) Multi-element revenue arrangements in practice: a professional services firm that sells a software licence, implementation services, and a one-year support contract in a single deal — three performance obligations with different recognition patterns, sold together at a bundled price. How NetSuite allocates the transaction price across the three elements using standalone selling prices: the residual approach when one element's SSP is not directly observable, and the relative SSP approach when all three are known. Contract modifications: what happens when a customer adds scope mid-contract (creates a new performance obligation) versus changes the price of existing scope (modifies the existing arrangement) — and the NetSuite configuration for each scenario. Modification types in NetSuite ARM: cumulative catch-up (recognise the adjustment in the current period) versus prospective adjustment (adjust the remaining recognition schedule going forward). Revenue reporting in NetSuite: the revenue recognition status report (which arrangements are ahead of or behind schedule), the deferred revenue aging report (how long revenue has been sitting in deferred), the contract liability rollforward (the board-level report that shows opening deferred, amounts recognised, new deferrals, and closing deferred), and the revenue backlog report (contracted revenue not yet recognised — the forward revenue visibility metric). Topics: Multi-element arrangement example; Software licence + services + support; Price allocation across elements; Residual approach; Relative SSP approach; Contract modifications; Scope addition; Price modification; Cumulative catch-up; Prospective adjustment; Revenue recognition status report; Deferred revenue aging; Contract liability rollforward; Revenue backlog report; Forward revenue visibility Delivery Delivered by a certified NetSuite revenue recognition specialist in partnership with Simpl'IT Cloud. Three sessions with worked examples drawn from African business contexts. Groups of 4–10. Not suitable as a first NetSuite course — the Chart of Accounts and PSA courses are prerequisites. Certification Certificate of completion Price USD 1000 · per participant per person · indicative · group pricing available HRDC eligibility Up to 75% refundable Mauritius-registered employers may claim this training via the HRDC levy. We provide full documentation to support your claim. Languages English Provider reference SIMPLIT-055-NS_REVENUE_RECOGNITION

• Finance directors and controllers responsible for revenue recognition compliance • NetSuite administrators configuring the Advanced Revenue Management module • Implementation consultants deploying NetSuite for clients with complex billing models • External auditors assessing NetSuite's revenue recognition configuration • CFOs of professional services, SaaS, or subscription businesses on NetSuite • Finance managers transitioning from manual revenue recognition to NetSuite automation