ContinuousControl For your finance and IT reviewers

Every object, prebuilt.

Continuous Control is a pair of native applications, one in Salesforce and one in NetSuite. Every record below has a prebuilt mapping that ships with the product. Nothing here is a custom build, and no data is stored outside the two systems you already own.

Salesforce · Agentforce Revenue Management matches on NetSuite · the Continuous SuiteApp

Customer & catalog

Accountthe customer who signed
→AccountId
Customercustomer · native
Contactthe people on the account
→ContactId
Contactcontact · native
Productthe catalog items sold
→Product2Id
Itemitem · native

Agreement & order graphrecords NetSuite has no native equivalent for

Contractthe master agreement and its term
→ContractId
ARM Contractcustomrecord_ct_agreement
Order · Amendment Orderthe original deal plus every later change
→Order Id
ARM Ordercustomrecord_ct_arm_order
Order Producta line on the order
→OrderItem Id
ARM Order Linecustomrecord_ct_arm_order_line
Order Products, groupedby item across the contract
→derived
Performance Obligationcustomrecord_ct_perf_ob

Billing plan

Billing Schedule Groupthe billing header
→BSG Id
ARM Billing Schedule Groupcustomrecord_ct_bs_group
Billing Schedulewhat bills, per line
→BS Id
ARM Billing Schedulecustomrecord_ct_billing_schedule
Billing Periodand when
→BP Id
ARM Billing Periodcustomrecord_ct_bs_period

Invoices & cashposts to the subledgers and the GL

Invoicea posted Salesforce invoice
→Invoice Id
Invoiceinvoice · native
Credit Memoa posted credit
→CreditMemo Id
Credit Memocreditmemo · native
Paymentcash received, with its allocations
→Payment Id
Customer Payment + applicationscustomerpayment · native
Refundcash returned to the customer
→Refund Id
Customer Refundcustomerrefund · native
Invoice lines × obligationslinks billed amounts to obligations
→derived
Obligation Detailcustomrecord_ct_ob_detail
Performance Obligationcustomrecord_ct_perf_ob
←writes back
Contract · Performance ObligationsCT_POB__c · Booked / Billed / Recognized

Salesforce Records the Continuous SuiteApp adds Native NetSuite

Every record matches on its Salesforce ID, so re-syncing never duplicates. Derived records are built inside NetSuite by the Continuous engine. Your team owns every record in both systems: switch the product off and the data stays exactly where it is.

ContinuousControl · the object mapPage 1 of 2
ContinuousControl For your finance and IT reviewers

The same deal, in both systems.

Sales works the contract in Salesforce. Finance closes the books in NetSuite. Both teams read the same obligations and the same numbers, because one is mirrored from the other rather than re-entered.

The mirror
Performance Obligations on the Salesforce Contract

Your contract's obligations, where sales livesEvery performance obligation on the Salesforce contract, with Booked, Billed, and Recognized kept current from the books.

ARM Contractthe same agreement, mirrored

Bookedsum of obligations
Billedfrom posted invoices
Recognizedfrom posted journals
POB-4 · QB-API-MGMTAPI ManagementStraight-Line
POB-2 · QB-SRV-SOWServices SOW% Complete
POB-101 · QB-CPUCompute usageEvent-Based

The same contract, where finance livesThe mirrored ARM Contract holds the same obligations and rolls the Booked, Billed, and Recognized waterfall your finance team closes on. (Illustration of the NetSuite record.)


How it posts

Book the order

The whole order graph posts to NetSuite in one call: contract, orders, lines, obligations, billing plan.

→

Bill in Salesforce

Invoices, credit memos, payments, and refunds post as native NetSuite transactions, tied out to the penny.

→

Recognize revenue

Journal entries post to the General Ledger, or your existing NetSuite ARM keeps the job. Your choice.

→

Back to the contract

Booked, Billed, and Recognized write back per obligation, so sales and finance never disagree.


What your reviewers ask

Where does the data live?

Only in your Salesforce org and your NetSuite account. No third-party data store, and credentials stay encrypted in your own org.

Does it change our close?

No. A/R, revenue, and the General Ledger stay native in NetSuite, on the records your auditors already accept.

Multi-subsidiary and currency?

Yes. Your subsidiaries, currencies, countries, and tax setup are read first, and every transaction is validated against them.

Do we keep NetSuite ARM?

If you want it. Performance obligations map straight into NetSuite ARM, or the included engine handles recognition. One engine, your pick.

What about our SI?

They keep the configuration work. The integration line leaves their scope, because the mappings ship with the product.

Are we locked in?

No. Every record is a native Salesforce or NetSuite record that you own, matched on Salesforce IDs. Turn it off and the data stays.


Certified

AppExchange certified · Built for NetSuite certified SuiteApp · SOC 1 / SOC 2
Reports available under NDA. Requires Salesforce Agentforce Revenue Management.

Next step

See your quote-to-cash tie out, live.

See it live →

or ask your Salesforce account team to set up a demo with Continuous

ContinuousControl · the object mapPage 2 of 2