"Salaried" is not the same as "exempt"

The single most common wage-and-hour mistake small employers make is assuming that paying someone a salary means they don't get overtime. It doesn't. Under the federal Fair Labor Standards Act (FLSA), whether an employee is owed overtime — time-and-a-half for hours over 40 in a workweek — depends on whether they are exempt or non-exempt, and that status is determined by what the job actually involves and how much it pays, not by whether you cut a salary check or an hourly one.

Get it wrong and the bill arrives years later, all at once: back overtime for every misclassified employee, liquidated damages that can double it, and penalties on top. Misclassification claims are among the most-litigated employment issues precisely because the mistake is so easy and so widespread. This is a practical compliance guide, not legal advice — the exemption tests are genuinely fact-specific and some states (notably California and New York) set tougher rules than the federal floor, so confirm close calls with counsel.

The two tests every exemption has to pass

To classify someone as exempt from overtime, you generally have to satisfy both of two tests. Failing either one makes the employee non-exempt and entitled to overtime, full stop.

  • The salary-basis and salary-level test. The employee must be paid a fixed, predetermined salary that isn't reduced based on the quality or quantity of work, and that salary has to meet a minimum dollar threshold set by the Department of Labor. Pay below the threshold and the employee is non-exempt no matter what their duties are. (The threshold gets revised periodically, so always confirm the current figure before you classify.)
  • The duties test. Meeting the salary floor isn't enough — the employee's actual day-to-day duties must fall into one of the recognized exemption categories. The job title is irrelevant; what matters is what the person really does most of the time.

Both tests, every time. A high salary doesn't buy you out of the duties test, and impressive duties don't excuse paying below the salary floor.

The duties tests, in plain language

The common "white-collar" exemptions each have their own duties requirements. The broad strokes:

  • Executive: the employee's primary duty is managing the business or a department, they regularly direct the work of at least two full-time employees, and they have real authority over hiring and firing (or meaningful input into it).
  • Administrative: the primary duty is office or non-manual work directly related to management or general business operations, and the role involves the exercise of independent judgment on significant matters. This is the most over-claimed and most-litigated exemption — clerical and routine work that follows set procedures usually does not qualify, no matter the title.
  • Professional: work requiring advanced knowledge in a field of science or learning, typically acquired through prolonged specialized education (think lawyers, engineers, accountants), or recognized creative/artistic work.

There are additional carve-outs — for certain computer professionals and for highly compensated employees — but the principle holds throughout: exemption is earned by genuine, consistent duties, not by a label. The classic trap is the "assistant manager" who spends 90% of their time doing the same line work as the hourly staff they nominally supervise. That person is almost certainly non-exempt, and calling them salaried doesn't change it.

Where small employers actually get burned

The expensive mistakes cluster in a few predictable places:

  • Auto-classifying everyone salaried as exempt. Plenty of salaried roles — coordinators, junior analysts, support staff — are squarely non-exempt and owe overtime.
  • Forgetting that non-exempt salaried still earns overtime. You can pay a non-exempt employee a salary, but you still have to track their hours and pay time-and-a-half past 40. A salary doesn't waive the overtime obligation.
  • Not tracking hours for non-exempt staff at all. If a misclassified employee later claims unpaid overtime and you have no time records, the law often resolves the gap in the employee's favor. Accurate hours are your evidence — which is exactly why time tracking matters even for people you think are exempt until you've confirmed it.
  • Treating comp time as a substitute for overtime pay. For most private employers, offering future time off instead of paying overtime is not lawful. Pay the overtime.

How to classify defensibly

You can't eliminate the risk, but you can make every decision auditable:

  • Classify by role, in writing, before the first paycheck. For each position, document which exemption (if any) you're claiming and why the duties qualify — the same discipline you'd apply to worker classification between employee and contractor, which is a separate question you also have to get right.
  • Track hours for everyone non-exempt, no exceptions. Make timekeeping a standard, dated part of the workflow rather than something people reconstruct from memory.
  • Re-examine the close calls. "Assistant manager," "coordinator," "lead," and newly-promoted roles are where duties drift away from the exemption you originally claimed. Revisit them when the job changes.
  • When in doubt, classify as non-exempt and pay overtime. It's almost always cheaper than defending an exemption that doesn't hold.

Bottom line

Overtime eligibility under the FLSA turns on two things — whether the salary clears the federal floor and whether the actual duties fit a recognized exemption — and never on whether you call the pay a "salary." Document your classifications by role, track hours for everyone who's non-exempt (including non-exempt salaried staff), and revisit the borderline jobs as they evolve. The cost of classifying correctly today is a few hours of honest analysis; the cost of getting it wrong is years of back pay assessed all at once. When accurate time records and clear role definitions live in one place, you can answer a wage-and-hour auditor without a fire drill.