What is subscription billing?

Subscription billing is the recurring monetization of an ongoing service, where a customer is charged on a repeating cycle (monthly, annual, or usage-based) rather than once per sale. It spans the full subscription management lifecycle: signup and provisioning, recurring invoicing, plan changes and renewals, dunning for failed payments, and revenue recognition. The major models are flat recurring, per-seat, tiered, usage-based or metered, and hybrid. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm and scopes subscription billing to the model and the system that fit a business, with no vendor kickbacks shaping the recommendation.

What is the difference between recurring billing and usage-based billing?

Recurring billing charges a fixed amount each cycle for defined access, which makes revenue predictable and forecasting straightforward. Usage-based billing (also called metered billing) charges for measured consumption such as API calls, gigabytes, transactions, or compute, so the invoice rises and falls with what the customer actually uses. Recurring billing favors predictability; usage-based billing aligns cost with delivered value and lowers the barrier to start. Most modern products land on a hybrid: a committed recurring base plus metered usage on top, often with an included allowance before overage rates apply.

How is usage-based billing treated under ASC 606?

Under ASC 606, the revenue standard issued by the FASB (asc.fasb.org) and converged with IFRS 15, usage-based and metered fees are generally variable consideration. They are addressed at step 3 of the five-step model, where an entity determines the transaction price and estimates variable amounts subject to the constraint on variable consideration. This is general information, not accounting, tax, or legal advice. Usage is not categorically excluded from recurring metrics: non-contractual variable usage is excluded from ARR, but contractual committed minimums can be included. Confirm treatment with your own accounting team and see the saas revenue recognition guide below.

What is dunning in subscription billing?

Dunning is the automated process of recovering a failed subscription payment. When a card is declined or a charge fails, a dunning sequence retries the payment on a schedule and sends reminders to the customer to update their method before access is suspended. Effective dunning reduces involuntary churn, the silent revenue loss that happens when paying customers lapse purely because a payment failed rather than because they chose to cancel. It is a core part of subscription management, distinct from voluntary cancellation. The what is dunning guide covers retry strategies and recovery in detail.

Do usage-based fees count toward ARR?

It depends on whether the usage is committed. ARR is annual recurring revenue, calculated as MRR multiplied by 12, and it counts normalized recurring subscription revenue only. It excludes one-time setup, implementation, and professional-services fees. For usage, the distinction matters: non-contractual, variable usage above any commitment is excluded from ARR because it is not guaranteed to recur, while contractual committed minimums can be included because they are recurring by agreement. ARR and MRR are SaaS-finance conventions for planning and valuation, not GAAP requirements. The annual recurring revenue guide on the umbrella site goes deeper.

What is the difference between tiered billing and per-seat billing?

Per-seat billing prices the subscription by the number of named users or seats, so the invoice scales as a team grows. Tiered billing instead packages capacity and features into set plans (for example good, better, and best), each at a fixed price per cycle, and the customer buys the tier that matches their needs. Per-seat billing tracks adoption closely but can cap expansion once everyone is licensed. Tiered billing simplifies the buying decision and creates clear upgrade paths. Many products combine the two, using seats within a tier, which is one more reason subscription management has to handle proration and mid-cycle changes cleanly.

What does subscription management software need to handle?

Subscription management software has to handle the full billing lifecycle: provisioning at signup, the billing cycle and anchor date, recurring invoicing with proration for mid-cycle starts, plan upgrades and downgrades, add-ons, renewals, dunning for failed payments, and accurate metering for any usage-based component. It also has to feed revenue recognition so earned revenue is spread across the service period rather than booked on cash receipt. Many ERP platforms include native subscription billing: NetSuite, for example, handles recurring and usage billing through its advanced billing capability. Lightbridge ERP evaluates these options neutrally against actual requirements.

How does Lightbridge ERP help with subscription billing?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. It helps recurring-revenue businesses choose a billing model and the system to run it, then carries the program through delivery. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the recommendation is driven by fit rather than commission. For the NetSuite practice, billing, revenue, and subscription management are delivered in-house; for other platforms, delivery runs through vetted partners under Lightbridge program management and technical leadership. The work always ties billing back to clean revenue recognition and reliable recurring metrics.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Last updated June 2026.

Subscription Billing Models: Recurring, Usage-Based, Hybrid

Lightbridge ERP defines subscription billing as the recurring monetization of an ongoing service, where a customer is charged on a repeating cycle rather than once per sale. The common models are flat recurring, per-seat, tiered, usage-based or metered, and hybrid. Subscription management spans the full lifecycle: signup, invoicing, renewals, changes, dunning, and revenue recognition.

Choose a billing system SaaS revenue recognition

Subscription billing charges customers on a repeating cycle, not once per sale.

Subscription billing is the model behind any recurring-revenue business: the customer pays on a repeating cycle for ongoing access, and the vendor bills, collects, and recognizes that revenue over time. The shift from one-time sales to subscriptions changes the back office. Instead of a single invoice at the point of sale, finance manages a living relationship that renews, expands, contracts, and occasionally fails to pay.

