What does not-to-exceed overrun look like on an invoice?

Executive Summary

A not-to-exceed overrun happens when a vendor bills above a dollar ceiling written into the contract, purchase order, or work order, and nothing in the normal invoice review catches it because that review checks the invoice against the PO and receipt, not against the cap clause itself. The mechanism is a matching gap: three-way matching confirms a service was ordered and delivered. It does not read the sentence in the master service agreement that says the job cannot exceed a stated amount without written approval.

The overrun appears in specific, recognizable forms: labor hours billed past the estimate, a parts markup added after the cap was already reached, a change order that never got separate approval, or a single invoice that rolls several smaller jobs into one total that clears the ceiling only in combination. Each form passes standard AP review because each looks like an ordinary invoice for ordinary work.

What changes it is checking the invoice against the NTE clause specifically, not against the PO amount, and doing it before payment rather than in a year-end audit. That check requires pulling the actual contract language, not just the PO dollar figure, since the two are not always the same number.

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

A not-to-exceed clause sets a dollar ceiling on what a vendor may bill for a defined scope of work, such as a repair job, a project phase, or a maintenance visit, without separate written approval. It typically covers labor, parts, and travel combined, though some contracts cap each separately. The ceiling is written into the master service agreement, the statement of work, or the purchase order, and it is the reference point an overrun is measured against, not the vendor's.

The clause exists because a vendor's initial estimate is not a guarantee. A repair that looks like a two-hour job can turn into six hours once the technician opens the equipment, and the NTE cap is the buyer's protection against that discovery turning into an open-ended bill.

The cap language matters more than its existence. Some contracts cap total invoice value. Others cap labor hours and let parts run separately, which means a vendor can stay under the labor ceiling while parts costs push the total invoice past what anyone intended.

A purchase order dollar amount is not automatically the same figure as the NTE cap in the underlying contract. A PO can be issued for an estimate while the contract's NTE clause sets a higher or lower true ceiling. Reviewing the PO number alone misses this distinction entirely.

2. How does an overrun get past standard invoice review?

Three-way matching checks that an invoice corresponds to an issued purchase order and a confirmed receipt of goods or services. It does not check the invoice total against a not-to-exceed clause, because that clause lives in the contract or statement of work, not in the PO record the matching engine reads. An invoice that matches its PO in the system can still exceed the cap written in the contract behind it.

This is a structural gap, not a lapse by any one reviewer. The AP system is built to confirm that a purchase was authorized and a service was delivered. It was not built to parse contract clauses sitting in a PDF outside the ERP.

An approver glancing at an invoice sees a vendor name, a PO reference, and a total that resembles past invoices from that vendor. Nothing on the invoice face announces that the total sits above a cap negotiated months earlier. The only way to catch it is to hold the contract's NTE language next to the invoice at the moment of approval, which most AP workflows are not built to do.

3. What does the overrun look like line by line?

An overrun rarely appears as one flagged line. It usually appears as ordinary-looking entries, labor hours, parts, a service fee, that sum past the cap once totaled. Reviewing any single line in isolation gives no signal; the overrun only becomes visible when the invoice total is compared against the contract ceiling for that specific scope of work, which is a step outside normal line-item review.

No single entry on the invoice announces the breach. The number that matters is the running total measured against the contract's ceiling for that job, not any one row on the page.

• Labor hours past estimate: A technician logs more hours than the original estimate implied, and the extra hours push the total past the cap without any single hour looking unusual.
• Parts markup added late: Parts get added to the invoice after labor already reached the cap, treating parts as a separate bucket the clause did not intend to exempt.
• Unapproved change order: The scope expanded mid-job and the change was billed without the separate written approval the NTE clause requires for anything above the ceiling.
• Multiple jobs rolled into one invoice: Several smaller service calls are combined onto a single invoice, and only the combined total clears the cap that applied to each job individually.

4. Which contract language decides whether an overrun is even a violation?

Whether a billed amount is an overrun depends entirely on the exact wording of the NTE clause: what scope it covers, whether it caps labor and parts together or separately, and what approval process it requires for anything above the ceiling. Two contracts with the same headline cap figure can produce different verdicts on the same invoice, because one exempts travel and the other does not.

Reading the dollar figure without the surrounding scope and approval language produces the wrong answer as often as it produces the right one, since the same total can be compliant under one clause and a violation under another.

A. Scope definition

The clause has to specify what work it caps: a single service call, a project phase, or an annual arrangement. An invoice that overruns the cap for one visit may be fine if the clause actually caps a longer engagement, and reading only the dollar figure without the scope sentence around it produces the wrong answer either way.

