Raising a Paycheck Error

Why this matters

Most paycheck errors are honest: a lunch the system deducted automatically, a ticket closed after the cutoff, an hour typed into the wrong box. Most get fixed the same day when someone asks clearly. The ones that do not get fixed usually fail for a reason on the tech's side: the question was vague ("my check seems light"), it was asked in the wrong place (shouted across the shop), or it was never put in writing, so three weeks later nobody remembers it was raised. The order below turns a hunch into a specific, checkable number, gives the shop an easy way to fix it, and leaves a paper trail if it does not.

This is not legal advice. It covers the ordinary path; where the steps say to stop and get help, take that seriously.

Step 1: Confirm it against your own record before you say anything

Put the stub next to your own log of start and stop times, jobs and flag hours, and find the exact line that disagrees. See related: Tracking Your Own Hours and Pay for how to keep that log, and Reading Your Pay Stub as a Technician for what each line on the stub means.

Why first: a fair share of "short" checks turn out to be explained by something on the stub you had not read, such as a ticket that will pay next period, a pre-tax deduction you signed up for, or a pay period that ended on a Wednesday. Finding that out before you raise it costs you nothing. Finding it out in front of the office manager costs you credibility for the next question, which may be real.

What breaks if you skip it: you raise a feeling instead of a number, and a feeling is easy to wave off.

Step 2: Put a number and a cause on it

Write one or two sentences: which pay period, which line, what you expected, what you got, and the likely cause if you can see it.

Why: "Week of the 9th shows 44 hours; my log has 46 including the Friday 7 to 9 safety meeting" can be checked in thirty seconds. "I think I'm missing some hours" cannot. Naming the probable cause also lets the office fix the system, not just your check: if the Friday meeting was left off for one tech, it was likely left off for everyone in it.

Get the overtime right in your own head first. For a nonexempt worker under the Fair Labor Standards Act, hours past 40 in a workweek are owed at one and a half times the regular rate (29 U.S.C. 207). So missing hours in a week already over 40 are missing at overtime, not at straight time. That is the most common way a tech under-asks.

Step 3: Ask the person who can fix it, in person or by message, calmly

Go to whoever runs payroll, not the dispatcher and not the group chat. Ask at a quiet moment, not at 7:00 while the trucks are rolling.

Why: the payroll person can usually see the timecard and correct it on the spot, and nobody fixes things well while being embarrassed in front of a crew. Keep the tone neutral: you are reporting a discrepancy, not accusing anyone. If the shop is small enough that payroll is the owner, the same applies.

A conversation that works sounds like this:

TECH:   Got a minute on my last check? Week of the
        9th shows 44 hours. I've got 46.
OFFICE: Hang on. 44 is what the timecard says.
TECH:   Friday we had the safety meeting 7 to 9
        before calls. I clocked in at 9 after it,
        because that's what we were told to do.
OFFICE: Right, everybody did. Meeting's paid,
        it should have gone in by hand.
TECH:   That puts me at 6 hours over 40, not 4.
        So it's 2 hours at time and a half.
OFFICE: Let me check the others in the meeting.
        I can do it on the next check.
TECH:   Next check works. I'll send you a quick
        text so we both have it.

Notice what the tech did not do: did not ask "why did you shortchange me," did not threaten anything, did not drag the other techs' pay into it, and did not leave without agreeing on a date.

Step 4: Follow up in writing the same day

Send a short text or email that restates what you discussed and what was agreed. For the conversation above:

"Thanks for looking at this. Confirming: week of the 9th, the Friday 7 to 9 safety meeting wasn't on my timecard, so I'm at 46 hours, 6 of them overtime. The difference is 2 hours at time and a half, to be added on the next regular check."

Why: a written follow-up turns a hallway conversation into a dated record that you raised the issue, what the number was, and what the shop agreed to do. If the fix lands, the message cost you nothing. If it does not, the message is the first exhibit in any complaint, and it shows you gave the shop a fair chance.

What breaks if you skip it: "I told them" becomes your word against a busy office manager's memory.

Step 5: Check the next stub, and give it one more nudge if needed

On the agreed payday, look for the correction as its own line or as adjusted hours. If it is not there, send one more polite message referencing the first one: "Following up on my note from the 16th; I don't see the 2 overtime hours on this check. Can you tell me when it'll be added?"

