NTE overrun in maintenance and repair contracts

Executive Summary

A not-to-exceed clause caps what a maintenance vendor may bill on a single work order without written approval to exceed it. The clause is specific: it names a dollar figure, a work order or asset, and usually a change-order procedure. It is not a general spending limit and it does not renew automatically across repeat visits to the same asset.

The overrun happens at the handoff between the field and the back office. A technician logs hours and parts against a work order; the invoice is generated from that labor and parts data, not from the NTE figure itself. Nothing in most vendor billing systems stops an invoice at the cap unless someone configured it to.

Three-way matching checks the invoice against the purchase order and receipt; it does not test whether a line total sits under a separate contractual ceiling that lives in the MSA, not the PO.

Closing it requires matching the invoice to the specific NTE clause for that work order, not just to the PO amount, and requiring the change-order paperwork before an over-cap invoice is paid.

1. What does a not-to-exceed clause actually cap?

A not-to-exceed clause sets a dollar ceiling on a single maintenance work order or repair job, covering labor hours, parts, and often travel or diagnostic fees combined. It applies to that specific job, not the vendor relationship as a whole. Crossing it requires the vendor to stop and get written approval, usually through a change order, before continuing the work or invoicing above the figure.

The clause sits in the master service agreement or in the work order itself, and its wording matters more than its number. Some caps include parts and labor together; others cap labor only and let parts bill separately, which changes what counts against the ceiling. Some caps require approval before the vendor exceeds the figure; others allow the vendor to proceed and simply flag the overage after the fact, which is a much weaker protection.

A cap tied to a work order resets with every new job. A repair visited three times in a year has three separate NTE figures, not one cumulative one, unless the contract states otherwise. That distinction is where a lot of ambiguity enters: an invoice reviewer checking a vendor's year-to-date total against a single NTE figure is applying the wrong test entirely.

The clause is also silent, in most contracts, on what happens to disputed hours already logged. If a technician logs 14 hours against a job capped at 10, the contract's change-order language decides whether those 4 hours are billable at all, or only billable retroactively once approval is documented.

2. How does an invoice cross the cap without anyone stopping it?

The overrun happens because the invoice is built from field-logged labor and parts data, not from the NTE figure. A technician's time entries and parts pulls feed the billing system directly, and that system has no reference to the dollar cap sitting in a separate contract document. Unless someone manually cross-checks the invoice total against the specific work order's NTE clause, the invoice generates and pays at whatever the field data totals.

Three-way matching, the standard AP control, checks the invoice against the purchase order and the goods or service receipt. It confirms the vendor billed what was ordered and received. It does not check the invoice against a not-to-exceed clause, because that clause typically lives in the MSA, a separate document the matching system never opens.

A purchase order raised for a repair often carries a round-number authorization, say the estimated cost, while the actual NTE ceiling in the underlying contract is a different, more precise figure with its own approval trigger. When the two documents disagree, whichever number the AP system was configured to check is the one that governs, and it is usually the PO, not the MSA clause.

Field data adds a second gap. A technician logging hours in a mobile app has no visibility into the dollar cap for the job. Hours get logged as worked, parts get logged as used, and the invoice reflects that regardless of the ceiling.

3. What has to happen before an over-cap invoice is legitimate?

An invoice that exceeds the not-to-exceed figure is only legitimate if the contract's change-order procedure was followed: written notice from the vendor that the cap will be exceeded, and written approval from the buyer before the additional work is billed. Without that documentation, the excess amount is a contract violation regardless of whether the underlying labor and parts were genuinely used.

The change-order requirement exists specifically to stop a vendor from treating the NTE figure as an estimate rather than a ceiling. It puts the decision to spend more back in the buyer's hands at the moment costs are rising, not after the invoice arrives.

In practice, the paperwork trail is uneven. Some vendors route change orders through the plant manager who called them in, not through procurement or AP, so the person paying the invoice has no record the approval ever happened. Verifying an over-cap invoice means asking for that specific document, not just checking whether the total looks reasonable for the work described.

A. Two failure patterns

The first: the vendor exceeds the cap and bills the full amount with no change order at all, treating the NTE figure as advisory. The second, subtler pattern: a change order exists but covers a different scope or a smaller amount than what was actually billed, so part of the invoice is authorized and part is not.

4. Why does repeat work on the same asset make this harder to catch?

A piece of equipment serviced repeatedly over a year generates a string of separate work orders, each with its own NTE cap, but AP review typically looks at vendor spend in aggregate rather than job by job. An asset with five service calls, each just under its individual cap, can carry real overruns hidden inside any one of those calls without the aggregate total ever looking abnormal.

Reviewing vendor spend by month or by total contract value is a reasonable way to catch a vendor whose overall billing has grown unexpectedly. It is the wrong lens for catching an NTE overrun, because the overrun is a violation at the level of a single work order, not the account.

