Spotting an NTE overrun on a facilities invoice

Executive Summary

A not-to-exceed clause caps what a vendor can bill for a defined job, work order or billing period without prior written approval. The overrun happens because the invoice and the contract are reconciled by different people on different timelines, often without either one holding the other's number. AP matches the invoice to a purchase order and a receipt.

Nobody on that path holds the NTE figure from the facilities contract, so an invoice that clears the cap looks identical to one that respects it.

The mechanism is structural, not a lapse by one person. A facilities invoice is coded, approved and paid inside AP's own workflow. The NTE figure lives in a contract document that AP may have seen once at signing and never again. Three-way matching checks the invoice against the purchase order and the receipt; it does not test a dollar ceiling that exists only in the contract text.

What changes it is holding the cap as a checkable number against every invoice tied to that job or period, rather than assuming the purchase order already encodes it. That means extracting the NTE figure at contract intake, tracking it against cumulative billing for the job, and flagging the invoice that would push the running total past the ceiling before it pays, not after.

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

A not-to-exceed clause sets a dollar ceiling on what a vendor can bill for a defined scope, usually a single work order, a repair job, or a billing period such as a quarter. It does not cap a rate; it caps a total. A facilities contract can carry several NTE figures at once, one per job type or service line, each requiring separate tracking rather than a single blanket number applied to the whole vendor relationship.

The clause exists because facilities work is hard to price up front. A landscaping contract might set a fixed monthly fee for routine mowing but an NTE figure for storm cleanup, since the scope of a cleanup job is not known until the storm happens. An HVAC service agreement might cap a repair call at a set dollar figure above which the vendor needs written sign-off before continuing work.

Each NTE figure is tied to a specific trigger: a work order number, a date range, or a named event. That specificity is exactly what makes the cap hard to track downstream. The invoice that eventually arrives references a work order number, not the contract clause that capped it, so the connection between the two has to be made by someone, and often nobody is assigned to make it.

2. Why does three-way matching miss an NTE overrun?

Three-way matching checks that the invoice amount, the purchase order amount, and the receipt of goods or services all agree. It does not check whether that agreed amount respects a not-to-exceed clause from the underlying contract, because the NTE figure was never loaded into the purchase order as a field the match can test. The invoice can match its own PO perfectly while still clearing the contract's dollar ceiling.

The purchase order is usually generated from an estimate or a prior approval, not from the contract's NTE clause. If the PO amount and the invoice amount agree, the match clears. Whether that agreed figure actually respects the contract's cap for that job is a separate question the matching system was never built to ask.

This gap widens when a job runs over multiple invoices. A single work order can generate progress billings across several weeks. Each invoice can match its own line item cleanly while the cumulative total across all of them exceeds the cap set for the whole job.

No single invoice trips a flag, because the flag would need to compare a running total against a contract figure, and the AP system is comparing invoice to PO, not invoice to contract.

3. Where does the overrun actually happen on a facilities job?

An NTE overrun on a facilities invoice happens in a small number of recurring situations: scope expands mid-job without a new approval, a single job is split across multiple invoices that individually look small, or a service call escalates from routine to emergency pricing without the cap being re-tested. Each situation produces an invoice that looks ordinary on its own and only reads as an overrun once set against the contract's ceiling for that job.

A repair can grow once the technician is on site and finds additional damage beyond the original estimate. If the contract requires written approval before exceeding the NTE figure and that approval step gets skipped under time pressure, the final invoice bills the full expanded scope with nothing on the invoice itself indicating the cap was crossed.

A. Split billing across invoices

A facilities vendor working a single capped job may issue separate invoices for labor, materials and disposal. Each invoice, reviewed alone, sits well under the cap. Added together against the one work order they all reference, the total clears the NTE figure. AP approving invoices one at a time has no natural point at which it sums them against the job's ceiling.

B. Emergency rate escalation

Many facilities contracts set a lower NTE threshold for standard service calls and a separate, higher one for after-hours or emergency response. When a routine call is reclassified as emergency partway through, the applicable cap changes. The invoice carries the emergency rate but nothing flags which NTE figure should have governed the job.

4. How do you check an invoice against its NTE cap before paying it?

Checking an invoice against a not-to-exceed cap requires holding three pieces of information in one place at approval time: the NTE figure from the contract, the cumulative amount already billed and paid against that same job or period, and the amount on the invoice in front of you. Add the third to the second and compare the sum to the first. If AP does not have all three available at the point of approval, the check cannot happen.

The practical failure is almost always that the second number, cumulative billing to date, does not exist anywhere AP can see it. Each invoice is filed and paid independently. Reconstructing a running total means pulling every prior invoice tied to the same work order or period and adding them by hand, which is not a step built into most AP workflows.

