What to ask procurement before a PE sponsor review

Executive Summary

A sponsor review tests whether your numbers hold up under someone else's scrutiny, not your own. The mechanism that most often breaks that test is not the P&L itself. It is the layer underneath it: vendor contracts that say one thing and invoices that charge another, sitting unreconciled because no one owns that reconciliation day to day.

Procurement owns the contracts. Finance owns the invoices. Between the two, nobody is checking that a rate card, a rebate tier, or a not-to-exceed cap is still being honored on the invoice that just got paid. That gap shows up as unexplained variance in gross margin, and an unexplained variance is exactly what a sponsor's diligence team is trained to chase.

What changes this before a review is asking procurement five specific questions now, not during diligence. Each question below maps to a document a diligence team will ask for anyway. Answering it first means you control the narrative instead of reacting to theirs.

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

Check whether every active service vendor contract has a current rate card, whether invoices are being matched against it, and whether anyone can produce that match on request. Also check rebate tracking, contract expiration dates, and whether multiple entities are paying different rates to the same vendor. These five items are what a diligence team tests first, and they are the items procurement can answer today if asked directly.

A sponsor review is not an audit of intent. It is a test of documentation: can you show, on request, that the price on the invoice is the price in the contract. Finance teams can often answer that question in aggregate, at the P&L level, but not vendor by vendor.

Procurement is the function most likely to have the underlying documents, because they negotiated the contracts. But procurement is rarely asked to reconcile those documents against what accounts payable actually paid. That reconciliation is a different skill and a different system.

Start by asking procurement for a simple inventory: which service vendor contracts are active, which have rate cards attached, and which have not been reviewed since they were signed. That inventory alone tells you where the exposure sits before a sponsor's advisor finds it independently.

2. Which contracts should procurement pull first?

Pull contracts for freight and 3PL, contract labor and staffing, maintenance and repair, and any vendor with a volume tier or rebate clause. These categories carry complex pricing logic and thin automated enforcement, because their terms live in a PDF outside the ERP rather than in a system that checks each invoice against the clause.

Freight contracts carry fuel surcharge schedules, accessorial tables and minimum charges that change by lane and by carrier. Contract labor agreements carry bill rates, overtime multipliers and not-to-exceed caps. Both are easy to negotiate well and easy to lose track of after signing.

Ask procurement to pull, at minimum, every contract with a rebate clause, a volume tier, or an NTE cap. These are terms that can drift silently, because the invoice looks ordinary against the wrong reference table and nobody catches it without pulling the contract back out.

A post-acquisition environment compounds this. If the company has made acquisitions, ask specifically whether acquired entities' vendor contracts were ever consolidated or even inventoried centrally. See post-acquisition vendor contract consolidation for what that process should look like.

3. How do you know if invoices match contract terms?

Ask procurement or AP to produce, for a sample of ten vendors, the contract clause next to the last three invoices paid against it. If that comparison does not already exist as a routine, it does not exist at all, and a diligence team will find that out by asking the same question with less patience. The test is whether the comparison can be produced, not whether it has ever been perfect.

AP review commonly checks the invoice against the purchase order and the receipt. Three-way matching confirms the item was ordered and received; it does not test whether a surcharge has expired, a volume tier has been crossed, or a rebate has been earned and never invoiced back.

That is a different check, and it requires the contract itself, not the PO. If procurement cannot produce contract-to-invoice matches for even a sample of vendors, that is the finding a diligence advisor will surface, framed as a control gap rather than a one-off error.

This is also where a gross margin bridge becomes useful internally before it becomes necessary externally. Building one that separates inflation from non-compliance forces the same contract-to-invoice comparison, and gives you language for the sponsor conversation instead of a surprise inside it.

4. What should you ask about rebates and credits?

Ask whether earned rebates are tracked against actual purchase volume, whether anyone reconciles rebate statements against contract terms, and whether credit memos for pricing errors are applied or left sitting unapplied. Unclaimed rebates and unapplied credits both understate cash the company has already earned, and both are recoverable without touching a single go-forward process.

A rebate clause is a promise the vendor makes to pay money back once a volume threshold is crossed. That promise only pays out if someone tracks volume against the threshold and invoices the vendor for the difference. Some companies rely on the vendor to self-report, which means the company receives only what the vendor chooses to calculate.

