How to Automate FLSA Overtime Enforcement: 5 Procedures for HR and Payroll | EasyClocking by WorkEasy Software

How to Identify and Configure FLSA Overtime Triggers in Your Timekeeping System

intermediate · Variable based on employee count and state coverage

This procedure translates federal and applicable state overtime thresholds into enforceable rules inside a timekeeping or payroll system. It is executed by an HR operations or payroll administrator during initial system setup or after a regulatory change and produces a validated rule set that fires automatically when an employee crosses a covered threshold.

1. Audit Employee Classifications
Prerequisites
- Confirmed FLSA non-exempt classification list for all in-scope employees
- Admin access to the timekeeping or time tracking platform
- Current FLSA salary-level threshold for exemption screening ($684/week as of current federal rule)
Pull the full non-exempt roster from your HR system and confirm each employee's FLSA status is recorded in the timekeeping platform before any rule is applied. Compare each employee's actual job duties and compensation against the FLSA exemption criteria. Employees paid on a salary basis must meet the current federal salary-level threshold for exemption screening.
Pay special attention to employees whose roles have changed recently. A promotion, a shift in duties, or a compensation adjustment can alter exempt status. Flag any employee whose classification has not been reviewed within the past 12 months.
Why this matters: Applying overtime rules to exempt employees inflates payroll costs. Failing to apply them to non-exempt employees creates wage-and-hour exposure. Every downstream procedure in this playbook depends on an accurate non-exempt roster.
Expected outcome: Every active employee in the timekeeping system has a verified exempt or non-exempt classification tag, and the non-exempt roster matches the HR system of record.
2. Define the Workweek Boundary
Prerequisites
- Organizational decision on workweek start day and time
- Admin access to the timekeeping platform
Set the fixed 7-consecutive-day workweek start day and time in the system. FLSA overtime is calculated per workweek, not per pay period. This is the single most important configuration decision in overtime enforcement because it determines which hours fall inside which calculation window.
Select a start day and time that aligns with your operational schedule. Many employers choose Sunday at midnight or Monday at midnight, but any fixed 168-hour period is permissible. Once set, the boundary must be applied consistently and cannot be changed to avoid overtime obligations.
If your organization operates across multiple time zones, define whether the workweek boundary follows each site's local time or a single headquarters time. Document this decision; it will be the first piece of evidence a DOL investigator requests in an overtime audit.
Expected outcome: The timekeeping system reflects a single, fixed workweek boundary that applies consistently to all non-exempt employees, and the boundary is documented in writing.
3. Enter the Federal Weekly Threshold
Prerequisites
- Workweek boundary configured (Step 2 completed)
- Non-exempt employee roster verified (Step 1 completed)
Configure the 40-hour weekly trigger as the baseline overtime rule for all non-exempt employees in scope. This is the federal FLSA minimum; every non-exempt employee in every state is covered by this threshold regardless of any additional state rules.
In EasyClocking by WorkEasy Software, navigate to the overtime rules configuration module and set the weekly threshold to 40 hours. Assign this rule to the non-exempt employee group you verified in Step 1. Confirm that the rule applies to every workweek independently, not to the pay period as a whole. A biweekly pay period does not create an 80-hour overtime threshold under FLSA.
Verify that the system is set to calculate overtime based on hours actually worked, not hours paid. PTO, holiday pay and sick leave generally do not count toward the 40-hour overtime threshold under federal law unless a collective bargaining agreement or company policy states otherwise.
Expected outcome: A 40-hour weekly overtime trigger is active for every non-exempt employee, calculated per workweek, with hours-worked (not hours-paid) as the calculation basis.
4. Layer State Daily Thresholds
Prerequisites
- Knowledge of applicable state daily overtime thresholds for each employee's work location
- Federal weekly threshold configured (Step 3 completed)
For employees in states with daily overtime laws, add a secondary daily trigger that fires before the weekly threshold is reached. California requires overtime at 1.5x for hours over 8 in a single workday. Nevada and Alaska have similar daily overtime provisions, though the specifics differ.
Identify every state where your non-exempt employees perform work, not where your company is headquartered. The governing jurisdiction is the state where the work is physically performed. For employees who travel between states during a single workweek, consult counsel on apportioning hours by work state.
Configure the daily threshold as a separate rule that runs before the weekly calculation. The system must be able to fire both a daily and a weekly trigger in the same workweek without double-counting hours that have already been captured as daily overtime. Test this interaction explicitly; it is the most common misconfiguration in multi-threshold setups.
Expected outcome: A daily overtime trigger is active for every non-exempt employee working in a state with daily overtime law, layered on top of the federal 40-hour weekly rule, with no double-counting between daily and weekly triggers.
5. Set the 1.5x Multiplier as the Default Overtime Rate
Prerequisites
- Federal and state overtime thresholds configured (Steps 3 and 4 completed)
Assign time-and-a-half as the system default for all hours exceeding the configured threshold. Under FLSA, the overtime premium is 0.5 times the employee's regular rate of pay, added to the straight-time compensation the employee has already earned for those hours. Most payroll systems express this as a 1.5x multiplier applied to the regular rate.
Confirm that the system calculates the regular rate correctly. The regular rate is not always the same as the base hourly rate; it includes non-discretionary bonuses, shift differentials and other qualifying compensation. Procedure 4 in this hub covers the blended regular rate calculation in detail for employees with multiple pay rates.
Set this multiplier as the default rather than a per-employee override. Individual employees should inherit the 1.5x rule from the non-exempt group configuration unless a specific state rule requires a different rate.
Expected outcome: The 1.5x overtime multiplier is the default rate for all non-exempt employees, applied automatically to hours exceeding the configured daily or weekly threshold.
6. Configure the 2x (Double-Time) Trigger Where Applicable
Prerequisites
- Identification of states with double-time requirements for your employee population
- 1.5x multiplier configured (Step 5 completed)
Add a secondary rate rule for hours exceeding state-mandated double-time thresholds. Federal FLSA does not require double time; this is exclusively a state-law obligation. California, for example, requires 2x pay for hours over 12 in a single workday and for hours over 8 on a 7th consecutive workday in a single workweek.
Configure the double-time rule only for employees working in states where it applies. Do not apply it globally; doing so overpays employees in states without double-time requirements. In the system, the 2x rule should fire after the 1.5x daily overtime rule and should replace (not stack on top of) the 1.5x rate for qualifying hours.
Document which state statute governs each double-time rule you configure. This documentation becomes part of the audit trail described in Procedure 5 and will be requested if the overtime calculation is ever challenged.
Expected outcome: A 2x overtime rate rule is active only for employees in jurisdictions with double-time requirements, firing correctly after the 1.5x threshold and replacing (not stacking on) the time-and-a-half rate for qualifying hours.
7. Run a Test Pay Period with Synthetic Data
Prerequisites
- All threshold and rate rules configured (Steps 1 through 6 completed)
- A set of synthetic employee time records covering each threshold-crossing scenario
Process a simulated workweek containing threshold-crossing scenarios and confirm the system fires the correct rule for each case before going live. Build test cases that cover the following scenarios at minimum:
- An employee working exactly 40 hours (no overtime should fire)
- An employee working 45 hours in a federal-only state (5 hours at 1.5x)
- An employee working 10 hours in a single day in California (2 hours at 1.5x daily overtime)
- An employee working 13 hours in a single day in California (2 hours at 1.5x, 1 hour at 2x)
- An employee working 7 consecutive days in California with 9 hours on the 7th day (8 hours at 1.5x, 1 hour at 2x on the 7th day)
- An employee working 38 hours across 5 days with no single day exceeding 8 hours (no overtime)
Compare the system's output to a manual calculation for each test case. Any discrepancy must be resolved before the rule set is activated for live payroll. EasyClocking by WorkEasy Software allows administrators to validate rule sets against synthetic pay data before activating for live payroll, reducing the risk of a misconfigured rule running undetected through a real pay cycle.
Expected outcome: Every test case produces the expected overtime classification and pay amount, matching a manual calculation. The rule set is validated and ready for live activation.

