How to Classify Exempt vs. Non-Exempt Employees for Overtime-Compliant Payroll | EasyClocking by WorkEasy Software

How to Apply the FLSA Salary Basis Test

intermediate · 1 hour

This procedure determines whether an employee's compensation structure meets the federal minimum salary threshold required for exemption consideration. Executed by HR or payroll compliance staff during onboarding or reclassification, it produces a documented salary basis determination. Use this procedure before running the duties test for any salaried employee.

1. Retrieve the Compensation Record
Prerequisites
- Current offer letter or compensation record showing weekly salary amount
- HRIS or payroll system access to confirm how compensation is structured
- Employee's pay frequency and any fee-based or piece-rate compensation details
Pull the employee's current weekly salary figure from the HRIS or offer letter. If the employee is paid biweekly or semi-monthly, convert the figure to a weekly equivalent by dividing accordingly. For employees paid on a fee basis (per project or per engagement rather than per period), collect the fee amount and the expected hours for a single engagement.
Confirm that the compensation record reflects the employee's guaranteed minimum salary, not variable bonuses or commissions. Only the guaranteed portion counts toward the salary basis threshold. If compensation includes nondiscretionary bonuses or incentive payments, note them separately; the DOL permits a portion of these to satisfy the threshold, but the guaranteed base must be isolated first.
Record the source document (offer letter, HRIS export, or payroll register) and the date of retrieval in the employee's classification file. This timestamp matters because salary thresholds can change, and your determination must be defensible as of the date it was made.
Expected outcome: A documented weekly salary figure on file, sourced from the HRIS or offer letter, with the retrieval date recorded.
2. Compare to the DOL Salary Threshold
Prerequisites
- DOL current salary threshold verified against the Federal Register
- Applicable state salary thresholds for the employee's primary work state
Confirm the weekly salary equals or exceeds the current federal minimum. As of the 2024 rule, the DOL threshold is $684 per week. Always verify this figure against the current Federal Register before completing any classification determination; the DOL updates thresholds periodically.
Check applicable state thresholds as well. Several states, including California, New York, and Washington, set higher salary minimums for exempt status. Apply whichever threshold is greater: federal or state. If the employee works across multiple states, apply the threshold for the state where the employee primarily performs work, or consult legal counsel for multi-state split scenarios.
Record the comparison in a simple pass/fail format: the employee's weekly salary, the applicable threshold (federal or state, whichever is higher), and the result. This record becomes part of the classification file and is the first document a DOL auditor will request.
Expected outcome: A documented pass or fail result comparing the employee's weekly salary to the applicable federal and state thresholds.
3. Verify Payment Consistency
Prerequisites
- Payroll register for the prior six months for the employee
- Company safe harbor policy for improper deduction complaints
Confirm the employee receives the full predetermined salary in any week work is performed, with no improper deductions for partial-day absences. Under the FLSA salary basis requirement, an employer cannot dock an exempt employee's pay because they left two hours early on a Tuesday or arrived late on a Friday. Deductions for partial-day absences destroy the salary basis and can reclassify the employee as non-exempt retroactively.
Review the payroll register for the prior six months to identify any partial-day deductions. If improper deductions have occurred, document them and flag the employee for immediate remediation under your safe harbor policy. The DOL's safe harbor provision allows employers to reimburse improper deductions and preserve the exemption if the employer has a written policy prohibiting such deductions and a complaint mechanism in place.
If you discover a pattern of improper deductions rather than an isolated incident, consult legal counsel before proceeding. A pattern may indicate the employee was effectively treated as non-exempt, which creates back-overtime liability.
Expected outcome: Confirmation that the employee's salary has been paid consistently without improper partial-day deductions, or a documented flag for remediation.
4. Identify Fee-Based Compensation Exceptions
Prerequisites
- Fee amount and expected hours for a single engagement if applicable
If the employee is compensated on a fee basis rather than a salary, determine whether the fee meets the salary threshold. Calculate the fee-basis equivalent by dividing the total fee for a single job by the number of hours the job is expected to take, then multiplying by 40. If the result equals or exceeds $684 per week (or the applicable state threshold), the fee satisfies the salary basis test.
Fee-based compensation is uncommon in most hands-on industries but appears in certain professional, consulting, or project-based roles. If the employee is paid hourly, this step does not apply; hourly employees are automatically non-exempt regardless of their hourly rate. Document the calculation and result in the classification file.
Expected outcome: A documented fee-basis calculation showing whether the fee equivalent meets the salary threshold, or confirmation that this step does not apply to the employee.
5. Document the Salary Basis Determination
Prerequisites
- Completed steps 1 through 4 for the employee
Record the complete salary basis determination in the employee's classification file. The file should include: the employee's name and ID, the weekly salary figure, the applicable threshold (federal or state), the pass/fail result, the payment consistency review outcome, any fee-basis calculation, and the date of the determination.
Use a consistent format across all employees. Whether you use a spreadsheet, a form within your HRIS, or EasyClocking by WorkEasy Software's classification workflow, the structure should be identical for every employee evaluated. Consistency makes batch auditing possible and reduces the risk of missing a field during a DOL records request.
Sign and date the determination. If your organization requires a second reviewer, route the file for countersignature before proceeding to the duties test or pay rule configuration.
Expected outcome: A signed, dated salary basis determination on file with all comparison data and the pass/fail result.
6. Flag Threshold Failures for Non-Exempt Routing
Prerequisites
- Salary basis determination showing a fail result
If the employee's salary falls below the applicable threshold, mark the employee as non-exempt in the HRIS immediately. Do not proceed to the duties test. An employee who fails the salary basis test cannot be classified as exempt under any FLSA exemption category (with the narrow exception of outside sales, teachers, and practicing lawyers or doctors, who are exempt regardless of salary).
Route the employee directly to the non-exempt overtime pay rule configuration procedure. Until overtime rules are active in the timekeeping system, every hour this employee works beyond 40 in a workweek is accumulating unpaid overtime liability. Speed matters.
EasyClocking by WorkEasy Software's classification workflow triggers this routing automatically: when an employee's salary is entered below the current threshold, the system flags the record and prevents an exempt designation from being saved.
Expected outcome: The employee is marked non-exempt in the HRIS and routed to overtime pay rule configuration, with no duties test initiated.
7. Advance Passing Employees to the Duties Test
Prerequisites
- Salary basis determination showing a pass result
- Current job description on file for the employee
If the salary basis test passes, document the result in the classification file and proceed to the FLSA Duties Test for Exemption. A passing salary basis test is necessary but not sufficient for exempt classification. The employee must also meet the duties test for a named exemption category.
Before advancing, confirm the employee has a current, accurate job description on file. The duties test evaluates actual work performed, not job titles or aspirational descriptions. If the job description is outdated, update it with the employee's direct manager before beginning the duties test. An inaccurate job description is the most common source of indefensible exempt classifications.
Note the date and result of the salary basis test at the top of the duties test intake form so reviewers can confirm the prerequisite was met.
Expected outcome: The employee is cleared for the duties test with a passing salary basis determination documented and a current job description ready for review.

