Revenue audit vs business intelligence

Business intelligence shows what is in your systems: revenue by month, by customer, by product, in charts anyone can read. A revenue audit looks for what is not there or does not add up: won deals without an invoice, contracts running at an outdated price, additional work that was never recharged. BI answers the questions you already ask. A revenue audit asks the questions nobody asked. That is why a company with good dashboards still finds leaks when someone looks for them deliberately.

What business intelligence does and does not do

A BI environment, whether that is Power BI, Tableau, Excel with pivot tables or a data warehouse in Snowflake, does three things well. It pulls data from sources, makes it comparable, and presents the result in a form you can read quickly. On Monday a director sees last week's revenue, margin by product group and outstanding receivables.

But BI reports on the data it receives. It does not ask whether that data is complete. A dashboard showing "invoiced revenue by customer" neatly shows what was invoiced. What should have been invoiced and was not does not appear in it. There is no bar for "forgotten additional work".

Three limitations keep coming back:

• BI shows outcomes, not expectations. To see a leak, you need to know what should have been there. That lives in contracts, order confirmations and pricing agreements, and those are rarely in the data model.
• BI looks per source or per linked table. If the CRM and the accounts are not linked at customer level, a dashboard cannot put them side by side. It then shows two figures that are both correct and together mean nothing.
• BI waits for someone to look. A chart that declines slowly only stands out if someone looks at it at the right moment with the right question.

More on that difference: Revenue Intelligence vs dashboards.

What does a revenue audit do?

A revenue audit does not start with the data, but with the question of how revenue is supposed to flow. From quote to order confirmation, from contract to recurring invoice, from won deal to first payment. It then checks at every hand-over point whether something gets lost.

That means working with sources BI usually does not have:

• contracts and their clauses: indexation, volume tiers, minimum commitments, renewal terms;
• pricing agreements that sit in emails or quotes and not in the system;
• job sheets, time records and project administration;
• the people who run the process, and their exceptions.

The result is not a chart but a list of findings: what is leaking, where, how much a year, and what to do about it.

Side by side

Why a good BI environment still leaks

It sounds contradictory: surely a company with a mature BI environment would spot leaks sooner? Sometimes it does. But BI can also hide a leak, because it gives the impression that everything is in view.

An example. A technical services firm has a Power BI dashboard showing revenue by contract type. Revenue from maintenance contracts rises a few percent each year. Everyone is satisfied. What the dashboard does not show: the number of contracts has grown by 12 percent, so revenue per contract has fallen. The reason: new contracts are signed at the current price list, while existing contracts have not been indexed for three years. Growth in new customers masks the leak in the old ones.

The dashboard is correct. The question it should have shown, "does every customer pay what their contract says?", was not in it.

A second example. A wholesaler shows order value from the ERP and revenue from the accounts in BI. Both lines move together, with a difference of a few percent that everyone puts down to "timing". Only during an audit does it turn out that part of that difference is not timing but orders that were partly delivered and whose remaining delivery was never invoiced. The difference was on screen every month. Nobody had broken it down. How to make that comparison yourself is covered in how to check CRM against billing.

Worked example: the gap between two lines

Worked example: suppose a company with EUR 6M in revenue sees a structural difference of 3 percent in BI between order value and invoiced revenue, some EUR 180,000 a year. An audit breaks the difference down:

• EUR 95,000 is genuine timing: orders in December, invoiced in January. Not a leak.
• EUR 40,000 is credit notes for returns. Not a leak, but a point to watch for quality.
• EUR 45,000 is remaining deliveries that were not invoiced and orders changed after hand-over without the invoice being adjusted. That is the leak.

Without the breakdown, the difference is noise. With it, a quarter can be recovered, year after year. BI supplied the signal, the audit supplied the answer.

When to use which

You need BI to run your business. It does not replace an audit, and an audit does not replace BI. The question is when an audit adds something to what you already see:

• Your dashboards disagree with each other. Sales and finance report different revenue. An audit works out which difference is leakage and which is definition. Those definitions are the subject of a single source of truth for revenue.
• You see a trend but not the cause. Margin falls, average price per customer drops, churn rises. BI shows it, an audit explains it.
• Your BI does not cover the whole chain. Contracts, projects or job sheets are not in it. That is usually where the leakage is.
• You have never searched deliberately. If nobody has ever looked at what is missing, the chances are that something is.

If you already have Power BI and wonder whether you need anything alongside it, read do I need Revenue Intelligence if I already have Power BI?.

From audit to BI: what to build in afterwards

An audit is worth most when its findings stay visible afterwards. Part of that you can build into your own BI environment. Step by step:

1. Pick the three largest findings from the audit, measured in euros.
2. For each finding, define the control question. For example: "which contracts with an indexation clause have the same price this year as last year?"
3. Check whether the data you need is in your BI. Often the contract field is missing. It then has to be recorded in the CRM or ERP first.
4. Build an exception report, not a chart. A list of records that do not add up, with an amount per line. An empty list is the goal.
5. Appoint an owner who clears the list every month, and record what they do with each line they find.
6. Repeat the audit when your process or systems change, because that is when the leaks your new report does not yet know about appear.

The difference between an exception report and a dashboard is large. A dashboard asks the reader to notice something. An exception report tells them what to do.

Where Revenue Intelligence fits

Between a one-off audit and a home-built exception report sits software that runs the checks continuously across systems. That is Revenue Intelligence. Its difference with BI and with an audit is worked out in the pillar of this cluster: Revenue Intelligence vs Business Intelligence. For the specific leak patterns an audit looks at, with what each one costs, see the use cases.

Frequently asked questions

Can I run a revenue audit with my own BI team?

Partly. Your BI team can build the comparisons if the data is available. What is often missing is knowledge of contracts, exceptions and processes, and the time to dig into them. An outside audit mainly brings the questions.

Why does my BI not show revenue leakage?

Because BI shows what has been recorded. Leakage is usually something that has not been recorded, or not compared with what should have happened. Without the expected value next to the actual value, nothing stands out.

Should I build new BI reports after an audit?

For the largest findings, yes, as an exception list with an owner. Do not build a report for every finding. Some leaks are better fixed in the process, so they can no longer occur.

Does a revenue audit need access to my BI?

Not necessarily. Exports or reports you already have are often enough. Many findings come from conversations and from putting a handful of contracts and invoices side by side.