Roll-Up Summary Fields and Salesforce Billing Automation

Example Your accounts have a custom roll-up summary field called Invoice Balances (1). It sums the Balance fields of all invoices on the account (2). For example, if your account has one invoice with a balance of $70 and one invoice with a balance of $100, your account would have an Invoice Balances value of $170.

When a customer makes a payment against an invoice, Salesforce Billing updates the invoice’s balance. The balance update triggers an update on the account’s Invoice Balances field. For example, if you make a $30 payment against your second invoice, the update causes the accounts Invoice Balances field to recalculate to $140. Whenever a rollup summary field updates, Salesforce triggers all automation that runs off updates on the same object. These types of automation include workflow rules, process builders, flows, validation rules, approval processes, and filtered lookups.

If you use an automated process to pay many invoices at the same time, such as a payment run, your account-level automation triggers would add up quickly. Let's say your account uses three custom update-based workflow rules and three custom update-based validation rules. If a payment run evaluates and pays 50 invoices, the resulting Invoice Balance updates trigger 300 instances of your custom account automation. Depending on the complexity of your automation, you can encounter performance impacts as Salesforce Billing resolves each automated process.

To reduce the likelihood of performance impacts, we recommend testing custom rollup summaries and custom automation in a sandbox. Note any significant impact to CPU, row lock errors, and instances of trigger recursion.