# Continuous Control

> Continuous Control connects Salesforce Revenue Cloud to NetSuite. It books Revenue Cloud orders into NetSuite, syncs invoices, credit memos, payments and refunds, and runs a revenue recognition engine in NetSuite whose results flow back to Salesforce. It ships as a Salesforce unlocked package plus a NetSuite SDF release zip.

Every page below is the Markdown version of a page on the docs site, written for agents and developers. It keeps the technical detail (API names, payloads, script ids, limits) that the human pages leave out. To load everything at once, fetch https://taggalongtech.github.io/continuous-control/llms-full.txt.

Automating setup with Claude Code: start with https://taggalongtech.github.io/continuous-control/automate-with-claude-code.md.


## Getting Started

- [Welcome](https://taggalongtech.github.io/continuous-control/index.md): Continuous Control connects Salesforce Revenue Cloud to NetSuite so you can bill in Salesforce and recognize revenue in NetSuite.
- [How it works at a glance](https://taggalongtech.github.io/continuous-control/how-it-works.md): How an order, an invoice and a payment travel from Salesforce to NetSuite, and how the revenue results come back.
- [Prerequisites](https://taggalongtech.github.io/continuous-control/prerequisites.md): What you need in Salesforce and NetSuite, and what to collect, before you install Continuous Control.
- [Quickstart](https://taggalongtech.github.io/continuous-control/quickstart.md): From two connected environments to a booked order, a synced invoice, and recognized revenue.
- [Automate with Claude Code](https://taggalongtech.github.io/continuous-control/automate-with-claude-code.md): Use Claude Code or another AI agent to install and set up Continuous Control. Every docs page has a Markdown version with the full technical detail, plus a downloadable setup skill.
- [Demo install runbook](https://taggalongtech.github.io/continuous-control/demo-install-runbook.md): Set up a Revenue Cloud demo org: install, connect to the shared demo NetSuite account, place the cards, and prepare the QuantumBit catalog and customers.
- [Demo the recognition methods](https://taggalongtech.github.io/continuous-control/demo-recognition-methods.md): A demo script with three QuantumBit customers that shows the recognition methods on the QuantumBit Complete Solution, from quote to recognized revenue.
- [Demo without a NetSuite account](https://taggalongtech.github.io/continuous-control/simulated-netsuite.md): Turn on Simulated NetSuite to demo the invoice, payment, refund and credit memo cards with no NetSuite account. Every sync completes inside Salesforce.

## General Concepts

- [The revenue lifecycle](https://taggalongtech.github.io/continuous-control/revenue-lifecycle.md): What Booked, Billed, Recognized and Deferred mean, and which records move each one.
- [The data model](https://taggalongtech.github.io/continuous-control/data-model.md): Which records Continuous Control adds in Salesforce and NetSuite, and how each NetSuite record stays paired with its Salesforce twin.
- [Performance Obligations](https://taggalongtech.github.io/continuous-control/performance-obligations.md): A performance obligation is one promise to a customer. Here is how order lines group into them and how they track revenue.
- [Recognition methods](https://taggalongtech.github.io/continuous-control/recognition-methods.md): The six recognition methods, when each one earns revenue, and how to set one on a product.
- [Billing mirrors](https://taggalongtech.github.io/continuous-control/billing-mirrors.md): How your Salesforce billing schedules are copied into NetSuite for viewing, and how they update when you invoice.
- [Sync runs & idempotency](https://taggalongtech.github.io/continuous-control/sync-runs-idempotency.md): Every sync is logged as a record you can open, and running a sync again updates records instead of duplicating them.
- [One engine, two switches](https://taggalongtech.github.io/continuous-control/one-engine-two-options.md): What the Continuous Revenue Engine does, what keeps running when you turn it off, and when to turn it off.

## Installation

- [Install the Salesforce package](https://taggalongtech.github.io/continuous-control/install-salesforce.md): Install the Continuous Control package into a Salesforce org that has Revenue Cloud with Billing.
- [Build a test org](https://taggalongtech.github.io/continuous-control/build-test-org.md): Build a Revenue Cloud scratch org with sample data and install Continuous Control into it for demos and testing.
- [Install the NetSuite components](https://taggalongtech.github.io/continuous-control/install-netsuite.md): Install the Continuous Control NetSuite components with the release installer, then create the login Salesforce uses.
- [NetSuite manual setup](https://taggalongtech.github.io/continuous-control/netsuite-manual-setup.md): Finish Continuous Control setup in the NetSuite UI: the settings record, custom sublists, preferred forms and existing items.

## Configuration

- [The Connection wizard](https://taggalongtech.github.io/continuous-control/connection-wizard.md): The NetSuite Connection tab walks an admin through connecting the two systems in nine guided steps, each with its own verification.
- [Credentials & authentication](https://taggalongtech.github.io/continuous-control/credentials-auth.md): How Salesforce logs in to NetSuite with Token-Based Authentication, and how to enter, protect and replace the credentials.
- [Field mappings](https://taggalongtech.github.io/continuous-control/field-mappings.md): Choose which Salesforce values fill which NetSuite fields, on the Calls & Mappings tab.
- [Configurable calls](https://taggalongtech.github.io/continuous-control/configurable-calls.md): Every sync is a call you can change without code: edit what it sends, add your own objects, build new calls, and publish when you're ready.
- [Change what a call sends](https://taggalongtech.github.io/continuous-control/calls-edit-mappings.md): Turn off, rename or delete the objects in a shipped call, change which addresses it sends, and reset it to how it shipped.
- [Book orders as Sales Orders](https://taggalongtech.github.io/continuous-control/calls-sales-orders.md): Point Order Booking at a NetSuite Sales Order or another transaction, and see what changes when you do.
- [Add your own objects to a call](https://taggalongtech.github.io/continuous-control/calls-add-objects.md): Send one of your own Salesforce objects to NetSuite as part of an existing call, as a record, a transaction or a line.
- [Build a call of your own](https://taggalongtech.github.io/continuous-control/calls-create-call.md): Build a new call from scratch, using a Quote booked as a NetSuite Estimate as the example, then run it from a sync card or a Flow.
- [Send a call somewhere else](https://taggalongtech.github.io/continuous-control/calls-endpoints.md): Point a call at another RESTlet in your NetSuite account or at an outside URL, and manage the endpoints your calls share.
- [Sync settings](https://taggalongtech.github.io/continuous-control/sync-settings.md): Org-wide settings that control the sync, from the revenue engine switch to failure alerts and run cleanup.
- [Placing the components](https://taggalongtech.github.io/continuous-control/placing-components.md): Add the Continuous Control cards to your Salesforce record pages, and automate syncs with Flow actions.

## Using Continuous Control

- [Booking an order](https://taggalongtech.github.io/continuous-control/booking-an-order.md): Book an activated order to send it to NetSuite as an RC Contract and start tracking its revenue.
- [Amendments](https://taggalongtech.github.io/continuous-control/amendments.md): Book an amendment order to send only what changed and adjust revenue from the change date forward.
- [Invoices & credit memos](https://taggalongtech.github.io/continuous-control/invoices-credit-memos.md): Sync posted invoices and credit memos to NetSuite, with Salesforce tax, so NetSuite tracks what customers owe.
- [Payments & refunds](https://taggalongtech.github.io/continuous-control/payments-refunds.md): Sync payments and refunds to NetSuite so both systems show the same open balances.
- [Running the revenue engine](https://taggalongtech.github.io/continuous-control/revenue-engine.md): Run the revenue engine on the RC Contract in NetSuite to build revenue plans and post recognition to the ledger.
- [Monitoring & troubleshooting](https://taggalongtech.github.io/continuous-control/monitoring-troubleshooting.md): Find and fix failed syncs from the Sync Runs tab, with a table of common error messages.

## Architecture

- [Architecture overview](https://taggalongtech.github.io/continuous-control/architecture-overview.md): How the Salesforce and NetSuite halves of Continuous Control fit together, and the signed call that connects them.
- [The Book Order call flow](https://taggalongtech.github.io/continuous-control/book-order-call-flow.md): How a booking runs from the button click to the booked contract, with the exact classes and hand-offs involved.
- [Anatomy of the payload](https://taggalongtech.github.io/continuous-control/payload-anatomy.md): What's inside the JSON payload a booking sends to NetSuite, key by key.
- [Inside the RESTlet](https://taggalongtech.github.io/continuous-control/inside-the-restlet.md): How the NetSuite RESTlet dispatches every sync, resolves records, writes them, and reports back.
- [The engine Suitelets](https://taggalongtech.github.io/continuous-control/engine-suitelets.md): How the three server-side processes behind the contract buttons group POBs, build revenue plans, and post recognition journals.
- [Writebacks & the POB mirror](https://taggalongtech.github.io/continuous-control/writebacks-pob-mirror.md): NetSuite answers every sync with an id map. Salesforce stamps those ids back, and the engine run mirrors the POBs into Salesforce so the Contract shows live revenue.
- [Security model](https://taggalongtech.github.io/continuous-control/security-model.md): What crosses the wire between Salesforce and NetSuite, how it's signed, where secrets live, and what each side can do.

## Reference

- [Flow actions](https://taggalongtech.github.io/continuous-control/ref-flow-actions.md): Twelve invocable actions for building automation, each starting a tracked sync run and returning right away.
- [RESTlet actions](https://taggalongtech.github.io/continuous-control/ref-restlet-actions.md): Every RESTlet action, with the request it takes and the response it returns.
- [Shipped calls](https://taggalongtech.github.io/continuous-control/ref-shipped-calls.md): What each of the package's nine calls does, where it runs from, and which NetSuite record type each node writes to.
- [Settings reference](https://taggalongtech.github.io/continuous-control/ref-settings.md): Every setting on both sides of the connection, and what each one controls.
- [NetSuite record reference](https://taggalongtech.github.io/continuous-control/ref-netsuite-records.md): The twelve custom records Continuous Control adds to NetSuite, with their key fields and relationships.
- [Sync status fields](https://taggalongtech.github.io/continuous-control/ref-sync-status-fields.md): Four fields on every synced Salesforce object record the NetSuite id and the last sync outcome.
- [Versions & compatibility](https://taggalongtech.github.io/continuous-control/ref-versions.md): The Salesforce and NetSuite halves version independently and check each other at setup time.
- [Release notes](https://taggalongtech.github.io/continuous-control/release-notes.md): What each Continuous Control release changed, newest first, with the steps to upgrade and the limitations worth knowing.
- [Roadmap](https://taggalongtech.github.io/continuous-control/roadmap.md): What we are building now, what is up next, what we are exploring, and what has shipped.