Known Issues · Salesforce Billing
The "Bill To Contact" and "Payment Methods" are not populated on an Invoice upon creation.
In Review ·Reported By 1 ·Updated 3 days ago
One you put a value in the Usage Floor Quantity field on the Order Product (OP) you can not delete it or change it due to a validation. This happens for unactivated orders.
In Review ·Reported By 12 ·Updated 14 days ago
1. On Order Product (OP), when End Date = Start Date the first invoice is correct. After posting that invoice, another invoice line can be generated for 0.00. This will continue to happen every time that OP meets the criteria to be invoiced. 2 When the OP has no End Date, it will never generate an...
Fixed in version Salesforce Billing 216.8 ·Reported By 1 ·Updated 19 days ago
The Credit button on the Invoice layout creates a posted Credit Note in Salesforce, but does not create a committed transaction in Avalara to offset the committed invoice document. A credit note needs to create an offsetting tax amount in Avalara. It should work like invoices: draft = uncommitted, posted...
In Review ·Reported By 10 ·Updated 2018-10-17
Entering a usage with quantity of >0 and <1.0 will throw an error if it is the first usage in a specific usage summary. If the user first enters a usage >= 1.0, and then enters one that is < 1.0 it works fine.
Fixed in version Salesforce Billing 212.13.8 ·Reported By 6 ·Updated 2018-10-17
When an Order is created with one or more Order Products (OP) that have a price of 0.00, and that OP has either the Override Next Billing Date and/or Bill Through Date Override fields populated, the Order cannot be activated.
Fixed in version Salesforce Billing 214.6.1 ·Reported By 5 ·Updated 2018-10-17
When attempting to load pre-rated usage (manually or via data loader), an extra value (either Usage Summary lookup, or Order product Look up) is required that is not required when loading usage.
Fixed in version Salesforce Billing 214.5 ·Reported By 1 ·Updated 2018-10-17
When using the Standard Tax integration, Tax amount is calculated to 3 decimal places on the OP. It is calculated to 2 or 3 decimal places on Invoice Lines depending on type of product. This can result in a mismatch in the total tax rollup on the Order vs. Invoice.
Fixed in version Salesforce Billing 212.13.9 ·Reported By 1 ·Updated 2018-10-17
Salesforce Billing 212 introduces Dynamic Invoice Plans https://help.salesforce.com/articleView?id=blng_dynamic_invoicing.htm&type=5 There is no tab provided by the managed package to set this up
Fixed in version Salesforce Billing 216 ·Reported By 1 ·Updated 2018-10-17
Upgrades to Billing 212.13.8 result in an Attempt to de-reference a null object error on invoices for existing orders when running an invoice scheduler. New Orders work as expected Usage Orders work as expected Existing Orders for non-usage products will throw errors
Fixed in version Salesforce Billing 212.13.10 ·Reported By 0 ·Updated 2018-10-17
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.