What is margin leakage?

Margin leakage is value a business has already agreed or earned, and then loses, because what was agreed, delivered, billed and paid no longer match.

It starts after the price is set. It hides in the hand-offs between teams and systems. And it can be stopped before money moves.

Four records of one transaction: agreed and delivered match in full; billed falls short of what was delivered (not billed); paid runs past what was agreed (overpaid). The gaps between them are margin leakage.

Definition

margin leakage (noun)

The loss of contracted or earned value that occurs when a transaction's agreed terms, delivery evidence, billing and payment do not match. Pricing decides what a business intends to earn; margin leakage is the failure to realise what was already agreed.

Also known as: contract value leakage, value erosion, revenue leakage (sell side), overpayment leakage (buy side).

It rarely shows up as one large loss.

It builds up across thousands of small mismatches.

An outdated rate. A shift invoiced but never worked. A service delivered but never billed. An invoice paid twice. On their own, each looks minor. Across thousands of transactions they add up, and because they fall between systems and teams, no report has a line called ‘leakage’.

The business impact is value you agreed to keep but did not realise: supplier overcharges raise costs, unbilled services reduce earned revenue, and duplicate or unsupported payments take cash out of the business. These gaps can reduce profitability without a change in pricing strategy or anyone acting dishonestly. Checking the agreement, delivery evidence, invoice and payment together makes the difference visible.

1,000 transaction lines · a few mismatches are enough to move margin

The framework

Every transaction leaves four records.

When all four agree, margin lands as planned. When any two disagree, value leaks.

  1. 01

    Agreed

    What you committed to.

    contracts · rate cards · POs · amendments · policies · delegations

  2. 02

    Delivered

    What actually happened.

    receipts · timesheets · rosters · usage · site sign-ins · carrier data

  3. 03

    Billed

    What was invoiced.

    supplier invoices in · customer invoices out · credit notes

  4. 04

    Paid

    What money moved.

    payment runs · cards · account-to-account · bank details

Where they disagree
  • Gap 1 · Supplier side

    Agreed ≠ Billed

    Billed above what was agreed.

    A supplier charges $108 when the contract says $95.

  • Gap 2 · Customer side

    Delivered ≠ Billed

    Delivered but not billed.

    A service is provided, but no customer invoice is raised.

  • Gap 3 · Payment

    Billed ≠ Paid

    Paid twice, early, late or to the wrong place.

    The same invoice is paid in two payment runs.

Margin leakage is not one problem. It is three gaps between four records.

The three types

Where margin leakage happens.

Each type is defined by which records disagree.

Supplier leakage

Paying suppliers more than the contract, rate card or delivered work supports.

  • Rates above contract
  • Tiers, discounts and rebates not applied
  • Indexation above the agreed cap
  • Charges the contract never allowed
  • Hours, shifts or quantities billed but not delivered
  • Variations paid without approval
Explore supplier leakage

Revenue leakage

Delivering work, services or usage that is never billed, or billed below what the contract says.

  • Delivered, never billed
  • Supplier costs not passed through
  • Contracted increases not applied
  • Discounts and free periods that outlive their terms
  • Lines where cost exceeds revenue
  • Ceased services still incurring cost
Explore revenue leakage

Payment leakage

Money leaving the business that should not, or not in the way it should.

  • Duplicate and near-duplicate payments
  • Payments to changed or fraudulent bank details
  • Payments outside delegated authority
  • Payments with no matching invoice or evidence
  • Off-policy card spend
  • Payment terms breached (missed early-payment discounts, statutory deadlines)
Explore payment leakage

Why it persists

No one owns the gap.

Each record lives with a different team, in a different system, on a different timetable.

Procurement and LegalAgreed
Operations and site teamsDelivered
Accounts payable and billingBilled
TreasuryPaid

At every hand-off between these teams, nobody is responsible for checking that the records still match.

  • Contract terms sit in PDFs, not in the systems that pay and bill.
  • Contract data is typically spread across about two dozen systems.1
  • Rate cards change; the systems that check invoices often don't.
  • Proof of delivery sits outside finance: on site, in rosters, in carrier and usage feeds.
  • Checks are sampled, so most lines are never tested.
  • Reconciliation happens at month-end or audit, after the money has moved.

The size of the problem

Most organisations lose a meaningful share of contracted value. Few can say how much.

  • Best performers: about 3%
  • Average: 8.6%
  • Worst performers: more than 20%
