Leakage Lives Between Two Systems That Were Never Asked to Agree
Here is the part that surprises people. Revenue leakage is not usually caused by a mistake. It is caused by two systems that are each behaving exactly as designed. The operational system says a job is complete because it is. The ledger says no invoice exists because none was created. Neither one has lied to you. The money is simply in the space between them.
That seam has no owner, because owning it means opening two screens every day and comparing them by hand. Nobody does that, and nobody should. So the gap persists until an owner notices a receivable balance that does not match their gut, and then spends a weekend reconciling by eye.
There is a reason the advice you keep finding does not help. Most "ten ways your business leaks money" content is about the cost side: subscription creep, unused licenses, vendor overbilling. Those leaks are real. They are also the cheap ones. Revenue you earned and never billed is a different order of magnitude, because it is gross revenue with no offsetting cost. You already paid the technician, the part, and the fuel.
Enterprise revenue assurance has been a discipline for decades in telecom and utilities, where billing systems and usage records have needed reconciling since the first meter reading. The vocabulary does not transfer to a twenty-truck plumbing company or a two-bay shop. The mechanism does.
What We Actually Find, Over and Over
These are not hypothetical. They are the same six patterns across every service business we reconcile.
Job Completed, No Invoice
Most common by far
A Real Example
A technician completes a three-hour service call at 4:40 PM on Friday and marks the work order complete. The office intended to invoice it Monday. Monday was busy.
What the Agent Sees
Deterministic. Job reference is a hard key. There is no ambiguity to resolve.
Typical Recovery
Fully recoverable, and the easiest to catch once somebody is looking.
Why Nobody Notices
The operational system is satisfied. The ledger is satisfied. Only the relationship between them is broken, and no single screen shows it.
The yearly figure and the example above are illustrative, based on the default rates in the model below and a sample job, not measured results or client data.
One Nightly Scan, Five Stages
Follow a single reconciliation run from candidate capture to published leak queue. Every stage is deterministic, evidence-backed, and human-gated at the decision.
Terminal Job Captured
What Happens
At 9:00 PM the reconciliation pass reads every job that reached a terminal state in the last twenty-four hours. Each one becomes a candidate with its job number, customer, vehicle or address, completion timestamp, and total value.
Scan Record
Sample record and figures for illustration only, not client data.
Price the Revenue You Already Earned
Set leakage rates per category and see the annual exposure stack up. Defaults are drawn from patterns we see across service businesses. Nothing is submitted, and no contact information is required.
The share of detected leakage that a business ultimately chooses to bill and successfully collects.
Illustrative estimate from the inputs on the left. Your own numbers will differ; this is not a measured result.
This Is a Set Difference, Not a Prediction
There is a version of this page where we tell you a sophisticated model learns your revenue patterns and surfaces anomalies. It would sound better. It would also be dishonest about how the work actually gets done.
The core of leakage detection is a set difference. One set is the work that reached a terminal state operationally. The other set is the work that got billed. The difference between them is the leak. No model is required to compute a set difference, and applying one where a join would do is how you end up with confident, unexplainable findings that nobody trusts.
Where reasoning genuinely earns its place is narrower and more interesting. Partial billing, where a job was billed in two pieces across different weeks. Split jobs, where one operational record spawned two invoices and a credit. Substituted parts with no matching part number. Those are the cases where a hard key is missing and judgment is needed, and that is precisely where a model is useful, provided it reports its confidence and its evidence rather than a bare assertion.
That distinction matters to you as a buyer. A vendor who leads with the model is selling you a story. A vendor who leads with the reconciliation and mentions the model second is describing a system you can audit.
Deterministic First
Hard keys, then composite matching. A finding is only accepted automatically above a confidence threshold, and every acceptance is reversible.
Evidence With Every Finding
Both sides of the comparison are attached to the finding, so a person verifies in seconds instead of trusting a number.
Reversible by Design
Turning the reconciliation off leaves both systems exactly as they were. Nothing was written that has to be undone.
Finding Is Automated. Billing Is Not.
Straight Answers
Let Us Run the First Scan
In thirty minutes we will look at your operational system and your ledger together, walk the six categories, and tell you which one is most likely costing you this month. You leave with the finding whether or not you hire us.
