Finding Profit Leakage in Contracts and Rebates: Nine Places Margin Disappears

Why does margin leak in nine small places instead of one big one

Ask a finance director where margin leakage analysis usually starts and most will describe a single dramatic discovery: a mispriced contract, a rebate nobody claimed, a customer on the wrong price list for two years. Those cases exist. They are also not typical.

In our experience, margin more often disappears in nine separate places, each individually below the threshold anyone bothers to investigate. A 0.4% price drift on one customer looks like rounding. Multiplied across a book of accounts, it is a material number nobody has connected because it never sat in one place to be added up.

Margin leakage: Margin leakage is the gap between the margin a contract or price list implies and the margin the business actually realises once invoicing, rebates and credits are accounted for. It is a measurement problem before it is a pricing problem.

The nine-point table below is the audit sequence we walk through with commercial and finance teams. Treat it as a checklist for a first pass, not a definitive taxonomy: most books have a version of all nine, but the size of each varies enormously by business model.

Where does the nine-point margin leakage audit actually look

None of these nine require new data. All nine require joining data that already exists but currently lives in separate systems: ERP, contract documents, rebate spreadsheets and freight invoices.

Why is this a data-joining problem before it is a pricing problem

Every one of the nine leaks above can be described as a pricing failure. Almost none of them are actually caused by bad pricing decisions. They are caused by the agreed price, the invoiced price and the paid price living in three different systems that never get reconciled at line-item level.

A contract sits in a document management system or, more often, an email thread and a PDF. The price list sits in the ERP. Rebate terms sit in a spreadsheet maintained by whoever negotiated the deal. Invoices sit in accounts receivable. A price-to-invoice audit means joining all four, at the SKU and customer level, on a recurring basis rather than as a one-off finance project.

• Contract terms captured as structured data, not just a signed PDF in a shared drive
• Rebate tiers and thresholds tracked against actual volume, updated at least monthly
• Invoice lines matched to the specific contract version active on the invoice date
• A single owner accountable for resolving mismatches, not just reporting them

Most teams trying to solve this manually in spreadsheets eventually look at a dedicated profit leakage finder approach instead, because the joining work is the part that does not scale by hand.

This is also why margin leakage projects stall when they are framed as pricing strategy work. Pricing strategy asks whether the price is right. A margin leakage audit asks whether the price that was agreed is the price that is actually being realised. Those are different questions and need different data.

What does a first pass usually find

It is tempting to assume a nine-point audit surfaces nine roughly equal problems spread evenly across a business. In practice, a first pass usually finds fewer, larger issues rather than many small ones. A pattern we see repeatedly: a distributor with 40,000 SKUs discovers that dead SKUs on legacy price lists and one or two rebate tiers account for most of the identified leakage, while the other seven categories contribute smaller, steadier amounts.

This matters for how you scope the first audit. Do not commit to reconciling all nine categories perfectly before you have any results. Run a first pass across all nine at a coarse level, rank them by estimated size, and go deep on the two or three that matter before refining the rest.

A realistic order of investigation

1. Pull invoice lines against the current active contract or price list for a sample of accounts
2. Cross-check rebate agreements against actual purchase or sales volume for the last completed period
3. Flag any promotional pricing still applying past its stated end date
4. Rank the flagged discrepancies by total value, not by count
5. Assign owners for the top three categories before expanding the scope further

Honest expectation-setting matters here. A first audit that finds one large systemic issue and quietly ignores the smaller categories is not a failure. It is usually the correct prioritisation.

How does a rebate audit differ from a price compliance audit

Contract price compliance asks a simple question at scale: does the invoiced price match the agreed price? Rebate auditing asks a harder question: given actual volume, what should have been claimed or paid, and was it? Rebates are typically tiered, time-bound and conditional, which means the calculation itself is more complex than a flat price comparison.

This is also where the direction of the leak matters. Rebates owed to you by a supplier and never claimed are a direct cash loss. Rebates you owe a customer and never pay expose you to disputes and, eventually, reputational cost when the customer's own audit catches it first. Both need tracking, and they usually sit with different teams, which is part of why nobody joins them up voluntarily.

• Rebate agreements should specify the exact volume metric used for tier calculation, not a loosely worded description
• Claims should be filed against a documented deadline, with a calendar reminder that does not depend on one person remembering
• Both sides of a rebate relationship deserve the same audit rigour: what you are owed and what you owe

How do you get started without rebuilding your commercial systems

None of this requires replacing the ERP, the pricing engine or the rebate tracker. It requires a data layer that sits alongside them and joins contract terms, invoiced amounts and rebate claims often enough to catch drift before it compounds over several quarters.

Teams evaluating whether they have the internal capacity to do this themselves can use a short readiness check to see where the gaps sit, particularly around whether contract terms exist anywhere in structured, queryable form. If they do not, that is usually the first fix, ahead of any pricing or rebate analysis.

Wholesale distribution businesses tend to carry the widest spread across all nine leak categories, simply because of the volume of customer-specific terms and rebate agreements in play at once. Businesses with fewer, larger contracts often find the leakage concentrated in one or two categories, which makes the audit faster but no less worth doing.