The revenue schedule's Total Revenue Amount field shows the amount of revenue that
Salesforce Billing can distribute across revenue transactions. The total revenue amount inherits
its value from one of several order product fields based on how you configure the Revenue Schedule
Amount field. You can find the Revenue Schedule Amount field on your revenue recognition
treatment. (Salesforce Billing Managed Package)
Required Editions
Available in: All Salesforce Billing editions
The Revenue Schedule Amount field has five picklist values. Each value corresponds to a field
on the order product. When your revenue recognition treatment evaluates an order product,
Salesforce Billing evaluates the corresponding order product field. It then sends the value of
that field the revenue schedule's Total Revenue Amount field.
When you configure your revenue recognition treatments, choose the Revenue Schedule Amount
value based on your revenue recognition needs for order products that fall under the treatment.
For example, if you want to recognize revenue based on bookings amounts, set your revenue
schedule amount to Bookings Amount. If your revenue recognition treatment evaluates an order
product with a bookings amount of $5000, the resulting revenue schedule has a total revenue
amount of $5000.
Let's review how each of these fields functions on the order product.
Bookings Amount
Represents the total amount that Salesforce Billing will invoice the order product for
across all its billing periods. Many organizations that recognize revenue from the order
product use this field for forecasting purposes.
On standard subscription order products, the bookings amount and total price are always the
same. However, an evergreen subscription has no predefined end date, so its total amount can
differ from the actual amount you bill for. To prevent inaccurate data, Salesforce Billing
always sets the bookings amount for an evergreen subscription order product to 0.
Revenue Allocation Amount
Represents the revenue that has been allocated from the revenue element to revenue
distributions. Different organizations have different ways of calculating revenue allocation,
so the field doesn't have any value on the order product by default. You can populate it
manually or use custom automation to provide a value based on your organization's requirements
for calculating revenue allocation amounts.
Revenue Expected Amount
Represents the revenue that finance operations users expect to come from the revenue source.
Different organizations have different ways of calculating expected revenue, so the field
doesn't have a default value. You can populate it manually or use custom automation to provide
a value based on your organization's requirements for calculating expected revenue
amounts.
Revenue Liability Amount
Represents the amount of revenue liable for delivery for payments made in advance of
delivering a service. Different organizations have different ways of calculating expected
revenue, so the field doesn't have a default value. You can populate it manually or use custom
automation to provide a value based on your organization's requirements for calculating revenue
allocation amounts.
Transaction Amount
Represents the total amount of the sales transaction, and inherits its value from the order
product's Total Price field. This field is useful for organizations that recognize revenue
based on the full amount of the sales transaction.
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.