How it works at a glance
You sell, bill and collect in Salesforce. Continuous Control sends each of those events to NetSuite, where your revenue is planned and recognized. The results come back to the Salesforce Contract.
Send each event in one call
QuantumBit activates Kingsbridge Digital's order for a one-year subscription. When QuantumBit books it, Salesforce gathers everything NetSuite needs into one package. That includes the account, contacts, addresses, products, contract, order, order lines and billing schedules. It sends the package to NetSuite in one secure call.
Because everything arrives together, you never worry about which record goes first. Nothing is left half-synced if a call fails.
Invoices, credit memos, payments and refunds work the same way. Each one travels as a single call. Every call is logged as a sync run, with the data sent and the reply.
Let NetSuite plan the revenue
NetSuite saves Kingsbridge's order as a set of Continuous Control records. The main one is the RC Contract, where RC stands for Revenue Cloud. Then three processes take over.
- Update POBs groups the order lines into performance obligations, one per product on the contract. It adds up what's booked, and ties each invoice line to its obligation to track what's billed. This always runs.
- Update Revenue Plans builds a month-by-month schedule for each obligation. The schedule follows the product's recognition method.
- Recognize Revenue posts one journal entry per period. It moves the amount from Deferred Revenue to Revenue. You see a preview before anything posts.
The first two run on their own after each order or invoice sync. Recognition waits for finance to click the button, or for a scheduled close if you turn one on.
Revenue plans and recognition make up the Continuous Revenue Engine. You can turn it off if you recognize revenue somewhere else. Update POBs keeps running either way. See One engine, two switches.
See the results in Salesforce
Each call returns the NetSuite ids of the records it created. Salesforce saves them on the matching records, with a sync status and time. So every account, order, invoice and payment links to its NetSuite record.
After the engine runs, each obligation comes back as a Performance Obligation record. Kingsbridge's Contract then shows booked, billed and recognized revenue without leaving Salesforce. See Writebacks & the POB mirror.
Know what to click day to day
| When | Where | What you do |
|---|---|---|
| An order is activated | The order | Click Book Order to NetSuite, or let a Flow do it |
| A billing run posts invoices | The Invoice Batch Run | Click Sync Invoices to NetSuite to send every posted invoice |
| Cash arrives | The payment, in either system | Sync the payment. Payments applied in NetSuite come back on a schedule |
| Month-end close | The RC Contract in NetSuite | Click Recognize Revenue and confirm the preview |
| Any time | The Sync Runs tab | Check each call, its status and its data |