Revenue Intelligence vs a manual revenue audit

A manual revenue audit is a one-off, thorough pass through your revenue chain carried out by a person: they ask questions, put documents side by side and put an amount on what is leaking away. Revenue Intelligence is software connected to your systems that makes those same comparisons continuously, so new leaks show up as soon as they appear. The audit gives you a sharp picture at one moment and a plan. Revenue Intelligence keeps that picture current. They answer different questions: "where am I leaking now?" versus "where will I be leaking next month?".

What does a manual revenue audit do?

A revenue audit follows revenue from the first click to the paid invoice and looks for the places where money disappears along the way. That is something other than a financial audit of the annual accounts. The question is not whether the books are right, but whether everything you should have invoiced was actually invoiced, at the right price, and whether you are holding on to customers and opportunities. The difference with a statutory audit is worked out in revenue audit vs financial audit.

A good manual audit works with three kinds of evidence:

• Conversations. How does an order travel from quote to invoice? Who is allowed to give discounts? What happens to additional work on a project? The answers show where the process leans on one person.
• Samples. Twenty won deals from the CRM set against the invoices. Ten contracts with an indexation clause set against current prices. Five customers with falling volumes followed up.
• Figures you already have. Revenue per customer, discount percentages, debtor days, churn, sales cycle. Deviations from what you would expect in a company of this type point to where to dig deeper.

The strength of a person is judgement. An auditor hears in a conversation that "the project manager usually does pass on the additional work" and knows there is a leak there, even if nobody can yet point to it in a system. They see that one customer appears three times in the CRM under slightly different names and understand why the forecast never adds up. Software only makes connections like that once someone has named them first.

The weakness is time. An audit is a snapshot. On the day the report is finished, it starts to age. A new price list, an employee who leaves, an integration that stops running: the leaks that appear afterwards go unseen until the next audit.

What does Revenue Intelligence do?

Revenue Intelligence connects to your CRM, billing, ERP and support system and puts the data side by side continuously. How that works technically is covered in the complete guide to Revenue Intelligence. In short, it does three things a manual audit cannot:

1. Check everything, not a sample. Every won deal against every invoice, every night. Not twenty out of four hundred.
2. Flag discrepancies at the moment they appear. A customer who orders less in March than in January, a contract that expires next month with no renewal action, an invoice without the indexation that should have taken effect on 1 January.
3. Hold on to the work. A finding becomes a task with an owner and an amount, not a line in a report.

The weakness of software is the mirror image of a person's. It only sees what is in the connected systems. An agreement that exists only in an email, a discount promised verbally, additional work that was never recorded: to a system, none of that exists. And software without good definitions mostly finds noise. If nobody has recorded that a deal only counts as "won" once there is a signed contract behind it, the system reports a hundred differences that are not real.

The difference side by side

Automated revenue audit vs traditional audit

You will also come across the term "automated revenue audit". It usually means software that runs the checks of an audit automatically: CRM against billing, contract against invoice, price list against billed price. In practice that is part of what Revenue Intelligence does, only once rather than continuously.

A traditional audit and an automated audit find different leaks. Take an installation company with maintenance contracts.

• The automated check sees that 14 contracts were not indexed this year, because the invoiced price is the same as last year while the contract has an indexation clause.
• The traditional audit discovers in a conversation that engineers "just do" small repairs during a maintenance visit without a job sheet. That is in no system at all, so no software finds it.

Both leaks are real. They simply call for a different instrument. That is why the question is rarely which of the two is better, but which comes first.

When to start with a manual audit

Start with an audit if you do not yet know where you are leaking. Connecting software before you know where to look is an expensive way to search. An audit is also the better start when:

• your systems do not line up and nobody knows exactly which source is leading;
• a large part of the process runs outside systems: verbal agreements, spreadsheets, paper job sheets;
• you first want to know whether the problem is big enough to address structurally;
• you need internal support, and an amount in euros makes that conversation easier than a hunch.

