9 Common Pay Stub Errors Employers Make

Most pay stub errors are typing failures, not accounting failures.

Somebody re-entered the company address from memory. Somebody copied last period’s stub and forgot to roll the year-to-date column. Somebody put the 401(k) match in the deductions section because that’s where it looked right. None of that requires incompetence. It requires being busy.

The trouble is that in most states a pay stub is a legal document with mandated contents, not a receipt, so a stub can be arithmetically perfect and still illegal. Here are the errors that actually cost employers money, what each one is worth, and how to stop making them at the source.

This article is general information, not legal or tax advice. Wage statement rules vary by state and change. Check with your state labor department or a qualified professional before setting policy.

Why pay stub errors cost more than they look

The dollar figures are worse than the intuition. Research by EY, reported by Paycom, put the error rate for organizations running traditional, non-automated payroll processes at roughly 20%, with an average cost of $291 to correct a single payroll error. A single Form W-4 error averages $539 to remediate. Nearly one in six businesses in that research reported legal, compliance, or regulatory trouble stemming from payroll errors.

That number is about businesses hitting compliance problems, not about paychecks being wrong. You’ll see a widely-quoted claim that “1 in 6 paychecks contains an error” on paystub vendor blogs. It has no traceable source. Ignore it.

“Pay stub error” also isn’t one thing. It’s three separate problems, and they carry very different consequences:

| Error type | Example | What it costs | |---|---|---| | Missing field | No total hours worked; DBA instead of legal entity name | Wage statement penalties. In California: $50 first period, $100 per employee per period after, $4,000 cap, plus attorney’s fees | | Math error | Overtime on base rate; YTD that doesn’t roll | Back wages, plus liquidated damages under the FLSA | | Classification error | 1099 issued to someone who is legally a W-2 employee | Back FICA, failure-to-withhold penalties, interest, lost Section 3509 relief if intentional |

Missing-field errors are the cheapest to make and, per dollar of effort, the most expensive to litigate. That’s where to start.

Errors 1-3: the fields that make a stub non-compliant

California’s Labor Code §226(a) is the strictest widely-cited standard, which makes it a useful common denominator. Build to it and you’re compliant nearly everywhere. It requires nine items on every itemized wage statement:

Gross wages earned
Total hours worked (for non-exempt employees)
Piece-rate units earned and the applicable piece rate, if paid that way
All deductions
Net wages earned
The inclusive dates of the pay period
The employee’s name and the last four digits of their SSN (or an employee ID)
The legal name and address of the employer entity
All applicable hourly rates in effect, with the number of hours worked at each rate

Error 1: The employer’s DBA instead of the legal entity. Your storefront is “Corner Coffee.” Your registered entity is “CCB Holdings LLC.” The stub needs the second one. This is the single easiest violation to commit, and it stays invisible until a plaintiff’s attorney is reading a year of stubs looking for exactly this.

Error 2: Total hours worked, omitted. Common when an employer pays a non-exempt employee a fixed salary or a flat weekly amount and figures hours are beside the point. They aren’t. If the employee is non-exempt, the hours belong on the document.

Error 3: The full SSN, printed. Some templates still do this. §226 requires the last four only, and a full SSN on a stub is both a compliance problem and a data breach waiting for a lost envelope.

Under §226(e), a knowing and intentional violation costs the greater of actual damages or $50 for the initial pay period and $100 per employee per subsequent pay period, capped at $4,000 in the aggregate, plus costs and reasonable attorney’s fees. The attorney’s fees clause is the part that matters. It’s what makes a $4,000 claim worth a lawyer’s time.

State rules vary widely. Nine states (Alabama, Arkansas, Florida, Georgia, Louisiana, Mississippi, Ohio, South Dakota, Tennessee) have no pay stub requirement at all. Hawaii is the only opt-in state for electronic delivery. Delaware, Minnesota, and Oregon are opt-out. Published roundups of this drift, so confirm the rule against your own state labor department rather than trusting a table.

Errors 4-6: the math that quietly doesn’t add up

Error 4: Overtime calculated on the base rate. The FLSA requires overtime at 1.5x the regular rate of pay, which is not the same as the hourly rate on the offer letter. Non-discretionary bonuses, commissions, shift differentials, and certain incentive pay have to be rolled into the regular rate before you multiply.

An employee at $20/hour who works 50 hours in a week and earns a $200 non-discretionary production bonus has straight-time earnings of $1,200 for that week, so their regular rate is $24 an hour, not $20. The overtime premium on those 10 extra hours is owed on $24. Paying it on $20 underpays them, and the FLSA gives employees two years to file a complaint, three if the violation was willful, per the DOL Wage and Hour Division. A systematic error compounds across every employee and every period in that window.

Error 5: Year-to-date columns that don’t roll forward. This happens the moment someone builds a stub by duplicating the last one and updating the current-period numbers. The YTD column keeps whatever it had. By December, YTD gross doesn’t reconcile to the W-2, and the employee who does reconcile it will ask why.