Download the procedure above

How to Determine Which Overtime Rate Applies (1.5x vs. 2x)

intermediate · Variable per employee per workweek

This procedure selects the correct overtime multiplier for a specific block of hours worked by a non-exempt employee. It is executed by a payroll administrator or HR analyst when processing hours that cross multiple thresholds and produces a documented rate-assignment decision for each overtime hour block.

1. Identify the Employee's Work State
Prerequisites
- Confirmed employee work state for each shift in the workweek
- FLSA overtime trigger configuration completed (Procedure 1)
Confirm the jurisdiction whose overtime rules govern the employee. The controlling state is where the work is physically performed, not where the employer is headquartered or where the employee lives. For a construction crew traveling between Nevada and Arizona job sites in the same workweek, each day's hours are governed by the state where that day's work occurred.
Record the work state at the shift level in your time tracking system. If your platform supports location tagging through GPS or site assignment, use that data. If not, require supervisors or employees to indicate the work state for each shift. This shift-level state assignment drives every downstream rate decision.
For remote employees, confirm whether your organization follows the employee's physical location or has a different policy. Consult counsel if employees work from multiple states within a single workweek.
Expected outcome: Each shift in the workweek has a documented work-state assignment that determines which overtime rules apply.
2. Check for Daily Overtime Eligibility
Prerequisites
- Work-state assignment completed for each shift (Step 1 of this procedure)
- Net daily hours calculated after break deductions
If the employee works in a state with daily overtime rules, flag all hours over 8 in a single workday as 1.5x-eligible before evaluating weekly totals. California, Nevada and Alaska are the most common daily-overtime states, but always verify current state law for each jurisdiction in your employee population.
Calculate net hours worked per workday after subtracting qualifying unpaid meal and rest breaks. Compare the net daily total to the state's daily threshold. Hours exceeding that threshold become daily overtime hours and are marked with a 1.5x rate code.
Do not skip this step for employees in states without daily overtime. Documenting that you checked and confirmed no daily trigger applies is part of the rate-assignment audit trail. It prevents questions later about whether the analysis was performed.
Expected outcome: All daily overtime hours are identified and flagged with a 1.5x rate code, or the absence of a daily overtime trigger is documented.
3. Check for Double-Time Eligibility
Prerequisites
- Daily overtime check completed (Step 2 of this procedure)
- Knowledge of applicable state double-time thresholds
Apply the 2x rate to hours exceeding state-mandated double-time thresholds. Under California law, hours over 12 in a single workday trigger double time. Hours over 8 on the 7th consecutive workday in a single workweek also trigger double time in California. Federal FLSA does not mandate double time under any circumstances.
Identify which hours, if any, fall into the double-time bucket. These hours should be re-coded from the 1.5x rate to the 2x rate. The 2x rate replaces 1.5x for qualifying hours; it does not stack on top. An employee who works 14 hours in a California workday earns straight time for the first 8 hours, 1.5x for hours 9 through 12, and 2x for hours 13 and 14.
If the employee does not work in a state with double-time requirements, document that no 2x trigger applies and move to the next step.
Expected outcome: All double-time hours are identified and coded at 2x, or the absence of a double-time trigger is documented.
4. Calculate Weekly Overtime Hours
Prerequisites
- Daily and double-time checks completed (Steps 2 and 3)
- Accurate net hours for each day of the workweek
Sum all hours worked in the 7-day workweek. Hours exceeding 40 that have not already been captured as daily overtime are 1.5x-eligible under federal FLSA. This is where the interaction between daily and weekly overtime requires careful handling.
Hours already flagged as daily overtime (1.5x or 2x) count toward the 40-hour weekly total but are not re-coded at the weekly level. The employee has already received the overtime premium for those hours. Only hours above 40 that are still coded as straight time convert to weekly overtime at 1.5x.
Example: An employee in California works five 9-hour days (45 total hours). Each day produces 1 hour of daily overtime at 1.5x (5 daily OT hours). The employee's weekly total is 45 hours, which is 5 hours over the 40-hour weekly threshold. However, those 5 hours are already captured as daily overtime. No additional weekly overtime hours are created because the daily premium already covers them.
Expected outcome: Weekly overtime hours are calculated without double-counting hours already captured as daily overtime. The total overtime hour count for the workweek is finalized.
5. Assign Rate Codes to Each Hour Block
Prerequisites
- Weekly overtime calculation completed (Step 4)
Label each hour segment in the payroll system with the corresponding rate code: straight time (ST), daily overtime (DOT at 1.5x), weekly overtime (WOT at 1.5x), or double time (DT at 2x). Include the rule that triggered each code. EasyClocking by WorkEasy Software automatically assigns rate codes to each hour block based on the employee's work-state rule set, eliminating the manual rate-selection step and producing a documented rate-assignment record for every pay period.
Review the final code assignments before passing to payroll. Look for anomalies: an employee with zero straight-time hours (likely a data error), an employee with double-time in a state that does not require it (misconfigured rule), or an employee whose weekly overtime hours overlap with daily overtime hours (double-counting).
Correct any anomalies before the data moves to payroll processing. A rate-code error at this stage becomes a paycheck error and potentially a wage-and-hour violation.
Expected outcome: Every hour in the workweek is labeled with the correct rate code and triggering rule, ready for payroll processing.
6. Document the Rate-Assignment Rationale
Prerequisites
- Rate codes assigned to all hour blocks (Step 5 completed)
Record the jurisdiction, threshold and rule citation for each rate code applied during this workweek. This documentation serves as the audit trail for the pay calculation and is a required component of the audit documentation package described in Procedure 5.
At minimum, the record should include: the employee's name and ID, the workweek dates, the work state for each shift, the daily and weekly hour totals, the rate code assigned to each hour block, and the specific rule (federal FLSA 40-hour weekly, California Labor Code Section 510 daily overtime, etc.) that triggered each code.
Store this record in your time tracking platform alongside the approved time data. If your system generates rate-assignment logs automatically, verify that the logs contain enough detail to reconstruct the decision. If they do not, supplement with a manual notation. The goal is a record that a third party, such as a DOL investigator or an auditor, can follow from raw time data to final pay without additional explanation.
Expected outcome: A complete, retrievable rate-assignment record exists for the workweek, containing jurisdiction, threshold, rule citation and hour-block breakdown for every non-exempt employee.

