# Recovering money lost to not-to-exceed overrun > How to recover money already lost to not-to-exceed overrun, and how to stop the next one, for $100M+ manufacturers. Part of the ValueXPA margin drift library. Source: https://valuexpa.com/insights/how-do-you-recover-money-lost-to-not-to-exceed-overrun Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A not-to-exceed overrun is one specific shape of that gap: the contract sets a ceiling on a rate, a labor charge or a project total, and the invoice quietly clears it. Recovering the money already spent past that ceiling is a different job from stopping the next one. This page separates the two, because most of the value in an NTE overrun sits in the recovery path, and the prevention path only works once you know what triggered the first breach. ## Executive Summary A not-to-exceed clause caps what a vendor may bill for a defined scope, rate or project. Recovery starts with proving the cap existed, proving the invoice crossed it, and then deciding whether the money is collectable now or only preventable going forward. Those are separate questions, and skipping the first one is the most common reason a legitimate overrun claim goes nowhere with a vendor. The mechanism that causes the overrun is almost always a mismatch between two documents that were never compared: the signed contract or purchase order carrying the cap, and the invoice or change order that billed past it. AP systems match invoices to purchase orders and receipts. They do not typically carry the NTE value itself as a field to check against, so the overrun clears three-way matching cleanly. What changes it is treating the NTE clause as a rule to test against every invoice line, not a term to remember. That means pulling the contract language, quantifying the gap per invoice, and routing the claim to the vendor with the clause cited. Where the invoice is old enough that the credit window has closed, the same evidence becomes a prevention control instead of a recovery claim. ## 1. What does a not-to-exceed overrun actually look like on an invoice? **A not-to-exceed overrun looks like an ordinary invoice line that happens to sit above a ceiling written into the contract or purchase order: a capped hourly rate, a capped project total, or a capped monthly service fee. The invoice itself gives no signal anything is wrong. It only becomes visible when someone lines the billed amount up against the contract clause that set the limit, line by line, invoice by invoice.** The overrun can appear as a single spike, a change order that quietly resets the cap without a new signature, or a slow creep where labor hours or material lines accumulate past the ceiling over several invoice cycles. Each version reads as routine to an approver who is checking the invoice against the purchase order and the delivery record, not against the underlying contract. That is the structural reason it survives normal AP review: purchase order matching confirms quantity and unit price against what was ordered, not against a cap that lives in a separate contract document. The NTE clause has to be pulled out and tested on its own. ## 2. How do you recover money already lost to a not-to-exceed overrun? **Recovery has four steps: locate every contract or purchase order carrying an NTE clause, match each one against the invoices billed under it, quantify the dollar gap between the cap and the billed amount, and present the finding to the vendor with the clause cited and the invoice numbers attached. Vendors typically process a documented overrun as a credit memo once the contract language and the arithmetic are both unambiguous.** The step most engagements skip is the first one: building a complete list of which contracts even carry a not-to-exceed clause. Without that list, review defaults to whichever invoices look unusual, which misses the overruns hidden inside invoices that otherwise look ordinary. Once the list exists, the match is mechanical: cap value against billed value, invoice by invoice, for the full period the contract has been active. Anything already outside a vendor's credit or dispute window is not recoverable as cash; it still has value as evidence for the next clause negotiation. The claim itself should cite the contract section and the specific invoices, not a general complaint about pricing. A vendor working from precise references settles faster than one asked to investigate a vague concern. ## 3. Why does the overrun clear AP review before anyone catches it? **Three-way matching checks the invoice against the purchase order and the goods or service receipt; it does not test whether the billed amount stayed under a not-to-exceed ceiling, because that ceiling is a contract term, not a purchase order field. An invoice can match its PO exactly, receive full approval, and still exceed a cap that was never loaded into the matching system in the first place.** This is a gap in what the control checks, not a failure of the person running it. Standard AP workflows are built to confirm that what was ordered is what arrived and what was billed. A not-to-exceed clause is a separate, contract-level constraint that sits outside that three-way relationship entirely. Closing the gap means adding the NTE value as a field the system, or a reviewer, actually checks: a line item in the purchase order record, a threshold in an AP automation rule, or a manual step at invoice approval. Until that field exists somewhere in the workflow, the invoice will keep clearing. ## 4. Which contract types carry not-to-exceed clauses worth checking? **Not-to-exceed clauses appear most often in categories billed on variable inputs rather than a fixed unit price: contract labor and staffing, maintenance and repair work billed by hour and part, IT and professional services engagements, and any project-based scope with a capped total. Each of these bills against a rate or a total that only makes sense with a ceiling attached, which is exactly what makes the ceiling easy to bill past.** Contract labor and staffing agreements typically cap either an hourly bill rate or a total engagement value, and both are vulnerable to a rate that creeps upward across renewal cycles without a new signed cap. Maintenance and repair invoices carry the same risk on labor hours and parts markups against a project ceiling. - **Contract labor and staffing:** Bill rates and total engagement value are the two figures most often capped, and both drift upward across renewals. - **Maintenance and repair:** Labor hours and parts markups against a project or annual ceiling are easy to bill past without a new invoice looking unusual. - **[IT and professional services](/glossary/it-and-professional-services-audit):** Statements of work commonly cap a project total or a monthly run rate that change orders can reset without new signatures. - **Capped facilities and janitorial contracts:** Recurring service agreements sometimes cap a monthly fee that step-up clauses or added scope quietly exceed. ## 5. Can you recover the money if the invoice is already a year old? **It depends on the vendor's own credit and dispute window, which is a contract term, not a fixed rule, so the honest answer is to check that clause before assuming the claim is dead. Where the window has closed, the invoice still has value: it documents exactly how the cap was breached and becomes the basis for tightening the clause or the review process before the next renewal.** Some vendor contracts set an explicit period for disputing a billed amount, often tied to the same section that sets the NTE cap itself. Reading that clause first avoids wasting effort on a claim the vendor is contractually entitled to refuse. When the window is closed, the finding converts from a recovery claim into a control fix: add the NTE value to the approval workflow, flag the vendor's contract for renegotiation at renewal, or require a signed change order before any cap adjustment. The dollar amount is gone, but the mechanism that let it through is not. ## 6. How do you stop the next not-to-exceed overrun instead of just finding the last one? **Prevention means putting the not-to-exceed value somewhere the invoice actually gets checked against it, before payment rather than after: a field in the purchase order record, a rule in AP automation, or a manual hold at approval for any invoice on a capped contract. Recovery finds what already happened; prevention changes what the workflow tests going forward, and the two require different work.** AP automation software is well suited to enforcing a rule once that rule is known and correctly configured. It cannot discover on its own that a given contract carries a cap, because that fact lives in a PDF, not in the ERP. Someone has to read the contract and hand the software the number. That is the sequencing question worth being explicit about: an audit of existing contracts and invoices establishes which caps exist and how they have already been breached. Only then does it make sense to configure a forward control against them, because a control built before the rules are known enforces whichever rules were guessed. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [what is margin erosion? causes and prevention for manufacturers](/guides/what-is-margin-erosion-causes-and-prevention-for). ## 7. Frequently Asked Questions (People Also Ask) ### What is a not-to-exceed clause in a service contract? It is a ceiling written into the contract, purchase order or statement of work that caps a rate, a labor charge or a total project cost. The vendor may bill up to that figure but not past it without a new signed agreement. ### How do you find out which of our contracts have a not-to-exceed cap? Pull every active service contract, purchase order and statement of work and search the terms for a stated ceiling on rate, hours or total value. There is no shortcut around reading the documents; the cap is contract language, not a field most ERPs store. ### Does three-way matching catch a not-to-exceed overrun? No. Three-way matching confirms the invoice agrees with the purchase order and the receipt. It does not test the invoice against a contract-level cap, because that cap is not one of the three documents the match compares. ### Is a not-to-exceed overrun the same thing as a rate card violation? They are related but distinct. A rate card violation bills a different unit price than the contract states. An NTE overrun bills correctly on a per-unit basis but exceeds a total or ceiling figure set separately in the contract. ### What evidence does a vendor need to process an NTE overrun credit? The specific contract section stating the cap, the invoice numbers that exceeded it, and the dollar calculation of the gap. A precise, documented claim moves faster than a general dispute of the invoice amount. ### Can an NTE overrun happen even if every invoice matched its purchase order? Yes. A purchase order can be issued for an amount that itself exceeds the contract's cap, or change orders can raise the PO value without a new signature against the original cap. Matching the invoice to the PO does not confirm the PO itself respected the cap. ### Should we renegotiate the not-to-exceed clause once we find an overrun? That depends on why the breach happened. If the cap was reasonable and simply unenforced, fix the review process. If the scope genuinely outgrew the original cap, renegotiating the clause at renewal is the more durable answer than repeatedly disputing invoices against a stale number. ### How far back should we look for not-to-exceed overruns? Look back across the full period the current contract or its predecessor has been active, since caps often carry over renewal to renewal. Where a vendor's dispute window has already closed on older invoices, the review still has value for prevention even if it produces no credit. ### Who inside the company should own catching this going forward? Whoever owns invoice approval for the contract needs the cap value in front of them at approval time, whether that is an AP team member with the contract on file or a rule inside the AP automation system. Ownership has to sit at the point of payment, not after. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary A not-to-exceed clause caps what a vendor may bill for a defined scope, rate or project. Recovery starts with proving the cap existed, proving the invoice crossed it, and then deciding whether the money is collectable now or only preventable going forward. Those are separate questions, and skipping the first one is the most common reason a legitimate overrun claim goes nowhere with a vendor. The mechanism that causes the overrun is almost always a mismatch between two documents that were never compared: the signed contract or purchase order carrying the cap, and the invoice or change order that billed past it. AP systems match invoices to purchase orders and receipts. They do not typically carry the NTE value itself as a field to check against, so the overrun clears three-way matching cleanly. What changes it is treating the NTE clause as a rule to test against every invoice line, not a term to remember. That means pulling the contract language, quantifying the gap per invoice, and routing the claim to the vendor with the clause cited. Where the invoice is old enough that the credit window has closed, the same evidence becomes a prevention control instead of a recovery claim. ## 1. What does a not-to-exceed overrun actually look like on an invoice? A not-to-exceed overrun looks like an ordinary invoice line that happens to sit above a ceiling written into the contract or purchase order: a capped hourly rate, a capped project total, or a capped monthly service fee. The invoice itself gives no signal anything is wrong. It only becomes visible when someone lines the billed amount up against the contract clause that set the limit, line by line, invoice by invoice. The overrun can appear as a single spike, a change order that quietly resets the cap without a new signature, or a slow creep where labor hours or material lines accumulate past the ceiling over several invoice cycles. Each version reads as routine to an approver who is checking the invoice against the purchase order and the delivery record, not against the underlying contract. That is the structural reason it survives normal AP review: purchase order matching confirms quantity and unit price against what was ordered, not against a cap that lives in a separate contract document. The NTE clause has to be pulled out and tested on its own. ## 2. How do you recover money already lost to a not-to-exceed overrun? Recovery has four steps: locate every contract or purchase order carrying an NTE clause, match each one against the invoices billed under it, quantify the dollar gap between the cap and the billed amount, and present the finding to the vendor with the clause cited and the invoice numbers attached. Vendors typically process a documented overrun as a credit memo once the contract language and the arithmetic are both unambiguous. The step most engagements skip is the first one: building a complete list of which contracts even carry a not-to-exceed clause. Without that list, review defaults to whichever invoices look unusual, which misses the overruns hidden inside invoices that otherwise look ordinary. Once the list exists, the match is mechanical: cap value against billed value, invoice by invoice, for the full period the contract has been active. Anything already outside a vendor's credit or dispute window is not recoverable as cash; it still has value as evidence for the next clause negotiation. The claim itself should cite the contract section and the specific invoices, not a general complaint about pricing. A vendor working from precise references settles faster than one asked to investigate a vague concern. ## 3. Why does the overrun clear AP review before anyone catches it? Three-way matching checks the invoice against the purchase order and the goods or service receipt; it does not test whether the billed amount stayed under a not-to-exceed ceiling, because that ceiling is a contract term, not a purchase order field. An invoice can match its PO exactly, receive full approval, and still exceed a cap that was never loaded into the matching system in the first place. This is a gap in what the control checks, not a failure of the person running it. Standard AP workflows are built to confirm that what was ordered is what arrived and what was billed. A not-to-exceed clause is a separate, contract-level constraint that sits outside that three-way relationship entirely. Closing the gap means adding the NTE value as a field the system, or a reviewer, actually checks: a line item in the purchase order record, a threshold in an AP automation rule, or a manual step at invoice approval. Until that field exists somewhere in the workflow, the invoice will keep clearing. ## 4. Which contract types carry not-to-exceed clauses worth checking? Not-to-exceed clauses appear most often in categories billed on variable inputs rather than a fixed unit price: contract labor and staffing, maintenance and repair work billed by hour and part, IT and professional services engagements, and any project-based scope with a capped total. Each of these bills against a rate or a total that only makes sense with a ceiling attached, which is exactly what makes the ceiling easy to bill past. Contract labor and staffing agreements typically cap either an hourly bill rate or a total engagement value, and both are vulnerable to a rate that creeps upward across renewal cycles without a new signed cap. Maintenance and repair invoices carry the same risk on labor hours and parts markups against a project ceiling. - Contract labor and staffing: Bill rates and total engagement value are the two figures most often capped, and both drift upward across renewals. - Maintenance and repair: Labor hours and parts markups against a project or annual ceiling are easy to bill past without a new invoice looking unusual. - [IT and professional services](/glossary/it-and-professional-services-audit): Statements of work commonly cap a project total or a monthly run rate that change orders can reset without new signatures. - Capped facilities and janitorial contracts: Recurring service agreements sometimes cap a monthly fee that step-up clauses or added scope quietly exceed. ## 5. Can you recover the money if the invoice is already a year old? It depends on the vendor's own credit and dispute window, which is a contract term, not a fixed rule, so the honest answer is to check that clause before assuming the claim is dead. Where the window has closed, the invoice still has value: it documents exactly how the cap was breached and becomes the basis for tightening the clause or the review process before the next renewal. Some vendor contracts set an explicit period for disputing a billed amount, often tied to the same section that sets the NTE cap itself. Reading that clause first avoids wasting effort on a claim the vendor is contractually entitled to refuse. When the window is closed, the finding converts from a recovery claim into a control fix: add the NTE value to the approval workflow, flag the vendor's contract for renegotiation at renewal, or require a signed change order before any cap adjustment. The dollar amount is gone, but the mechanism that let it through is not. ## 6. How do you stop the next not-to-exceed overrun instead of just finding the last one? Prevention means putting the not-to-exceed value somewhere the invoice actually gets checked against it, before payment rather than after: a field in the purchase order record, a rule in AP automation, or a manual hold at approval for any invoice on a capped contract. Recovery finds what already happened; prevention changes what the workflow tests going forward, and the two require different work. AP automation software is well suited to enforcing a rule once that rule is known and correctly configured. It cannot discover on its own that a given contract carries a cap, because that fact lives in a PDF, not in the ERP. Someone has to read the contract and hand the software the number. That is the sequencing question worth being explicit about: an audit of existing contracts and invoices establishes which caps exist and how they have already been breached. Only then does it make sense to configure a forward control against them, because a control built before the rules are known enforces whichever rules were guessed. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [what is margin erosion? causes and prevention for manufacturers](/guides/what-is-margin-erosion-causes-and-prevention-for). ## Common questions ### What is a not-to-exceed clause in a service contract? It is a ceiling written into the contract, purchase order or statement of work that caps a rate, a labor charge or a total project cost. The vendor may bill up to that figure but not past it without a new signed agreement. ### How do you find out which of our contracts have a not-to-exceed cap? Pull every active service contract, purchase order and statement of work and search the terms for a stated ceiling on rate, hours or total value. There is no shortcut around reading the documents; the cap is contract language, not a field most ERPs store. ### Does three-way matching catch a not-to-exceed overrun? No. Three-way matching confirms the invoice agrees with the purchase order and the receipt. It does not test the invoice against a contract-level cap, because that cap is not one of the three documents the match compares. ### Is a not-to-exceed overrun the same thing as a rate card violation? They are related but distinct. A rate card violation bills a different unit price than the contract states. An NTE overrun bills correctly on a per-unit basis but exceeds a total or ceiling figure set separately in the contract. ### What evidence does a vendor need to process an NTE overrun credit? The specific contract section stating the cap, the invoice numbers that exceeded it, and the dollar calculation of the gap. A precise, documented claim moves faster than a general dispute of the invoice amount. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us