•

Temporary Worker Short Pay: Resolve the Report

A worker’s hand aligns a missing paper tab while a drafting compass compares two blank cards, representing short-pay evidence reconciliation.
What’s in this article?

    Trace a reported pay shortfall from the original work record to the paid wage lines. Give each discrepancy a decision owner, and close the case only when the correction is evidenced.

    A temporary worker says Friday’s paycheck is missing part of Tuesday’s shift. The client says the timesheet was approved. The recruiter says payroll has the hours. Everyone has an answer, but nobody has reconciled the same dates and pay period.

    A temporary worker short-pay process should establish where the worker’s account, recorded time, agreed pay terms and actual payroll result diverge. Then it should put the correction with the person authorized to make it. Forwarding the worker’s message is not a completed handoff.

    This guide is for staffing coordinators handling reports from agency-employed hourly workers. It sits at Manage → Pay → Review: after work and a reported pay result, before the issue is closed and the underlying staffing process is improved. It is not a supplier-invoice dispute procedure or a guide to calculating every jurisdiction’s wages.

    Open one case without making the worker diagnose it

    Accept a report even if the worker cannot identify the payroll system or produce a perfect screenshot. Name one coordinator who remains accountable for follow-up while the host verifies work and payroll investigates the pay result. Give the worker a case reference, contact and next update time.

    Capture the worker and assignment reference, affected work dates, pay period, expected payday, what appears wrong and the worker’s preferred contact method. Ask whether the concern is missing hours, the rate, an earning line, the net amount or a payment that has not arrived. Keep the worker’s own description alongside that initial category.

    Use an approved restricted channel for pay documents. A host supervisor may need the disputed work dates and time entries, not the worker’s full pay statement, bank information or unrelated deductions. Keep access proportionate to the reviewer’s task.

    If the report includes alleged retaliation, discrimination, coercion or other sensitive conduct, use the contingent worker complaint process as well. A pay investigation should not erase a separate concern about how the worker was treated.

    Compare records before choosing the correction

    Build a small evidence packet for the affected period, not a copy of every worker record. Start with the original time entry or clock record, any revision and approval, the effective assignment pay terms, the payroll input or export confirmation, and the wage lines actually paid. Record unavailable evidence and who will obtain it.

    The U.S. Department of Labor’s FLSA recordkeeping fact sheet describes accurate hours and wage records for covered nonexempt employees, including daily and weekly hours, pay rate, additions or deductions, wages paid and the payment date and period. These are different facts: a schedule is not proof of actual hours, and an approved timesheet is not proof of payment.

    Check the period before comparing totals. Work performed in one calendar week may be shown on a later pay statement. Identify the dates the statement actually covers without assuming that a different period explains away the report.

    Locate the first divergent handoff

    1. Work to recorded time: does the source record include the reported shift and all claimed working time?
    2. Time to approval: did the correct version reach an authorized reviewer, and what did they accept or dispute?
    3. Approval to payroll: which version, hours and effective pay inputs were sent, and did payroll receive them?
    4. Payroll input to paid lines: do the paid earning lines reflect those inputs, or is there a calculation, coding or processing difference?
    5. Paid record to receipt: if payroll records a payment but the worker reports none, who can investigate its delivery through the approved payment channel?

    Provider guidance illustrates why routing matters. Ascen’s short-pay help distinguishes missing or unapproved time from approved time with a pay problem. NextCrew’s hours and pay guidance directs payroll issues to the agency rather than the app provider. Those are provider-specific arrangements, not universal rules for every staffing firm.

    Use a discrepancy matrix, not one “payroll issue” status

    Adapt the following decision aid to the agency’s actual employer, payroll provider and client responsibilities. The coordinator owns the case; the decision owner below owns the relevant fact or correction.

    Short-pay report: evidence and decision routing
    Reported differenceEvidence to compareDecision owner and next stepEvidence needed to complete this branch
    Hours absent or reducedWorker’s account, source time, revisions and host work confirmationHost reviewer verifies work facts; agency/payroll resolves the wage treatment and correctionReasoned hours decision, preserved original and revised records, payroll action reference
    Hours correct, rate appears wrongEffective pay terms, assignment history and paid rate for the affected datesAgency confirms applicable terms; payroll checks affected earning linesEffective-date decision and identified corrected lines, not a change to future setup alone
    Premium or overtime appears missingRelevant workweek time, earning codes and applicable pay rulesQualified payroll reviewer checks treatment; escalate uncertain rules for legal reviewDocumented calculation decision and any required adjustment
    Gross pay matches but net pay differsPay statement and authorized payroll records for deductions, withholding and adjustmentsPayroll explains the difference through a restricted channelItemized explanation or correction; no coordinator-invented tax or deduction advice
    Payment recorded but not receivedPayment date, method and provider’s delivery or trace evidencePayroll/payment provider investigates; coordinator maintains worker updatesConfirmed delivery, resolved failure or an explicit still-open exception

    Do not change a client bill rate to repair a worker pay rate. Do not route a reimbursement, missing wage and bank-delivery issue through the same correction merely because they appear on one report. One case can contain several separately owned differences.

    After payroll has run, preserve the original

    A corrected timesheet is not automatically a corrected paycheck. Record whether the affected time is still editable, already exported or included in a completed pay run. Obtain the payroll owner’s correction reference, affected period and lines, processing route and expected update or payment date.

    For example, ManpowerGroup’s customer time-approval terms distinguish changes after time has gone to payroll from earlier approval actions. Use that as a reason to establish the processing stage—not as a cutoff or rule to copy into another agency’s policy.

    Preserve the original submission and pay result. Link the authorized correction rather than overwriting history or entering the same hours again in an unrelated current period. Before a second adjustment, payroll should check whether an earlier request has already been processed.

    Operational approval queues do not determine legal wage-payment obligations. Have qualified payroll or legal reviewers establish the applicable payment timing and escalation immediately, especially when payday has passed or facts are disputed. Do not promise “next payroll” or tell the worker to wait for client billing as a default answer.

    Illustrative case: two hours disappeared after approval

    A worker reports that a ten-hour Tuesday appears as eight paid hours. The original time entry and host confirmation both show ten, but the payroll input contains eight. For this constructed example, the difference is at the approval-to-payroll handoff, not in the worker’s submission.

    The coordinator records the two-hour difference and assigns the payroll investigation. Payroll determines the correct wage treatment, including whether other earning lines are affected, and provides the adjustment reference and timing. The coordinator does not calculate a final amount from two hours alone or ask the worker to resubmit the entire week.

    The case remains open until the resulting pay evidence is checked and the worker receives an explanation. If only the assignment’s future setup was corrected, the historical shortfall is still unresolved.

    Close with evidence, then repair the upstream cause

    Use distinct states: Reported → Evidence review → Decision recorded → Correction processing → Verification → Closed. A case can also be awaiting evidence, escalated or reopened. Each nonterminal state needs an owner and next update time.

    • Reconcile the outcome: payroll identifies what changed, which period it affects and the actual correction evidence. Check any remaining difference.
    • Explain it to the worker: provide the relevant dates, decision, correction or reason no correction was made, and a clear route to challenge unresolved facts.
    • Record unresolved receipt: if the worker still reports no payment, continue the delivery investigation. Silence is not confirmation.
    • Fix the cause separately: link the case to an owner for the export, effective-date, approver or setup problem. A process fix does not substitute for resolving this worker’s pay.

    Use the staffing timesheet approval workflow to improve upstream submission and approval controls. Keep worker payment resolution distinct from any subsequent client invoice or commercial dispute.

    Where Workhint fits

    Workhint’s Workflow Engine supports routing requests and approvals to defined roles and requiring details, files or approval steps before work moves forward. A staffing team could use that structure for the report, evidence review, payroll decision and worker-update handoffs described here.

    The Staffing Managers solution describes worker-submitted hours, manager timesheet review and tracking payout details and payment history. That makes the assignment/time context relevant to a pay-case workflow. It does not establish that Workhint calculates statutory wages, makes a payroll correction in another system or guarantees payment timing.

    Keep the actual payroll decision and payment evidence with the authorized employer/provider. Design the workflow around those responsibilities rather than treating an internal “approved” label as proof the worker has been paid.

    Questions staffing coordinators should settle

    Who owns the case when the host and payroll disagree?

    The named coordinator keeps the case moving, but should not invent the work facts or wage decision. Obtain the host’s evidence and payroll’s documented position, then escalate unresolved issues to the authorized agency leader and qualified reviewers.

    Does an approved timesheet prove correct payment?

    No. Compare the approved version with the payroll input and paid wage lines for the same period. A correct time approval can still be followed by an export, rate or processing error.

    Can the report be closed when payroll says “submitted”?

    Not as a verified correction. Submission is an intermediate state. Retain the processing reference and follow through to the actual result, including any unresolved payment-receipt concern.

    What if no pay error is found?

    Explain the period, hours and relevant earning lines used in the decision, record the evidence and provide a way to dispute remaining facts. Do not close merely because the worker stopped replying.

    Comments

    Leave a Reply

    Your email address will not be published. Required fields are marked *


    The reCAPTCHA verification period has expired. Please reload the page.