Can a salaried employee be non-exempt under the FLSA?

Yes. Salary basis alone does not confer exemption. The employee must also meet the DOL salary level threshold and satisfy the applicable duties test. A full-time salaried worker paid below the federal salary floor is non-exempt and overtime-eligible regardless of pay frequency or job title.

What is the difference between exempt and non-exempt employees?

The distinction is overtime eligibility. Non-exempt employees are entitled to FLSA overtime pay (1.5 times their regular rate for hours over 40 in a workweek). Exempt employees are not, provided they meet all three FLSA tests: salary basis, salary level, and duties. State law may create additional overtime obligations regardless of federal exemption status.

Do part-time employees qualify for overtime?

Part-time status does not determine overtime eligibility. FLSA overtime is triggered by hours worked in a workweek (over 40), not by employment classification. A part-time non-exempt employee who works 45 hours in a week is owed overtime for those 5 hours, the same as a full-time non-exempt employee.

What happens if an employer misclassifies an employee as exempt?

The employer faces exposure to back wages for unpaid overtime, potentially covering two to three years under the FLSA willfulness standard, plus liquidated damages equal to back wages and DOL civil penalties. Misclassification discovered in an audit typically triggers a look-back across all similarly classified employees, not just the individual who raised the complaint.

Can a payroll system automatically apply the FLSA duties test?

No. The duties test is qualitative and requires human judgment. A payroll system's role is to encode the result of that determination as a pay rule so overtime is calculated or suppressed correctly going forward. The human determination must happen first and be documented before the system can enforce it.

Why FLSA Classification Errors Are Payroll Architecture Failures

Why Does the FLSA Draw the Line but Your Payroll System Fail to Hold It?

The gap between a correct classification and a compliant paycheck is not legal. It is operational. HR completes the FLSA three-part exemption test (salary basis, salary level, duties) and files the determination. Then nothing connects that determination to the payroll engine's overtime rules. The classification record and the payroll rule live in separate systems with no enforced sync, and every pay period that passes without alignment adds to the organization's exposure.

The DOL's framework is well known. To qualify as exempt, an employee must be paid on a salary basis, meet the salary level threshold, and perform duties that satisfy one of the recognized exemption categories. Most HR practitioners can recite this. The problem is what happens after the test is applied. The determination goes into a personnel file or HRIS field. The payroll system, meanwhile, calculates overtime based on whatever pay type code was configured at hire. If those two records disagree, the paycheck is wrong.

EasyClocking by WorkEasy Software has seen this pattern repeatedly across payroll configurations for mid-market employers: the classification record says one thing, the payroll rule says another, and the discrepancy only surfaces during an audit or employee complaint. The fix is not better legal knowledge. It is better system architecture, where classification status is a live input to the payroll rule engine rather than a static field filed elsewhere. You can explore the components of the FLSA three-part exemption test in the frameworks for a detailed breakdown of each requirement.

Does Salaried Mean Exempt? Why This Confusion Is the Most Expensive Misclassification in Payroll

No. Salaried does not mean exempt. This is the single most widespread misclassification error, and it is also the most expensive because it suppresses overtime for workers who are legally entitled to it. Under the FLSA, a full-time salaried worker who does not meet both the salary level threshold and the applicable duties test is non-exempt and overtime-eligible, regardless of how the employer structures their pay frequency.

The DOL salary level test establishes a minimum weekly salary. Workers paid below that floor cannot be classified as exempt no matter what their job duties look like. Workers paid above the floor still must satisfy a duties test. Salary basis alone is a necessary condition, not a sufficient one. Yet in practice, many payroll systems treat "salaried" as a pay type that automatically suppresses overtime calculation, which creates a systemic mismatch between the legal determination and the payroll outcome.

EasyClocking by WorkEasy Software addresses this at the configuration layer. The platform distinguishes salary basis from exemption status, preventing the assumption that a salaried pay type automatically suppresses overtime calculation. This means a salaried non-exempt employee is configured to receive overtime when hours exceed the applicable threshold, without manual intervention each pay period. For definitions of salary basis and salary level as they apply to exemption status, see the exempt vs non-exempt overtime rules resource.

Where Do Duties Tests Get Contested, and Why Do Payroll Systems Go Silent?

The FLSA duties tests are where classification decisions become qualitative, contested, and difficult to automate. The five primary exemption categories (executive, administrative, professional, outside sales, computer employee) each carry a duties test that hinges on judgment, not math. The administrative exemption's "primary duty" standard is the most litigated because it requires evaluating whether the employee exercises independent judgment on matters of significance, a determination that reasonable people regularly disagree about.

