Subscription billing is the model where customers pay on a recurring schedule for ongoing access to a product. Rather than buying software outright, the customer pays each period and retains access as long as they keep paying. It is the dominant SaaS revenue model because it produces predictable revenue and aligns the vendor's incentive with keeping customers successful.
The building blocks
Subscription billing has three core components that work together: plans, features, and subscriptions.
A plan is the pricing template. It defines the base price, the billing interval (monthly, quarterly, yearly), and the set of features included. Think of it as the product you put on your pricing page. "Starter at $29/month" or "Pro at $99/month" are plans.
Features are the individual capabilities within a plan. Each feature has a type that determines how it is priced and consumed.
- Boolean features are on/off toggles. "Custom branding: included" or "Priority support: included." They have no variable cost and are bundled into the plan's base price.
- Metered features track usage against an included quota and charge overage at the end of the billing cycle. A plan might include 10,000 API calls, with each additional call costing $0.01. See metered billing for details.
- Seat features charge per user. A plan includes 5 seats, and each additional seat costs $25/month. Seats use a hybrid model: the base allocation is charged in advance, and additional seats are trued up during or at the end of the period. See seat-based pricing for details.
- Consumption features use one of three models depending on the plan configuration: metered (overage at period end), credits (blocks when exhausted), or balance (dollar-denominated deductions).
A subscription is the binding between a customer and a plan. When a customer checks out, a subscription is created that records which plan they chose, when their billing cycle starts, their payment method, and their currency. The subscription is the object that drives all recurring charges, usage tracking, and invoice generation.
How a subscription lifecycle works
The lifecycle of a subscription follows a predictable path.
Creation. The customer selects a plan, enters payment details, and completes checkout. The subscription is created with status active, the first invoice is generated, and the base price is charged immediately.
Renewal. At the end of each billing cycle, the system generates a new invoice. It includes the next period's base charge (advance) and any usage-based charges from the period that just ended (true-up). The stored payment method is charged. If the payment succeeds, the cycle repeats.
Plan changes. A customer can upgrade or downgrade their plan at any time. Upgrades are prorated immediately: the customer pays the difference for the remaining days in the current cycle and gets instant access to the new plan. Downgrades take effect at the next renewal.
Cancellation. When a customer cancels, they retain access until the end of their current billing period. They have already paid for that time. At the end of the period, the subscription moves to cancelled and access is revoked. There is no prorated refund for the remaining days because the customer chose to cancel, not the system.
Payment failure. If a renewal charge fails, the subscription enters dunning. The system retries the payment over a grace period. If recovery succeeds, the subscription returns to active. If all retries fail, the subscription is cancelled.
Plan design principles
Good plan design follows from understanding what your customers value and how your costs scale.
Start from the value metric. The value metric is the unit that most closely correlates with the value your customer receives. For a communication API, it is messages sent. For an AI product, it is tokens processed. For a collaboration tool, it is team members. Your plan's primary consumption feature should track this metric.
Include enough to cover the common case. The base plan should include enough usage that 60-70% of customers never exceed it. If most customers make 5,000-8,000 API calls per month, set the included quota at 10,000. The majority get a predictable bill, and overage pricing captures value from heavy users.
Use feature gates for differentiation. Boolean features create plan tiers. Starter includes core features. Pro adds custom branding and analytics. Enterprise adds SSO and audit logs. Each tier unlocks capabilities for progressively larger customers.
For a step-by-step guide to creating plans, see the create plans documentation.
Subscription billing and revenue recognition
Subscription billing creates specific revenue recognition requirements. The base charge paid in advance is recognized ratably over the service period, not at the point of collection. A $1,200 annual subscription is recognized as $100/month over 12 months, not $1,200 in the month it was charged.
Usage-based charges are recognized when the usage occurs, typically at the end of the measurement period. This distinction matters for financial reporting and is one reason why the billing system needs to maintain precise records of what was charged, when, and for what period.
Related
- Recurring Billing: the automated payment collection mechanism that powers subscriptions
- Billing Cycle: the time period between two invoice dates
- Proration: how mid-cycle plan changes are calculated
- Dunning: recovering failed payments to prevent involuntary churn
- Usage-Based Billing: consumption models used within subscription plans
- Create Plans: guide to setting up plans with features and pricing