Subscription, Usage and Hybrid Pricing in Revenue Cloud

November 17, 2026

How pricing procedures, decision tables and billing schedules fit together.

Pricing is the design decision


How you charge decides how you build everything else in Revenue Cloud. The catalog, quote, order, asset and invoice all carry the pricing model you choose.


Most companies no longer sell one way. A single deal might mix a platform subscription, usage overage, a one-time setup fee and a price that steps up each year. Revenue Cloud is built for that kind of hybrid deal, but only if the pricing model is designed on purpose rather than added one exception at a time.


The building blocks


Pricing in Revenue Cloud is declarative. Instead of CPQ price rules and custom scripts, you combine a few standard pieces.


  • Price books: Hold list prices, as in core Salesforce
  • Price adjustments: Apply discounts, tiers and other changes to list price
  • Context definitions: Tell the engine which quote, order or account data it can read
  • Pricing procedures: Run the pricing steps in order, from list price to net price
  • Decision tables: Look up values, such as a discount by region or segment, without code


On the back end, Usage Management and Rate Management handle consumption, and Revenue Cloud Billing turns all of it into billing schedules and invoices.


Source: Trailhead, Configure pricing for products


Five patterns and how to model them


  • One-time. Typical example: Setup fee, hardware, training day. What to get right: Keep it off the subscription so renewals don't repeat it.
  • Subscription. Typical example: Annual platform license. What to get right: Term length, billing frequency, and whether it renews automatically.
  • Usage. Typical example: API calls, transactions, seats used. What to get right: Where usage data comes from, how it's rated, billed in arrears.
  • Ramp. Typical example: Price or quantity steps up each year. What to get right: One deal with segments, so renewals and amendments see the whole ramp.
  • Hybrid. Typical example: Subscription with included usage and overage. What to get right: Which piece carries the commitment, and which piece bills on actuals.


Revenue Cloud Billing can bill monthly, quarterly or annually, in advance or in arrears, on milestones, or on usage. It also adjusts billing schedules for ramp deals and creates new schedules automatically when an order is amended or cancelled.


Sources: Trailhead, Get started with Billing; Trailhead, Navigate the full billing lifecycle


Design tips before you build


  • Start from the invoice. Ask Finance what the customer's invoice must show, then design backward to the quote.
  • Name the commitment. For every hybrid offer, decide whether the customer commits to a subscription, a minimum spend, or nothing at all.
  • Keep pricing data in decision tables. Regional prices and discount bands change often. Tables let your team update them without a release.
  • Test the day-two cases. Price a mid-term upgrade, a ramp renewal and a cancellation before go-live, not just the first quote.


Need help modeling a complex pricing structure? Book a free consultation with Amwintech.


Salesforce, Revenue Cloud, Agentforce and Trailhead are trademarks of Salesforce, Inc.


Amwintech's Blog

By looka_production_187211612 • November 17, 2026
What changes, a six-step migration plan, and the pitfalls we see most.
By looka_production_187211612 • November 17, 2026
How assets work, and a go-live checklist for day-two changes.
March 10, 2025
Revenue Cloud Billing product from Salesforce provides the following key capabilities: Accounting Foundations: Allows the configuration of legal entities, accounting periods, and general ledger accounts to establish the necessary accounting framework. Provides "accounting awareness" by integrating the billing system with core financial processes. Flexible Product Configuration: Supports a wide range of product types, including subscriptions, one-time purchases, professional services, and usage-based offerings. Enables granular control over billing policies, tax configurations, and usage rating for these different product types. Automated Billing Workflows: Tracks customer purchases through billing schedule groups and schedules. Enables automated invoice generation on a scheduled basis (daily, weekly, monthly). Allows invoices to be produced and emailed directly from within the Salesforce platform. Accounting Integration: Generates the necessary journal entries and general ledger postings based on the invoices processed. Ensures tight alignment between the billing operations and the financial reporting. Revenue Cloud Advanced Billing product provides a comprehensive, Salesforce-native solution for managing complex billing requirements, from establishing the accounting foundations to automating the end-to-end billing process and integrating with financial systems Observations of a demo: I. Set Up Legal Entities and Accounting Foundations A. Configured legal entities - Legal entities represented different operating companies (e.g., US, Japan, Canada) in the system. - Each legal entity was able to have its own set of accounting periods, such as 445 model or monthly, allowing for flexibility. B. Established general ledger accounts - The system allowed for the setup of general ledger accounts within Salesforce, similar to an ERP system. - This provided the necessary "accounting awareness" for the billing system by setting up accounts for receivables, deferred revenue, cash, and other financial elements. II. Flexible Product Configuration A. Subscription-based products - Billing policies, such as advanced billing, was defined for subscription products. - Tax policy integration was also configured, with support for Avalara and Vertex tax providers. B. One-time/equipment products - The system was able to handle one-time purchases or equipment-related charges. C. Professional services products - Milestone-based billing for professional services, allowed for percentage-based or fixed-amount charges at defined project milestones. D. Usage-based products - The system provided the ability to configure usage grants, rate cards, and other parameters to handle consumption-based billing. - Validity terms, refresh policies, and rollover policies could be defined for usage-based offerings. III. Order Management and Billing Workflows A. Order creation and decoration - Orders could originate from various sources, such as Revenue Cloud Advanced or Commerce. - Billing details, including payment terms and legal entity, were added to the orders. B. Billing schedule groups and schedules - The system tracked customer purchases and created the necessary billing data in the form of billing schedule groups and schedules. - Detailed billing information was made accessible from the asset record. C. Automated invoice generation - Billing batch schedulers were set up to allow for scheduled invoice runs on a daily, weekly, or monthly basis. - Invoices could be generated and emailed directly from the customer account within Salesforce. IV. Accounting Integration A. Journal entries and general ledger postings - The system generated the necessary dual-entry accounting entries based on the invoices, ensuring accurate financial tracking and reporting. B. Aligning billing operations with financial reporting