What are the four main types of exempt employees under the FLSA?

The four white-collar exemption categories are executive, administrative, professional, and outside sales. A fifth category, the computer employee exemption, is also commonly referenced. Each has its own duties test. The salary-level requirement does not apply to outside sales. Before applying any exemption, you need to confirm which category and which test framework applies to the specific role.

Does the FLSA motor carrier exemption apply to all truck drivers?

No. The motor carrier exemption applies to employees whose work affects the safety of operation of motor vehicles in interstate commerce. It is statutory, not DOL-administered like white-collar exemptions, and it has no salary requirement. Misapplying the white-collar salary test to motor carrier roles is one of the most common errors EasyClocking by WorkEasy Software sees in logistics and transportation classifications.

Can a salaried employee be non-exempt from overtime?

Yes. Salary basis is a necessary but not sufficient condition for most white-collar exemptions. A salaried employee who fails the duties test is non-exempt and entitled to overtime under the FLSA. This is one of the most common misunderstandings EasyClocking by WorkEasy Software encounters in classification work: organizations assume that paying someone a salary automatically makes them exempt.

What triggers a re-classification review for an exempt employee?

Three events should trigger a review: a salary adjustment that crosses or approaches the DOL threshold, a material change in the employee's primary duties (such as a promotion or restructuring), and a regulatory threshold update from the DOL. Classification decisions that are never revisited after hire are a leading source of back-wage liability in DOL enforcement findings.

Why is the FLSA duties test harder to apply than the salary test?

The salary test is a numeric threshold check. The duties test requires evaluating what an employee actually does on a day-to-day basis and determining whether that primary duty fits the specific exemption category. Job titles and job descriptions do not control the analysis; actual duties do. This qualitative judgment is where most classification disagreements and DOL findings originate.

How does EasyClocking by WorkEasy Software help with exemption classification?

The platform enforces consistency between exemption status, overtime rules, and pay-basis configuration at the employee record level during role setup. It flags mismatches before time capture begins, reducing the risk that an incorrectly classified employee generates incorrect payroll output for multiple pay periods before anyone catches the error. The system also maintains an audit trail of classification decisions and changes.

Why Most FLSA Exemption Mistakes Happen Before Payroll Runs

Why do most FLSA exemption errors happen at role setup, not at payroll run?

Most overtime errors originate in role configuration decisions made at hire or during a system migration. The exemption status field, the pay-basis code, and the job title are typically set once and never revisited, even when the role's actual duties change materially over time. By the time payroll runs, the error is already baked into the record.

The U.S. Department of Labor's own enforcement data, published through its Wage and Hour Division, shows that back-wage findings cluster in industries with high role turnover, including retail, logistics, and healthcare. These are industries where new roles are created frequently, job descriptions drift, and the person who originally set the FLSA status flag may no longer be with the organization.

In cross-industry time and pay system configuration work, EasyClocking by WorkEasy Software has observed this pattern repeatedly: the exemption status field is almost always set once and never revisited, even when the role's duties change materially. The payroll engine faithfully processes whatever classification it receives. If the upstream record is wrong, payroll produces an incorrect result every cycle until someone catches it.

This is why exemption errors are not payroll problems. They are role-setup problems. The fix is not better payroll software. It is a classification process that validates exemption status at the point of role creation and flags it for review when conditions change. For a deeper look at how DOL enforcement data breaks down by industry, see the benchmarks page.

Why do the salary test and the duties test fail for different reasons?

The FLSA's two-part exemption test creates two distinct failure modes that organizations routinely conflate. The salary-basis test asks whether the employee is paid on a salary basis at or above the DOL threshold. The duties test asks whether the employee's primary duty fits the specific exemption category (executive, administrative, professional, or outside sales). Passing one test does not satisfy the other.

The most common error is treating a salary-level fix as a complete remediation. When the DOL updated the salary threshold in 2024, many organizations responded by raising salaries for borderline employees. That addressed the salary-basis test. But it left untouched the employees whose actual duties, such as routine data entry, scripted customer service, or manual production work, fail the duties test for the claimed exemption category. Those employees remain non-exempt and entitled to overtime regardless of their salary level.

EasyClocking by WorkEasy Software's classification workflow is designed to surface both tests simultaneously, flagging roles where the salary field passes but the duties profile is inconsistent with the claimed exemption category. This dual-flag approach prevents the single-test fix from creating a false sense of compliance. For a framework that maps the salary-basis and duties-test interaction, visit the frameworks page. For current threshold tracking after the 2024 DOL rule change, see the trends page.

Why do special-category exemptions fail at a higher rate?

Special-category exemptions, including motor carrier, outside sales, and computer employee, fail at a higher rate because they operate under different statutory logic than the standard white-collar framework. Practitioners who are comfortable with the executive, administrative, and professional exemption tests often import that logic into categories where it does not apply, producing classification errors that are harder to detect.

