2–5% Contract Leakage: The EBITDA Line Item Hiding in Plain Sight

Contract leakage — the gap between what companies should pay their suppliers under negotiated contracts and what they actually pay — runs at 2-5% of total indirect spend across mid-market companies. On a $100M revenue portco with $20M in addressable indirect spend, that is $400K-$1M leaking out of EBITDA every year. The leakage is invisible in most P&Ls because it spreads across hundreds of transactions and thousands of line items. AI operating layers surface the leakage, capture it systematically, and convert it into recovered margin without requiring additional procurement headcount. For PE operating partners scanning for overlooked EBITDA levers, this is one of the largest and most persistent hiding-in-plain-sight opportunities in the portfolio.

The Sources of Contract Leakage

Contract leakage is not a single phenomenon. It emerges from multiple overlapping sources.

Rebate and volume-discount non-capture. Suppliers offer tiered pricing or rebate structures tied to volume, timing, or category. Companies frequently fail to execute the actions required to trigger these — hitting volume thresholds, submitting rebate documentation, completing quarterly reviews — and lose the negotiated savings.

Pricing drift. Contract pricing includes provisions for rate updates, CPI escalators, and market-based adjustments. Suppliers apply these strictly; buyers rarely verify that applied rates match contractual language. Over time, pricing drifts above what contracts actually allow.

Service-level credit non-capture. Contracts specify service-level agreements with financial credits or remedies for underperformance. Underperformance happens; credits rarely get claimed because nobody is tracking the metrics consistently against the contract terms.

Off-contract spend. Employees buy from non-preferred suppliers or off-contract pricing structures even when preferred agreements exist. The spend that leaks off contract typically runs at 15-30% higher effective pricing than the on-contract alternative.

Favorable-terms non-exercise. Contracts include provisions like early-payment discounts, free services bundled with primary purchases, or exit provisions that can be exercised to secure renegotiated terms. Awareness of these provisions decays over time and the provisions get left on the table.

Audit and invoice discrepancies. Supplier invoices frequently contain errors — duplicate charges, incorrect unit pricing, mis-applied taxes, phantom line items. In the absence of systematic invoice audit, these errors accumulate without being caught.

Each category individually is a small fraction of total spend. Collectively, the leakage is material.

Why the Leakage Persists

Contract leakage persists because capturing it requires continuous, transaction-level analysis across the entire spend base. That analysis has historically required procurement labor that mid-market companies cannot justify economically — the analyst time needed to track rebate triggers, verify pricing, audit invoices, and enforce contract compliance exceeds the savings produced on any single item.

The same labor-economics constraint covered in the long tail of procurement is found money — AI just makes it economical applies here. The unit economics of manual leakage capture have never supported the investment; the cumulative economics of leakage capture have always justified it. The gap between the unit and the cumulative is exactly the gap that AI operating layers close.

The Operating-Layer Response

An AI operating layer against contract leakage works continuously across the full spend base. It ingests contracts and extracts the operative terms, ingests invoices and reconciles against expected pricing, ingests volume and activity data and tracks rebate and tier qualifications, monitors SLA metrics against contractual commitments, and identifies off-contract spend patterns.

When discrepancies or opportunities surface, the operating layer generates action items for the procurement or finance team. Invoice errors get flagged for supplier correction. Rebate thresholds get tracked proactively so action is taken before deadlines pass. SLA credits get computed and claimed. Off-contract spend gets redirected via workflow routing. Unfavorable pricing drift gets surfaced for renegotiation.

The capture rate on identified leakage is a function of how well the workflow is integrated with procurement and finance operations. Mature deployments typically recover 70-90% of identified leakage within 12-18 months.

The Math on a Typical Mid-Market Portco

Consider a $120M-revenue portco with $25M in addressable indirect spend. Contract leakage of 3% represents $750K annually. Operating-layer deployment identifies roughly 95% of the leakage and captures 80% of what is identified, producing $570K in recovered annual savings.

That is direct EBITDA expansion, recurring year-over-year, on a deployment that typically costs a fraction of the first-year savings to operate. Across a PE portfolio of 10 comparable portcos, the annual leakage capture runs $5-8M — a fund-level EBITDA contribution from a single workflow category.

These economics are conservative. Portcos with more complex spend bases, higher-volume transactional patterns, or heavier reliance on percentage-of-volume supplier agreements typically capture larger absolute savings. This is the same financial-impact pattern covered in the EBITDA case for AI, applied to a highly specific savings category.

The Compliance and Risk Dimension

Contract leakage is not purely an economic issue. It is also a risk and governance issue. Missed rebate captures and unclaimed SLA credits erode the commercial terms negotiated at signing. Pricing drift undermines budget predictability. Off-contract spend creates supplier-relationship risk and can violate procurement policy commitments made to lenders or investors.

Operating-layer deployment against contract leakage strengthens the company's commercial governance posture in ways that matter during audits, lender reviews, and exit diligence. Buyers notice when a portco demonstrates rigorous contract management because it signals operational discipline that typically extends to other functions as well.

The Buyer for This Deployment

The natural internal buyer for contract-leakage deployment is the CFO, with procurement and finance operations as execution partners. The value accrues to the financial line, the deployment requires finance-adjacent data integration, and the CFO has the authority to redirect any resulting savings.

Operating partners driving cross-portfolio deployment should be engaging CFOs specifically on this workflow and sequencing the deployment across portcos on a portfolio schedule. The same fund-level scaling pattern covered in why your CFO's outsourced close is the highest-ROI AI swap in your portfolio applies — CFOs are the correct entry point for any workflow where the savings hit the financial line.

The Deployment Sequence

A typical deployment runs in three phases.

Phase one ingests the contract portfolio and extracts operative terms. Mid-market companies often discover their contract inventory is less organized than they believed; this phase produces the structured contract data that everything downstream depends on.

Phase two integrates spend and activity data from the ERP, AP system, and operational platforms. The operating layer begins reconciling actual spend against contractual expectations and producing the first wave of leakage findings.

Phase three formalizes the leakage-capture workflow: how findings flow to procurement or finance for action, how supplier disputes are handled, how recovery is tracked, how reporting rolls up to the CFO and the operating partner. This phase converts findings into captured savings.

Realistic timelines run six to nine months to full operating maturity, with first meaningful savings typically showing up in month three or four.

Why This Gets Deprioritized

Contract-leakage deployment often gets deprioritized against more visible AI initiatives. The deployment is less glamorous than customer-facing AI or strategic analytics, and the category expertise required to execute it well is not universally distributed among operations teams.

Operating partners who recognize the scale of the available savings push through the deprioritization. The ROI math is unambiguous, and the savings compound across every subsequent year of the hold period. Few other workflow categories produce similar recurring EBITDA impact at similar deployment investment.

Hiding in Plain Sight

The point of "hiding in plain sight" is that the leakage is visible to anyone willing to look, but almost nobody is looking systematically. The transactions exist in the AP system. The contracts exist in the repository. The gaps exist in the spread. Nothing is hidden technically — but the volume of transactions and the complexity of the reconciliation exceeds what manual labor can economically analyze.

Operating layers close the gap between what is visible in principle and what is captured in practice. Every PE-backed portco has 2-5% leakage in its indirect spend right now. The deployment to capture it exists, the economics support it, and the savings flow directly to EBITDA for the remainder of the hold period. The line item is waiting. The question is which operators act on it first.