Duplicate payment in contract labor and staffing

Executive Summary

Contract labor and staffing invoices duplicate payment through a specific mechanism: a single timesheet or work order gets billed more than once because the staffing agency's invoice cadence, correction process, and consolidated billing runs are not reconciled against each other inside accounts payable. A weekly invoice pays the hours once. A correction invoice reissued for a rate error, a client credit not applied, or a month-end reconciliation bill can restate the same hours without either party flagging it as a repeat.

The mechanism is structural, not fraudulent. Staffing vendors invoice from their own timekeeping system, AP pays from purchase orders and approved timesheets, and the two systems rarely cross-check invoice numbers against the underlying shift ID. When an agency reissues a corrected invoice instead of a credit memo against the original, the original often still gets paid alongside the correction.

What changes it is matching at the shift level, not the invoice level. An invoice-level three-way match confirms that a timesheet was approved and a PO exists. It does not confirm that the specific worker, date, and shift referenced on this invoice have not already been billed under a different invoice number.

1. How does a staffing invoice get paid twice?

It happens when the same shift is billed on two separate invoice numbers that both clear AP independently. A weekly invoice pays the hours; a later correction, consolidated, or resubmitted invoice restates the same hours under a new number. Because AP matches each invoice against its own purchase order and approved timesheet, and not against every other invoice number the vendor has submitted, both pass the match and both get paid.

The staffing agency's own invoicing system runs on its payroll cycle. When a rate error, missed shift differential, or client-side rejection surfaces after the original invoice has already been paid, the agency's standard fix is to reissue an invoice covering the corrected amount, not to net it against the original.

If that reissued invoice restates the full period rather than only the delta, AP has no way to see that the underlying hours were already paid unless someone compares shift-level detail across both invoice numbers. The purchase order and the approved timesheet check out on both invoices because the timesheet approval sits at the period level, not the invoice level.

Consolidated billing runs make it worse. A staffing vendor covering multiple sites or job codes for one client sometimes issues a monthly reconciliation invoice that resums hours already billed weekly, intended as a summary rather than a new charge. Read literally by AP as a new invoice, it pays again.

A. Correction invoices

A correction invoice restates hours or rate for a period already invoiced, usually to fix an error the agency caught after submission. The correct form is a credit memo against the original invoice number followed by a new charge for the difference. In practice, many agencies issue a full replacement invoice instead, and if the original is not voided in the AP system before the replacement is entered, both get paid.

B. Consolidated reconciliation runs

Some staffing MSAs call for a periodic reconciliation invoice across multiple work orders or sites. Its purpose is to true up totals, not to add new charges. When it lists shift totals that match hours already paid on weekly invoices, and AP processes it as a standalone bill because it carries its own PO reference, the reconciliation becomes a second payment for the same work.

2. Which contract clause makes this possible?

Most staffing MSAs specify invoice frequency and require timesheet approval before billing, but few specify that a corrected invoice must reference and void the original invoice number. Without that clause, the agency is contractually free to issue a replacement invoice as a new document, and AP has no contractual basis to reject it for lacking a cross-reference to what it replaces.

A staffing MSA typically states billing frequency, the timesheet approval workflow, and the rate card that applies. It rarely states what a correction invoice must contain to be processed as a correction rather than a new charge.

That gap matters because AP's control point, matching the invoice to an approved timesheet and PO, was designed to stop unauthorized billing, not repeated billing of authorized work. The timesheet was approved. The PO exists. Nothing in the standard three-way match asks whether this shift has appeared on a prior invoice number.

A contract clause requiring every correction invoice to cite the original invoice number and net against it, rather than restate the full amount, closes this specific gap. Without it, the agency's own invoicing convention decides whether duplicate payment is possible, and that convention is set for the agency's convenience, not the client's control.

3. What does the invoice actually look like when this happens?

The two invoices rarely look identical. One carries the vendor's standard weekly invoice number and format; the other is labeled a correction, an adjustment, or a reconciliation and carries a different number and often a different total, because it bundles other periods or job codes. Only the underlying shift date, worker identifier, and hours repeat between them.

A duplicate does not present as two copies of the same PDF. It presents as two invoices with different totals, different invoice numbers, and often different formatting, because one is the vendor's routine weekly bill and the other is a special-purpose document generated by a different part of the agency's back office, sometimes a regional office correcting an error the branch office already billed.

What is identical between them is buried at the line-item level: the same worker ID, the same week-ending date, the same job code and hours. An AP reviewer scanning invoice totals and vendor names sees two unrelated bills. Only a line-by-line comparison against a shift register surfaces the overlap.

This is why the finding tends to surface in a full invoice-to-contract audit rather than in routine AP review: it requires holding every invoice from a vendor against a single shift-level ledger, not reviewing each invoice on its own terms.

4. How do you catch it before it pays?