B. Approval mechanism

Most NTE clauses allow an overrun if it was approved in writing before the work proceeded. The question an invoice review has to answer is not just whether the total exceeds the cap but whether that specific overrun has a signed approval attached to it in the file. An overrun with a signed change order is a contract event. The same overrun with no approval on file is the leak.

5. How is an NTE overrun different from a legitimate scope change?

A legitimate scope change is a job that grew and got the written approval the contract requires before the added cost was billed. An overrun is the same growth billed without that approval, or billed against a cap that was never renegotiated at all. The dollar amount on the invoice can be identical in both cases; what separates them is entirely whether the paperwork trail matches what the contract demands.

This distinction is why an overrun cannot be identified from the invoice total alone. Two invoices for the same dollar amount above the same cap can have opposite answers once the supporting documentation is checked.

A vendor who bills past estimate without seeking approval is treating the NTE clause as advisory rather than binding. A vendor who requests approval every time the scope grows is operating the contract as written. The invoice alone will not tell you which vendor you are dealing with; the approval record will.

6. Can accounts payable catch this without reading every contract?

Not reliably, and that is the actual constraint. Catching an NTE overrun at the point of invoice requires the cap figure and approval rule to be available in a form the reviewer can check quickly, which means extracting NTE clauses out of contract PDFs into a reference table before invoices arrive rather than searching for the clause invoice by invoice under time pressure.

The fix is not asking AP staff to read a master service agreement for every invoice that arrives. That does not scale and it is not what the role is designed to do.

The fix is building a reference table, vendor by vendor and scope by scope, that states the NTE cap and the approval threshold in a format that can sit next to the invoice at review time. Once that table exists, checking an invoice against it is fast. Building it the first time is the actual work, because the clauses live scattered across contracts, statements of work, and change orders that were never consolidated.

7. What does fixing this actually change going forward?

Fixing an NTE overrun problem changes two things: the historical invoices get checked against the actual cap language to identify what was billed and paid above ceiling, and a forward rule gets put in place so future invoices against that vendor and scope get checked before payment rather than after. Both steps require the contract's NTE language in hand, not just the PO amount.

The retrospective piece and the forward piece are different projects with different value. The retrospective piece finds money already paid out that a written cap says should not have been billed. Recovering it depends on the contract's own remedy language, which varies by agreement.

The forward piece is cheaper to run and compounds over time: once a vendor's NTE terms sit in a checkable reference, every future invoice against that scope gets tested before it clears, and the same overrun cannot recur silently. Neither piece requires guessing at a company-wide rate of how often this happens. It requires the specific contract language for the vendor in front of you.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and what is margin erosion? causes and prevention for manufacturers.

8. Frequently Asked Questions (People Also Ask)

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

No. A PO amount is often set from an estimate and can differ from the actual NTE ceiling written into the master service agreement or statement of work. Checking the PO alone can miss a lower or higher true cap sitting in the underlying contract.

Does three-way matching catch NTE overruns?

Three-way matching confirms the invoice corresponds to an issued PO and a confirmed receipt. It does not read the NTE clause in the contract, so an invoice can pass the match and still exceed the ceiling the contract sets.

Can a vendor legally bill above the NTE cap?

Only if the contract's approval mechanism was followed, typically written approval before the added work proceeded. Without that approval on file, an amount above the cap is a contract violation regardless of whether the work was actually performed.

Does an NTE cap always cover parts and labor together?

Not always. Some contracts cap total invoice value, others cap labor and parts as separate ceilings. Read the specific clause; assuming one structure when the contract states the other is a common source of missed overruns.

What documentation proves an overrun was legitimate?

A signed change order or written approval obtained before the additional cost was incurred, referencing the specific job and the amount by which the cap was exceeded. Without that document, the excess is an overrun rather than an approved scope change.

How far back should we check for NTE overruns?

A diagnostic typically reviews the historical spend window available in your AP records against the contract language on file for each vendor, which across ValueXPA diagnostics covers 12 to 18 months of historical spend.

Is this the same issue as accessorial charge creep?

No. Accessorial charge creep involves added fees not contemplated by the base rate, usually in freight. An NTE overrun is a total exceeding an explicit dollar ceiling for a defined scope of work, most common in labor, maintenance, and professional services contracts.

Can software alone prevent NTE overruns?

Software can flag an invoice against a cap once that cap is loaded into a checkable reference. It cannot extract the correct NTE terms from unstructured contract PDFs on its own; that extraction work has to happen first, whoever performs it.