ARM & Revenue Recognition

Revenue recognitionthat survives the audit.

We configure NetSuite ARM for companies where revenue isn't simple. Multi-element arrangements, variable consideration, usage-based billing, hybrid license-and-services models. The configurations that keep your auditors quiet and your close on schedule.

The Problem

ARM doesn't tell you when it's wrong.

NetSuite's Advanced Revenue Management module is powerful. It handles fair value allocation, multi-element bundling, amortization schedules, and deferred revenue journals. But it has a blind spot: it won't flag its own data-integrity failures.

Arrangement totals can quietly drift from the sum of their element allocations. Revenue elements get created without revenue plans. Credit memos post without touching a single element. Plans sit on hold-recognition with balances that should have been released two periods ago.

None of these show up as errors in NetSuite. They show up at quarter-end, when a controller is manually running saved searches at 11pm. Or they show up in audit.

Allocation drift
Arrangement total ≠ sum of element allocations. ARM won't tell you.
Orphaned elements
Revenue elements generated without a revenue plan. They sit there indefinitely.
Unlinked credit memos
Posted credit memos with no generated revenue element in the open period.
Template drift
Active plans whose rev rec rule no longer matches the item's current rule.
Stale holds
Plans flagged hold-recognition with remaining balance past their end date.
What We Do

ASC 606 configuration that actually holds up.

We've configured ARM for SaaS companies, professional services firms, and hybrid license models. Every engagement starts from the revenue contract and works backward into NetSuite.

Configuration
ARM Setup & SSP Allocation
We build the revenue recognition framework from your contracts. Fair value pricing, standalone selling prices, allocation rules, performance obligation mapping. Every element gets a plan, every plan gets a schedule, every schedule ties to GL.
SaaS, professional services, and hybrid license-and-services models. ASC 606 and IFRS 15.
Close Process
Revenue Close & Reconciliation
Deferred revenue roll-forwards, unbilled receivable reconciliation, arrangement-level variance analysis. We design the close checklist and the saved searches that support it. Your month-end rev rec close should take hours, not days.
Designed for multi-entity orgs running consolidated closes across 5–15+ subsidiaries.
Audit
Audit-Ready Schedules
We build the reconciliation package your auditors actually want. SSP documentation, allocation waterfalls, deferred revenue roll-forwards by arrangement, and JE trace-back to source transactions.
Zero audit findings on first-year ARM engagements.
Migration
ARM Data Migration
Moving from spreadsheet rev rec or a legacy system into ARM. Historical arrangement import, opening balance load, mid-stream plan creation for in-flight contracts. No recognition gaps.
We've migrated orgs with 3,000+ active arrangements into ARM.
Governance
Ongoing ARM Governance
Monthly ARM health checks, configuration drift monitoring, new arrangement review. We catch the problems that build up between quarters. Or you can let Sentry do it automatically.

“VCG configured ARM from scratch. We passed our first revenue audit with zero adjustments.”

Controller, SaaS Platform · ASC 606 · $12M recognized
Sentry

The ARM governance tool we kept rebuilding for every engagement.

Sentry runs inside NetSuite and reads ARM tables directly via SuiteQL. No external data sync. No separate platform. It runs a catalog of governance checks against your revenue arrangements, elements, plans, and fair values, then tells you exactly what will block your close.

Built from the audit prep workflows we run on every ARM engagement. If you've ever rebuilt a set of ARM governance searches from scratch at a new company, this is the tool you wanted.

Preparing close/April 2026
Last run 18:05 PSTUpdate ArrangementsRun checks
Close blocked
$48.7M
Revenue impact across 2,847 records
Export blocker list
This run
Critical5
Warning3
Passing6
Last run18:05 PST
Subsidiaries with findings8 of 33
Cascade Inc.
2 · 5 checks failing
$14.2M
Critical
Boreal Systems
4 · 7 checks failing
$11.8M
Critical
Pacific Wire
7 · 4 checks failing
$9.1M
Critical
Summit Digital GmbH
12 · 3 checks failing
$6.4M
Critical
Redstone Manufacturing
5 · 2 checks failing
$4.8M
Warning
Northvane Solutions AB
3 · 3 checks failing
$2.4M
Critical
▸25 subsidiaries clean · 8 elimination entities excluded
Shared failing checks
Plans Past End Date with Remaining Balance6 of 8 subs
Cascade Industries, Boreal Systems, Pacific Wire, Summit Digital, Redstone Mfg, Northvane
Revenue Element Date Mismatch4 of 8 subs
Cascade Industries, Boreal Systems, Pacific Wire, Summit Digital
Elements Without a Revenue Plan3 of 8 subs
Boreal Systems, Summit Digital, Northvane
Plans Past End Date with Remaining Balance affects 6 of 8 failing subs. Likely a shared root cause - investigate common data sources or ARM configuration.
Close blockers8 checks · 5 failing
Plans Past End Date with Remaining Balance
Plans past end date with remaining deferred balance
$22.1M
1,847 records
Critical
Revenue Element Date Mismatch
Element start/end dates don't match source transaction's revenue period
$14.3M
412 records
Critical
Elements Without a Revenue Plan
Revenue elements with no revenue plan generated
$8.6M
318 records
Critical
Revenue Holds with Unrecognized Balance
Active plans flagged hold recognition with remaining balance
$2.4M
183 records
Warning
Missing Fair Value on Elements
Elements with $0 or null fair value
$1.3M
87 records
Critical
▸3 passing checks

Mockup with fictional data - all subsidiary names are fictional.

How ARM Engagements Work

Start from the contract. Work backward into NetSuite.

01
Contract Review
We read your revenue contracts, not your requirements doc. Performance obligations, variable consideration, SSP methodology - we need to understand the accounting before we touch the system.
02
ARM Architecture
Fair value pricing rules, element creation rules, plan templates, recognition schedules. We design the full ARM data model and walk your team through it before configuration starts.
03
Build & Validate
Sprint-based configuration with test arrangements at every stage. We validate allocation accuracy, recognition timing, and JE output against your expected results. Your auditors get invited to review.
04
Close Support
First close support, hypercare, reconciliation assistance. We stay through at least one full quarter-end close. Then ongoing governance through managed services or Sentry.
Let's Talk

Your ARM configuration should close the books, not create work.

Free 30-minute ARM assessment. We'll review your current rev rec setup, identify the highest-risk gaps, and tell you honestly whether we're the right team.