Understand the requirements and limitations of the rollback feature to reverse the most
recent transaction on an asset. Familiarizing yourself with these rules ensures data integrity and
helps you determine when a transaction is eligible for reversal.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions of
Revenue Cloud where Transaction Management is enabled
Rollback Eligibility and Usage
Review these critical constraints and
behaviors before initiating a rollback.
Timing Restrictions: You only roll back future-dated transactions that haven’t started. If
the start date occurred in the past or occurs today, the system prohibits rolling back the last
transaction.
Bundle Constraints: Rollback rules apply to child products within a bundle. If renewal or
amendment of any child product has started, you can’t roll back the entire bundle transaction.
Transaction Scope: The system doesn’t support the partial rollback of a transaction.
Legacy Data: You can’t roll back assets created before the Salesforce Winter '26 release.
Sequence of Actions: The rollback action always applies to the most recent or last
transaction. You can perform multiple rollbacks to undo transactions sequentially. After you
roll back the last transaction, you can then roll back the next most recent transaction.
Action Restrictions: You can’t roll back a rollback transaction.
Unsupported Transaction Types: The system doesn’t support the rollback of initial sales,
cancellations, or transfer transactions.
Feature Incompatibility: The system doesn’t support rollbacks for asset transactions
involving ramps, usage-based products, or Dynamic Revenue Orchestration features.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.