Tiered pricing looks simple: buy more, pay less per unit. In practice it is one of the most common sources of overbilling we see, because two small details are easy to get wrong.
Detail one: graduated or volume tiers?
There are two common ways tiers work.
- Graduated tiers price each band separately. The first 50,000 units cost $18.50, the next 70,000 cost $16.75, and so on.
- Volume tiers price every unit at the rate of the tier you reach. Pass 120,000 units and all units cost $15.20.
The contract wording decides which applies. Get it wrong and every invoice is wrong.
Detail two: what volume counts?
Most network contracts measure volume across all sites combined for the period, often a calendar month that resets on day one. Suppliers, though, usually invoice each site separately. If each invoice is tiered on its own site’s volume, every site starts again at Tier 1.
A worked example
Take an airline catering contract with these graduated tiers for economy meals, resetting monthly:
| Tier | Monthly volume | Per meal |
|---|---|---|
| 1 | 0 to 50,000 | $18.50 |
| 2 | 50,001 to 120,000 | $16.75 |
| 3 | 120,001 to 200,000 | $15.20 |
| 4 | 200,001 and above | $14.00 |
In July, six hubs served 187,600 meals between them. Priced correctly across the network:
- 50,000 × $18.50 = $925,000
- 70,000 × $16.75 = $1,172,500
- 67,600 × $15.20 = $1,027,520
- Total $3,125,020, a blended rate of $16.66 a meal
Now the supplier bills each hub separately. London (62,400 meals) reaches Tier 2 on its own and is billed $1,132,700, an average of $18.15. Every other hub stays below 50,000, so every meal is billed at $18.50. Across the six hubs the invoices total $3,448,900.
The difference is $323,880 in one month, or close to $3.9M a year. And every single invoice is arithmetically correct.
Why reviewers miss it
An accounts payable reviewer checking the London invoice sees 62,400 meals, the right tier for 62,400 meals and correct maths. Nothing looks wrong. The error only appears when you add up every hub’s volume for the month, which means waiting until all six invoices have arrived and doing the sum yourself.
How to catch it
You need three things:
- Running totals. Keep a total of volume per contract, product and period that updates with every invoice.
- Reference matching. Link each hub invoice to the same contract, even when each hub’s billing system uses a different reference.
- A rules engine. Recalculate the correct blended rate as volume builds, and compare each invoice line against it.
That is exactly how ContractSense works. Try it with your own numbers in the tier pricing checker, or see the full worked example.