Download the procedure above

How to Map Shift Hours to Daily and Weekly Overtime Thresholds

intermediate · Variable based on employee count and shift complexity

This procedure translates raw time-punch data from non-standard shifts, including extended schedules, split shifts and shifts spanning midnight, into correctly bucketed straight-time and overtime hours. It is executed by a payroll or scheduling administrator before each payroll run and produces a shift-level hour map that feeds directly into overtime rate calculation.

1. Pull Approved Time Records
Prerequisites
- Complete, approved time records for all non-exempt employees for the workweek
- Workweek boundary configured in the timekeeping system (Procedure 1 completed)
- All timesheet exceptions resolved
Export or access the finalized, manager-approved time punches for the workweek. Do not run overtime calculations on unapproved or estimated time. Every missing punch, pending exception and unresolved dispute must be resolved before shift mapping begins.
In EasyClocking by WorkEasy Software, the timesheet approval workflow surfaces missing punches, late arrivals, early departures and no-shows as exceptions before payroll close. Review the exception dashboard and resolve every open item. An unresolved missing punch can shift hours between days, potentially triggering or suppressing overtime incorrectly.
Confirm that the time records reflect the workweek boundary configured in Procedure 1, not the pay-period boundary. If your organization uses biweekly pay periods, the system must still calculate overtime on a per-workweek basis. Pull records for each complete workweek within the pay period separately.
Expected outcome: A clean, approved set of time records for each non-exempt employee covering every complete workweek in the pay period, with zero unresolved exceptions.
2. Apply Break and Meal-Period Deductions
Prerequisites
- Approved time records pulled (Step 1 completed)
- Break and meal-period rules configured for each applicable state
Subtract all qualifying unpaid break periods from gross hours worked per shift, per applicable federal and state rules, before any threshold comparison. This step must happen before overtime calculations because overtime thresholds apply to net hours worked, not gross scheduled time.
Federal FLSA does not require meal or rest breaks, but many states do. California requires a 30-minute unpaid meal period for shifts over 5 hours and a second meal period for shifts over 10 hours. If an employee works through a required meal break, the break time may still need to be paid, and the hours count toward overtime thresholds.
Verify that your system applies break deductions based on actual break punches, not scheduled break times. If an employee's scheduled break is 30 minutes but they clocked back in after 20 minutes, the system should deduct 20 minutes, not 30. Over-deducting break time understates hours worked and can suppress overtime that the employee actually earned.
Expected outcome: Gross shift hours are reduced to net hours worked after accurate break deductions, and the deductions match actual punch data rather than scheduled break times.
3. Calculate Daily Hours per Employee
Prerequisites
- Break deductions applied (Step 2 completed)
- Workday start time defined for daily-overtime jurisdictions
Sum net hours worked per calendar day for each employee and flag any day exceeding the applicable daily overtime threshold. In daily-overtime states like California, every workday with net hours over 8 generates overtime hours at 1.5x, and hours over 12 generate double-time hours at 2x.
Define "workday" consistently. Under California law, a workday is any consecutive 24-hour period beginning at the same time each calendar day. If you have not defined a workday start time, the default is midnight. Once defined, the workday start time must remain consistent.
For employees in states without daily overtime, this step still produces a useful output: the daily hour total feeds into the weekly accumulation in Step 5 and the schedule reconciliation in Step 7. Calculate daily hours for all non-exempt employees regardless of state.
Expected outcome: Each employee has a net daily hour total for every day in the workweek, with daily overtime hours flagged for employees in daily-overtime states.
4. Identify Midnight-Spanning Shifts
Prerequisites
- Daily hours calculated (Step 3 completed)
- Organizational policy on midnight-shift hour assignment documented
For shifts that cross midnight, assign all hours to the workday on which the shift began unless your state law or company policy requires otherwise. Splitting hours across two calendar days inflates daily hour counts and can incorrectly trigger or suppress daily overtime.
Example: An employee starts a shift at 10:00 PM on Tuesday and ends at 6:30 AM on Wednesday, working 8 net hours after a 30-minute break deduction. If these hours are assigned entirely to Tuesday's workday, the employee has 8 hours for Tuesday and zero for Wednesday (from this shift). If the hours are split at midnight, Tuesday shows 2 hours and Wednesday shows 6 hours, neither of which triggers daily overtime in California. The split approach understates Tuesday and could mask overtime on a day when the employee also worked a daytime shift.
Document your midnight-shift assignment rule in writing. This rule should be configured in the platform and applied automatically. The system should not require manual intervention for overnight shifts every pay period.
Expected outcome: All midnight-spanning shifts are assigned to a single workday per the documented rule, and no shift is inadvertently split across two calendar days.
5. Accumulate Weekly Hours in Workweek Order
Prerequisites
- Midnight-spanning shifts resolved (Step 4 completed)
- Daily overtime hours flagged where applicable (Step 3)
Add daily net hours in chronological order across the 7-day workweek, flagging the specific hour at which the employee crosses 40 (or the applicable weekly threshold). The chronological accumulation matters because it identifies exactly which shift and which day produced the overtime crossover point.
This accumulation should account for hours already coded as daily overtime. Those hours count toward the 40-hour weekly total but have already been assigned a premium rate. Only straight-time hours above 40 convert to weekly overtime.
If the employee works in a state with no daily overtime, all hours are straight time until the 40-hour weekly threshold is crossed. The chronological accumulation still matters because it identifies the crossover shift, which determines what rate the employee was earning when they entered overtime.
Expected outcome: A chronological weekly accumulation showing the exact hour at which each employee crosses the 40-hour threshold, with daily overtime hours accounted for and not double-counted.
6. Bucket Hours into Straight-Time and Overtime Segments
Prerequisites
- Weekly accumulation completed (Step 5)
- Rate codes from Procedure 2 available
Label each hour block for every employee: straight time (ST), daily overtime (DOT), weekly overtime (WOT), or double time (DT). Use the rate codes established in Procedure 2. EasyClocking by WorkEasy Software's shift-mapping engine applies break deductions, midnight-shift rules and threshold bucketing automatically, producing a payroll-ready hour map without manual spreadsheet reconciliation.
The bucketed hour map is the primary input for payroll rate application. Each hour block should carry not just the rate code but also the rule citation (federal weekly, state daily, state double-time) and the shift or day that generated it. This traceability is essential for the audit documentation package in Procedure 5.
Review the bucketed map for logical consistency before passing it downstream. No employee should have weekly overtime hours that overlap with daily overtime hours for the same clock time. No employee should have double-time hours in a state without a double-time statute. Flag and resolve any inconsistencies before proceeding.
Expected outcome: Every hour worked by every non-exempt employee is labeled with the correct pay category (ST, DOT, WOT or DT), with rule citations attached and no double-counting.
7. Reconcile Against Scheduled Hours
Prerequisites
- Bucketed hour map completed (Step 6)
- Scheduled shift definitions loaded in the system
Compare the bucketed actuals to each employee's scheduled shift to flag anomalies before passing to payroll. Common anomalies include unauthorized overtime (hours worked beyond the schedule without prior approval), missed punches that produced artificially long or short shifts, and schedule-to-actual variances exceeding your organization's tolerance threshold.
This reconciliation is not about denying employees pay for hours actually worked. Under FLSA, employers must pay for all hours they knew or should have known the employee worked, even if those hours were not authorized. The reconciliation identifies where actual hours diverged from the plan so managers can address scheduling issues going forward and so payroll processes the correct amounts.
Document any variance that required a correction. If a missed punch was reconstructed, note who approved the reconstruction and on what basis. If unauthorized overtime was worked, note that the employee will be paid but that the scheduling issue has been flagged for management follow-up.
Expected outcome: A reconciled hour map where every variance between scheduled and actual hours is documented, corrected if needed and flagged for management review. The map is payroll-ready.

