Where margin drift shows up before a PE sponsor review

Executive Summary

Before a PE sponsor review, the real risk is not a bad number. It is a number you cannot explain on the spot, in a room where the sponsor's team has already built their own version of it. Vendor invoices drift away from contract terms continuously: a surcharge that outlives the fuel condition that justified it, a rebate tier crossed and never invoiced, a staffing rate that rolled over without the contract's escalation cap being checked.

None of these show up as an error in the general ledger.

They show up as margin that moved for a reason nobody wrote down.

The mechanism is simple: AP pays against the purchase order and the invoice total, not against the full text of the contract. Nobody in the payment path checks a surcharge's expiration date or a volume tier's rebate trigger, so drift accumulates quietly until someone outside the company goes looking for it.

What changes it is running the reconciliation before the sponsor's team does: match a sample of service vendor invoices back to their contracts, quantify what does not match, and have the explanation ready before the question is asked.

1. What should you check before a PE sponsor review?

Check every service vendor category where the invoice depends on a contract clause rather than a fixed price: freight surcharges, labor rate escalators, MRO rate cards, rebate and volume tiers, and not-to-exceed caps. For each, pull a sample of recent invoices and match them line by line against the current signed contract, not the contract you remember signing. The gap between the two is what a sponsor's diligence team will find on its own if you do not find it.

Start with the categories that move independently of volume: a surcharge, an escalator, or a minimum charge does not scale with units shipped or hours billed, so it is the easiest place for a rate to go stale without anyone noticing on the P&L.

Pull twelve months of invoices for each category and lay them against the contract's actual rate table, not the summary someone wrote into a spreadsheet at signing. Contracts amend, and the amendment often lives in an email thread, not in the ERP.

Where the invoice and the contract disagree, write down the dollar difference and the specific clause. A sponsor's team will ask for the mechanism, not just the total, and "the surcharge kept charging after the fuel index dropped" is a stronger answer than a single unexplained number.

2. Why does a sponsor's team find drift that internal AP never flagged?

A sponsor's diligence team builds a spend cube from raw invoice data and compares it against contract terms independently of how AP processed the invoice. Internal AP review checks the invoice against the purchase order and the receipt; it does not test whether a surcharge's trigger condition still applies or whether a rebate tier was crossed. The two checks look at different documents, so a clean AP close and a clean contract-compliance result are not the same thing.

Three-way matching confirms that the invoice, the purchase order, and the goods receipt agree with each other. None of those three documents contains the rebate clause or the surcharge's expiration condition; that language sits in the contract, usually a PDF outside the ERP.

A diligence team works from the contract first. They pull the vendor's rate card, the volume tier schedule, and the not-to-exceed cap, then rebuild what the invoice should have charged. Any gap between that rebuild and what was actually paid becomes a diligence finding, whether or not AP ever saw a problem.

This is why a clean AP close is not protection on its own. It confirms the invoice matched the paperwork in front of AP. It says nothing about whether that paperwork still matched the contract.

3. Which vendor categories deserve a contract check first?

Prioritize categories where the invoice depends on a variable clause rather than a flat rate: freight and 3PL surcharges, contract labor rate escalators and overtime rules, MRO rate cards and volume rebates, and IT or professional services not-to-exceed caps. Each has a contract term that can drift out of sync with the invoice without triggering any automated control, because the control that exists checks the purchase order, not the clause.

A category-by-category pass keeps the review manageable and lets each finding trace back to a specific clause rather than a vague sense that something looks off.

Treat each category on its own terms rather than ranking them against each other: the mechanism that causes drift in freight is different from the mechanism in staffing, and the fix looks different in each case.

• Freight and 3PL: Fuel surcharges, accessorial fees, and lane rates are set against an index or a rate card that changes on its own schedule, separate from the invoice cycle.
• Contract labor and staffing: Bill rates roll over on contract anniversaries and shift differentials apply under specific conditions; both can be misapplied without anyone re-reading the agreement.
• MRO and maintenance: Rate cards and volume-based rebates require the buyer to track cumulative spend against a tier, something the ERP was not built to watch.
• IT and professional services: Not-to-exceed caps and statement-of-work scope limits get invoiced past their ceiling when a project extends past its original term.

4. How far back should the review go?