Value erosion across contracts, World Commerce & Contracting with Deloitte, 2023, n = 1,236 organisations.2
A$166.8m

lost by Australians to payment redirection in 2025, up 9.3% on the year before.3

Published figures measure different things (contract value, revenue, spend) and are mostly self-reported. The only number that matters is yours, measured line by line on your own transactions.

Get your leakage baseline

Timing is the control

Recovery finds the money later. Prevention keeps it.

Conceptual: the value you can still keep or recover is highest at the transaction and approval, then falls once the payment run has passed, through month-end to an audit months later. Prevention happens at approval.

Recovery audit

After payment · sampled · months later · fees on what is recovered · partial.

Continuous detection

After payment · every transaction · days later · still a recovery.

Prevention

Before payment · every transaction · at approval · nothing to recover.

Where are you?

Five levels of margin leakage control.

Signs you're here

Periodic samples; findings arrive months later.

Next move

Test every line, not a sample.

How margin leakage is prevented.

Your agreements are the benchmark.

Every check traces to a clause, rate card or approval, not a generic rule.

Every line, not a sample.

Leakage hides in the lines no one tests.

Before money moves.

The cheapest dollar to recover is the one never paid.

Evidence, not assertion.

Delivery is proven by receipts, rosters, sign-ins and usage, not by the invoice.

People decide.

Findings arrive with the clause, the amount and the evidence; your team approves, holds or corrects.

Prove it.

Leakage found, prevented and recovered, reported in dollars to the CFO and board.

RedOwl

Find it. Prevent it. Prove it.

01

Find.

Twelve months of your own transactions, reconciled against your contracts, rate cards and evidence. A baseline in days.

02

Prevent.

Every invoice, payment and card transaction checked before approval. Each finding comes with the clause, the amount and a recommended action.

03

Prove.

Leakage found, prevented and recovered, reported to the CFO and board.

FAQ

What is margin leakage?

Margin leakage is value a business has already agreed or earned, and then loses, because what was agreed, delivered, billed and paid no longer match.

Is pricing a type of margin leakage?

No. Setting prices and discounts is a commercial decision about what you intend to earn. Margin leakage is what happens after the price is agreed: being billed above it, failing to bill to it, or paying outside it.

How is margin leakage different from fraud?

Fraud is deliberate deception. Margin leakage is lost value, and most of it happens in good faith: an outdated rate card, a missed rebate, a delivered service never billed. Fraud is one cause of payment leakage, but stopping fraud alone leaves most leakage untouched.

What are the three types of margin leakage?

Supplier leakage (paying more than agreed or delivered), revenue leakage (delivering or incurring cost without billing as agreed) and payment leakage (money leaving that shouldn't, or not as approved).

Where does margin leakage happen?

Wherever records pass between teams or systems: between contracts and supplier invoices, between delivery records and customer billing, and between approvals and payment runs.

How big is margin leakage?

World Commerce & Contracting and Deloitte found organisations lose an average of 8.6% of contract value, from about 3% for the best performers to more than 20% for the worst. Your own figure depends on your contracts and controls, and is best measured on your transactions.

How is margin leakage measured?

By comparing each transaction with the agreement and evidence behind it, adding up the differences, and stating the result against a clear base: spend, revenue or contract value.

Who owns margin leakage?

Ultimately the Office of the CFO, because leakage crosses procurement, operations, accounts payable, billing and treasury. That shared ownership is why it persists.

How do you stop margin leakage?

By checking every transaction against its agreement and evidence before money moves, rather than auditing a sample afterwards. RedOwl connects contracts, delivery evidence, supplier costs, billing and payments, and flags mismatches before approval or payment.

How quickly can you find it?

A leakage baseline on twelve months of your own transactions can be produced in days. The same checks then run on every new transaction.

Sources

  1. World Commerce & Contracting, Contract Management: An Overlooked Driver of Business Agility and Financial Performance, August 2025. info.worldcc.com
  2. World Commerce & Contracting with Deloitte, The ROI of Contracting Excellence, 2023 (n = 1,236). www.deloitte.com
  3. ACCC, Targeting Scams report, March 2026. www.accc.gov.au

Worked examples are illustrative. Figures describe the sources cited and are not RedOwl customer results unless stated.

Last updated:

How much value is leaking?

Find the gap before it lands.

Start with twelve months of your own transactions. See your baseline in days, then turn it into controls that run every day.