Common mistakes auditing contract labor invoices

Executive Summary

The recurring failure in contract labor audits is treating the bill rate as the whole contract. A staffing MSA usually encodes a pay rate, a markup, an overtime multiplier, a burden rate for statutory costs, and a set of labor category definitions tied to skill level. An invoice can be arithmetically correct on the bill rate line and still bill the wrong category, apply the wrong multiplier, or keep billing for a worker who rolled off the engagement weeks earlier.

The mechanism behind this is approval design, not vendor intent. Timesheet sign-off happens at the manager level, where the question asked is "did this person work these hours," not "does this labor category match the requisition" or "did the markup reset after the rate escalation clause expired." Those are contract questions, and the person approving the timesheet is rarely the person holding the contract.

What changes it is separating the two checks: one person confirms hours worked, a second process reconciles the invoice's category codes, multipliers, and headcount against the signed MSA and the current requisition list. The sections below give the specific fields to pull for that second check.

1. Why does checking the bill rate alone miss most of the drift?

A staffing invoice's bill rate is a calculation, not a single negotiated number: pay rate plus markup plus any overtime or shift multiplier. Checking only the final bill rate against the rate card confirms the output but not the inputs. A markup applied to the wrong pay-rate tier, or an overtime multiplier applied to hours that were straight time, produces a bill rate that can still land inside a plausible range while being contractually wrong.

The fix is to pull the invoice's rate calculation apart into its components before comparing anything to the rate card. That means the pay rate line, the markup percentage, and the multiplier applied to any hours coded as overtime, holiday, or shift differential, each checked against the MSA's stated formula rather than against the final number alone.

This matters most where the MSA defines markup as a percentage of pay rate rather than a flat bill rate, because a pay-rate change on the vendor's side, a raise or a shift to a different worker, changes the bill rate automatically and correctly, while a markup percentage change does not, and is the one that needs catching.

A concrete check: recompute the bill rate from pay rate and markup for a sample of line items each cycle, rather than comparing the invoice's stated bill rate to last cycle's stated bill rate. Comparing an invoice to itself over time confirms consistency, not correctness against the contract.

Where a bill-rate check and a component check catch different things.

2. What happens when a timesheet gets approved without checking the labor category code?

A manager approving a timesheet confirms hours, not the labor category the hours were billed under. MSAs typically define several labor categories at different bill rates for the same general role, such as junior and senior technician. A worker performing junior-level work billed under a senior category code produces a fully signed timesheet and an invoice that is still wrong, because the approval never tested the category field at all.

The category code sits on the invoice line, usually as an abbreviation or an internal vendor code, and it maps to a specific bill rate in the MSA's rate schedule. Verifying it means holding the requisition that requested the worker, which states the intended category, next to the invoice line, which states the billed category. Those two documents rarely get compared because they sit with different people: the hiring manager holds the requisition, AP holds the invoice.

A concrete check: for any worker on the account longer than one billing cycle, confirm the category code on the invoice still matches the requisition, not just the first invoice. Vendors reclassify workers into higher categories after a performance review or a scope change without a corresponding contract amendment, and the invoice is the only place that reclassification shows up before it compounds across months.

• Requisition category: The role and skill level the hiring manager actually requested, stated in the original staffing request.
• Invoice category code: The abbreviation on the billing line, which maps to a specific rate in the MSA's schedule and can drift from the requisition unnoticed.
• Amendment trail: Any signed change to the category should have a dated amendment. A category change with no amendment is a finding, not a judgment call.

3. How do rolled-off workers keep appearing on invoices?

When a contractor's assignment ends, the offboarding notice usually goes to the hiring manager and to badge or system access, not automatically to the vendor's billing system. A worker removed from the building can still be on the vendor's active roster, and the invoice keeps a line item running until someone on the client side notices the name. Nothing about that invoice line is fraudulent; it is simply unreconciled.

The check that catches this is a headcount reconciliation, run on its own schedule separate from the rate audit: pull the current active roster from the vendor's invoice, and pull the current active roster from internal records, badge access or the ticketing system the contractor used, and compare names.

Workers who appear on the invoice but not in internal activity records for the billing period are the finding. The gap between an offboarding date and the last billed date is the exposure window, and it can run for a full billing cycle or more if the reconciliation only happens at contract renewal instead of every cycle.

This check works independently of category or rate accuracy. A worker billed at the exact right rate, in the exact right category, who left the company three weeks ago, is still a finding, and it is one that a rate-card comparison will never surface because the rate on that line is correct.

4. Why does a signed MSA not guarantee the invoice matches it?

A signed master service agreement states the terms once, but staffing invoices are generated by a different system, often the vendor's own payroll and billing platform, on a recurring cycle. Nothing forces that system to re-check itself against the MSA every time it runs. Rate escalation clauses, markup caps, and burden rate terms live in a document the invoicing system never reads, so a term can lapse or change without the invoice ever reflecting it.

Two clauses cause most of the drift between what the MSA says and what the invoice does: the rate escalation clause, which sets when and how much a bill rate can rise, and the burden rate term, which sets how statutory costs are folded into that rate. Both are static contract language sitting outside the system that generates the invoice, so neither gets enforced automatically.

A. Rate escalation timing

