# How NTE overruns happen in staffing invoices

> A not-to-exceed cap looks firm on the page. See how contract labor invoices still cross it, and where the break happens. Written for finance and AP teams.

Source: https://valuexpa.com/insights/how-does-not-to-exceed-overrun-happen-in-contract-labor-and
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 clause is one of the plainest promises a staffing agreement makes: total billing on a role or purchase order will not cross a stated dollar ceiling.

Yet NTE overruns are common in contract labor spend, because the cap lives in the contract file and the invoice is generated somewhere else entirely, by a vendor system that was never told the number existed.

## Executive Summary

A not-to-exceed overrun is not usually a vendor trying to overbill. It is a cap that exists in a signed agreement and nowhere in the systems that produce and pay the invoice. The staffing vendor's own billing platform tracks hours against a rate card. It does not know your purchase order has a ceiling unless someone manually enters and maintains that number inside the vendor's tools, on every renewal, for every role.

The mechanism is structural. Timesheets are approved against hours worked and a bill rate, not against a running total compared to a contract limit. Three-way matching in most AP systems checks the invoice against the purchase order amount and the goods or services received. It does not carry forward a cumulative NTE ceiling from the master agreement and flag the invoice that finally crosses it.

What changes it is putting the cap somewhere it gets checked automatically: a running total compared against the PO limit at the point an invoice posts, not months later during a spend review. Until then, the overrun sits in AP history exactly the way a rate deviation does, unflagged because nothing in the workflow was built to flag it.

## 1. What is a not-to-exceed cap in a staffing agreement?

**A not-to-exceed cap is a dollar ceiling written into a staffing agreement or purchase order that limits total billing for a role, project, or period, regardless of hours logged or rate applied. It exists to give the buyer budget certainty on contract labor that is billed by the hour rather than by a fixed fee. The cap is a contract term, not a system control: nothing about the invoicing process enforces it unless someone builds that enforcement separately.**

The cap is typically set at the purchase order level, sometimes per resource and sometimes per statement of work covering several resources at once. It is meant to answer a specific budget question: what is the most this engagement can cost before someone has to approve more.

The number sits in a contract PDF or a PO line item. The staffing vendor's invoicing system operates off a rate card and logged hours. Those two records were never designed to talk to each other, which is the condition every overrun in this category starts from.

## 2. How does an NTE overrun actually occur on a timesheet?

**The overrun happens one approved timesheet at a time. Each week's hours and rate look correct in isolation: the resource worked the hours, the rate matches the card, the approver signs off. No single timesheet exceeds anything. The ceiling is a cumulative figure across the life of the engagement, and cumulative totals are exactly what a week-by-week approval workflow is not built to track.**

A manager approving a weekly timesheet is checking whether the hours are plausible and the rate is the one they remember agreeing to. They are not carrying a running total of every invoice paid against this PO since the engagement started.

That running total lives, if it lives anywhere, in a spreadsheet someone updates manually or does not update at all. By the time an AP recovery audit rebuilds the cumulative figure, the overrun has often been running for several billing cycles, each one individually approved and individually unremarkable.

## 3. Where does approval break down before the overrun reaches AP?

**Approval breaks down at handoff points where the cumulative total against the cap never travels from one document or person to the next: a PO ceiling that is never entered into a tracking system, added scope with no revisited cap, a renewal that carries the total forward unnoticed, and an approver who never saw the original figure. Each is a separate place the number gets lost, and any one of them alone is enough to produce an overrun.**

Each of these is a handoff point, and a handoff is where a number written in one document fails to travel to the next. Purchase order software rarely surfaces a cumulative-versus-cap figure on the approval screen; it shows the current invoice and asks for a yes or no.

Three-way matching, where it exists, checks the invoice against the PO amount and what was received. A PO issued for a large round number to cover an engagement's expected duration will absorb months of overrun before the match itself trips.

- **No cumulative tracker:** The PO ceiling is never entered into a system that sums invoices against it as they post.

- **Scope added without a new cap:** A resource's hours increase, or a second resource is added to the same role, without revisiting the original dollar limit.

- **Renewal resets the clock, not the cap:** A staffing agreement renews annually but the cumulative total carries forward from the prior term unnoticed.

- **Approver changes mid-engagement:** A new manager approves timesheets without ever having seen the original NTE figure.

## 4. What role does bill rate escalation play in NTE overruns?

