Revenue Leakage: The Cost of Handoffs Nobody Owns

One of the largest consumer goods companies in the world loses revenue every month through a mechanism nobody in the company would describe as a problem.

They agree a price with a retailer. They update it in their system. The retailer does not update it in theirs. The invoice goes out at the agreed price and the payment arrives short. The difference is small per transaction and the volume is enormous.

The finance team sees it as a receivables discrepancy. The commercial team sees it as a pricing sync issue. The IT team sees it as an integration gap. Each is correct within their frame, and the loss sits between the frames where no team's dashboard reports it.

This is the shape of most enterprise revenue leakage. It rarely comes from one large failure. It comes from small discrepancies at handoffs, repeated at volume, in places where the metric that would reveal them belongs to nobody.

Key takeaways

• Revenue leakage concentrates at boundaries between systems, teams and counterparties.
• Individually the amounts are too small to trigger investigation, which is what allows them to persist.
• Aggregate reporting hides leakage by design, since the variance is absorbed within a larger number.
• The compensating work is often more expensive than the leakage itself.
• Leakage that has been running for years tends to be staffed rather than fixed.
• Finding it requires asking the people who reconcile, not reading the reports they produce.

Why leakage forms at boundaries

Each side is internally consistent

Two systems that disagree are usually both correct according to their own rules. A price updated on the fifteenth in one system and on the twentieth in another is not an error in either. The mismatch exists only in the space between them, and neither system is instrumented to detect it.

No metric spans the gap

Organizations measure what functions own. Finance measures collection and days sales outstanding. Commercial measures pricing and volume. Operations measures fulfilment. A loss occurring in the handoff between them appears as a small degradation in each metric and as a cause in none.

The consequence is that the aggregate number can look acceptable while a specific mechanism drains steadily underneath it.

The individual amount is below the investigation threshold

Every organization has an implicit threshold below which a discrepancy is written off rather than pursued, because pursuing it costs more than it recovers. That threshold is sensible per transaction and irrational in aggregate.

A discrepancy of a few hundred units, occurring on a percentage of transactions, across a volume in the millions, produces a material annual figure that no single instance ever justifies investigating.

Compensation forms and then becomes normal

Someone starts reconciling. A spreadsheet appears. The reconciliation stabilizes into a weekly routine, and after a while it is simply part of the job.

At that point the leakage has been converted into labor, which is harder to see than a financial variance. The variance shrinks because someone is catching it. The cost moved rather than disappeared, and it moved into a line nobody attributes to the original cause.

Where it accumulates

The last row is worth attention in any organization operating across markets. Differences between countries are frequently accepted as inherent to operating internationally, when a portion of them is a process divergence that could be closed.

The compensation is usually the larger cost

There is a counterintuitive point here that changes how these problems should be prioritized.

By the time an organization notices a leakage mechanism, someone has usually been compensating for it for years. The recovered revenue from fixing the root cause may be modest, because the compensation is catching most of it.

The larger cost is the compensation. Hours per week spent reconciling, comparing line by line, chasing discrepancies, rerunning failed steps. That work scales with volume, occupies experienced people, and produces nothing beyond restoring what should have been correct.

Which means the business case for fixing a leakage mechanism is often built on the wrong number. The recovered revenue is the visible benefit. The released capacity is usually the bigger one, and it appears in a different budget line.

Leakage and its shadow

Two costs, one cause

Fixing the cause addresses both. Measuring only the first understates the case for fixing it.

Why reporting cannot find it

Three structural reasons.

Aggregation absorbs it. A monthly figure that combines thousands of transactions cannot distinguish a systematic small loss from normal variance. The signal exists at the transaction level and the reporting exists at the period level.

System data records the outcome, not the mechanism. A system knows a payment arrived short. It does not know that the cause was a price update timing difference with a specific counterparty, because that fact exists in the difference between two systems rather than in either one.

The people who know are not the people writing reports. The analyst who reconciles two payment providers every week could describe the mechanism in detail. Nothing in the reporting chain asks them.

That third reason is the practical one. The information is not missing from the organization. It is missing from the channel that would surface it to someone able to fix it.

How to find it

Start where two things meet

Leakage concentrates at boundaries, so the search should too. List every point where a transaction crosses between systems, between teams, or between the organization and a counterparty. Those are the candidate sites.

Ask about reconciliation, not about losses

Nobody will describe their work as revenue leakage. They will readily describe what they reconcile, how often, how long it takes, and what they find when they do.

The question that works: what do you check every week that you wish you did not have to check.

Quantify the compensation as well as the loss

