# How to Set Up Revenue Recognition With NetSuite ARM

> Source: https://netray.co/erp-help/netsuite-how-to-revenue-recognition-arm-setup
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

NetSuite Advanced Revenue Management (ARM) recognizes revenue on a schedule independent of invoicing by generating a Revenue Element from each transaction line, applying a Revenue Recognition Rule to determine timing, and optionally allocating revenue across performance obligations using Standalone Selling Price (SSP). Setup requires enabling the ARM feature, defining recognition rules, and mapping item revenue categories before transactions start generating revenue plans.

## Kind

how-to

## System

netsuite

## Erp

Oracle NetSuite

## Module

Advanced Revenue Management (ARM)

## Query

how to set up revenue recognition in NetSuite ARM

## Alternate Queries

- NetSuite Advanced Revenue Management setup guide
- NetSuite revenue recognition rule vs revenue element
- how does NetSuite ARM create revenue plans
- NetSuite SSP setup revenue allocation

## Applies To

NetSuite Advanced Revenue Management (ARM) module, requires SuiteSuccess or Enterprise-tier license; distinct from the legacy Revenue Recognition feature

## Steps

### How to configure Advanced Revenue Management

**Items:**

Enable the feature at Setup > Company > Enable Features > Accounting tab, checking Advanced Revenue Management (this disables the legacy Revenue Recognition feature; they cannot run concurrently on new implementations).

Define Revenue Recognition Rules at Revenue > Revenue Recognition Rules > New, setting recognition method (straight-line, immediate, milestone-based, or event-based) and default recognition period.

Set up Revenue Recognition Treatments if you need multiple accounting books (e.g. ASC 606 vs IFRS 15) generating different revenue plans from the same transaction.

On each revenue item, assign a default Revenue Recognition Rule under the item record's Accounting subtab, and set the Revenue Allocation Group if the item participates in bundled/multi-element arrangements.

Configure Standalone Selling Price under Revenue > Setup > Manage Standalone Selling Price, either as a fixed price, a percentage of list price, or an SSP range with high/low bounds for allocation.

Save a transaction (sales order or invoice) containing revenue items; NetSuite automatically creates a Revenue Arrangement and one Revenue Element per eligible line.

Run Revenue > Revenue Recognition > Create Revenue Plans (or let the scheduled process run) to generate the actual Revenue Plan records showing period-by-period recognition amounts.

Review generated plans under Revenue > Revenue Recognition > Revenue Plans, and post recognition journal entries via the recurring Revenue Recognition process (Revenue > Revenue Recognition > Recognize Revenue).

## Sections

### Revenue arrangements and elements

**Body:**

Every source transaction line with a revenue item creates a Revenue Element, and all elements from one transaction (or explicitly grouped transactions) roll up into a Revenue Arrangement, which is the unit ARM uses to allocate revenue across multiple obligations when a deal bundles a license, implementation service, and support into one order.

Revenue Arrangement combination rules, set at Revenue > Setup > Revenue Arrangement Sources, control whether multiple sales orders for the same customer/project combine into a single arrangement (needed for correct SSP allocation across a bundled deal) or stay separate.

### SSP allocation mechanics

**Body:**

When a Revenue Arrangement contains items in the same Revenue Allocation Group, ARM allocates the arrangement's total consideration across elements proportionally to each item's Standalone Selling Price, not its contract price, which is the core ASC 606 / IFRS 15 requirement that revenue reflect what each obligation would sell for on its own.

SSP can be entered as a fixed value, calculated as a percentage of the item's list price, or defined as an acceptable range (high/low); NetSuite uses the range's midpoint or a specified method when the contract price for an item falls outside its expected range, flagging the arrangement for review.

### Recognition rules and methods

**Body:**

Straight-line recognition spreads the element's allocated amount evenly across a start and end date, typically driven by a subscription term. Immediate recognition posts the full amount on element creation, used for delivered goods. Milestone and event-based rules tie recognition to a percent-complete field or an explicit trigger event, common for professional services and project-based revenue.

The recognition rule's Amount Source setting determines whether the plan uses the allocated (SSP-adjusted) amount or the original transaction amount, which matters when allocation differs materially from list price on a bundled deal.

### Multi-book and dual reporting

**Body:**

Revenue Recognition Treatments let one Revenue Element generate multiple Revenue Plans against different accounting books when a company must report under both ASC 606 and a local GAAP standard with different recognition timing rules for the same underlying transaction.

Each treatment can have its own recognition rule assignment per item, so the same sale can recognize revenue on delivery for local statutory books while recognizing straight-line over a service period for US GAAP, without duplicating the source transaction.

## Pitfalls

Enabling Advanced Revenue Management on a company that still needs the legacy Revenue Recognition feature for existing open transactions, since the two do not run side by side on the same subsidiary going forward.

Missing a Revenue Recognition Rule on an item, which leaves the revenue element without a recognition method and blocks plan generation until fixed.

Setting SSP as a static fixed value and never revisiting it, causing allocation to drift from actual standalone pricing as list prices change.

Forgetting that combining transactions into one Revenue Arrangement affects allocation; splitting a bundled deal across separate orders that do not combine will allocate each order independently instead of as one arrangement.

Not reconciling Revenue Plans to the general ledger regularly; unposted or stuck plans accumulate silently if the recurring Recognize Revenue process is not scheduled or fails.

Changing an item's Revenue Recognition Rule after arrangements already exist, which does not retroactively update existing plans and creates inconsistency between old and new deals.

## Ai Angle

ERPray, grounded on your NetSuite ARM configuration and historical revenue plans, can explain why a specific arrangement allocated the way it did, trace an element back to its source transaction and SSP basis, and flag arrangements where the contract price fell outside the configured SSP range, work that normally means manually cross-referencing the Revenue Arrangement, Revenue Element, and Revenue Plan records by hand.

## Faq

### Can I use Advanced Revenue Management and legacy Revenue Recognition together?

**Answer:** Not for the same subsidiary going forward. Enabling ARM is generally a one-way migration; NetSuite provides transition tooling to convert existing legacy revenue recognition schedules, but new transactions after cutover use ARM exclusively on that subsidiary.

### What triggers a Revenue Arrangement to combine multiple transactions?

**Answer:** Revenue Arrangement Source rules, configured under Revenue > Setup, define matching criteria such as same customer and same project or contract reference; transactions meeting those criteria combine into one arrangement for allocation purposes.

### Does changing SSP retroactively affect existing revenue plans?

**Answer:** No. SSP changes apply to new Revenue Arrangements created after the change; existing plans keep the allocation calculated at arrangement creation time unless you manually reallocate, which NetSuite supports but does not do automatically.

### How do I handle a contract modification under ARM?

**Answer:** Amend the source transaction or create a change order that ARM recognizes as a modification event; depending on configuration this either adjusts the existing Revenue Arrangement prospectively or creates a new arrangement, so contract modification handling should be tested against your specific recognition rules.

## Search terms

NetSuite Advanced Revenue Management, NetSuite ARM setup, NetSuite revenue recognition rule, NetSuite revenue element, NetSuite standalone selling price SSP, NetSuite revenue arrangement, NetSuite ASC 606 setup, NetSuite revenue plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json