Rev-Con-201 cheat sheet

Product-to-Cash sequence: product and price definition → configuration and quoting → contract → order and fulfillment → billing → invoicing → payment → revenue recognition.

Revenue Cloud bundles CPQ, Billing, and Revenue Recognition on one shared set of product, price, quote, order, and invoice records, so transactions are not re-keyed between stages.

Core object chain: Product2 → PricebookEntry → SBQQ__Quote__c / SBQQ__QuoteLine__c → Order / OrderItem → Asset → Invoice → Payment.

An Order is the commitment document that activates records downstream; an Asset records what the customer owns or subscribes to, including quantity and start/end dates.

Contract lifecycle transactions are Amend (change quantities or terms mid-term), Renew (extend into a new term), and Cancel (terminate early); each generates its own quote before affecting the contract.

Data flows one direction down the chain; corrections must be made at the quote or order stage because assets, invoices, and revenue schedules are generated from them.

Cash application closes the loop: payments are recorded and allocated against open invoices, reducing the account balance.

Revenue recognition is the final stage and consumes the same transaction data to build revenue schedules and revenue transactions.

Product2 is the sellable item; PricebookEntry joins Product2 to Pricebook2 and stores List Price, Currency, and Active flag. A product needs an entry in the standard price book before it can be added to any other price book.

Bundle configuration uses Product Feature (a slot or section in the bundle), Product Option (links a bundle to an includable product), and Option Group (visual grouping of related options).

Product Option settings that drive the configurator include Min/Max Quantity, Quantity Editable, Optional, Selected by Default, and Bundled.

Product Rules validate configuration: Validation, Alert, Selection, and Exclusion rules block or warn on invalid combinations at configuration time, not at price calculation time.

A Price Rule has a Price Condition (when it applies), a Price Action (what it changes), and an Evaluation Order that sequences it against other rules and the calculator steps.

Discount Schedules hold tiers keyed on volume, term, or segment; the tier matching the quote line sets the discount percent, and the schedule is attached to the product or injected by a price rule.

Bundle pricing methods: List (sum of component list prices), Bundle (a bundle list price shared across options), Static (fixed bundle price with free options), and attribute-driven pricing via Configuration Attributes.

Configuration Attributes capture buyer selections on a bundle and can carry their own price contribution or feed a price rule that adjusts the bundle total.

Proration charges a partial period proportionally by day; it must be enabled on the subscription pricing so mid-term adds, cancels, and co-terminated changes bill correctly.

The Quote Line Editor calculates and displays list price, net price, net total, discount, and margin; the Calculate action re-runs the calculator after any change to product, quantity, or discount.

The quote calculator runs in stages - list price, price rules, discount schedules, then subscription pricing and proration - so a price rule evaluated before a discount schedule can be overridden by that schedule.

Key quote line fields: Quantity, SBQQ__ListPrice__c, SBQQ__NetPrice__c, SBQQ__CustomerPrice__c, SBQQ__Discount__c, and SBQQ__SubscriptionTerm__c.

Quote Line Groups provide grouped subtotals and group-level discounting; a group-level price rule can distribute a discount across the member lines.

Ordering a quote creates Order and OrderItem records; recurring lines additionally create Subscriptions and Assets, and a Contract when the deal is contracted.

An Amendment quote references the original subscription, flags changed quantities, and on order creates a new contract while the original is marked as amended.

A Renewal quote copies the expiring contract's subscriptions onto new start and end dates; ordering it creates the next-term contract and restarts the term.

Contract Term in months plus Start Date determines the number of billing periods and the subscription end date, so both must be set on the quote before ordering.

A Billing Rule controls how a charge is invoiced: Invoice Type (In Advance vs In Arrears), Billing Type (Recurring, Fixed, Usage), and whether periods are prorated or aligned.

The Billing Schedule is the dated list of billing transactions generated for a subscription or order item; each transaction becomes an invoice line when the invoice is generated.

An Invoice groups billing transactions for one account and legal entity; invoice lines carry quantity, charge amount, tax, and a reference back to the source transaction.

Finance Books hold the accounting entries and Legal Entity identifies the selling entity, currency, and tax registration printed on the invoice.

A Credit Memo is a negative invoice that reduces the balance of an earlier invoice and is applied before or alongside cash.

Payment allocation applies an open payment to one or more invoices; any remainder stays as an unapplied balance on the account until it is matched.

Invoice generation runs in batches by billing period; one run can process all due billing schedules and produce invoices, invoice lines, and PDF documents.

Tax is normally computed by an external engine invoked at invoice generation, which writes tax lines back onto the invoice.

Dunning escalates on days past due with reminder steps and can place the account on hold or block further orders until the balance is cleared.

Subscription end date = start date + term months; the end date sets the coverage boundary and determines renewal eligibility.

Mid-term changes generate prorated charges: an add bills from the change date to period end, and a cancel credits the unused days of the current period.

A Revenue Recognition Rule sets the method and timing; a Revenue Schedule splits the transaction amount into dated Revenue Transactions that post to the ledger.

Recognition methods include straight-line over the service period, percent complete, and milestone or event-based recognition.

A Performance Obligation is a distinct promise to the customer under ASC 606/IFRS 15; each obligation receives its own allocation of transaction price and its own revenue schedule.

When obligations are sold as a bundle, transaction price is allocated across them in proportion to standalone selling price.

Remaining Performance Obligation (RPO) equals contracted but not yet recognized revenue, and is the standard forward backlog metric for subscription businesses.

Deferred revenue balance = amount billed minus amount recognized; it decreases as revenue transactions are posted over the term.

