Glossary

How claims are labelled

Salesforce docsdocumented by SalesforceField experienceobserved on a real orgRecommended patternwhat we recommendTo verifyunverified

Métier

Quote-to-Cash: The whole chain of a sale, from assembling an offer to collecting the payment and booking it. Literally “from quote to cash”.
CRM: Customer relationship management. The system that knows who the customer is, who spoke to them and where the deal stands. It does not natively configure offers or bill.

Revenue Cloud Advanced: Salesforce’s native platform for the quote → order → contract cycle. No namespace, unlike Salesforce CPQ. Often shortened to RCA.
Revenue Cloud Billing: The billing side: schedules, invoices, credit memos, tax, ledger entries. Often shortened to RCB.
Revenue Management: Salesforce’s current name for what was called Revenue Cloud. Both names are still in circulation, including in the official documentation.
Salesforce CPQ: An acquired, earlier product with its own SBQQ__ namespace and its own rule engines. Almost nothing written about the native platform applies to it.
Selling model: How a product is sold: one-time, term-defined or evergreen. It governs what the pricing and billing engines may do with the line.
Bundle: An offer made of a parent product and components, with quantity and compatibility rules.
Classification: What a product is, and therefore which attributes it carries. Not to be confused with the category, which only says where a seller finds it.

Namespace: A prefix on object and field names, showing they come from an installed package. Checking an org’s namespace is the fastest way to know which product you are dealing with.
Context definition: The data contract: what the pricing, tax and document engines are allowed to see. Extending it once serves all three.
Dynamic Revenue Orchestrator: The layer that decomposes a sales transaction into fulfilment lines and maintains asset state. Often shortened to DRO.
Org: A Salesforce instance. Production, pre-production, sandbox or demo — each with its own configuration, and therefore its own behaviour.
Permission set: A set of permissions granted to a user. On Revenue Cloud, many objects look absent when they are merely invisible for lack of permission.

Pricing procedure: The ordered list of steps that turns a list price into a net price. Technically an expression set. The version that runs is a compiled one, not the one you edit.
Expression set: The object holding a sequence of executable rules. A pricing procedure is one.
Decision table: A lookup table returning a value for a set of inputs. Only worth using when there is a condition or a tier: a flat price belongs on the price book entry.
PricebookEntry: A product’s price in a price book, for a selling model and a currency. Where a price that depends on no condition belongs.

Billing schedule: The billing plan for an order line: what to invoice, when, over which period. Produced by the engine, never keyed in by hand.
Billing schedule group: The grouping that makes several schedules come out on a single invoice.
Avoir: The document that cancels or reduces an invoice already issued. It is how you correct the past: an issued invoice is not edited.
Prorata: The partial calculation applied when a service period does not start at the beginning of a cycle. How it is computed depends on configuration.

Reconnaissance du revenu: When revenue is booked in the accounts. Independent of the invoice date and of the collection date.

Legal entity: The selling legal entity. Tax treatments and rates hang off it.
Tax treatment: The rule tying a product and a tax code together under a tax policy.
Tax engine adapter: An Apex class that computes tax when the shipped engine is not enough. Registered through a provider and an engine.

Actif: What the customer holds at a given moment. Its state is kept over time, which is what lets you say what they held on a past date.
Avenant: A new transaction read against the current asset state, producing a delta. It is not an edit of the original order.