Why a set date matters: few states set a separate deadline for correcting an underpayment, but most states have a payday law requiring wages to be paid on a regular schedule, so a fix that drifts across several paydays is a payday-law problem as well as a pay problem. One reminder is reasonable. A third and fourth reminder over two months is the shop telling you something.

Step 6: Go above the payroll person, still in writing

If two paydays pass with no fix and no clear reason, write to the owner or general manager. Attach or quote your earlier messages, state the number again, and ask for a date.

Why: sometimes the payroll person does not have authority to pay a correction, or disagrees with you on a policy question (whether meetings are paid, how a recall is coded) and has not said so. The owner may see it differently, and in any case you now have a record that the person with authority was told.

Step 7: Know when to take it outside the shop

If the owner refuses, ignores you, or says the time is not compensable when you believe it is, you have outside options. This is the fork where you stop acting on an article.

• The state labor agency (usually the department of labor or labor commissioner) takes wage claims at no cost and often enforces state rules that are stronger than federal ones. Many states' minimum wage, final-pay and daily-overtime rules exist only at the state layer.
• The U.S. Department of Labor's Wage and Hour Division takes FLSA complaints, also free, and keeps the identity of the person who complained confidential to the extent the law allows.
• An employment attorney is worth a call when several techs are affected, when you have been disciplined or had hours cut after raising it, or when the dispute is about how you are classified (exempt, independent contractor). Under the FLSA a winning employee recovers back pay plus an equal amount in liquidated damages, and the employer pays reasonable attorney's fees (29 U.S.C. 216(b)), which is why many wage attorneys take these cases on contingency. Some states go further, such as Massachusetts, whose Wage Act makes damages triple.

Walk in with: your log, the stubs for the affected periods, your written messages and any replies, and the handbook or pay-plan document if you have one.

Watch the clock. Federal claims reach back two years, or three for a willful violation (29 U.S.C. 255). State deadlines differ and are often longer; California, for example, allows three years on most wage claims. Errors older than the window cannot be recovered however solid the record.

Retaliation is illegal. Firing or otherwise discriminating against an employee for filing a wage complaint is prohibited under federal law (29 U.S.C. 215(a)(3)), and courts and the Department of Labor generally treat a complaint made internally to the employer as protected, not only one filed with an agency. Most states have their own anti-retaliation rules too. If hours or assignments change right after you raise a pay issue, write down the dates and go to the agency or an attorney rather than arguing it out in the shop.

Worked example: what the 2 hours are worth

The tech above earns an hourly rate, call it R. The log shows 46 hours in the workweek. The stub paid 40 regular hours and 4 overtime hours.

• Paid: 40 hours times R, plus 4 hours times 1.5 R (which is 6 R), for 46 R.
• Owed: 40 hours times R, plus 6 hours times 1.5 R (which is 9 R), for 49 R.
• Difference: 49 R minus 46 R is 3 R, which is exactly the 2 missing hours at 1.5 R each.

Had the tech asked for "2 more hours," the shop could have added 2 R and closed it, leaving 1 R on the table. Across a crew of six who all sat in the same meeting, the shop's correction is 6 times 3 R, or 18 R, which is why the tech's naming of the cause (the meeting, not "my timecard") matters to the shop as much as to the tech.

What changes the answer. If this tech worked in California, the meeting hours also fall into a daily count: under state law, hours past 8 in a workday are owed at one and a half times, so if Friday's total including the meeting ran past 8 hours, those hours are daily overtime there, and in a shorter week that never reached 40 the same meeting could still owe overtime. If the tech were exempt (a salaried manager meeting the federal duties and salary tests), no overtime would be owed at all, and the conversation would be about something else. And if the error had run the other way (overpaid), whether the shop can simply deduct the overpayment from a future check is a state question: some states allow it with written notice, others require your signed authorization, and federally a deduction may not take pay below the minimum wage or eat into overtime owed.

References

• 29 U.S.C. 207 (overtime), 215(a)(3) (retaliation), 216(b) (damages and attorney's fees), 255 (limitations)
• U.S. Department of Labor, Wage and Hour Division: how to file a complaint
• Massachusetts General Laws chapter 149, section 150 (treble damages under the Wage Act); California Labor Code on daily overtime and wage claims
• See related: Tracking Your Own Hours and Pay; Reading Your Pay Stub as a Technician; Overtime Rights a Tech Should Know