Salaried Non-Exempt Employees and Overtime Obligations

Salary is a pay structure. Exemption from overtime is a legal classification. An employer can decide to pay someone a fixed weekly amount for reasons that have nothing to do with the law: predictability, simplicity, a sense that hourly pay feels junior. None of that decides the employee's entitlement to overtime. Classification is determined by FLSA rules, not by how an employer chooses to pay.

A salaried non-exempt employee is what the phrase says: someone paid a fixed weekly sum who still keeps full overtime rights, because the job itself doesn't meet the legal bar for exemption. This appears constantly in entry-level management, where team leads spend most of the week doing the same tasks as the hourly staff around them, inside sales reps, junior administrative employees. These are roles that got moved to salary for convenience, not because anyone ran the exemption test and confirmed the role qualified.

Getting paid on a "salary basis," meaning the amount is fixed in advance and doesn't shrink because of a slow week or a slightly-off performance stretch, is a real legal requirement. It's just not the only one, and satisfying it alone does nothing to confer exemption. It's one leg of a three-legged test, and a stool missing two legs doesn't stand.

What the FLSA requires: the salary and duties tests in 2026

To exempt an employee from overtime under the executive, administrative, or professional (EAP) categories, an employer has to clear three separate tests at once: salary basis, salary level, and duties. All three. Not two out of three, not "mostly." Failing even one means the employee is non-exempt, full stop, regardless of title, regardless of how the offer letter reads, regardless of what the employee themselves believes about their own job.

The salary level test asks a blunt question: is the person paid enough to even be considered for exemption. The federal floor is $684 per week, the same figure that's applied since 2019. That number has a complicated recent history, because it explains why so many employers are confused about where the line actually sits. The $684/week figure, the prior 2019 standard formally restored by the DOL in May 2026, is what's operative right now. The DOL has said it intends to revisit the rule through the normal regulatory process, so $684 is stable for the moment, though it may change. The same reversal applies to the highly compensated employee threshold: the blocked rule would have raised that annual figure considerably, and until further legal or regulatory action, the prior standard governs.

The duties test is where the real complexity lives, and it's the prong employers most consistently get wrong. Clearing the salary threshold tells you nothing about whether the job itself qualifies. A salaried manager earning well above $684 a week who spends most of the shift doing the same physical, manual work as the hourly team around them doesn't automatically become exempt just because the paycheck cleared the bar. The exemption requires that executive, administrative, or professional duties make up the employee's primary work, not an occasional task layered on top of a job that's functionally identical to a non-exempt one. A title on an org chart proves nothing here. What the person actually does, hour by hour, is the entire test.

How state law raises the bar beyond federal minimums in 2026

Federal law sets a floor, and where a state requires more than the FLSA does, the state standard controls. Employers have to meet whichever bar is higher, full stop. For a company hiring across state lines, that means the federal $684 figure is often close to irrelevant.

Five states raised their overtime exemption salary thresholds effective January 1, 2026, and every one of them sits well above the federal floor:

California: $1,352 per week for the standard EAP exemption, tied to the state's $16.90 minimum wage; fast-food chain restaurants fall under a separate industry rule requiring $1,600 per week. Colorado: $1,111.23 per week for executive, administrative, and professional exemptions; highly technical computer employees can instead be paid hourly, at a minimum of $34.85 an hour. Maine: $871.16 per week. New York: $1,237.50 per week. Washington: $1,541.70 per week.

These aren't just different numbers plugged into the same formula. Some states layer on overtime triggers that don't exist federally at all, daily overtime, or double-time rules. The calculation itself changes shape from state to state, not just the dollar figure that unlocks it. California and New York go a step further and simply don't recognize the FLSA's highly compensated employee exemption at all, so an employee who's valid as HCE-exempt under federal law may be fully non-exempt under state law.

A company operating in even three or four of these states is no longer running one compliance calculation. It's running several, in parallel, permanently, and that's before a single hour of overtime gets calculated. Alaska's minimum salary requirement for overtime exemption is set to rise to $1,120 per week on July 1, 2026, though this exact figure remains unconfirmed as of publication.