That living relationship is what subscription management handles. It spans signup and provisioning, recurring invoicing, plan changes and renewals, dunning for failed payments, and the revenue recognition that keeps the books honest. The billing model you pick (flat, per-seat, tiered, usage-based, or hybrid) sets the rhythm for all of it.

This guide is vendor-neutral and general. Where it references how a platform implements a model, it does so as a neutral example, not an endorsement. Nothing here is accounting, tax, or legal advice: confirm any treatment with your own qualified advisors.

Subscription billing models range from flat recurring to usage-based and hybrid.

There is no single right subscription billing model. The fit depends on how a product delivers value and how customers prefer to buy. Most businesses combine a few of these, and the dominant pattern today is hybrid: a recurring base plus metered usage on top. These are the building blocks.

Flat recurring billing

A fixed price per cycle for defined access, the simplest recurring billing model. Revenue is predictable and easy to forecast, which is why most subscriptions start here. The trade-off is that a flat fee does not flex when one customer consumes far more than another.

Per-seat billing

Price scales with the number of named users or seats. Common in software where value tracks the size of the team using it. Per-seat billing grows neatly with adoption, but it can cap expansion once every user is already licensed.

Tiered billing

Customers buy a packaged tier (good, better, best) at a set price per cycle, each tier bundling more capacity or features. Tiered billing simplifies the buying decision and creates clear upgrade paths, while keeping invoices predictable within a tier.

Usage-based and metered billing

Charges follow measured consumption: API calls, gigabytes, transactions, or compute. Usage-based billing (also called metered billing) aligns cost with value delivered and lowers the entry barrier, but it makes revenue less predictable and demands accurate, auditable metering.

Hybrid billing

A committed recurring base plus variable usage on top, often with an included allowance before overage rates apply. Hybrid billing is now the dominant pattern for usage-driven products: it preserves a predictable floor while still capturing upside from heavy consumption.

One-time and add-on charges

Setup fees, implementation, professional services, and one-off add-ons sit alongside the recurring stream. They are real revenue, but they are not recurring, which matters when calculating normalized recurring metrics like ARR.

Subscription management runs the full billing lifecycle, from signup to recognition.

Choosing a model is the start. Running subscription billing well means managing the lifecycle that follows: provisioning, invoicing, mid-cycle changes, renewals, failed-payment recovery, and the revenue recognition that ties it all back to the financial statements.

Provisioning and invoicing

Subscription management begins at signup: provision access, set the billing cycle and anchor date, and generate the first invoice. Proration handles mid-cycle starts so the first charge matches the days actually granted.

Changes, renewals, and dunning

Upgrades, downgrades, add-ons, and renewals each adjust the recurring amount, often with proration or credits. When a charge fails, dunning is the automated retry and reminder sequence that recovers the payment before access lapses.

Recognition and reporting

Cash collected is not the same as revenue earned. Subscription management feeds revenue recognition, which spreads each obligation across the service period, and feeds the recurring metrics leadership tracks. Treat any benchmark figure as a rule of thumb that varies by model and industry.

Failed payments are a quiet source of churn. The recovery sequence that addresses them is covered in the what is dunning guide, and the way subscription revenue is earned over time is covered in the SaaS revenue recognition guide.

Subscription billing meets ASC 606 at the transaction price and variable consideration.

How you bill is a commercial decision. How you recognize the resulting revenue is an accounting one, governed by ASC 606 (the FASB revenue standard at asc.fasb.org, converged with IFRS 15 and superseding most of legacy ASC 605). ASC 606 applies a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate it, and recognize revenue as each obligation is satisfied.

Usage-based and metered fees matter most at step 3, where the transaction price is determined. They are generally variable consideration, estimated and subject to the constraint that limits how much variable revenue can be recognized. Amounts billed in advance create deferred revenue, a contract liability under ASC 606 that becomes revenue as the service is delivered. None of this is accounting, tax, or legal advice. The SaaS revenue recognition guide works through the mechanics, and your accounting team should confirm treatment for your contracts.

Subscription billing feeds the recurring metrics leadership tracks, starting with ARR.

Once subscription billing is running, finance and leadership measure it. The headline figure is ARR, annual recurring revenue, calculated as MRR multiplied by 12. ARR normalizes recurring subscription revenue only and excludes one-time setup, implementation, and professional-services fees. Usage is the nuance: non-contractual variable usage above commitments is excluded, but contractual committed minimums can be included because they are recurring by agreement.

These are planning and valuation conventions, not GAAP requirements, so keep them distinct from the audited revenue ASC 606 produces. A fuller treatment of the headline metric lives in the annual recurring revenue guide on the Lightbridge umbrella site. Treat any retention or growth benchmark as a rule of thumb that varies by model, segment, and industry.

