The lightweight path from Salesforce revenue to the NetSuite ledger.
The customer, and nearly everything they do, stays on Salesforce. Continuous Control posts transactions to the NetSuite general ledger, or runs revenue out of NetSuite, with or without NetSuite ARM. Prebuilt native apps on both platforms. No middleware, no custom build.
native to both · no middleware NetSuite · the books tie out
Unlocks Agentforce Revenue Management adoption
The large NetSuite-finance installed base can adopt RCA/RCB without an integration project. The books objection disappears in the first call.
Keeps the lifecycle on platform
Billing, collections, and payments stay in Salesforce in every recommended method. More platform footprint, more Agentforce surface.
Lightweight, not another project
Prebuilt app on both sides, prebuilt mappings, no middleware. The easy attach to an Agentforce Revenue Management deal, not an integration project.
No integration black box, and nothing new to build
Salesforce
Owns the customer · native package
Salesforce record
Order · Invoice · Payment · Credit Memo
↓
Finance Staging
one row per record, status tracked
↓
Finance Sync Job
maps, validates, writes · one-click retry
Continuous
The prebuilt sync
Config fetch first
subsidiaries · currencies · countries · categories, so every transaction lands in the right place
↓
Order graph + A/R documents out
to NetSuite, matched on Salesforce IDs
↓
Ids, status + revenue back
on every record · recognized revenue to the Contract
NetSuite
Owns the books · native SuiteApp
ARM Contract → Orders → Lines
the mirrored order graph
↓
Performance Obligations
lines grouped by rule · Revenue Plans + Schedules
↓
Journal Entries → General Ledger
Dr Deferred · Cr Revenue, per period
Staging, jobs, status, and retry are all native to the Salesforce org. Already standardized on MuleSoft, Celigo, Boomi, or Workato? The same certified mappings ship as prebaked recipes on the middleware you own. What the customer stops buying: a middleware license, an SI integration build, the maintenance contract that follows it, a separate billing engine, and a separate revenue engine.
Method 1
Salesforce-First
Version: Ledger
SF · Customer 360 + A/R + Revenue (RightRev)
NS · General Ledger
Integrating transactions to the ledger, everything else on Salesforce
+Whole customer and revenue lifecycle on Salesforce; full Agentforce
−Revenue on Salesforce needs RightRev (separate purchase)
Method 2
NetSuite Revenue
Version: Revenue
SF · Customer 360 + A/R subledger
NS · Revenue + General Ledger
Revenue out of NetSuite, with or without ARM, while A/R stays on Salesforce
+Revenue in NetSuite without buying a Salesforce-side revenue engine
−Split subledgers: A/R on Salesforce, revenue in NetSuite
Method 3
Unified Books
Version: Books
SF · Customer 360
NS · A/R + Revenue + General Ledger
Front office on Salesforce, books fully consolidated in NetSuite
+Automatic: Continuous Control syncs RCA/RCB in; A/R, revenue and GL all in NetSuite
−Subledgers run in NetSuite, not on the Salesforce platform
Method 4 · custom
Back-Office Sync
Version: Back Office
SF · Customer 360 + Sales · status synced back
NS · Native billing + A/R + Revenue + GL
Customers set on billing natively in NetSuite, a custom path
+Supported with a standard, certified sync (order out, invoice / A/R status back)
−Standard NetSuite limits & more NetSuite work; blocks a future Salesforce billing opportunity
The books (the General Ledger) always run from NetSuite. Revenue on Salesforce uses RightRev. Methods 1–3 keep billing on Salesforce, the recommended, fully-supported path.
Every object we provide a prebuilt mapping for
Badges show the method each mapping unlocks at; mappings are cumulative, so Method 3 includes everything. Derived records are built in NetSuite by the Continuous engine. Every record matches on its Salesforce ID, so re-syncing never duplicates.
See it before you show it
01 · The placemat
Set up, map, and monitor from one place
The Continuous home in Salesforce: connect NetSuite, choose what syncs, map objects, and watch it run. Set Up · Map & Sync · Monitor & Operate · Reference Data, all on one screen.
Watch the demo →
02 · Prebuilt mappings
Every object mapped out of the box
Account to customer, order to the ARM order graph, invoice to invoice. The mappings ship prebuilt and editable, with per-object toggles. No mapping spreadsheet, no field-by-field build.
Watch the demo →ARM Contractmirrored from Salesforce
03 · The NetSuite objects
The books side: obligations and the waterfall
The SuiteApp holds the mirrored contract, groups lines into Performance Obligations, and rolls Booked / Billed / Recognized on every obligation and the contract. Revenue posts as journal entries to the GL.
Watch the demo →
04 · Mission Control
Every transaction tracked to the books
Pending, in-progress, and attention-required syncs on one dashboard, with history. Errors are one click to retry. Nothing hidden in middleware; finance and admins see the same truth.
Watch the demo →
05 · Book Order, one click
The whole order graph, in one call
From the Salesforce Order: customer, contract, order, lines, billing schedules and periods land in NetSuite in a single call, with per-object status and a deep link to the ARM Contract.
Watch the demo →Versions match the deal type, one for one
Ledger
Version 1 · Method 1
Config fetch: subsidiaries, currencies, accounts
Account → Customer
Summary GL postings (one-way) with a reconciliation report
Postings only; no Continuous objects in NetSuite
Revenue
Version 2 · Method 2
Everything in Ledger
Native Continuous objects in NetSuite: ARM Contract / Orders / Lines / POBs / Revenue Plans + Schedules
Rev-rec engine (or the native ARM bridge); A/R as summary JEs
Adds the Continuous objects + revenue engine
Books
Version 3 · Method 3
Everything in Revenue
A/R documents: invoices, credit memos, payments, refunds
Obligation Details + the Billed waterfall
Syncs the most objects into NetSuite
Back Office
Version 4 · Method 4 · custom
Standard certified sync only: order out, invoice / A/R status back
Does not power native NetSuite billing; standard NetSuite limits apply
Scoped per engagement
We recommend billing on Salesforce
1 · Where should revenue run?
On Salesforce (with RightRev) → Method 1. In NetSuite, with or without ARM → Methods 2–3.
2 · Where should A/R live?
On Salesforce → Methods 1–2. Consolidated in NetSuite → Method 3.
3 · Set on native NetSuite billing?
That is Method 4, a custom path. Steer to billing on Salesforce when you can: it keeps the lifecycle (and the future billing opportunity) on platform.
Bring Continuous Control into your Agentforce Revenue Management deals.
1 · Spot the NetSuite objection→2 · Qualify the method (3 questions)→3 · Continuous demos with your team