Revenue leakage between contract and invoice

Revenue leakage between contract and invoice arises when terms in the contract are not applied, or not applied correctly, in invoicing. Think of volume tiers, minimum commitments, rates for additional work, indexation, discounts with an end date and recharged costs. Invoicing is set up at the start on what is known at that moment, and every later condition has to be carried through by hand. Because the contract usually sits as a PDF in a folder and no system knows about it, a leak like this can run for years.

Below: the clauses that leak most often, why, how to find them and how to stop them leaking again. For the full picture, see the complete guide to revenue leakage.

Why the contract and the invoice drift apart

A contract is a legal document, written to record agreements. A billing system is an administrative system, set up to produce invoices. Between the two sits a translation, and that translation usually happens once: at the start of the contract.

At that moment someone copies the monthly amount, the start date and the product into invoicing. Whatever else the contract says, such as "from 51 users, rate B applies", "the rate is indexed on 1 January each year" or "the 10 percent discount applies for the first twelve months", is conditional or lies in the future. It cannot be set up at the start, or only with a knowledge of the billing system that the person entering it does not have.

After that nothing happens, unless someone remembers. And nobody remembers, because nobody opens the contract again.

Which contract clauses leak most often?

Volume tiers and thresholds

"Up to 50 users EUR 30 per user, from 51 to 100 users EUR 27, above that EUR 25." That looks like it favours the customer, and it does. But tiers work the other way too: a customer who drops below a minimum falls into a more expensive rate. And tiers with surcharges, for example for extra support above a certain volume, are often not applied when the threshold is crossed.

Minimum commitment

"The customer commits to a minimum of EUR 5,000 a month." If the customer buys EUR 3,800, you may invoice the difference. In practice that rarely happens, because nobody puts monthly volume next to the minimum.

Rates for additional work

The contract states EUR 95 an hour for work outside the scope. Invoicing uses the standard rate of EUR 85, or does not invoice the additional work at all because it was not flagged as such.

Discounts with an end date

"A 15 percent discount applies in the first contract year." The discount is entered as a permanent discount on the customer, and simply carries on afterwards. This is one of the most common and best-hidden leaks, because the invoice looks normal. See revenue leakage from wrong prices.

Indexation

"The rate is adjusted on 1 January each year in line with the consumer price index." If that is not in invoicing as a date and a rule, it is forgotten. Because of its impact and the way it compounds, it has its own article: revenue leakage from missed price indexation.

Recharged costs

Travel costs, material costs, third-party licences, shipping costs. The contract says they are recharged, but they never reach the invoice because the costs sit in a different system from invoicing.

Term and renewal

The contract ends. Under its terms it renews at the rate then in force, but invoicing carries on at the old rate. Or it should have been renegotiated, and nobody saw the end date. See revenue leakage from expired contracts.

Worked example

Worked example: suppose a facilities services provider has 150 contract customers with an average contract value of EUR 40,000 a year. A check of all contracts against the past year's invoices shows:

Total: EUR 72,750 a year, around 1.2 percent of contract revenue of EUR 6 million. Indexation has not even been counted here. The figures are assumptions for the example. How to put a figure on each finding is set out in how to calculate revenue leakage.

How to find it

Step 1: make the terms checkable

You cannot check an invoice against a contract if the terms exist only in a PDF. For each contract, extract the clauses that determine the price:

• base rate and unit;
• volume tiers and thresholds;
• minimum commitment;
• rate for additional work;
• discounts, with start and end dates;
• indexation: which index, which date, any floor or cap;
• recharged costs;
• term, renewal and notice period.

Put them in a table, one row per contract. For a few hundred contracts that is a substantial job. AI can extract the clauses from PDFs, after which a person checks the result. Start with the largest contracts.

Step 2: calculate the expected invoice per contract

With the clauses and the actual volume or delivery per period, calculate what should have been invoiced. For tiers and minimum commitments you need the quantities. For additional work, the hours. For discounts, the date.

Step 3: compare with the actual invoice

Put the expected invoice next to the actual invoice, per period, per customer. Every difference is a finding.

Step 4: prioritise

Start with the largest recurring differences. A discount that keeps running costs money every month. A one-off missed recharge costs less.

How to close it for good

Record price-setting clauses in a system. Not only in the PDF. That can be in the CRM as fields on the customer or the deal, in invoicing as rules, or in a contract management system. What matters is that the date and the rule sit somewhere a system can read them.

Standardise where you can. The more contracts have non-standard clauses, the greater the chance of error. A limited set of standard clauses for indexation, tiers and additional work makes checking simpler.

Make end dates active. Every discount with an end date, every indexation date and every contract end date becomes a task or alert before the date passes, not after.

Do not leave it to the salesperson alone. Sales often negotiates a non-standard clause and then considers the job done. Have finance or contract management sign off the translation into invoicing.

Check periodically or continuously. An annual check of all contracts is the minimum. Continuous is better, especially with recurring revenue.

Checklist

• Are the price-setting clauses of each contract recorded somewhere other than the PDF?
• Do you know for each customer whether there is a discount with an end date, and when it ends?
• Is volume per period compared with the minimum commitment?
• Is additional work invoiced at the contractual rate?
• Are costs that the contract says must be recharged actually recharged?
• Is there an alert before a contract ends?
• Does someone other than the salesperson sign off the translation from contract to invoicing?

Frequently asked questions

What is the difference between this leak and the leak between CRM and billing?

The leak between CRM and billing concerns the handover of a deal; see revenue leakage between CRM and billing. The leak between contract and invoice concerns the terms that apply afterwards: tiers, discounts, indexation, minimum commitments. A deal can be handed over correctly and still be invoiced wrongly for years.

Can I still invoice amounts missed in the past?

That depends on the contract, the limitation period and the relationship with the customer. It is often wiser to invoice correctly from now on and discuss the past with the customer. Check the rules in your jurisdiction and take legal advice if in doubt.

How do I get the clauses out of hundreds of PDFs?

By hand, with a fixed template per contract, or with AI that reads the clauses and a person who checks the result. Start with the largest contracts.

Which clause leaks most?

It differs per company. Discounts with an end date and indexation are often missed in practice, because once the date has passed the invoice still looks normal.