NTE overrun: what it costs above the cap

Executive Summary

A not-to-exceed clause sets a maximum price for work billed on a variable basis: time and materials, a repair estimate, a project rate. The overrun happens when the invoice clears that ceiling and AP pays it anyway, usually because the control checking the invoice compares it to the purchase order, not to the contract clause that capped the job.

The mechanism is structural, not a vendor lapse. A cap lives in a contract PDF or a statement of work. A three-way match lives in the ERP and checks quantity and unit price against a PO line. Neither system reads the other's document, so a job that runs past its own ceiling can still match its PO cleanly and pay on time.

What changes it is checking the invoice against the cap itself, not against the PO, before the invoice pays. That means someone, or some system, holds the contracted ceiling as a discrete, checkable number per job and tests every invoice against it. Absent that check, the cap is a sentence in a document nobody re-reads at payment time.

1. What is a not-to-exceed clause and why does it fail?

A not-to-exceed clause sets a ceiling price on work billed by time, materials, or a variable rate: a repair job, a T&M service call, a project quoted with a cap instead of a fixed fee. It fails not because the vendor ignores it but because the systems checking invoices for payment do not check against it. A purchase order confirms a vendor and a general amount; it rarely encodes the specific dollar ceiling the contract or the statement of.

The clause is written to protect the buyer from an open-ended bill. Time and materials work is priced by hour and part, which means the total is not known until the job finishes. The cap is the buyer's insurance against that uncertainty.

The insurance only works if something re-reads it at invoice time. In practice the PO authorizing the job carries a round number, sometimes the estimate, sometimes a blanket authorization amount, and the invoice is matched against that PO line rather than against the contract clause.

A vendor invoice can match its PO exactly, on quantity and rate, and still exceed the ceiling the underlying agreement actually set. The PO and the contract are two different documents, held in two different places, and nothing forces them to agree.

2. How does an overrun get past AP without anyone noticing?

Three-way matching checks an invoice against a purchase order and a receipt. It confirms the vendor billed the quantity it delivered at the price it quoted. It does not test whether that total sits under a separate not-to-exceed figure written into the contract or statement of work, because that figure is not a field the ERP holds.

The invoice can be correct against the PO and still be wrong against the cap, and the match that runs at payment time.

The failure is not a missing approval step. Many invoices in this category do get approved, by someone who reviewed the job and the amount looked reasonable relative to the work performed.

What that reviewer does not have in front of them is the original cap. It sits in a signed contract or an SOW, in a system the AP workflow does not open. The reviewer is judging reasonableness against experience, not against a documented ceiling.

Once the invoice clears three-way match and a plausibility review, it pays. Nothing downstream re-checks it against the contract, because nothing downstream owns the contract as a data source at all.

3. How much does an NTE overrun cost a mid-market manufacturer?

There is no published rate for how often not-to-exceed caps are breached or by how much industry-wide; no dataset exists to support one. What can be stated is the arithmetic: take every invoice tied to a T&M or capped job in the last 12 to 18 months, pull the cap named in its contract or SOW, and compare the two directly. The dollar difference, summed across every breached invoice, is the exposure.

It is a number you compute from.

A margin drift diagnostic runs exactly this comparison as part of a broader review: it matches invoice-to-contract terms, including rate cards, volume tiers, rebate clauses, surcharge schedules and NTE caps, across service vendor categories, and reports leakage across the full engagement typically running 1% to 3% of service vendor spend, across ValueXPA diagnostics.

That aggregate figure describes the whole diagnostic, not this one drift type in isolation, because no breakdown by category exists. What is knowable at the category level is mechanical: pull every job billed against a cap, find its contracted ceiling, and subtract. Whatever total that produces for your own vendor base is your real number, and it is the only one worth acting on.

4. Which contract structures make NTE overruns more likely?

The clause shows up wherever price is variable at the time the contract is signed: maintenance and repair work billed by labor hour plus parts, staffing engagements with an overtime or premium component, and professional services scoped with a not-to-exceed instead of a fixed fee. Each structure puts a ceiling on an amount that is not known until the job runs, which is exactly the condition under which a ceiling is both necessary and easy to lose track of at.

In maintenance and repair, the cap usually sits on a specific work order rather than the master agreement, so there can be many active ceilings across a single vendor relationship running in parallel.

In contract labor and staffing, the risk compounds with a related drift type: a shift or overtime premium can push a bill past its cap even when the base rate is correct, because two variables are moving instead of one.

