Salesforce Revenue Cloud, RCA, RCB and ARM: The Complete Guide

The vocabulary around Revenue Cloud has shifted a lot in recent years: Revenue Lifecycle Management, Revenue Cloud Advanced, Revenue Cloud Billing, Agentforce Revenue Management… This guide puts things in order. It draws on the Revenue Cloud projects we run at Meir IT for SaaS vendors, services firms and manufacturers in France and French-speaking Switzerland.

What is Salesforce Revenue Cloud (ARM)?

Revenue Cloud is the Salesforce solution that manages the entire revenue lifecycle: defining what you sell and at what price, configuring it, pricing it in a quote, turning it into an order, then into a contract and assets, renewing it and, finally, billing it. Salesforce now sells it as Agentforce Revenue Management (ARM), to highlight the role of AI agents in these processes. In practice, teams and documentation still talk a lot about "Revenue Cloud", "RCA" and "RCB".

The fundamental difference from earlier generations: Revenue Cloud is built directly into the core of the Salesforce platform (standard Quote, Order, Asset, Contract objects, etc.) rather than in a managed package installed on top. That changes how you configure it, extend it and evolve it.

RCA vs RCB vs ARM: what is the difference?

• ARM (Agentforce Revenue Management): the current commercial name for the Revenue Cloud offering as a whole.
• RCA (Revenue Cloud Advanced) is the "pre-sales and lifecycle management" part: catalogue, pricing, configuration, quotes, orders, orchestration, contracts, assets, renewals, usage.
• RCB (Revenue Cloud Billing) is the billing layer: billing schedules, invoices, credit notes, taxes, postings to GL accounts, payments and collections. RCB relies on the orders and assets managed in RCA.

You can deploy RCA without RCB (billing then stays in the ERP, fed by Salesforce orders), but RCB only makes sense with the orders produced by RCA. Exact licence names and their scope change regularly: always check with your Salesforce account team exactly what your contract covers.

What are the components of Revenue Cloud?

Product Catalog Management (PCM)

The product catalogue defines what you sell: simple products, bundles, options, attributes (size, term, service level…), classifications and selling models (one-time, subscription, usage). It is the foundation for everything else. A well-modelled catalogue sharply reduces the number of pricing and configuration rules you need to write later.

Salesforce Pricing

The pricing engine calculates the price of each line through pricing procedures that chain steps together: list price, volume discounts, negotiated discounts, attribute-based pricing, rounding, and so on. Price grids live in decision tables, which in most cases lets business teams maintain prices without development.

Product Configurator

The configurator guides sales reps towards a valid offer: mandatory options, incompatibilities, minimum quantities, dependent attributes. Configuration rules are expressed as constraints rather than coded one by one, which is easier to read for complex catalogues.

Transaction Management: quotes and orders

Transaction Management covers the quote, its approval, PDF generation and its conversion into an order. The same model handles new sales, amendments (adding licences mid-contract), renewals and cancellations.

Dynamic Revenue Orchestrator (DRO)

DRO (Dynamic Revenue Orchestrator) is Revenue Cloud's order orchestration engine: it breaks a commercial order down into technical lines and fulfilment plans (provisioning, account creation, field interventions, sending to the ERP…), with steps, dependencies and recovery points. It is often the piece that makes the difference between "a well-built quote" and "a genuinely automated end-to-end process".

Contracts, assets and renewals

Once the order is activated, Revenue Cloud creates or updates the customer's assets, with a history of quantities and prices over time. These assets are the basis for amendments, renewals and cancellations. The contract groups together the commitments and associated terms.

Usage Management

For consumption-based offers (API calls, volumes processed, active users…), usage management lets you define units, included entitlements and overages, rate consumption, and then pass it on to billing.

Billing (RCB)

RCB turns orders and usage into billing schedules, then into invoices and credit notes, applying tax, legal entity and accounting rules. We cover this layer in detail in our article Revenue Cloud Billing: invoicing, credit notes, VAT and ERP integration.

Which companies is Revenue Cloud a good fit for?

Revenue Cloud really pays off when the sales process goes beyond a simple catalogue quote:

• SaaS vendors: subscriptions, set-up fees, user tiers, mid-contract amendments, automatic renewals, and monthly, quarterly or annual billing at the customer's choice.
• Services and consulting firms: offers that mix recurring revenue and person-days, linked to the scheduling of interventions.
• Manufacturers: configurable products, technical options, after-sales, and a link with the ERP for production and logistics.
• Multi-entity companies: several companies, countries or currencies, with different VAT and accounting rules.

If you sell a few fixed-price products with simple quotes, Sales Cloud and its standard quotes are often enough: our Sales quickstart includes a simple-quotes option. Revenue Cloud becomes worthwhile when the complexity of your offer, customer lifecycle or billing starts to cost real money in re-keying, errors or delays.

Revenue Cloud project examples

A few projects delivered by Meir IT that show the range of use cases:

• Memoritz (RCA + RCB): quotes with complex products and renewals, after-sales and ERP-side processes managed through RCA's DRO, and billing that flows from actual orders.
• Coptis (RCA + RCB): quotes for SaaS solutions combining subscriptions and set-up fees, amendments and contractual rules, and billing at the frequency chosen by each customer.
• Nowbrains (RCA): complex products mixing recurring revenue and person-days, a renewal / order / contract cycle, and a link with Field Service for interventions.
• Transvalor (RCA): quotes that reflect the specifics of their offer, while keeping the existing link with Sage for accounting.

More customer stories are available in our case studies.

How does a Revenue Cloud implementation run?

1. Scoping: mapping the catalogue, price grids, discount and approval rules, the contract lifecycle and flows to the ERP. This is where you decide what belongs in RCA, in RCB or in the ERP.
2. Catalogue modelling: product types, attributes, bundles. We deliberately start with a small scope (around ten representative products) to validate the model.
3. Pricing and configuration: pricing procedures, decision tables, configuration rules.
4. Quotes and documents: quote PDF layout, approval process, conversion to order.
5. Lifecycle: orders, contracts, assets, amendments, renewals and, if needed, orchestration with DRO.
6. Billing (RCB) or ERP interface.
7. Data migration, testing, training and go-live, then iterations across the rest of the catalogue.

Revenue Cloud Advanced vs Salesforce CPQ: what are the differences?

Salesforce CPQ (formerly Steelbrick) and Salesforce Billing are managed packages installed in the org. Salesforce now steers new customers towards Revenue Cloud Advanced and is focusing its investment on the native platform. Here are the differences that matter in practice:

If you are already on Salesforce CPQ, read our dedicated guide: Migrating from Salesforce CPQ to Revenue Cloud Advanced.

Revenue Cloud and Agentforce

Bringing Revenue Cloud and Agentforce together is more than a name change. Because catalogue, prices, quotes and assets live in the standard Salesforce data model, an agent can work with them: drafting a quote from a request, explaining a price, retrieving a customer's assets before a renewal. The quality of these use cases depends directly on the quality of the catalogue and rules: a well-modelled Revenue Cloud is the best preparation for useful agents. See also our Agentforce use cases.

Common mistakes to avoid

• Copying the ERP catalogue as is: a sales catalogue is not a production bill of materials. It needs to be redesigned for selling.
• Coding every special case: most needs can be handled with attributes, decision tables and constraints. Code should remain the exception.
• Forgetting the lifecycle: a successful quote that produces inconsistent assets will make renewals and billing painful.
• Putting off the ERP question: decide early what Salesforce bills and what the ERP accounts for.