How to Set Up and Use Usage Management in Salesforce Revenue Cloud

Key Objects and Architecture

Before getting started, familiarize yourself with the following core components:

Part 1: Setup Rate Management Entities

  — Unit of Measure Setup

1. Deploy the UoM Type picklist values. Note: This picklist arrives empty by default and requires manual deployment.
2. Establish measurement classes (e.g., Data, Time, Currency).

 — Create Usage Resources

1. Create UsageResource records for each metered dimension you need to track (e.g., Compute Time, Data Storage, AI Tokens).

 — Build the Anchor Product

1. Create a Product2 record and set the UsageModelType to "Anchor."
2. Assign the appropriate selling models to the product.

 — Link Resources and Define Grants

1. Create ProductUsageResource (PUR) records to connect each resource to the product.
2. Create ProductUsageGrant (PUG) records to define:
   • Included grant quantities
   • Whether overage usage is chargeable

— Configure Rate Cards

1. Create a RateCard record.
2. Add RateCardEntry records that define the conversion: usage units → tokens → dollars.
3. Ensure the PriceBookRateCard uses "PriceBookId" 

Phase 6 — Configure Policies and Binding

1. Configure the UsageResourcePolicy (API name: UsageResourceBillingPolicy) to define aggregation frequency and overage rules.
2. Create the UsagePrdGrantBindingPolicy binding declaration.
3. Refresh decision tables for rate card resolution, tier adjustments, and asset/binding lookups. Skipping this step will cause blank rates to appear in the UI even when data is correctly configured.

Important: Activation must follow this strict order — UoM Classes → UoMs → UsageResources (Token-category first) → PURs (Token first) → PUGs → RateCardEntry records. Activating out of sequence will trigger validation errors.

Part 2: Quote-to-Liable Summary

— Quote and Order

• The sales rep adds the anchor product to the quote.
• Upon ordering, Revenue Cloud automatically creates:
  • An Asset record
  • A UsageEntitlementAccount
  • Grant-tracking bucket records

— Ingestion (Creation of  Transaction Journals)

• Customer workload activity generates TransactionJournal records with a status of "Pending."
• Ensure users have the "View All Records" permission to access Transaction Journals.

— Aggregation (Creation of Usage Summaries)

• Run the "Summarize" operation to aggregate all pending TransactionJournal records into UsageSummary records.

— Rating (Creation of Ratable Summaries)

• Run the "Calculate Rate" operation.
• This executes the rating procedure, produces UsageRatableSummary records with pricing, and updates provisional balances.

— Liable Summary

Run the Liable Summary DPE to get the rates reflected.

— T+3 Drawdown (3-Day Waiting Period)

• A deliberate 3-day waiting period is applied before committed balances are updated.
• This delay accommodates late-arriving usage data.