In professional services and IT engagements, the cap is often set at the statement-of-work level and renegotiated project by project, which means a stale cap from an earlier phase can still be the number, or lack of one, sitting in AP's system when a later invoice arrives.

5. Can you catch an NTE overrun before you pay it, not after?

Yes, but only if the cap is captured as a discrete field checked at invoice receipt, not left inside a contract PDF read once at signing. That requires someone to extract every active not-to-exceed ceiling from current contracts and SOWs into a place AP actually queries, then test each incoming invoice against it before approval, not after the money has moved. Catching it after payment turns a preventable control gap into a recovery project instead.

The retrospective version of this work, an AP recovery audit, finds overruns that already paid: it reviews 12 to 18 months of historical invoices for duplicate payments, vendor overbilling, missed credit memos and unapplied rebates, an approach that catches what already happened.

The forward version requires the ceiling to exist as data the AP workflow reads before it releases payment. That is a process and data change, not a personnel change: it does not need a new approver, it needs the approver to have the right number in front of them.

Until that data exists in a checkable form, every invoice against a capped job is being approved on judgment rather than against a documented ceiling, and judgment alone does not scale across a vendor base running many active caps at once.

6. What should you do differently starting with your next invoice cycle?

Build a single list of every active not-to-exceed ceiling across current contracts and statements of work, tagged to the vendor and job it applies to, and put it somewhere AP checks before approving an invoice in that category. That single change converts the cap from a clause read once at signing into a number tested every cycle. It is the same underlying fix whether it is done manually on a spreadsheet or built into a system, and it is the.

Start with the vendor categories most likely to carry an NTE clause: maintenance and repair, contract labor and staffing, and IT and professional services. Pull every active contract or SOW in those categories and extract the capped dollar figure, not the estimate on the PO.

Build the check as a simple comparison run before approval: invoice total against the extracted cap, flagged whenever the invoice exceeds it without an attached change order. This does not require new software to start; it requires the ceiling to exist somewhere AP looks.

The split between what already leaked and what a forward control would prevent decides where the effort pays off first, and that split is worth working out before choosing between a one-time cleanup and an ongoing check.

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

7. Frequently Asked Questions (People Also Ask)

What counts as a not-to-exceed overrun?

An invoice billed against a job with a contracted price ceiling, T&M, a repair estimate, a capped SOW, that exceeds that ceiling without an approved change order. The overrun is the dollar amount above the cap, not the whole invoice.

Is a not-to-exceed clause the same as a purchase order limit?

No. A PO limit is an authorization amount set when the job is opened, often an estimate. The not-to-exceed clause is a contractual ceiling written into the agreement or statement of work. The two can differ, and a three-way match only checks the invoice against the PO.

Why does three-way matching miss this?

Three-way matching checks the invoice against the purchase order and the goods or service receipt. It confirms quantity and price agree with what was ordered and delivered. It does not read the contract clause that set the ceiling, because that clause is not a field the match compares.

Can a change order legitimately raise the cap?

Yes. A documented, approved change order can raise a not-to-exceed ceiling for a specific job. The overrun problem is invoices that exceed the original cap with no such document attached, not every invoice above the first estimate.

Which vendor categories carry NTE clauses?

Maintenance and repair, contract labor and staffing, and IT and professional services commonly use not-to-exceed structures because the underlying work is billed on a variable basis. Freight and MRO categories more often use fixed rate cards instead.

Does this only matter for large invoices?

No. A small overrun on a single work order can repeat across many work orders under the same vendor relationship. The exposure is the sum across every capped job, not the size of any one invoice.

How far back should we look for existing overruns?

12 to 18 months of historical invoices, across ValueXPA diagnostics, is the window used to size leakage already embedded in past spend. Anything older is harder to substantiate against the original contract terms.

Is this covered by AP automation software?

AP automation prevents errors at the point of invoice receipt going forward, but it needs the contracted cap loaded as a rule to check against. Without that rule loaded, the software matches the invoice to the PO the same way manual review does, and misses the same overrun.

What is the difference between this and a minimum commitment shortfall?

A not-to-exceed overrun is billing above a contracted ceiling. A minimum commitment shortfall is the opposite structure: paying a penalty or true-up for falling below a volume floor. Both require checking the invoice against a clause outside the PO.

Should legal review the contract language on NTE clauses?

This is general information, not legal advice. How a not-to-exceed clause is worded, and what remedy it gives you for a breach, is a contract drafting question your counsel should review directly.