Ask procurement directly: for each rebate-bearing contract, who tracks the volume, and who requests the rebate. If the answer is nobody, that is quantifiable exposure sitting in AR that nobody has claimed.

Credit memos work the other direction. A vendor issues a credit for an overbilled invoice, and the credit sits in the vendor's system unapplied because nobody matched it back to the original charge. Both failures are AP recovery audit territory: retrospective, bounded, and answerable before a sponsor asks the same question.

5. Should procurement check for duplicate vendor rates across entities?

Yes. If the company operates multiple entities or locations, ask procurement whether the same vendor is charging different rates to different entities for the same service, and whether that difference is explained by volume or geography. An unexplained difference is a negotiation left on the table, and a sponsor's advisor will ask why it was never consolidated.

Multi-entity manufacturers accumulate vendor relationships the way they accumulate acquisitions: one contract per site, negotiated at different times by different people, none of them aware of the other. The result is the same freight carrier or the same staffing agency billing three different rate cards to three plants under common ownership.

This is not a compliance problem in the strict sense. Each rate may be honored correctly against its own contract. It is a lost buying-power problem: the company is paying as three small customers instead of one large one.

Ask procurement to run a vendor name match across entities and flag any vendor billing more than one rate card. This connects directly to month-end close complexity too, since multi-entity closes already have to reconcile intercompany vendor spend line by line.

6. What should the answer look like when the sponsor asks?

The answer should be a short, dated summary: which vendor contracts were reviewed, what was found, what was corrected, and what remains open with a stated reason. A sponsor does not expect zero findings. A sponsor expects to see that findings were found by you first, quantified, and already moving toward resolution before diligence started.

The worst outcome in a sponsor review is not a finding. It is a finding the company did not know about, presented by someone else's advisor, with no context and no plan attached. A second poor outcome is a finding presented defensively, as though it undermines the deal, rather than as evidence that the finance function has controls.

The fix is sequencing. Run the contract-to-invoice check internally, on your own timeline, and have the summary ready before anyone asks for it. That summary becomes part of the story you tell about the business: not a company with no drift, but a company that finds and fixes its own drift.

This is also the moment a fixed-scope diagnostic earns its cost. An engagement delivering a prioritized roadmap in 2 to 4 weeks across service vendor categories, across ValueXPA diagnostics, produces exactly the documentation a sponsor review will ask for, on a timeline that fits before diligence rather than during it.

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

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

7. Frequently Asked Questions (People Also Ask)

How far ahead of a sponsor review should we ask procurement these questions?

As early as the review is on the calendar, and ideally before any advisor is engaged. A contract-to-invoice check takes time to run properly, and finding a gap with no runway to fix or explain it is worse than not looking at all.

Does IT and professional services spend need the same review as freight and labor?

Yes. IT and professional services contracts carry their own drift risk: statement-of-work overruns, auto-renewed licenses, and rate escalators that were never checked against the invoice. The mechanism is the same even though the vendor category is different.

What if procurement says the contracts are all current but nobody has checked invoices against them?

That answer is itself the finding. A current contract file with no matching process still leaves the company unable to show, on request, that the invoiced price equals the contracted price. Treat it as an open item, not a clean bill of health.

Should finance or procurement own the contract-to-invoice reconciliation?

Neither owns it today in most companies, which is the underlying problem. It requires procurement's contract knowledge and finance's invoice data together, so the answer is usually a joint process with one function named accountable for it.

Is this different from a standard AP audit?

A standard AP audit typically checks for duplicate payments and math errors. This review checks something upstream of that: whether the price terms in the contract are the price terms being billed, which a payment-level audit does not test.

What documentation should procurement have ready if a diligence team asks directly?

A vendor contract inventory, current rate cards attached where they exist, a rebate tracking log, and a sample of invoice-to-contract matches for the largest vendors by spend. Those four items answer most of what a diligence advisor asks for first.

Can this checklist be run for a single business unit instead of the whole company?

Yes. Running it unit by unit is often more practical, especially where entities were acquired separately and never had their vendor contracts consolidated. The same five questions apply at any scope.

What happens if we find drift but do not have time to fix it before the review?

Document it anyway. A quantified, explained finding with a stated remediation plan reads as a company that knows its own numbers. An unexplained gap discovered later reads as a company that does not.