Sometimes, your payment run can receive a successful gateway response and create a
payment, but fail to allocate the payment to your invoice. This can happen due to user-defined
validation rules or database errors. To finish the allocation process, manually create an
allocation record and assign it to your invoice. (Salesforce Billing Managed Package)
Required Editions
Available in: Salesforce Billing Winter ’19 and later
Failed Allocations
Failed allocations can happen in response to
user-created validations or failed database inserts. After the failure, the payment run
updates status fields on the following objects.
Invoice
Last Payment Run Processing Message: Payment Allocation Failed
In some cases, the payment run updates the payment transaction with an error log
showing details about why the allocation failed. However, if the payment run itself fails
before making the allocation (for example, due to a lost server connection), the run is
unable to make an error log on the transaction.
We recommend creating a workflow rule
or process to provide an alert when a transaction changes its payment creation status to
Payment Allocation Failed. If the payment run produced as an error log, you can also review
it to find the transaction and then the payment where the allocation failed.
Once
you’ve identified the payment, manually create an allocation from that payment to your
invoice. Manual allocation is important as future payment runs will attempt to pick up that
invoice if its related payment remains unallocated.
Duplicate Allocations
If multiple browser tabs to allocate or unallocate payments are open, refresh the browser before
you click Allocate or Unallocate to avoid
allocating or unallocating the same payment twice.
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.