A usage summary is an object that groups usage records for an order product. As you load
usage into your org, Salesforce Billing associates the usage records with the summary based on
matching IDs. When you invoice your usage order product, Salesforce Billing prices the resulting
invoice line based on the sum of usage subtotals across your entire usage summary. (Salesforce Billing Managed Package)
Required Editions
Available in: Salesforce Billing Spring ’18 and later
Salesforce Billing creates a usage summary when you order a product with a charge type of
Usage. In this case, Salesforce Billing generates usage summaries for your usage order products
based on the order product’s billing day of month, billing frequency, start date, and end date. A
usage order product billed monthly with a start date of 01/01/2018 and end date of 12/31/2018
would have 12 usage summaries, each the length of each month in the year.
The usage summary's Usage related list shows all your associated usage records. Remember,
Salesforce Billing evaluates assigning usage to a summary only if they both records have the same
Matching ID field values. We recommend using a process builder to quickly provide matching IDs to
large groups of usage summaries at once.
Note You can use any value for the matching ID. However, if a usage record matches the matching
IDs and start/end dates of multiple usage summaries, Salesforce Billing assigns it to one of the
usage summaries at random. We recommend using the order product's record ID or number as your
matching ID. That way, Salesforce Billing will always match the IDs between the usage summary
and usage. If you use a more generic number such as a desk number or org ID, Salesforce Billing
could assign your usage to a usage summary that's not related to the correct order
product.
Usage summaries inherit their start and end dates from the order products that created them.
After Salesforce Billing sees equal matching IDs between a usage record and a summary, it checks
whether the usage's End Date Time field falls within the summary's start date and end date. If it
does, the usage record appears in the summary's Usage related list.
You can assign usage to a usage summary between (and including) the summary's start date and
end date. After the end date, the summary won't accept new usage, even if the usage and summary
have equal matching IDs.
The usage summary's quantity field shows the total quantity of all related usage, and the
unbilled subtotal shows the subtotal of all related usage before billing.
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.