A usable check assigns a job or period identifier to the NTE figure at contract intake, then requires every invoice referencing that identifier to be logged against a running total before approval. The comparison itself is simple arithmetic. The work is in making sure the NTE figure and the running total both exist somewhere AP actually looks.

5. What documentation should an NTE overrun review ask for?

A review of a facilities invoice for NTE overrun should pull the original contract or work order with the NTE clause stated in dollars, every prior invoice tied to the same job or period identifier, and any written approval issued when the cap was exceeded or expected to be. Absence of that approval on an invoice that clears the cap is itself the finding: the clause required sign-off and none exists in the file.

This is a document-gathering exercise before it is an arithmetic one. Most facilities contracts sit in a shared drive or a vendor management file separate from the AP system entirely, so the first obstacle is locating the clause at all.

Once gathered, the review is mechanical: total the billing history, compare it to the NTE figure, and check whether an approval exists for any invoice that pushed the total past the cap. A missing approval on a job that cleared its ceiling is the finding itself, independent of whether the amount was ultimately justified by the work performed.

1. The governing clause: Pull the contract page stating the NTE figure in dollars, the scope it applies to, and the date range or trigger event it covers.
2. The full billing history: Gather every invoice referencing the same work order or period identifier, not just the one under review, and total them.
3. Any written approval: Check for the sign-off the contract requires before billing can exceed the cap, and note its date relative to the work performed.
4. The scope description: Compare what the invoice describes against the original job scope to see whether the work expanded without a matching approval.

6. Can a facilities NTE overrun be prevented, not just caught after the fact?

Prevention means testing the cumulative total against the NTE figure at the point an invoice is submitted, not during a later audit. That requires the contract's NTE figure to be captured as a structured field at intake, tied to a job or period identifier, and checked automatically as each invoice against that identifier arrives. Without that structure, prevention depends on someone remembering to check manually, which is not a control.

It is a hope.

A forward control differs from a periodic audit in what question it asks and when. A periodic audit reviews a sample of closed jobs after payment and asks whether the cap was respected. A forward control asks the same question of every invoice, before it pays, against a running total that already includes everything billed so far on that job.

Building that control does not require new software by itself. It requires the NTE figure to exist somewhere AP checks routinely, attached to an identifier that every subsequent invoice on the same job also carries. Where that structure is missing, the diagnostic work is establishing it: locating every active facilities contract's NTE clauses, assigning identifiers, and reconciling billing to date before any forward control can run against clean data.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and duplicate freight billing and the multi-carrier consolidation problem.

7. Frequently Asked Questions (People Also Ask)

What is a not-to-exceed clause on a facilities contract?

It is a dollar ceiling on what a vendor can bill for a defined job, work order or billing period without prior written approval. It caps a total amount, not a rate, and a single contract can carry several separate NTE figures across different service lines.

Why doesn't AP catch an NTE overrun during normal invoice approval?

AP's approval workflow runs three-way matching between the invoice, the purchase order and the receipt. The NTE figure lives in the contract, not in the PO, so nothing in that match tests whether the billed amount respects the ceiling the contract sets.

Can a purchase order encode the NTE cap automatically?

Only if someone enters it there deliberately. A PO is typically generated from an estimate or a prior approval, not pulled from the contract's NTE clause, so the cap has to be loaded in as a separate step or it never appears in the match at all.

How do multiple invoices on one job cause an overrun that no single invoice shows?

A capped job can generate several invoices over time for labor, materials or progress billing. Each one can look ordinary reviewed alone. Only the sum of all of them against the job's single NTE figure reveals that the cumulative total has cleared the cap.

What should trigger a written approval on a facilities job?

The contract's own NTE clause should state the trigger, usually the point where cumulative billing on a job or period is projected to exceed the stated ceiling. Any invoice that crosses that line without a matching approval on file is the finding, regardless of whether the underlying work was legitimate.

Does an emergency service call change the applicable NTE cap?

It can. Many facilities contracts set separate NTE thresholds for standard versus after-hours or emergency response. If a call is reclassified mid-job, the cap that should govern it changes too, and the invoice rarely states which threshold was actually applied.

Who should own tracking cumulative billing against an NTE figure?

Ownership has to sit with whoever processes invoices against that job or period identifier, since the contract owner is rarely in the invoice approval path. Without an assigned owner, the running total is reconstructed after the fact, if at all.

Is an NTE overrun the same thing as a duplicate payment?

No. A duplicate payment is the same invoice or charge paid twice. An NTE overrun is a single, otherwise valid set of invoices whose combined total exceeds a contractual ceiling. Both are margin drift, but they require different documentation to catch.

What's the first step to prevent NTE overruns going forward?

Extract every active facilities contract's NTE figures into a structured field tied to a job or period identifier, so every future invoice referencing that identifier can be checked against a running total before it pays, rather than reconstructed later.