Who is responsible for revenue leakage?

Ultimate responsibility for revenue leakage lies with the board or the CFO, because leakage arises between departments and no single department sees the whole. Day-to-day responsibility lies with whoever manages the handover where the leak occurs: sales for what goes into the contract, operations for what is delivered and recorded, finance for what is invoiced and collected. The problem in most companies is not that nobody is responsible, but that everyone thinks someone else is.

Why nobody feels ownership

Revenue leakage has a particular characteristic: it almost always arises on the boundary between two departments. A deal is won by sales and invoiced by finance. Additional work is agreed by a project manager and invoiced by the accounts team. An indexation clause is negotiated by sales, recorded by legal and applied by finance, if someone remembers.

Each department does its own part well. Sales closes the deal and marks it as won. Finance invoices what comes in. Operations delivers. But what gets lost between those steps is in nobody's job description.

Ask sales about a won deal that was never invoiced, and the answer is: "I marked it as won, invoicing is finance's job." Ask finance, and the answer is: "We never received an order confirmation." Both are right. And the money is gone.

This pattern is at the heart of why silos cause revenue leakage. It is also why fixing revenue leakage is first an organisational question, and only then a systems question.

What are the levels of responsibility?

It helps to separate responsibility into three levels.

1. Accountable: who answers for the total

Someone has to answer the question: how much revenue are we leaking, and what are we doing about it? That has to be someone with oversight of sales, operations and finance at the same time. In most companies, that is the CFO, the finance director or, in smaller companies, the managing director.

Why not sales? Because sales has no view of invoicing and payment. Why not finance alone? Because finance has no influence over what is agreed in contracts or how deals are recorded in the CRM. The accountable person must be able to steer across that boundary.

2. Process owner: who manages the handover

Every leak arises at a specific handover. For each handover, one person must be responsible for making sure it goes right.

This breakdown follows the line of contract-to-cash: the chain from agreement to money in the bank. Exactly where the leaks in that chain sit is covered in where revenue leakage comes from.

3. Executor: who fixes the specific leak

Once a leak has been found, someone has to fix it: raise the invoice after all, call the customer, adjust the price, correct the subscription. That is often someone other than the process owner. A missed indexation is fixed by the account manager who informs the customer and the accounts team who enters the new price.

Importantly, the executor must have the time and the authority. A bookkeeper who has to send a customer a corrective invoice for a mistake made by sales, without sales knowing about it, is in an awkward position.

Where does RevOps fit in?

Larger companies, and increasingly mid-sized ones, have a Revenue Operations function. RevOps is meant precisely to bridge the boundaries between sales, marketing, customer success and finance. It seems obvious to place revenue leakage there.

That works if RevOps also has access to, and influence over, billing. In many companies RevOps is in practice sales operations with a new name: responsible for the CRM, the pipeline and the sales tools, but with no view of what happens in the accounts. Then the problem simply moves.

The difference between a RevOps team and the tools that support it is covered in Revenue Intelligence vs RevOps.

Why "everyone is responsible" does not work

A common response is that revenue leakage is a shared responsibility. Everyone should work carefully, everyone should pay attention. That is true, and it solves nothing.

Shared responsibility without an owner leads to three things:

1. Nobody looks actively. Everyone watches their own work. Nobody looks at the space in between.
2. Leaks that are found stay unresolved. When someone spots a discrepancy, they do not know who to take it to.
3. Nobody learns from the cause. A leak may be fixed, but the process that caused it stays the same.

How to set it down: a step-by-step plan

1. Name an accountable person. One person, by name, who reports on revenue leakage to the board every quarter.
2. Map your chain. From quote to payment, with every handover between people or systems.
3. Assign an owner to each handover. Use the table above as a starting point and adapt it to your own organisation.
4. Agree how leaks that are found are reported. One place, one format, with amount, customer and cause.
5. Set down who may fix what. May finance send a corrective invoice on its own, or must sales inform the customer first? May the accounts team change a price, or does the account manager have to approve it?
6. Make it measurable. Number of leaks found, amount, time to resolution, per handover.
7. Review it every quarter. Which handover leaks most? What will you change in the process?

Worked example: what unclear ownership costs

Suppose a EUR 12M company finds ten discrepancies every quarter, averaging EUR 3,000 each. Without a clear owner, half are resolved within a month, and the other half sit for an average of four months before someone picks them up. Some of those are never resolved, for example because the customer has left in the meantime or it is commercially too late. This is an example.

Suppose a quarter of the discrepancies that sit are never resolved. That is about 1.25 discrepancies of EUR 3,000 per quarter, so EUR 3,750 per quarter and EUR 15,000 a year. That is only the part that is lost for good. On top of that comes the money that arrives months late. With one owner per handover and a fixed turnaround time, most of that loss disappears.

The role of systems

Systems do not solve the question of responsibility. They do make it more visible. When discrepancies are found automatically and land with the right owner, there is no more debate about who should have seen them. The question shifts from "who should have found this" to "why has this not been resolved yet".

That is also where many investments in detection run aground: the system finds discrepancies, but they end up in a list without an owner. So decide first who picks up what, and only then choose a system. What a well organised approach delivers more broadly is covered in what Revenue Intelligence delivers.

Frequently asked questions

Is the financial controller responsible for revenue leakage?

The controller is often a logical process owner for the steps from invoice to payment and for periodically reconciling systems. But they usually have no influence over what sales agrees in contracts. Ultimate responsibility belongs with someone who can steer across both sales and finance.

Should sales be measured on invoiced revenue rather than won deals?

That is an effective way to make sales a co-owner of what happens after closed-won. It makes salespeople check for themselves that their deals are handed over correctly. It does require the link between deal and invoice to be reliable, otherwise every commission payment becomes a debate.

What if a leak is caused by a customer?

A customer who does not pay, or who uses more than they bought, does not cause the leak. They benefit from it. The leak lies in the fact that it goes unnoticed or is not followed up. So the responsibility still lies internally.

How big does a company need to be to formalise this?

As soon as the person who sells is not the same as the person who invoices, you have a handover. From that point it makes sense to set down who is responsible. It does not need to be a heavy document. A table of handovers and names is enough.