Getting Amendments and Renewals Right in Revenue Cloud

November 17, 2026

How assets work, and a go-live checklist for day-two changes.

Day two is where it breaks


The first quote is rarely the problem. Trouble starts when a customer adds seats mid-term, upgrades a plan, renews early or cancels part of a deal.


In Salesforce CPQ, those changes ran through contracts and subscription records, and complex ones often needed workarounds. Revenue Cloud handles them through assets instead. If your assets are set up well, amendments and renewals mostly take care of themselves. If they aren't, every change becomes a manual fix.


How assets work


In Revenue Cloud, anything you sell can be tracked as an asset: a product, a service, a subscription or a bundle. Assets are created when an order is activated, and they become the record every later change starts from.


Two related records tell the asset's story:


  • Asset actions record every change made to the asset on a specific date, such as an amendment or renewal.
  • Asset state periods cover the time spans when the asset's quantity, amount and monthly recurring revenue (MRR) stayed the same.


Together they give a dated history of what the customer had, when, and at what price. That history is what amendments, renewals and revenue reporting read from.


Source: Trailhead, Provide post-sales support


The three day-two changes


  • Amendment. What the customer wants: Add users, upgrade a service, change a start date. What to plan for: Proration, co-terming with the existing end date, and how discounts carry over.
  • Renewal. What the customer wants: Extend before the term ends. What to plan for: When renewal opportunities are created, price uplifts, and early renewals.
  • Cancellation. What the customer wants: End all or part of a deal. What to plan for: Effective dates, credits, and what happens to bundled items.


Each change adds a new asset action and new state periods, so the asset keeps a full history. With Revenue Cloud Billing, schedules are updated automatically when a subscription is amended, cancelled or renewed.


One common surprise: a renewal opportunity won't appear until the asset's end date is inside your renewal window. If renewals seem to be missing, check the timing and the renewal flow settings before assuming something is broken.


Sources: Trailhead, Manage customer asset amendments; Trailhead, Navigate the full billing lifecycle


Go-live checklist for day-two changes


  •  Migrated contracts land as assets with correct start dates, end dates and MRR
  • A mid-term add-on co-terms to the existing end date and prorates correctly
  • An upgrade swaps the old product for the new one without double billing
  • A ramp deal renews at the right price for the next term
  • Renewal opportunities are created on the timeline Sales expects
  • Partial cancellations create the right credits
  • ARR and MRR reports match Finance's numbers after each change


Amwintech designs and tests asset, amendment and renewal processes for Revenue Cloud and Salesforce CPQ. Book a free consultation.


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 pricing procedures, decision tables and billing schedules fit together.
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