What to ask procurement when margin misses plan

Executive Summary

When gross margin misses plan, the finance team usually starts with the P&L and procurement usually starts with commodity prices. Both are looking in the wrong place first. Margin drift does not show up in a commodity index or a freight surcharge announcement. It shows up in the invoice-to-contract match that rarely runs before close.

The mechanism is specific: rate cards left unupdated after a renewal, volume tiers that reset a threshold silently, surcharges that outlived the condition that justified them, and rebates earned but never invoiced back. Each produces a margin miss that looks identical to an input cost increase on a variance report, because both reduce gross margin through the same account by the same dollar amount.

What changes the outcome is the order of the questions asked in the procurement review. Ask about the contract terms before asking about the market. This page lists the specific questions to ask, and explains why each one isolates a different type of drift from the general cost pressure procurement will otherwise name first.

1. What should you check first when gross margin misses plan?

Check whether the invoice matches the contract before checking whether the market moved. Pull the vendor rate card, the volume tier schedule and the last invoice for the top service vendors by spend, and compare line by line. If the invoice rate exceeds the contracted rate, the miss is a compliance problem, not a market problem, and no commodity index explains it.

This single comparison, done for the top ten vendors by spend, usually surfaces the answer before any broader.

Procurement's first instinct is to explain a margin miss with a market story: freight rates rose, steel moved, labor costs increased. Some of that is real. But a market move should show up consistently across every vendor in a category, at roughly the rate the market moved.

A vendor whose invoice rate has drifted above its contracted rate is not a market signal. It is a billing error or a stale rate card.

The fastest way to tell the two apart is a direct comparison: pull the signed rate card or contract amendment for each of the top vendors by spend, and compare it line by line against the most recent invoice. Do this before accepting any market explanation, because once a market story is accepted, nobody checks the contract.

This is not a company-wide audit. It is a targeted pull on the vendors carrying the largest share of the variance, which is usually a short list.

2. How do you tell a rate card problem from a real cost increase?

A rate card problem shows a single vendor's invoiced rate exceeding its own signed contract rate. A real cost increase shows the market rate moving and the vendor invoicing at or near that new market rate, consistently, across the category. The test is whether the invoice cites the contract rate or a different one.

If the invoiced rate cannot be traced to a specific clause in the current contract, it is drift, not the market.

Ask procurement to produce the specific clause that authorizes the current invoiced rate. Not the master service agreement in general, the specific line: the rate card version, the effective date, and any amendment that changed it.

If procurement cannot produce that clause quickly, the invoice is likely being paid against whatever rate the vendor billed, not the rate the contract sets. This happens most often after a renewal, when the new rate card is signed but never loaded into the system that generates payment approvals.

A real cost increase has a paper trail on the vendor's side too: a price increase letter, a surcharge notice, or a renegotiated rate card with a new signature. If that document does not exist, the rate did not actually change. It only started being billed as if it had.

3. What questions isolate a volume tier or rebate problem?

Ask three questions: what volume tier are we contracted at, what volume did we actually ship or spend last period, and has the vendor issued the rebate or credit that tier entitles us to. A gap between the tier the contract sets and the tier being invoiced, or a rebate that was earned but never received, both reduce gross margin without any change in unit cost, and both are recoverable once identified.

Volume-based contracts set a rate or a rebate that depends on a threshold: ship this much, spend this much, and the rate drops or a rebate applies. These thresholds are set once at signing and rarely revisited as volume changes.

Ask procurement whether current volume has crossed a tier threshold in either direction. If volume grew past a threshold, the vendor may still be billing at the lower tier's higher rate. If volume fell, the contract may specify a minimum commitment that changes the math entirely.

Separately, ask whether earned rebates have actually been invoiced back or credited. A rebate clause that requires the buyer to submit a claim, rather than the vendor to pay automatically, is a common place for money to sit unclaimed. Nobody on the AP side is checking for a check that never arrives.

4. Which contract terms should procurement re-verify against the current invoice?

Re-verify four terms against the most recent invoice: the base rate card, any volume tier trigger, every accessorial or surcharge line, and any not-to-exceed cap on labor or project spend. These four account for most of the drift types that produce a margin miss without a corresponding market event, and each can be checked from documents already on file without new data collection.

A. Rate card and effective date. Confirm the invoice cites the current signed rate card, not a prior version still loaded into the payment system.

B. Surcharge conditions. A surcharge tied to a fuel price or a labor shortage should expire when the condition does. Check whether the surcharge is still being billed after the condition that triggered it has passed.

C. Not-to-exceed caps. Contract labor and project-based service contracts often carry an NTE cap. Confirm invoiced totals against the cap, not against the budget, since the two are set independently.

D. Volume tier and rebate terms, covered above but worth re-stating here because they are the term most often left unchecked at renewal.

