SuiteBilling: What It Does
SuiteBilling is NetSuite's subscription and usage billing module. It manages billing schedules, subscription changes (upgrades, downgrades, cancellations), proration, and invoice generation. If you bill customers on a recurring basis, whether monthly, annually, or usage-based, SuiteBilling automates the creation of invoices based on the terms you configure.
Key capabilities:
Subscription management with mid-term changes (upgrade, downgrade, suspend, terminate)
Charge-based billing (flat, tiered, volume, overage)
Proration rules for partial-period changes
Renewal management with auto-renewal or manual renewal workflows
Rating and invoice generation on configurable schedules
ARM: What It Does
Advanced Revenue Management handles revenue recognition under ASC 606 and IFRS 15. It determines when and how revenue is recognized, independent of when the invoice is sent. ARM takes your contracts, identifies performance obligations, allocates the transaction price based on standalone selling prices (SSP), and creates revenue recognition schedules.
Key capabilities:
Revenue arrangement creation from sales orders, invoices, or subscription records
Fair value allocation across multiple performance obligations
Recognition patterns: over time (straight-line, percentage-of-completion) or at a point in time
Contract modification handling (prospective or cumulative catch-up)
Revenue waterfall reporting for forecasting and audit
How They Work Together
SuiteBilling generates the invoice. ARM determines when the revenue from that invoice gets recognized. A customer might be billed annually upfront (SuiteBilling creates a single invoice for $120,000), but revenue is recognized monthly over the service period (ARM creates 12 monthly recognition events of $10,000 each).
The two modules share data through revenue elements. When SuiteBilling creates a charge, it can feed into ARM as a revenue element within a revenue arrangement. The billing event triggers the cash and AR entry. The ARM schedule triggers the revenue entry. They are independent journal entries that happen on different timelines.
Where Teams Get Confused
Thinking billing = revenue
Billing is a cash event. Revenue recognition is an accounting event. They happen at different times for different reasons. Conflating them leads to misstated financials.
Not setting up SSP tables correctly
ARM allocates revenue based on standalone selling prices. If your SSP table is not maintained (or does not exist), ARM cannot allocate correctly, and your revenue waterfall will be wrong.
Ignoring contract modifications
When a customer upgrades mid-term, both SuiteBilling and ARM need to handle it. SuiteBilling prorates the billing. ARM needs to determine whether the modification is treated prospectively or as a cumulative catch-up. If this is not configured, your revenue will be misstated.
Enabling both without a clear data flow
You need to map the data flow: subscription record to charge to invoice to revenue arrangement to recognition schedule. If any link in that chain is misconfigured, you get orphaned records or double-counted revenue.
Do You Need Both?
Not necessarily. If you bill on a recurring basis but recognize revenue at the point of billing (simple monthly SaaS with no multi-element arrangements), you might only need SuiteBilling. If you have complex contracts with multiple deliverables but bill on simple terms, you might only need ARM. Most companies that sell subscriptions with professional services, implementation fees, or bundled hardware need both.
Quick Decision Matrix
SuiteBilling only: Simple recurring billing, single performance obligation, revenue = billing
ARM only: Complex contracts with multiple deliverables, but simple invoicing (milestone or upfront)
Both: Recurring billing + multi-element arrangements + ASC 606 allocation requirements
How We Approach Revenue Configuration
SuiteBilling and ARM are complex modules that require deep expertise in both the technical configuration and the accounting standards behind them. Our team has configured these modules across SaaS, professional services, hardware, and hybrid business models. We understand the edge cases because we have seen them.
We work collaboratively with your revenue accounting team and your auditors. Configuration decisions are documented with the accounting rationale alongside the technical setup. When your auditors ask "why is this revenue arrangement structured this way," the answer is already written down.
Post-implementation, StrongSupport provides ongoing access to the same team that built your configuration. New contract types, pricing changes, or audit questions are handled by people who already know your setup. No re-onboarding. No context loss.
Getting SuiteBilling and ARM right requires understanding your contracts, your billing terms, and your revenue recognition policies before touching the system. Configuration without that clarity creates problems that compound every month.
Or email us directly at hello@sixstrong.io