For each mechanism found, record both the financial variance and the hours spent catching it. The second is usually easier to establish and frequently larger.

Compare across markets

If the same process runs in several countries and one takes materially longer or produces more discrepancies, the difference is a mechanism. Comparison converts a local complaint into a quantified gap with a target.

Trace to a cause that can be owned

A finding without a cause becomes a recurring reconciliation. The disposition requires knowing which system, policy or counterparty relationship produces the mismatch, and who can change it.

Where Horizon fits

Horizon is an AI-powered continuous discovery platform. Its relevance here is that leakage mechanisms are describable by the people who compensate for them and are invisible to the reporting those people feed.

Discovery Cycles run AI-led interviews across the roles that operate a process, asking about exceptions, reconciliation and the work that repeats. The Insights Dashboard quantifies the time impact per mechanism and groups findings by process and cause, which is what turns several teams' separate reconciliations into one traceable root cause.

PedidosYa, the leading food delivery and quick commerce platform in Latin America operating across 15 markets, shows what the layer looks like once it is quantified. A focused pilot across Rider Payments and Partner Payments produced 31 findings from 14 or more asynchronous interviews over three months, without blocking a calendar slot.

Several of them are leakage mechanisms with their compensation attached. Partner billing control required 4 to 5 hours per week cross-referencing three data sources in a spreadsheet and verifying in a back-office tool, covering 25,000 partners with around 150 weekly discrepancies. Manual reconciliation between two systems in Bolivia generated over 1,000 discrepancies per week and consumed roughly two hours of weekly analysis against about 40 minutes in other markets, driven by a visualization error that forced line-by-line comparison. Payment report downloads from one provider consumed around 40 hours per month, partly due to download failures. Rider wallet adjustments required 3 to 4 hours per week of manual retries affecting roughly 2,400 riders weekly.

The pattern across those four is consistent. In each case the discrepancy is being caught, which is why it does not appear as a financial loss, and the catching consumes hours that appear in no report about the process.

PedidosYa has since extended discovery to Tax, Collections and cross-market benchmarking, running it as a continuous program.

That is one engagement under specific conditions rather than a projection for any organization. What generalizes is where the effort was found: at the boundaries, in the compensation, described by the people doing it.

Diagnostic checklist

1. Have you listed every point where transactions cross systems, teams or counterparties?
2. For each one, do you know whether anyone reconciles it manually?
3. Do you know how many hours per week that reconciliation consumes?
4. Do you know the discrepancy rate, not only the net variance?
5. Have you compared the same process across markets?
6. For each mechanism, do you know the root cause and who owns it?
7. Have you quantified the compensation cost alongside the financial loss?
8. Is there anyone whose metric would improve if this were fixed?
9. What is the implicit threshold below which discrepancies are written off, and what is its annual aggregate?

Question 8 is the one that determines whether a fix will be funded. Mechanisms with no owner tend to stay.

FAQ

What is revenue leakage?

Revenue that an organization has earned and does not collect, or pays out incorrectly, through operational rather than commercial causes. It typically originates at boundaries between systems, teams or counterparties, where a discrepancy is too small per transaction to investigate and material in aggregate.

What causes revenue leakage in enterprises?

Most commonly, mismatches at handoffs: pricing not synchronized between an organization and a counterparty, contract terms negotiated in one system and billed from another, payment reconciliation across multiple providers, manual rebate calculation, and adjustments issued outside the standard flow. The individual amounts sit below the threshold that would trigger investigation.

Why does financial reporting miss revenue leakage?

Because reporting aggregates. A systematic small loss across thousands of transactions is indistinguishable from normal variance at the period level, and the signal exists at the transaction level. Reporting also records outcomes rather than mechanisms, so it can show a payment arrived short without showing why.

How do you find revenue leakage?

Start at the boundaries where transactions cross systems, teams or counterparties, and ask the people who work there what they reconcile and how often. Quantify both the financial variance and the hours spent catching it. Comparing the same process across markets is one of the fastest ways to surface a mechanism.

Is fixing revenue leakage worth it if someone is already catching it?

Usually yes, and for a different reason than expected. When compensation exists, the recovered revenue may be modest because most of it is already being caught. The larger benefit is the released capacity, which scales with volume and typically occupies experienced people on work that produces nothing beyond restoring correctness.

The expensive problems are the quiet ones

The failures that get attention are the ones that break something visible. The ones that cost most tend to run for years without breaking anything, because someone quietly absorbed them into their week.

Those mechanisms sit at the boundaries between the things an organization measures, which is exactly where nobody is looking.

See it. Fix it. Win it.

See Horizon in action.