A. Base rate and surcharge terms

These two terms drive most of the dollar variance because they apply to every invoice in a category, not just one. A one dollar error in a base rate compounds across every unit billed for the life of the contract.

B. Caps and tier triggers

These terms apply less often but produce larger single instances of drift when they do, since an NTE breach or a missed tier reset can represent a large share of a single invoice.

5. Who should own the answer once the cause is identified?

Procurement owns the vendor relationship and the contract terms. AP owns whether the invoice was paid as billed. Finance owns whether the variance is explained and closed out. The answer to a margin miss usually needs input from all three, because the point where drift is created, the point where it is paid, and the point where it is reported sit on three different desks that rarely compare notes.

A margin miss investigation stalls when one function is asked to explain a variance that was actually created upstream of them. AP can confirm an invoice was paid as billed, but cannot confirm the billed rate was correct without the contract. Procurement holds the contract but does not see the invoice-level detail that finance closes the books against.

The fix is not a new department. It is a standing three-way review: finance brings the variance, procurement brings the contract terms, AP brings the paid invoice detail. Run this for any vendor category where the miss is material, and it usually converges in one meeting.

Where this review has to happen every close cycle rather than once after a bad quarter, it is worth building into the standard month-end process rather than treating each miss as a one-off investigation.

6. When does this warrant a full contract compliance review instead of a spot check?

A spot check on the top vendors by spend is enough when the miss is small and concentrated in one or two categories. A full contract compliance review is warranted when the miss recurs across multiple quarters, spans several vendor categories, or the spot check itself turns up drift on more than a couple of the vendors sampled. At that point the pattern, not the single miss, is the signal worth acting on.

A one-time miss traced to a single stale rate card is a fix, not a program. Correct the rate, recover what is owed, and move on.

A miss that recurs, or a spot check that finds drift on several vendors rather than one, points to a systemic gap: nobody owns the reconciliation between signed contract terms and what the payment system actually enforces. That gap does not close itself between quarters.

At that point the question changes from what happened this quarter to how many contracts across indirect spend categories, such as freight, contract labor, and MRO, carry the same kind of unreconciled term. Answering that requires a structured pass across contracts and invoices rather than a spot check on the top few vendors, and it is the point at which a dedicated diagnostic engagement, run as a fixed-scope exercise separate from the monthly close cycle, becomes worth the time.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and margin drift vs. legitimate price increases: how to tell them apart.

7. Frequently Asked Questions (People Also Ask)

What is the fastest way to check if procurement's margin explanation is correct?

Pull the signed rate card and the most recent invoice for the vendors carrying the largest share of the variance and compare them line by line. If the invoiced rate matches the contract, the explanation likely holds. If it does not, the miss is a billing or compliance issue, not the market cause procurement first names.

Should we ask procurement or AP first when margin misses plan?

Ask procurement for the contract terms first, since AP can only confirm an invoice was paid as billed, not whether the billed rate was correct. Once the contract terms are in hand, bring AP in to confirm what was actually paid against them.

How do we know if a surcharge is still valid?

Check the condition that triggered the surcharge, such as a fuel price threshold or a labor shortage clause, against current conditions. A surcharge is only valid while its triggering condition holds. If the condition has lapsed and the charge continues, it is no longer contractually supported.

What if procurement cannot produce the current rate card?

That is itself the answer. If procurement cannot quickly produce the specific rate card version and effective date behind a current invoice, the payment system is likely running on an outdated or undocumented rate, which is a compliance gap regardless of whether the resulting dollar variance is large or small.

Does a volume tier reset automatically?

No. A volume tier is set in the contract at a fixed threshold and does not adjust unless someone re-checks actual volume against it and updates the billing rate or rebate accordingly. Volume that has grown or shrunk past a threshold without that recheck is a common source of undetected margin drift.

Is this something our ERP should already be catching?

An ERP with three-way matching checks the invoice against the purchase order and the receipt. It does not test whether a surcharge's triggering condition has expired or whether a rebate tied to a volume threshold was ever claimed, because those checks require reading the unstructured contract terms, not just the transaction data already in the system.

How many vendors should we check before concluding there is a pattern?

Start with the vendors representing the largest share of the missed spend, typically the top ten by dollar volume in the affected category. If more than one or two of them show a documented rate or term mismatch, treat it as a pattern worth a structured review rather than a series of one-off fixes.

Can this explain a margin miss that market data seems to support?

Yes. A real market move and a compliance gap can occur in the same category at the same time and produce a combined variance that looks entirely explained by the market. Separating the two requires checking contract terms directly rather than assuming the market accounts for the full gap.

What is the general information disclaimer here?

This guide provides general information about reviewing vendor contracts and invoices for finance purposes. It is not legal advice. Any decision about enforcing, disputing, or amending a specific vendor contract should involve counsel familiar with that agreement.