Metered billing

DEFINITION

Metered billing is a pricing and invoicing model in which a customer is charged based on actual usage of a product or service during a billing period, rather than a fixed recurring fee. Usage is tracked continuously and the final invoice reflects however much or little the customer consumed.

Metered billing is a pricing and invoicing model in which a customer is charged based on actual usage of a product or service during a billing period, rather than a fixed recurring fee. Usage is tracked continuously, or at regular intervals, and the customer's final invoice reflects however much or little they actually consumed.

This model is common for services where consumption naturally varies from customer to customer and from month to month, such as cloud infrastructure billed by compute hours or data transferred, communications platforms billed by messages or minutes, and API products billed by number of calls. Metered billing requires infrastructure to track usage accurately, apply pricing rules (a rate per unit, tiered rates, or included allowances) to that usage, and generate an invoice that reflects the result. A subscription billing platform such as Recurly can ingest usage data and apply metered pricing rules to generate accurate invoices, coordinating the usage tracking, rating, and billing steps that metered billing depends on.

Why metered billing matters for subscription businesses

Metered billing lets a business align what a customer pays with the value that customer actually receives, which can make pricing feel fairer to customers with highly variable usage and can also make a service accessible to smaller customers who would be priced out by a large flat fee. This flexibility is a major reason metered and usage-based pricing has grown alongside cloud infrastructure and API-driven products.

At the same time, metered billing introduces revenue variability that a purely flat-rate subscription does not have. Revenue in a given month depends on how much customers actually use the product, which makes forecasting more complex and puts pressure on usage tracking accuracy, since any error in measuring consumption flows directly into what customers are billed. Getting metered billing right, both the usage tracking and the resulting customer experience, is central to running a usage-based pricing model well.

How metered billing works

Metered billing depends on a pipeline that captures usage events, converts them into billable units, and turns those units into an invoice.

  1. The product or service emits usage events as a customer consumes it, such as an API call, a gigabyte transferred, or a minute of usage.

  2. Those usage events are collected over the billing period and aggregated into a billable quantity per usage type per customer, typically by summing every event (cumulative aggregation), though usage types that reflect a current state, such as seat count or storage level, may instead be billed on only the most recently recorded value.

  3. Pricing rules are applied to the aggregated usage, which may include a flat rate per unit, a percentage of the usage amount, tiered or volume-based rates, or an included usage allowance before charges begin.

  4. The resulting charge is calculated once the billing period closes and added to the customer's next invoice, since usage is billed in arrears, often alongside the base subscription fee for the new period.

  5. The invoice is generated and sent to the customer, ideally with a usage breakdown so the customer can see how the charge was calculated.

Because usage can be difficult for a customer to predict in advance, many metered billing setups also expose usage dashboards or alerts so customers can track consumption before the invoice arrives.

How to use metered billing effectively

A well-run metered billing model depends on more than accurate usage tracking:

  • Give customers visibility into their usage in near real time, not just at invoice time, so unexpected charges do not come as a surprise.

  • Set usage alerts or spending caps where practical, especially for new customers who are still learning their typical consumption pattern.

  • Combine metered charges with a base subscription fee when appropriate, which stabilizes some revenue while still capturing upside from higher usage.

  • Reconcile usage data carefully before invoicing, since billing disputes over metered charges are harder to resolve after the fact than disputes over a flat, predictable fee.

  • Choose billing cycles and true-up periods that make sense for how usage naturally accrues, so customers are not billed on an awkward schedule relative to their actual consumption pattern.

Metered billing vs flat-rate billing

Flat-rate billing charges a customer the same fixed amount each billing period regardless of how much they use the product, while metered billing ties the charge directly to actual consumption. Flat-rate billing is simpler to predict and budget for, both for the customer and for the business's own revenue forecasting, but it can overcharge light users and undercharge heavy users relative to the value each receives. Metered billing aligns cost with usage more precisely, which tends to suit products with highly variable consumption, but it introduces more billing complexity and less predictable revenue. Many businesses combine the two, charging a flat base fee plus metered overage charges once usage crosses an included allowance.

Benefits and examples

  • Pricing that scales with value received. Customers pay in proportion to what they actually use, which can lower the barrier to entry for smaller customers and grow revenue naturally as usage increases.

  • Revenue that grows with customer success. As a customer's usage increases, so does the business's revenue from that account, aligning incentives between vendor and customer.

  • Supports a wide range of product types. Metered billing fits naturally with infrastructure, API, communications, and other consumption-driven products where a flat fee would poorly match actual value delivered.

  • Example scenario (illustrative). An API platform charges customers a small base subscription fee plus a per-call rate once monthly usage exceeds an included allowance of calls. A customer running a seasonal promotion sees a temporary spike in API calls one month, and their invoice reflects that spike accurately, rather than being capped at a flat rate that would have undercharged for the extra load on the platform.

Frequently asked questions

How is metered billing different from usage-based pricing? The terms are closely related and often used interchangeably. "Usage-based pricing" typically refers to the pricing strategy itself, while "metered billing" often refers more specifically to the billing mechanics of tracking usage and generating invoices from it.

Can metered billing be combined with a flat subscription fee? Yes, this is a very common hybrid model, where customers pay a base subscription fee that may include a set amount of usage, plus additional metered charges once usage exceeds that included allowance.

What happens if usage data is inaccurate? Inaccurate usage tracking flows directly into inaccurate invoices, which can lead to billing disputes and customer trust issues, so reliable usage measurement and aggregation is a critical foundation for any metered billing setup.

Does metered billing make revenue harder to forecast? Yes, to some degree. Because charges depend on customer usage, which can vary month to month, metered revenue is generally less predictable than flat-rate subscription revenue, though patterns often stabilize as a customer base matures.