# Timesheet correction case: a shift across cutoffs | SourceX

Canonical: https://refer.sourcex.si/guides/timesheet-correction-approvals-exception-examples
Last updated: 2026-10-18

The records that explain how a staffing firm handled a timesheet exception are the ones that follow one correction through every system it touches: the worker's original time entry, the correction request, the client approver's sign-off, the payroll adjustment, the revised invoice or credit memo, and the reconciliation showing paid hours and billed hours agree again. The hard case is a shift that crosses a weekly cutoff, because the error changes overtime, pay and billing at once.

This worked case belongs to the guide on [procurement approvals and exception workflows](/guides/how-to-assess-procurement-approvals-and-exception-workflows), which explains the problem, action and result test. This page does one job: it walks a single staffing exception step by step, then shows a payroll advisor how to recognize the same pattern at a client.

## The shift and the two calendars

Illustrative and invented for this page. A 900-person staffing firm places a warehouse lead at a distribution client on nights. The firm's payroll workweek runs Monday 00:00 to Sunday 23:59, and the client's billing week uses the same boundary.

In week 1 the worker has already worked 38 hours by Sunday evening. Then comes a 10-hour shift from Sunday 22:00 to Monday 08:00: 2 hours belong to week 1 and 8 hours to week 2. In week 2 the worker works another 36 hours after that Monday morning.

| Calendar | Week 1 boundary | Week 2 boundary | Why it matters |
|---|---|---|---|
| Payroll workweek | Ends Sunday 23:59 | Starts Monday 00:00 | Overtime is figured per workweek |
| Client billing week | Ends Sunday 23:59 | Starts Monday 00:00 | The client is billed per week, with an overtime bill rate |
| The night shift | 2 hours | 8 hours | One shift, two weeks |

The federal rule is the reason the split matters. Under 29 CFR 778.104 each workweek stands alone: hours cannot be averaged across weeks, whatever the shift pattern.

## What went wrong: ten hours entered on the wrong day

The worker clocks in on Sunday night through the client's time-capture kiosk, but the kiosk session drops and the worker later enters the whole shift by hand, dated Sunday. The client's site supervisor approves the week as usual on Monday.

| Week | Hours as entered | Overtime as entered | Hours as worked | Overtime as worked |
|---|---|---|---|---|
| Week 1 | 48 | 8 | 40 | 0 |
| Week 2 | 36 | 0 | 44 | 4 |
| Total | 84 | 8 | 84 | 4 |

Total hours are right; the week is wrong. The firm pays 8 overtime hours in week 1 and bills the client 8 hours at the overtime rate. Nothing looks broken until week 2 closes with 36 hours and the worker asks why the pay stub for week 2 is short.

## The correction, step by step

| Day | Action | Who | Record it left |
|---|---|---|---|
| Week 2, Tuesday | Worker disputes the week 2 hours | Worker | Correction request in the time-capture tool, with the kiosk error |
| Week 2, Wednesday | Payroll team pulls the kiosk log showing the 22:00 Sunday clock-in | Payroll specialist | Kiosk log extract attached to the request |
| Week 2, Thursday | Client approver signs the split: 2 hours Sunday, 8 hours Monday | Client site supervisor | Approval in the vendor management system, replacing the original week 1 approval |
| Week 2, Friday | Payroll moves 8 hours to week 2: week 1 overtime reversed, 4 overtime hours in week 2 | Payroll operations head | Payroll adjustment with reason code and approver |
| Following Monday | Credit memo for week 1 overtime billed; week 2 invoice includes the 8 hours | Billing specialist | Credit memo and revised invoice, both citing the original invoice number |
| Following Tuesday | Paid hours and billed hours reconcile for both weeks | Finance analyst | Reconciliation report: 84 paid, 84 billed, 4 overtime both sides |

The approval in the vendor management system is the hinge. Without the client's sign-off on the split, the firm would have corrected its pay records while the client still held an approved week 1 that disagreed with the bill.

## Why each record earns its place

Read as a chain, the case shows the problem, the authorized action and the checked result:

- **The problem** is visible in two records that disagree: the hand-entered time and the kiosk log.
- **The authorized action** is the client approver's split, because only the client can confirm when the worker was on site.
- **The checked result** is the reconciliation, which proves pay and billing were moved together rather than one of them alone.

Three things make this sequence rare and useful. It involves two organizations, so it shows a hand-off of authority. It turns on a precise rule, so every step can be checked against the rule. And it ends with a number that either reconciles or does not. For an AI system learning payroll and billing work, a case like this shows more of the actual judgment than any number of clean weeks.

Depth is the first qualification question. The Department of Labor's recordkeeping fact sheet says payroll records are kept for at least three years and time cards for two. A firm that deletes at the minimum holds a short window; one that kept a decade of time, approval and invoice history holds a deep archive of corrections. Related correction workflows are covered in the guide to [human review records and correction workflows](/guides/how-to-assess-human-review-records-and-correction-workflows).

## Recognizing the pattern at a staffing client

Staffing payroll advisors, fractional CFOs and VMS consultants can spot firms with cases like this without seeing a record. Ask the payroll operations head:

- **Do night or weekend shifts cross the workweek boundary?** Warehousing, healthcare and security placements make it routine.
- **How is a correction approved?** In the VMS, by client email, or both.
- **Do the time entry, the approval, the payroll adjustment and the credit memo share a worker and assignment ID?**
- **How many years of time entries, approvals and invoices are kept, and is the VMS or payroll system changing soon?**
- **Who owns client-approved timesheets under the client contracts?** That is a question for counsel, not the partner.

Then introduce the person who can authorize a licensing discussion, the CEO, with the payroll operations head as working contact. The firm needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. See [who qualifies](/who-qualifies) and the note on [whether temporary employees count toward headcount](/questions/do-staffing-firm-temporary-employees-count-toward-headcount). Worker names, pay rates and IDs are for SourceX's rights and redaction review, never the partner. What stays unknown until SourceX reviews it: export options for each system and whether buyers want these records. The page for [staffing firm owners](/for/staffing-firm-owners) and the [staffing and recruiting industry page](/industries/staffing-and-recruiting) cover the firm side. Other hard cases: [conflicting service recovery promises](/guides/service-recovery-approvals-exception-examples) and a [franchise brand standard variation](/guides/brand-standard-exception-approvals-exception-examples).

## Next step

> **Refer a company. Earn up to $100,000.** Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a staffing firm you advise can follow a cross-cutoff correction from time entry to reconciliation, [register as a partner](/register), confirm [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://www.ecfr.gov/current/title-29/subtitle-B/chapter-V/subchapter-B/part-778/subpart-B/subject-group-ECFR8e3979fde83542b/section-778.104
- https://www.dol.gov/agencies/whd/fact-sheets/21-flsa-recordkeeping
- https://refer.sourcex.si/terms