Margin Drift or Legitimate Increase: How to Tell Them Apart

Executive Summary

A price increase is legitimate when the contract contains a clause that permits it, the increase matches what that clause specifies, and the vendor followed the notice and documentation terms attached to it. Everything that does not clear that bar counts as drift: an increase applied without a triggering clause, an increase larger than the clause allows, or an increase applied before the effective date the contract sets.

The mechanism that produces drift is not fraud. It is that contracts route escalation, surcharge, and index clauses through language buried in an exhibit or an appendix, while AP systems match invoices against a PO and a unit price field that never gets updated to reflect those clauses. The invoice looks ordinary.

The increase looks routine. Neither system checks it against the clause that actually governs it.

What changes this is treating every increase as a two-part question: is there a clause, and does the invoice match the clause. That test applies the same way whether the increase is a fuel surcharge, an annual escalator, or a renegotiated rate card, and it is the only reliable way to separate a vendor's legitimate cost pass-through from drift that erodes margin quietly, invoice after invoice.

1. How do you tell a legitimate price increase from margin drift?

Check the contract for a clause that authorizes the specific increase you are seeing: an index escalator, a fuel surcharge formula, a renegotiated rate card, or an annual adjustment provision. If the clause exists and the invoice matches its formula, timing, and notice requirements, the increase is legitimate. If no clause exists, the invoice amount exceeds what the clause allows, or the vendor skipped the notice step, the increase is margin drift.

This test has three parts, and all three have to clear before an increase counts as legitimate.

First, does a clause exist. Many service contracts are silent on price changes entirely, which means any increase during the term needs a signed amendment, not a note on an invoice.

Second, does the invoice match the clause's formula. An index escalation misapplied against the wrong base period, or a fuel surcharge calculated off the wrong published rate, produces a number that looks plausible but fails the test.

Third, did the vendor follow the notice and effective-date terms the clause specifies. A notice requirement that the vendor skipped, or an increase applied a full billing cycle early, is drift even when the underlying rate itself is correct. Each part is checkable against the contract text, not against instinct.

The AP team's job is not to judge whether a vendor's cost increase feels fair. It is to confirm the contract permits it, in the amount and on the date charged.

2. What clauses actually authorize a price increase?

Four clause types authorize a price change in a typical service contract: an index escalation clause tied to a published index, a fuel or energy surcharge formula, an annual rate adjustment provision with a stated cap, and a renegotiated rate card signed as an amendment. Anything charged outside one of these, however reasonable the vendor's explanation, has no contractual basis and is margin drift by definition.

An index escalation clause ties a rate to a named index, such as a producer price series, with a defined base period and adjustment date. The clause states the formula; the invoice either follows it or does not.

A fuel or energy surcharge clause defines the trigger, usually a published diesel or energy price crossing a threshold, and the formula for translating that into a line-item charge. See index escalation misapplied for how these formulas break.

An annual rate adjustment provision permits a defined increase, often capped at a percentage, on a stated anniversary date. Applying it early, or above the cap, is drift.

A renegotiated rate card, signed as an amendment, replaces the prior pricing outright and is the cleanest of the four because it leaves a document trail. Outside these four, a vendor raising a rate mid-term because of its own cost pressure has no contractual standing, whatever the invoice memo says.

3. Why does drift get mistaken for a normal increase?

Three-way matching checks the invoice against the purchase order and the goods receipt. It does not check the invoice against the escalation, surcharge, or rate-card clause governing that vendor's contract, because those clauses live in a PDF outside the ERP, not in a field the matching engine reads. An increase that clears three-way matching has only been checked against the PO, never against the contract.

The purchase order carries a unit price, but that field is rarely updated when a contract's rate card changes, and it is never updated automatically when an escalation clause fires on its own schedule. So the match between invoice and PO can pass cleanly while the invoice itself has already drifted from the contract.

A fuel surcharge is a clear example. The formula lives in an exhibit, references an external index, and recalculates monthly. Nothing in a standard AP workflow pulls that exhibit and recomputes the number before approving the invoice.

The same gap applies to accessorial charge creep and to volume tier misapplication, where a rate depends on a threshold nobody is tracking against actual volume. In each case the invoice is internally consistent and looks like routine business. The failure is not in the invoice. It is that no system in the AP workflow is reading the clause that should be checked against it.

4. What does the review process look like in practice?

A contract compliance review pulls every price-affecting clause from the vendor agreement into a structured reference, then checks each invoice line against that reference rather than against the PO alone. This catches increases with no authorizing clause, increases that exceed what a clause permits, and increases applied before their effective date, across a full billing history rather than one invoice at a time.