Error 6: Rounding drift. Most advice on this stops at “double-check your math” without ever explaining why the math goes wrong in the first place. Spreadsheets and most programming defaults store money in binary floating point, which cannot exactly represent a value like 0.10. Add enough of them and you get totals ending in fractions of a cent, which then round in inconsistent directions. Gross stops equalling net plus deductions by a penny, and nobody can find the penny.

The structural fix is exact decimal arithmetic, not more checking. Payslip44 does money math in decimal end to end for this reason, so the totals line ties out because it can’t do anything else. If you’re building stubs in a spreadsheet, at minimum round each line item to two decimals explicitly before summing, rather than summing then rounding.

Errors 7-8: deductions and withholding

Error 7: Pre-tax and after-tax, mixed up. A 401(k) contribution or an HSA deduction booked as after-tax doesn’t just look wrong on the stub. It changes taxable wages, which cascades into the W-2, which cascades into the employee’s return. This is one of the few stub errors that reliably becomes someone else’s tax problem.

Sort every deduction into exactly three buckets before you enter it: tax withholding, pre-tax deduction, after-tax deduction. If you can’t say which bucket a line belongs in, that’s the item to check.

Error 8: Employer contributions shown as employee deductions. The employer’s 401(k) match is not withheld from the employee. Neither is the employer share of FICA or the employer portion of a health premium. Putting them in the deductions column makes the stub say the employee paid something they didn’t, and it makes net pay reconciliation impossible. Employer contributions belong in their own section, informational, not subtracted.

Also on this list, less dramatic but common: withholding computed from a stale W-4, deductions omitted entirely (garnishments and union dues are the usual casualties), and the same deduction entered twice because two people were editing the same period.

Error 9: misclassification, which poisons the whole document

This is the one nobody connects to pay stubs, and it’s the biggest.

Worker classification isn’t a formatting choice. It determines which lines legally belong on the document at all. A W-2 employee’s stub carries withholding, employer contributions, and hours. A 1099 contractor’s payment record carries none of that. A statutory employee is a hybrid: FICA is withheld, income tax is not. An owner or partner draws differently again.

Get the classification wrong and every line beneath it is wrong. You cannot fix that by editing a field.

The IRS applies three tests, described on its independent contractor vs. employee page: behavioral control (who directs how the work is done), financial control (who bears the business expense and profit risk), and relationship type (contracts, benefits, permanence, whether the work is core to the business).

The exposure for getting it wrong: back FICA plus a failure-to-withhold penalty. Section 3509 offers reduced rates for unintentional misclassification, and that relief disappears entirely if the misclassification was intentional. If you’ve already discovered a problem, the IRS runs a Voluntary Classification Settlement Program (Form 8952) that lets employers reclassify workers prospectively for roughly 10% of one year’s employment tax liability on those workers. It exists precisely because self-correcting beats being found.

Lock the classification onto the worker’s record, once, before you issue anything. In Payslip44 that’s a field on the employee (W-2, 1099, statutory, owner), so it’s a decision you make deliberately rather than one you infer from whatever template you opened.

How to correct a pay stub error, step by step

So you found one. Work in this order.

Document it. Which employees, which pay periods, which amounts, when you discovered it. This record is what separates “we fixed it” from “willful” if anyone ever asks.
Recalculate from source records, not from the bad stub. Go back to time cards, rate tables, and the W-4.
Tell the employee before they tell you. An employer who reports the error and a timeline is in a very different position than one who is responding to a complaint.
Reissue the corrected stub for the affected period. The stub is the legal record for that period, so correcting it on the next one leaves the wrong document standing.
If the tax year is already closed, correct upstream: Form W-2c for a filed W-2, and Form 941-X for the affected quarter.
Check your state’s clock. Under ORS 652.120(5), Oregon gives an employer three business days after it has notice to pay an unpaid amount that is 5% or more of the employee’s gross wages for the period; below that threshold it can go on the next regular payday. And if the shorted employee has already quit or been fired, the stakes change: California’s waiting-time penalty applies to unpaid final wages and can run up to 30 days’ wages. There is no federal deadline, which is not the same as having time.

The pre-send checklist

Run this before the stub leaves your hands. It takes ninety seconds.

[ ] Employer legal entity name and address (not the DBA)
[ ] Employee name and last four of SSN only
[ ] Pay period start and end dates, plus the pay date
[ ] Total hours worked for non-exempt employees
[ ] Every hourly rate in effect, with hours at each rate
[ ] Overtime computed on the regular rate, with bonuses and differentials rolled in
[ ] Gross = net + all deductions. Check it. To the cent.
[ ] YTD columns rolled forward from the last period
[ ] Each deduction sorted into tax / pre-tax / after-tax
[ ] Employer contributions in their own section, not deductions
[ ] Worker classification (W-2 / 1099 / statutory / owner) matches the withholding shown
[ ] Preview the actual output document, not the input form

Then keep it. Under DOL Fact Sheet #21, the FLSA requires payroll records be preserved for at least three years, and the records that wage computations rest on (time cards, wage rate tables, work schedules, records of additions and deductions) for two years.

