7 Paystub Errors Employees Should Catch Early

A paystub error caught in the first pay period it appears costs minutes to fix; the same error caught in March of the following year costs a W-2c, an amended return, and sometimes a referral to your state labor agency. Most employees only glance at the net-pay figure on payday, which is exactly the figure most likely to look correct even when something underneath it is wrong. The five-minute review below covers seven error categories that compound silently — pay period, hours, rate, overtime, deductions, identity, and YTD — and the document, the recipient, and the escalation path that corrects each one. The DOL FLSA recordkeeping rules require your employer to keep accurate pay-period records under 29 CFR §516.2; the IRS About Form W-2c page covers the correction when a year-end record needs amending; and IRC §6051 is the statute that ultimately makes your employer responsible for the W-2 your paystub feeds.

The seven-item scan every employee should run, in the order the fields appear on a standard paystub:

• Pay period dates — start and end dates that match your stated frequency (weekly, biweekly, semimonthly, monthly)
• Hours worked — regular hours, overtime hours, holiday hours, PTO hours, each broken out
• Pay rate — hourly rate or salary per period, matching your offer letter or most recent raise
• Overtime premium — at least 1.5x your regular rate for hours over 40 in a workweek under FLSA (state rules can be stricter)
• Deduction stack — pre-tax health, HSA, 401(k); post-tax Roth; federal income tax; state; FICA at 6.2% SS + 1.45% Medicare
• Identity fields — your legal name, SSN last four, address; employer legal name, EIN, address
• YTD totals — gross, taxable wages, each tax type, each deduction, net — all rolling forward correctly from period to period

The threaded character for this post: Jordan Park, senior business analyst at a Chicago consulting firm. Salary $105,000, biweekly = $4,038.46 gross/period. After Jordan changed benefit selections during open enrollment in February 2026, his employer's payroll system stopped applying the $200/period HSA contribution as pre-tax but kept deducting it post-tax. Across the eight pay periods before he caught it, $1,600 of HSA contributions were mis-categorized as taxable wages — pushing Box 1 federal-taxable wages higher and overwithholding federal income tax at his 24% marginal rate plus the 7.65% FICA he shouldn't have paid on HSA dollars. Jordan caught it by comparing his YTD HSA contribution against his YTD Box 1 wages and noticing Box 1 didn't drop by the expected $1,600. The rest of this post walks through the seven categories, Jordan's actual math, the correction request, and the W-2c that ultimately closed the loop.

#The Seven Error Categories, In Detection Order

The order below tracks the order the fields appear on a standard ADP, Gusto, Paychex, or Workday stub. Run the scan in this order every pay period; catching an error in category 1 often surfaces a related issue in category 5 (deduction stack changes when a benefit enrollment date shifts), so the sequence matters.

#1. Incorrect Pay Period Dates

The pay period is the date range the stub covers (e.g., "5/4/2026 – 5/17/2026"). The pay date is when the money lands (e.g., "5/22/2026"). For biweekly pay, the period should be exactly 14 days; for semimonthly, the 1st–15th and 16th–end-of-month; for weekly, exactly 7 days. A period that drifts from the stated frequency (a "biweekly" stub covering 13 days, then 15 days next period) signals a payroll re-run or a missed-period correction the reviewer wants explained. The fix is fast: payroll re-runs the period and issues a corrected stub. Don't ignore it — drift in period dates is the single most common reason YTD totals stop reconciling in category 7.

Detection: Stub start date − stub end date ≠ your standard period length, or pay date falls on a non-business day with no holiday explanation.

Who to contact: Payroll administrator (HR for smaller employers, payroll-shared-services email for larger ones).

Document that corrects it: Replacement paystub for the affected period. No W-2c needed if caught in the same calendar year.

#2. Wrong Hours Worked

Hourly employees: the regular hours, overtime hours, holiday hours, and PTO hours on the stub must match the timekeeping system (ADP TimePro, UKG, Kronos, Paychex Time). Salaried employees still see hours on most stubs (typically 80 for biweekly, 86.67 for semimonthly) even though the figure doesn't drive gross pay. A salaried stub showing 75 hours instead of 80 won't change your paycheck but can affect benefit accruals or PTO-balance reporting downstream.

Detection: Compare timesheet hours (regular + OT + holiday + PTO) against the corresponding lines on the stub. Variance over 0.25 hours is worth flagging.

Who to contact: Direct manager first (to confirm the timesheet was approved), then payroll if the timesheet shows correct hours but the stub does not.

Document that corrects it: Corrected stub plus a retroactive pay adjustment line on the next stub for the difference in hours times rate.

#3. Incorrect Pay Rate