Download the procedure above

How to Calculate Overtime Pay for Employees with Multiple Pay Rates

advanced · Variable per employee per workweek

This procedure computes the FLSA-compliant blended (weighted average) regular rate of pay when a non-exempt employee works at two or more rates in a single workweek. It is executed by a payroll administrator during pay period close and produces a defensible regular-rate calculation that correctly sets the overtime premium base.

1. List All Compensation Earned in the Workweek
Prerequisites
- All rate codes and hours worked at each rate for the workweek (from Procedure 3)
- Confirmation that the employee is non-exempt and worked overtime hours in the workweek
- Any non-discretionary bonuses, shift differentials or incentive pay earned in the workweek
Compile every form of compensation the employee earned during the workweek that must be included in the FLSA regular rate. This includes base wages at each hourly rate, shift differentials, non-discretionary bonuses (such as production bonuses and attendance bonuses) and any other qualifying compensation.
Exclude items that FLSA specifically permits to be excluded from the regular rate: discretionary bonuses (where the employer retains discretion over both the fact and amount of payment), gifts, vacation pay for time not worked and certain benefit contributions. When in doubt about whether a payment qualifies for exclusion, consult the DOL's regulations at 29 CFR Part 778.
For employees who work different jobs at different rates within the same workweek, such as a warehouse worker who also drives a forklift at a higher rate, list each rate and the hours worked at that rate separately. This separation is the foundation of the blended calculation in the next steps.
Expected outcome: A complete list of all qualifying compensation components for the workweek, with hours at each rate and bonus amounts itemized separately.
2. Calculate Total Straight-Time Compensation
Prerequisites
- Compensation components listed (Step 1 completed)
Multiply hours worked at each rate by that rate and sum all amounts, including differentials and non-discretionary bonuses. This total represents the employee's straight-time earnings for every hour worked in the workweek, before any overtime premium is applied.
Example structure (do not use these specific numbers as verified figures; they illustrate the arithmetic pattern): if an employee works some hours at one rate and other hours at a different rate, plus earns a production bonus, sum all three amounts. The total is the straight-time compensation base.
This calculation assumes the employee has been paid at the applicable straight-time rate for every hour, including hours that will ultimately be overtime hours. The overtime premium calculated in Step 4 is the additional half-time owed on top of the straight-time rate, not the full 1.5x rate. This is the FLSA's "half-time" premium method for blended rates.
Expected outcome: A single total straight-time compensation figure for the workweek that includes all qualifying pay at each applicable rate and all non-discretionary bonuses.
3. Divide by Total Hours Worked to Get the Regular Rate
Prerequisites
- Total straight-time compensation calculated (Step 2 completed)
- Total hours worked in the workweek confirmed
Divide total straight-time compensation by total hours worked in the workweek. The result is the FLSA regular rate of pay. This rate must be at least the applicable minimum wage (federal or state, whichever is higher). If the calculated regular rate falls below minimum wage, you have a minimum-wage compliance issue that must be resolved before proceeding.
The regular rate is a per-workweek calculation. It cannot be averaged across multiple workweeks or across a pay period. Even within a biweekly pay period, each workweek gets its own regular rate calculation if the employee worked at multiple rates or earned a non-discretionary bonus.
Record the regular rate to at least four decimal places to avoid rounding errors that compound across overtime hours. Document the inputs (total compensation and total hours) alongside the result so the calculation can be audited and reproduced later.
Expected outcome: A documented regular rate of pay for the workweek, calculated to at least four decimal places, that meets or exceeds the applicable minimum wage.
4. Calculate the Overtime Premium
Prerequisites
- Regular rate calculated (Step 3 completed)
- Overtime hour count confirmed (from Procedure 3)
Multiply the regular rate by 0.5 (the premium portion of time-and-a-half) and then by the number of overtime hours. The employee has already been paid straight time for those overtime hours in Step 2, so only the additional half-time premium is owed.
If the employee works in a state with double-time requirements, the premium for double-time hours is the full regular rate (1.0x the regular rate as premium, on top of the straight-time already paid), not 0.5x. Calculate 1.5x and 2x overtime premiums separately and sum them.
This is the step where errors are most costly and most common. A payroll administrator who applies a flat 1.5x of the employee's base hourly rate instead of 1.5x of the blended regular rate underpays overtime whenever the employee earned a bonus or worked at multiple rates. The underpayment creates back-pay liability under FLSA.
Expected outcome: A calculated overtime premium amount that reflects the blended regular rate, with separate premium amounts for 1.5x and 2x hours where applicable.
5. Add the Overtime Premium to Total Straight-Time Compensation
Prerequisites
- Overtime premium calculated (Step 4 completed)
Sum the total straight-time compensation from Step 2 and the overtime premium from Step 4. The result is the employee's total gross pay for the workweek, compliant with FLSA's weighted-average method.
Compare this gross pay figure to what the employee would have earned if you had applied 1.5x to the base hourly rate alone (without blending). The difference is the additional amount owed because of the blended regular rate. This comparison is a useful sanity check; if the blended method produces a lower gross pay than the simple method, something is wrong in the calculation.
Enter the total gross pay into your payroll system as the validated amount for the workweek. If your system supports blended-rate automation, verify that the system's output matches your manual calculation for at least the first few pay periods after configuration.
Expected outcome: A total gross pay figure for the workweek that correctly includes the blended regular rate overtime premium, validated against a comparison calculation.
6. Document the Regular-Rate Calculation
Prerequisites
- Gross pay validated (Step 5 completed)
Record the inputs (hours at each rate, bonus amounts, total hours) and the resulting regular rate in the payroll system for audit traceability. This record is a required component of the audit documentation package described in Procedure 5.
The documentation should be detailed enough that a third party can reproduce the calculation from the record alone, without interviewing anyone or requesting additional data. Include the employee name and ID, the workweek dates, each rate and the hours worked at that rate, each non-discretionary bonus included, the total straight-time compensation, the total hours worked, the regular rate, the overtime premium and the total gross pay.
Store this record alongside the shift-level hour map from Procedure 3 and the rate-assignment log from Procedure 2. Together, these three documents form the complete overtime calculation chain from raw time punches to final pay.
Expected outcome: A complete, retrievable calculation record for the workweek that a third party can use to reproduce the blended regular rate and overtime premium without additional information.