Many staffing MSAs allow an annual rate escalation tied to a published index rather than a flat percentage. Checking this means confirming the escalation's effective date against the invoice date it first appears on, and confirming the size of the increase against the index the contract names, not against the vendor's stated figure alone. 3% year over year (BLS, read 2026-09-06). If an MSA escalation clause is pegged to a labor cost index, that published figure, not the vendor's invoice narrative, is the number to check the increase against.

B. Burden rate reconciliation

The burden rate, covering statutory costs like payroll tax and workers' compensation, is usually built into the bill rate as a fixed component rather than itemized. When a vendor's actual burden cost drops, because a state rate changed or a claims history improved, the MSA typically has no mechanism forcing the bill rate down to match, unless the contract specifically requires periodic burden rate true-up. Checking whether that clause exists, and whether it has been invoked, is a two-minute contract read that most invoice-level reviews never reach.

5. Which pass-through costs get billed without documentation?

Staffing MSAs commonly allow pass-through billing for items like background checks, drug screens, travel, or equipment, at cost or at cost plus a small handling fee. These lines are easy to approve because they look like reimbursements rather than markup, but a pass-through with no receipt, no itemized vendor invoice behind it, or a handling fee applied where the MSA specifies none, is drift with a low approval bar and no visible rate to compare against a rate card.

The check is documentation, not rate comparison, because there is often no rate card entry for a pass-through cost. Each pass-through line should be traceable to a third-party receipt or invoice at the amount billed, and to the MSA clause that permits it. A pass-through fee with a round number and no backing document is a finding regardless of size, because the MSA's permission for the charge, not the charge's plausibility, is what makes it billable at all.

A second concrete check: confirm whether the MSA caps pass-through handling fees or requires they be billed at cost with no markup. Contracts frequently specify one or the other, and a vendor invoice that adds a markup to a cost the contract says should pass through unmarked is a contract violation with no ambiguity about the correct answer.

6. Should an audit stop at the invoice or go back to the requisition?

An invoice only shows what was billed. It cannot show what was requested, what category was approved, or whether the position was ever authorized to continue past a stated end date. An audit that never opens the original requisition is checking the invoice for internal consistency, not for agreement with the contract, and those are different tests that can both pass on a wrong invoice.

The requisition is the document that states intent: role, category, expected duration, and any approved extension. Holding it next to the invoice is what surfaces off-contract resources, meaning people billed who were never on an approved requisition at all, a distinct problem from a correctly requisitioned worker billed at the wrong rate.

A practical audit sequence pulls three documents per worker rather than one: the requisition, the MSA's rate schedule for that worker's category, and the invoice line. Checking any two of those three against each other catches part of the picture. Checking all three catches category drift, rate drift, and unauthorized headcount in a single pass, and it is the only sequence that does.

Building this into a recurring cycle, rather than a one-time contract review, is what closes the gap this page describes. Contract labor and staffing invoices change every pay period; a contract compliance check run once a year cannot keep pace with a roster and rate structure that turns over monthly.

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)

What is the single most common document missing from a contract labor audit?

The original requisition. Most audits compare the invoice to the rate card or the MSA's rate schedule but never pull the requisition that stated the intended role, category, and duration, which is the only document that shows whether a worker was authorized to be billed at all.

How do I check if a staffing markup was applied correctly?

Recompute it from the invoice's stated pay rate and the markup percentage in the MSA, rather than comparing the final bill rate to last cycle's bill rate. A markup applied to the wrong pay-rate tier can still produce a bill rate that looks consistent over time.

Why would a fully approved timesheet still be wrong?

Timesheet approval confirms hours worked, signed by a manager. It does not test the labor category code, the markup calculation, or whether the worker is still an active assignment. Those are contract-level checks a manager's sign-off was never designed to perform.

What counts as an off-contract resource in a staffing invoice?

A worker billed on the invoice with no corresponding approved requisition, or a worker whose requisition expired or was never extended in writing. The invoice line can be arithmetically correct and still represent unauthorized headcount.

How often should a headcount reconciliation run?

Every billing cycle, not just at contract renewal. Offboarding notices typically reach the hiring manager and internal systems before they reach the vendor's billing platform, so the exposure window between an actual roll-off and the invoice catching up grows with every cycle it is not checked.

Are pass-through costs like background checks and travel worth auditing?

Yes. They usually have no rate card entry, so they are approved on plausibility rather than documentation. Each should be checked against a third-party receipt and against whether the MSA permits a handling fee or requires cost-only billing.

What does a burden rate true-up clause do?

It requires the bill rate's built-in cost for statutory items like payroll tax and workers' compensation to be periodically reconciled against the vendor's actual cost. Without that clause, a bill rate set when burden costs were higher has no mechanism to come back down.

Can a rate escalation be checked against a public index?

Where the MSA ties escalation to a named index, yes. The US Bureau of Labor Statistics publishes a Producer Price Index series for employment services, which read 175.559 in July 2026, up 5.3% year over year (BLS, read 2026-09-06), a figure that can be checked against a vendor's stated escalation.

Is a category code error usually intentional?

There is no dataset showing how often category errors are intentional versus a byproduct of unrecorded reclassification after a performance review or scope change. Either way, a category mismatch with no signed amendment is a finding to raise with the vendor, not a judgment about intent.

What is the fastest way to start auditing an existing staffing contract?

Pull the MSA's rate schedule, the current active roster invoice, and the original requisitions for a sample of workers, then reconcile category codes and headcount first, since those checks require no rate recalculation and surface the clearest findings fastest.