Reach back far enough to cover the window a sponsor typically builds their spend cube around: 12 to 18 months of historical spend, across ValueXPA diagnostics. A shorter window misses drift that compounds slowly, like a surcharge that started correctly and was never revisited after the condition behind it changed. A longer window adds cost without adding much explanatory value once the pattern is already visible.

A single month of invoices tells you whether a vendor billed correctly that month. It does not tell you whether a rate has been wrong since a contract renewed eight months ago and has been compounding quietly since.

Twelve to eighteen months is long enough to catch a full seasonal cycle in freight and to cover at least one contract anniversary for most staffing and services agreements, where escalators and rate resets tend to sit.

Going back further adds review cost without changing the finding much: once a pattern shows up in twelve months, more history tends to confirm it rather than reveal a new one.

5. Should you fix the contract or fix the invoice first?

Fix the invoice first, because it carries the immediate cash impact and is the easier conversation with the sponsor: a credit memo or a corrected rate going forward is a concrete, closed item. Fix the contract language only where the ambiguity caused the drift in the first place, such as an undefined trigger condition for a surcharge. A sponsor's team wants to see both a recovered dollar amount and a control that prevents the same gap from reopening after close.

An invoice-level fix is fast and countable: you know the credit memo amount, and you can show it as recovered before the deal closes. That is the number a sponsor's team can put directly into their model.

A contract-level fix takes longer and often requires the vendor's agreement, so it rarely finishes before a review deadline. Flag it as a known issue with a remediation plan rather than trying to force a renegotiation on the diligence clock.

Keep the two separate in how you present them: recovered dollars are a fact, a planned contract amendment is a commitment. Blending them into one number invites the sponsor's team to ask which part is real.

6. How do you present the finding without looking like the problem is bigger than it is?

Separate the total dollar variance into its components: input cost movement that is legitimate, and drift that is not. A gross margin bridge that shows both, with the non-compliant portion isolated and sourced back to a specific clause, reads as control rather than surprise. A single blended number invites the sponsor's team to assume the worst about the rest of the spend base they have not yet reviewed.

A sponsor's team is trying to answer one question: is this a company where margin moves for reasons management understands, or one where it moves and nobody notices until someone from outside asks. The presentation answers that question as much as the dollar figure does.

Show the bridge from last year's margin to this year's, with each driver labeled: volume, price, input cost, and contract non-compliance as its own line. The last one should read small relative to the others if the review has already run, which is the point of running it early.

Bring the underlying invoice-to-contract matches as backup, not as the headline. The headline is the bridge and the remediation plan; the detail is there if someone asks how a number was built.

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

How long does a pre-sponsor-review check take?

A prioritized review of service vendor invoices against contract terms typically delivers a roadmap in 2 to 4 weeks, across ValueXPA diagnostics. That is fast enough to run ahead of most sponsor timelines if started as soon as a process begins.

Does the sponsor's diligence team use the same method as an internal AP review?

No. AP review checks the invoice against the purchase order and the goods receipt. A diligence team rebuilds what the invoice should have charged directly from the contract's rate card and rebate terms, independent of how AP processed it.

Who keeps the recovered dollars from a pre-review check?

The company does. A fixed-scope engagement is not contingency-priced, so the client retains 100% of any recoveries identified, unlike traditional recovery audit firms that charge 25% to 50% of recoveries.

Can this replace the quality of earnings review?

No. A quality of earnings review tests the accounting; a contract-compliance check tests whether vendor invoices matched the contracts behind them. They answer different questions and a sponsor's team typically wants both addressed separately.

What if we do not have time before the review starts?

Start with the categories most likely to carry variable clauses, freight and contract labor, since a single invoice error there can carry a larger dollar impact than in a flat-rate category. A partial review with a stated scope is more credible than no review at all.

Does this apply to an add-on acquisition, not just a platform sale?

Yes. An add-on brings its own vendor contracts, and those often go unreviewed until they are consolidated with the platform's. The same invoice-to-contract check applies before and after the deal closes.

What counts as a finding versus normal cost inflation?

Cost inflation is a rate that changed and was invoiced correctly under the new rate. A finding is a rate, surcharge, or rebate that the invoice did not apply correctly under the contract actually in force. Separating the two is the point of the bridge.

Is this only relevant to companies above a certain size?

The method applies broadly, but ValueXPA's diagnostic is built for manufacturers and distributors above $100M in revenue, where service vendor spend and contract complexity are large enough to make a structured review worth the time it takes.