Building the clause reference comes first, then matching invoices against it. Both steps are described below.

A. Building the clause reference

Every price-affecting clause, index escalators, surcharge formulas, rate caps, renegotiation terms, gets extracted from the contract and its exhibits into one structured document per vendor. This is the step most AP workflows skip, because the clauses sit in unstructured PDF exhibits the ERP never ingests.

B. Matching invoices against it

Each invoice line is checked against the relevant clause: does an authorizing clause exist, does the amount match its formula, was the effective date and notice period honored. Lines that fail any part are flagged as drift rather than assumed correct because they matched the PO.

5. Can a vendor increase be partly legitimate and partly drift?

Yes. A vendor can have a valid escalation clause and still overapply it: charging the correct percentage but on the wrong base rate, or applying an authorized increase a full quarter before its effective date. These partial cases are the hardest to catch because the invoice contains a real clause and a real number, just not the number that clause actually produces.

A minimum commitment shortfall charge is a useful comparison. The clause is real and the concept is legitimate, a shortfall fee for under-ordering, but the calculation depends on tracking actual volume against the committed threshold accurately over the right period. Get the period wrong and the fee is drift even though the clause is entirely valid.

The same partial pattern shows up in not-to-exceed overrun situations, where a cap exists and is real, but billed hours or units are recorded against the wrong contract period or the wrong scope line, pushing the total over the cap without anyone applying an unauthorized rate. Partial drift requires the same clause-by-clause check as a wholesale unauthorized increase. Treating any invoice with a matching clause as automatically clean is exactly how partial drift stays uncaught.

6. What should an AP team do differently starting now?

Build a clause reference for each major service vendor, listing every price-affecting term with its formula, cap, and effective date, and check new invoices against it before approval rather than after. For historical spend, a contract compliance review applied across 12 to 18 months of invoices finds increases that already cleared approval but never cleared the clause that should have governed them, across ValueXPA diagnostics.

The steps below apply in sequence, from building the reference to tracking it going forward.

1. Extract every clause: Pull index, surcharge, cap, and renegotiation terms out of each vendor contract into one reference document, not left buried in the signed PDF.
2. Match before approval: Check new invoices against the clause reference at approval time, not just against the PO and receipt.
3. Review historical invoices: Apply the same clause check backward across recent billing history, where increases already paid may not have cleared the clause governing them.
4. Track effective dates separately: Log each clause's next adjustment date so a surcharge or escalation applied early is flagged automatically rather than caught by chance.

For the wider pattern this sits inside, start with the margin drift guide. See also off-contract resources: people billed outside the agreement and unapplied volume rebates in staffing agreements.

7. Frequently Asked Questions (People Also Ask)

Is a fuel surcharge automatically legitimate if the diesel price went up?

No. The surcharge is legitimate only if the contract contains a formula tying the charge to a published index, and the invoiced amount matches that formula and its stated trigger. A rising diesel price does not by itself authorize a charge; the clause does.

What if the vendor contract does not mention price increases at all?

Then no increase is authorized during the term without a signed amendment. Silence in a contract is not permission. Any increase applied under a silent contract is margin drift regardless of how reasonable the vendor's stated reason is.

Does three-way matching catch margin drift?

No. Three-way matching checks the invoice against the purchase order and the goods receipt, not against the escalation or surcharge clause governing the vendor's rate. An invoice can pass three-way matching and still not match the contract clause that should govern it.

Can a correctly calculated increase still be drift?

Yes. An increase can use the correct rate and formula but be applied before its effective date, or applied against the wrong base period, and still count as drift. The formula being right does not make the timing or the base right.

Who is responsible for catching this, AP or procurement?

The clause reference has to come from the contract itself, which typically sits with procurement or legal, but the invoice-level check runs through AP. The gap in most workflows is that neither team owns building the reference document that connects the two.

How far back should a historical review go?

A contract compliance review applied across 12 to 18 months of invoices, across ValueXPA diagnostics, finds increases that already cleared approval but never cleared the governing clause. Going back further is reasonable if records and contract versions are available.

Is a renegotiated rate card the safest kind of increase to accept?

It is the easiest to verify because it is a signed amendment that replaces the prior pricing outright, which leaves a clear document trail. It still needs to be checked against the invoice date to confirm it was applied only after its signed effective date.

What happens if a vendor skips the required notice period?

An increase applied without the notice the clause requires is drift even if the rate itself is correct and the clause authorizing it is real. The notice term is part of what makes the increase valid, not a formality separate from it.