Salesforce Known Issues
Trailblazer Community

Known Issues · Salesforce Billing

Invoice Payment Status shows "Partially Paid" for fully paid invoices

Salesforce Billing

For invoices with payments fully allocated, the Payment Status shows up as Partially Paid. The issue can be intermittently observed. In the developer console, checking the field values related to the formula for Payment Status shows decimal places even though it is expected that the fields only holds...

In Review ·Reported By 6 ·Updated Yesterday

Proration Type custom setting changes when user language is changed

Salesforce Billing

When changing a user's language, the proration setting for Salesforce Billing may change.

In Review ·Reported By 1 ·Updated 2 days ago

Unit Price on the Invoice Line and Usage Summary is incorrect when using prerated usage

Salesforce Billing

The Unit Price on the Invoice Line for a usage based products pulls its value from the Unit Price on the Usage Summary. If the value on the Usage Summary is incorrect, the value on the Invoice Line is also incorrect. This happens when there is prerated usage on the usage summary. The expectation...

In Review ·Reported By 1 ·Updated 2 days ago

Invoice plans rounding logic can cause overbilling when third decimal place is non zero

Salesforce Billing

When using Invoice Plans, Salesforce Billing will over-bill in the event the Order Product amount is divided in such a way that the Billing Transactions have amounts that calculate with a non zero third decimal place. The easiest way to see this is with two transcations of x.xx5.

In Review ·Reported By 0 ·Updated 2 days ago

Cancel and Rebill pulls Tax and Billing Rules from Product rather than Invoice Line/Order Product

Salesforce Billing

A credit note created by Cancel and Rebill or Credit pulls its Tax Rule and Billing Rule from the Product (Product2) instead of from the invoice line. Credit note lines must reflect what they are crediting - the tax rate used on the credit note must be the same as the one in force at the time of sup...

In Review ·Reported By 1 ·Updated 4 days ago

Mixing prerated and regular usage in the same batch causes math error on Usage Summary resulting in possible invoice error

Salesforce Billing

Loading Pre-Rated usage and standard usage in the same batch causes the Usage Summary to miscalculate the Unbilled Subtotal leading to an erroneous invoice line. Note that the Invoice Line Subtotal comes from the Unbilled Subtotal of the Usage Summary.

In Review ·Reported By 1 ·Updated 4 days ago

Credit Notes are created in corporate currency instead of Invoice currency when using Process Builder to trigger apex class creditnegativelines

Salesforce Billing

While generating Credit Note from Negative Invoice Line using Process Builder, currency ISO Code is set to corporate currency / user default currency when Invoice/Order/Quote/Opportunity is in different currency.

In Review ·Reported By 1 ·Updated 4 days ago

Apex CPU Timeout when crediting an Invoice that has more than 600 Invoice Lines

Salesforce Billing

For an environment without any customization, Credit action in the Invoice can work up to about 600 invoice lines. Remember that the number is subjective and can be much lower if there are customization present within the environment.

In Review ·Reported By 0 ·Updated 4 days ago

Attempt to de-reference null on Revenue Transaction Creation for Order Products with different Finance Books

Salesforce Billing

Error seen in the Error Log during Revenue Transaction creation: Attempt to de-reference a null object-18-Class.blng.RevenueRecognitionCalculator.calculate: line 18, column 1 Class.blng.RevenueScheduleService.createRevenueTransactions: line 1606, column 1 Class.blng.QueueableRevenueTransaction.execute:...

In Review ·Reported By 0 ·Updated 4 days ago

Error on Contracting an Amendment Order with Usage Product and Existing Usages

Salesforce CPQ (Configure-Price-Quote) , Salesforce Billing

Contracting an amendment order with usage product and usages returns error: System.DmlException: Update failed. First exception on row 0 with id a2h7X0000007UbaQAE; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Can't set Prerated Amount on usage summaries with a order item consumption schedule.:...

In Review ·Reported By 11 ·Updated 5 days ago

1 to 10 of 107 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.