Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Accounting

ERP

Financial Management

NetSuite Revenue Recognition: How ARM Works and How to Set It Up

Sherman Hsieh
Share This Post!
Published
NetSuite Revenue Recognition: How ARM Works and How to Set It Up

Last updated: October 8, 2026 · Independent guide · We do not sell rankings or coverage.

NetSuite revenue recognition for ASC 606 runs through Advanced Revenue Management (ARM). Approved sales create revenue arrangements, each line becomes a revenue element (a performance obligation), rules turn each element into a revenue recognition plan, and journal entries move revenue from deferred revenue to income each period. Oracle says classic revenue recognition is no longer available in new NetSuite implementations, so new accounts set up ARM (Essentials), and add ARM (Revenue Allocation) when contracts bundle several obligations that need relative standalone selling price allocation.

How ARM works: the four records you configure

ARM separates billing from recognition: invoices post to receivables, and revenue sits in deferred revenue until a recognition journal entry moves it to income (NetSuite Help, no date shown).

Record What it is Where it comes from
Revenue arrangement A non-posting transaction that holds a contract’s performance obligations for allocation and recognition Approved sales transactions, returns, projects, subscriptions or journal entries
Revenue element One line on the arrangement, representing one performance obligation One per source transaction line
Revenue recognition rule The pattern: recognition method, amount source, start and end date sources Built by the revenue manager and set as a default on items
Revenue recognition plan The posting periods and amounts for one element; one forecast plan and one or more actual plans Generated from the rule; actual plans drive posting

With ARM (Revenue Allocation), a fifth record matters: the fair value price list. It holds the standalone selling price (or VSOE, ESP or third-party evidence) that NetSuite uses to allocate a contract’s transaction price across elements (NetSuite Help, no date shown). Revenue elements map to step 2 (identify the performance obligations) and allocation to step 4 (allocate the transaction price) of the ASC 606 model in FASB ASU 2014-09 (May 2014).

When you need ARM, and which part of it

Oracle states that “Classic revenue recognition features aren’t available in new NetSuite implementations,” though existing users remain supported (NetSuite Help, no date shown). Your choices are these:

  • No deferral needed for some items. The item-level Direct Revenue Posting setting turns ARM off for an item, so transactions that include it post straight to the income account. Every item on such a transaction must use the setting (NetSuite Help, no date shown).
  • ARM (Essentials) only. Enough when lines are priced at standalone selling price and you only need deferral by time, fulfillment, billing or project progress.
  • ARM (Essentials) plus Revenue Allocation. Needed when you sell discounted bundles that must be allocated by relative standalone selling price.
  • Classic customers. Moving from classic revenue recognition to ARM requires NetSuite Professional Services or a qualified partner (NetSuite Help, no date shown).

NetSuite describes revenue management as an add-on module and does not publish a price for it. NetSuite is sold on an annual license fee made up of the core platform, optional modules and users, and the page directs buyers to contact NetSuite (NetSuite, Revenue Management, no date shown). See our NetSuite cost and fit analysis.

Before you start

  • License: ARM (Essentials), and ARM (Revenue Allocation) if you allocate. Revenue Allocation requires Essentials (NetSuite Help, no date shown).
  • Feature: Accounting Periods enabled, with periods set up for the full range your plans will cover.
  • Role: Administrator to enable features. ARM adds Revenue Manager and Revenue Accountant roles; neither includes Journal Approval by default (NetSuite Help, no date shown).
  • Policy and sandbox: A written ASC 606 policy (obligations, standalone selling prices, modifications) and a sandbox account for testing.

Step 1: Enable ARM (Essentials)

Go to Setup > Company > Setup Tasks > Enable Features, open the Accounting subtab, check Advanced Revenue Management (Essentials), confirm Accounting Periods is checked, and click Save (NetSuite Help, no date shown).

NetSuite adds system accounts for Deferred Revenue, Deferred Revenue Clearing, Unbilled Receivable and a non-posting Revenue Arrangement account. Once Configuration Mode is turned off, ARM cannot be disabled.

If you allocate, return to the same page and check Advanced Revenue Management (Revenue Allocation) on the Accounting subtab (NetSuite Help, no date shown).

Step 2: Work in Configuration Mode

ARM in Configuration Mode switches on with Essentials. While it is on, transactions do not run through ARM, so your current process keeps running. You cannot re-enable it once disabled, and disabling ARM features while in it deletes your configuration (NetSuite Help, no date shown). Accounts on Essentials before release 2024.2 lack this mode.

Step 3: Set accounting preferences

