Usage-Based Billing: How to Invoice Metered SaaS Usage

Quick answer: Usage-based billing charges customers for what they actually consume in a period, such as API calls, storage or seats. To invoice it, measure usage at period end, apply your pricing model (per unit, tiered, volume or overage on top of a base fee), list each tier as its own line with quantity and rate, then add tax and any credits.

Usage-based billing, also called metered billing or consumption pricing, has become a standard way to sell SaaS, APIs and cloud services. It lines up price with value, but it makes invoices harder to read. A flat subscription invoice has one line; a usage invoice may have a base fee, three pricing tiers, an overage, a prorated plan change and a prepaid credit. If the customer cannot check the math, they will question it.

This guide explains the main metered pricing models, how each one should appear on an invoice, how to handle minimum commits, proration and credits, and a fully worked sample invoice with every calculation shown. If you bill a small number of usage customers, you can build each invoice in our free invoice generator once you have the usage numbers from your product.

What usage-based billing means for your invoices

With a fixed subscription, you know the invoice amount before the period starts. With usage-based billing, you only know it after the period ends and the usage data is final. That changes three things about how you invoice:

• Timing: usage is billed in arrears, usually a few days after the period closes so late-arriving events can be counted.
• Evidence: the invoice amount depends on data the customer did not create by hand, so they need a way to verify it, either on the invoice or in a linked usage report.
• Line structure: each billable metric, and often each tier within a metric, needs its own line item with quantity, unit and rate.

The best usage invoices are boring in the right way. A finance person at the customer should be able to open the PDF, open their own usage dashboard and reconcile the two in a few minutes. That is the standard to aim for, whatever pricing model you use.

Common metered pricing models

Most usage-based billing setups are built from a handful of models. Many companies combine two or three of them.

Model	How it works	How it appears on the invoice
Pure per-unit	Every unit costs the same, for example $0.002 per API call	One line: quantity times unit price
Graduated (tiered)	Units in each band are priced at that band's rate	One line per tier, each with its own quantity and rate
Volume	All units are priced at the rate of the tier the total lands in	One line, with the tier reached named in the description
Base fee plus overage	A fixed fee includes an allowance; extra units cost more	Base fee line, included allowance line, overage line
Package or block	Units sold in blocks, such as $10 per 1,000 messages	Number of blocks used, rounded up as the contract says
Prepaid credits	Customer buys credits upfront and draws them down	Usage lines, then a negative line for credits applied
Minimum commit	Customer promises a minimum spend per period	Usage lines, then a true-up line if usage falls short

The difference between graduated and volume pricing causes more disputes than any other detail, so state which one you use in the contract and in the line description. Under graduated pricing, 150,000 units with a first tier of 100,000 means 100,000 at the first rate and 50,000 at the second. Under volume pricing, all 150,000 are charged at the second rate.

Choosing a billable metric

The metric you charge for should be easy for the customer to understand, easy for you to measure accurately, and connected to the value they get. Good metrics include API requests, gigabytes stored per month, minutes processed, messages sent, monthly active users and compute hours. Avoid metrics that the customer cannot see or influence, because they make every invoice feel arbitrary.

Seats are usage too

Per-seat pricing is a simple form of usage-based billing. If seats can be added mid-month, you need a policy for partial periods. Some products charge the full month for any seat active during it; others prorate by day. Our prorated invoice guide walks through daily and monthly proration formulas you can reuse for seats and plan changes.

How to invoice usage-based billing step by step

1. Close the usage period. Decide on a cut-off, for example midnight UTC on the last day of the month, and wait a short grace period for delayed events before you finalize the numbers.
2. Export usage per customer and per metric. Pull totals from your product database, logs or metering service. Keep the raw export; you will need it if the customer asks.
3. Apply the pricing model. Split usage into tiers, subtract included allowances and calculate overage. A spreadsheet works fine at low volume.
4. Add fixed and advance charges. Include the next period's base fee or platform fee if you bill it in advance, with its own service dates.
5. Apply proration, discounts and credits. Add prorated amounts for mid-cycle plan changes, contractual discounts and any prepaid credits being drawn down.
6. Calculate tax. Apply sales tax, VAT or GST according to the customer's location and the tax treatment of your service.
7. Issue the invoice with a usage summary. Number it in sequence, attach or link the usage report, and send it on the same day each cycle.

Once you invoice more than a few dozen usage customers, doing this by hand becomes risky. That is the point where a billing platform with built-in metering earns its cost. Our Stripe invoicing guide covers how one popular option handles invoices, and Stripe's usage-based billing documentation is a useful reference for the concepts even if you use a different tool.

Sample usage-based billing invoice

Here is a worked example for a fictional API company. The customer is on a Growth plan: a $500 monthly platform fee that includes 100,000 API calls, graduated overage pricing above that, storage billed per gigabyte-month, and seats at $15 each. They also hold $100 of promotional credit.

October 2026 usage: 162,500 API calls, 1,240 GB-months of storage and 12 active seats.

