Learn how Billing evaluates suspensions when invoice runs and the Invoice Creation API use a target date or billing period count.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with the Revenue Cloud Advanced license or the Revenue Cloud Billing license |
Deferred Charges
Suspending billing defers charges for the suspension period—it doesn’t waive them. Charges for the suspended period are billed when billing resumes or when a later invoice run uses a target date on or after the resumption date.
Target Date and Suspensions
When a run uses a target date, Billing evaluates billing suspensions as of that date, not the run date. Backdating suspensions isn’t required to prevent charges during the suspension period. Invoicing depends on where the target date falls relative to the suspension window.
- Target date before the suspension starts: Invoicing proceeds as normal. The suspension has no effect yet.
- Target date falls within the suspension window: Billing doesn’t create billing period items or generate an invoice for the suspended billing periods, even if the run date is before the suspension starts. If a billing schedule falls partially in the suspension window, Billing creates billing period items and invoices for the periods before the suspension start date. Invoice run responses can report that the account or billing schedule group is suspended, if no billing periods fall before the suspension window.
- Target date falls on or after the resumption date: The invoice run bills all periods up through the target date, including previously deferred charges from the suspension period, in the same run. The suspension has no effect on those invoices because the target date is on or after the resumption date.
Because the target date falls in the suspension window, Billing creates billing period items only for periods that end before the suspension starts—through August 15—and generates an invoice for those charges. The billing period item for the period that ends September 15 isn’t created because that period overlaps the suspension window.
Billing for September charges occurs when a later invoice run uses a target date on or after September 30, or when you cancel the suspension and run invoicing again.
Billing Period Count and Suspensions
When an invoice run uses billing period count instead of a target date, Billing still evaluates suspension for each schedule separately. A suspended schedule isn’t invoiced for any period that falls in its suspension window.
What changes is which periods the run retrieves. A target date selects schedules up to a calendar date. Billing period count selects a fixed number of periods per schedule, so the period range can differ for schedules with different next billing dates.
Multiple Suspensions
If more than one suspension applies to the same account or billing schedule group, Billing uses the earliest suspension start date.