How to calculate overtime pay for a salaried non-exempt employee

Once an employee is confirmed non-exempt and paid on salary, the first job is converting that salary into an hourly rate, dividing total compensation earned by total hours actually worked in the workweek. From there, federal law is direct: one and a half times the regular rate of pay for every hour worked past 40 in that workweek.

The catch sits in the phrase "regular rate," and it trips up more payroll teams than any other part of this calculation. The regular rate must include all remuneration for employment except specific statutory exclusions, rather than simply being the base salary divided by 40.

That plays out with real numbers. Skipping that recalculation and running overtime off the base salary alone shorts the employee on every single overtime hour that week, silently, in a way that's fully auditable months or years later.

Some employers instead use a fluctuating workweek method: a fixed salary meant to cover all hours worked in a week, whatever that number turns out to be, with a half-time premium (rather than full time-and-a-half) added on top for overtime hours. It's legal under specific conditions, but it's restricted or barred outright in some states, and it only works with a genuinely clear, mutual understanding with the employee about how pay is structured. It's an option that exists. It is not a default anyone should reach for without checking state law first.

The One Big Beautiful Act, passed in July 2025, lets employees deduct the overtime premium portion, the "half" above the regular rate, from federal income taxes for tax years 2025 through 2028. Standard payroll taxes, Social Security, Medicare, and state income taxes still apply in full; the deduction is federal income tax only. Employers don't get to skip recordkeeping either way. The FLSA requires hours-worked and wages-paid records for non-exempt employees going back at least three years, and that includes time worked before a shift officially starts or after it officially ends.

Where misclassification happens at fast-scaling companies

The most common misclassification pattern doesn't look like fraud. It looks like a promotion. An hourly employee gets moved to a salaried "manager" title, often as a reward, often in good faith, without anyone actually auditing whether the day-to-day duties changed enough to satisfy the duties test. If that person still spends the bulk of the week doing the same tasks as the hourly staff they now technically supervise, the exemption doesn't apply, no matter how the org chart reads.

Job title carries zero legal weight here. A "Director of Operations" who spends most working hours on manual fulfillment tasks alongside the warehouse team is non-exempt, whatever the offer letter says, whatever the business card says. Regulators look at what the job actually is.

The pattern that scaling companies hit hardest is geographic. A company hiring its 10th employee across states may correctly classify that employee as exempt under federal rules while unknowingly violating California's or Washington's higher salary threshold, since the exemption evaporates at the state level. The federal exemption doesn't travel. It evaporates at the state line, and nobody necessarily notices until an audit or a departing employee's attorney notices first.

A related, quieter error is adding a non-discretionary bonus or sales commission to a salaried non-exempt employee's pay but calculating overtime on base salary alone, leaving the bonus out of the regular-rate math. It's underpayment, and because payroll runs on a cycle, it compounds every single pay period it goes uncorrected. And the exposure window is long. The FLSA's statute of limitations runs two years for unintentional violations and three years for willful ones, so an undetected misclassification can accumulate liability across that entire span, with back pay and liquidated damages, which double the award, standing as the normal remedy once it's found.

How compliance exposure compounds as headcount grows across states

Deel's 2024 State of Global Hiring report found that the average Series A startup already operates across roughly six states and two countries. That number tends to catch founders off guard. Multi-jurisdictional complexity isn't a later-stage problem that arrives once a company is mature and well-resourced. It appears early, often before there's a dedicated compliance function in place to handle it.

Each new hire in a new state adds its own salary threshold, its own duties interpretation, sometimes its own daily-overtime or double-time trigger layered on top of the federal 40-hour baseline. The compliance surface area doesn't grow one-to-one with headcount. It grows multiplicatively, because every new state interacts with every existing pay component, every bonus structure, every job classification already on the books.

The recordkeeping obligation scales the exact same way. Three years of hours-and-wages data, required for every single non-exempt employee. Across a workforce of even fifty salaried non-exempt employees spread across multiple states, that's a genuinely large, audit-ready data requirement, and it has to stay accurate continuously, not just at the moment someone checks.

