Billed scope beyond contract in staffing invoices

Executive Summary

Contract labor invoices pass three-way matching and still bill outside the agreement, because the staffing MSA and the timesheet describe two different things: the MSA sets which labor categories, sites, and shift types are in scope, while the timesheet only proves hours were worked. Nothing in the standard approval path checks the invoice line against the scope table in the agreement, so a supplier can bill an approved timesheet for a role, site, or overtime condition the MSA never authorized, and it clears.

The mechanism is scope drift: a supplier adds a job title, a site, or a billing condition incrementally, each addition looking like a small, reasonable request, until the accumulated set of billed categories no longer matches the signed schedule of rates and roles. Approvers sign off on the hours; nobody re-checks the hours against the scope table because the scope table lives in a contract PDF, not the timesheet system.

What changes it is a control that sits between the timesheet and the invoice: a line-by-line comparison of each billed labor category, site, and rate condition against the MSA's own scope schedule, run at invoice time rather than at contract renewal. Producer Price Index data for employment services shows the underlying billing base is not static, which makes an unmoored scope check more consequential, not less.

1. How does billed scope beyond contract actually happen in a staffing MSA?

A staffing MSA defines scope through a schedule: approved labor categories, approved sites, and the billing conditions attached to each, such as overtime multipliers or shift differentials. The invoice, though, is generated from the timesheet system, which records hours against a job code and a site, not against the MSA's scope schedule. When a supplier staffs a role or site the schedule never listed, the timesheet accepts it, the manager approves the hours worked, and the invoice bills a category.

The MSA's scope schedule is typically a static exhibit: a table of job titles, site codes, and the rate or rate structure attached to each. It is negotiated once, at signing, and rarely touched again unless the contract is renewed.

The timesheet system, by contrast, is built to be flexible. A site manager who needs a new role filled, or needs coverage at a site not yet on the schedule, can usually get a supplier's recruiter to fill it within days. The requisition gets approved operationally, hours get logged, and the invoice follows.

Nowhere in that chain does anyone compare the job code on the timesheet against the job code in the MSA's exhibit. The approval workflow tests whether the hours were worked and whether a manager signed off, not whether the category billed was ever added to the contract.

2. What specific contract mechanism creates this exposure?

The exposure sits in the change-order or addendum clause most staffing MSAs include for adding labor categories or sites, paired with the absence of any invoice-side control that enforces it. The contract requires a written addendum before a new category or site becomes billable. In practice, suppliers and site managers agree verbally or by email, staff the role, and invoice it, and the addendum requirement goes unenforced because nothing at invoice time checks for its existence.

Most MSAs in this category include language stating that any labor category or site not listed in the schedule requires a signed addendum before it becomes billable, and that pricing for the new category will be negotiated at addition. This clause exists precisely to prevent scope from expanding without a rate discussion.

The clause is enforceable only if something checks for the addendum at the point of payment. In practice, AP systems match invoice to purchase order and to approved timesheet, none of which reference the addendum log. A category can be billed for months before anyone notices it was never formally added, and by then the rate charged was never negotiated at all: it was whatever the supplier's timesheet system defaulted to.

3. How is this different from off-contract resources or rate deviations?

Off-contract resources describes a person billed who was never approved to work at all; a labor rate deviation describes an approved person billed at the wrong rate for their own category. Billed scope beyond contract is a third, distinct failure: the category itself, the site itself, or the billing condition itself sits outside what the MSA's schedule defines, even though a real person did real, approved work under it. The person and the hours are legitimate; the scope they were.

These three drift types are easy to conflate because they all surface on the same invoice line and get caught, if at all, by the same review. Keeping them separate matters because the fix is different for each.

An off-contract resource is a headcount problem: someone working who was never vetted or approved under the MSA. A rate deviation is a pricing problem: the right person, the wrong number. Billed scope beyond contract is a scope problem: the category, site, or condition itself was never written into the agreement, so there is no contracted rate to even deviate from.

It has to be caught by comparing the invoice against the MSA's scope schedule, not against a rate card, because the schedule is what defines what may be billed at all.

4. Which billing conditions typically carry this exposure?

Scope drift concentrates in a handful of billing conditions that sit outside the base labor category: overtime multipliers applied to shifts the schedule never classified as eligible, shift differentials billed at a new site, on-call or standby charges the MSA never priced, and temp-to-perm conversion fees triggered without the notice period the contract requires. Each is a condition layered on top of an otherwise ordinary labor line, which is exactly why it clears review without a second look.

Each of these conditions rides on top of a timesheet entry that otherwise looks routine, which is why they survive standard review. The base hours are correct; the condition attached to them is what falls outside the schedule.

