Revenue leakage audit: contracts, billing and the records behind them

How do you run a revenue leakage audit?

Match what the company contracted to deliver against what it delivered and billed, line by line, across several years, then trace each gap to its cause. The audit also shows how deep the contract, billing and usage records go and whether customer contracts limit use of that data, two questions that matter for any data licensing screen.

Leakage usually hides between systems: the signed order form says one thing, the billing tool another, the usage log a third. Finding it means pulling those records side by side, which makes a revenue leakage review one of the best natural views a CFO gets of a company's record base.

Prerequisites

• Read access to the contract repository, billing or ERP system and any usage or delivery logs
• A sample window of at least eight quarters, longer if the contract cycle is multi-year
• A named contact in sales operations, billing and customer success
• Agreement that findings stay inside the company and that only metadata leaves the audit

The five-match audit

1. Contract to order. Does every signed agreement or SOW have a matching order in the billing system, with the same term, price and quantity?
2. Order to usage. For metered or milestone work, does recorded usage or delivery match what was ordered?
3. Usage to invoice. Was everything delivered or consumed actually invoiced, at the contract rate?
4. Invoice to cash. Were invoices collected, credited or written off, and who approved the credit?
5. Renewal to price. Did escalators, renewals and expirations take effect on the dates in the contract?

Run the five matches on a sample of customers across at least three years. Keep a log of every break.

Where leakage tends to appear

What the audit teaches you about the record base

Each match depends on a different system and a different era of data. Record these facts as you go.

The rights question deserves care. Customer agreements may contain confidentiality, data-use or non-assignment terms that limit what the company can license, and the answer varies by contract. This is general information, not legal, tax or financial advice. Confirm with the company's own counsel before acting.

Common mistakes

Illustrative example

Illustrative: a fictional 90-person managed services company runs the five matches on 40 customers over six years. The audit finds escalators that never took effect, scope that was delivered without change orders and credits issued without approvers. It also shows contracts in a repository since the company's first year, billing history in two systems, and a retired ticketing tool whose archive nobody owns. The CFO writes the archive owner into the audit log. If the owner is later interested in licensing, that single line is the start of the inventory.

How to raise licensing with the owner

Lead with the audit, not the pitch. After you present findings, you can mention that the same records are what some AI developers want to license, under strict conditions.

The company fit checker gives a preliminary, non-binding screen, and the who qualifies page lists the baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license and an authorized sponsor.

How the introduction and rewards work

You never export, upload or describe confidential records. Register as a partner, share your referral link or use the referral form, and SourceX qualifies the company, which then completes its own data inventory. Price and terms are agreed before buyers review, and data is delivered only under an executed agreement.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is never deducted from what the company receives. Check your own engagement terms and fee rules first; the fractional CFO playbook covers them.

Who owns each fix?

A finding without an owner repeats next year. Assign each break to a function and set a date to re-test.

• Sales operations: escalators, renewals and discount end dates.
• Billing or finance operations: unbilled usage, invoice rates and credit approvals.
• Delivery or project leads: scope added without a change order.
• Controller: write-off policy and approver evidence.

Re-run the five matches on the same sample after two quarters. A falling break count shows the fixes worked, and the log becomes a dated record of how the company manages its contracts.

When not to raise it

• The contracts mainly bind the company to confidentiality that prohibits any reuse.
• The records are mostly customer personal data without a licensing basis.
• The audit shows records were purged or the systems have no export.
• The data has already been licensed for AI training.
• The sponsor will not consider an exclusive license for an agreed term.

Next step

Add three lines to your audit template: years searchable, systems touched and contract restrictions noted. For a promising client, register as a partner and make the introduction, or have the owner apply at sourcex.si/apply. Related reading: the CFO handover document, the budget assumptions log, the records handoff checklist, the CAS growth guide and the audited financials explainer.