Go to Setup > Accounting > Accounting Preferences. The key settings sit on the General subtab (NetSuite Help, no date shown):

  • Revenue Arrangement Update Frequency and Revenue Plan Update Frequency: Manual or Automatic (every three hours).
  • Default Standard Revenue Recognition Rule: the rule items inherit unless you set another.
  • Create Revenue Recognition Journals in GL: Detail or Summary posting.
  • Unbilled Receivable Adjustment Journal Grouping: Element, Arrangement or Sub-Arrangement Group.

On the Items/Transactions subtab, set the Default Deferred Revenue Account. For Revenue Allocation, the same page adds Enable Fair Value Range Checking, Use Sales Price as Fair Value and Enable Contingent Revenue Handling (NetSuite Help, no date shown).

Step 4: Build revenue recognition rules

Go to Revenue > Non-Transaction Revenue Recognition Records > View Revenue Recognition Rules > New. Enter a unique name, then choose the Recognition Method, Amount Source, Rev Rec Start Date Source, Rev Rec End Date Source and Reforecast Method (NetSuite Help, no date shown).

Methods are four straight-line variants (even periods, prorated first and last period, exact days, period-rate) plus Custom, whose period percentages must total 100. End dates can come from a term, a number of periods, the element’s end date or a subscription end date (NetSuite Help, no date shown).

Name rules with a version, because a rule cannot be edited once it has generated a plan (except its name) and cannot be deleted once used (NetSuite Help, no date shown).

Step 5: Configure items

On each item record, the Accounting subtab holds the Deferred Revenue Account and Income Account. The Revenue Recognition/Amortization subtab holds the Revenue Recognition Rule, Rev Rec Forecast Rule and Create Revenue Plans On (Revenue Arrangement Creation, Billing, Fulfillment, Project Progress, Project Revenue Event or Subscription Events) (NetSuite Help, no date shown).

The trigger must match the rule’s amount source. For example, Fulfillment pairs with Event-Percent based on quantity. With Revenue Allocation, set the Allocation Type (Normal, Exclude or Software), Item Revenue Category and Permit Discount. Item changes do not update revenue elements that already exist.

Step 6: Set up fair values (Revenue Allocation only)

Create formulas first at Revenue > Setup > Fair Value Formula > New (NetSuite Help, no date shown). Then add a price record per item or item revenue category at Revenue > Setup > Fair Value Price Lists > New, with a base fair value, currency and default formula (NetSuite Help, no date shown).

Illustration: a customer pays $12,000 for a software subscription with a standalone selling price of $10,000 and implementation with a standalone selling price of $4,000. Total standalone value is $14,000, so ARM allocates $8,571.43 to the subscription (10/14 of $12,000) and $3,428.57 to implementation.

Step 7: Test, then go live

In the sandbox, run a subscription, a discounted bundle, an upsell, a return and a multi-currency deal end to end and check each plan and journal entry. Oracle advises confirming the configuration before you disable Configuration Mode, because every later transaction runs through ARM (NetSuite Help, no date shown). Record the cutover date, since workflows started earlier keep their prior treatment (NetSuite Help, no date shown).

Step 8: Run the monthly revenue process

  1. Update arrangements and plans at Financial > Other Transactions > Update Revenue Arrangements and Revenue Recognition Plans, and refresh until each process shows Complete (NetSuite Help, no date shown).
  2. Create revenue recognition journal entries. Administrators use Transactions > Financial > Schedule Revenue Recognition Journal Entries > Run Now, choose the posting period and click Create Journal Entries. Closed or locked periods are blocked (NetSuite Help, no date shown).
  3. Run deferred revenue reclassification, always after recognition, to split contract assets from contract liabilities.
  4. Recalculate forecast plans if you use them, then run and save the Deferred Revenue Waterfall report (NetSuite Help, no date shown).

For the wider close, see our guide to SaaS accounting for subscription revenue.

Common mistakes and how to fix them

  • Running reclassification before recognition. Run recognition first. If recognition entries were still unapproved, rerun reclassification after approval (NetSuite Help, no date shown).
  • Recording discounts as negative lines. Use non-posting discount items, record returns with return authorizations, then merge the positive and negative arrangements (NetSuite Help, no date shown).
  • A mismatched trigger and amount source. Align Create Revenue Plans On with the rule’s amount source. Changing the trigger after an arrangement exists can create a duplicate arrangement.
  • Journal approval workflows catching system entries. Create a custom form for revenue recognition journals, exclude it from the workflow and set it as the Default Revenue Recognition Journal Entry Form (NetSuite Help, no date shown).
  • Missing fair values. With Use Sales Price as Fair Value cleared, an item with no price record causes an error. Load fair values for every allocable item and kit component.

