Is not-to-exceed overrun common in manufacturing?

Executive Summary

A not-to-exceed clause caps what a vendor may bill under a contract, a purchase order, or a change order. The overrun happens when billed amounts pass that cap and nobody catches it before payment. This is a mechanism, not a statistic: it depends on how many active NTE clauses a company carries, how those caps are tracked outside the ERP, and whether AP review checks the cap or just the PO line.

The reason it survives is structural. Three-way matching validates an invoice against a purchase order and a receipt. It does not test whether a cumulative billed total, across multiple invoices tied to one project or one contract year, has crossed a ceiling written in a separate document.

That check requires someone to hold the cap value and the running total side by side, and most AP workflows are not built to do that automatically.

What changes it is not a benchmark, it is a control: a place where every active NTE cap is recorded against the vendor and PO it governs, and a running total that is checked against that cap before each invoice is approved. Building that control does not require knowing how common the problem is elsewhere. It requires knowing which of your own contracts carry a cap at all.

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

A not-to-exceed clause sets a ceiling on what a vendor may bill under a specific contract, purchase order, or change order. It can apply to a single project total, a labor rate multiplied by a maximum hour count, or a cumulative annual spend figure. The cap is a contract term, not an ERP field, so it usually lives in a signed document or an email approval rather than in a system that can flag a breach automatically.

The clause exists to give a buyer cost certainty on work whose scope is hard to fix in advance: a repair job that might need more parts than expected, a staffing engagement billed hourly, an IT project scoped by phase. The vendor is authorized to invoice up to the cap, and no further, without a new approval.

The cap can be structured three ways: a hard dollar ceiling on one purchase order, a per-unit rate ceiling that still allows the total to grow with volume, or a cumulative ceiling that spans multiple invoices over a contract period. Each requires a different check. A single PO cap is visible if AP compares the invoice to the PO.

A cumulative cap requires someone to track a running total across every invoice tied to that contract, which is the part a line-by-line invoice review does not do by default.

Because the cap is a negotiated term and not a system default, it exists only where someone wrote it into the contract and someone else remembered it applies.

2. How does an invoice cross the cap without being stopped?

Three-way matching checks the invoice against the purchase order and the goods or service receipt. It does not test whether a cumulative billed total, tracked separately across several invoices, has passed the ceiling stated in the contract. If the cap lives in a PDF outside the ERP, the match has nothing to compare the running total against, so an invoice that clears the ceiling still passes every automated check the system runs.

A single overrun invoice can look completely ordinary. The line items match the work performed, the rate matches the rate card, and the PO reference is correct. What is wrong is not visible on that one document: it is the sum of this invoice plus every prior invoice against the same cap.

That sum lives nowhere the matching engine looks unless someone built a separate tracker for it. Spreadsheets used for this purpose drift out of date as soon as an invoice is approved outside the process that updates them, which is a common way the tracker itself becomes the point of failure rather than the invoice.

The overrun is also easy to miss because it does not require the vendor to do anything unusual. Continuing to bill for continuing work is the vendor's default behavior. The obligation to stop at the cap sits with the buyer's approval process, not with the vendor's billing system.

3. Is not-to-exceed overrun common in mid-market manufacturing?

There is no dataset that measures how often NTE overrun occurs across mid-market manufacturers, so no honest answer states a rate or calls it common or rare. What can be said is conditional: overrun risk rises with the number of active NTE clauses a company carries and falls close to zero if every clause is tracked against a running total that AP checks before each invoice is approved. The right question is not how common it is elsewhere, but whether.

A claim about frequency across companies would need a survey of contracts and invoices this engine does not have and will not estimate. Any answer that states a rate, a share, or a ranking against other drift types would be inventing a number to fill a real gap in the reader's question.

What is answerable is the condition that creates exposure. A company with no cumulative NTE clauses in its vendor contracts has no overrun risk of this kind, by definition. A company with several such clauses, tracked only informally, carries exposure that scales with how many of those clauses exist and how long the associated projects run.

The useful move is to count your own exposure rather than look for an industry rate. Pull every active contract with a not-to-exceed clause, note whether the cap is a single PO or a cumulative figure, and check whether a running total is maintained anywhere. That count is the actual answer for your company, and it is one no external benchmark could give you even if one existed.

4. Which contract types carry the most exposure?

Not-to-exceed clauses appear in engagements where scope is hard to fix in advance: contract labor and staffing, maintenance and repair work, and IT or professional services billed by phase or hour. Each carries the clause for a different reason, so each needs a different tracking approach rather than one generic control applied uniformly across every vendor category.

The three categories below share the same underlying exposure, an evolving scope paired with a fixed dollar ceiling, but the point at which the ceiling gets crossed differs enough that a single tracking method will not fit all three.

A. Contract labor and staffing

Staffing engagements are often billed hourly against a project budget with a stated ceiling. The cap covers the whole engagement, so tracking it means summing timesheets and invoices across the full duration, not checking one invoice against one PO.