Description	Service period	Quantity	Rate	Amount
Growth plan platform fee (includes 100,000 API calls)	Nov 1 to Nov 30, 2026	1	$500.00	$500.00
API calls 1 to 100,000 (included in plan)	Oct 1 to Oct 31, 2026	100,000	$0.000	$0.00
API calls 100,001 to 500,000 (tier 2 overage)	Oct 1 to Oct 31, 2026	62,500	$0.004	$250.00
Storage, GB-months	Oct 1 to Oct 31, 2026	1,240	$0.02	$24.80
Active seats	Oct 1 to Oct 31, 2026	12	$15.00	$180.00
Subtotal				$954.80
Less promotional credit applied				-$100.00
Sales tax (not taxable in this customer's state in this example)				$0.00
Total due				$854.80

The arithmetic, line by line:

• Overage calls: 162,500 total minus 100,000 included = 62,500 calls. 62,500 x $0.004 = $250.00.
• Storage: 1,240 x $0.02 = $24.80.
• Seats: 12 x $15.00 = $180.00.
• Subtotal: $500.00 + $0.00 + $250.00 + $24.80 + $180.00 = $954.80.
• Total: $954.80 - $100.00 credit = $854.80.

Notice two details. First, the platform fee covers November and is billed in advance, while every usage line covers October and is billed in arrears; each line carries its own service period. Second, the included allowance appears as a zero-value line. That line costs nothing, but it shows the customer that the first 100,000 calls were counted and covered, which heads off the most common question on usage invoices.

To make this layout in our generator, enter each row as a line item, use the description field for the tier and service period, and add the credit as a discount. A clean layout such as the startup invoice template keeps a long list of metered lines readable.

Minimum commits, true-ups and overages

Larger usage-based contracts often include a minimum commitment. The customer agrees to spend at least a set amount per month or per year, usually in exchange for a lower unit rate. Invoicing it is straightforward if you keep the calculation visible.

Example: a customer commits to $2,000 per month. In September their metered usage totals $1,640. The invoice shows the usage lines totaling $1,640, then a line reading "Minimum monthly commitment true-up ($2,000.00 - $1,640.00)" for $360.00, for a total of $2,000.00. If usage had been $2,300, there would be no true-up and the invoice would simply total $2,300.

Annual commits work the same way, but the true-up usually appears on the final invoice of the contract year. Some contracts let the customer prepay the commit upfront and draw it down, which turns the commit into prepaid credits. Whichever structure you use, keep a running balance of commit consumed so far and show it in the invoice notes; it saves a support ticket every month.

Rollover and expiry of credits

If unused credits or commit expire at the end of a term, say so in the contract and repeat it on the invoice notes in the final months. Expiring credits also affect how you recognize revenue, which is covered in our guide to revenue recognition under ASC 606.

Proration and plan changes mid-cycle

Usage customers change plans often. When a customer upgrades from a $500 plan to a $1,200 plan on day 11 of a 30-day month, a common approach is to credit the unused portion of the old plan and charge the remaining portion of the new one:

• Unused old plan: $500 x 20/30 = $333.33 credit.
• Remaining new plan: $1,200 x 20/30 = $800.00 charge.
• Net proration: $800.00 - $333.33 = $466.67.

Included allowances should be prorated the same way, or your contract should state that the higher allowance applies for the whole period. Pick one rule and apply it consistently. Proration lines belong on the next regular invoice unless the change is large enough to warrant an immediate one.

What to include on a usage-based invoice

Use this checklist before every usage-based billing run:

• Your business name, address, contact details and tax registration number where required.
• Customer legal name, billing address, and their PO or account number.
• A unique, sequential invoice number; the invoice number generator can help you pick a format.
• Invoice date, due date and payment terms.
• The service period for each line, especially when advance and arrears charges are mixed.
• Each billable metric on its own line with unit, quantity and rate.
• Each tier on its own line under graduated pricing, including the included allowance at zero.
• Proration, discounts, commit true-ups and credits as separate, labeled lines.
• Tax rate and amount, or a note explaining why none applies, such as reverse charge.
• A link to, or attachment of, the detailed usage report for the period.
• Payment methods and, if you take cards, any auto-charge date.

The general principles behind line-level detail are covered in our itemized invoice guide, and they matter even more when quantities change every month.

Common mistakes in usage-based billing

• One blended usage line. "Usage, October: $474.80" gives the customer nothing to check. Break it out by metric and tier.
• Mixing up graduated and volume pricing. Applying the wrong one can overcharge or undercharge by a large margin. Write the model into the contract and the invoice.
• Missing service periods. When advance and arrears lines share one invoice without dates, customers assume they are being double billed.
• Closing the period too early. Events that arrive after you finalize get lost or billed in the wrong month. Allow a short grace window.
• Editing a sent invoice to fix usage. Issue a credit note or an adjustment invoice instead, so your audit trail stays intact.
• No usage alerts. A surprise five-figure invoice damages trust even when it is correct. Warn customers as they approach their allowance.
• Ignoring tax on usage lines. If your service is taxable in a customer's jurisdiction, usage charges usually are too, not just the base fee.
• Rounding inconsistently. Decide whether you round per unit, per line or per invoice, and whether partial blocks round up, then stick to it.

When to automate usage-based billing

Manual usage invoicing works for a few customers with simple pricing. It stops working when you have many customers, several metrics, frequent plan changes or daily usage alerts. At that point you need metering that captures events reliably, a rating engine that applies your price book, and invoicing that runs on schedule. Our recurring invoices guide explains the scheduling side, and you can browse more billing guides by trade in the industry invoices section.

Until then, the combination of a usage export, a spreadsheet for the tier math and a clean PDF invoice is perfectly respectable. What matters most in usage-based billing is not the software but the transparency: every number on the invoice should be traceable to a meter the customer can see.