Revenue reporting aggregates recognized, deferred, and scheduled amounts by product, period, and revenue rule to produce forecast and backlog views.

Product-to-Cash sequence: product and price definition → configuration and quoting → contract → order and fulfillment → billing → invoicing → payment → revenue recognition.

Revenue Cloud bundles CPQ, Billing, and Revenue Recognition on one shared set of product, price, quote, order, and invoice records, so transactions are not re-keyed between stages.

Core object chain: Product2 → PricebookEntry → SBQQ__Quote__c / SBQQ__QuoteLine__c → Order / OrderItem → Asset → Invoice → Payment.

An Order is the commitment document that activates downstream records; an Asset records what the customer owns or subscribes to, including quantity, start date, and end date.

Contract lifecycle transactions are Amend (change quantities or terms mid-term), Renew (extend into a new term), and Cancel (terminate early); each produces a quote before the contract changes.

Data flows one direction down the chain; corrections must be made at the quote or order stage because assets, billing transactions, and revenue schedules are generated from them.

Cash application closes the loop: payments are recorded and allocated against open invoices, reducing the account balance.

Revenue recognition is the final stage and consumes the same transaction data to build revenue schedules and revenue transactions.

Product2 is the sellable item; PricebookEntry joins Product2 to Pricebook2 and stores List Price, Currency, and Active flag; a product needs a standard price book entry before any other price book.

Bundle configuration uses Product Feature (a slot or section), Product Option (links a bundle to an includable product), and Option Group (visual grouping of related options).

Product Option settings driving the configurator: Min/Max Quantity, Quantity Editable, Optional, Selected by Default, and Bundled.

Product Rules enforce valid configurations - Validation, Alert, Selection, and Exclusion - and fire during configuration, not during price calculation.

A Price Rule has a Price Condition (when it applies), a Price Action (what it changes), and an Evaluation Order sequencing it against other rules and calculator steps.

Discount Schedules hold tiers keyed on volume, term, or segment; the tier matching the quote line sets the discount, and the schedule is attached to the product or injected by a price rule.

Bundle pricing methods: List (sum of component list prices), Bundle (one bundle list price shared across options), Static (fixed bundle price, options free), and attribute-driven pricing via Configuration Attributes.

Configuration Attributes capture buyer selections on a bundle and can carry their own price contribution or feed a price rule that adjusts the bundle total.

Proration charges a partial period proportionally by day and must be enabled in subscription pricing so mid-term adds, cancels, and co-terminated changes bill correctly.

The Quote Line Editor calculates and displays list price, net price, net total, discount, and margin; the Calculate action re-runs the calculator after any change to product, quantity, or discount.

The quote calculator runs in stages - list price, price rules, discount schedules, subscription pricing, then proration - so a price rule evaluated earlier can be overridden later.

Key quote line fields: Quantity, SBQQ__ListPrice__c, SBQQ__NetPrice__c, SBQQ__CustomerPrice__c, SBQQ__Discount__c, and SBQQ__SubscriptionTerm__c.

Quote Line Groups provide grouped subtotals and group-level discounting; a group-level price rule can distribute a discount across member lines.

Ordering a quote creates Order and OrderItem records; recurring lines also create Subscriptions and Assets, plus a Contract when the deal is contracted.

An Amendment quote references the original subscription, flags changed quantities, and on order creates a new contract while the original is marked amended.

A Renewal quote copies the expiring contract's subscriptions onto new start and end dates; ordering it creates the next-term contract and restarts the term.

Contract Term in months plus Start Date determines the number of billing periods and the subscription end date, so both must be set on the quote before ordering.

A Billing Rule controls how a charge is invoiced: Invoice Type (In Advance vs In Arrears), Billing Type (Recurring, Fixed, Usage), and whether periods are prorated or aligned.

The Billing Schedule is the dated list of billing transactions generated for a subscription or order item; each transaction becomes an invoice line when invoices are generated.

An Invoice groups billing transactions for one account and legal entity; invoice lines carry quantity, charge amount, tax, and a reference to the source transaction.

Finance Books hold accounting entries and Legal Entity identifies the selling entity, currency, and tax registration printed on the invoice.

A Credit Memo is a negative invoice that reduces the balance of an earlier invoice and is applied before or alongside cash.

Payment allocation applies an open payment to one or more invoices; any remainder stays as an unapplied balance on the account until matched.

Invoice generation runs in batches by billing period; one run can process all due billing schedules and produce invoices, invoice lines, and PDF documents.

Tax is typically computed by an external engine invoked at invoice generation, which writes tax lines back onto the invoice.

Dunning escalates on days past due with reminder steps and can place the account on hold or block new orders until the balance clears.

Subscription end date = start date + term months; the end date sets the coverage boundary and determines renewal eligibility.

Mid-term changes generate prorated charges: an add bills from the change date to period end, and a cancel credits the unused days of the current period.

A Revenue Recognition Rule sets method and timing; a Revenue Schedule splits the transaction amount into dated Revenue Transactions that post to the ledger.

Recognition methods include straight-line over the service period, percent complete, and milestone or event-based recognition.

A Performance Obligation is a distinct promise to the customer under ASC 606/IFRS 15; each obligation gets its own allocation of transaction price and its own revenue schedule.

When obligations are sold as a bundle, transaction price is allocated across them in proportion to standalone selling price.

Remaining Performance Obligation (RPO) equals contracted but not yet recognized revenue and is the standard forward backlog metric for subscription businesses.

Deferred revenue balance = amount billed minus amount recognized; it declines as revenue transactions post across the term.

Revenue reporting aggregates recognized, deferred, and scheduled amounts by product, period, and revenue rule to produce forecast and backlog views.