• Overtime eligibility: A shift billed at an overtime multiplier when the MSA's schedule never classified that site or role as overtime-eligible.
• Shift differentials: A night or weekend differential applied at a site the schedule does not list as carrying one.
• On-call and standby charges: A billing condition with no corresponding rate in the MSA at all, invoiced because the timesheet system has a code for it.
• Conversion fees: A temp-to-perm conversion fee charged without the notice period or tenure threshold the MSA requires before the fee applies.

5. Can three-way matching catch billed scope beyond contract?

No. Three-way matching checks the invoice against the purchase order and the approved timesheet; it does not test the timesheet's job code, site, or billing condition against the MSA's own scope schedule, because that schedule lives in a contract document, not in the PO or timesheet system. A line can match its PO and its approved hours perfectly and still bill a category, site, or condition the contract never authorized.

This is a structural gap, not a lapse by any one reviewer. Three-way matching exists to confirm that what was ordered, what was worked, and what was billed agree with each other. All three of those documents can agree while still describing something the underlying contract never priced.

Closing it requires a fourth comparison: invoice line against the MSA's scope schedule and any signed addenda. That comparison has to be run against the contract document itself, not against the PO or timesheet, because the PO and timesheet were generated downstream of the same operational agreement that created the drift in the first place.

6. How do you stop billed scope beyond contract from recurring?

Stopping it requires a control that runs at invoice time: every billed job code, site, and billing condition checked against the MSA's current scope schedule and addendum log before payment, not a periodic contract review. A retrospective audit finds and recovers what already leaked. A forward control tests the next invoice against the schedule before it pays, closing the gap between what the contract authorizes and what the timesheet system will happily generate.

The retrospective step comes first: pull the MSA's scope schedule and every signed addendum, and compare it line by line against a sample of recent invoices to find categories, sites, or conditions billed without a matching authorization. This finds what has already leaked and quantifies it.

The forward step is what prevents recurrence: a standing rule that checks each new invoice's job codes and sites against the current schedule before the invoice clears for payment, flagging anything not on it for review rather than paying it by default. This does not require replacing the timesheet system. It requires the scope schedule to be an active reference at invoice time instead of a document read once at signing and never again.

Producer Price Index data for employment services (US Bureau of Labor Statistics, read 2026-09-06) put the July 2026 index for the industry at 175.559, up 5.3% year over year, which means the underlying cost base a staffing MSA prices against is moving. A scope schedule negotiated a year ago is already priced against conditions that have shifted, which makes checking invoices against that schedule, rather than assuming it still fits, a live financial question and not a compliance formality.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

Is billed scope beyond contract the same as an off-contract resource?

No. An off-contract resource is a person working who was never approved under the MSA at all. Billed scope beyond contract involves an approved, real worker whose job category, site, or billing condition was never added to the contract's scope schedule. The person is legitimate; the scope they were billed under is not.

Who is responsible for catching this, AP or the site manager?

Neither, under most current workflows. The site manager approves hours worked, and AP matches invoice to PO and timesheet. Catching scope drift requires comparing the invoice against the MSA's own scope schedule, a document neither AP nor the site manager routinely reference at invoice time.

Does a signed addendum always exist when a new category gets billed?

It should, under most MSA change-order clauses, but the clause is only as strong as the enforcement behind it. If nothing checks for the addendum at invoice time, a category can be billed for months on a verbal or email agreement with no addendum on file.

Can this happen even if every timesheet is properly approved?

Yes. Timesheet approval confirms hours were worked and a manager signed off. It does not confirm the job category, site, or billing condition was ever added to the MSA's scope schedule. Approved hours and authorized scope are two separate questions.

What is the difference between this and a labor rate deviation?

A rate deviation bills an approved category at the wrong price. Billed scope beyond contract bills a category, site, or condition that was never in the contract's schedule at all, so there is no contracted rate to deviate from in the first place.

Where do overtime and shift differential errors fit into this?

They are one form this takes: a shift billed at an overtime or differential rate when the MSA's schedule never classified that site or role as eligible for it, because the timesheet system allows the code even though the contract never priced it.

Does this require renegotiating the whole MSA to fix?

No. It requires comparing current invoices against the existing scope schedule and addendum log, then adding a standing check that runs at invoice time. Renegotiation only becomes necessary if the audit finds scope that should be formally added going forward.

How far back should an audit look for this drift type?

Far enough to cover a full contract cycle since the schedule was last updated or an addendum signed, since drift accumulates incrementally and a short window can understate how many categories or sites have gone unauthorized.