Auditing Contract Labor and Staffing Spend in Plex

Executive Summary

Contract labor spend in Plex passes through the same three-way match as a raw material purchase: PO, receipt, invoice. That match confirms a vendor billed what the purchase order authorized. It does not confirm the purchase order was built from the correct bill rate, the correct overtime multiplier, or a markup percentage that was still valid on the invoice date.

The mechanism behind most contract labor drift is a staffing rate card that changes on its own schedule, sometimes annually, sometimes at contract renewal, while the PO in Plex was set up once and never revisited. An agency that raises its bill rate mid-term, or applies a shift differential the contract does not authorize, bills correctly against Plex's PO and incorrectly against the underlying agreement.

Closing that gap means moving the rate card, the NTE cap, and the markup terms into a reference a person checks against every invoice, since Plex will not check them automatically. That can be a manual reconciliation on a defined cadence or a system built for contract-to-invoice matching. Either way, the terms have to leave the PDF.

1. How do you audit contract labor and staffing spend in Plex?

Pull every contract labor invoice paid through Plex for the audit period, then compare each line against three source documents: the staffing agency's current rate card, the master service agreement's not-to-exceed cap if one exists, and the timesheet or hours log the invoice claims to bill. Plex confirms the invoice matches its own PO. It does not confirm the PO reflects the current contract terms, so the comparison has to happen outside the system, against the agreement itself.

Start with the vendor list, not the invoice list. Contract labor spend usually runs through a small number of staffing agencies, so isolating those vendor codes in Plex narrows the population fast.

For each vendor, pull the signed agreement or the most recent rate amendment. Line up the bill rate, overtime multiplier, and any markup percentage against what actually appears on invoices for the same period. A rate card increase that never made it into the Plex PO will bill correctly against the PO and incorrectly against the contract.

Check NTE caps separately from rate accuracy. A correct bill rate applied to more hours than a not-to-exceed clause allows is still an overrun, and Plex has no field that stops a PO from exceeding a cap defined in a separate document.

2. What does Plex actually check on a contract labor invoice?

Plex performs a three-way match: it confirms the invoice amount agrees with the purchase order and that a receipt exists for the service. That match answers one question only, whether the vendor billed what the PO authorized. It does not test whether the PO itself was built from an accurate rate card, whether a markup percentage changed since the PO was created, or whether hours billed align with an approved timesheet.

The three-way match is a control against unauthorized billing, not against outdated authorization. If a PO was set up with a bill rate that was correct a year ago and the agency's rate card has since changed, Plex approves the new, incorrect invoice without objection because it matches the old PO.

Markup percentages compound this. A staffing agency invoice often bundles a base pay rate with a markup for overhead and margin. Plex records the total line amount. It has no field that separates base rate from markup, so a markup creep is invisible unless someone breaks the invoice back down.

Timesheet validation sits outside Plex entirely in most contract labor programs, handled through a vendor management system or manual approval, which means the hours a receipt confirms are whatever the receiving employee entered, not necessarily what a signed timesheet supports.

3. Where does contract labor drift usually originate?

Contract labor drift originates at points where a contract term changes but the Plex PO does not follow it. A rate card renewal, a shift differential applied outside its authorized hours, an overtime multiplier calculated on a different threshold than the contract states, and a markup percentage that shifts after the initial agreement are the recurring sources. Each one produces an invoice that looks ordinary because it matches a PO that itself went stale.

A rate card renewal is the most direct source. Staffing agreements often specify an annual or multi-year rate schedule. When that schedule steps up, the increase has to be manually reflected in the Plex PO, and if AP does not catch the renewal date, the PO keeps authorizing the old rate while the agency bills the new one, or vice versa.

Overtime calculation is a recurring, easy-to-miss source because the trigger threshold, whether it is a daily eight hours or a weekly forty, is defined in the contract and not enforced by any field in Plex.

Shift differentials and holiday premiums follow the same pattern: contractually defined, invoiced by the agency's own system, and never checked against the contract term because the term is not in Plex.

4. Can Plex be configured to catch these overruns on its own?

Plex can be configured with tighter PO controls, such as requiring a receipt before payment and flagging invoices that exceed PO value by a defined tolerance. Those settings catch a bill that exceeds its own PO. They cannot catch a PO that was built from the wrong rate in the first place, because Plex has no field for the underlying contract term the rate should have come from.

The configuration ceiling is the PO itself.

Tightening the match tolerance in Plex, so an invoice more than a small percentage over its PO gets held for review, closes one failure mode: gross overbilling against an otherwise correct PO. It does not touch the more common failure mode, where the PO was wrong from the start.

