Known Issues · Salesforce Billing

New!Payeezy Gateway Integration: Payments can be processed in the gateway without a corresponding record in Salesforce if the card number is null

Salesforce Billing

The only fields that are required by Payeezy to create payments are: -Name on Card -Card Type -Card Expiration Month -Card Expiration Year -Payment Gateway Token Entering only these fields on the Payment Method record will cause an error in the Payment Center or will cause a Payment Scheduler...

In Review ·Reported By 1 ·Updated Today

Balance Snapshot Scheduler will error, not complete when Account 'Name' is longer than 80 characters

Salesforce Billing

When a Balance Snapshot Scheduler runs and finds an account with a name longer than 80 characters, the job will throw an error. This is due to the fact that 'Name' fields on custom objects are limited to 80 characters per Salesforce.

In Review ·Reported By 0 ·Updated Today

When generating a large number of Orders at the same time, users experience Record Lock errors on the Billing Rule record

Salesforce Billing

When organizations are generating a large number of Orders at the same time, users experience Record Lock errors on the Billing Rule record. This prevents order from being created.

Fixed in version Billing 212.13.12 ·Reported By 4 ·Updated 5 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.

In Review ·Reported By 4 ·Updated 7 days ago

Credit button on invoices should also create a committed transactions to Avalara

Salesforce Billing

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 13 days ago

Cannot activate Order with Order Products priced at 0.00 if Bill Through Override or Override Next Billing Date are specified

Salesforce Billing

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.

In Review ·Reported By 5 ·Updated 28 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 7 ·Updated 2018-08-15

Invoice Plan tab is missing

Salesforce Billing

Salesforce Billing 212 introduces Dynamic Invoice Plans There is no tab provided by the managed package to set this up

In Review ·Reported By 1 ·Updated 2018-08-15

Entering or Uploading Pre-Rated Usage records fails without Usage Summary or Order Product fields

Salesforce Billing

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.

In Review ·Reported By 1 ·Updated 2018-07-17

Salesforce Billing Configuration Page Settings do not display in Orgs on Salesforce Summer '18

Salesforce Billing

The Salesforce update for sandboxes to test the Summer '18 release causes the Billing configuration page to not display fully.

Fixed in version Billing-212.13.6 ·Reported By 2 ·Updated 2018-07-13

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