What Is Back Pay? An Employer Guide

Nobody sets out to owe back pay. That is the thing worth understanding before anything else.

The employer who ends up writing a five-figure check for unpaid overtime is almost never somebody who decided to cheat their staff. They are somebody who gave an employee a manager title without checking whether the role actually met the exemption test, and then, because that person was salaried, never tracked their hours for two years. And now the hours are gone, the records do not exist, and the amount owed is whatever the other side can reasonably estimate.

So this is written for the person who has not been sued yet: what back pay actually is, how it accumulates without anybody noticing, why the bill is usually roughly double what you first calculate, and the uncomfortable fact underneath all of it, which is that the absence of records does not protect you. It works against you. I build FirstHR, which is where those records live. This is general information rather than legal advice, and wage law is unusually unforgiving, so talk to somebody qualified before you act on any of it.

What Is Back Pay?

Back pay is compensation an employee earned but never received. It is the gap between what you actually paid somebody and what you were legally required to pay them, for a period that has already passed.

Two features of that definition drive everything that follows.

It is a debt, not a gesture. An employer who discovers an underpayment and pays it is not being generous. They are settling an obligation that already existed, and that has been accruing since the day the wages went unpaid.

Intent is largely irrelevant to whether you owe it. There is no honest-mistake exemption. The wages were earned or they were not. Intent matters for how much worse it gets, and for how far back the clock runs, but not for whether the underlying debt exists.

Back Pay vs Back Wages vs Retro Pay

Three terms, used interchangeably, meaning two different things. Worth getting straight, because the difference between two of them is the difference between paperwork and liability.

Back pay and back wages are the same thing. There is no substantive distinction. Back wages is simply the vocabulary the government uses. If you are reading a federal agency page it will say back wages, and if you are reading a payroll vendor it will say back pay, and they are describing the same money.

Retro pay is different, and the difference is one of origin. Retro pay arises from a timing lag: a change took effect on one date and reached payroll on a later one, and you owe the difference for the gap. That is an administrative catch-up. It is usually nobody's fault and it carries no particular legal weight, and the mechanics of it are covered in the guide to retro pay.

But here is the connection nobody draws. Retro pay you never actually pay becomes back pay. The raise approved in March that nobody entered into the system is retro pay in April. It is still retro pay in June. By the following March, when the employee finally does the arithmetic, it is a year of unpaid wages, and it is now something with a statute of limitations attached to it.

How Employers Actually End Up Owing It

Not through malice. Through a set of small, boring, entirely comprehensible administrative failures.

The first two entries on that list are worth dwelling on, because they are the ones that produce the enormous numbers.

Misclassification is the expensive one

Here is the mechanism, and it is almost elegant in how badly it compounds.

You give somebody a title with the word manager or coordinator or specialist in it. You pay them a salary. Because they are salaried, and because you believe they are exempt, you do not track their hours. Why would you? Exempt employees do not get overtime.

Except the exemption is not about the title or the salary. It is about the duties, and the salary threshold, and both tests have to be met. If the role does not actually qualify, that person was non-exempt the entire time, every hour over forty in a workweek was owed at one and a half times their regular rate, and you have no record of how many hours they worked. Which test applies and how it works is the subject of the exempt versus non-exempt guide, and it is worth the twenty minutes.

Contractor misclassification has the same shape and a worse tail: no overtime, no minimum wage floor, and now also unpaid employer payroll taxes on top of the wages. Where the line actually falls is covered in the guide to independent contractors.

The quiet ones

Off-the-clock work is the failure nobody sees, because by definition it is not on the clock. The five minutes of setup before the shift starts. The email answered at nine at night. The working lunch that was supposed to be unpaid. Individually trivial, and across two years, across a team, it is a number.

And the overtime rate itself trips people up. Overtime is one and a half times the regular rate, and the regular rate is not necessarily base pay. It includes non-discretionary bonuses and certain commissions. An employer computing overtime on base pay alone, for somebody who earns a production bonus, has underpaid every single overtime hour, correctly and consistently, for as long as they have been doing it.

The FLSA and the Clock

Federal wage law sets the floor, and it sets the window in which somebody can come after you.

The word willful is doing a lot of work there, and it is worth understanding what it does not mean. It does not require malice or a scheme. It generally turns on whether the employer knew or showed reckless disregard for whether the conduct violated the law.

Which produces an uncomfortable corollary: the moment you find out you have a problem, the clock on willfulness starts. An employer who discovers an underpayment and fixes it has an ordinary two-year exposure. An employer who discovers it, decides to see whether anyone notices, and gets found out eighteen months later has just handed the other side an argument for the third year. Delay does not make this cheaper.

The Wage and Hour Division has several routes to recover back wages, including supervised payment, litigation, and injunctions against continued withholding. The full architecture of the statute is in the FLSA guide, and the agency's own Handy Reference Guide to the FLSA is short and genuinely readable, which is not a sentence you often get to write about a federal publication.

Why the Number Is Usually Double What You Calculated

You work out the unpaid wages, and you brace yourself, and you have just calculated half of what this is going to cost.

