Recurring Billing
Pronunciation: ree-KUR-ing BIL-ing
Also known as: Automatic Billing, Repeat Billing
Definition
Recurring Billing is the repeated calculation and collection of charges according to an ongoing agreement or schedule. In billing and recurring commerce, it commonly covers customer agreement, billing cycle, price, usage, invoice creation, payment method, retries, proration, and cancellation. It is the billing process, while a subscription is the broader commercial relationship and entitlement being billed.
Overview
How it works and where it fits
Recurring Billing is the repeated calculation and collection of charges according to an ongoing agreement or schedule. The definition becomes actionable in billing and recurring commerce only when the relevant merchant, customer, product or plan, transaction context, system owner, and lifecycle state are explicit.
It is the billing process, while a subscription is the broader commercial relationship and entitlement being billed. Related operational concepts include Subscription, Subscription Renewal, and Merchant-Initiated Transaction (MIT), each of which should retain a separate definition and system owner.
It normally interacts with Subscription and Subscription Renewal, although the exact system boundaries vary by merchant and platform. Operationally, teams should preserve consent, calculate charges deterministically, handle changes and failures, prevent duplicate collections, and keep billing events linked to invoices and subscription states. Common failure modes include price-version drift, duplicate charges, incorrect proration, missing usage, late events, and invoices that cannot be reconstructed from source data.
In billing and recurring commerce, it commonly covers customer agreement, billing cycle, price, usage, invoice creation, payment method, retries, proration, and cancellation. The concept commonly includes customer agreement, billing cycle, price, usage, invoice creation, payment method, retries, proration, and cancellation.
Related glossary concepts
Example
A cloud tool bills each client monthly for usage. Each billing cycle generates a new commercial obligation and payment request. If the customer uses a self-custodied crypto wallet, recurring invoices do not mean the merchant can pull assets automatically: a signing or pre-authorized payment mechanism must exist separately.
Comparison
Contrast recurring billing with recurring collection. The first calculates and issues periodic charges; the second successfully collects them. Protect against duplicate invoice generation on job retries, support plan changes and store the applicable tax and exchange-rate rules per billing period. Never call payment fully automated merely because an invoice email is scheduled.
Key Takeaway
Periodic billing and automatic movement of crypto assets require different systems and authorizations.
Sources
- Billing — Stripe (2026-08-02)
- Usage-based billing — Stripe (2026-08-02)