Manual tracking is where this tends to break. HR professionals in fragmented systems can spend as much as 60% of their working time on handoffs, chasing down updates, and reconciling data between disconnected tools, time that's directly unavailable for the proactive classification audits or jurisdiction monitoring that would catch these problems early. And the failure has a sting built into it: when an employer can't produce clean timekeeping records during an audit, regulators can treat that absence itself as evidence the violation was willful, converting a two-year exposure window into a three-year one and triggering liquidated damages on top.

Why manual payroll processes are structurally mismatched to salaried non-exempt complexity

Salaried non-exempt payroll is not a simple biweekly arithmetic exercise. It requires variable-hours tracking, bonus inclusions in the regular rate, multi-state threshold checks, and in some jurisdictions, daily overtime rules, and each payroll run requires a series of conditional checks that are not tasks benefiting from a human doing them manually every two weeks. Every payroll run is really a sequence of conditional checks stacked on top of each other. That's not a task that benefits from a person doing it by hand every two weeks, no matter how careful or experienced that person is.

Most companies run this through a fragmented stack, with one system for HR records, a separate tool for timekeeping, a distinct payroll engine, and often a fourth platform for benefits. Data has to pass cleanly across all four every single cycle, and each handoff between systems is a place where a regular-rate inclusion can quietly get dropped or the wrong state threshold can get applied without anyone noticing.

HR teams end up functioning as the connective tissue holding that fragmented stack together, rather than functioning as the people enforcing classification policy from the start. That's the same 60% figure again, HR capacity absorbed into manual reconciliation and update-chasing instead of the strategic classification work that actually prevents violations. PwC's 2025 benchmarking work found that automated error detection substantially reduced correction rates year over year, which is a useful signal in itself: it suggests a meaningful share of the corrections happening in manual payroll environments were preventable all along, not inevitable.

And the errors in this specific context don't stay contained. An under-calculated regular rate in week one isn't a single mistake that gets fixed and forgotten. It repeats every pay period until someone catches it, and each repetition is its own separate FLSA violation, stacking liability quietly in the background.

What automated payroll infrastructure does for salaried non-exempt compliance specifically

Well-built payroll automation attacks the exact failure points described above, not payroll complexity in the abstract. A properly integrated system pulls bonus and commission data into the same run as base salary and recalculates the regular rate automatically before the overtime multiplier gets applied, which removes the single most common source of overtime underpayment described earlier.

Jurisdiction handling works the same way. A system tracking a large number of tax and wage jurisdictions can apply California's threshold to California-based employees and Washington's to Washington-based employees within the same payroll run, with no manual lookup and no per-hire configuration step. Timekeeping integration closes the other major gap: when HRIS and timekeeping live in the same system, the handoff where hours data is most likely to get lost or attached to the wrong employee type disappears, and the records the FLSA requires simply exist as a byproduct of running payroll normally, rather than as a separate compliance chore bolted on afterward.

Agentic systems are pushing this further in 2026. Payroll agents built to flag anomalies and surface variance before a pay cycle closes, routing exceptions for review instead of waiting for a human to stumble across them manually, are already in production at scale. Organizations running AI-powered payroll automation report 30 to 50 percent fewer paycheck corrections and pay cycles completing roughly 40 percent faster. ADP announced an AI agent for its Global Payroll product in April 2026 that identifies payroll variances automatically and can move toward remediation before a variance turns into an actual payroll error, following its January 2026 rollout of AI agents across HR and payroll workflows more broadly, with a policy and compliance agent alone reportedly saving a substantial number of minutes across more than 600 organizations in a single measured month in 2025. Such a solution would take the form of an AI-native platform purpose-built for scaling companies, combining payroll, compliance monitoring, and timekeeping in a single system with AI agents.

That's the structural shift automation offers here: not a faster version of the manual process, but a system where the compliance check is built into the payroll run itself, rather than layered on top of it after the fact. Vendor activity from 2025–2026 serves as confirmed evidence of the direction this shift is taking.