# Who catches shift and overtime premium misuse? > Shift and overtime premium misuse falls between AP, procurement, and operations. Here is who should own the check, and how it actually catches drift. Source: https://valuexpa.com/insights/who-is-responsible-for-catching-shift-and-overtime-premium Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- [Margin drift](/guides/what-is-margin-erosion-causes-and-prevention-for) is the gap between what a vendor contract says and what the invoice actually charges. Shift and overtime premium misuse is one specific way that gap opens: a staffing or contract labor vendor bills a premium rate for hours, shifts, or crews that the contract never authorized at that rate. The honest answer to who catches it is nobody, by default. It falls between three desks, and each one has a reason to assume someone else is checking the premium math. ## Executive Summary The shift and overtime premium clause in a contract labor agreement usually sets specific triggers: a second or third shift differential, hours beyond a daily or weekly threshold, holiday or weekend work, or emergency call-out. The invoice, by contrast, arrives as a total labor charge with a premium line item that rarely shows the underlying hours, shift code, or trigger condition. That asymmetry is the mechanism: the contract is granular, the invoice is not, and nobody upstream of payment is required to reconcile the two. Three functions each have partial visibility and none has full ownership. AP matches the invoice to the purchase order and the approved total, not to the shift schedule. Procurement or the category manager who negotiated the labor contract rarely reviews individual invoices after signing. The operations manager who approves the timesheet knows the hours worked but usually does not see the contract's premium rate table. Each has a piece of the answer and none is asked to assemble the whole one. What changes it is making the reconciliation an explicit, assigned step rather than an assumed one: someone with both the contract's premium terms and the invoice's shift detail, checking one against the other on a defined cadence. ## 1. Why does shift premium misuse slip past normal AP review? **Standard AP review checks that an invoice matches its purchase order and that the total falls within an approved amount. Neither check touches the shift code or hours breakdown behind a labor premium line. Three-way matching confirms a PO, an invoice, and a receipt agree on quantity and price; it does not test whether the second-shift differential applied to hours that ran during first shift, because the PO was never built to carry that level of contract detail in the.** A contract labor purchase order typically states a blanket rate or a not-to-exceed ceiling for the engagement, not a shift-by-shift rate table. When the invoice arrives, AP has no reference document in the ERP that says which hours qualify for a premium and which do not. The system approves the invoice because it matches the PO on the fields the PO actually contains. The premium rate table itself usually lives in the underlying contract or statement of work, a document that sits outside the ERP as a PDF. AP staff processing invoice volume have no practical way to open that document for every labor invoice and check the shift code against it. The control gap is not carelessness; it is a document living in the wrong place for the process built to catch it. This is why [shift and overtime premium misuse](/glossary/shift-and-overtime-premium-misuse) persists as a category of its own rather than getting caught incidentally by existing controls built for a different purpose. ## 2. What does the vendor's role look like in this drift? **The staffing or contract labor vendor sets the invoice, and the invoice reflects whatever the vendor's own timekeeping and billing system generates. Shift codes get assigned at the point the schedule is built, often by a vendor site supervisor working from a shift roster, not from the client's signed rate schedule. A shift coded as premium at that stage carries through to billing unless someone downstream checks it against the contract.** Vendor billing systems are configured once, at contract start, and rarely re-checked against contract amendments or renegotiated rate schedules. A rate that was correct in year one of a multi-year staffing agreement can persist unchanged after a renewal changed the premium trigger. This is not necessarily deliberate. A vendor supervisor scheduling coverage for a plant running three shifts has an incentive to staff shifts reliably, not to audit the billing consequence of how a shift gets coded. The premium classification is a byproduct of a scheduling decision made for operational reasons. The client side still bears the cost of not checking it, regardless of vendor intent. A billing error that nobody catches functions identically to overbilling for the purposes of the invoice paid. ## 3. Which internal function should actually own this check? **The function with both the contract's premium terms and the invoice's shift-level detail should own the check, and today that is usually nobody, because those two documents live with different people. The closest existing owner is whoever manages the contract labor relationship day to day: an operations manager or category-level procurement lead who reviews timesheets. Making the check real means adding the contract's premium rate table to what they review, not creating a new role.** Assigning ownership on paper does not work unless the owner also receives the document they are missing. An operations manager told to own this check still cannot without the contract's rate table in hand. A workable version pairs the two: the person closest to the hours worked, given the reference document held by the person who negotiated the terms. Neither role changes; the document simply moves. This is a process fix, not a headcount fix. It costs a recurring meeting or a shared file, not a new position. ### A. Operations manager Has direct visibility into the shift schedule and the hours actually worked. Lacks the contract's rate table unless procurement hands it over as a reference document, not just a signed agreement filed away. ### B. Procurement or category lead Negotiated the premium terms and knows what should trigger a differential. Rarely sees individual invoices after the contract is signed, so the terms they negotiated are never checked against what gets billed. ### C. AP Processes the invoice against the PO and pays it on time. Has no mandate or reference document to check shift-level billing logic, and adding that mandate without the reference document changes nothing. ## 4. How would a periodic check actually catch this? **A periodic check pulls the contract's premium rate table and the vendor's invoice-level shift detail into the same review, on a defined schedule rather than an ad hoc one. It compares the shift code billed against the trigger condition the contract actually specifies: was the hour worked during the differential window, did the week exceed the overtime threshold, was the call-out genuinely an emergency. Where the two disagree, that line item becomes a credit request, not a write-off.** The check needs two inputs in the same place: the contract's premium clause, stated in plain terms, and the invoice's underlying hours and shift codes, not just the summary total. Some vendors provide this detail on request even when it is not on the standard invoice. A quarterly or semiannual cadence is realistic for most [contract labor relationships](/glossary/contract-labor-and-staffing-audit). Checking every invoice line in real time is a software problem, not a periodic-review problem, and a periodic review can still catch a pattern of misapplied premiums before it compounds across a year. The output of the check is a specific, documented discrepancy: this shift, this date, billed at the wrong rate, against this clause. That specificity is what makes it something a vendor will actually credit rather than dispute in general terms. ## 5. Does the size of the labor contract change who should check it? **A larger contract labor spend justifies a more frequent check, not a fundamentally different owner. A single-site relationship with a handful of shift workers may only need an annual reconciliation before renewal. A multi-site staffing agreement covering hundreds of workers across shift patterns carries more dollars behind each misapplied premium and more shift-code variation, which is exactly what a quarterly cadence is built to catch before it accumulates.** The mechanism is the same at any size: a rate table the invoice does not reference, checked or not. What changes with scale is how much sits behind an uncaught error and how quickly a pattern, rather than a one-off, develops. A multi-site relationship also multiplies the number of vendor supervisors assigning shift codes, which multiplies the number of independent points where a classification can drift from the contract without anyone intending it. Contract renewal is a natural forcing point regardless of size: the rate table changes, so the prior period's invoices are worth checking against the terms that were actually in effect during the period being billed, not the terms that replaced them. ## 6. Is this a recoverable finding or a control to prevent it forward? **It is both, and the two require different actions. Past invoices billed against the wrong premium rate are a recoverable finding: specific dollars, on specific dates, against a specific clause, that a vendor can credit. Fixing who reviews the rate table against future shift codes is a preventable control: an assigned owner, a defined cadence, and a reference document that did not previously exist in the review process.** Treating this only as a one-time recovery misses the point. If nobody owned the check before, nobody owns it after, and the same misclassification recurs on the next billing cycle. Treating it only as a forward control misses the money already paid. Historical invoices, often spanning 12 to 18 months of past billing, across ValueXPA diagnostics, can still contain premium misclassifications within a reasonable window to raise with the vendor. The split matters because it changes what gets measured. A recovery is judged by dollars returned. A control is judged by whether the same discrepancy appears again next quarter. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. ## 7. Frequently Asked Questions (People Also Ask) ### Is AP responsible for catching shift premium misuse? Not under standard three-way matching. AP checks that the invoice matches the purchase order and an approved total; it does not have access to shift-level detail or the contract's premium rate table, so it has no basis to flag a misapplied premium even when reviewing every line. ### Should procurement review individual labor invoices? Not every invoice, but procurement or the category owner who negotiated the contract's premium terms is the function best positioned to periodically compare those terms against actual billed shift codes, since they hold the rate table AP and operations do not routinely see. ### What information do we need from the vendor to check this? Invoice-level detail showing the date, shift, and hours behind each premium line item, not just the summary total. Many vendors will provide this on request even when their standard invoice format omits it. ### How far back can we ask a vendor to credit a misapplied premium? This depends on the contract's own audit and dispute terms, which vary by agreement. As a general matter, not legal advice, review the specific contract language on invoice disputes before raising a claim outside its stated window. ### Does this only apply to staffing agency contracts? It applies to any contract labor arrangement with a shift or overtime differential written into the rate terms, including maintenance contractors and outsourced operations staff, not staffing agencies exclusively. ### Can our ERP flag this automatically? Only if the premium rate table is entered into the system at the shift-code level, which most ERP purchase orders for labor contracts do not carry. Without that reference data loaded, three-way matching has nothing to compare the invoice against. ### Is this the same issue as a not-to-exceed overrun? No. A not-to-exceed overrun is a total spend cap being exceeded; shift premium misuse is a rate classification error that can occur well within an approved total. These are distinct drift patterns worth checking separately. ### What should we ask our operations manager to check? Whether the shift code on a sample of recent invoices matches the actual time of day and day of week the work occurred, and whether that shift genuinely falls within the contract's stated differential window. ### How often should this check happen? A quarterly or semiannual cadence is reasonable for most contract labor relationships, with an additional check timed to contract renewal, when rate tables change and prior-period billing is worth comparing against the terms that were actually in effect. ### 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 The shift and overtime premium clause in a contract labor agreement usually sets specific triggers: a second or third shift differential, hours beyond a daily or weekly threshold, holiday or weekend work, or emergency call-out. The invoice, by contrast, arrives as a total labor charge with a premium line item that rarely shows the underlying hours, shift code, or trigger condition. That asymmetry is the mechanism: the contract is granular, the invoice is not, and nobody upstream of payment is required to reconcile the two. Three functions each have partial visibility and none has full ownership. AP matches the invoice to the purchase order and the approved total, not to the shift schedule. Procurement or the category manager who negotiated the labor contract rarely reviews individual invoices after signing. The operations manager who approves the timesheet knows the hours worked but usually does not see the contract's premium rate table. Each has a piece of the answer and none is asked to assemble the whole one. What changes it is making the reconciliation an explicit, assigned step rather than an assumed one: someone with both the contract's premium terms and the invoice's shift detail, checking one against the other on a defined cadence. ## 1. Why does shift premium misuse slip past normal AP review? Standard AP review checks that an invoice matches its purchase order and that the total falls within an approved amount. Neither check touches the shift code or hours breakdown behind a labor premium line. Three-way matching confirms a PO, an invoice, and a receipt agree on quantity and price; it does not test whether the second-shift differential applied to hours that ran during first shift, because the PO was never built to carry that level of contract detail in the. A contract labor purchase order typically states a blanket rate or a not-to-exceed ceiling for the engagement, not a shift-by-shift rate table. When the invoice arrives, AP has no reference document in the ERP that says which hours qualify for a premium and which do not. The system approves the invoice because it matches the PO on the fields the PO actually contains. The premium rate table itself usually lives in the underlying contract or statement of work, a document that sits outside the ERP as a PDF. AP staff processing invoice volume have no practical way to open that document for every labor invoice and check the shift code against it. The control gap is not carelessness; it is a document living in the wrong place for the process built to catch it. This is why [shift and overtime premium misuse](/glossary/shift-and-overtime-premium-misuse) persists as a category of its own rather than getting caught incidentally by existing controls built for a different purpose. ## 2. What does the vendor's role look like in this drift? The staffing or contract labor vendor sets the invoice, and the invoice reflects whatever the vendor's own timekeeping and billing system generates. Shift codes get assigned at the point the schedule is built, often by a vendor site supervisor working from a shift roster, not from the client's signed rate schedule. A shift coded as premium at that stage carries through to billing unless someone downstream checks it against the contract. Vendor billing systems are configured once, at contract start, and rarely re-checked against contract amendments or renegotiated rate schedules. A rate that was correct in year one of a multi-year staffing agreement can persist unchanged after a renewal changed the premium trigger. This is not necessarily deliberate. A vendor supervisor scheduling coverage for a plant running three shifts has an incentive to staff shifts reliably, not to audit the billing consequence of how a shift gets coded. The premium classification is a byproduct of a scheduling decision made for operational reasons. The client side still bears the cost of not checking it, regardless of vendor intent. A billing error that nobody catches functions identically to overbilling for the purposes of the invoice paid. ## 3. Which internal function should actually own this check? The function with both the contract's premium terms and the invoice's shift-level detail should own the check, and today that is usually nobody, because those two documents live with different people. The closest existing owner is whoever manages the contract labor relationship day to day: an operations manager or category-level procurement lead who reviews timesheets. Making the check real means adding the contract's premium rate table to what they review, not creating a new role. Assigning ownership on paper does not work unless the owner also receives the document they are missing. An operations manager told to own this check still cannot without the contract's rate table in hand. A workable version pairs the two: the person closest to the hours worked, given the reference document held by the person who negotiated the terms. Neither role changes; the document simply moves. This is a process fix, not a headcount fix. It costs a recurring meeting or a shared file, not a new position. ### A. Operations manager Has direct visibility into the shift schedule and the hours actually worked. Lacks the contract's rate table unless procurement hands it over as a reference document, not just a signed agreement filed away. ### B. Procurement or category lead Negotiated the premium terms and knows what should trigger a differential. Rarely sees individual invoices after the contract is signed, so the terms they negotiated are never checked against what gets billed. ### C. AP Processes the invoice against the PO and pays it on time. Has no mandate or reference document to check shift-level billing logic, and adding that mandate without the reference document changes nothing. ## 4. How would a periodic check actually catch this? A periodic check pulls the contract's premium rate table and the vendor's invoice-level shift detail into the same review, on a defined schedule rather than an ad hoc one. It compares the shift code billed against the trigger condition the contract actually specifies: was the hour worked during the differential window, did the week exceed the overtime threshold, was the call-out genuinely an emergency. Where the two disagree, that line item becomes a credit request, not a write-off. The check needs two inputs in the same place: the contract's premium clause, stated in plain terms, and the invoice's underlying hours and shift codes, not just the summary total. Some vendors provide this detail on request even when it is not on the standard invoice. A quarterly or semiannual cadence is realistic for most [contract labor relationships](/glossary/contract-labor-and-staffing-audit). Checking every invoice line in real time is a software problem, not a periodic-review problem, and a periodic review can still catch a pattern of misapplied premiums before it compounds across a year. The output of the check is a specific, documented discrepancy: this shift, this date, billed at the wrong rate, against this clause. That specificity is what makes it something a vendor will actually credit rather than dispute in general terms. ## 5. Does the size of the labor contract change who should check it? A larger contract labor spend justifies a more frequent check, not a fundamentally different owner. A single-site relationship with a handful of shift workers may only need an annual reconciliation before renewal. A multi-site staffing agreement covering hundreds of workers across shift patterns carries more dollars behind each misapplied premium and more shift-code variation, which is exactly what a quarterly cadence is built to catch before it accumulates. The mechanism is the same at any size: a rate table the invoice does not reference, checked or not. What changes with scale is how much sits behind an uncaught error and how quickly a pattern, rather than a one-off, develops. A multi-site relationship also multiplies the number of vendor supervisors assigning shift codes, which multiplies the number of independent points where a classification can drift from the contract without anyone intending it. Contract renewal is a natural forcing point regardless of size: the rate table changes, so the prior period's invoices are worth checking against the terms that were actually in effect during the period being billed, not the terms that replaced them. ## 6. Is this a recoverable finding or a control to prevent it forward? It is both, and the two require different actions. Past invoices billed against the wrong premium rate are a recoverable finding: specific dollars, on specific dates, against a specific clause, that a vendor can credit. Fixing who reviews the rate table against future shift codes is a preventable control: an assigned owner, a defined cadence, and a reference document that did not previously exist in the review process. Treating this only as a one-time recovery misses the point. If nobody owned the check before, nobody owns it after, and the same misclassification recurs on the next billing cycle. Treating it only as a forward control misses the money already paid. Historical invoices, often spanning 12 to 18 months of past billing, across ValueXPA diagnostics, can still contain premium misclassifications within a reasonable window to raise with the vendor. The split matters because it changes what gets measured. A recovery is judged by dollars returned. A control is judged by whether the same discrepancy appears again next quarter. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. ## Common questions ### Is AP responsible for catching shift premium misuse? Not under standard three-way matching. AP checks that the invoice matches the purchase order and an approved total; it does not have access to shift-level detail or the contract's premium rate table, so it has no basis to flag a misapplied premium even when reviewing every line. ### Should procurement review individual labor invoices? Not every invoice, but procurement or the category owner who negotiated the contract's premium terms is the function best positioned to periodically compare those terms against actual billed shift codes, since they hold the rate table AP and operations do not routinely see. ### What information do we need from the vendor to check this? Invoice-level detail showing the date, shift, and hours behind each premium line item, not just the summary total. Many vendors will provide this on request even when their standard invoice format omits it. ### How far back can we ask a vendor to credit a misapplied premium? This depends on the contract's own audit and dispute terms, which vary by agreement. As a general matter, not legal advice, review the specific contract language on invoice disputes before raising a claim outside its stated window. ### Does this only apply to staffing agency contracts? It applies to any contract labor arrangement with a shift or overtime differential written into the rate terms, including maintenance contractors and outsourced operations staff, not staffing agencies exclusively. --- 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