Usage-Based Billing
How It Works, Pricing Models & Revenue Recognition
Usage-based billing charges customers for what they actually consume instead of a flat fee. This guide covers how the metering-to-revenue process works, the five usage-based pricing models, why it leaks revenue, and how to recognize revenue on variable usage contracts under ASC 606.
Usage-Based Billing Definition
Usage-based billing is a pricing model where customers are charged based on how much of a product or service they consume — API calls, compute, seats, data, or transactions — rather than a fixed subscription fee. The billing cycle meters consumption, applies the contract's rate card, generates an invoice for the period, and recognizes the resulting revenue.
Because consumption varies every period, usage-based billing creates variable consideration that must be reconciled against the signed contract and recognized under ASC 606 or IFRS 15. That reconciliation — not the metering itself — is where most teams lose revenue and audit confidence.
Also referred to as: metered billing, consumption-based billing, pay-as-you-go billing, usage-based pricing.
How Usage-Based Billing Works
The usage-based billing process runs in six steps, from capturing raw consumption to recognizing revenue. Steps 3–5 are where metered usage has to match the contract — and where it usually breaks.
Meter usage
Capture raw consumption events from your product — API calls, compute, seats, data, or transactions.
Rate & aggregate
Apply the contract's rate card to raw events and aggregate them into a billable total for the period.
Reconcile to contract
Match metered usage against signed terms — per-unit pricing, tiered thresholds, minimum commitments, caps, and prepaid credits.
Generate invoice
Create the invoice for the period and sync it to your billing system without manual re-keying.
Recognize revenue
Build ASC 606 / IFRS 15 revenue schedules for variable consideration and post them to your ERP.
Reconcile cash
Match incoming payments back to invoices and the general ledger so billing, cash, and revenue agree.
The 5 Usage-Based Pricing Models
Most usage-based billing falls into one of five pricing models. Many B2B SaaS companies run several at once across different customers — which is exactly what makes reconciliation hard.
Per-unit / Pay-as-you-go
A fixed price for every unit consumed — $0.01 per API call, $1 per GB, $5 per seat-hour. Simple to explain, but revenue is hard to forecast.
Example: Twilio, AWS Lambda
Tiered
The unit price changes as usage crosses thresholds. The first 1,000 units cost one rate, the next 9,000 a lower rate, and so on.
Example: Most API platforms
Volume
All units are priced at the rate of the highest tier the customer reaches in the period — rewarding large commitments with a single blended rate.
Example: Infrastructure & data tools
Prepaid credits
The customer buys a credit balance up front that usage draws down. Requires tracking burn-down, expirations, and top-ups against the contract.
Example: OpenAI, cloud credits
Hybrid (subscription + overage)
A base platform fee covers an included allotment, and metered overages bill on top. The most common B2B SaaS model — and the one that leaks the most revenue.
Example: Most B2B SaaS
Why Usage-Based Billing Leaks Revenue
Metering the usage is the easy part. The revenue leaks downstream — when usage has to be reconciled against the contract, invoiced accurately, and recognized correctly.
Unbilled overages HappyRobot recovered in 30 days
LedgerUp customer
of revenue lost to billing errors
MGI Research
of revenue can leak between contracts, billing & collections
Zilliant
Revenue leakage
Overages calculated by hand in spreadsheets. Formulas break, and billable usage slips through unbilled for months before anyone notices.
Manual overage math
Reconciling usage against contract terms means pulling data from multiple systems and double-checking every result. A single cycle can take 5–7 days.
Revenue recognition headaches
Variable usage creates variable consideration under ASC 606. Recognizing it correctly each month with journal entries is slow, error-prone, and hard to audit.
System sync failures
Invoice data in Stripe or Orb drifts out of sync with contract terms in your CRM. Discrepancies take hours to resolve and erode customer trust.
Billing Engine vs. Revenue Subledger
A metering engine and LedgerUp solve different halves of usage-based billing. You need both: an engine to count usage, and a revenue subledger to make sure every unit is billed and recognized.
| Metering / billing engine | LedgerUp revenue subledger | |
|---|---|---|
| Primary job | Count usage events and apply a rate card | Verify every unit is billed, reconciled & recognized |
| Examples | Stripe Billing, Orb, Metronome, Chargebee | LedgerUp (works alongside your engine) |
| Catches unbilled overages | Limited — bills what it meters | Yes — reconciles usage against the signed contract |
| ASC 606 / IFRS 15 rev rec | Partial or add-on module | Built-in variable-consideration schedules |
| Contract-aware | No — rate cards only | Yes — reads signed contracts and terms |
| Where it runs | Standalone billing app | Slack + your CRM, billing system & ERP |
Bottom line: Use a metering engine like Stripe Billing, Orb, or Metronome to count usage. Use LedgerUp to reconcile that usage against the contract, catch unbilled overages, and recognize revenue under ASC 606 — without ripping out the billing stack you already have.
How LedgerUp handles usage-based billing
LedgerUp's AI agent Ari sits on top of your billing engine, reconciles metered usage to the contract, and turns it into invoice-ready, audit-ready revenue.
Automated overage reconciliation
Ari continuously compares metered usage to contract thresholds and surfaces every billable overage automatically — no spreadsheets, no broken formulas.
Contract-aware metering
Ari reads your signed contracts and understands per-unit pricing, tiers, minimums, and overage terms, so billing always matches what was agreed.
ASC 606 revenue schedules
Ari builds audit-ready revenue schedules from metered usage, handling variable consideration and minimum commitments under ASC 606 and IFRS 15.
Works with your billing engine
Keep Stripe, Orb, or Metronome for metering. Ari adds the reconciliation and revenue layer on top and keeps every system in sync.
“Ari took a job we dreaded and turned it into something we don't even think about anymore. Billing just works now. And we found $72K we didn't know we were leaving on the table.”
- Varez, GTM Lead at HappyRobot
Related Guides
A side-by-side comparison of the top usage-based and metered billing platforms, and where each one fits.
How to recognize revenue on variable, usage-based contracts and stay audit-ready.
Where usage-based billing quietly loses money — and how to plug the gaps.
Stop leaving money on the table when metered usage doesn't match what you invoice.
Usage-Based Billing FAQ
Frequently asked questions about usage-based billing, pricing models, and revenue recognition.
What is usage-based billing?
Usage-based billing (also called metered or consumption-based billing) is a pricing model where customers are charged based on how much of a product or service they actually consume — API calls, compute, seats, data, or transactions — rather than a flat subscription fee. The billing process meters consumption, applies the contract’s rate card, generates an invoice for the period, and recognizes the resulting revenue.
How does usage-based billing work?
Usage-based billing works in five steps: (1) meter raw consumption events from your product, (2) rate and aggregate those events using the contract’s pricing, (3) reconcile the total against signed terms such as minimums, caps, and prepaid credits, (4) generate and send the invoice, and (5) recognize the revenue under ASC 606 or IFRS 15. The hard part is steps 3–5, where metered usage has to match the contract and produce audit-ready revenue schedules.
What is the difference between a metering engine like Orb or Metronome and LedgerUp?
A metering or billing engine (Stripe Billing, Orb, Metronome, Chargebee) counts usage events and applies a rate card to produce a charge. LedgerUp sits on top of whatever engine you use as a revenue subledger: it reconciles metered usage against the signed contract to catch unbilled overages, builds ASC 606 / IFRS 15 revenue schedules for variable consideration, and keeps your billing system, CRM, and ERP in sync. Use a metering engine to count usage; use LedgerUp to make sure every unit is billed, reconciled, and recognized.
How do you handle revenue recognition (ASC 606) for usage-based contracts?
Usage-based contracts create variable consideration, which ASC 606 and IFRS 15 require you to estimate and recognize as the customer consumes. Because usage changes every month, manual journal entries break down quickly. LedgerUp generates revenue schedules directly from metered usage, handles variable consideration and minimum commitments, and produces audit-ready schedules that sync to your ERP — without monthly spreadsheets.
What are the common usage-based pricing models?
The five most common usage-based pricing models are: per-unit / pay-as-you-go (a fixed price per unit consumed), tiered (the unit price changes as usage crosses thresholds), volume (all units are priced at the rate of the highest tier reached), prepaid credits (the customer buys a balance that usage draws down), and hybrid (a base subscription fee plus metered overages). Most B2B SaaS companies use a hybrid model.
Why does usage-based billing cause revenue leakage?
Usage-based billing leaks revenue when metered usage is calculated manually in spreadsheets, when overages aren’t reconciled against contract terms, or when invoice data in the billing system falls out of sync with the CRM. Billable usage slips through unbilled for months, and disputes erode customer trust. Research from Zilliant estimates up to 31.8% of annual revenue can leak through gaps between contracts, billing, and collections.
Can LedgerUp work with our existing billing system?
Yes. LedgerUp is not a replacement billing engine — it works alongside Stripe, Orb, Metronome, Chargebee, and others. It reads your contracts and usage data, reconciles them, catches unbilled overages, and recognizes revenue, so you keep your existing metering stack and add the reconciliation and revenue layer on top.