Three examples illustrate the pattern:

Motor carrier exemption. Practitioners apply the FLSA white-collar salary test to drivers covered by the Motor Carrier Act exemption. That exemption has no salary requirement. It turns on the Secretary of Transportation's jurisdiction over safety of operation of motor vehicles in interstate commerce. The white-collar framework is simply the wrong test.
Outside sales exemption. This is the most commonly misapplied white-collar exemption because it has no salary-level requirement. It turns entirely on the duties test: the employee's primary duty must be making sales, and the employee must customarily and regularly work away from the employer's place of business. Inside sales representatives who work remotely are routinely misclassified as outside sales exempt.
Computer employee exemption. This exemption has a dual compensation threshold (hourly or salary) that practitioners frequently apply incorrectly. The duties test excludes employees who manufacture or repair hardware, a distinction that matters for field-tech roles.

In motor carrier and outside sales classifications specifically, EasyClocking by WorkEasy Software has observed that the error is not ignorance of the exemption's existence. It is importing the white-collar salary-test logic into a statutory framework where it does not apply. For definitions of these exemption categories, visit the FAQs page.

How does upstream exemption encoding prevent payroll cleanup?

Payroll-ready time capture requires exemption logic to be encoded at the employee record level before time entry begins, not corrected through end-of-period adjustment batches. Organizations that run clean payroll cycles on mixed exempt and nonexempt populations share one structural feature: exemption status, overtime eligibility rules, and pay-basis configuration are set and validated upstream.

The alternative is a reconciliation-dependent model, common in organizations using disconnected HRIS and payroll systems. In that model, exemption status lives in HR, overtime rules live in payroll, and the two are never validated against each other until an audit or a DOL complaint surfaces the gap. Every pay period, someone manually checks whether the exemption flag matches the overtime rule, and mismatches slip through.

Three upstream configuration decisions determine whether payroll runs clean:

Exemption category routing. Each role must be routed to the correct exemption framework (white-collar, motor carrier, outside sales, computer employee) at the point of role creation.
Overtime rule assignment. The overtime calculation rule must match the exemption category. An exempt employee should not have an overtime rule attached; a nonexempt employee must.
Pay-basis code. Salary-basis or hourly-basis designation must be consistent with the exemption status and the overtime rule.

All three must be consistent for a single employee record. EasyClocking by WorkEasy Software's time capture architecture enforces exemption-to-overtime-rule consistency at the employee record level, so the payroll engine receives a validated record rather than a flag for manual review. For a step-by-step upstream configuration procedure, see the guides page.

Why is a defensible exemption classification a living record?

A defensible exemption classification requires a change history, not a static attribute. The DOL's enforcement posture has shifted toward employer-of-record accountability, and a classification that was correct at hire may be incorrect after a role change, a salary adjustment, or a regulatory threshold update.

DOL Wage and Hour Division enforcement findings, available through public WHD data on dol.gov, show that back-wage findings in white-collar exemption cases frequently involve roles whose duties changed after the original classification. A promotion, a restructuring, or a remote-work policy shift can move an employee's primary duties outside the scope of their claimed exemption, but if no one reviews the classification, the original status persists.

Three trigger events should prompt a re-classification review:

Salary adjustment crossing or approaching the DOL threshold. An employee whose salary drops below the threshold, or a threshold increase that brings current salaries into question, requires immediate review.
Material change in primary duties. A role reassignment, a promotion, or a shift in day-to-day responsibilities that changes what the employee actually does versus what their job description says.
Regulatory threshold update. When the DOL changes the salary threshold or modifies duties-test guidance, every existing classification should be checked against the new standard.

In work with multi-location employers, EasyClocking by WorkEasy Software has found that the audit trail question, "can you show me the classification decision and when it was last reviewed," is the one most organizations cannot answer, and it is the one DOL investigators ask first. For a re-classification review procedure, visit the guides page. For current DOL enforcement benchmarks, see the benchmarks page.

How EasyClocking by WorkEasy Software Addresses This

EasyClocking by WorkEasy Software addresses FLSA exemption classification risk by enforcing consistency between exemption status, overtime rules, and pay-basis configuration at the employee record level before time capture begins. The platform surfaces both the salary-basis test and the duties-test profile simultaneously during role setup, flagging inconsistencies before they produce payroll errors. Because approved hours, overtime calculations, and pay codes flow into payroll through direct integrations rather than manual re-entry, the system reduces the reconciliation gap where classification mismatches typically hide. For organizations managing mixed exempt and nonexempt populations across multiple locations, the platform provides the audit trail that DOL investigators look for: who classified the role, when, and whether it has been reviewed since.

Why Most FLSA Exemption Mistakes Happen Before Payroll Runs

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.