Guide

Overage tiers: does the count reset every month or run all year?

"The first 20,000 credits at $0.05, the next 40,000 at $0.04" doesn't say whether the count runs per month or per year, or whether crossing a band reprices every credit. On one ordinary contract, those readings put the year's overage bill anywhere from $10,620 to $16,310.

TrueUpp Research · Published 19 October 2026 · 6 min read

About the example. The contract and usage below are an illustration we built to show the mechanics. They aren't any company's real figures. Every number was computed line by line and is reproducible from the table.

Two choices hidden in one clause

Tiered overage clauses usually look like this: Usage above the included credits is billed at $0.05 per credit for the first 20,000, $0.04 for the next 40,000 and $0.03 thereafter. That sentence leaves two decisions open, and billing systems have to make both of them anyway.

• Graduated or volume. Under graduated pricing, each rate applies only to the credits inside its band. Under volume pricing, crossing a threshold reprices every credit at the new rate.
• What the count measures. The position in the tiers can start again at zero every billing period, or it can keep counting through the contract year. The clause above doesn't say.

Two choices with two answers each gives four readings. The gap between them runs to thousands of dollars on a mid-sized contract.

What each reading does to the invoices

Graduated, resetting monthly: $16,310

The monthly reset is what a billing system gives you when it prices each period on its own. Stripe's tiered prices, for example, are worked out on the usage in each billing period, so a monthly metered price starts its tiers again every month. Graduated or volume is a setting chosen when the price is created. Under this reading the customer never reaches the $0.03 band, even though it used 354,000 overage credits over the year. In annual terms, it went through the 60,000 threshold in May.

Volume, resetting monthly: $14,710

Volume pricing has cliffs. In April the customer used 22,000 overage credits and paid $880. In May it used fewer, 20,000, and paid $1,000, because 20,000 sits at the top of the first band and is billed at $0.05 throughout. Using less cost more. Customers notice this kind of thing, and then they ask what else is wrong with the invoice.

Graduated, counting all year: $11,420

The running total passes 20,000 in March and 60,000 in May. From June, every overage credit is billed at $0.03. Each invoice is still easy to check, as long as it shows the year-to-date count it started from.

Volume, counting all year: $10,620

This is the hardest one to invoice monthly. When the running total crosses a threshold, every earlier credit moves to the new rate, so the crossing month carries a credit for the months before it. March's invoice is $450: $640 for March's 16,000 credits at $0.04, less $190 because January's and February's 19,000 credits drop from $0.05 to $0.04. May's invoice is $30 for 20,000 credits: $600 for May, less $570 for repricing the 57,000 credits billed earlier. Someone in finance will have to explain a $30 invoice for a month with 20,000 overage credits.

Which one did the contract mean?

If the clause doesn't say, look for the intent elsewhere before the billing system decides for you:

• Threshold size. Bands of 20,000 and 40,000 on a 50,000-a-month allowance suggest monthly thresholds. Bands in the millions on the same allowance suggest annual ones.
• Wording elsewhere in the order form. Look for "cumulative", "during the term", "per contract year" or "in any billing period". The rollover and minimum clauses often state their period even when the tier clause doesn't.
• What the deal was modeled on. If the deal desk or the rep sent a pricing calculator or a renewal projection, it shows which reading the customer was quoted.
• How it has been billed so far. Past invoices the customer paid without dispute are evidence too, though not always of what was agreed.

When none of these settles it, the billing system's default becomes the contract in practice. A RevOps practitioner made the same point in a public discussion about rollover: the system just does "whatever the first person coded". The argument tends to come at renewal, when the customer's finance team adds up the year.

Running annual tiers on monthly invoices

• Keep a running count per contract year. Start it on the contract's anniversary, not 1 January, and store it next to each invoice so anyone can check where the month started.
• Supply the tier position from outside the billing system if it prices each period separately. One option is to work out the month's overage from the year-to-date count and post it as its own line. Another is to bill overage once a year on an annual price, which delays the cash by up to twelve months.
• Show repricing as a separate line. Under annual volume tiers, put the credit for earlier months on its own line with the old and new rate, instead of netting it into the month's charge.
• Decide what an amendment does to the count. If an upgrade starts a new segment of the contract, say whether the year-to-date count carries into it or starts again. See why amendments should start a new segment.

What to write down

1. Graduated or volume. Name it in the clause itself.
2. The period the count covers: billing month, quarter or contract year.
3. What's counted toward thresholds: overage credits only, or all usage including the included credits. That's a third choice, which doubles the readings to eight.
4. When the count starts again: at renewal, at an amendment, or never during the term.
5. A worked month. One month of example usage, priced out line by line, in the order form. Both sides then read the same number.

The true-up calculator prices one contract with up to six overage tiers and shows the bill under both tier methods side by side. For how often pricing pages leave these rules out, see our review of 64 usage-based pricing pages.