Download the procedure above

How to Prepare an Overtime Audit Documentation Package

advanced · Variable based on scope of audit and record volume

This procedure assembles the records, calculations and rule citations a payroll team needs to respond to a Department of Labor investigation or an employee wage dispute involving overtime pay. It is executed by an HR compliance officer or payroll manager when an audit is initiated or as a proactive quarterly review and produces a complete, organized documentation package.

1. Define the Audit Scope
Prerequisites
- At least 2 years of retained payroll records (FLSA requires 3 years for payroll records, 2 years for time records)
- Shift-level hour maps and rate-assignment records from Procedures 3 and 4 for all periods under review
- Written overtime policy and workweek definition on file
- Employee classification records (exempt vs. non-exempt) with supporting job-duty documentation
Confirm the time period, employee population and specific overtime questions under review. If the audit is triggered by a DOL investigation, the scope will be defined in the investigator's initial request. If it is a proactive internal review, define the scope yourself: select a representative sample of employees, a recent quarter and the specific overtime rules you want to verify.
Scope discipline matters. Producing records beyond what is requested in a DOL investigation can expose issues the investigator had not identified. Producing too narrow a sample in a proactive review can miss systemic errors. Consult counsel before responding to any external audit request to confirm the appropriate scope.
Document the scope decision in writing, including who made it and when. This becomes the first page of the audit package.
Expected outcome: A written scope definition specifying the time period, employee population, overtime rules under review and the person who authorized the scope.
2. Pull Payroll Records for the Scope Period
Prerequisites
- Audit scope defined (Step 1 completed)
- Access to payroll system export functionality
Export gross pay, overtime hours, overtime premiums and rate codes for every non-exempt employee in scope for every workweek in the period. These records must show, at minimum, the employee's name and identifying number, total hours worked each workweek, total straight-time earnings, total overtime earnings, deductions and net pay.
FLSA requires employers to retain payroll records for three years. If your records for any portion of the audit period are incomplete, document the gap and the reason. A gap in records shifts the burden of proof to the employer in a wage dispute; the DOL will rely on the employee's estimate of hours worked if the employer cannot produce records.
Verify that the exported records match the payroll system's internal data. Export errors, field-mapping issues and date-range mismatches are common. Spot-check at least a few employees' records against the payroll system before including them in the package.
Expected outcome: A complete export of payroll records for every in-scope employee and workweek, verified against the payroll system and free of export errors.
3. Pull Corresponding Time Records
Prerequisites
- Payroll records pulled (Step 2 completed)
- Access to time records in the time tracking system
Retrieve the approved, timestamped time records (punches or attestations) that support the payroll figures. These are the primary evidence of hours worked and are the records a DOL investigator will compare against payroll output to verify that overtime was calculated correctly.
Time records must show the exact time each employee started and ended work each day, along with any break periods. EasyClocking by WorkEasy Software's compliance export feature generates a pre-indexed set of time records organized by employee and pay period, reducing the manual assembly effort.
Match each time record to the corresponding payroll record by employee and workweek. If any time record is missing or does not match the payroll output, flag it as a discrepancy and investigate before including it in the package. An unexplained discrepancy between time records and payroll output is the most common finding in a DOL overtime audit.
Expected outcome: A matched set of time records and payroll records for every in-scope employee, with discrepancies identified and documented.
4. Reconstruct the Overtime Calculation for Flagged Pay Periods
Prerequisites
- Time records and payroll records pulled and matched (Steps 2 and 3)
- Procedures 3 and 4 methodology available for re-execution
For any period where overtime pay is questioned, re-run the Procedure 3 (shift mapping) and Procedure 4 (blended rate) calculations using the original time data to confirm the calculation is reproducible and correct. This reconstruction proves that the payroll output is not arbitrary; it follows a documented, repeatable methodology.
Compare the reconstructed result to the actual payroll output. If they match, include both in the package as evidence of accuracy. If they do not match, investigate the discrepancy. Common causes include mid-period rate changes that were not reflected in the original calculation, bonuses that were excluded from the regular rate when they should have been included, or break deductions that were applied incorrectly.
Document every reconstruction, including the inputs used, the calculation steps followed and the result. A reconstruction that produces a different answer than the original payroll is a finding, not a failure; it means the original calculation can be corrected and the correction documented.
Expected outcome: A documented reconstruction of the overtime calculation for every flagged pay period, with a match-or-discrepancy finding for each.
5. Compile the Workweek-Boundary Documentation
Prerequisites
- Workweek boundary configured in the system (Procedure 1, Step 2)
Produce written evidence of the fixed workweek start day and time in effect during the audit period. This is frequently the first document a DOL investigator requests because the workweek boundary determines when overtime accrual begins and resets.
Acceptable evidence includes the system configuration showing the workweek start day, the written company policy defining the workweek, employee handbook language referencing the workweek and any historical change records showing when the boundary was modified. If the boundary changed during the audit period, document the old boundary, the new boundary and the effective date of the change.
An undocumented or inconsistently applied workweek definition is one of the most common DOL findings in overtime audits. If your current documentation is weak, strengthen it now even if no audit is pending; it costs nothing to document and the cost of not documenting is significant.
Expected outcome: Written, timestamped evidence of the workweek boundary in effect during the audit period, including any changes and their effective dates.
6. Assemble Employee Classification Records
Prerequisites
- Employee roster with exempt/non-exempt status (Procedure 1, Step 1)
- Job descriptions and duty records available in HR system
Pull job descriptions, duty checklists and salary records for any employee whose exempt status may be questioned during the audit. Misclassification is a frequent DOL focus area; if an employee classified as exempt does not meet the duties test and salary-level threshold, all hours worked over 40 become retroactive overtime liability.
For each employee in scope, include the written job description, the actual duties performed (which may differ from the job description), the salary or hourly rate and the specific FLSA exemption category applied (executive, administrative, professional, computer, outside sales). If no exemption category was documented at the time of classification, note that gap.
This step applies even to employees who were correctly classified. Producing the classification documentation proactively demonstrates that the organization has a systematic approach to classification, not an ad hoc one.
Expected outcome: A classification record for each in-scope employee showing job title, job description, actual duties, compensation and the FLSA exemption category applied.
7. Prepare a Calculation Narrative
Prerequisites
- Reconstructed calculations completed (Step 4)
- Workweek-boundary documentation compiled (Step 5)
Write a plain-language explanation of how overtime was calculated for the audit period. This narrative is not a legal brief; it is a walkthrough that a DOL investigator or an arbitrator can follow from time records to payroll output without specialized knowledge of your payroll system.
The narrative should cover: which overtime thresholds applied (federal weekly, state daily, state double-time), which rate method was used (straight 1.5x for single-rate employees, blended regular rate for multi-rate employees), how breaks were deducted, how midnight-spanning shifts were assigned and how the workweek boundary was applied. Reference the specific procedures (P1 through P4) and the system configurations that produced the calculations.
Keep the narrative concise. A strong calculation narrative is typically a few pages that walk through the methodology once and then reference the supporting records for individual employee calculations. It is not a line-by-line recalculation of every employee's pay.
Expected outcome: A plain-language narrative explaining the overtime calculation methodology, referencing the system configuration, the procedures followed and the supporting records.
8. Organize and Index the Package
Prerequisites
- All preceding steps (1 through 7) completed
- Secure storage location identified for the completed package
Compile all documents into a structured package with a cover index, organized by employee and pay period, so any record can be located within minutes of a request. The index should list every document type (payroll records, time records, classification records, workweek-boundary evidence, calculation reconstructions, calculation narrative) and the employees and pay periods each document covers.
EasyClocking by WorkEasy Software's compliance export feature generates a pre-indexed audit package containing payroll records, time records, rate-assignment logs and workweek-boundary documentation formatted for DOL response or internal wage-dispute resolution. If you are assembling the package manually, follow the same structure: one section per document type, within each section organized by employee and then by workweek.
Store the completed package in a secure, accessible location. If the audit is external, confirm with counsel the appropriate delivery method and format. If the audit is an internal proactive review, store the package as a baseline for comparison against the next quarterly review.
Expected outcome: A complete, indexed audit documentation package containing payroll records, time records, workweek-boundary evidence, classification records, calculation reconstructions and a calculation narrative, sufficient to respond to a DOL investigation or resolve an employee wage dispute without additional data gathering.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Identify and Configure FLSA Overtime Triggers in Your Timekeeping System

