AutoMaat
Knowledge base· ROI and decisions

When does a revenue audit make sense?

When a one-off revenue audit delivers more than it costs, when it is too early or too late, and how to prepare for one.

Ricardo Mastenbroek8 min read
Lees dit artikel in het Nederlands

A revenue audit makes sense when you suspect revenue is leaking but do not know where or how much, and you want to establish that before you invest in processes or software. Typical moments are a growth phase in which processes fall behind, a change of people in finance or sales, an acquisition, or a persistent gap between the figures from sales and finance. An audit makes less sense when you already know exactly where the leak is and only need time to close it.

What a revenue audit is, and what it is not

A revenue audit is a focused investigation into one question: is this company earning everything it should, given what it sells and delivers? It looks at the whole chain, from pipeline and pricing to invoicing, collection and retention, and searches for places where revenue is lost.

It is not a statutory audit of the financial statements. An external auditor checks whether what is in the books matches what happened. A revenue audit investigates whether things happened that are not in the books: work that was not invoiced, prices that are too low, customers who drifted away without anyone noticing. The difference is set out in revenue audit vs financial audit.

Nor is it a dashboard or BI project. An audit does not produce a tool, but findings with an amount and an order in which to tackle them. How the two relate is covered in revenue audit vs business intelligence.

Six situations in which an audit makes sense

1. You have a suspicion, but no figure

You have a feeling there should be more revenue. The margin is lower than you expect, customers complain about invoices, or the figures from sales and finance do not reconcile. But you do not know where it sits, and without a figure it is hard to decide how much time or money to put into it. An audit turns a suspicion into a number.

2. You have grown fast

Growth puts processes under pressure. What worked with twenty customers and one salesperson no longer works with two hundred customers and five salespeople. The handover from sales to finance that used to happen in conversation now happens by email, and sometimes not at all. An audit after a growth phase shows which processes have not kept pace.

3. Key people have left

A bookkeeper who handled invoicing for twelve years retires. A sales manager who kept every discount agreement in their head leaves. In many companies, knowledge about contracts and agreements sits with individuals. When they go, gaps appear. An audit shortly after such a change finds the agreements that were not handed over.

4. You are preparing for an acquisition, funding round or sale

When your company is valued, buyers and investors look at the quality of your revenue. Recurring revenue that is not invoiced properly, contracts that were not indexed, or a large gap between the CRM and the accounts: all of that surfaces in due diligence. It is better to find it yourself first.

5. You are considering software to monitor revenue

Before investing in continuous monitoring, you want to know whether there is enough to find to justify the investment. An audit gives you that figure and shows which areas deliver the most. Whether you then need software is a separate decision.

6. You have changed your pricing model

A new price list, a move to subscriptions, a new discount policy. Changes to pricing models are a well-known source of leakage, because old agreements keep running alongside new ones. An audit six months after the change shows whether it has actually been implemented in practice.

When an audit does not make sense

An audit is not always the right step.

  • You already know where the leak is. If you know additional work is not being invoiced and you just need a better process, skip the audit and set up that process.
  • Your company is too small or too simple. If all your revenue arises in one system and one person oversees it, the chance of significant leakage is small.
  • There is no capacity to act on the outcome. An audit produces a list of findings. If nobody has time to pick them up in the coming months, it delivers little.
  • You are in the middle of a system migration. Wait until the new system has been running for a few months. Otherwise you are investigating a situation that will no longer exist in three months.

Manual, one-off or continuous

There are different ways to carry out a revenue audit.

Doing it yourself. Your finance team puts the CRM next to billing, goes through contracts and spot-checks projects. That can work well for a first impression. The drawback is that your team mainly finds what it already knows about, and it takes time alongside normal work.

An external audit. Someone who does this every day goes through the areas systematically with questions tailored to your company. You get a list of findings, each with an amount, and an order in which to tackle them.

Continuous monitoring. Software connects your systems and compares them continuously. That is no longer an audit but a permanent control. The difference between a manual audit and automated monitoring is covered in Revenue Intelligence vs a manual revenue audit.

A one-off audit and continuous monitoring are not steps in the same programme. They are two different choices. You can do an audit and resolve the findings yourself without ever using software.

What to expect from a good audit

A good revenue audit has a number of characteristics.

  1. Broad coverage. Not only invoicing, but also pipeline, pricing, retention and data quality. Leakage often sits somewhere other than where you are looking.
  2. Questions that adapt. An installation company leaks differently from a software company. A fixed questionnaire misses what is specific to your business.
  3. Every finding in euros. With the calculation included, so you can check it yourself.
  4. An order of work. Not only what is wrong, but what to do first, based on impact and effort.
  5. An outcome that is yours. You must be able to act on the findings yourself, without being tied to a follow-on engagement.

The AutoMaat Revenue Audit is an example: a one-off review, carried out personally, across eight areas (pipeline, conversion, pricing, invoicing, retention, support, marketing and data quality), in five blocks of questions that adapt to each company. Every finding is priced in euros. It costs EUR 1,500 one-off, with a guarantee that you pay nothing if the audit finds less leakage than it costs. No systems need to be connected.

How to decide whether it is worth it

Worked example: the expected return

Suppose your company has EUR 6M in revenue. You take the bottom of the commonly cited range for revenue leakage, 1 percent, and assume an audit finds half of it. This is an example, not a prediction.

  • 1 percent of EUR 6M = EUR 60,000 of leakage a year.
  • Half found = EUR 30,000.
  • Of that, you realistically recover 60 percent in the first year = EUR 18,000.

Set against that the cost of the audit, plus the internal time to prepare for it and follow up the findings. Even with these cautious assumptions, the return is a multiple of an audit costing a few thousand euros. The question is then not whether it pays off, but whether you have the time to act on the findings.

How to prepare

An audit delivers more if you are well prepared.

  1. Make sure the right people are available. Someone from finance, someone from sales and someone who knows operations.
  2. Know which systems you use. CRM, accounting, billing, time tracking, contract management. Who manages what?
  3. Collect your suspicions. Where do you think things go wrong? Which complaints do you get? Where do figures not reconcile?
  4. Have recent figures to hand. Revenue per month, number of customers, average deal size, outstanding invoices.
  5. Plan time for follow-up. Reserve capacity in the weeks after the audit to pick up the first findings.

If you would rather look yourself first, there is an approach in how to find revenue leakage in a business. For the broader trade-off between a one-off review and continuous monitoring, see what Revenue Intelligence delivers.

Frequently asked questions

How long does a revenue audit take?

That depends on the size of the company and the approach. An audit carried out through conversations, without connecting systems, can be completed within a few weeks, including the report. An audit in which all data first has to be collected and linked takes longer.

Do I have to open up my systems for an audit?

Not necessarily. Some audits run entirely on conversations and figures you supply. Others require access to your CRM and accounts. Ask in advance which approach is used and what happens to your data.

How often should you do a revenue audit?

A one-off audit gives a snapshot. After major changes, such as an acquisition, a new pricing model or a system migration, a new audit can make sense. If you want continuous visibility, continuous monitoring serves you better than an annual audit.

What if the audit finds nothing?

Then you know your processes work, and that is an outcome too. It stops you investing in software or process changes that deliver nothing. Some providers offer a guarantee for this situation.

Share this article
Knowledge base · ROI and decisions

More in this cluster

All 12 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