You can override the target date and amount on your billing transactions. This feature
is useful in milestone billing if a sales rep renegotiated terms and changes an invoicing setup
that you already created. (Salesforce Billing Managed Package)
Required Editions
Available in: Salesforce Billing Spring ’18 and later.
Example Your sales rep sold an enterprise IT performance management package on 06/02/18 for
$30,000, with an initial billing date of 07/01/18. Your rep and the customer agreed to invoicing
$10,000 every 45 days, so you made an invoice plan with invoice plan lines that reflected the
division. When you activated the order product, your invoice plan created a billing schedule with
3 billing transactions. However, on 06/09/18, your sales rep renegotiated to the following terms.
Milestone 1: 60% on 07/15/18
Milestone 2: 40% upon UAT completion
Use override fields on your billing transactions to reflect the changes. Field values that
the related invoice plan line originally created are represented with italics.
Billing Transaction 1
Status: Pending
Billing Target Date: 07/01/18
Override Billing Target Date: 07/15/18
Amount: 10000
Override Amount: 18000
Since you don’t know when your customer will hit their Milestone 2 goal, find your second
and third billing transactions and set their Override Status field to Cancelled. This ensures you
won’t accidentally invoice based on the original terms. Your customer meets Milestone 2 on
09/30/18, so you can add the following billing transaction to your billing schedule.
Billing Transaction 2
Status: Pending
Billing Target Date: 09/30/18
Amount: 12000
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.