Billing mirrors

You bill in Salesforce. Continuous Control copies your Salesforce billing schedules into NetSuite, so NetSuite users can see what's been billed and what's coming. The copies are for viewing only.

See what's copied

QuantumBit bills Kingsbridge Digital's one-year subscription each quarter. In Salesforce, that's one billing schedule group, a schedule for the line and four billing periods. NetSuite gets a matching record for each.

SalesforceNetSuiteWhat it shows
Billing Schedule GroupRC Billing Schedule GroupHow and when the customer is billed, the term, and what's billed and still to bill
Billing ScheduleRC Billing ScheduleOne per order line: how often, how much, totals and status
Billing Period ItemRC Billing PeriodOne per period: dates, amount and status. Once billed, it links to the NetSuite invoice.

RC stands for Revenue Cloud. You'll find the copies on the RC Contract and on the NetSuite customer. Nothing in NetSuite bills from them. Billing runs stay in Salesforce.

Know how the records link

The copies keep the Salesforce structure. Groups belong to the customer, as they do in Salesforce, so they show on the NetSuite customer record. Each schedule links to its group and its order line. After the engine runs, it links to its performance obligation too. Each period links to its schedule and group.

Salesforce leaves a few group fields blank, such as start and end dates. Continuous Control fills them in from the schedules.

Periods appear only once Salesforce creates them. A Salesforce billing run adds future periods. If Salesforce removes a period, the next sync removes it from NetSuite too. Nothing is forecast.

Watch the copies update when you invoice

When QuantumBit syncs Kingsbridge's first quarterly invoice, the same call refreshes the billing records it used. That covers the schedule, its group and all its periods.

Right after the sync, NetSuite shows the new billed and remaining amounts. The billed period is marked and links to the NetSuite invoice. See Invoices & credit memos.

Follow amendments

When Kingsbridge adds API units, Salesforce creates a new billing schedule linked to the original. NetSuite keeps that link. The new schedule sits in the same group, so the group's totals include the original and the amendment.

Billing records don't drive revenue. They're there for people to read. Revenue follows the obligation's recognition method. Event-Based obligations follow the actual invoice lines, not the schedules. That keeps what you plan to bill apart from what you've earned.