A concrete example of such a one-off pass is AutoMaat's Revenue Audit: carried out personally, across eight areas from pipeline to data quality, in five blocks of questions that adapt to the company, with every finding priced in euros. Nothing is connected to your systems for that audit. It is a separate product with its own plan as the result, not a preliminary step to software.

When to look at Revenue Intelligence

Revenue Intelligence becomes interesting when you know where you leak and notice that the same leak keeps coming back. Signs of that:

• You have done the CRM-to-billing comparison once before, found something, fixed it, and six months later the difference is back.
• The volume is too large for sampling: hundreds of orders a month, thousands of contract lines, many recurring invoices.
• Leaks arise from changes that happen every week: new customers, changed subscriptions, price adjustments.
• You do not want an unpleasant surprise once a year, but to see the leak in the month it appears.

Whether it pays for itself depends on how much is leaking and how quickly it returns. The arithmetic is in what Revenue Intelligence delivers.

Worked example: a snapshot versus a film

Worked example: suppose a wholesaler with EUR 8M in revenue finds in an audit that 1.2 percent of won orders were never fully invoiced. That is EUR 96,000 a year. The cause: orders that are edited in the CRM after they have already been passed to the ERP. The company fixes it with an agreement: changes after hand-over go through finance.

Six months later there is a new salesperson who does not know the agreement, and an integration that maps a field wrongly after a CRM update. The leak grows back to 0.8 percent. With an annual audit, the company only notices in month twelve. By then roughly EUR 5,300 a month has leaked away for six months, around EUR 32,000 in total.

With continuous checking, the difference shows up in the first week after the update. The difference between the two scenarios is not the leak itself. It is how long it runs before anyone sees it.

The same arithmetic can point the other way. If the leak does not return after the fix, because the cause really is gone, continuous monitoring adds little at that point. A periodic repeat of the check is then enough.

Step by step: how to choose

1. Write down where you think you are leaking. Three to five places, with a rough estimate in euros. If you do not know, that is already an answer: start with an audit.
2. For each place, decide whether the leak is visible in systems. An invoice without indexation is visible. Additional work without a job sheet is not.
3. For each place, decide how often it can occur. Once a year at the price round, or every day with every order?
4. Visible and frequent: a candidate for continuous checking. Invisible or rare: a candidate for an audit and a process change.
5. Check your definitions. Before you automate anything: what counts as won, as invoiced, as an active customer? Without those agreements, software produces noise.
6. Plan the repeat. Whoever runs an audit puts the next one in the diary, or decides which check must continue after the audit.

How they complement each other

In practice, companies that take this seriously use both. The audit finds the causes and the leaks that fall outside systems. The software monitors the leaks that are visible in systems and flags when a previously closed leak returns. An audit without follow-up produces a report that is no longer accurate after a year. Software without an audit monitors the wrong things or finds differences nobody understands.

For the wider comparison with other kinds of software, from BI to ERP, see Revenue Intelligence vs Business Intelligence. It also explains why a dashboard replaces neither of the two.

Frequently asked questions

Is a manual revenue audit outdated now that software exists for it?

No. Software checks what is in systems. An audit also finds what is not: verbal agreements, work that was never recorded, processes that rely on one person. Those leaks are often the largest.

How often should you repeat a manual audit?

There is no fixed rule. Repeat it when your organisation changes significantly: new systems, a new pricing model, growth in customers or staff. Without such changes, an annual review of the largest findings is often enough.

Can Revenue Intelligence replace an audit?

For leaks that are visible in connected systems, largely yes, and it does better because it works continuously. For process errors and agreements outside systems, no. There you still need a person who asks questions.

What do you need for a manual audit?

Time from the people who know the process, access to a few exports or reports, and someone who asks the right questions. Connections are not needed. An audit in conversation form can even be done without any data leaving your systems.

What comes first, the audit or the software?

In most cases the audit. It tells you where the money is and which checks are worth doing. After that you know whether continuous monitoring adds anything and where it should focus.