Catch it by matching at the shift level: maintain a running ledger of worker, date, and hours already invoiced per vendor, and check every new invoice, including anything labeled a correction or reconciliation, against that ledger before payment. A control that only checks the current invoice against its own PO and timesheet cannot see a shift billed twice under different invoice numbers.

The fix does not require new software. It requires a register, maintained per staffing vendor, that records worker ID, shift date, and hours for every invoice paid, and a step in the approval workflow that checks new invoices against that register before release.

1. Build a shift-level ledger: Track worker ID, shift date, and hours per vendor across every invoice received, not just the current one.
2. Flag correction or reconciliation labels: Route these to a manual check against the ledger before approval, since they are the documents most likely to restate paid hours.
3. Require original invoice references: Push vendors to cite the invoice number being corrected on any adjustment document, even where the contract does not yet require it.
4. Reconcile at month-end, not just at receipt: A monthly pass comparing total hours billed against total hours approved catches an overlap that individual invoice review misses.

5. Why do routine AP controls miss this?

Standard AP three-way matching checks the invoice against the purchase order and the approved timesheet for that invoice period. It does not check the invoice against every other invoice number the same vendor has submitted. A control built to confirm authorization cannot also confirm non-repetition unless it is explicitly extended to compare across invoice numbers.

Three-way matching answers one question: does this invoice correspond to work that was ordered and approved? It answers that question correctly for both the original and the duplicate, because both cite a real, approved timesheet.

The question it does not ask is whether the timesheet referenced here has already been paid under a different invoice number. That check requires a cross-invoice ledger, which most AP workflows do not maintain for staffing vendors specifically, because staffing invoices are recurring in a way that makes each one look routine on its own.

High invoice volume from a single staffing vendor is itself a reason this drift type persists: the more invoices a vendor generates per month, across sites, job codes, and correction cycles, the harder it is for a reviewer to hold all of them against one register by memory or spot check.

6. How does this connect to other staffing drift types?

Duplicate payment surfaces alongside rate deviations and off-contract billing on the same vendor, because all three share a root cause: invoices reviewed individually against a PO rather than collectively against the contract and the shift register. A vendor whose corrections restate rather than net is often the same vendor whose rate card is applied inconsistently.

A staffing vendor prone to reissuing full invoices instead of credit memos is frequently the same vendor whose billed rate drifts from the master service agreement over time, a distinct pattern covered under labor rate deviations against master service agreements.

Duplicate payment is also easy to confuse with a different problem entirely: a worker billed under the agreement who was never authorized to be on site at all, which is a matter of scope rather than repetition. Both require going past the invoice total to the underlying shift or worker detail, but they are separate checks and separate fixes.

A full margin drift diagnostic reviews staffing invoices for both patterns in the same pass, because the underlying weakness, no shift-level cross-reference, produces both.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and rate card enforcement: why approved timesheets still produce wrong invoices.

7. Frequently Asked Questions (People Also Ask)

Is duplicate payment in staffing usually fraud?

No. The mechanism described here is a documentation gap: a correction or reconciliation invoice restates hours instead of netting against the original. It happens through normal agency invoicing convention, not intent to overbill, though the effect on your AP ledger is identical either way.

Would a three-way match catch this?

Not on its own. A three-way match confirms the invoice matches a purchase order and an approved timesheet. It does not check whether the same shift already appeared on a different invoice number, which is what a duplicate correction or reconciliation invoice does.

What should the contract require to prevent this?

A clause requiring every correction or adjustment invoice to cite the original invoice number it corrects, and to net against that original rather than restate the full period. Without that requirement, the agency's own invoicing convention decides whether a duplicate is possible.

How far back should we check for this?

Check across the full period covered by available invoice and timesheet records. Reissued corrections can surface weeks or months after the original invoice, so a single-period review will miss overlaps that only appear when invoices are compared across a longer window.

Does this only happen with staffing vendors that bill weekly?

It is most visible with weekly billing because that cadence generates the most invoice volume and the most opportunity for a correction cycle, but the same mechanism applies to biweekly or monthly billing wherever a correction or reconciliation invoice restates hours instead of referencing the original.

Can our staffing vendor's own system prevent this?

The agency's payroll and invoicing system is built to bill its own payroll cycle accurately. It has no visibility into what your AP system has already paid, so the check has to live on your side, against your own shift-level ledger, not inside the vendor's system.

What is the difference between this and an off-contract labor charge?

Off-contract billing means a worker or role was invoiced who was never authorized under the agreement at all. Duplicate payment means an authorized shift was billed correctly once, then billed again under a different invoice number. Both require shift-level detail to catch, but they are different failures.

How does the PPI data relate to this?

It does not cause duplicate payment, but it explains why the exposure is rising: the Producer Price Index for Employment Services was 175.559 in July 2026, up 5.3% year over year (US Bureau of Labor Statistics, read 2026-09-05), meaning the same billing gap now carries a larger dollar value per shift than a year earlier.