Look back at that checklist and notice what most of it is: things you type in every single period, that never change, and that only go wrong because someone typed them again. The structural fix is to stop retyping them. Saved employer records mean the legal name is entered correctly once. Saved employee records mean the classification is set once. Reusable line-item templates mean the same deduction lands in the same bucket every period.

Vigilance fails on a Friday afternoon. Templates don’t.

Frequently Asked Questions

What are the most common pay stub errors employers make?

Missing required fields (total hours, pay period dates, employer legal name), overtime computed on the base rate instead of the regular rate, stale or non-rolling YTD totals, omitted or duplicated deductions, pre-tax and after-tax miscategorization, and worker misclassification.

Is an employer legally required to give a pay stub?

It depends on the state. Most states plus DC require it; nine (Alabama, Arkansas, Florida, Georgia, Louisiana, Mississippi, Ohio, South Dakota, Tennessee) have no pay stub requirement. Federal law doesn’t mandate the stub itself, but the FLSA does require the underlying payroll records.

What has to be on a pay stub?

Requirements vary by state. California’s Labor Code 226 is the strictest common benchmark: nine items including gross wages, total hours worked, all deductions, net wages, inclusive pay period dates, employee name and last four of SSN, the employer’s legal name and address, and all hourly rates in effect with hours at each.

What happens if a pay stub is wrong?

It depends on the error. A math error means back pay. A missing-field error can be a wage statement violation: in California, $50 for the first pay period and $100 per employee per pay period after, up to $4,000, plus the employee’s attorney’s fees. A classification error can trigger back FICA, withholding penalties and interest.

How long does an employer have to fix a payroll error?

There is no federal deadline. State rules govern: Oregon requires payment within three business days of notice when the unpaid amount is 5% or more of the employee’s gross wages. In California, if the employee has already quit or been discharged, unpaid final wages can trigger a waiting-time penalty of up to 30 days’ wages. Employees have two years to file a federal wage complaint, three if the violation was willful.

How do you correct a pay stub after it’s been issued?

Document the error, recalculate from source records, notify the employee, and reissue a corrected stub. If the error already flowed into a filed W-2, file Form W-2c. If it affected a filed Form 941, file Form 941-X.

Can an employer correct a pay stub error on the next paycheck instead?

Sometimes, but not always. Several states require correction sooner when the shortfall is material. Reissuing a corrected stub for the affected period is the safer practice, since the stub is the legal record for that pay period.

What’s the penalty for misclassifying an employee as a 1099 contractor?

Unintentional misclassification exposes the employer to back FICA plus a failure-to-withhold penalty. Intentional misclassification forfeits IRS Section 3509 reduced-rate relief and carries steeper penalties. The Voluntary Classification Settlement Program (Form 8952) allows prospective reclassification at roughly 10% of one year’s employment tax liability.

How long do employers have to keep pay stubs and payroll records?

Under the FLSA, payroll records must be kept for at least three years, and the records the wage computations are based on (time cards, rate tables, schedules) for two years. Some states require longer.

The short version

The expensive errors aren’t the ones that look expensive. A missing address line stacks penalties per employee per pay period. A misclassification invalidates every number underneath it. Meanwhile the arithmetic, the part everyone worries about, is the part a machine can just get right.

Build the stub from saved records instead of retyping it, set the classification deliberately, let decimal math handle the cents, and check the preview against the list above before you send.

Payslip44 builds paystubs line by line from reusable employer, employee, and item templates, with tax classification on the employee record and decimal-precise money math, entirely on your device. It’s a document builder, not a tax calculator, so the withholding numbers are still yours to get right. Download it, or read more on the blog.

Frequently Asked Questions

What are the most common pay stub errors employers make?

Is an employer legally required to give a pay stub?

It depends on the state. Most states plus DC require it; nine (Alabama, Arkansas, Florida, Georgia, Louisiana, Mississippi, Ohio, South Dakota, Tennessee) have no pay stub requirement. Federal law doesn't mandate the stub itself, but the FLSA does require the underlying payroll records.

What has to be on a pay stub?

Requirements vary by state. California's Labor Code 226 is the strictest common benchmark: nine items including gross wages, total hours worked, all deductions, net wages, inclusive pay period dates, employee name and last four of SSN, the employer's legal name and address, and all hourly rates in effect with hours at each.

What happens if a pay stub is wrong?

It depends on the error. A math error means back pay. A missing-field error can be a wage statement violation: in California, $50 for the first pay period and $100 per employee per pay period after, up to $4,000, plus the employee's attorney's fees. A classification error can trigger back FICA, withholding penalties and interest.

How long does an employer have to fix a payroll error?

There is no federal deadline. State rules govern: Oregon requires payment within three business days of notice when the unpaid amount is 5% or more of the employee's gross wages. In California, if the employee has already quit or been discharged, unpaid final wages can trigger a waiting-time penalty of up to 30 days' wages. Employees have two years to file a federal wage complaint, three if the violation was willful.

How do you correct a pay stub after it's been issued?

Can an employer correct a pay stub error on the next paycheck instead?

What's the penalty for misclassifying an employee as a 1099 contractor?

How long do employers have to keep pay stubs and payroll records?