AutoMaat
Knowledge base· Data and integrations

Contract-to-cash explained

What contract-to-cash is, which steps it covers, where revenue disappears along the way and how to check the process from signed contract to payment.

Ricardo Mastenbroek8 min read
Lees dit artikel in het Nederlands

Contract-to-cash is the process from a signed contract to the money in your bank account: recording the terms, setting up billing, invoicing throughout the term, applying changes and indexation, collecting payment, and renewing or ending the contract. It matters most for companies with recurring revenue, such as maintenance contracts, subscriptions, licences and framework agreements. The biggest risks are not in the first invoice but in the years that follow, when nobody reads the contract any more.

How does contract-to-cash differ from the other chains?

There are several "to-cash" processes, and they overlap. Quote-to-cash starts at the quote and focuses on price and configuration. Order-to-cash starts at the order and covers delivery, invoicing and collection of individual transactions. Lead-to-cash is the full chain from first interest.

Contract-to-cash starts with the signed contract and runs until the contract ends. Its defining feature is time. An order is completed within weeks. A contract runs for years, and during those years everything changes: quantities, prices, contacts, systems and the people who once drew up the contract.

What are the steps of contract-to-cash?

1. Recording the terms

After signature, the terms of the contract have to be entered into a system: customer, start date, term, price per period, invoicing frequency, indexation clause, notice period, renewal arrangement, special rates, volume tiers, discounts with an end date. This is the step where things go wrong most often, because the contract is written in legal language and billing expects fields.

An indexation clause such as "prices are adjusted annually on 1 January based on the consumer price index" has to become a field: index yes, date 1 January, index a published price index (for example the national consumer price index). An introductory discount "for the first six months" has to get an end date. Whatever is not recorded here will not be invoiced later.

2. Setting up billing

Based on the recorded terms, a recurring invoice, subscription or instalment schedule is created in the ERP or accounting system. Check three things here: is the amount right, is the frequency right, and is the start date right? A contract that starts on 1 March and is invoiced from 1 April misses a month. That month never comes back.

3. Invoicing throughout the term

An invoice goes out every period. This usually goes well, because it is automated. The risk is not in the run itself but in what the run does not know: that the customer has been buying more since last month, that the discount should have stopped, that the contract has renewed automatically.

4. Applying changes and indexation

The contract changes during its term. The customer expands, adds a site, takes extra licences, asks for a different service level. Every change has to reach both the recorded terms and billing. And every year the indexation has to be applied, to the right amount, on the right date.

This is the step with the most silent leakage. A change is agreed by an account manager, confirmed in an email, and never reaches the person who invoices. An indexation is skipped for a year because the employee who always did it has left. The article revenue leakage from missed price indexation describes how that builds up.

5. Collecting

The invoice has to be paid. This is about payment terms, reminders, collection and keeping track of outstanding items. It is the most visible step and usually the best organised: an overdue debtor shows up in red in every accounting package.

6. Renewing or ending

At the end of the term, the contract is renewed, renegotiated or ended. Two risks: a contract that renews automatically but whose billing stops, and a contract that was cancelled but is still being invoiced. The first costs revenue, the second costs a credit note and trust. A third, less visible risk: a renewal that quietly continues at the old price while there was room to renegotiate.

Where does it leak? A summary

Step Typical leak
Recording the terms Indexation clause, volume tier or discount end date not carried over
Setting up billing Start date too late, wrong amount, wrong frequency
Invoicing Run continues on outdated data
Changes Expansion agreed but not invoiced
Indexation Skipped or calculated on the wrong base amount
Collecting Outstanding items without follow-up, written off without reason
Renewing Billing stops on automatic renewal, or renegotiation missed

How do you check contract-to-cash?

The core of the check is always the same: set the agreement against the invoice, contract by contract. Not per month in total, but per contract, per period.

  1. Build a contract register. One list of all running contracts and the terms that determine money. If this is currently in PDFs in a folder, this is the first step. See how to check that contracts are billed correctly.
  2. Calculate the expected invoice per contract per period. Base amount, plus accumulated indexation, plus changes, minus discounts still running.
  3. Compare with what was actually invoiced. Per contract, per period.
  4. Check the calendar. Which contracts have an indexation date, a discount end date or a renewal moment in the next three months? Put each one as a task with an owner.
  5. Check changes. Which expansions were agreed in the CRM or by email and have not yet been processed in the contract register?
  6. Check the end. Which contracts have expired but still have ongoing delivery? Which have been cancelled but are still being invoiced?

Why does it go wrong after year one?

In the first year of a contract everyone is still involved. The salesperson knows the customer, sales support has just entered the contract, finance checked the first invoice. In years two and three that is different. The salesperson is busy with new deals or has left. The contract sits in a folder. Billing runs on the settings from day one.

That is why contract-to-cash is above all a memory problem. The process has to remember what people forget: that indexation is due on 1 January, that the discount stops after eighteen months, that the notice period expires three months before the end date. A system that does not know those moments cannot guard them. That is why the contract register from step 1 carries so much weight: everything after it depends on it.

Worked example

Worked example: suppose a facilities services company has 120 running contracts with an average value of EUR 24,000 a year. While setting up a contract register, it turns out that on 15 contracts an expansion was agreed, averaging EUR 250 a month, that was never processed in billing. And on 20 contracts this year's indexation was not applied. For the example, assume indexation of 3 percent.

The expansions: 15 times EUR 250 times 12 is EUR 45,000 a year. The indexation: 20 times 3 percent of EUR 24,000 is EUR 14,400 a year. Together EUR 59,400 a year, and every year it is not discovered, it keeps running. The indexation also grows, because next year's indexation is calculated on the amount that is too low.

Who owns contract-to-cash?

Contract-to-cash crosses departments. Sales or management signs the contract. Sales support or a contract administrator records it. Finance invoices and collects. Account management renews. That is exactly what makes it a classic silo problem: every department does its step well, and the agreement disappears between the steps. Nobody is responsible for the handover, so nobody notices that something is missing. More on that in why silos cause revenue leakage.

A workable split: finance owns the contract register and the comparison with billing, account management is responsible for reporting changes within a fixed period, and one person guards the calendar of indexations and renewals.

Contract-to-cash is one of the chains that come together in a single source of truth for revenue.

Frequently asked questions

For which companies does contract-to-cash matter most?

For companies where a large share of revenue comes from running contracts: maintenance, service, facilities services, managed services, software and licences, and wholesalers with framework agreements.

Do I need a contract management system?

Not necessarily. A well-kept contract register in a structured form, linked to customer numbers in the accounting system, is enough for many companies to start with. What counts is that the terms that determine money are available as data and not only as a PDF.

How often should I check contracts against invoices?

After every invoice run for the expected amounts, and every quarter for the calendar of indexations, discounts and renewals in the coming months.

What do I do about an indexation that has not been applied for years?

First check what the contract allows. Some contracts allow you to catch up on missed indexations later, others do not, and the rules in your jurisdiction may also play a part. Apart from the legal question, it is a commercial choice: confronting a customer with a large correction can cost more than it brings in. In any case, make sure the indexation is applied correctly from now on.

Share this article
Knowledge base · Data and integrations

More in this cluster

All 16 topics in this cluster

More from AutoMaat

Rather know what this costs you specifically?

The Revenue Audit puts a euro amount on where your revenue leaks.

Plan the Revenue Audit