1. Audit Employee Classifications

2. Define the Workweek Boundary

3. Enter the Federal Weekly Threshold

4. Layer State Daily Thresholds

5. Set the 1.5x Multiplier as the Default Overtime Rate

6. Configure the 2x (Double-Time) Trigger Where Applicable

7. Run a Test Pay Period with Synthetic Data

How to Determine Which Overtime Rate Applies (1.5x vs. 2x)

1. Identify the Employee's Work State

2. Check for Daily Overtime Eligibility

3. Check for Double-Time Eligibility

4. Calculate Weekly Overtime Hours

5. Assign Rate Codes to Each Hour Block

6. Document the Rate-Assignment Rationale

How to Map Shift Hours to Daily and Weekly Overtime Thresholds

1. Pull Approved Time Records

2. Apply Break and Meal-Period Deductions

3. Calculate Daily Hours per Employee

4. Identify Midnight-Spanning Shifts

5. Accumulate Weekly Hours in Workweek Order

6. Bucket Hours into Straight-Time and Overtime Segments

7. Reconcile Against Scheduled Hours

How to Calculate Overtime Pay for Employees with Multiple Pay Rates

1. List All Compensation Earned in the Workweek

2. Calculate Total Straight-Time Compensation

3. Divide by Total Hours Worked to Get the Regular Rate

4. Calculate the Overtime Premium

5. Add the Overtime Premium to Total Straight-Time Compensation

6. Document the Regular-Rate Calculation

How to Prepare an Overtime Audit Documentation Package

1. Define the Audit Scope

2. Pull Payroll Records for the Scope Period

3. Pull Corresponding Time Records

4. Reconstruct the Overtime Calculation for Flagged Pay Periods

5. Compile the Workweek-Boundary Documentation

6. Assemble Employee Classification Records

7. Prepare a Calculation Narrative

8. Organize and Index the Package

How These Procedures Connect

Next steps