Limitations of native ARM

Automatic arrangement updates run every three hours, so same-day reporting needs a manual run. Revenue recognition journals post in the subsidiary base currency (NetSuite Help, no date shown). Forecast reports read plans, not posted GL entries, and can differ from the ledger after direct postings to deferred revenue (NetSuite Help, no date shown). Migrating from classic, or running a standards transition in ARM, requires Professional Services or a partner (NetSuite Help, no date shown).

When companies add a third-party tool

If you bill inside NetSuite, the native path is ARM paired with SuiteBilling, which adds default recognition rules for fixed recurring, adjustable recurring and usage rate plans (NetSuite Help, no date shown). Teams that bill in another platform sometimes run recognition outside NetSuite and post summary entries back. Chargebee RevRec, for example, syncs NetSuite invoices and credit memos into its engine and posts monthly journal entries to the NetSuite ledger at period close (Chargebee docs, no date shown; Chargebee sells this product). The cost is a second subledger to reconcile. A NetSuite implementation partner or our guide to quote-to-cash automation can help you choose.

How we researched this

We worked from Oracle’s NetSuite help topics on ARM, checked on October 8, 2026, and used only menu paths printed there. We also reviewed the top-ranking pages for “netsuite revenue recognition,” mostly from NetSuite partners. We have no commercial relationship with Oracle NetSuite or any partner.

Related guides

Frequently asked questions

Is NetSuite ARM required for ASC 606?

For new NetSuite accounts, ARM is the only revenue recognition engine on offer, because Oracle says classic revenue recognition is not available in new implementations. ARM (Essentials) handles deferral and timing. You also need ARM (Revenue Allocation) if contracts bundle obligations that must be allocated by standalone selling price.

What is the difference between ARM (Essentials) and ARM (Revenue Allocation)?

Essentials defers revenue and recognizes it through rules, plans and journal entries. Revenue Allocation is a separately enabled add-on that reallocates a contract’s price across elements using a fair value price list. You need Essentials before you can enable Revenue Allocation.

Why didn’t my sales order create a revenue arrangement?

With automatic updates, arrangements are created about three hours after the source transaction. Transactions that need approval create arrangements only after approval. Run the update manually from Financial > Other Transactions > Update Revenue Arrangements and Revenue Recognition Plans and check the process status for errors.

How much does NetSuite Advanced Revenue Management cost?

NetSuite does not publish a price. It describes revenue management as an add-on module within an annual license, so you need to contact NetSuite for pricing. Budget separately for partner configuration time.

Sources

Oracle NetSuite help pages show no publication date; we checked each on October 8, 2026. Vendor sources that sell the product are marked.

  • Oracle NetSuite Help, Advanced Revenue Management (Essentials) and (Revenue Allocation), no date shown. docs.oracle.com
  • Oracle NetSuite Help, Setup for ARM (Essentials), no date shown. docs.oracle.com
  • Oracle NetSuite Help, Enabling the ARM (Essentials) Feature, no date shown. docs.oracle.com
  • Oracle NetSuite Help, ARM in Configuration Mode, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Setting ARM (Essentials) Preferences, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Recognition Rules, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Defining a Revenue Recognition Rule, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Recognition Rule Field Reference, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Item Configuration for ARM, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Setup for ARM (Revenue Allocation), no date shown. docs.oracle.com
  • Oracle NetSuite Help, Enabling the ARM (Revenue Allocation) Feature, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Setting ARM (Revenue Allocation) Preferences, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Adding Fair Value Formulas, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Creating the Fair Value Price List, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Management Roles and Permissions, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Recognition and ARM (Essentials), no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Arrangement Management, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Updating Revenue Arrangements, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Generating Advanced Revenue Recognition Journal Entries, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Revenue Recognition Journal Entries, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Reclassification of Deferred Revenue, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Month-End Revenue Processing, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Reports for Advanced Revenue Management, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Transition to the New Revenue Recognition Standard, no date shown. docs.oracle.com
  • Oracle NetSuite Help, Enabling the Revenue Recognition Feature (classic), no date shown. docs.oracle.com
  • Oracle NetSuite, Revenue Management product page, no date shown (vendor). netsuite.com
  • FASB, Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers (Topic 606), May 2014. storage.fasb.org
  • Chargebee, RevRec NetSuite integration documentation, no date shown (vendor; sells the product). chargebee.com

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read