The rate on the stub should match your offer letter, your most recent merit-increase letter, or the rate confirmation HR sent after your last role change. Jordan's case: his salary went from $95,000 to $105,000 effective January 1, 2026, after a January promotion. His January 17 stub correctly showed the new $4,038.46 biweekly gross. If the rate had remained at $3,653.85 (the $95,000 / 26 biweekly figure), Jordan would have caught it the first period because the gross-pay line is the single most-visible field on the stub.

Detection: Stub gross pay (salaried) = annual salary / number of periods per year. For Jordan: $105,000 / 26 = $4,038.46. Anything other than $4,038.46 needs an explanation.

Who to contact: HR business partner first (to confirm the rate change took effect), then payroll if HR confirms the change should be in the system but isn't.

Document that corrects it: Corrected stub plus a retroactive-pay line for the periods at the wrong rate. If discovered in a subsequent calendar year, a W-2c may be required.

#4. Missing or Unusually Low Overtime

The FLSA requires non-exempt employees to be paid at least 1.5x their regular rate for hours worked over 40 in a workweek. State rules can be stricter (California requires 1.5x over 8 hours/day and 2x over 12 hours/day; see CA Labor Code §226 for the paystub itemized-statement requirement). Exempt salaried employees aren't entitled to overtime under federal law, but state-level exempt thresholds shift annually — confirm exempt classification with HR if you're not sure.

Detection: Workweek hours total > 40 → check for an "Overtime" line at 1.5x rate. Workweek hours total > 50 → check the OT line covers all hours over 40, not just the first few.

Who to contact: Payroll for the OT calculation; HR if classification (exempt vs. non-exempt) is unclear.

Document that corrects it: Retroactive OT pay on the next stub plus a corrected period stub. Repeated failure to pay OT is a wage-and-hour violation under FLSA and grounds for a DOL Wage and Hour Division complaint.

#5. Unexpected Deduction Changes (Jordan's Category)

This is the error Jordan caught. Pre-tax deductions (Section 125 health premiums, HSA, traditional 401(k), Section 132 transit) lower Box 1 federal-taxable wages and FICA wages. Post-tax deductions (Roth 401(k), garnishments, union dues, after-tax charity) do not. A deduction that switches from pre-tax to post-tax — or that gets miscoded by the payroll system after an open-enrollment selection — quietly raises Box 1 and FICA without changing the dollar amount deducted from the gross. The employee sees the same $200/period coming out and assumes nothing changed; the IRS sees $1,600 in additional taxable wages by the time Jordan catches it in April.

Detection: Compare each deduction line to the prior stub. Any line that changes amount, classification (pre-tax vs. post-tax), or disappears entirely needs an explanation. Cross-check against your benefit-enrollment confirmation email.

Who to contact: Benefits administrator first (to confirm the elected coverage), then payroll if the elected coverage doesn't match what's deducting.

Document that corrects it: Reclassification on the next stub plus a YTD adjustment moving the affected dollars from post-tax to pre-tax. If discovered after year-end, requires a W-2c showing the corrected Box 1 and Box 12 figures.

#6. Incorrect Employee or Employer Information

Your legal name on the stub must match the name on file with SSA, because the employer reports W-2 wages to SSA under that name. Address mismatches don't trigger SSA flags but do mean year-end forms (W-2, 1095-C, 1099-MISC for any prizes or awards) ship to the wrong address. Employer information must show the legal entity (not just the DBA), the federal EIN (XX-XXXXXXX format), and a current address.

Detection: Compare every identity field to your driver's license, Social Security card, and most recent W-2 from the same employer.

Who to contact: HRIS administrator (Workday, BambooHR, Rippling, Gusto) to update employee records; payroll for downstream stub regeneration.

Document that corrects it: Updated stub. If the legal name on prior W-2s was wrong, a W-2c per IRS General Instructions for Forms W-2 and W-3.

#7. Year-to-Date Totals That Don't Reconcile

YTD totals on every stub must equal the prior stub's YTD plus the current-period figure, for every line. YTD gross, YTD Box 1 federal-taxable, YTD Social Security wages (capped at $184,500 for 2026 per the SSA wage base), YTD Medicare wages (uncapped), YTD federal income tax withheld, YTD state income tax withheld, YTD each pre-tax and post-tax deduction, YTD net pay. The reconciliation must hold to the dollar — drift indicates one of the prior categories had an error that propagated.

Detection: For each YTD field on the current stub, compute (prior-stub YTD) + (current-period figure). The result should equal current-stub YTD exactly. Anything different is a flag.

Who to contact: Payroll, with both stubs in hand. Most YTD-drift fixes are an out-of-cycle payroll adjustment.

Document that corrects it: Corrected YTD on the next stub, sometimes with a year-to-date adjustment line. If drift carries into year-end, a W-2c is needed.

#Jordan's HSA Mis-Categorization