The mechanism is liquidated damages. Under the FLSA, an employee who was not paid minimum wage or overtime may be awarded their unpaid wages plus an additional equal amount. Not as a punishment for bad behavior. As the default remedy.

An employer can sometimes avoid liquidated damages by demonstrating that the violation was in good faith and that they had reasonable grounds to believe they were complying. But read that carefully: it is a defense you have to prove, with evidence, in front of somebody. It is not an assumption you get to make from your desk. And the evidence that supports it is, once again, documentation you created before there was a problem.

Then add attorney fees, which the statute provides for on behalf of a prevailing employee, and which in a small wage case are routinely larger than the wages themselves. And interest. And, if the violation was willful, the possibility of civil money penalties on top.

The Records Problem, Which Is the Whole Problem

Now the part that reframes everything above, and the reason this article exists.

Read that box again in the context of misclassification, and the trap closes.

You classified somebody as exempt. Therefore you did not track their hours, because exempt employees do not need hours tracked. Therefore, when the classification turns out to be wrong, you have precisely zero evidence about how many hours they worked, and the person on the other side of the table does have a recollection, and it is going to be the higher number.

Which means the practical defense against a back pay claim is not legal at all. It is a timesheet. Kept routinely, when nothing was wrong, for somebody you were fairly confident you did not need to track. And that is a deeply unsatisfying thing to hear, because it means the work has to be done in advance, on a day when there is no problem, for a reason that will never become visible if it works.

The place all of this lives is the same place: accurate timesheets, an accurate record of what each person's rate and classification actually is, and a personnel file that still exists three years after somebody left. Which is a records discipline, not a payroll one.

Where State Law Makes It Worse

Federal law is the floor. Several states have built considerably more expensive structures on top of it, and the final paycheck is where they concentrate.

Other states have their own final-pay deadlines, their own penalties, their own longer statutes of limitations, and their own remedies stacked on top of the federal ones. The general pattern: the federal window is a floor, not a ceiling, and the state where each employee physically works is the one whose rules apply. If you have people in California, the full picture is in the California compliance guide.

How to Calculate Back Pay

The arithmetic is not hard. The inputs are.

An hourly example

Somebody at $22 an hour worked 46 hours in a week and was paid for 46 hours at $22, with no overtime premium. They should have received 40 hours at $22 plus 6 hours at $33. The shortfall is $66 for that week. Now multiply by however many weeks that happened, which is the question you cannot answer without records.

A salaried example

Somebody was promised a raise from $60,000 to $66,000 effective March 1. It reached payroll on July 1. That is four months of underpayment at $500 a month, so $2,000 in back pay. Clean, computable, and entirely avoidable by having the raise approval and its effective date recorded somewhere other than a manager's memory.

How to Process It in Payroll

Three options. One of them is a mistake.

The principle that unites the two good options and rules out the third: the correction has to be visible.

Beyond making the employee whole, the entire value of a back pay payment to you is evidentiary. It demonstrates that you found the problem, quantified it, and fixed it, on a date, in a document. That is the good-faith story, and it is the same story that might spare you liquidated damages later. A correction that is silently folded into ordinary wages tells nobody anything, and if you ever need to prove you paid it, you will find you cannot point at it. The line item is the point, and where it belongs on the document is covered in the pay stub guide.

How Back Pay Is Taxed

It is wages. It is taxed like wages. But there are two wrinkles worth knowing before you run it.

The supplemental wage rate is the one that generates the email. Per IRS Publication 15, the withholding rate on supplemental wages remains 22 percent for 2026, with a higher mandatory rate above $1 million. An employee receiving a back pay check will see a withholding that looks nothing like their usual rate and will conclude they were punished for being underpaid. They were not. Withholding is not the tax owed, and the same confusion attaches to bonuses, which is covered in the guide to supplemental pay.

The other wrinkle is prior-year back pay, which has its own reporting rules including special treatment for reporting to the Social Security Administration. If the back pay spans a closed tax year, this is the point at which you stop reading articles and call your accountant. IRS Publication 957 is the relevant reference.

You Just Found One. Now What?

The most useful section in this article, and the shortest. You have discovered you underpaid somebody. Order matters.

How Not to Owe It in the First Place

Every item on this list is boring, cheap, and something you do on a day when nothing is wrong. Which is precisely why they do not get done.

Notice that not one of those is about payroll software. They are about knowing things and writing them down: who is classified how, and why, and when their rate changed, and who approved it, and how many hours they actually worked. That is an HRIS question. The payroll run is downstream of it, and a payroll system fed bad records produces confident, precise, wrong payments.

Common Mistakes

These recur, and the pattern in them is worth seeing.

The unifying error is treating back pay as a payroll event when it is a records failure. The money is the symptom. The cause, every single time, is that somebody's classification, rate, or hours were not written down accurately at the moment they mattered, and by the time anybody looks, the only version of events that exists belongs to the other side. The rest of the recurring small-employer failures are collected in the HR rules and regulations guide, and an HR audit is the structured way to find out what is already in there while it is still cheap to fix.

Frequently Asked Questions