Download the procedure above

How to Run the FLSA Duties Test for Exemption

advanced · 2 hours

This procedure evaluates whether an employee's primary job duties qualify for one of the FLSA's named exemption categories: executive, administrative, professional, outside sales, or computer employee. Executed by HR after a passing salary basis test, it produces a documented exemption category determination or a non-exempt finding. Use this procedure for every salaried employee who passes the salary basis test.

1. Identify the Candidate Exemption Category
Prerequisites
- Passing salary basis test result (procedure 1 complete)
- Current job description listing primary duties and percentage of time per duty
Based on the employee's job title, department, and description, select the most likely FLSA exemption category. The five primary categories are:
- Executive: manages a recognized department, directs two or more employees, has hiring/firing authority or meaningful input.
- Administrative: performs office or non-manual work directly related to business operations or management policies, exercises discretion and independent judgment.
- Professional: performs work requiring advanced knowledge in a field of science or learning, customarily acquired through prolonged specialized instruction.
- Outside Sales: primary duty is making sales or obtaining orders away from the employer's place of business.
- Computer Employee: systems analyst, programmer, software engineer, or similar; applies systems analysis techniques or designs/develops computer programs.
Select one category as the starting point. If the employee's duties span multiple categories, evaluate the most likely category first. You may evaluate a second category if the first fails, but document both analyses.
Expected outcome: A candidate exemption category selected and recorded, with rationale based on job title and duties.
2. Pull the DOL Fact Sheet for the Candidate Category
Prerequisites
- DOL Fact Sheet for the applicable exemption category (current version)
Retrieve the DOL Fact Sheet for the selected exemption category. The relevant documents are:
- Fact Sheet #17A: General exemption overview
- Fact Sheet #17B: Executive exemption
- Fact Sheet #17C: Administrative exemption
- Fact Sheet #17D: Professional exemption
- Fact Sheet #17E: Computer employee exemption
- Fact Sheet #17F: Outside sales exemption
These fact sheets define the primary duty standard, the specific tests for each element, and the DOL's interpretive guidance. Use the fact sheet as your checklist; do not rely on memory or secondary summaries. The DOL updates these documents periodically, so confirm you are working from the current version by checking the revision date on the DOL Wage and Hour Division website.
Print or save the fact sheet alongside the employee's classification file so auditors can see exactly which standard you applied.
Expected outcome: The correct DOL Fact Sheet is retrieved, version-confirmed, and saved in the employee's classification file.
3. Evaluate the Primary Duty
Prerequisites
- DOL Fact Sheet primary duty standard for the selected category
- Job description with percentage-of-time estimates per duty
Confirm that the employee's principal, main, or most important duty matches the category's primary duty standard. "Primary duty" under the FLSA does not require a strict percentage-of-time test, but the DOL considers time spent a useful indicator. An employee who spends a meaningful majority of their time on exempt duties is more likely to meet the standard than one who performs exempt work only occasionally.
Compare the job description's duty list against the fact sheet's primary duty definition. For each duty listed, note whether it is exempt or non-exempt work. If the employee's actual work includes significant non-exempt duties (stocking shelves, operating equipment, serving customers), evaluate whether the exempt duties are genuinely the "most important" component of the role, not just the highest-titled component.
Do not rely on the job description alone. Cross-reference with the manager attestation (next step) to confirm the description reflects reality on the job site, the shop floor, the warehouse, or wherever the employee actually works.
Expected outcome: A documented assessment of whether the employee's primary duty matches the exemption category's standard, with duty-by-duty notes.
4. Apply the Discretion and Independent Judgment Test (Administrative Exemption)
Prerequisites
- Candidate exemption category is administrative
- Manager attestation confirming examples of discretion exercised
If evaluating the administrative exemption, confirm the employee exercises discretion and independent judgment on matters of significance. This is the most litigated element of any FLSA exemption test. The DOL defines "discretion and independent judgment" as comparing and evaluating possible courses of conduct and acting or making a decision after the various possibilities have been considered.
Key indicators include: authority to formulate or interpret company policies; authority to commit the employer in matters with significant financial impact; authority to negotiate and bind the company; and providing expert advice to management. Following detailed procedures, filling in forms, applying well-established techniques, or performing clerical work does not satisfy this standard, even if the employee has some latitude in sequencing tasks.
Document specific examples of decisions the employee makes and the significance of those decisions. If you cannot identify at least two or three concrete examples from the prior 12 months, the employee likely does not meet this test.
Expected outcome: A documented pass or fail on the discretion and independent judgment test, supported by concrete examples or their absence.
5. Apply the Management Test (Executive Exemption)
Prerequisites
- Candidate exemption category is executive
- Organizational chart showing direct reports and reporting structure
If evaluating the executive exemption, confirm three elements: (1) the employee manages a recognized department or subdivision, (2) the employee customarily and regularly directs the work of two or more full-time employees (or their equivalent), and (3) the employee has authority to hire or fire, or their recommendations on hiring, firing, advancement, or other status changes are given particular weight.
"Two or more full-time employees" means two employees working 40 hours per week, or the equivalent (four half-time employees, for example). Directing temporary or seasonal workers counts toward this threshold. However, merely assigning tasks without genuine supervisory responsibility does not qualify.
For the hiring/firing element, the employee does not need sole authority. If their input is one of several factors considered and is given particular weight, the test can be satisfied. Document the reporting structure, the number and type of direct reports, and specific examples of the employee's hiring, firing, or personnel recommendation authority.
Expected outcome: A documented pass or fail on the management test, with reporting structure and examples of supervisory authority on file.
6. Document the Duty-by-Duty Analysis
Prerequisites
- Completed primary duty evaluation and applicable sub-tests
Record each primary duty evaluated, the applicable standard from the DOL Fact Sheet, and whether the standard was met. Use a structured format: one row per duty, with columns for duty description, exemption element being tested, pass/fail, and supporting evidence.
This documentation is the core of your classification defense. In a DOL audit or wage-and-hour lawsuit, the question is not "did you classify this person as exempt?" but "can you show me the analysis that supports the classification?" A duty-by-duty analysis with dates, attestations, and fact sheet references is the defensible answer.
EasyClocking by WorkEasy Software's classification module stores this duty-by-duty analysis and exemption determination in the employee record, making it retrievable for DOL audit response without digging through paper files or shared drives.
Expected outcome: A structured duty-by-duty analysis on file for the employee, with each element documented as pass or fail.
7. Render the Exemption Determination
Prerequisites
- Completed duty-by-duty analysis for at least one exemption category
If all elements of the selected exemption category are met, classify the employee as exempt and record the specific category (executive, administrative, professional, outside sales, or computer employee). If any element fails, classify the employee as non-exempt.
If the primary category failed but a secondary category may apply, document the failure and begin the analysis for the secondary category. Do not assume a second category will succeed; evaluate it with the same rigor. If both categories fail, the employee is non-exempt.
Record the final determination, the exemption category (if applicable), and the date. This is the record that drives downstream pay rule configuration. A non-exempt determination routes to the overtime pay rule configuration procedure. An exempt determination routes to the exempt pay rule configuration procedure.
Expected outcome: A final exemption determination recorded: exempt under a named FLSA category, or non-exempt.
8. Obtain HR Sign-Off
Prerequisites
- Complete classification file including salary basis test, duty-by-duty analysis, and manager attestation
- Available HR manager or legal counsel for review
Have an HR manager or legal counsel review and countersign the determination before it is entered into the HRIS. The reviewer should confirm: (1) the salary basis test was completed and passed, (2) the duty-by-duty analysis is supported by current job duties and manager attestation, (3) the correct DOL Fact Sheet version was used, and (4) state-specific exemption rules were applied if the employee works in a state with stricter standards (California, for example, requires that exempt employees spend more than 50% of their time on exempt duties).
Once signed, enter the classification into the HRIS and attach the complete classification file. The classification is now the system of record for pay rule configuration and future audit defense.
Expected outcome: A countersigned exemption determination entered into the HRIS, with the complete classification file attached and ready for pay rule configuration.

