R
Glossary
Recurring Billing
Recurring billing is a payment model where a business automatically charges a customer on a fixed schedule for a plan or subscription, using payment details the customer authorized once. Each period the system creates the invoice, charges the stored payment method, records the result, and retries or renews.
Key Takeaways
Recurring billing runs on a stored authorization: the customer signs up and gives permission once, and offline card charges rest on the customer's agreement to your terms.
A typical cycle runs schedule, invoice, charge, record, and renew, and retries and reconciliation are part of the mechanism.
A $49 plan anchored on January 31 bills on February 28, March 31, and April 30, so period lengths change while the flat fee doesn't.
The schedule stays fixed while the amount can change, because a bill with varying balances based on usage still counts as recurring billing.
How does one cycle of recurring billing run?
A typical cycle runs schedule, invoice, charge, record, and renew in order, and none of the steps needs the customer present:
Schedule. The anchor date arrives, the billing cycle closes, and the next billing period opens.
Invoice. The system totals the new period's fee plus anything accrued in the old one.
Charge. It collects against the stored payment method with no customer present.
Record. It stores the result and applies the payment.
Renew. Success continues the subscription, failure hands off to payment retry and dunning management.
The table runs that loop for a $49 plan anchored on January 31, 2027, with usage at $0.002 per API call billed in arrears. When the anchor day doesn't exist in a shorter month, one common rule bills on the last day of the month closest to the anchor date: February 28, March 31, then April 30.
Charge date | Base fee (advance) | Usage billed (arrears) | Invoice total |
|---|---|---|---|
Jan 31 | $49.00 | none yet | $49.00 |
Feb 28 | $49.00 | 12,000 calls x $0.002 = $24.00 | $73.00 |
Mar 31 | $49.00 | 20,500 calls x $0.002 = $41.00 | $90.00 |
Apr 30 | $49.00 | 9,000 calls x $0.002 = $18.00 | $67.00 |
The four invoices add up to $279.00, and the base fee stays $49.00 while periods run 28, 31, and 30 days. Billing in advance and billing in arrears explain why the two lines land on different periods.
What does the customer agree to before the first charge?
The customer agrees to be charged later without being asked again, and the seller records that agreement. Offline card charges rest on that agreement, and the terms should include:
The customer's agreement to your initiating a payment or a series of payments for specified transactions.
The anticipated timing and frequency, such as scheduled installments, subscription payments, or unscheduled top-ups.
How you determine the payment amount.
Your cancellation policy for any subscription services.
Keep a record of each customer's agreement to your terms. For a metered plan, the amount item explains how usage sets the amount. See auto-renewal for renewal terms.
What changes when the amount isn't fixed ahead of time?
The schedule stays fixed but the invoice total doesn't, so the loop gains a metering step before the invoice.
Model | Amount known before the cycle? | What the loop adds |
|---|---|---|
Flat or per-seat fee | Yes | Nothing, the amount is fixed |
Usage-based | No | Metering, then rating at close |
Hybrid (base fee plus usage) | Partly | A base fee plus metered usage overages |
A bill with varying balances based on usage still counts as recurring billing. Metered billing covers measurement, and subscription pricing models compares structures.
How is recurring billing different from subscription billing?
Some sources say all subscriptions involve recurring billing but not all recurring billing is a subscription, and others separate the charging mechanism from the wider subscription arrangement. The definitions fall into these readings:
Reading | Recurring billing | Subscription billing |
|---|---|---|
Payments view | Regular payments for ongoing services, including retainers and usage-based bills | The narrower case, which can let customers shift between tiers between payments |
Charging-mechanism view | Charging at predefined intervals, with a scope of the payment mechanism only | Full lifecycle management, including proration, upgrades, downgrades, and pauses |
Operations view | The operational mechanism: automated charging, retries, and reconciliation | The customer-facing arrangement |
Subscription lifecycle covers plan changes.
Related terms
Each linked page picks up a step of the loop that this entry only names.
Billing cycle explains how the anchor date sets each period.
Billing period covers the dated span each charge pays for.
Billing frequency compares weekly, monthly, and annual cadence.
Auto-renewal covers notice laws before a renewal charge.
Payment retry covers what happens when step three fails.
Metered billing covers variable amounts on a fixed schedule.
FAQ
Can a customer stop a recurring charge?
Yes, though the mechanism differs for SEPA debits and cards. A SEPA customer can request cancellation of a mandate at any time through the party that set it up or through their bank, and canceling a mandate invalidates any future debit requests on it. For card charges, state your cancellation policy in the terms the customer agrees to.
What happens when a recurring charge fails?
The system retries the charge and communicates with the customer. Automated charging, retries, and reconciliation are all part of the mechanism. Payment retry covers the retry schedule, and failed payment recovery covers the full stack.
Does recurring billing always need a card on file?
No. Recurring collection works on cards and on SEPA Direct Debit mandates. It requires the customer to provide their information and permission, and the stored credential can be a card or a bank debit mandate.
Back to glossary
