Payroll Error Underpayment: How to Catch It Before It Becomes Wage Theft

Key Takeaways

• Most underpayment comes from a pay rule configured correctly in the past and never revisited again.
• Intent can affect the penalty but not the liability. FLSA back pay can double through liquidated damages, and some state windows run six years.
• It hides because it pulls labor cost below plan, and the employees it affects are the least likely to report it.
• Reliable detection means recalculating what each employee should have been paid and comparing that to what the cycle is about to pay.
• Remediation covers the full affected population back to the date the rule broke, not only the person who complained.

A payroll error underpayment can be surprisingly easy to miss. On the payroll side, a small amount can disappear inside a much larger total. On the employee side, a few missing dollars may go unnoticed too. And even when employees do catch it, they may decide it is not worth chasing down.

Speaking up about your paycheck can be uncomfortable. When the amount is small, it can feel easier to let it go than to ask questions, follow up, and potentially push more than once just to get it corrected.

And those small amounts add up. In fiscal year 2025, the U.S. Department of Labor’s Wage and Hour Division recovered $259 million in back wages for nearly 177,000 workers, about $1,465 per worker.

In many cases, the problem can start with something very simple: one pay rule coded incorrectly, one setting left untouched, one mistake repeated across paycheck after paycheck. By the time it is discovered, the issue may have been running for months, and the first person to raise it may be an investigator rather than someone inside the business.

The most common causes of payroll error underpayment

The payroll errors that underpay people almost always trace back to a rule. Usually, someone configured a calculation once, it was correct for the situation in front of them back then, and then the situation changed.

The regular rate of pay is the biggest single source. Under the FLSA, overtime is owed on the regular rate, which includes nondiscretionary bonuses, shift differentials, and most other earnings, not base wage alone. A system computing overtime at 1.5 times base hourly pay underpays every employee who earned a differential that week. The shortfall is a few dollars a period, which is exactly the reason it survives.

Misclassification is the next one. An employee sits in an exempt salaried bucket, works fifty hours, and no overtime is owed on paper. If the duties test does not hold up, every one of those hours was unpaid.

Timing accounts for another cluster. Retroactive raises never applied back to their effective date. Rate changes entered after the cycle closes. Approved time landing after the cut-off and dropped.

Multi-location employers get one more. Someone working Monday to Wednesday at one location and Thursday to Friday at another can appear as two records of twenty-four hours. Neither crosses forty, so no overtime pays, even though that person worked forty-eight hours for one employer.

Rounding and pre-shift work finish the list. Rounding rules that always land in the employer's favor. Unpaid minutes spent booting systems before the clock starts. Meal deductions taken automatically on breaks that were interrupted.

How payroll underpayment becomes a legal problem

Under the FLSA, an underpaid employee is owed the money regardless of how the shortfall happened, and the Department of Labor allows recovery of back pay plus liquidated damages equal to the same amount, which doubles the bill. The federal statute of limitations is two years, stretching to three when the violation is willful. State law is frequently harsher. For example, New York Labor Law section 198 gives employees six years and liquidated damages of up to 100% of the wages owed, rising to 300% for willful violations.

So where is the line between a payroll discrepancy and wage theft? Wage theft is not one defined federal offense. It is a label covering the statutes that make withholding earned wages unlawful, and in a growing number of states, criminal. What moves an error across that line is knowledge and what you did with it. An employer who miscalculates overtime, finds it in an audit, and repays the affected population has made a mistake. An employer who was told, or who held the records that would have shown it, and kept running the cycle unchanged is somewhere else entirely.

Recordkeeping is where a lot of defenses collapse. The FLSA requires payroll records to be kept for three years and the underlying time cards, wage rate tables, and work schedules for two. In Anderson v. Mt. Clemens Pottery Co., the Supreme Court held that where an employer's records are inadequate, an employee's reasonable estimate of hours worked can carry the day. Thin records do not create doubt in your favor.

Why underpayment is harder to detect than overpayment

Overpayment comes with two alarms attached. The budget variance moves the wrong way, and finance asks why. Underpayment has neither one. It pushes labor cost down, and a line that lands under plan reads as good management rather than an open liability.

The employee is the other missing alarm. Someone overpaid by eleven dollars usually says nothing. Someone underpaid by eleven dollars often also says nothing, partly because reading a pay stub against a schedule is genuinely hard, mostly because raising eleven dollars means a conversation with a manager. Payroll teams know this, which is why the complaints that do arrive get handled as individual cases rather than as the visible edge of a population.

Scale finishes the job. Eleven dollars, twenty-six periods, four hundred people hit by the same rule, and the exposure is $114,400 before anyone has filed anything. That figure appears nowhere, because no report in a standard payroll system asks what an employee should have been paid. Those reports state what was paid. The damage does not stay inside payroll either, and what repeated payroll mistakes cost in retention shows up long before a claim does.

{{learn}}

How to find payroll underpayment before it finds you

Detection means recalculating pay independently and comparing, rather than reviewing what the system already produced. Start with the regular rate. Take one pay period, pull every employee who earned a bonus, a differential, or any non-base earning that week, and recompute their overtime from scratch. If your figure and the paid figure differ for even one person, the rule might be wrong for all of them.

A floor test comes next. Divide gross pay by hours worked for every employee in every period and flag anyone below the applicable minimum wage. That catches deductions that should never have been taken, and salaried people whose real hours dropped them under the floor.

The comparison most teams get wrong is approved hours against paid hours. That only proves the system did what it was told after a manager edited the record. Compare raw punches instead.

Exceptions tell you more than averages here. Anyone landing on exactly 40.00 hours week after week. Anyone whose rate change took effect one cycle late. Anyone whose hours split across two cost centers.

Then move the checks ahead of the run. Post-payroll audits find real money, but everything they find is already a correction with a legal clock running on it. Pre-payroll checks catch the same errors while they are still configuration. Celery is an AI-powered payroll protection platform built for that, running more than a hundred tests against a cycle before it commits, so errors get caught before money moves.

{{review}}

What to do when you discover payroll underpayment

First, fix the rule before you calculate anything. If the next cycle runs on the same configuration, your exposure grows while you are still building the spreadsheet.

Then size the whole population. The temptation is to correct the one person who raised it. Everyone touched by that rule has the same claim, and a remediation covering one employee while two hundred stay uncorrected is the fact pattern that turns an error into a willfulness argument.

Go back to the real start date of the error, not the two-year federal window. That window limits what a claim can reach. It does not limit what you owe, and picking the shorter of the two is a decision a plaintiff's lawyer will use.

Pay the back pay gross, with the correct tax treatment for the year the wages were earned, and write down what happened: the rule, the date it broke, the population, the method, the amounts. That file is your defense if this resurfaces.

Tell affected employees plainly what went wrong and what they are getting. Repeated payroll errors are one of the quickest ways to lose people who were otherwise staying, and silence after a correction does more damage than the shortfall did.

Talk to employment counsel about voluntary disclosure before choosing a route.