Download the procedure above

How to Configure Non-Exempt Overtime Pay Rules in a Timekeeping System

intermediate · 30 minutes

This procedure translates a confirmed non-exempt classification into automated overtime calculation and pay code routing in a timekeeping and payroll platform. Executed by a payroll administrator after classification is confirmed, it produces a configured pay rule set that calculates overtime without manual intervention. Use this procedure immediately after any employee is classified or reclassified as non-exempt.

1. Open the Employee's Pay Rule Profile
Prerequisites
- Confirmed non-exempt classification on file (procedure 1 or 2 complete)
- Access to timekeeping/payroll system with pay rule configuration permissions
- Employee's assigned cost center and work schedule
Navigate to the timekeeping system's pay rule configuration for the employee or their assigned employee group. In EasyClocking by WorkEasy Software, this is located under the employee's profile in the pay rules section. If your organization uses employee groups (for example, grouping all non-exempt warehouse workers under one rule set), confirm the employee is assigned to the correct group before making changes.
If the employee is being reclassified from exempt to non-exempt, note the effective date of the reclassification. Pay rules should be activated as of the reclassification date, not retroactively; retroactive overtime calculations for misclassified employees require a separate remediation process and potentially legal counsel.
Expected outcome: The employee's pay rule profile is open and ready for configuration, with the correct employee group assignment confirmed.
2. Set the FLSA Status Field to Non-Exempt
Prerequisites
- Classification determination showing non-exempt status
Confirm the system's FLSA status flag is set to "non-exempt." This flag is the master switch that enables overtime calculation. In most timekeeping platforms, including EasyClocking by WorkEasy Software, setting this flag activates the overtime engine for the employee and makes overtime pay codes available for mapping.
Double-check that the flag was not previously set to exempt. If the employee was incorrectly flagged as exempt, changing the flag to non-exempt will not retroactively calculate missed overtime. Address back-pay obligations separately with HR and legal counsel.
Expected outcome: The FLSA status field reads "non-exempt" in the timekeeping system, and the overtime calculation engine is active for the employee.
3. Configure the Weekly Overtime Threshold
Prerequisites
- Applicable overtime threshold (federal and state) confirmed
Set the overtime trigger at 40 hours per workweek, or the applicable state threshold if lower. The federal FLSA requires overtime pay at 1.5 times the regular rate for all hours worked beyond 40 in a workweek. No state currently sets a weekly threshold below 40 hours, but several states layer daily overtime rules on top of the weekly threshold.
If the employee works in a state or jurisdiction with a lower weekly threshold (verify with your state labor department), apply the lower threshold. Record the threshold source (federal FLSA or state statute) in the pay rule configuration notes.
Expected outcome: The weekly overtime threshold is set to 40 hours (or the applicable state threshold) in the employee's pay rule profile.
4. Apply State Daily Overtime Rules
Prerequisites
- State daily overtime rules for the employee's work state(s) identified
If the employee works in California, Colorado, Alaska, or another state with daily overtime requirements, add the daily threshold as a secondary pay rule layer. California, for example, requires overtime at 1.5 times the regular rate for hours worked beyond 8 in a single workday, and double-time for hours beyond 12.
Configure the daily overtime rule as a separate layer that operates independently of the weekly threshold. The employee should receive whichever calculation produces the greater overtime payment. In EasyClocking by WorkEasy Software, the pay rule engine applies state-specific daily overtime layers automatically based on the employee's work location, but verify the configuration is active for the correct state.
If the employee works across multiple states (for example, a construction crew member who works in both Nevada and California), configure location-based rules that apply the correct daily overtime standard for each workday based on where the work was performed.
Expected outcome: Daily overtime rules are active for applicable states, layered on top of the weekly threshold, with correct rates (1.5x and 2x where applicable) configured.
5. Assign the Overtime Pay Code
Prerequisites
- Payroll system earning codes for overtime (1.5x) and double-time (2x) identified
Map hours exceeding the weekly threshold to the 1.5x overtime pay code. Map hours exceeding double-time thresholds (where applicable, such as California's 12-hour daily rule or seventh-consecutive-day rule) to the 2x pay code.
Confirm that the pay codes are recognized by your payroll system's import or integration. If you export time data to a third-party payroll provider, verify that the overtime pay code maps correctly to the payroll system's earning codes. A mapping error here means overtime hours will import as regular hours, producing incorrect paychecks and accumulating back-pay liability.
If your organization uses EasyClocking by WorkEasy Software with one of the platform's 20+ payroll integrations, the pay code mapping is pre-configured for most major payroll systems. Verify the mapping by checking the integration settings before running a test calculation.
Expected outcome: Overtime and double-time pay codes are mapped correctly and will flow into the payroll system with the proper earning code designation.
6. Configure the Workweek Definition
Prerequisites
- Employer's defined workweek start day confirmed
Confirm the system's workweek start day matches the employer's defined workweek. The FLSA defines a workweek as a fixed, recurring period of 168 hours (seven consecutive 24-hour periods). Employers can choose any day and time as the workweek start, but once set, it cannot be changed for the purpose of avoiding overtime obligations.
A misaligned workweek is one of the most common causes of systematic overtime miscalculation. If the system thinks the workweek starts on Sunday but the employer's defined workweek starts on Monday, every weekly overtime calculation will be off by one day. This error compounds across every non-exempt employee and every pay period.
Verify the workweek start day in the timekeeping system's global settings, then confirm it matches the employee's assigned schedule. Document the workweek definition in the pay rule configuration notes.
Expected outcome: The timekeeping system's workweek start day matches the employer's defined workweek, and the alignment is documented.
7. Run a Test Calculation
Prerequisites
- A sample timecard scenario with known correct overtime calculation
Enter a sample timecard with known overtime hours and verify the system produces the correct gross pay. Use a realistic scenario: for example, a workweek with 45 hours, where 40 hours should calculate at the regular rate and 5 hours at the 1.5x rate. If the employee is subject to daily overtime rules, include a day with 10 hours to verify the daily threshold triggers correctly.
Compare the system's output to a manual calculation. If the figures match, activate the pay rule for live payroll. If they differ, check the workweek alignment, pay code mapping, and threshold settings before rerunning the test.
Document the test scenario, the expected result, and the actual result in the configuration notes. This test record serves as evidence that the pay rule was validated before going live, which is relevant in any future audit or dispute.
Expected outcome: The test calculation matches the manual calculation, the pay rule is validated, and the configuration is activated for live payroll.

Download the procedure above

How to Configure Exempt Employee Pay Rules to Prevent Improper Deductions

intermediate · 30 minutes

This procedure sets up a timekeeping and payroll system so that exempt employees receive their full salary in any week work is performed, with no automatic deductions that would destroy the salary basis. Executed by a payroll administrator after exempt classification is confirmed, it produces a pay rule set that protects exemption status. Use this procedure for every newly confirmed exempt employee.

1. Set the FLSA Status Field to Exempt
Prerequisites
- Confirmed exempt classification with named FLSA category on file (procedure 2 complete)
- Timekeeping/payroll system access with pay rule configuration permissions
Confirm the system's FLSA status flag is set to "exempt." This flag disables automatic overtime calculation and signals salary-basis pay for the employee's profile. In EasyClocking by WorkEasy Software, setting this flag also activates the exempt pay rule template, which includes default protections against improper deductions.
Before changing the flag, confirm the employee has a signed, countersigned exemption determination on file from the duties test procedure. Setting the exempt flag without a documented basis creates audit exposure. The flag setting and the classification file should reference each other by date and employee ID.
If the employee was previously classified as non-exempt, deactivate the overtime pay rules before setting the exempt flag. Leaving both active creates conflicting pay calculations and confusing payroll records.
Expected outcome: The FLSA status field reads "exempt" in the timekeeping system, overtime calculation is disabled, and the exempt pay rule template is active.
2. Disable Partial-Day Time Deductions
Prerequisites
- Exempt pay rule template active for the employee
- FMLA leave pay code configured separately if applicable
Configure the system to block automatic pay deductions for partial-day absences. Under the FLSA salary basis requirement, an exempt employee must receive the full predetermined salary for any week in which they perform any work. Deducting pay because an employee left two hours early, arrived 30 minutes late, or took a long lunch destroys the salary basis and can retroactively reclassify the employee as non-exempt, triggering back-overtime liability.
In EasyClocking by WorkEasy Software, the exempt pay rule template blocks partial-day deductions by default. Verify this setting is active and that no override has been configured at the employee group or individual level. If your organization tracks exempt employee hours for project costing or client billing purposes, confirm that the tracking does not trigger pay deductions; tracking hours for informational purposes is permissible, but docking pay is not.
The only permissible partial-day deduction for an exempt employee is under the Family and Medical Leave Act (FMLA), where intermittent leave may be deducted in partial-day increments. Configure FMLA leave as a separate pay code that does not interact with the standard partial-day deduction block.
Expected outcome: The system blocks all automatic partial-day pay deductions for the exempt employee, with FMLA leave handled as a separate, permissible deduction.
3. Enable Permissible Full-Day Deductions
Prerequisites
- Company PTO policy and absence types defined in the system
- List of permissible deduction scenarios under FLSA reviewed
Configure the system to allow deductions only for full-day absences when the employee has exhausted their paid time off (PTO) balance, or for full workweeks with no work performed. The FLSA permits deductions for full-day personal absences (not sickness or disability) once PTO is exhausted, and for full-day absences due to sickness or disability if the employer has a bona fide plan providing wage replacement.
Map each permissible deduction scenario to a specific pay code or absence type in the system. Do not use a generic "unpaid absence" code that could be applied to partial-day absences as well. Specificity protects you; a DOL auditor reviewing payroll records can see exactly which deduction type was applied and confirm it falls within the permissible categories.
Also configure deductions for unpaid disciplinary suspensions of one or more full days imposed in good faith for violations of workplace conduct rules. This is a narrow FLSA permission; ensure suspensions are documented with the conduct rule violated and the number of full days imposed.
Expected outcome: Full-day deductions are configured with specific pay codes for each permissible scenario, and no generic absence code can trigger a partial-day deduction.
4. Suppress Overtime Pay Codes
Prerequisites
- Overtime pay code mapping reviewed for the employee's profile and group
Confirm that no overtime pay code is mapped to the exempt employee's profile. Overtime payments to exempt employees can imply non-exempt treatment, and if a DOL auditor sees overtime earn codes on an exempt employee's payroll record, it raises an immediate question about whether the classification is valid.
Check both the individual employee profile and the employee group assignment. If the employee was recently reclassified from non-exempt to exempt, the overtime pay code from the prior configuration may still be active. Remove or deactivate it.
If your organization voluntarily pays exempt employees additional compensation for extra hours (sometimes called "straight-time bonuses"), use a bonus or supplemental pay code, not an overtime code. The distinction matters for audit defensibility.
Expected outcome: No overtime pay code is active or mapped for the exempt employee, and any supplemental pay uses a non-overtime earning code.
5. Link the Safe Harbor Policy
Prerequisites
- Company safe harbor policy drafted and approved by legal counsel
- Policy communicated to the employee (acknowledgment on file)
Attach the company's written improper deduction complaint procedure to the employee's record so it is retrievable during a DOL audit. The FLSA safe harbor provision protects the employer's exempt classifications if: (1) the employer has a clearly communicated written policy prohibiting improper deductions, (2) the policy includes a complaint mechanism, (3) the employer reimburses any improper deductions, and (4) the employer makes a good-faith commitment to comply going forward.
Without the safe harbor policy on file and linked to the employee record, a single improper deduction can be used as evidence that the employer did not intend to pay on a salary basis, potentially reclassifying the employee and triggering back-overtime liability. EasyClocking by WorkEasy Software's exempt pay rule template includes a pre-built safe harbor policy link field; populate it with the document reference or URL where the policy is stored.
Expected outcome: The safe harbor policy is linked to the employee's record in the timekeeping system and retrievable for audit response.
6. Validate with a Test Payroll Scenario
Prerequisites
- Sample timecard scenarios prepared for partial-day absence and full-day unpaid absence
Run a test scenario with a partial-day absence and confirm no deduction is generated. Enter a timecard showing the exempt employee worked four days and left two hours early on the fifth day. The system should calculate the full weekly salary with no reduction. If the test produces a deduction, review the partial-day deduction block and the pay code configuration before activating the rule for live payroll.
Run a second test showing a full-day unpaid absence (PTO exhausted) and confirm the system deducts exactly one full day's pay, not a partial amount. Both tests should pass before the pay rule goes live.
Document both test scenarios, expected results, and actual results in the configuration file. This validation record is your evidence that the pay rule was tested before it affected a live paycheck.
Expected outcome: Both test scenarios produce correct results: no deduction for the partial-day absence, a full-day deduction for the unpaid full-day absence. The pay rule is activated for live payroll.

Download the procedure above

How to Audit Employee Classification Accuracy for FLSA Compliance

advanced · 2 days

This procedure systematically reviews an employer's exempt and non-exempt classifications to detect misclassification, stale determinations, and pay rule misconfigurations before they generate liability. Executed by HR and payroll compliance staff on an annual or event-triggered basis, it produces a classification audit report with a remediation list. Use this procedure annually and after any reorganization, acquisition, or DOL rule change.

1. Export the Classification Roster
Prerequisites
- HRIS access with permission to export classification data for all employees
- Full employee roster including terminated employees active in the prior 12 months
- Current DOL salary threshold and applicable state thresholds on hand
Pull a full employee list from the HRIS with columns for FLSA status, job title, weekly salary, pay rule assignment, exemption category, and last classification review date. Export to a format that supports filtering and sorting (spreadsheet or structured report).
EasyClocking by WorkEasy Software's compliance audit workflow automates this export, pulling the roster with all classification fields pre-populated. If you are exporting manually, confirm every column is present before proceeding; a missing field (especially "last review date") will make it impossible to flag stale determinations in the next step.
Include terminated employees who were active during the audit period (prior 12 months). Misclassification liability does not end at termination; a former employee can file a wage claim for back overtime for up to three years under the FLSA (two years for non-willful violations, three years for willful violations).
Expected outcome: A complete classification roster exported with all required fields, including terminated employees from the audit period.
2. Flag Stale Determinations
Prerequisites
- Classification roster with last review date and current job title columns populated
Mark any employee whose classification was last reviewed more than 24 months ago, or whose job title or duties have changed since the last review. FLSA exemption is based on current duties; a classification made three years ago for a different role is indefensible if the employee's responsibilities have shifted.
Also flag employees who have been promoted, transferred to a different department, or had their job description rewritten since their last classification review. These events are common triggers for duties changes that can invalidate a prior exempt determination.
Record the flag reason for each employee (stale date, title change, department transfer, or description rewrite). This reason determines which remediation procedure applies in step 9.
Expected outcome: All employees with stale or potentially invalid classifications are flagged with a documented reason for review.
3. Run the Salary Threshold Screen
Prerequisites
- Current DOL salary threshold verified against the Federal Register
- Applicable state salary thresholds for each employee's work state
For every exempt employee on the roster, compare the current weekly salary to the current DOL threshold and the applicable state threshold (whichever is higher). Flag any employee whose salary now falls below the threshold. This happens more often than organizations expect: salary thresholds increase, but not every employee receives a corresponding raise.
EasyClocking by WorkEasy Software automates this comparison, flagging employees below the threshold as soon as a new DOL rule takes effect. If you are running this screen manually, sort the roster by weekly salary (ascending) and work from the bottom up to catch threshold failures quickly.
Employees flagged in this step require immediate reclassification to non-exempt and activation of overtime pay rules. Do not wait until the end of the audit to address threshold failures; every week that passes accumulates unpaid overtime liability.
Expected outcome: Every exempt employee's salary has been compared to the current threshold, and all below-threshold employees are flagged for immediate reclassification.
4. Sample Duties Test Files
Prerequisites
- Classification files with duty-by-duty analysis on file for sampled employees
- Current job descriptions and manager attestations for sampled employees
For a random 20% sample of exempt employees, pull the duty-by-duty analysis from their classification file (produced in procedure 2) and verify it reflects the employee's current actual duties. Compare the documented duties against the current job description and, if available, recent performance reviews or project assignments.
If the documented duties no longer match the employee's actual work, flag the employee for a full duties test re-evaluation. Common mismatches include: a "manager" who no longer supervises two or more employees due to layoffs or restructuring; an "administrative" exempt employee whose role has shifted to primarily operational or manual work; or a "professional" exempt employee who is now performing routine tasks that do not require advanced knowledge.
Document each sampled employee, the comparison result (match or mismatch), and the specific discrepancy if any. A 20% sample provides a statistically meaningful snapshot; if the mismatch rate exceeds 10% of the sample, consider expanding the audit to a full population review.
Expected outcome: A documented sample of 20% of exempt employees, with match/mismatch results and specific discrepancies flagged for re-evaluation.
5. Cross-Reference Overtime Payments
Prerequisites
- Payroll register for the prior 12 months showing overtime payments by employee
- Classification roster with FLSA status for cross-reference
Identify any exempt-flagged employee who received overtime pay in the prior 12 months. Pull the payroll register filtered by earning codes for overtime (1.5x) and double-time (2x), then cross-reference against the classification roster to find exempt employees who appear on the overtime register.
An overtime payment to an exempt employee signals one of two problems: a pay rule misconfiguration (overtime codes were not suppressed per procedure 4), or the employee is being treated as non-exempt in practice despite being classified as exempt on paper. Either scenario requires investigation.
For each flagged employee, determine whether the overtime payment was a one-time payroll error (correctable with a payroll adjustment) or a recurring pattern (which may indicate the employee is actually performing non-exempt work and should be reclassified). Document the finding and the resolution path.
Expected outcome: All exempt employees who received overtime pay are identified, with a documented determination of whether each case is a pay rule error or a potential misclassification.
6. Identify Salaried Non-Exempt Employees
Prerequisites
- Classification roster filtered for salaried non-exempt employees
- Pay rule configuration records for each salaried non-exempt employee
Confirm that any salaried employee classified as non-exempt has active overtime rules configured per procedure 3. Salaried non-exempt is a valid FLSA status, but it is the classification most likely to have misconfigured pay rules. Because these employees receive a salary, payroll administrators sometimes assume they are exempt and skip overtime configuration.
Pull all employees from the roster who are flagged non-exempt but paid on a salary basis. Verify that each one has an active weekly overtime threshold, correct pay code mapping, and a validated test calculation on file. If any salaried non-exempt employee lacks active overtime rules, flag them for immediate procedure 3 configuration.
Expected outcome: All salaried non-exempt employees are confirmed to have active, validated overtime pay rules, or are flagged for immediate configuration.
7. Document Findings
Prerequisites
- Completed steps 2 through 6 with all flagged employees documented
Record each flagged employee, the nature of the issue (stale determination, salary threshold failure, pay rule misconfiguration, duties mismatch, or overtime payment anomaly), and the required remediation action. Use a structured format: one row per flagged employee, with columns for employee name/ID, issue type, severity (high/medium/low), remediation procedure (P1, P2, P3, or P4), assigned owner, and due date.
Categorize severity as follows: threshold failures and pay rule misconfigurations are high severity because they create active, accumulating liability. Stale determinations and duties mismatches are medium severity because they create audit exposure but may not result in immediate financial liability. Overtime payment anomalies are variable severity depending on whether they reflect a one-time error or a pattern.
Expected outcome: A structured findings document with every flagged employee, issue type, severity, remediation procedure, and assigned owner recorded.
8. Prioritize and Assign Remediation
Prerequisites
- Completed findings document with severity ratings
Rank findings by liability exposure. Address threshold failures and pay rule misconfigurations first, as these represent active, accumulating wage-and-hour violations. Assign each finding to a specific owner (HR analyst, payroll administrator, or legal counsel) with a due date that reflects the severity.
High-severity findings should be remediated within one pay period. Medium-severity findings should be remediated within 30 days. If the volume of findings exceeds the team's capacity, escalate to HR leadership and consider engaging outside counsel to prioritize based on legal exposure.
Track remediation status in the same document used for findings. Do not create a separate tracker; a single source of truth reduces the risk of a finding being overlooked during a busy payroll cycle.
Expected outcome: All findings are ranked by severity, assigned to named owners with due dates, and tracked in a single document.
9. Rerun Affected Procedures
Prerequisites
- Remediation assignments distributed to owners with due dates
- Access to procedures 1 through 4 for re-execution
For each flagged employee, execute the appropriate procedure to produce a current, defensible classification and pay rule set. Route threshold failures to procedure 1 (salary basis test). Route duties mismatches to procedure 2 (duties test). Route pay rule misconfigurations to procedure 3 (non-exempt overtime rules) or procedure 4 (exempt pay rules). Route stale determinations to procedure 1 and then procedure 2 in sequence.
As each remediation is completed, update the findings document with the completion date and the new classification or pay rule status. Once all high-severity findings are resolved, compile the findings document, the remediation log, and any updated classification files into a classification audit report.
Sign and date the audit report. This report is your primary defense document in a DOL audit or wage-and-hour claim. Store it alongside the employee classification files in a location accessible to HR leadership and legal counsel. EasyClocking by WorkEasy Software's compliance audit workflow maintains this report digitally, linked to each employee's updated classification record.
Expected outcome: All flagged employees have current, defensible classifications and validated pay rules. A signed classification audit report is on file with a complete remediation log.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Apply the FLSA Salary Basis Test

1. Retrieve the Compensation Record

2. Compare to the DOL Salary Threshold

3. Verify Payment Consistency

4. Identify Fee-Based Compensation Exceptions

5. Document the Salary Basis Determination

6. Flag Threshold Failures for Non-Exempt Routing

7. Advance Passing Employees to the Duties Test

How to Run the FLSA Duties Test for Exemption

1. Identify the Candidate Exemption Category

2. Pull the DOL Fact Sheet for the Candidate Category

3. Evaluate the Primary Duty

4. Apply the Discretion and Independent Judgment Test (Administrative Exemption)

5. Apply the Management Test (Executive Exemption)

6. Document the Duty-by-Duty Analysis

7. Render the Exemption Determination

8. Obtain HR Sign-Off

How to Configure Non-Exempt Overtime Pay Rules in a Timekeeping System

1. Open the Employee's Pay Rule Profile

2. Set the FLSA Status Field to Non-Exempt

3. Configure the Weekly Overtime Threshold

4. Apply State Daily Overtime Rules

5. Assign the Overtime Pay Code

6. Configure the Workweek Definition

7. Run a Test Calculation

How to Configure Exempt Employee Pay Rules to Prevent Improper Deductions

1. Set the FLSA Status Field to Exempt

2. Disable Partial-Day Time Deductions

3. Enable Permissible Full-Day Deductions

4. Suppress Overtime Pay Codes

5. Link the Safe Harbor Policy

6. Validate with a Test Payroll Scenario

How to Audit Employee Classification Accuracy for FLSA Compliance

1. Export the Classification Roster

2. Flag Stale Determinations

3. Run the Salary Threshold Screen

4. Sample Duties Test Files

5. Cross-Reference Overtime Payments

6. Identify Salaried Non-Exempt Employees

7. Document Findings

8. Prioritize and Assign Remediation

9. Rerun Affected Procedures

How These Procedures Connect

Next steps