NetSuite Advanced Revenue Management (ARM) and Sage Intacct Contracts both recognise revenue inside an ERP, and in both the step that allocates price across obligations sits in an add-on. This comparison uses only each vendor's own public help pages, checked on 23 Oct 2026. Where a page doesn't say something, we write "not published". That means the page we read did not state it, not that the product lacks it. For the method itself, read our ASC 606 SSP allocation guide.
What are NetSuite ARM and Sage Intacct Contracts?
NetSuite ARM is a revenue module inside NetSuite ERP. Oracle says ARM (Essentials) "automates revenue forecasting, recognition, reclassification, deferral, and auditing through a rule-based event handling framework". Sage Intacct Contracts is the contract billing and revenue recognition application in Sage Intacct, whose help page states "complete support for ASC 606 and IFRS 15".
Oracle adds that ARM Essentials and Revenue Allocation support "both existing standards and the new standard", which it names as ASC 606 and IFRS 15. In practice the choice usually follows the ERP you already run. Whether Sage Intacct Contracts can be used without Sage Intacct as the ERP is not published on the pages we read.
How do NetSuite ARM and Sage Intacct compare side by side?
The table below sets each vendor's own wording side by side, row by row, with a link to the page each fact comes from. Every fact was checked on 23 Oct 2026. "Not published" means the page we read did not say it. Vendor pages change, so re-check before relying on any row.
| Topic | NetSuite ARM | Sage Intacct Contracts |
|---|---|---|
| What it is | Revenue module inside NetSuite ERP (Oracle) | Contract billing and revenue recognition in Sage Intacct (Sage Intacct) |
| Standards named | "both existing standards and the new standard" (ASC 606, IFRS 15) (Oracle) | "complete support for ASC 606 and IFRS 15" (Sage Intacct) |
| Allocation basis | SSP, VSOE, ESP, TPE "or some other method"; fair value pricing, range checking, formulas (Oracle) | "multiple-element arrangement (MEA) allocations"; SSP or fair value not named on the pages read (Sage Intacct) |
| Where allocation sits | Revenue Allocation "is an add-on feature" to ARM Essentials (Oracle) | Advanced Revenue Recognition, described as an "add-on subscription" (Sage Intacct) |
| Five-step mapping | Not published (Oracle) | Each step mapped to a Contracts task (Sage Intacct) |
| Recognition methods | Rules and plans; each element "can have a forecast plan and one or more actual plans" (Oracle) | "Straight-line, daily rate, quantity-based, and custom recognition schedules, independent of billing" (Sage Intacct) |
| Modifications | Prospective and retrospective merges (Oracle) | "contract add-ons, change orders, and cancellations"; automatic renewals (Sage Intacct) |
| Audit trail | ARM "automates ... auditing"; audit-trail reports not published (Oracle) | "Provides an audit trail for MEA executions" (Sage Intacct) |
| Multi-book | Parallel processing in a secondary book, "Optional - requires Multi-Book Accounting" (Oracle) | "Multi-book accounting" (Sage Intacct) |
| GL posting | "You must generate revenue recognition journal entries to post the revenue to the general ledger" (Oracle) | "Post revenue recognition" according to the contract line's revenue schedule (Sage Intacct) |
| Price | Not published (Oracle) | Not published; "Contact your Sage Intacct account manager" (Sage Intacct) |
Which add-on do you need to allocate across obligations?
In both ERPs, allocation across obligations sits in an add-on. Oracle says Revenue Allocation "is an add-on feature to Advanced Revenue Management (Essentials)". Sage's help says its Advanced Revenue Recognition add-on "includes support for multiple-element arrangement (MEA) allocations". Which subscription levels include each add-on is not published on the pages we read.
Oracle also names the basis for the fair values it allocates with: "standalone selling price (SSP), vendor-specific objective evidence (VSOE), best estimate of selling price (ESP), third party evidence (TPE), or some other method". Sage's pages describe the MEA allocation but do not name SSP or fair value as its basis, so confirm the configuration with Sage before you document it.
How does each one map to the five ASC 606 steps?
Sage Intacct's help maps each ASC 606 step to a Contracts task: create a contract, create the contract lines, enter the amount, "create a multiple element arrangement (MEA) allocation", then "post revenue recognition" from each line's revenue schedule. Oracle's ARM pages describe arrangements, elements, rules and plans, but do not set out a step-by-step mapping.
In either system, step 2 is a judgement you make before the software runs. Whether setup, training or support is distinct decides whether it becomes its own contract line or revenue element, and that decision drives the allocation more than any setting does.
Which recognition methods does each one support?
Sage lists "straight-line, daily rate, quantity-based, and custom recognition schedules, independent of billing". Oracle describes revenue recognition rules that set "the recognition method, amount source, and start and end date sources", with revenue plans derived from those rules. Each ARM revenue element "can have a forecast plan and one or more actual plans".
Oracle adds that "the actual revenue plans control the posting of revenue". Sage's step 5 posts revenue "according to the contract line's revenue schedule". Both tie recognition to a schedule per obligation, which is what an auditor re-performs.
How does each one handle change orders and modifications?
Oracle documents prospective and retrospective merges. A prospective merge "terminates and locks the original revenue arrangements and creates a new arrangement with the residual values as of the effective date". Sage says Contract Billing can "automate the accounting for contract add-ons, change orders, and cancellations" and can "automatically trigger contract renewals as the contract end date approaches".
Oracle also states when a prospective merge can't be reverted: when it "has recognized revenue or reclassified deferred revenue" or "has contract acquisition costs". That is a documented control point to plan period-end work around. Sage's page does not describe its modification accounting method in more detail.
What does each one cost?
Neither vendor publishes a price on the pages we read. Oracle's ARM help gives no price, and says moving from classic Revenue Recognition needs "NetSuite Professional Services or a qualified NetSuite partner". Sage's help says to "Contact your Sage Intacct account manager" for subscription details, and describes advanced revenue recognition as an add-on subscription.
Why does the setup decision change the allocation?
Step 2 decides it. If setup is a distinct obligation, it takes its own share of the price and is recognised when delivered. If it is not distinct, it joins the subscription and is recognised over the term. Both ERPs model this as contract lines or revenue elements, but the judgement comes before either tool.
Take a $40,000.00, 12-month contract starting January 2027, run both ways through the Soluqube engine.
| Treatment | Obligation | Pattern | SSP | Allocated |
|---|---|---|---|---|
| Setup distinct | Subscription | Ratable, 12 months | $38,000.00 | $35,348.84 |
| Setup distinct | Setup (absorbs residual cent) | Point in time, month 1 | $5,000.00 | $4,651.16 |
| Setup distinct | Total | $43,000.00 | $40,000.00 | |
| Setup not distinct | Subscription incl. setup | Ratable, 12 months | $40,000.00 | $40,000.00 |
If setup is distinct, the $3,000.00 discount is spread pro rata by relative SSP. Month 1 (Jan 2027) recognises $7,596.89: subscription $2,945.73 and setup $4,651.16. Months 2 to 11 recognise $2,945.73 each, and month 12 (Dec 2027) recognises $2,945.81 because the final month absorbs $0.08. The engine result's SHA-256 hash is 936908566cb996e4f4f3920acfc70f6b4e16a8c806efb13b1af259b50d5bcbd9.
If setup is not distinct, the full $40,000.00 is recognised ratably: $3,333.33 in each of months 1 to 11 and $3,333.37 in month 12, which absorbs $0.04. The engine result's SHA-256 hash is f5b417cdac460df761556c9b4c8c2dfcad5ef30fc8b2e27222004d149ff8c606. Both runs end with $0.00 unrecognised. Try either in the app, or check the split in the SSP allocation calculator.
How does Soluqube help with revenue allocation evidence?
Soluqube documents the allocation outside either ERP. You confirm the obligations, price and SSPs. It returns the relative-SSP allocation in integer arithmetic, a full-term schedule that ties to the cent, page-and-excerpt clause evidence for each obligation and a SHA-256-hashed export for your external auditor. You then book the result in NetSuite or Sage Intacct.
Clause evidence is the page and verbatim excerpt behind each obligation. In the app, uploaded text-layer PDFs also get a highlight on the cited line, and exports carry the page and excerpt. Contract extraction is heuristic, so you confirm every field. The point is that the step 2 and step 4 judgements are reviewable whichever ERP books them.
The limits are plain. Soluqube does not do contract-modification accounting, does not handle usage-based fees, and has no billing or ERP sync. For a billing-led comparison, see Maxio vs NetSuite ARM. For vendor-by-vendor detail, see NetSuite ARM alternatives and Sage Intacct revenue recognition alternatives.
To test it on your own deals, send three of your hardest bundled contracts through the design partner programme. Founding prices for the first 10 customers are a free 3-contract workpaper, a $475 audit workpaper (up to 10 contracts), a $1,750 QoE deal pack and $49/month firm tool access; see pricing.
Sources
All checked on 23 Oct 2026.
- Oracle NetSuite help, Advanced Revenue Management: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_4328435538.html
- Oracle NetSuite help, transition to the new revenue standard (ASC 606 / IFRS 15, Multi-Book Accounting): https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4703499262.html
- Oracle NetSuite help, prospective merge of revenue arrangements: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1498077674.html
- Sage Intacct help, about Contracts: https://www.intacct.com/ia/docs/en_US/help_action/Contracts/Using_Contracts/Learn_about/about-contracts.htm
- Sage Intacct help, revenue recognition standard steps (Sage's en_ZA regional help page): https://www.intacct.com/ia/docs/en_ZA/help_action/Contracts/Using_Contracts/Learn_about/recognition-standard-steps.htm
Does Sage Intacct allocate revenue by standalone selling price?▼
The Sage Intacct help pages we read describe step 4 as creating "a multiple element arrangement (MEA) allocation", and say the Advanced Revenue Recognition add-on "includes support for multiple-element arrangement (MEA) allocations". They do not name SSP or fair value as the basis. Ask Sage or your partner for the configuration documentation before relying on it for an audit file.
Can you revert a prospective merge in NetSuite ARM?▼
Sometimes. Oracle's help says prospective merge arrangements include a Revert Change Order button, but you can't revert one that "has recognized revenue or reclassified deferred revenue" or "has contract acquisition costs". Plan period-end work around that point, and confirm the behaviour in your own account.
Can Soluqube post its allocation into NetSuite or Sage Intacct?▼
No. Soluqube has no billing or ERP sync today. It produces the allocation, the schedule and a hashed export with clause evidence, and your team books the result in NetSuite or Sage Intacct. It also does not handle contract modifications or usage-based fees yet.