**A staffing agreement's bill rate is not always fixed for the life of the engagement. Some agreements carry an annual escalation tied to a published wage or cost index for the labor category. When that escalation applies without a matching increase to the not-to-exceed ceiling, the same hours cost more each cycle, and the cumulative total reaches the cap faster than the original budget assumed.**

Employment services costs move over time. The US Bureau of Labor Statistics Producer Price Index for the employment services industry group put its July 2026 index at 175.559, up 5.3% year over year (read 2026-09-07). A staffing rate tied to that kind of index, or to a comparable published benchmark, rises even when nobody at either company renegotiates anything.

The original NTE figure was set against the rate in effect when the agreement was signed. If the cap was never revisited alongside the escalation clause, the ceiling and the rate are now out of step, and the overrun is a direct consequence of a rate that changed while the cap did not.

## 5. How can you catch an NTE overrun before it becomes an invoice?

**Catching an overrun before it posts requires the cumulative total, the PO ceiling, and the invoice to reference the same running number at the moment of approval. A hard cap on a single invoice, a cumulative cap across the PO, and a bare rate cap each guard against a different failure and leave a different one exposed, which is why the type of cap written into the agreement matters as much as its dollar amount.**

Catching the overrun before it posts means the cumulative total has to sit somewhere a person or a system checks at the moment of invoice approval, not during a periodic audit months later. That requires the PO ceiling, the rate card, and the invoice to reference the same running number.

Without that, the earliest realistic catch point is a scheduled review of open POs against invoices paid to date, compared line by line rather than by total spend. This is slower than a system check, but it is faster than discovering the overrun during an annual audit, by which point the amount at stake is larger and harder to recover.

Three ways an NTE limit is commonly structured, and what each one leaves unchecked.

| Cap type
| What it limits
| What it typically misses

| Hard cap per invoice
| A single invoice cannot exceed a stated amount
| A cumulative total across many invoices can still exceed the PO

| Cumulative cap per PO
| Total billing across the PO's life
| Nothing tracks the running total unless someone builds that tracker

| Rate cap only, no dollar ceiling
| The rate charged per hour
| Hours worked can grow without limit, so total cost is unbounded

## 6. What should you do once an NTE overrun has already been paid?

**Once an overrun has been invoiced and paid, the first step is establishing the cumulative total against the original PO, not the amount of any single invoice. The overrun is only visible when every invoice tied to that PO is summed, so the reconciliation has to pull the full billing history for the engagement, not a sample of recent invoices, before anyone can size what happened.**

The reconciliation should compare the cumulative invoiced total against the NTE figure in the signed agreement or PO, then separate the overage into two questions: was the cap breached because of unauthorized scope, or because the rate escalated without a corresponding cap revision.

That distinction matters for the recovery conversation with the vendor. An unauthorized scope addition is a different discussion than a rate that moved under a clause both parties agreed to. Either way, the fix going forward is the same: the cumulative total needs a home that gets checked before the next invoice posts, not after.

For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

## 7. Frequently Asked Questions (People Also Ask)

### Is a not-to-exceed overrun the vendor's fault or the buyer's?

Neither party necessarily did anything wrong. The staffing vendor's billing system tracks hours and rate, not your PO ceiling. The overrun happens because nobody built a system that compares the running invoice total to the cap before payment, which is a gap in process on the buyer's side as much as anything the vendor did.

### Can a not-to-exceed clause be added retroactively to an existing staffing PO?

A cap can be added to a future term or renewal, but it cannot be applied to invoices already paid. Adding one going forward requires updating the PO in whatever system generates it and giving the approver visibility into the cumulative total, not just the current invoice.

### Does three-way matching catch NTE overruns automatically?

Three-way matching checks an invoice against the purchase order amount and what was received. It does not carry forward a cumulative total across multiple invoices against a life-of-engagement cap unless that cumulative figure is built into the matching logic separately.

### How far back should we check for NTE overruns in contract labor?

Check as far back as the current PO or master agreement term extends, since the cumulative total only means something measured across the full life of that agreement. A partial history undercounts the overage because it misses invoices from earlier in the term.

### What is the difference between an NTE overrun and a rate deviation?

A rate deviation is a single invoice billed at the wrong rate against the rate card. An NTE overrun is a cumulative total across many invoices, each individually correct on rate, that together cross the agreement's dollar ceiling. See labor rate deviations for how the rate-level version of this problem is checked.

