Usage-Based Invoice Template
A usage-based invoice bills for measured consumption — API calls, storage, compute hours, messages sent, or units used. Because the amount varies each period, the invoice must show the meter readings or usage totals the charge is based on so the customer can verify it.
When to use this
- When pricing is metered: per API call, per GB, per user-minute
- When customers pay for cloud, telecom, or utility consumption
- When a base plan includes an allowance plus overage charges
- When usage varies enough that flat billing would be unfair
- When the contract defines tiered rates that change with volume
Key fields to include
- Billing period and the usage metric billed
- Opening and closing meter readings or total units consumed
- Rate per unit, including any tiered pricing bands
- Base plan fee separate from usage charges
- Overage lines where usage exceeded included allowances
- Link or reference to detailed usage logs
Frequently asked questions
How do tiered usage rates work on an invoice?
Consumption is split across the tiers: for example, the first 1,000 units at one rate and the next 5,000 at a lower rate. Show each tier as its own line with the units and rate so the customer can check the math.
What if the customer questions the usage figures?
Point them to the usage logs or dashboard the invoice references. Keeping verifiable meter data behind every usage invoice is what makes metered billing defensible.
Should I warn customers before a high usage bill?
Yes — usage alerts before the invoice lands prevent shock and disputes. Many providers notify customers at 80% or 100% of their expected usage.
More use cases
Create your document in seconds
Free forever. No signup, no watermarks — your data never leaves your browser.