Jordan's HSA contributions are $200/period, biweekly, intended to be pre-tax under Section 125 cafeteria-plan rules referenced in IRS Pub 969 (HSAs). Pre-tax means the $200 reduces Box 1 federal-taxable wages and reduces FICA wages (HSA contributions are exempt from federal income tax and FICA when made through a Section 125 plan). After his February 2026 open-enrollment selection, the payroll system kept deducting $200/period but stopped applying the pre-tax flag — the deduction continued post-tax. Jordan didn't notice because the dollar amount on the stub didn't change.

The math behind the totals row: 8 periods × $200 = $1,600 of HSA contributions that should have lowered Box 1 federal-taxable wages but did not. At Jordan's 24% federal marginal rate, that's $1,600 × 0.24 = $384 of federal income tax overwithheld during those eight periods. On the FICA side, $1,600 × 0.0765 (employee share of SS + Medicare) = $122.40 of FICA overwithheld. Combined: roughly $506 of taxes Jordan paid that he should not have, plus the HSA contribution itself is sitting in the wrong bucket on his year-to-date record.

Jordan caught it by running the YTD reconciliation in category 7: he expected YTD Box 1 wages on his May 23 stub to equal YTD gross minus YTD HSA contributions minus YTD pre-tax health premium minus YTD 401(k) deferral. The math didn't work — Box 1 was higher than expected by exactly $1,600. He pulled his benefit-enrollment confirmation from February showing he had elected the HSA as pre-tax, screenshot the YTD discrepancy on his current stub, and sent an email to payroll using the template at the end of this post. The fix took two pay periods: a YTD adjustment on the June 6 stub moving $1,600 from post-tax to pre-tax, a refund of the $506 in overwithheld taxes split across that stub and the next, and a confirmation note from payroll that the system flag was now correct going forward.

The two-period delay is typical. The longer the delay between the error and the catch, the harder the correction becomes. If Jordan had caught it in December 2026 instead of May, the correction would have required a Form W-2c per IRS About Form W-2c showing the corrected Box 1, Box 3, Box 5, and Box 12 figures, and Jordan would have needed to file his 2026 return using the corrected W-2 — adding three to four weeks of cleanup in March 2027.

#When a Corrected W-2 Is Required

A W-2c (Corrected Wage and Tax Statement) is filed by the employer to correct a previously issued W-2. The corrections that require a W-2c are narrower than employees often think — most in-year payroll errors get fixed on subsequent paystubs without ever touching the W-2.

The IRS does not impose a hard deadline for filing W-2c, but employers must do so "as soon as possible" after discovering the error. SSA penalties under IRC §6051 and the IRS General Instructions for Forms W-2 and W-3 accrue if the employer files W-2s with incorrect information and doesn't issue corrections. If the W-2 never arrives at all — distinct from a W-2 with errors — the employee files Form 4852 (Substitute for W-2) using the final paystub of the year to estimate wages and withholding, then amends the return when the actual W-2 arrives.

For employees, the W-2c triggers a downstream amended return (Form 1040-X) if the original return was already filed. The corrected Box 1, Box 3, Box 5, and Box 12 figures roll through to the federal return, the state return, any AGI-dependent credits (EITC, education credits), and any retirement-account deduction calculations. The cleanup compounds quickly, which is the argument for catching the error in the pay period it occurs.

#Detection, Contact, Escalation, Correction

A single matrix mapping each of the seven categories to the operational steps that close the loop.

The escalation column matters. If your employer's payroll team can't or won't fix the error after two written requests, the federal recourse is the Department of Labor Wage and Hour Division, which investigates FLSA violations and can require the employer to pay back wages plus liquidated damages. State recourse runs through the state labor agency; the next section covers the state-by-state paystub statutes that may apply.

#What Your Employer Must Include

FLSA recordkeeping under 29 CFR §516.2 requires the employer to maintain accurate pay-period records but does not require the employer to give the employee a paystub. The paystub mandate is state-law. Six states' paystub-itemization statutes worth knowing:

A handful of states have no paystub-itemization statute (e.g., Arkansas, Tennessee, South Dakota), in which case the FLSA-recordkeeping rule on the employer still applies but the employee has no statutory right to a paystub. Even in those states, most employers issue stubs as a matter of practice — the recordkeeping obligation falls on them either way under 29 CFR §516.2.

California's §226 is the most-cited statute in private wage-and-hour litigation because of the penalty structure: $50 for the first pay period the employer fails to provide an itemized statement, then $100 per pay period after, capped at $4,000 plus attorney's fees per employee. New York's §195 carries similar penalties under §198, plus a §195.1 wage-theft-prevention-act notice requirement at hire. If your stub doesn't include the fields the law in your state requires, that's actionable separately from any underlying wage error.

#8 Mistakes Employees Make

The eight items below are the mistakes that turn a fixable paystub error into a year-end W-2c, an amended return, or a referral to a state labor agency:

• Ignoring small deductions. A $15 line you don't recognize on a $4,000 stub is easy to skip. If that $15 is a wrongly-applied garnishment, union dues for a union you don't belong to, or a 401(k) loan repayment after the loan was paid off, it compounds across 26 pay periods into $390 the next year. Flag every unfamiliar line.
• Not comparing YTD across periods. YTD reconciliation is the single most powerful detection tool on a paystub. Most employees never run it. Five minutes per period catches what would otherwise become a W-2c next March.
• Accepting "we'll fix it next period" indefinitely. Payroll teams sometimes promise a fix and then forget. Two written requests with two-week gaps, then escalate to HR director. Don't let three months pass on a verbal promise.
• No written record of the report. Phone calls and Slack messages disappear. Email creates a record. Every error report should go in writing with the stub attached.
• Missing the W-2c deadline window. Once the W-2 is issued in January, every additional week before requesting a W-2c increases the chance the employer's payroll team will defer it. The IRS recommends filing "as soon as possible"; in practice, employees should ask for the W-2c within 30 days of discovering the error.
• Not checking benefit-enrollment confirmations. Open-enrollment selections must propagate from the benefits system (Workday, BambooHR, Rippling) to the payroll system. They don't always. The confirmation email from open enrollment is the document that establishes what you elected; if the payroll-stub deduction doesn't match the confirmation, that's the error.
• Treating Box 1 as gross. Box 1 federal-taxable wages is gross minus pre-tax deductions (Section 125 health, HSA, traditional 401(k), Section 132 transit). A loan application or rental screening that asks for "annual gross" usually wants Box 3 (Social Security wages, which exclude only 401(k) and a few smaller items) or the year-to-date gross on the December stub. Submitting Box 1 where the form asked for gross may undercount your income by 5–15%.
• Ignoring the Additional Medicare Tax threshold at $200,000. Once year-to-date Medicare-eligible wages cross $200,000 (filing single) or $250,000 (filing MFJ), the Additional Medicare Tax of 0.9% kicks in on the excess. Employers withhold automatically once you cross $200,000 with that employer, but two-employer households can over- or under-withhold; reconcile on Form 8959 at filing time.

Print this list once and run it every pay period. It takes five minutes:

The MyStubs tools that help with the verification side: the paycheck calculator models gross-to-net by state so you can confirm the expected federal, state, and FICA on any given stub; the paystub generator reconstructs a clean stub from real payroll inputs when your employer's portal is down or a copy was lost. For the broader anatomy of what should appear on a paystub, the companion guide on what should appear on a paystub walks every field in detail. For how paystubs differ from contractor records, see W-9 vs. W-2. For the federal-vs-state tax distinction underlying the deduction stack, see payroll tax vs. income tax. For paystub access rules and digital portal expectations in 2026, see paystub access in 2026, and for the distinction between a paystub and other income proofs, see paystub vs. bank statement vs. 1099 income proof.

Copy, paste, and fill the bracketed fields. Send this to your payroll administrator with the affected paystub(s) attached. Keep a copy. If the error isn't corrected on the next two pay periods, forward the same email chain to your HR business partner with a one-line escalation note.

Jordan used this template verbatim on May 24, 2026, the day after he caught the HSA error. Payroll confirmed receipt within four business hours, processed the YTD adjustment on the June 6 stub, and refunded the over-withheld federal income tax ($384) and FICA ($122) split across the June 6 and June 20 stubs. The total elapsed time from email-sent to fully-corrected was 14 days. Naming the specific dollar amount of the discrepancy and the underlying classification issue saved Jordan roughly a week compared to a general "I think something's wrong with my deductions" email.

#DOL Wage and Hour Path

When the employer doesn't fix the error, the federal recourse for FLSA-covered violations (unpaid wages, unpaid overtime, recordkeeping failures) is the Department of Labor Wage and Hour Division complaint process. The WHD investigates, can order back-wage payment plus liquidated damages, and can refer egregious cases for criminal prosecution. Filing is free, can be anonymous in some cases (though the investigation typically requires the complainant's identity), and starts a clock under 29 USC §216(b) for any private right of action the employee might bring separately.

The state-level path runs through the state labor agency: California's Division of Labor Standards Enforcement, New York's Department of Labor Wage Theft division, Illinois Department of Labor, Texas Workforce Commission. State enforcement is sometimes faster than federal but with smaller damages caps; some states (CA, NY) carry both a statutory minimum and waiting-time penalties on top of the underlying wage claim.

What doesn't escalate to DOL: deduction mis-categorizations (Jordan's HSA case), pre-tax vs. post-tax classification errors, identity-field corrections, and W-2c issuance. Those are payroll-administration issues handled inside the employer; the federal recourse is filing Form 4852 (Substitute W-2) if the employer refuses to issue a W-2 or a W-2c, plus IRS notification per the IRS About Form W-2c instructions.

#Official sources