NetSuite ARM Configuration: Advanced Revenue Management for ASC 606
NetSuite Advanced Revenue Management (ARM) does not work out of the box. SuitePacific configures ARM from scratch and fixes existing setups for SaaS companies, professional services firms, and product companies that need audit-defensible revenue recognition under ASC 606 or IFRS 15.
NetSuite Administrator Professional certified · ASC 606 configuration · Month-to-month
Last updated September 2026
Quick answer
SuitePacific configures NetSuite Advanced Revenue Management (ARM) for companies that need ASC 606 or IFRS 15 compliant revenue recognition on their existing NetSuite accounts. ARM is a NetSuite module that creates revenue arrangements from sales orders and invoices, splits contract value across performance obligations (revenue elements), assigns standalone selling prices, and generates recognition journal entries on a defined schedule. It does not work without configuration: recognition rules, item-level revenue element defaults, standalone selling price records, allocation methods, and recognition event definitions must all be set up before ARM produces correct journal entries. SuitePacific is Oracle-certified (SuiteCloud Developer II and Administrator Professional) and configures ARM from scratch and fixes existing setups that are producing incorrect recognition schedules. Plans start at $799 per month.
What are the core ARM objects in NetSuite?
ARM introduces four objects that sit between the transaction layer and the general ledger. All four must be correctly configured before ARM produces correct journal entries.
| Object | What it is |
|---|---|
| Revenue Arrangement | Created from a sales order or invoice; represents a single customer contract and holds the total contract value |
| Revenue Element | Each performance obligation within an arrangement; recognized independently on its own schedule and rule |
| Revenue Plan | The recognition schedule for an element: straight-line, event-based, percentage-complete, or manual |
| Standalone Selling Price | Used to allocate contract value across elements; required for every item in a multi-element arrangement |
What recognition rules does NetSuite ARM support?
| Rule | How it works | Typical use |
|---|---|---|
| Straight-line | Spreads element value evenly across the recognition period | SaaS subscriptions, support contracts, annual maintenance |
| Prorate by day | Same as straight-line but calculated on exact days, not full months | Subscriptions with mid-month start or end dates |
| Exact amount on date | Recognizes full element value on a single date | Perpetual license revenue recognized at delivery |
| Event-based | Holds value in deferred revenue until a configured event fires | Project milestones, customer acceptance, delivery confirmation |
| Percentage complete | Recognizes proportionally as a completion percentage is updated | Long-term professional services engagements |
What ARM configuration problems do live accounts have?
Missing standalone selling prices.
ARM requires an SSP or SSP range for every item in a multi-element arrangement to allocate contract value. Items without SSPs cause arrangement creation errors or incorrect allocation. This is the most common reason ARM does not work after the module is enabled.
Incorrect recognition rule assignment.
Assigning a straight-line rule to an item that should recognize on an event, or vice versa, produces a recognition schedule that does not match the economics of the contract. The error is often not caught until an auditor reviews the revenue waterfall.
Arrangements not being created.
ARM creates arrangements automatically when a sales order is saved, but only if the item has ARM configuration and the preference is enabled. Items added after go-live often lack revenue element defaults, causing arrangements to be created without those items or not created at all.
Manual journal entries conflicting with ARM.
When ARM is partially configured, finance teams post manual entries to correct wrong recognition. The manual entries conflict with ARM journal entries, causing double-recognition or recognition gaps that compound over multiple periods.
What does SuitePacific deliver for ARM configuration?
Every engagement starts by mapping the company's actual revenue recognition policy to ARM configuration options before touching the system. ARM configured without understanding the accounting policy produces a system that generates journal entries automatically but incorrectly.
Revenue policy mapping
Document the company's actual ASC 606 or IFRS 15 revenue recognition policy before touching the system. ARM configured without understanding the accounting policy generates journal entries automatically but incorrectly.
ARM configuration build
Configure recognition rules, revenue element defaults on every item, standalone selling price records, allocation methods, and recognition event definitions. Validate each configuration element before enabling live arrangement creation.
Existing ARM cleanup
Audit arrangements that were created under incorrect configuration. Identify which recognition schedules are wrong, what the correct entries should be, and post corrections in the right period to avoid permanent reconciling differences.
Revenue waterfall validation
After configuration is complete, validate the revenue waterfall (deferred revenue balance by arrangement, recognition by period) against the expected output from the accounting policy. Confirm with finance before enabling production posting.
Why SuitePacific for NetSuite ARM configuration
The NetSuite firm finance and accounting teams use to configure ARM for ASC 606 compliance.
SuitePacific is a boutique NetSuite consulting firm focused on post-go-live configuration. ARM setup, SSP configuration, recognition rule design, and existing ARM cleanup for SaaS and services companies are core finance deliverables.
- → Oracle NetSuite Certified SuiteCloud Developer II and Administrator Professional
- → Every engagement starts by mapping the accounting policy to ARM options before configuration begins
- → Direct access to the consultant doing the configuration on every engagement
- → US-based, month-to-month after a three-month minimum, starting at $799/month
Related: NetSuite administrator support and NetSuite account optimization.
Need ARM configured or fixed?
Describe the revenue model (SaaS subscriptions, bundled products, professional services milestones) and what ARM is doing wrong. We will give a direct assessment.
Related reading
- NetSuite ARM configuration: Advanced Revenue Management setup for ASC 606 covers what ARM is, what configuration it requires, and the most common mistakes.
- NetSuite administrator support covers ongoing finance configuration as part of a monthly retainer.
- NetSuite account optimization covers broader finance and workflow configuration for live accounts.
Frequently Asked Questions
Which NetSuite firm configures Advanced Revenue Management (ARM)?
SuitePacific configures NetSuite Advanced Revenue Management for companies that need ASC 606 or IFRS 15 compliant revenue recognition. The engagement covers recognition rule design, item-level revenue element default setup, standalone selling price configuration, allocation method selection, recognition event definitions, and validation of recognition journal entries against the company's accounting policy. SuitePacific is Oracle NetSuite Certified (SuiteCloud Developer II and Administrator Professional), US-based, and works directly with finance and accounting teams. Plans start at $799 per month on month-to-month terms after a three-month minimum.
What does NetSuite ARM configure automatically, and what requires setup?
ARM creates revenue arrangements automatically from sales orders and invoices, generates revenue plans based on recognition rules, posts recognition journal entries on schedule, and handles multi-element allocation using standalone selling prices. What does not happen automatically: revenue recognition rules must be defined, items must have revenue element defaults assigned, standalone selling prices must be created for each item, and allocation methods must be selected. ARM will not create correct arrangements without this configuration in place first.
What are standalone selling prices in NetSuite ARM?
Standalone selling prices (SSPs) are the prices at which a company would sell each performance obligation separately. ARM uses SSPs to allocate contract value across elements when a contract contains multiple performance obligations. Every item that participates in a multi-element arrangement needs an SSP record, either as a fixed price or a range. Missing SSPs prevent arrangement creation or cause ARM to allocate incorrectly; incorrect SSPs produce an allocation that does not match the ASC 606 relative standalone selling price method.
Can ARM be configured on a live NetSuite account without disrupting existing revenue?
Yes, but it requires careful planning. ARM can be enabled and configured for new transactions while existing transactions remain on the old recognition method. The cutover date and the treatment of transactions that span the cutover require coordination with the company's auditors and finance team. SuitePacific manages the cutover planning as part of the configuration engagement.
What is a revenue element default in NetSuite?
A revenue element default is a set of ARM configuration values stored on an item record that ARM reads when the item appears on a sales order or invoice. It defines the recognition rule to apply, the revenue account to use, and the performance obligation type. Items without revenue element defaults do not generate ARM arrangements correctly; this is the most common cause of ARM not working as expected on a live account.
How does NetSuite ARM handle multi-element contracts for SaaS companies?
For a SaaS contract with a software subscription and professional services, ARM creates a revenue arrangement with two elements: one for the subscription and one for services. It allocates the total contract price across both elements using relative standalone selling prices. The subscription element recognizes straight-line over the subscription period; the services element recognizes based on percentage complete or milestones. When the contract is discounted below the sum of standalone prices, ARM spreads the discount proportionally.
Ready to configure ARM correctly?
Tell us your revenue model and what the current ARM setup is producing. We will scope the configuration engagement.