What is ARM?

NetSuite Advanced Revenue Management (ARM) is a module that automates the complex accounting requirements of ASC 606 (Revenue from Contracts with Customers) and IFRS 15. It handles the allocation of transaction prices across multiple performance obligations and automates revenue recognition timing.

Prerequisites

ASC 606 Policy Decisions

Before configuring ARM, document decisions on these key accounting policy questions:

Enable ARM Feature

Setup › Company › Enable Features › Accounting subtab

Check Advanced Revenue Management in the Revenue Recognition section. This enables:

• Revenue Element records
• Revenue Arrangement records
• Revenue Recognition Rules
• ARM-specific reports

ARM Preferences

Setup › Accounting › Revenue Recognition › ARM Preferences

GL Account Setup

ARM requires specific GL accounts for proper revenue accounting:

ARM GL ACCOUNT STRUCTURE
===============================================================

BALANCE SHEET ACCOUNTS:
---------------------------------------------------------------
1200    Unbilled Receivables (Contract Asset)
        - Revenue recognized before invoicing

2300    Deferred Revenue - Current (Contract Liability)
        - Invoiced but not yet recognized (< 12 months)

2400    Deferred Revenue - Long Term (Contract Liability)
        - Invoiced but not yet recognized (> 12 months)

INCOME STATEMENT ACCOUNTS:
---------------------------------------------------------------
4000    Revenue - Products
4100    Revenue - Software License
4200    Revenue - SaaS Subscription
4300    Revenue - Professional Services
4400    Revenue - Support & Maintenance
4500    Revenue - Training

RECOMMENDATION: Create separate deferred revenue accounts
for each revenue type to support disclosure requirements.

SSP Hierarchy

ASC 606 prescribes a hierarchy for determining SSP:

Observable Price Method

Best evidence of SSP--actual prices from standalone sales:

• Pull historical sales data for standalone transactions
• Analyze price distribution (median, mean, range)
• Consider customer segment, volume, geography adjustments
• Document data sources and analysis methodology

SSP ANALYSIS EXAMPLE: IMPLEMENTATION SERVICES
===============================================================

DATA GATHERING:
- Period: Last 24 months
- Filter: Standalone implementation deals (no bundled software)
- Sample size: 47 transactions

ANALYSIS:
+-------------------------------------------------------------+
| Transaction Count:  47                                       |
| Total Revenue:      $2,115,000                               |
| Average Deal Size:  $45,000                                  |
|                                                              |
| Price Distribution:                                          |
|   Minimum:          $18,000                                  |
|   25th Percentile:  $32,000                                  |
|   Median:           $42,500                                  |
|   75th Percentile:  $55,000                                  |
|   Maximum:          $95,000                                  |
|                                                              |
| Standard Deviation: $18,200                                  |
+-------------------------------------------------------------+

CONCLUSION:
SSP for Implementation Services = $42,500 (median)
Range: $32,000 - $55,000 (interquartile range)

DOCUMENTATION: Saved Search #SS-2847, exported to Excel
analysis file "SSP_Implementation_2025.xlsx"

Adjusted Market Assessment

When observable prices aren't available, use market data:

• Competitor pricing research
• Industry benchmarks and surveys
• Adjust for company-specific factors (brand, quality, features)

Expected Cost Plus Margin

Build up SSP from expected costs:

• Calculate expected costs to fulfill obligation
• Add appropriate margin based on company targets or industry norms
• Common for services and customization work

COST PLUS MARGIN EXAMPLE: TRAINING SERVICES
===============================================================

COST BUILDUP (Per Training Day):
---------------------------------------------------------------
Trainer Salary (fully loaded):      $800/day
Travel & Expenses (average):        $400/day
Materials & Facilities:             $100/day
---------------------------------------------------------------
Total Direct Cost:                  $1,300/day

Target Margin:                      35%
Cost Plus Margin:                   $1,300 / (1 - 0.35) = $2,000/day

SSP for Training = $2,000 per day

Residual Approach

Only when SSP is highly variable or uncertain:

• SSP = Total Transaction Price - Sum of other elements' SSP
• Strict criteria: Must demonstrate high variability
• Often used for software licenses with highly negotiated pricing

SSP in NetSuite

Configure SSP at the Revenue Element level:

Setup › Accounting › Revenue Recognition › Revenue Elements

Revenue Element Structure

Revenue Elements define the recognition rules for item types:

Setup › Accounting › Revenue Recognition › Revenue Elements

Common Revenue Element Configurations

REVENUE ELEMENT EXAMPLES
===============================================================