No payroll system can auto-apply a duties test. The test requires a documented human determination: someone reviews the actual work performed, evaluates it against the DOL's criteria, and records that evaluation. The payroll system's role begins after that determination is made. It must encode the result as a pay rule so that overtime is either calculated or suppressed for that employee going forward. If the determination is not encoded, or is encoded incorrectly, the payroll system will pay the employee according to whatever default rule exists, not according to the FLSA.

What EasyClocking by WorkEasy Software has observed in implementations is that employers who document duties-test determinations in a structured classification record, not just a job title, are dramatically better positioned for audit defense than those who rely on title alone. Documentation is necessary, but it is not sufficient. The classification record has to connect to a pay rule that fires automatically. For a walkthrough of classification documentation procedures, see the compliance audit failure incomplete time records guide.

What Are the Three Patterns That Turn a Correct Classification Into a Payroll Failure?

Three recurring patterns convert correct FLSA classifications into incorrect paychecks. Each one represents a gap between the classification record and the payroll rule engine.

The Stale Rule. An employee is promoted or changes roles. HR updates the classification determination. The payroll system's overtime rule is not updated. For the entire period between the role change and the payroll correction, overtime is either incorrectly suppressed or incorrectly paid. This gap can persist for months or years before discovery.
The Part-Time Assumption. Part-time employees are assumed non-exempt and overtime-eligible, which is often correct. But their payroll records are never configured with weekly hour thresholds. When a part-time non-exempt employee works more than 40 hours in a week, the system should trigger overtime. If no threshold is configured, overtime may not calculate, and the employer accumulates back-wage exposure without knowing it.
The Multi-State Blind Spot. Federal FLSA exemption is correctly applied, but state-level overtime rules are not layered on top. States like California, Alaska, and Nevada enforce daily overtime thresholds that apply regardless of federal exempt status at the state level. An employer operating in multiple states who applies only the federal rule will be non-compliant in every state with additional requirements.

EasyClocking by WorkEasy Software's classification-to-payroll-rule workflow was designed to close these three gaps: every classification change triggers a rule-review prompt, part-time hour thresholds are configurable at the employee level, and state overtime overlays are applied automatically based on work location. For more on how multi-state overtime rules layer on FLSA, see the multi-state overtime compliance systems gap analysis.

Why Is Classification a Payroll Data Maintenance Problem, Not a One-Time Decision?

Classification status changes with role changes, promotions, salary adjustments, and regulatory updates. Even a correctly classified employee can become misclassified through regulatory change without any action by the employer. The DOL has revised the salary threshold multiple times, and each revision converts some previously exempt employees into non-exempt employees overnight. Employers who treat classification as a static field rather than a monitored data point will accumulate misclassification debt silently until an audit or employee complaint surfaces it.

The employers with the cleanest audit outcomes are not those who classified most carefully at hire. They are the ones who built a review trigger into every compensation event and every regulatory update cycle. Three triggers should prompt a classification review: any compensation event (promotion, salary change), any role or duties change, and any DOL regulatory update to the salary threshold. Annual blanket reviews alone are insufficient because misclassification debt accumulates between events, not on a calendar.

EasyClocking by WorkEasy Software treats exemption status as a live payroll rule input, not a static employee field, so every overtime calculation reflects the current, documented classification without manual intervention. For information on DOL salary threshold regulatory updates and how they affect classification, see the wage and hour compliance multi-state employers resource. For individual classification questions, visit the faqs hub.

How EasyClocking by WorkEasy Software Addresses This

EasyClocking by WorkEasy Software closes the gap between classification determination and payroll rule execution. The platform distinguishes salary basis from exemption status at the configuration layer, so salaried non-exempt employees receive correct overtime calculation without manual overrides each pay period. Classification changes trigger rule-review prompts, and state overtime overlays are applied automatically based on work location. Approved hours, overtime calculations, and pay codes flow into payroll through 20+ direct or file-based integrations, replacing the manual reconciliation that turns classification errors into recurring payroll cleanup. The system treats exemption status as a live input to the pay rule engine rather than a static field, so every paycheck reflects the current documented classification.

Why FLSA Classification Errors Are Payroll Architecture Failures

What You Need to Know

Sources

Related on EasyClocking

Is your time tracking system fair to your team?

Frequently Asked Questions

Clocked

Not Ready for a Quote? Start Here.