B. Maintenance and repair

A repair job can be quoted with an NTE ceiling that covers labor and parts together, set before the full extent of the repair is known. Additional damage found mid-repair should trigger a new approval, not a silent continuation past the original cap.

C. IT and professional services

Phased projects often carry a cap per phase and sometimes a separate cap for the whole engagement. A cumulative check has to track both levels, since a phase can stay under its own cap while the project total still crosses the contract ceiling.

5. Can a control catch this before payment instead of after?

Yes, but it requires a register, not a review habit: every active NTE clause recorded against its governing PO or contract, with a running total updated at each invoice and checked against the cap before approval. Three-way matching alone cannot do this because the cap is not a field the matching engine reads. The control has to sit outside that match and feed a stop signal into it.

Building the register starts with pulling every contract that contains a not-to-exceed term and recording three things: the cap value, whether it applies per invoice or cumulatively, and the PO or vendor it governs. This is a one-time inventory task, not an ongoing burden, once it exists.

The running check is the part that has to be maintained. Each new invoice against a capped contract needs its amount added to the running total before approval, and the total compared to the cap. Where the volume of capped contracts is small, this can be a maintained spreadsheet. Where it is not, it needs to live in a system that updates automatically as invoices post.

The payoff is that the check happens before the payment, not during a later audit. A retrospective review can recover an overrun that already happened. A running-total check at approval time can stop the invoice before the overrun exists at all.

6. What should you check in your own contracts this week?

Pull every active contract, purchase order, and change order that references a not-to-exceed, ceiling, or cap term, and note whether each is tracked anywhere against a running total. Cross-reference that list against invoices paid in the last twelve months on the same vendor and PO. Any contract with no tracker and more than one invoice against it is worth checking by hand before assuming it is fine.

Start with the vendor categories most likely to carry the clause: contract labor and staffing, maintenance and repair, and IT and professional services. A search of contract files for the terms not to exceed, NTE, or ceiling will surface most of them quickly.

For each one found, ask whether the cap is per invoice or cumulative. A per-invoice cap is checkable by anyone comparing that single invoice to that single PO. A cumulative cap needs the running total, and if no one can produce that total on request, the control does not currently exist for that contract regardless of what the contract says.

This inventory answers the only version of the frequency question that matters: not how common the overrun is across the industry, but how exposed your own vendor base is right now, and it does so with information you already have.

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

7. Frequently Asked Questions (People Also Ask)

What is a not-to-exceed overrun exactly?

It is an invoice, or a sequence of invoices, that bills more than the ceiling a contract sets on a project, rate, or cumulative spend. The cap is a negotiated contract term, and the overrun is the gap between that cap and what was actually billed and paid.

Does three-way matching catch NTE overruns?

No. Three-way matching checks an invoice against its purchase order and receipt. It does not track a cumulative total across multiple invoices against a separate cap value written into a contract, which is where a cumulative NTE overrun actually occurs.

How common is NTE overrun across manufacturers?

There is no dataset that measures this across companies, so no honest source states a rate. What determines your exposure is how many active NTE clauses your contracts carry and whether a running total is tracked against each one.

Which vendor categories are most likely to have NTE clauses?

Contract labor and staffing, maintenance and repair, and IT and professional services commonly use the clause because their scope is hard to fix in advance. Each needs its own tracking approach since the cap structure differs by category.

Can an NTE overrun be recovered after payment?

Sometimes, depending on the contract language and vendor relationship, but recovery after the fact is harder than preventing the overrun at approval. A recovery conversation starts from a weaker position than a running-total check that stops the invoice before it posts.

What is the difference between a per-invoice cap and a cumulative cap?

A per-invoice cap limits one bill and is visible by comparing that invoice to its purchase order. A cumulative cap limits a total across many invoices over a contract period, and requires a running total maintained outside the standard invoice-to-PO match.

Who is responsible for stopping an invoice at the cap?

The obligation sits with the buyer's approval process, not the vendor's billing system. A vendor continuing to bill for continuing work is normal behavior; stopping at the contract ceiling requires the buyer to check the running total before approving.

Where should a company start if it suspects NTE overruns?

Pull every contract containing a not-to-exceed or ceiling term, note whether it is tracked anywhere, and cross-reference against the last twelve months of invoices on the same vendor and PO. Untracked cumulative caps with multiple invoices are the ones worth checking by hand first.

Is an NTE overrun the same as billed scope beyond contract?

They are related but distinct. An NTE overrun is a ceiling breach on dollar amount or rate. Billed scope beyond contract covers work billed that the contract never authorized at all, regardless of any dollar cap.

Does a not-to-exceed clause need to be in every contract?

No. It applies only where scope is hard to fix in advance and the buyer wants cost certainty. A fixed-price contract with defined deliverables typically has no need for a separate NTE ceiling.