Some manufacturers add a custom field to the vendor record for a rate card reference or renewal date. That helps a person remember to check, but Plex still does not read the PDF or compare the invoice line to it automatically.

The honest boundary: PO-based ERPs enforce whatever the PO says. They do not enforce what the contract says unless someone keeps the PO synchronized with the contract by hand, on a schedule.

5. How far back should a contract labor audit look?

A contract labor audit should cover the full period since the last rate card change or contract renewal, whichever is more recent, because drift compounds from that point forward and does not reset on its own. Most engagements reviewing service vendor spend look back 12 to 18 months across ValueXPA diagnostics, which is long enough to capture at least one renewal cycle for most staffing agreements without the review becoming unmanageable.

The renewal date matters more than a fixed lookback window. If a staffing contract renewed 20 months ago and the rate never changed in Plex, the audit needs to reach back to that renewal, not stop at an arbitrary 12-month mark.

For agencies billed monthly, pulling a full year of invoices also captures seasonal shift differential and overtime patterns that a shorter window would miss, since overtime exposure tends to cluster around specific production periods rather than distributing evenly.

Where multiple agencies are in play, stagger the review by contract anniversary date rather than calendar quarter, so each agency's audit window actually spans its own renewal cycle.

6. What does an audit finding actually recover?

A contract labor finding typically recovers the delta between the rate actually billed and the rate the current contract authorizes, applied across every invoice affected since the discrepancy began, plus any credit owed for hours billed outside an NTE cap. Recovery requires the original signed agreement or amendment as evidence, since a vendor dispute without the contract in hand is a negotiation, not a documented claim.

Documentation matters more than the size of the discrepancy. A $2 per hour rate gap across a modest contract labor program adds up over a year of invoices, but only if the audit can point to the specific rate card page or amendment that sets the correct number.

Credit memos for past overbilling are the direct recovery. The forward-looking value is arguably larger: once a PO reflects the correct rate, every future invoice against that PO is protected until the next renewal, at which point the same synchronization step has to repeat.

Where Producer Price Index data is useful is context, not proof. The Employment services PPI series (BLS, read September 25, 2026) stood at 174.047 in August 2026, up 3.5% year over year, which explains why a stale rate card understates true labor cost increases. It does not substitute for the contract's own rate terms in a recovery claim.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

7. Frequently Asked Questions (People Also Ask)

Does Plex track staffing agency rate cards?

No. Plex has no native field for a staffing agency's rate card, tiered bill rates, or markup schedule. Those terms live in the signed agreement, and Plex only stores the PO value that was manually entered from it, which can go stale after a renewal.

What is a not-to-exceed cap in a staffing contract?

An NTE cap is a ceiling on total billable spend or hours under a contract labor agreement, often tied to a specific role or project. Plex enforces the PO amount it was given, not the underlying NTE clause, so a PO set above the actual cap will approve invoices the contract does not permit.

How do I know if my contract labor rate card is out of date in Plex?

Compare the bill rate on the current PO against the effective date and rate listed in the most recent signed rate amendment. If the amendment postdates the PO's last update, the PO is out of date, and every invoice against it should be checked for the same gap.

Can three-way matching in Plex catch a rate overbilling issue?

Three-way matching confirms the invoice agrees with the PO and that a receipt exists. It does not test whether the PO itself reflects the current contract rate, so a rate overbilling issue that matches a stale PO passes the match without being flagged.

Should I audit contract labor spend manually or use software?

It depends on volume and how many staffing agencies you manage. A small number of vendors with infrequent rate changes can be reconciled manually on a set schedule. Higher vendor counts or frequent renewals make manual tracking harder to sustain, which is the tradeoff covered in diagnostic or software: what to buy first.

What documents do I need before starting a contract labor audit in Plex?

The signed master service agreement, every rate amendment since signing, the current Plex PO for each staffing vendor, and 12 to 18 months of paid invoices. Timesheets or an equivalent hours record are needed if you also want to verify billed hours, not just rates.

Does overtime get calculated correctly by default in Plex?

Plex does not calculate overtime against a contract's stated threshold. It approves whatever amount the invoice bills against the PO. The overtime trigger, whether daily or weekly, is defined in the staffing contract and has to be checked against the invoice separately.

Is contract labor a bigger risk category than freight or MRO in Plex?

There is no dataset that ranks drift by category, so that comparison cannot be made. What is true is that contract labor has its own recurring mechanism, a rate card and NTE structure that lives outside Plex entirely, which is distinct from how freight or MRO spend drifts.

How does the Producer Price Index relate to contract labor audits?

The BLS Employment services PPI series tracks staffing industry pricing trends generally. It provides context for why bill rates rise over time but is not evidence of what a specific vendor contract authorizes, so it supports background analysis, not a recovery claim.