Lightbridge ERP matches the subscription billing model to the business, then the system.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. For recurring-revenue companies, it helps select a subscription billing model and the platform to run it, then carries the program through delivery. Many ERP and billing platforms now ship native subscription management. NetSuite, for example, handles recurring and usage billing through its advanced billing capability, described in the NetSuite SuiteBilling guide. Lightbridge compares such options against real requirements rather than steering toward one product.

What keeps the advice honest is the commercial model: Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, so a recommendation follows fit, not commission. Billing and revenue are delivered in-house for the NetSuite practice and through vetted partners under Lightbridge program management elsewhere. To start, ERP consulting and a structured selection connect the billing model to clean revenue recognition and dependable metrics.

Subscription billing models: frequently asked questions

What is subscription billing?: Subscription billing is the recurring monetization of an ongoing service, where a customer is charged on a repeating cycle (monthly, annual, or usage-based) rather than once per sale. It spans the full subscription management lifecycle: signup and provisioning, recurring invoicing, plan changes and renewals, dunning for failed payments, and revenue recognition. The major models are flat recurring, per-seat, tiered, usage-based or metered, and hybrid. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm and scopes subscription billing to the model and the system that fit a business, with no vendor kickbacks shaping the recommendation.
What is the difference between recurring billing and usage-based billing?: Recurring billing charges a fixed amount each cycle for defined access, which makes revenue predictable and forecasting straightforward. Usage-based billing (also called metered billing) charges for measured consumption such as API calls, gigabytes, transactions, or compute, so the invoice rises and falls with what the customer actually uses. Recurring billing favors predictability; usage-based billing aligns cost with delivered value and lowers the barrier to start. Most modern products land on a hybrid: a committed recurring base plus metered usage on top, often with an included allowance before overage rates apply.
How is usage-based billing treated under ASC 606?: Under ASC 606, the revenue standard issued by the FASB (asc.fasb.org) and converged with IFRS 15, usage-based and metered fees are generally variable consideration. They are addressed at step 3 of the five-step model, where an entity determines the transaction price and estimates variable amounts subject to the constraint on variable consideration. This is general information, not accounting, tax, or legal advice. Usage is not categorically excluded from recurring metrics: non-contractual variable usage is excluded from ARR, but contractual committed minimums can be included. Confirm treatment with your own accounting team and see the saas revenue recognition guide below.
What is dunning in subscription billing?: Dunning is the automated process of recovering a failed subscription payment. When a card is declined or a charge fails, a dunning sequence retries the payment on a schedule and sends reminders to the customer to update their method before access is suspended. Effective dunning reduces involuntary churn, the silent revenue loss that happens when paying customers lapse purely because a payment failed rather than because they chose to cancel. It is a core part of subscription management, distinct from voluntary cancellation. The what is dunning guide covers retry strategies and recovery in detail.
Do usage-based fees count toward ARR?: It depends on whether the usage is committed. ARR is annual recurring revenue, calculated as MRR multiplied by 12, and it counts normalized recurring subscription revenue only. It excludes one-time setup, implementation, and professional-services fees. For usage, the distinction matters: non-contractual, variable usage above any commitment is excluded from ARR because it is not guaranteed to recur, while contractual committed minimums can be included because they are recurring by agreement. ARR and MRR are SaaS-finance conventions for planning and valuation, not GAAP requirements. The annual recurring revenue guide on the umbrella site goes deeper.
What is the difference between tiered billing and per-seat billing?: Per-seat billing prices the subscription by the number of named users or seats, so the invoice scales as a team grows. Tiered billing instead packages capacity and features into set plans (for example good, better, and best), each at a fixed price per cycle, and the customer buys the tier that matches their needs. Per-seat billing tracks adoption closely but can cap expansion once everyone is licensed. Tiered billing simplifies the buying decision and creates clear upgrade paths. Many products combine the two, using seats within a tier, which is one more reason subscription management has to handle proration and mid-cycle changes cleanly.
What does subscription management software need to handle?: Subscription management software has to handle the full billing lifecycle: provisioning at signup, the billing cycle and anchor date, recurring invoicing with proration for mid-cycle starts, plan upgrades and downgrades, add-ons, renewals, dunning for failed payments, and accurate metering for any usage-based component. It also has to feed revenue recognition so earned revenue is spread across the service period rather than booked on cash receipt. Many ERP platforms include native subscription billing: NetSuite, for example, handles recurring and usage billing through its advanced billing capability. Lightbridge ERP evaluates these options neutrally against actual requirements.
How does Lightbridge ERP help with subscription billing?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. It helps recurring-revenue businesses choose a billing model and the system to run it, then carries the program through delivery. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the recommendation is driven by fit rather than commission. For the NetSuite practice, billing, revenue, and subscription management are delivered in-house; for other platforms, delivery runs through vetted partners under Lightbridge program management and technical leadership. The work always ties billing back to clean revenue recognition and reliable recurring metrics.

From billing model to clean recurring revenue.

When the question shifts from which subscription billing model to which system runs it, Lightbridge ERP runs a vendor-neutral selection and ties billing back to reliable revenue recognition.

Talk to an ERP advisor Start an ERP selection