### Does adding a second resource to the same role affect the NTE cap?

It can. If the original cap was set assuming one resource's hours and a second resource is added to the same PO without revisiting the ceiling, the cumulative total against that PO now grows faster than the cap anticipated.

### Should the NTE cap be revised when a staffing rate escalates under contract?

That is a fair question to raise with the vendor when the agreement includes a rate escalation clause. If the cap stays fixed while the rate rises, the same hours consume the ceiling faster, and the cap effectively shrinks in real terms even though the number on the page has not changed.

### Can an NTE overrun be recovered after the invoices are paid?

Recovery depends on what the agreement's overrun and audit rights language allows, and on whether the overage traces to unauthorized scope versus a permitted rate escalation. A formal audit against the original agreement is the starting point for that conversation, not an assumption either way.

### 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 overrun is not usually a vendor trying to overbill. It is a cap that exists in a signed agreement and nowhere in the systems that produce and pay the invoice. The staffing vendor's own billing platform tracks hours against a rate card. It does not know your purchase order has a ceiling unless someone manually enters and maintains that number inside the vendor's tools, on every renewal, for every role. The mechanism is structural. Timesheets are approved against hours worked and a bill rate, not against a running total compared to a contract limit. Three-way matching in most AP systems checks the invoice against the purchase order amount and the goods or services received. It does not carry forward a cumulative NTE ceiling from the master agreement and flag the invoice that finally crosses it. What changes it is putting the cap somewhere it gets checked automatically: a running total compared against the PO limit at the point an invoice posts, not months later during a spend review. Until then, the overrun sits in AP history exactly the way a rate deviation does, unflagged because nothing in the workflow was built to flag it.

## 1. What is a not-to-exceed cap in a staffing agreement?

A not-to-exceed cap is a dollar ceiling written into a staffing agreement or purchase order that limits total billing for a role, project, or period, regardless of hours logged or rate applied. It exists to give the buyer budget certainty on contract labor that is billed by the hour rather than by a fixed fee. The cap is a contract term, not a system control: nothing about the invoicing process enforces it unless someone builds that enforcement separately. The cap is typically set at the purchase order level, sometimes per resource and sometimes per statement of work covering several resources at once. It is meant to answer a specific budget question: what is the most this engagement can cost before someone has to approve more. The number sits in a contract PDF or a PO line item. The staffing vendor's invoicing system operates off a rate card and logged hours. Those two records were never designed to talk to each other, which is the condition every overrun in this category starts from.

## 2. How does an NTE overrun actually occur on a timesheet?

The overrun happens one approved timesheet at a time. Each week's hours and rate look correct in isolation: the resource worked the hours, the rate matches the card, the approver signs off. No single timesheet exceeds anything. The ceiling is a cumulative figure across the life of the engagement, and cumulative totals are exactly what a week-by-week approval workflow is not built to track. A manager approving a weekly timesheet is checking whether the hours are plausible and the rate is the one they remember agreeing to. They are not carrying a running total of every invoice paid against this PO since the engagement started. That running total lives, if it lives anywhere, in a spreadsheet someone updates manually or does not update at all. By the time an AP recovery audit rebuilds the cumulative figure, the overrun has often been running for several billing cycles, each one individually approved and individually unremarkable.

## 3. Where does approval break down before the overrun reaches AP?

Approval breaks down at handoff points where the cumulative total against the cap never travels from one document or person to the next: a PO ceiling that is never entered into a tracking system, added scope with no revisited cap, a renewal that carries the total forward unnoticed, and an approver who never saw the original figure. Each is a separate place the number gets lost, and any one of them alone is enough to produce an overrun. Each of these is a handoff point, and a handoff is where a number written in one document fails to travel to the next. Purchase order software rarely surfaces a cumulative-versus-cap figure on the approval screen; it shows the current invoice and asks for a yes or no. Three-way matching, where it exists, checks the invoice against the PO amount and what was received. A PO issued for a large round number to cover an engagement's expected duration will absorb months of overrun before the match itself trips. - No cumulative tracker: The PO ceiling is never entered into a system that sums invoices against it as they post. - Scope added without a new cap: A resource's hours increase, or a second resource is added to the same role, without revisiting the original dollar limit. - Renewal resets the clock, not the cap: A staffing agreement renews annually but the cumulative total carries forward from the prior term unnoticed. - Approver changes mid-engagement: A new manager approves timesheets without ever having seen the original NTE figure.

