What Revenue Cloud Advanced adds
Legacy CPQ + Billing is being superseded by Revenue Cloud Advanced (RCA) built on Industries Common Components. Core new objects:
- Product Catalog (Industries model, effective-dated)
- Order + Order Item (subscription-aware, standard objects, not CPQ's
Order__c) - Asset as the source of truth for what the customer owns
- Fulfillment Order → Billing Schedule → Invoice
Everything is API-first — Order Management APIs are the same the LWC and MuleSoft use.
Subscription primitives
- One-time — charge once, no schedule
- Recurring — monthly/quarterly/annual, aligned to term
- Usage — metered, rated via Rate Cards and Usage Records
- Tiered / volume — pricing rules on the Rate Card
Rate Card: API Calls
Tier 1: 0 – 100,000 → $0.000 (included)
Tier 2: 100k – 1,000,000 → $0.0004
Tier 3: 1M+ → $0.0002
Aggregation: Sum per Billing Period, Volume-based
Ingesting usage at scale
Usage arrives through the Usage Records API. Batch, don't stream individual events:
POST /services/data/v62.0/commerce/usage-records/actions/upload
Content-Type: application/json
{
"usageRecords": [
{ "subscriptionId":"a0X...", "quantity": 250, "usageDate":"2026-01-15", "eventId":"evt_01H..." },
...
]
}
Deduplicate on eventId — the API is idempotent when you supply one.
Amendments, renewals, and co-terms
The three operations every subscription business needs, and where legacy CPQ struggled:
- Amendment — add/remove/change quantity mid-term
- Renewal — extend the term, price uplift rules
- Co-terming — align a new subscription's end date with an existing one
RCA models these declaratively. The Change Cart UI produces a delta order that references the source Asset — no more cloning quotes.
Revenue recognition
RCA integrates with Sub-Ledger Accounting (or exports to NetSuite / SAP). Revenue Schedules generate from Order Items:
Order Item: $12,000 / 12 months / Ratable
Revenue Schedule:
2026-01 → $1,000
2026-02 → $1,000
...
For usage: recognition happens at Rating, not ContractStart.
Migration from CPQ + Billing
Two-phase pattern that actually works:
- Coexist — RCA runs new lines of business; legacy CPQ keeps existing ones
- Cut over per product family — migrate Assets + open Contracts one family at a time, script the data move via Bulk API 2.0
Do not attempt a big-bang cutover. Every implementation that tried is a case study we've seen.
Testing
- Order Management APIs are covered by simulation endpoints — use them in CI
- Rating logic is deterministic — write Apex tests against Pricing Procedures
- Contract-level tests: create → amend → renew → cancel, assert Asset state at each step