ELEMENT: Software License (Perpetual)
---------------------------------------------------------------
Recognition Rule:     Point in Time
Trigger:              Ship Date (or Delivery Date)
SSP Source:           Fair Value Price Level
Revenue Account:      4100 - Software License Revenue
Deferred Account:     2300 - Deferred Revenue

ELEMENT: SaaS Subscription
---------------------------------------------------------------
Recognition Rule:     Over Time - Straight Line
Recognition Period:   Custom Field (Subscription Term)
SSP Source:           List Price
Revenue Account:      4200 - SaaS Revenue
Deferred Account:     2300 - Deferred Revenue - SaaS

ELEMENT: Implementation Services
---------------------------------------------------------------
Recognition Rule:     Over Time - Percent Complete (Cost)
Recognition Period:   Project Dates
SSP Source:           Cost Plus Margin (35%)
Revenue Account:      4300 - Professional Services Revenue
Deferred Account:     2310 - Deferred Revenue - Services

ELEMENT: Support & Maintenance
---------------------------------------------------------------
Recognition Rule:     Over Time - Straight Line
Recognition Period:   12 months from Start Date
SSP Source:           20% of Software License SSP
Revenue Account:      4400 - Support Revenue
Deferred Account:     2320 - Deferred Revenue - Support

Link Elements to Items

Associate Revenue Elements with NetSuite items:

1. Open item record (Lists → Accounting → Items)
2. Navigate to Accounting subtab
3. Set Revenue Recognition Template field
4. This links the item to a Revenue Element

Arrangement Creation

Revenue Arrangements are created automatically from source transactions based on your ARM preferences:

Arrangement Structure

REVENUE ARRANGEMENT ANATOMY
===============================================================

+-------------------------------------------------------------+
| REVENUE ARRANGEMENT HEADER                                   |
|-------------------------------------------------------------|
| Arrangement ID:     RA-00456                                 |
| Source:             Sales Order SO-12345                      |
| Customer:           TechCorp Industries                      |
| Arrangement Date:   2025-03-01                               |
| Total Value:        $250,000                                 |
| Status:             Pending Allocation                       |
+-------------------------------------------------------------+
                    |
                    v
+-------------------------------------------------------------+
| REVENUE ELEMENTS (Performance Obligations)                   |
|------------------+---------+---------+----------+------------|
| Element          | Amount  | SSP     | Alloc %  | Allocated  |
|------------------+---------+---------+----------+------------|
| Software License |$150,000 |$180,000 | 56.25%   | $140,625   |
| Implementation   | $60,000 | $80,000 | 25.00%   |  $62,500   |
| Year 1 Support   | $40,000 | $60,000 | 18.75%   |  $46,875   |
|------------------+---------+---------+----------+------------|
| TOTAL            |$250,000 |$320,000 | 100%     | $250,000   |
+------------------+---------+---------+----------+------------+
                    |
                    v
+-------------------------------------------------------------+
| REVENUE PLANS (Recognition Schedules)                        |
|-------------------------------------------------------------|
| Plan 1: Software License                                     |
|   Amount: $140,625                                           |
|   Recognition: Point in Time (Ship Date: 2025-03-15)        |
|                                                              |
| Plan 2: Implementation                                       |
|   Amount: $62,500                                            |
|   Recognition: Over Time (Mar-Jun 2025, % Complete)          |
|                                                              |
| Plan 3: Year 1 Support                                       |
|   Amount: $46,875                                            |
|   Recognition: Over Time (12 months, Straight-Line)          |
+-------------------------------------------------------------+

Allocation Calculation

ARM allocates the transaction price using relative SSP:

RELATIVE SSP ALLOCATION FORMULA
===============================================================

Allocated Amount = Transaction Price x (Element SSP / Total SSP)

EXAMPLE:
---------------------------------------------------------------
Transaction Price: $250,000
Total SSP: $180,000 + $80,000 + $60,000 = $320,000

Software License Allocation:
$250,000 x ($180,000 / $320,000) = $250,000 x 56.25% = $140,625

Implementation Allocation:
$250,000 x ($80,000 / $320,000) = $250,000 x 25.00% = $62,500

Support Allocation:
$250,000 x ($60,000 / $320,000) = $250,000 x 18.75% = $46,875

Total Allocated: $140,625 + $62,500 + $46,875 = $250,000

Recognition Methods

Point in Time

Revenue recognized when control transfers:

• Ship Date: When goods ship (FOB shipping point)
• Delivery Date: When goods arrive (FOB destination)
• Acceptance Date: When customer formally accepts
• License Effective Date: When software license starts

Over Time - Straight Line

Equal recognition each period over service term:

STRAIGHT-LINE RECOGNITION EXAMPLE
===============================================================

Total Amount: $120,000
Recognition Period: 12 months (Jan 1 - Dec 31)

Monthly Recognition = $120,000 / 12 = $10,000

RECOGNITION SCHEDULE:
---------------------------------------------------------------
Month     | Recognized | Cumulative | Remaining Deferred
----------+------------+------------+--------------------
January   |   $10,000  |   $10,000  |    $110,000
February  |   $10,000  |   $20,000  |    $100,000
March     |   $10,000  |   $30,000  |     $90,000
...       |   ...      |   ...      |     ...
December  |   $10,000  |  $120,000  |          $0

Over Time - Percentage of Completion

Recognition based on progress measure:

PERCENTAGE OF COMPLETION EXAMPLE (COST-TO-COST)
===============================================================

Project: ERP Implementation
Contract Value: $200,000
Estimated Total Cost: $120,000
Margin: 40%

END OF MONTH 3 STATUS:
---------------------------------------------------------------
Costs Incurred to Date:    $45,000
% Complete:                $45,000 / $120,000 = 37.5%
Revenue to Recognize:      $200,000 x 37.5% = $75,000
Previously Recognized:     $50,000
This Period Recognition:   $75,000 - $50,000 = $25,000

JOURNAL ENTRY:
   Dr: Unbilled Receivables     $25,000
   Cr: Revenue - Services               $25,000

Running Recognition

Transactions › Financial › Create Revenue Recognition Journal

1. Select recognition period
2. Choose arrangements to process (or all)
3. Preview recognition amounts
4. Generate journal entries
5. Review and post journals

Modification Types

ASC 606 defines three modification scenarios:

CONTRACT MODIFICATION EXAMPLES
===============================================================

SCENARIO 1: SEPARATE CONTRACT
---------------------------------------------------------------
Original: 100 SaaS seats @ $100/seat = $10,000/month
Modification: Add 25 seats @ $100/seat (list price)

Analysis:
- Additional seats are distinct (customer can use them)
- Price is at SSP ($100 = list price)
Result: Account as separate contract
ARM Action: New Revenue Arrangement for 25 seats

SCENARIO 2: TERMINATION + NEW CONTRACT
---------------------------------------------------------------
Original: 12-month implementation ($120K)
Month 6: Scope change - completely different approach

Analysis:
- Remaining services (months 7-12) are distinct
- New scope is different from original deliverables
Result: Terminate old, start new contract
ARM Action:
- Close original RA (recognize $60K earned)
- Create new RA for revised scope

SCENARIO 3: CUMULATIVE CATCH-UP
---------------------------------------------------------------
Original: Fixed-fee project ($200K over 10 months)
Month 4: Change order adds $30K, extends to 12 months

Analysis:
- Additional work is NOT distinct from original
- Project is one integrated deliverable
Result: Cumulative catch-up adjustment
ARM Action:
- New total: $230K over 12 months
- Recalculate % complete
- Recognize catch-up in current period

Processing Modifications in ARM

1. Create sales order amendment or change order
2. ARM evaluates modification against criteria
3. System prompts for modification type (or auto-determines)
4. Generates appropriate revenue adjustment
5. Updates Revenue Arrangement and plans

Types of Variable Consideration

Estimation Methods

Expected Value

Probability-weighted sum of possible outcomes:

EXPECTED VALUE CALCULATION
===============================================================

SCENARIO: Volume Rebate Program
Customer commits to purchase, rebate tiers based on volume

Possible Outcomes:
---------------------------------------------------------------
Outcome          | Revenue  | Probability | Expected Value
-----------------+----------+-------------+----------------
< $500K (0%)     | $400,000 |    10%      |   $40,000
$500K-$750K (5%) | $570,000 |    30%      |  $171,000
$750K-$1M (7.5%) | $740,000 |    40%      |  $296,000
> $1M (10%)      | $900,000 |    20%      |  $180,000
-----------------+----------+-------------+----------------
Expected Value:                             $687,000

Transaction Price = $687,000

Most Likely Amount

Single most probable outcome--use for binary outcomes:

MOST LIKELY AMOUNT CALCULATION
===============================================================

SCENARIO: Performance Bonus
$50,000 bonus for on-time project delivery

Assessment:
- Project is on track
- 85% probability of achieving bonus
- Binary outcome (either $50K or $0)

Most Likely Amount: $50,000 (since >50% probability)
Transaction Price includes: $50,000 bonus

The Constraint

Include variable consideration only to the extent a significant reversal is NOT highly probable:

ARM Configuration for Variable Consideration

ARM handles variable consideration through:

• Estimated fields: Capture initial estimates on arrangements
• Reassessment triggers: Update estimates periodically
• Constraint application: Apply constraint percentage
• True-up processing: Adjust when uncertainty resolves

Common Journal Entry Patterns

ARM GL FLOW PATTERNS
===============================================================

PATTERN 1: INVOICE BEFORE RECOGNITION (Deferred Revenue)
---------------------------------------------------------------
Invoice Customer:
   Dr: Accounts Receivable         $120,000
   Cr: Deferred Revenue                      $120,000

Monthly Recognition:
   Dr: Deferred Revenue            $10,000
   Cr: Revenue - SaaS                        $10,000


PATTERN 2: RECOGNITION BEFORE INVOICE (Unbilled AR)
---------------------------------------------------------------
Recognize Revenue (% complete):
   Dr: Unbilled Receivables        $25,000
   Cr: Revenue - Services                    $25,000

Invoice Customer:
   Dr: Accounts Receivable         $25,000
   Cr: Unbilled Receivables                  $25,000


PATTERN 3: SIMULTANEOUS (Point in Time)
---------------------------------------------------------------
Ship Product & Invoice:
   Dr: Accounts Receivable         $50,000
   Cr: Revenue - Products                    $50,000


PATTERN 4: ALLOCATION RECLASS
---------------------------------------------------------------
When contract price < total SSP, recognize allocated amounts:

Invoice at Contract Price:
   Dr: Accounts Receivable         $250,000
   Cr: Deferred Revenue - License            $140,625
   Cr: Deferred Revenue - Services            $62,500
   Cr: Deferred Revenue - Support             $46,875

Account Reconciliation

Monthly reconciliation between ARM subledger and GL:

Standard ARM Reports

ASC 606 Disclosure Requirements

Public companies must disclose:

• Disaggregation of revenue: By product line, geography, timing (point vs. over time)
• Contract balances: Receivables, contract assets, contract liabilities with rollforward
• Performance obligations: Remaining obligations and expected timing
• Significant judgments: Timing of satisfaction, transaction price, allocation
• Contract costs: Capitalized costs and amortization

EXAMPLE DISCLOSURE: CONTRACT BALANCES
===============================================================

                              December 31,  December 31,
                                  2025          2024
                              -----------   -----------
Accounts receivable           $45,200,000   $38,500,000
Contract assets (unbilled)     $8,300,000    $6,200,000
Contract liabilities (def rev)$32,100,000   $28,400,000

Revenue recognized during 2025 that was included in
contract liabilities at December 31, 2024: $24,800,000

Revenue recognized during 2025 from performance
obligations satisfied in prior periods: $1,200,000

Conversion Approaches

Conversion Steps (Modified Retrospective)

1. Identify open contracts: Active arrangements with remaining performance obligations
2. Gather historical data: Original terms, amounts, recognition to date
3. Recompute allocations: Apply SSP methodology to each contract
4. Calculate adjustment: Difference between old and new recognition
5. Load conversion entries: Import Revenue Arrangements and plans
6. Record cumulative adjustment: Adjust retained earnings at transition

CONVERSION EXAMPLE
===============================================================

CONTRACT: Multi-year SaaS + Implementation
Original Contract: $360,000 (3 years)
Start Date: July 1, 2024
Go-Live Date: January 1, 2025

OLD METHOD (simple straight-line on total):
---------------------------------------------------------------
Total: $360,000 over 36 months = $10,000/month
Recognized (Jul-Dec 2024): $60,000
Deferred at 12/31/24: $300,000

NEW METHOD (ARM with allocation):
---------------------------------------------------------------
Implementation (SSP $40,000) -> Recognized Jul-Sep 2024
SaaS (SSP $320,000 over 36 months) -> $8,889/month

Proper Recognition (Jul-Dec 2024):
  Implementation: $40,000 (complete)
  SaaS: $8,889 x 6 = $53,333
  Total: $93,333

CONVERSION ADJUSTMENT:
---------------------------------------------------------------
Should have recognized: $93,333
Actually recognized:    $60,000
Adjustment needed:      $33,333

Entry at 1/1/2025:
   Dr: Deferred Revenue         $33,333
   Cr: Retained Earnings                $33,333

Common Issues

Validation Checks

Build these saved searches for ongoing monitoring:

• Items without Revenue Element assignment
• Revenue Elements with missing SSP
• Arrangements pending approval > 7 days
• Recognition journals pending posting
• Deferred revenue balance vs. ARM subledger
• Negative deferred revenue (over-recognition)

Back to Chapter

Return to Chapter 8.9: Advanced Revenue Management for implementation overview.