Overage Billing: Included Quotas, Excess Usage and Plan Changes

A plan with an included quantity and a price for anything above it sounds like one line of code: usage minus allowance, times price. In practice the trouble starts elsewhere. The customer changes plan mid-month and nobody decided what happens to the allowance. The contract says "per started block of 100 documents" and the system bills per document. The overage line lands on the next invoice with the wrong service period, and the direct debit comes back because the amount surprised the customer.

This article works through one plan and shows which rules you need to settle before you automate overage billing. How multi-tier prices behave beyond a single allowance is covered in tiered pricing for SaaS billing.

The example plan

A document-processing provider has two plans. All amounts are net and made up:

A Team customer processes 6,240 documents in April. The invoice: €900 base fee plus 1,240 × €0.20 = €248 overage, €1,148 in total.

So far the formula holds. Before it goes into production it has to answer three questions.

What a 16th-of-the-month upgrade does to the allowance

The customer processes 4,000 documents on Team from 1 to 15 April, moves to Business on the 16th and processes another 7,000 by 30 April. That's 11,000 in total. The base fee is split by day: 15/30 × €900 plus 15/30 × €1,600 = €1,250. For the overage there are three common rules:

Same usage, between €0 and €700 of overage. The third row isn't an edge case. It often happens by accident when a plan change is implemented as a cancellation plus a new subscription: the base fee gets prorated, but the allowance is granted in full every time. A customer who notices can multiply their allowance by switching plans.

The prorated rule is the easiest to defend, because base fee and allowance are split the same way. The second is friendlier and easier to explain. Sales and finance pick one. What matters is that exactly that rule is in your terms and that the billing system applies it. Downgrades need the same decision, usually with the addition that they only take effect at the next period start.

Unit price, block price, cap: the rounding lives in the contract

Many overage prices are written as blocks, for example "€20 per started 100 documents". For the 1,240 overage documents from the first example that gives three amounts, depending on the reading:

• per document: 1,240 × €0.20 = €248
• per started 100: 13 blocks × €20 = €260
• per full 100: 12 blocks × €20 = €240

A €20 monthly difference rarely escalates. With enterprise customers who recompute invoices it does, and then the question is whether the system and the contract read the clause the same way.

Other contract terms the billing system has to know:

• Cap: maximum overage per period, for example €1,000. Applied after rounding and before tax.
• Minimum commitment: the base fee then acts as a prepayment that overage is drawn against.
• Rollover: can unused allowance carry into the next month? If so, for how long, and what happens on cancellation?
• Unit definition: what counts as a "document"? Does a failed upload count? Does a reprocessed document count twice?

That last one is also a technical question. If retries send the same event twice, the customer pays overage for work that happened once. How to prevent that is covered in idempotent usage event processing.

Overage goes on the next invoice, with its own service period

The most common cadence: the base fee is billed monthly in advance, overage in arrears. The 1 May invoice then has two lines with different periods:

• Business base fee, service period 1 to 31 May: €1,600
• Overage, service period 1 to 30 April: €700

Both periods belong on the invoice. The date of supply is a mandatory invoice detail under the EU VAT Directive, and an invoice that only says "May" is wrong for April's usage. For a reverse-charge customer elsewhere in the EU, both lines carry the same tax treatment, as long as the customer's master data didn't change between the two periods.

The close sees the shift too. April's overage is April revenue, even though the invoice is only raised in May. Finance therefore needs an accrual for unbilled usage at month end, which means a reliable number on 30 April before the invoice exists.

Two alternatives to monthly billing in arrears:

• Threshold invoice: once accrued overage exceeds an amount, say €2,000, it's invoiced straight away. That limits credit risk when usage swings a lot.
• Prepaid balance: the customer buys credit that's drawn down with usage. That changes the accounting and needs a rule for unused balance at contract end.

Direct debit makes surprises expensive

Overage is a varying amount. With SEPA direct debit that has two consequences.

First, pre-notification. Unless agreed otherwise, the customer has to be told the amount and date 14 calendar days before collection. If you invoice on 1 May and want to collect on 3 May, your terms need a shorter period. With fixed base fees nobody notices; with overage the amount changes every month.

Second, the refund right. Under the SEPA Core scheme a customer can reclaim an authorised debit within eight weeks without giving a reason; in Germany that's § 675x BGB (German Civil Code). A customer surprised by a €700 overage line may well return the whole €2,300 debit, not just the disputed part. The SEPA B2B scheme has no such refund right.

The most effective protection against returns is usage alerts during the month: a message at 80% and 100% of the allowance, with the current count and the price of each further unit. How mandates, pre-notification and returns fit together is covered in SEPA direct debit for SaaS.

Test cases before the first automated run

With the example plan, the rules can be tested against fixed expected values:

1. 6,240 documents on Team: €248 overage, or €260 or €240 with block pricing depending on the contract wording.
2. Upgrade on 16 April with 4,000 + 7,000 documents: base fee €1,250, overage according to the chosen rule (€700, €200 or €0).
3. Two plan changes in one month: the allowance must not be granted more often than the rule allows.
4. Usage exactly equal to the allowance: no overage line, not even one for €0.00.
5. Cap exceeded: the amount stops at the cap, but the full quantity still appears on the invoice.
6. Next invoice: base fee and overage each carry their own service period.
7. The same event sent twice: usage goes up once.

In Kontier, the allowance and overage price are part of the versioned plan definition that's applied to usage events.