Skip to main content
Arrears billing flips the default: instead of charging at the start of a billing period, we charge at the end. The customer uses the service first and pays for what they used.

When to use arrears

  • Usage-based billing — you meter API calls, seats, or transactions during the month, then bill based on actual usage
  • Enterprise contracts — the customer has net-30 or net-60 payment terms
  • Trials converting to paid — bill after the first period so the customer experiences the value before the first charge
  • Credit-gated models — customer has a credit limit; you bill after confirming usage

How it works

With billing_mode: "advance" (default), the invoice is created at the start of the period:
With billing_mode: "arrears":
The invoice and payment logic are identical — it’s only the timing that differs.

Setting up arrears billing

Add billing_mode: "arrears" when creating the subscription:
Response
next_bill_at is July 1st — that’s when the June invoice is created and the July period begins simultaneously.
The Postpaid preset applies arrears billing along with a longer grace period (14 days) and more lenient dunning settings. If you’re doing enterprise billing, applying the Postpaid preset first is quicker than configuring each knob. See Presets.