Usage-based plans and reporting usage

Historical retrospective - March 2026
This article was written afterwards and describes the feature as it worked during the stated period.

A usage plan calculates price from one or more parameters reported for a customer. The plan has a unit and pricing rule; a fixed plan amount is not a promise of the final period price.

Create the plan

Create a plan with usage-based pricing, attach the parameter, and enter its unit and pricing rule. Review the interval and currency before making the plan visible in checkout. Then create subscriptions from that plan.

Report and follow usage

Report usage through the current UI or API flow before the period is locked for invoicing. The value must match the parameter’s unit and reporting date. Open the customer’s usage view to confirm that the entry was received and which period it belongs to. Only after the data is accepted and the period price is calculated can the expected invoice line show the result.

A missing report does not automatically mean one particular price. The expected amount may be absent or follow the documented plan fallback; check its status before invoicing. Usage already invoiced is an existing financial record and cannot be freely edited as a new entry. A visible usage entry and a completed invoice are separate things.

What happens without a report? The expected price may be missing or follow the documented fallback; check the status before invoicing.

See the plans and pricing guide (Markdown file, AI agent-friendly) and checkout guide (Markdown file, AI agent-friendly).