## 4. What role does bill rate escalation play in NTE overruns?

A staffing agreement's bill rate is not always fixed for the life of the engagement. Some agreements carry an annual escalation tied to a published wage or cost index for the labor category. When that escalation applies without a matching increase to the not-to-exceed ceiling, the same hours cost more each cycle, and the cumulative total reaches the cap faster than the original budget assumed. Employment services costs move over time. The US Bureau of Labor Statistics Producer Price Index for the employment services industry group put its July 2026 index at 175.559, up 5.3% year over year (read 2026-09-07). A staffing rate tied to that kind of index, or to a comparable published benchmark, rises even when nobody at either company renegotiates anything. The original NTE figure was set against the rate in effect when the agreement was signed. If the cap was never revisited alongside the escalation clause, the ceiling and the rate are now out of step, and the overrun is a direct consequence of a rate that changed while the cap did not.

## 5. How can you catch an NTE overrun before it becomes an invoice?

Catching an overrun before it posts requires the cumulative total, the PO ceiling, and the invoice to reference the same running number at the moment of approval. A hard cap on a single invoice, a cumulative cap across the PO, and a bare rate cap each guard against a different failure and leave a different one exposed, which is why the type of cap written into the agreement matters as much as its dollar amount. Catching the overrun before it posts means the cumulative total has to sit somewhere a person or a system checks at the moment of invoice approval, not during a periodic audit months later. That requires the PO ceiling, the rate card, and the invoice to reference the same running number. Without that, the earliest realistic catch point is a scheduled review of open POs against invoices paid to date, compared line by line rather than by total spend. This is slower than a system check, but it is faster than discovering the overrun during an annual audit, by which point the amount at stake is larger and harder to recover. Three ways an NTE limit is commonly structured, and what each one leaves unchecked. | Cap type | What it limits | What it typically misses | | --- | --- | --- | | Hard cap per invoice | A single invoice cannot exceed a stated amount | A cumulative total across many invoices can still exceed the PO | | Cumulative cap per PO | Total billing across the PO's life | Nothing tracks the running total unless someone builds that tracker | | Rate cap only, no dollar ceiling | The rate charged per hour | Hours worked can grow without limit, so total cost is unbounded |

## 6. What should you do once an NTE overrun has already been paid?

Once an overrun has been invoiced and paid, the first step is establishing the cumulative total against the original PO, not the amount of any single invoice. The overrun is only visible when every invoice tied to that PO is summed, so the reconciliation has to pull the full billing history for the engagement, not a sample of recent invoices, before anyone can size what happened. The reconciliation should compare the cumulative invoiced total against the NTE figure in the signed agreement or PO, then separate the overage into two questions: was the cap breached because of unauthorized scope, or because the rate escalated without a corresponding cap revision. That distinction matters for the recovery conversation with the vendor. An unauthorized scope addition is a different discussion than a rate that moved under a clause both parties agreed to. Either way, the fix going forward is the same: the cumulative total needs a home that gets checked before the next invoice posts, not after. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

## Common questions

### Is a not-to-exceed overrun the vendor's fault or the buyer's?

Neither party necessarily did anything wrong. The staffing vendor's billing system tracks hours and rate, not your PO ceiling. The overrun happens because nobody built a system that compares the running invoice total to the cap before payment, which is a gap in process on the buyer's side as much as anything the vendor did.

### Can a not-to-exceed clause be added retroactively to an existing staffing PO?

A cap can be added to a future term or renewal, but it cannot be applied to invoices already paid. Adding one going forward requires updating the PO in whatever system generates it and giving the approver visibility into the cumulative total, not just the current invoice.

### Does three-way matching catch NTE overruns automatically?

Three-way matching checks an invoice against the purchase order amount and what was received. It does not carry forward a cumulative total across multiple invoices against a life-of-engagement cap unless that cumulative figure is built into the matching logic separately.

### How far back should we check for NTE overruns in contract labor?

Check as far back as the current PO or master agreement term extends, since the cumulative total only means something measured across the full life of that agreement. A partial history undercounts the overage because it misses invoices from earlier in the term.

### What is the difference between an NTE overrun and a rate deviation?

A rate deviation is a single invoice billed at the wrong rate against the rate card. An NTE overrun is a cumulative total across many invoices, each individually correct on rate, that together cross the agreement's dollar ceiling. See labor rate deviations for how the rate-level version of this problem is checked.

---

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