Salesforce Known Issues

Known Issues · Salesforce Billing

Contract generation for Amended Order fails if Override Next Billing Date ONBD is populated for Original Order Product

Salesforce Billing

Set Override Next Billing Date (ONBD) is set on an Order Product (OP), contract the Order and do not invoice it. Then amend the OP to cancel it. When contracting the cancellation Order an error is thrown: Error:Apex trigger SBQQ.OrderTrigger caused an unexpected exception, contact your administrator:...

In Review ·Reported By 3 ·Updated 3 days ago

Payment Allocations - with multiple lines to allocate against a Payment the Amounts are not correct on all lines

Salesforce Billing

Payment Allocations do not allocate successfully to Invoice Lines when multiple Invoice Lines exist related to one Invoice record.

In Review ·Reported By 5 ·Updated 4 days ago

Invoices are fully paid, but the Payment Status field displays Partially Paid.

Salesforce Billing

Invoices that are fully paid will sometimes show the Payment Status field = 'Partially Paid'.

In Review ·Reported By 13 ·Updated 6 days ago

Cancel and Rebill fails for invoices with more than 80 lines

Salesforce Billing

Invoices with more than 80 Invoice Lines can not use the Cancel and Rebill function

In Review ·Reported By 1 ·Updated 6 days ago

Next Billing Date is null when ordering One-Time Products with no subscription term or end date.

Salesforce Billing

When creating an order for a one-time product, there should be no need for a subscription term or end date. If you create a quote for just one time products, or one time products and evergreen subscriptions (neither of which require a term or end date) the one time product will not populate Next Billing...

Fixed in version Billing 220.3 ·Reported By 11 ·Updated 11 days ago

Large batches of invoices may not be able to be posted using built in methods

Salesforce Billing

When there are several thousand or more invoices, the Automatically Post Invoices function on the Invoice Scheduler or the Post All Invoices button on Invoice Run may fail to post all invoices.

Fixed in version Billing 220 ·Reported By 4 ·Updated 11 days ago

Pending Billing Amount (without tax) is incorrect for Amendments when Billing Day of Month changes

Salesforce Billing

On amendments that eventually cancel an order product, there appears to be a remainder in the Pending Billing Amount (without tax) field on the first amendment order. This appears to depend on Billing Day of Month (BDOM) changing over the amendments. BDOM changes when package setting for CPQ is Default...

In Review ·Reported By 2 ·Updated 11 days ago

Contracting cancellation order for order product with invoice plan hitting next billing date validation, failing

Salesforce Billing

Email error received when contracting the cancellation order: Error type: System.DmlException Reason for error: Update failed. First exception on row 0 with id xxxxxxxxxxxxxxxx; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, Can't change the billing date for order products whose billing frequency...

Fixed in version Salesforce Billing 220 ·Reported By 5 ·Updated 12 days ago

When Price Tier Lower Bound is Zero, Prerated Usage record throws error

Salesforce Billing

For Customers using Usage products in the legacy manner (no consumption schedule) there is a workaround to be able to enter fractional amounts for the first usage in a usage summary. That workaround is to either manually, or via discount schedule, change the Lower Bound on the Price Tier for the Price...

In Review ·Reported By 0 ·Updated 18 days ago

Payment Center and other Billing VF pages do not accept comma as decimal separator in Locales that use it that way

Salesforce Billing

For many Locales, the decimal separator is a comma instead of a period. for example, in the US 35 + (1 / 4) = 35.25. In other locales, this would be represented as 35,25. For many of the Salesforce Billing VisualForce pages, like Payment allocation and Credit Note allocation, Payment Center, the comma...

In Review ·Reported By 1 ·Updated 26 days ago

1 to 10 of 70 | 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.