The fix is procedural rather than analytical: every work order above a threshold amount gets checked against its own NTE clause at the time the invoice is coded, before it reaches whatever aggregate review AP runs monthly. That check has to happen line by line, work order by work order, because a job costing exactly its cap looks identical, on a monthly total, to a job costing over its cap that never got a change order.

5. Does the maintenance vendor's own cost base change how the cap is applied?

A vendor's underlying repair costs move over time, and a fixed NTE figure written into a contract months or years earlier does not move with them. Per the US Bureau of Labor Statistics Producer Price Index for commercial machinery repair and maintenance, the industry index rose 9.1% year over year to 237.468 in July 2026, read September 5, 2026, meaning a vendor's real cost to perform the same repair has climbed since the cap was negotiated.

That does not authorize a vendor to bill above the contracted cap. A not-to-exceed clause is a ceiling the vendor agreed to regardless of its own cost movement, and it stays enforceable until the parties renegotiate it. What the cost movement does explain is why vendors have more reason now to push for change orders or contract renegotiation than they did when the cap was set.

That makes it more important, not less, to track which NTE figures were set against an older cost base and are due for renegotiation, versus which invoices are simply exceeding a still-current cap without authorization. Confusing the two lets a vendor use rising costs as informal cover for an unapproved overrun.

6. How do you stop this at the contract level, not invoice by invoice?

Stopping NTE overruns durably means writing the cap so it can actually be checked: tie it to a specific work order number, state whether labor and parts count together or separately, and require the change-order document as a condition of payment, not just a condition of doing the work. Then configure AP to match the invoice against that clause specifically, not against the PO alone.

A few contract terms make the difference between a cap that holds and one that quietly erodes.

• Work-order-level ceiling: State the cap per work order or per asset visit, not as a blanket annual figure, so a reviewer knows exactly which invoice to test it against.
• Explicit scope of the cap: Specify whether labor, parts, travel, and diagnostic fees all count toward the same number, so there is no argument later about what was capped.
• Payment-conditioned change order: Make the signed change order a precondition of paying any amount above the cap, not just a notice requirement.
• Invoice-to-clause matching: Route work orders above a threshold to a check against the specific NTE clause before payment, separate from standard PO matching.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and rate card enforcement: why approved timesheets still produce wrong invoices.

7. Frequently Asked Questions (People Also Ask)

What is a not-to-exceed clause in a maintenance contract?

It is a dollar ceiling written into a work order or master service agreement that caps what a maintenance vendor may bill for a specific repair job without written approval to exceed it. It typically covers labor and parts for that job and requires a change order before the vendor can bill above the figure.

How is an NTE overrun different from a labor rate deviation?

A labor rate deviation is about the hourly or unit rate charged being wrong against the contracted rate. An NTE overrun is about the total dollar amount for a specific job exceeding an agreed ceiling, regardless of whether each individual rate charged was correct. A job can have correct rates and still breach its cap.

Does three-way matching catch an NTE overrun?

No. Three-way matching checks the invoice against the purchase order and the receipt of goods or services. It does not test the invoice against a not-to-exceed clause, which usually lives in the master service agreement rather than the PO, so the matching system never checks it.

Who has to approve work that will exceed the cap?

The contract's change-order procedure specifies this, and it usually requires written approval from the buyer, often procurement or the maintenance manager, before the vendor proceeds with work above the NTE figure or bills for it. Verbal approval from whoever is on-site does not substitute for the documented change order the contract requires.

Does an NTE cap reset every year or every work order?

It depends entirely on how the contract is written. Most work-order-level caps apply per job and reset with each new service call on the same asset, rather than accumulating across a year. A reviewer needs to check the specific clause language rather than assume either pattern.

Can a vendor justify exceeding the cap because their own costs went up?

Rising input costs explain why a vendor might want to renegotiate a cap, but they do not authorize billing above a still-active contracted ceiling. Per the Bureau of Labor Statistics, the Producer Price Index for commercial machinery repair and maintenance rose 9.1% year over year to 237.468 in July 2026, read September 5, 2026, which is a reason to review the cap, not a basis for the vendor to override it unilaterally.

What documentation should AP require before paying an over-cap invoice?

A signed change order that names the specific work order, the amount by which the cap is being exceeded, and the approver, dated before the additional work was performed or billed. An invoice above the NTE figure with no matching change order on file should not be paid at the higher amount.

Why does reviewing total vendor spend not catch this?

NTE overruns occur at the level of a single work order, not the vendor account. A vendor whose monthly total looks normal can still have individual jobs that exceeded their specific caps, because the aggregate view has no visibility into any one job's contracted ceiling.

What should the contract state to make this checkable later?

The cap should be tied to a specific work order or asset visit, state clearly whether labor, parts, and travel all count toward the same ceiling, and make the signed change order a condition of payment for any amount above the cap, not just a notice obligation.

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

No, and treating them as the same is a common source of the overrun. A PO often carries a round estimated authorization, while the actual NTE figure sits in the underlying master service agreement with its own, sometimes more precise, ceiling and approval trigger.