Usage below a SaaS billing threshold is not open accounts receivable merely because it can be measured or priced. Keep accrued usage in an upstream billing lane until the configured threshold or billing-period event creates and finalizes an invoice. After issuance, move only the supported invoice balance into AR and assign collection timing from the invoice's payment method, due date, and current evidence.

A threshold controls invoicing, not cash

Stripe documents billing thresholds that can trigger an invoice when accrued subscription usage or a monetary amount reaches a configured level. It also notes that an invoice can otherwise wait until the end of the billing period, and that previously billed usage can affect later threshold invoices under tiered pricing.

For a small SaaS finance team, three amounts can coexist: metered usage not yet invoiced, a threshold-triggered invoice already issued, and remaining period activity that may appear on a later invoice. Adding all three to receivables would duplicate part of the contract value and mix billing operations with collections.

Use the usage-charges boundary guide for the general unbilled-versus-AR distinction. If invoice finalization is delayed, the draft-invoice guide applies until the invoice is open.

Build a threshold-to-invoice bridge

For each subscription or enterprise contract, preserve:

  • customer, subscription, meter, product, and currency;
  • billing-period start and end;
  • usage or monetary threshold and the time it was configured;
  • measured usage and valuation through the evidence cutoff;
  • threshold event timestamp, if reached;
  • invoice identifier, issue or finalization time, and open amount;
  • previously billed usage or credits included in the calculation;
  • unbilled usage remaining after the invoice;
  • collection method, payment status, due date, and owner; and
  • next billing and forecast review triggers.

Reconcile usage across periods so the same units cannot support two invoices. A threshold alert without an invoice remains operational evidence. A generated draft remains upstream. A finalized open invoice enters the receivable population, while any new usage after its cutoff remains unbilled.

Do not estimate threshold crossing from incomplete usage and call the result AR. If a management cash view needs an outlook for future billing, keep it in a clearly separate scenario outside the invoice-level collections range. The pending-invoice-items comparison provides a related control for billing items not yet attached to an invoice.

Decision rule

Treat the threshold as an invoice trigger, not a receivable or receipt. Move value into AR only from the supported issued invoice, subtract previously billed usage once, and keep later usage in a separate billing queue until its own invoice event occurs.

AR Pulse analyzes an authorized QuickBooks receivables export and produces a ranked cash-action list and four-week range. It does not meter usage, create Stripe invoices, or guarantee collections. Small SaaS finance teams can apply for AR Pulse.