Revenue leakage from missed price indexation

Revenue leakage from missed price indexation happens when a contract gives you the right to raise prices every year, and that increase never reaches the invoice. The money is legally yours, but nobody enters the new price in the billing system. Because every missed indexation becomes the base for the next one, the gap grows every year. You close this leak with a contract register that holds the indexation date for each customer and a fixed check before the first invoice run of the year.

Why is this leak so hard to see?

A missed indexation produces no error message. The invoice is correctly prepared, the customer pays on time and the receivables ledger is clean. Nothing looks out of place, except that the amount is lower than it should have been. That is exactly the kind of loss that never shows up in any report.

The difference from an invoicing error is that nobody here does anything wrong. The finance team invoices what is in the system. Sales closed the contract and moved on to the next deal. The account manager does not want to burden the relationship with a price increase during a busy period. Everyone acts reasonably, and still the company loses money. It is one of the most common forms of revenue leakage, precisely because it causes no pain anywhere on the shop floor.

How does an indexation clause work in practice?

Most B2B contracts with a term longer than a year contain an indexation clause. The form varies:

• Linked to an index. For example a published price index (such as the national consumer price index), a collective wage index or a sector index. The increase follows the published figure over an agreed period.
• A fixed percentage. "Rates will be increased by 3 percent on 1 January each year." No index needed, just a date.
• A combination or a cap. "Indexation in line with CPI, capped at 5 percent." Or: "CPI plus 1 percent."
• A right, not an obligation. "The supplier is entitled to index its rates annually." In that case you have to announce it yourself, often with a notice period.

That last form is the most dangerous. An automatic indexation can often still be corrected afterwards, because the customer has already agreed to it. An indexation you had to announce and did not announce is often simply gone. If the contract has a thirty-day notice period and you missed it, there is usually nothing more you can do for that period.

Where does it go wrong?

There are four places where an indexation falls through the cracks.

The contract is not in a system. The signed contract sits as a PDF in a folder or in the account manager's mailbox. The indexation clause is on page seven. The billing system only knows an item and a price. Nobody has transferred the date and the formula into anything that can raise a flag.

Everyone thinks someone else is doing it. Finance thinks sales will inform the customer. Sales thinks finance will adjust the prices in January. In revenue leakage between contract and invoice this is the standard pattern: the agreement was made, but nobody owns its execution.

Terms are negotiated customer by customer. One customer has CPI, another a fixed percentage, a third has a cap and a fourth was given a year's exemption as part of a large order. A general price increase via the price list then hits the wrong customers, or misses precisely the customers with a different arrangement.

People do not dare. An account manager who has just secured a difficult renewal is not going to announce in February that the price is going up 4 percent. That is understandable. But if that choice is not made explicitly and recorded, it is not a commercial decision. It is a forgotten euro.

The compounding effect

A missed indexation does not cost money just once. It lowers the base on which every later indexation is calculated. If you do not index in year one, you invoice at the old price in year two, and any indexation in year two is calculated from that price, which is too low.

Worked example: suppose you have a service contract worth EUR 60,000 a year with a fixed indexation of 3 percent on 1 January. You forget the indexation three years in a row.

That is one contract. With forty contracts like it, the cumulative difference after three years is more than EUR 440,000. And the leak does not stop by itself: as long as nobody intervenes, the annual gap is larger every year than the year before.

The worked example shows something else too. If you do index by 3 percent in year four, you arrive at EUR 61,800, while the contractual price by then is EUR 67,531. You will never close that gap with one normal indexation. For that you need to go back to the customer with a conversation about catching up, and that is a different conversation from an annual routine letter.

What can you still recover?

Whether you may invoice missed indexations after the fact depends on the wording of the contract and on what you have communicated to the customer since. An automatic indexation based on a fixed formula gives you a stronger position than a right you had to announce. Even then, a customer who has received and paid three years of invoices without indexation will not welcome a back-charge. The rules differ between jurisdictions, so if in doubt, put it to your lawyer.

In practice most companies take a middle path: apply the indexation correctly from now on, on the right contractual base, and have a business conversation about the past. What you leave on the table there is a commercial choice. The most important thing is that it is a choice, not an accident.

How do you check for it?

You do not need software to see whether you have a problem here. You do need an afternoon and access to the contracts and the billing data.

1. List every running contract older than twelve months. Customer name, start date, contract value, term.
2. Find the indexation clause in each contract. Record the type (index, fixed percentage, right), the effective date, any notice period and any cap.
3. Pull the current price per contract from the billing system. Look at the price on the most recent invoice, not at the price list.
4. Calculate today's contractual price. Apply every indexation since the start. For an index-linked clause you will need the published figures for each year.
5. Put the two side by side. Every contract where the invoiced price is lower than the contractual price gets a line with the annual difference and the cumulative difference.
6. Check whether there is a recorded reason. A written agreement with the customer not to index for a year is a decision. No reason is a leak.

This check overlaps with the broader work of verifying that contracts are invoiced correctly, and indexation is often the largest single item in it.

How do you prevent it structurally?

A one-off check finds the leak. A process keeps it closed. This works in practice:

• A contract register with fields, not PDFs. For each contract at least: indexation type, formula, effective date, notice period, cap, owner. This can live in your CRM (a separate set of fields on the contract or deal object in HubSpot or Salesforce) or in your ERP. A shared spreadsheet works too, as long as it has one owner.
• A fixed calendar. Put the notice deadline in a calendar, not the indexation date itself. With a thirty-day notice period before 1 January, the letter must go out before 1 December, so the work starts in November.
• One owner per annual round. Usually finance or a commercial director. That person checks that every contract with indexation has been processed before the first invoice run of the year.
• Record exceptions. If you decide not to index a particular customer, record who decided, why and for which period. Next year you will know whether it was an exception or a new base.
• Link the price in the billing system to the contract. In Exact, AFAS, Xero or NetSuite a subscription price is often disconnected from the contract. Add the contract reference to the description or a free field, so a check can always trace which contract sets the price.

Why doing it by hand does not scale

With ten contracts, an annual check in a spreadsheet is fine. With two hundred contracts with different indices, effective dates and caps, it becomes error-prone. Then the same problems return as with wrong prices in general: what is in one system no longer matches the other, and nobody sees it until someone happens to look.

A continuous comparison between contract data and invoice lines catches this the moment it happens: the first invoice after the effective date that still carries the old price. Whether you do that with a script, a BI report or a platform matters less than that it happens automatically. The use cases page shows what this pattern looks like next to the other seven areas where revenue leaks away.

Frequently asked questions

Can I still invoice missed indexations after the fact?

That depends on the wording of the contract and on what you have communicated since. An automatic indexation gives a stronger position than a right you should have announced. If in doubt, have it assessed legally, and check the rules in your jurisdiction, before you send a back-charge.

Which index do I use if the contract does not specify one?

If the contract only mentions "indexation" without naming an index, there is room for dispute. A common choice is a published price index such as the national consumer price index, but in new contracts always record the index, the reference period and the effective date. A vague clause is almost as bad as no clause.

Is a general price increase via the price list enough?

Only if all your customers are on the price list. Customers with a contract price, their own indexation arrangement or a cap often fall outside it. So check at customer level, not at item level.

How often should I check?

At least once a year, well before the first indexation date and allowing for notice periods. If you have contracts with different effective dates throughout the year, a monthly check is better.

Who is responsible for indexation?

Whoever it is, it must be one named person. It usually sits with finance, with sales informing the customer. The leak arises precisely when both departments think the other one is handling it.