ARM Allocation for a Discounted Implementation Service
A NetSuite Advanced Revenue Management customer signs a 24-month contract on January 1. The sales order has two lines: SaaS subscription $240,000 ($10,000 per month) and implementation services $30,000. The implementation requires 400 hours of configuration that changes the customer's production environment, and the customer cannot benefit from the SaaS without it; the implementation does not transfer to another provider. Sales operations set the implementation list price at $50,000 but discounted it to $30,000. The revenue arrangement created two elements with fair value sources: SaaS 'ESP' at $240,000 and implementation 'Residual'. The revenue plan recognizes $30,000 in January and $10,000 per month for 24 months. Total consideration is $270,000. The January close is complete and revenue has been posted. The controller asks whether the plan is acceptable and what to do before the February close.
1. Evaluate whether the implementation is a distinct performance obligation and compute the correct revenue pattern.
Read the worked answer
The implementation is not distinct. It requires 400 hours of configuration that changes the production environment, the customer cannot benefit from the SaaS without it, and it does not transfer to another provider. Under the revenue standard, that is a combined performance obligation with the SaaS. The $30,000 discount is not allocated to a separate implementation element; total consideration of $270,000 is recognized over the 24-month service period, or $11,250 per month. The current plan front-loads $30,000 in January and then $10,000 monthly, which recognizes $270,000 but at the wrong pattern.
If the facts were different and the implementation were distinct, relative SSP would apply: total SSP $290,000; implementation $50,000/$290,000 × $270,000 = $46,552 at a point in time; SaaS $223,448 over 24 months = $9,310 per month. But the stated dependency makes the combined treatment correct.
2. Why did NetSuite produce the current plan, and how would you correct it in ARM without restating prior periods incorrectly?
Read the worked answer
The system produced the front-loading because the arrangement has two elements and the implementation's fair value source is 'Residual' while the SaaS uses ESP equal to its stated price. Residual allocation pushes the discount to the implementation, and because the implementation was treated as a separate element, its revenue was released at go-live.
Inspect the revenue arrangement's elements, allocation, fair value source, and revenue plan; then put the arrangement on hold so no further recognition posts. Use a revenue arrangement revision, retroactive to January 1, to combine the elements or correct the allocation and regenerate the plan. The catch-up should be posted in February if January is closed and the amount is immaterial; if material, reopen January. Document the distinctness judgement in the arrangement file.
3. What controls would prevent an incorrect ARM arrangement from being set up and released again?
Read the worked answer
Require revenue accounting review before booking non-standard implementation discounts; maintain an ESP and fair-value table by SKU; do not default new elements to Residual; add a close-checklist task reconciling the ARM waterfall to GL revenue; and require a documented distinctness assessment for implementation services. Also restrict who can change fair value sources and who can resume a held revenue arrangement.