How to Automate Overtime and Holiday/PTO Pay Calculations | EasyClocking by WorkEasy Software

How to Configure Overtime Threshold Rules by Jurisdiction

intermediate · 4 hours

This procedure establishes the daily and weekly hour thresholds that trigger overtime pay in a payroll system. It is executed by a payroll administrator during initial system setup or when a new jurisdiction is added, and it produces a validated ruleset that automatically flags overtime-eligible hours. Use this procedure before configuring any premium pay stacking.

1. Identify All Active Jurisdictions
Prerequisites
- List of all jurisdictions where employees work (state, federal, local)
- Admin access to the payroll rule-engine configuration panel
Compile a complete list of every state and locality where active employees are paid. Pull this data from your HR system's employee records, filtering by work location rather than home address. Flag California separately because it requires daily overtime rules in addition to the federal weekly threshold.
If your organization operates on construction job sites, warehouse locations, or fleet routes that cross state lines, include every state where work is physically performed, not just states where you have a registered office. For staffing agencies placing workers at client sites, the client's work location determines the applicable jurisdiction.
Record each jurisdiction in a spreadsheet or directly in the platform's jurisdiction settings. Include the jurisdiction name, applicable statute reference, and the date of last statutory update. This list becomes the foundation for every threshold, rate, and audit rule configured in subsequent steps and procedures.
Expected outcome: A documented, complete list of every jurisdiction where employees perform work, with California and any other daily-OT states flagged for special configuration.
2. Map Statutory Overtime Thresholds for Each Jurisdiction
Prerequisites
- Completed jurisdiction list from Step 1
- Current FLSA and applicable state overtime statutes (CA Labor Code §510 for California)
For each jurisdiction identified in Step 1, record the daily overtime threshold, weekly overtime threshold, and double-time threshold where applicable. Under FLSA, the federal weekly threshold is 40 hours per workweek. California Labor Code §510 adds daily thresholds: 1.5× for hours beyond 8 in a single day and 2.0× for hours beyond 12 in a single day.
California also imposes a 7th-consecutive-day rule: all hours on the 7th consecutive day in a workweek earn at least 1.5×, and hours beyond 8 on that day earn 2.0×. Record this as a separate trigger condition so it is not missed during configuration.
Consult the applicable state labor department website for each jurisdiction. Statutory thresholds change through legislation, so record the effective date and statute citation alongside each threshold. Store this reference table in your compliance document repository for audit purposes.
Expected outcome: A reference table documenting daily OT, weekly OT, and double-time thresholds for every active jurisdiction, with statute citations and effective dates.
3. Enter Employer-Policy Overrides
Prerequisites
- Employer overtime policy document (any thresholds more generous than statutory minimums)
- Admin access to the payroll rule-engine configuration panel
Open the rule-engine configuration panel in EasyClocking by WorkEasy Software. For each jurisdiction, input any employer overtime thresholds that are more generous than statutory minimums. For example, if your company policy triggers overtime at 35 hours per week instead of the FLSA's 40-hour threshold, enter 35 as the policy-layer rule.
Flag every policy override as a distinct rule layer, separate from the legal-minimum layer. This separation matters for two reasons. First, auditors can verify that statutory minimums are always met regardless of policy changes. Second, if employer policy changes (through a new CBA or board decision), you can update the policy layer without touching the statutory layer.
Attach the governing document (employee handbook section, CBA article, or board resolution) to each policy override as a reference tag. This documentation is your audit trail if a wage-and-hour investigation questions why a particular threshold was applied.
Expected outcome: All employer-policy overtime overrides are entered as a separate rule layer in the system, each tagged with its governing document reference.
4. Assign Rulesets to Employee Groups
Prerequisites
- Completed jurisdiction threshold table from Step 2
- Employer-policy overrides entered from Step 3
Map each jurisdiction ruleset to the corresponding employee group or work location in EasyClocking by WorkEasy Software. The system should apply the correct overtime threshold automatically at time-entry based on where the employee works, not based on a global default.
For organizations with employees working across multiple states (common in construction, transportation, and staffing), configure location-based rule routing. An employee who works Monday through Wednesday in Nevada and Thursday through Friday in California needs Nevada's rules applied to the first three days and California's daily overtime rules applied to the last two.
Create employee groups that align with your jurisdiction assignments. A single employee can belong to multiple groups if they work in multiple jurisdictions during a pay period. Verify that each group's ruleset is the correct one by cross-referencing the group name against your jurisdiction threshold table from Step 2.
Expected outcome: Every employee group is mapped to its correct jurisdiction ruleset, and employees working in multiple states have location-based rule routing configured.
5. Set Overtime Rate Multipliers
Prerequisites
- Jurisdiction rulesets assigned to employee groups from Step 4
Configure the rate multipliers for each threshold in the jurisdiction's rate table. For standard overtime under FLSA, set the multiplier to 1.5× the regular rate of pay. For California double-time thresholds (hours beyond 12 in a day, or hours beyond 8 on the 7th consecutive day), set the multiplier to 2.0×.
Enter these multipliers at the jurisdiction level, not the employee level. Individual employee base rates will vary, but the multiplier is a function of the jurisdiction and threshold, not the individual. The system in EasyClocking by WorkEasy Software calculates the actual dollar amount by applying the multiplier to each employee's regular rate of pay at runtime.
If your employer policy provides a higher multiplier than the statutory minimum (for example, 2.0× for all overtime, not just California daily double-time), enter the policy multiplier as a separate line in the rate table and flag it as a policy override. This keeps the statutory multiplier visible for compliance verification.
Expected outcome: Rate multipliers of 1.5× and 2.0× are configured for each applicable jurisdiction and threshold, with any employer-policy multiplier overrides entered as separate, flagged line items.
6. Run a Threshold Validation Test
Prerequisites
- Rate multipliers configured from Step 5
- Access to a sandbox or test environment
Process a test time-entry batch that crosses each configured threshold. Create test entries for at least the following scenarios: an employee working 42 hours in a week (triggers FLSA weekly OT), a California employee working 9 hours in a single day (triggers CA daily OT at 1.5×), a California employee working 13 hours in a single day (triggers CA daily double-time at 2.0×), and a California employee working 7 consecutive days with 9 hours on the 7th day (triggers the 7th-day rule).
Review the system's output for each test entry. Confirm that the correct hours are flagged at the correct rate. If any test fails, trace the error to the specific rule or multiplier configuration and correct it before proceeding. Document each test result, including the input hours, expected output, and actual output.
Run these tests in a sandbox or test environment within the platform to avoid affecting live payroll data. Save the test results as part of your configuration audit trail.
Expected outcome: All test scenarios produce correct overtime flags and rate applications, with documented test results stored in the configuration audit trail.
7. Save and Version the Ruleset
Prerequisites
- Successful validation test results from Step 6
Commit the final configuration with a version timestamp in EasyClocking by WorkEasy Software. Document the statutory basis for each threshold in the audit log, including the statute citation, effective date, and the date of configuration. If your employer policy adds an override, record the policy document reference and the approval authority.
Export the complete ruleset as a configuration report and store it in your compliance document repository. This report serves two purposes: it is your proof of configuration for any future wage-and-hour audit, and it is your baseline for comparison when statutory thresholds change (which happens through legislative action, not on a predictable schedule).
Set a calendar reminder to review the ruleset at least quarterly. When a jurisdiction updates its overtime statute, update the threshold, increment the version number, and re-run the validation tests from Step 6 before activating the change in the live environment.
Expected outcome: A versioned, timestamped overtime ruleset is active in the payroll system, with a complete audit log and configuration report archived for compliance review.

Download the procedure above

How to Map Pay Codes to Overtime Eligibility

intermediate · 3 hours

This procedure classifies each pay code (regular hours, holiday pay, PTO, sick leave, weekend differentials) as either included in or excluded from the overtime calculation base. It is executed by a payroll administrator before the first pay period runs and produces a pay-code eligibility matrix that the system applies automatically. Use this procedure after Procedure 1 and before Procedure 3.

1. Export the Complete Pay-Code List
Prerequisites
- Completed jurisdiction overtime ruleset from Procedure 1
- Full list of active pay codes in the payroll system
Pull a full export of all active pay codes from your payroll system. Include regular time, PTO, sick leave, holiday, bereavement, jury duty, weekend differential, shift differential, and any premium codes specific to your organization. If you use EasyClocking by WorkEasy Software, navigate to the pay-code management section and export the list as a spreadsheet.
Verify the export is complete by comparing it against your employee handbook's pay-type definitions. Missing codes are a common source of misclassification. If a pay code exists in the handbook but not in the system, create it before proceeding. You cannot classify what the system does not recognize.
Organize the exported list into a working table with columns for: pay code name, code ID, current OT-inclusion setting (if any), intended classification, governing rule (FLSA, state statute, employer policy, or CBA), and sign-off status. This table becomes your pay-code eligibility matrix.
Expected outcome: A complete, organized table of every active pay code in the system, ready for OT-eligibility classification.
2. Classify Each Code as Hours Worked or Hours Paid but Not Worked
Prerequisites
- FLSA guidance on 'hours worked' vs. 'hours paid' distinction (29 CFR §778.200)
Apply the FLSA "hours worked" standard (29 CFR §778.200) to each pay code. Under FLSA, only hours the employee was suffered or permitted to work count toward the 40-hour weekly overtime threshold. Hours paid but not worked, such as PTO, sick leave, holiday pay for a day off, bereavement, and jury duty, do not count under the federal standard.
Walk through each code on your list and assign it to one of two categories: "hours worked" (included in OT base) or "hours paid but not worked" (excluded from OT base). Regular time, on-call time where the employee is required to remain on premises, and training time are typically "hours worked." PTO, sick leave, and holiday pay for days not worked are typically excluded.
Record the classification directly in your working table. For each code, note the specific regulatory or policy basis for the classification. This documentation is critical for defending your configuration in a wage-and-hour audit.
Expected outcome: Every pay code is classified as either 'hours worked' or 'hours paid but not worked' with a documented regulatory basis for each classification.
3. Flag Jurisdiction and Policy Exceptions
Prerequisites
- Employer policy on whether PTO/sick/holiday hours count toward the 40-hour OT threshold
- Any applicable collective bargaining agreements
Review your jurisdiction list and employer policies for any rules that override the FLSA default. Some employer policies and collective bargaining agreements require paid-not-worked hours (PTO, sick, holiday) to count toward the overtime threshold. When that is the case, the employer's more generous policy controls.
Mark each exception in your working table. For each flagged code, record: the employee group affected, the jurisdiction or policy that requires the override, and the specific provision (CBA article, handbook section, or state statute). Create a separate row or flag for each exception so the system can apply the correct logic by employee group rather than globally.
Be precise about which employee groups are affected. A single global toggle that includes PTO in the OT base for all employees will overstate overtime liability for groups that should follow the FLSA default. Configure at the group level from the start.
Expected outcome: All jurisdiction and policy exceptions are flagged in the working table, with the affected employee groups, governing rules, and specific provisions documented.
4. Enter Classifications in the Pay-Code Eligibility Matrix
Prerequisites
- Completed working table with classifications and exceptions from Steps 2 and 3
- Admin access to the pay-code eligibility matrix
Open the pay-code eligibility matrix in EasyClocking by WorkEasy Software. For each code on your working table, set the OT-inclusion toggle to "included" or "excluded." Attach the governing rule (FLSA, CA policy, employer policy, CBA) as a reference tag on each code so the classification rationale is visible to any administrator or auditor who reviews the configuration.
For codes with employee-group exceptions, create group-level override rules. The system should apply the default classification to all employees and then apply the override only to the specified groups. Verify that the override structure is hierarchical: group-level rules should take precedence over global defaults, and jurisdiction-level rules should take precedence over employer-policy defaults.
Save each classification as you enter it. Do not batch-save at the end; if the session times out or an error occurs, you lose all unsaved work.
Expected outcome: Every pay code in the system has an OT-inclusion toggle set to 'included' or 'excluded,' with reference tags and group-level overrides configured.
5. Configure PTO and Sick Leave Exclusion Logic
Prerequisites
- Classifications entered from Step 4
Set PTO and sick leave codes to "excluded from OT base" by default for FLSA compliance. This is the correct federal baseline: PTO and sick hours are paid but not worked, and they do not inflate the overtime threshold under FLSA.
Then create policy-override rules for any employee groups whose contracts require inclusion. For example, a CBA that states "all paid hours count toward weekly overtime" requires PTO and sick hours to be included in the OT base for that bargaining unit. Enter this override at the group level, not globally.
Document the reasoning for each override in the system's notes field or in your compliance repository. A misconfigured PTO/sick inclusion rule is one of the most common payroll errors in organizations with mixed policy environments. When an auditor asks why one group includes PTO in the OT base and another does not, your documentation should answer the question immediately.
Expected outcome: PTO and sick leave codes default to 'excluded from OT base,' with documented group-level overrides active for any employee groups whose contracts require inclusion.
6. Test the Matrix with a Mixed Pay-Period Scenario
Prerequisites
- PTO and sick exclusion logic configured from Step 5
- Access to a sandbox or test environment
Run a test employee through a week containing regular hours, one PTO day, and one holiday. Specifically, create a test scenario where the employee works 32 regular hours, takes 8 hours of PTO on one day, and has 8 hours of holiday pay (not worked) on another day. The total paid hours are 48, but the total hours worked are 32.
Under the FLSA default configuration, no overtime should trigger because only 32 hours were worked. If the system flags overtime, your exclusion logic is misconfigured. Trace the error to the specific pay code that is incorrectly set to "included" and correct it.
Run a second test for an employee group with a CBA override that requires PTO inclusion. The same 48-hour week should produce 8 hours of overtime (48 minus 40) for this group. If it does not, the group-level override is not applying correctly. Correct the override hierarchy and re-test before moving to the next procedure.
Expected outcome: The FLSA-default test produces zero overtime for 32 worked hours plus 16 paid-not-worked hours; the CBA-override test produces 8 hours of overtime for the same total paid hours.
7. Document the Matrix and Obtain HR Sign-Off
Prerequisites
- Successful test results from Step 6
Export the completed eligibility matrix from EasyClocking by WorkEasy Software as a configuration report. The report should show every pay code, its OT-inclusion classification, the governing rule, and any group-level overrides. Attach the policy rationale for each classification.
Route the report to your HR director or compliance lead for review and sign-off. This step is not optional. The pay-code eligibility matrix directly determines how overtime liability is calculated for every employee. A misconfigured code can quietly overstate or understate overtime for months before anyone catches it. HR sign-off creates accountability and a second pair of eyes on the configuration.
Store the signed report in your compliance document repository alongside the jurisdiction ruleset from Procedure 1. Together, these two documents form the foundation that Procedures 3 through 5 build on. Update the matrix and obtain fresh sign-off whenever a new pay code is added or employer policy changes.
Expected outcome: A signed, archived pay-code eligibility matrix is stored in the compliance repository, with HR sign-off confirming the accuracy of every classification and override.

Download the procedure above

How to Stack Holiday Premium and Overtime Rates in the Same Pay Period

advanced · 3 hours

This procedure configures the correct combined pay rate when an employee works overtime on a holiday or accumulates weekly overtime in a week that includes a holiday. It is executed by the payroll system's rate engine, configured by a payroll administrator, and produces a single blended rate line per affected employee. Use this procedure after Procedures 1 and 2 are validated.

1. Define the Holiday Premium Rate
Prerequisites
- Validated jurisdiction overtime ruleset (Procedure 1) and pay-code eligibility matrix (Procedure 2)
- Employer holiday premium policy (e.g., time-and-a-half for working the holiday)
Enter the employer's holiday work premium as a named rate code in EasyClocking by WorkEasy Software. This code must be distinct from the overtime rate code. Common holiday premiums include 1.5× base rate for hours worked on a designated holiday, though the specific multiplier is set by your employer policy or collective bargaining agreement, not by federal law.
FLSA does not require employers to pay a premium for working on holidays. Holiday premium pay is entirely a policy or CBA obligation. This distinction matters because it determines whether the premium is negotiable, and it affects how you document the rate for audit purposes. Tag the holiday premium rate code with the governing policy reference (handbook section or CBA article) so the audit trail is clear.
Create one holiday premium rate code per unique premium level. If your organization pays 1.5× for Thanksgiving but 2.0× for Christmas (per CBA terms), create two distinct codes rather than manually overriding a single code each holiday. Distinct codes reduce manual intervention and error risk.
Expected outcome: A named holiday premium rate code exists in the system for each unique premium level, tagged with the governing policy reference.
2. Establish the Rate-Stacking Rule
Prerequisites
- Clarification on whether the holiday premium is additive to OT or calculated as the higher of two rates
- Admin access to the rate-stacking configuration panel
Configure whether overtime hours worked on a holiday pay at an additive rate (holiday premium plus OT premium) or at the higher of the two rates. This is the critical policy decision in holiday/OT stacking.
Under the additive method, an employee earning a 1.5× holiday premium who also triggers 1.5× overtime would receive a combined 2.5× rate (or whatever your policy formula yields). Under the higher-of method, the employee receives whichever single rate is greater. Most CBAs specify the method; if your employer policy is silent, consult with legal counsel to establish the rule before configuring it.
Document the chosen method, the policy or CBA basis, and the approval authority in the system's configuration notes. Enter the stacking rule in the rate-stacking configuration panel of EasyClocking by WorkEasy Software. The system needs an explicit rule here because the default behavior (if unconfigured) varies by platform and can produce incorrect paychecks silently.
Expected outcome: The rate-stacking method (additive or higher-of) is configured in the system and documented with its policy basis and approval authority.
3. Set the Regular Rate of Pay Calculation
Prerequisites
- List of non-discretionary holiday bonuses and shift differentials
- Understanding of 29 CFR §778.207 regular rate requirements
Configure the system to include any non-discretionary holiday bonuses or shift differentials in the FLSA regular rate of pay before computing the overtime multiplier. Under 29 CFR §778.207, the "regular rate" for overtime purposes must include all remuneration except specific statutory exclusions (gifts, discretionary bonuses, vacation pay, and a few others).
If your organization pays a flat holiday bonus (for example, a fixed dollar amount for working Thanksgiving), that bonus is non-discretionary if employees expect it based on past practice or policy. It must be folded into the regular rate before the OT multiplier is applied. Failing to do this understates OT liability.
In EasyClocking by WorkEasy Software, map each non-discretionary bonus code to the regular-rate calculation formula. The system should automatically recalculate the regular rate for any pay period that includes a qualifying bonus and then apply the OT multiplier to the adjusted rate. Test this with a sample bonus scenario to confirm the calculation is correct before proceeding.
Expected outcome: Non-discretionary holiday bonuses are included in the FLSA regular rate of pay calculation, and the OT multiplier is applied to the correctly adjusted rate.
4. Map the Stacking Rule to Employee Groups
Prerequisites
- Rate-stacking rule configured from Step 2
Assign the configured stacking rule to each employee group in the system. Different groups may require different stacking methods. A CBA-covered group may use the additive method while non-CBA employees use the higher-of method. A group in a jurisdiction with specific stacking requirements may need a third configuration.
In EasyClocking by WorkEasy Software, navigate to the employee-group settings and attach the correct stacking rule to each group. Verify that the group assignment aligns with both the jurisdiction ruleset from Procedure 1 and the pay-code matrix from Procedure 2. Misalignment between these three layers (thresholds, eligibility, and stacking) is the root cause of most holiday/OT calculation errors.
Create a cross-reference document that shows, for each employee group: the OT threshold source, the pay-code eligibility rules, and the stacking method. This document is your configuration map and should be updated whenever any of the three layers changes.
Expected outcome: Every employee group is assigned the correct stacking rule, and a cross-reference document maps thresholds, eligibility, and stacking for each group.
5. Test a Same-Day Holiday-Plus-Overtime Scenario
Prerequisites
- Stacking rules mapped to employee groups from Step 4
- Access to a sandbox or test environment
Process a test employee who works 10 hours on a designated holiday. Confirm the system outputs the correct rates for each hour segment. Under a typical configuration: hours 1 through 8 receive the holiday premium rate, and hours 9 through 10 receive the stacked rate (holiday premium plus OT, or the higher of the two, depending on your Step 2 configuration).
Compare the system's output against a manual calculation. Multiply the employee's base rate by the expected multiplier for each hour segment and verify the totals match. If the system applies the holiday premium but not the OT stacking for hours 9 and 10, the stacking rule is not triggering correctly. Trace the issue to the stacking configuration or the threshold assignment.
Document the test input, expected output, actual output, and pass/fail status. If the test fails, correct the configuration and re-test before proceeding. Do not skip this test; same-day stacking errors are the most common source of paycheck corrections in holiday weeks.
Expected outcome: The test employee's 10-hour holiday shift produces correct pay rates for both the standard-hour and overtime-hour segments, matching the manual calculation.
6. Test a Holiday-Week Overtime Scenario
Prerequisites
- Pay-code eligibility matrix validated in Procedure 2
Process a test employee who works 32 regular hours plus receives 8 hours of holiday pay (paid, not worked) in one week. Under the FLSA default, the 8 holiday hours do not count toward the 40-hour OT threshold because they are hours paid but not worked. The employee's total hours worked are 32; no overtime should trigger.
Run a second test where the employee works 36 regular hours and receives 8 hours of holiday pay (not worked). Total paid hours are 44, but total hours worked are 36. Again, no FLSA overtime should trigger. If the system flags overtime in either test, your pay-code eligibility matrix from Procedure 2 is not excluding holiday-not-worked hours correctly.
Run a third test for an employee group whose policy requires counting paid holiday hours toward OT. The second scenario (36 worked + 8 holiday = 44 total) should produce 4 hours at the overtime rate for this group. If it does not, the group-level override is not applying. Correct and re-test.
Expected outcome: FLSA-default tests produce zero overtime when paid-not-worked holiday hours are present; policy-override tests produce the correct overtime hours for groups whose contracts require holiday hour inclusion.
7. Export the Rate-Stacking Configuration Summary
Prerequisites
- Successful test results from Steps 5 and 6
Generate a configuration report from EasyClocking by WorkEasy Software that documents every rate-stacking rule, the employee groups each rule is assigned to, the regular-rate-of-pay calculation settings, and the test results from Steps 5 and 6. This report is your audit trail for the stacking methodology.
Store the report in your compliance document repository alongside the jurisdiction ruleset (Procedure 1) and the pay-code eligibility matrix (Procedure 2). Together, these three documents constitute your complete overtime and holiday pay configuration record.
Route the report to your HR director or compliance lead for review. If any stacking method requires legal interpretation (for example, whether a CBA's "premium pay" language means additive or higher-of), flag that item for legal counsel review before the first live pay period. Unresolved interpretation questions should not be configured as assumptions; they should be resolved and documented.
Expected outcome: A complete rate-stacking configuration report is archived in the compliance repository, with HR review completed and any legal interpretation questions flagged and resolved.

Download the procedure above

How to Apply Multi-Jurisdiction Double-Time Logic for Holiday and Overtime Interactions

advanced · 4 hours

This procedure configures California daily double-time rules, 7th-consecutive-day rules, and any other jurisdiction-specific double-time mandates alongside federal overtime rules. It is executed by a payroll administrator for organizations with employees in California or other double-time jurisdictions and produces jurisdiction-correct pay rates automatically. Use this procedure when Procedure 1 reveals double-time thresholds in any active jurisdiction.

1. Activate the California Daily Overtime Layer
Prerequisites
- Completed Procedure 1 ruleset with California thresholds entered
- CA Labor Code §510 and applicable IWC Wage Order for the employee's industry
- List of employees assigned to California work locations
In the jurisdiction settings of EasyClocking by WorkEasy Software, enable the California daily overtime layer for all employees assigned to California work locations. Set the 1.5× trigger at hours beyond 8 in a single day and the 2.0× trigger at hours beyond 12 in a single day, per California Labor Code §510.
This layer operates independently of the FLSA weekly overtime threshold configured in Procedure 1. Both layers must be active simultaneously for California employees. The system should evaluate each day's hours against the CA daily threshold and each week's hours against the FLSA weekly threshold, then apply whichever produces the higher rate for each hour.
Verify that the daily OT layer applies only to employees whose work location is in California, not to employees whose home address is in California but who perform work in other states. The trigger field must be work location. Misconfiguring this based on home address will apply CA daily OT to employees who are not entitled to it, overstating payroll costs.
Expected outcome: The CA daily overtime layer is active for all California-work-location employees, with 1.5× at >8 hours/day and 2.0× at >12 hours/day, triggered by work location.
2. Configure the 7th-Consecutive-Day Rule
Prerequisites
- California daily OT layer activated from Step 1
- Correct workweek definition entered in the system
Set a separate trigger condition in EasyClocking by WorkEasy Software that applies 1.5× to the first 8 hours and 2.0× to all hours beyond 8 on the 7th consecutive day in a workweek for California employees. This rule exists independently of the daily overtime thresholds and must be configured as its own trigger.
The 7th-consecutive-day rule resets at the start of the employer's defined workweek. If your workweek starts on Monday, the 7th consecutive day is Sunday. If your workweek starts on Sunday, the 7th consecutive day is Saturday. Verify that the workweek definition in your system matches the definition in your employer policy. An incorrect workweek start date will cause the 7th-day trigger to fire on the wrong day.
Test this by creating a time-entry batch for a California employee who works all 7 days in a workweek, with 9 hours on the 7th day. The system should apply 1.5× to hours 1 through 8 and 2.0× to hour 9 on that 7th day. If the 7th-day rule does not fire, check the workweek definition and the employee's work-location assignment.
Expected outcome: The 7th-consecutive-day trigger is active for CA employees, applying 1.5× to the first 8 hours and 2.0× beyond 8 on the 7th day, resetting correctly at the workweek boundary.
3. Layer California Daily Overtime Over Weekly FLSA Overtime
Prerequisites
- FLSA weekly OT threshold from Procedure 1
- CA daily OT layer from Step 1
Configure the system to apply whichever rate is higher on a given day: California daily OT or FLSA weekly OT. This "greater of" logic ensures California employees always receive the greater statutory protection without being double-counted.
For example, a California employee who works five 9-hour days (45 total hours) earns CA daily OT (1.5×) on the 9th hour each day, which is 5 hours at 1.5×. Under FLSA weekly OT alone, the employee would earn 5 hours at 1.5× (45 minus 40). The result is the same in this scenario, but the system must not pay both; it must apply the greater protection once.
In a different scenario, a California employee works four 12-hour days (48 total hours). CA daily OT produces 16 hours at 1.5× (4 days × 4 OT hours). FLSA weekly OT produces 8 hours at 1.5× (48 minus 40). The CA daily rule is more generous, so the system applies the CA daily rate. Configure EasyClocking by WorkEasy Software to compare the two calculations and select the higher total for the employee.
Expected outcome: The system applies the greater of CA daily OT or FLSA weekly OT for each California employee, preventing double-counting while ensuring the employee receives the higher statutory protection.
4. Handle Holiday Hours Under California Rules
Prerequisites
- Holiday premium stacking rules from Procedure 3
- CA daily OT layer active from Step 1
Configure the system to treat hours worked on a California-recognized holiday as regular worked hours for daily OT purposes. California does not mandate holiday pay or a holiday premium rate. However, California's daily overtime rules apply to hours worked on holidays the same as on any other day.
This means a California employee who works 13 hours on a holiday earns: hours 1 through 8 at the regular rate (plus any employer holiday premium if your policy provides one), hours 9 through 12 at 1.5× (CA daily OT), and hour 13 at 2.0× (CA daily double-time). If your employer also provides a holiday premium, the stacking rules from Procedure 3 apply on top of the CA daily OT.
Verify in EasyClocking by WorkEasy Software that the holiday designation does not suppress or override the CA daily OT trigger. Some systems treat holiday hours differently by default, which can cause the daily OT calculation to skip holiday-marked days. Test explicitly to confirm.
Expected outcome: Hours worked on California holidays are subject to CA daily OT rules, and the holiday designation does not suppress or override the daily OT trigger in the system.
5. Set Up Multi-State Employee Routing
Prerequisites
- Jurisdiction rulesets from Procedure 1 for all active states
- Work-location tagging configured in the time-entry workflow
For employees who work in both California and other states in the same pay period, configure a work-location-based rule router in EasyClocking by WorkEasy Software. The router must apply the correct jurisdiction's overtime rules to each day's hours based on where the work was performed that day.
This is common in construction (crews moving between CA and NV job sites), transportation (drivers crossing state lines), and staffing (agency workers placed at different client locations). Each day's time entry must carry a work-location tag that the rule router reads to determine which jurisdiction's rules apply.
If work-location tagging is not already part of your time-entry workflow, configure it now. Mobile clock-ins through the platform can use GPS geofencing to auto-assign the work location. For job-site-based industries, tie the location tag to the job or project code. For employees who self-report location, add a required field to the clock-in screen. Without accurate location data on every time entry, multi-state routing cannot produce correct results.
Expected outcome: Multi-state employees have location-based rule routing active, and each day's hours are processed under the correct jurisdiction's overtime rules based on where work was performed.
6. Test a California Holiday-Week Double-Time Scenario
Prerequisites
- All Steps 1 through 5 configured
- Procedure 3 stacking rules validated
Process a test California employee who works 13 hours on a designated holiday. Confirm the system outputs the following rate breakdown: hours 1 through 8 at the holiday premium rate (if employer policy provides one), hours 9 through 12 at 1.5× (CA daily OT, stacked with holiday premium per Procedure 3 stacking rule), and hour 13 at 2.0× (CA daily double-time, stacked with holiday premium per Procedure 3 stacking rule).
Compare every line item against a manual calculation. If the holiday premium is 1.5× base and the stacking rule is additive, the rate for hours 9 through 12 should be the holiday premium plus the OT premium applied to the regular rate. Hour 13 should reflect the holiday premium plus the double-time premium.
If any segment is incorrect, trace the error to the specific layer: CA daily OT threshold (Step 1), holiday premium rate (Procedure 3, Step 1), or stacking rule (Procedure 3, Step 2). Correct and re-test. Document the test results and archive them.
Expected outcome: The 13-hour California holiday shift produces correct rates for each segment (regular/premium, 1.5× OT, 2.0× double-time), with stacking applied per the configured rule.
7. Validate the 7th-Consecutive-Day Scenario
Prerequisites
- 7th-consecutive-day rule configured from Step 2
- Correct workweek start date verified
Process a test California employee who works 8 consecutive calendar days, with 9 hours on day 7. Confirm the system applies 1.5× to hours 1 through 8 on day 7 and 2.0× to hour 9 on day 7. Then confirm the system resets on day 8 (the start of a new workweek) and applies the standard daily OT rules, not the 7th-day rules.
This test validates two things: that the 7th-day trigger fires correctly, and that it resets at the workweek boundary. A system that does not reset will apply 7th-day rates on day 8 and beyond, overstating payroll costs. A system that does not fire at all will understate payroll and create DLSE exposure.
Run one additional test with a California employee working 7 consecutive days where day 7 falls on a designated holiday. Confirm that both the 7th-day OT rules and the holiday premium stacking rules apply simultaneously. Archive all test results in EasyClocking by WorkEasy Software's compliance repository alongside the Procedure 3 stacking report.
Expected outcome: The 7th-day trigger fires correctly and resets at the workweek boundary; a 7th-day-plus-holiday test produces correct stacked rates for all hour segments.

Download the procedure above

How to Audit Pay Period Outputs for Overtime and Holiday/PTO Compliance

intermediate · 2 hours

This procedure verifies that every paycheck in a completed pay period correctly reflects overtime thresholds, holiday premium rates, PTO exclusions, and double-time rules before payroll is finalized. It is executed by a payroll administrator or compliance reviewer at the close of each pay period and produces an audit-ready exception report. Use this procedure before every payroll submission.

1. Run the Pre-Submission Audit Report
Prerequisites
- Completed pay period time-entry data (all hours submitted and approved)
- Validated rulesets from Procedures 1 through 4 active in the system
- Audit report template with exception flagging enabled
In EasyClocking by WorkEasy Software, generate the pay period audit report with exception flags enabled. Configure the report to flag at minimum: overtime threshold breaches (hours exceeding the configured daily or weekly threshold), holiday premium mismatches (employees who worked on a designated holiday but did not receive the premium rate), and PTO/sick OT-inclusion anomalies (paid-not-worked hours that were incorrectly included in or excluded from the OT base).
Run the report for all employees in the pay period, not just those you suspect have exceptions. Silent errors (correct-looking paychecks with miscalculated rates) are the most dangerous because they accumulate over multiple pay periods before discovery. A full-population scan catches these.
Export the report to a reviewable format (spreadsheet or PDF). If the report contains more than a few dozen flags, sort by exception type first to identify systemic configuration issues before reviewing individual cases.
Expected outcome: A complete audit report is generated covering all employees in the pay period, with exception flags active for OT thresholds, holiday premiums, and PTO/sick OT-inclusion anomalies.
2. Review Overtime Exception Flags
Prerequisites
- Audit report from Step 1
For each flagged employee, confirm the system applied the correct overtime threshold (daily vs. weekly, FLSA vs. California) and the correct multiplier (1.5× or 2.0×). Cross-reference the employee's work location against their jurisdiction ruleset assignment from Procedure 1.
Common flag types include: an employee who exceeded 40 weekly hours but was not assigned to an OT-eligible employee group (configuration error), an employee who triggered CA daily OT but is not assigned to a California work location (possible location-tagging error), and an employee whose OT hours appear correct but whose multiplier does not match the configured rate (rate-table error).
For each flag, record whether the exception is a data-entry error (wrong hours submitted), a configuration error (wrong ruleset assigned), or a legitimate edge case (correct hours and rules, but the combination is unusual). Document the determination and the resolution action for each.
Expected outcome: Every overtime exception flag is reviewed, classified as data error, configuration error, or legitimate edge case, and documented with a resolution action.
3. Verify Holiday Premium Applications
Prerequisites
- List of designated holidays for the pay period
Cross-reference the list of designated holidays for the pay period against employees who worked on those dates. Confirm that each employee who worked on a designated holiday received the correct premium rate as configured in Procedure 3. Also confirm that employees who did not work on the holiday but received paid holiday hours have those hours correctly classified as "paid but not worked" per the Procedure 2 matrix.
Look specifically for two common errors. First, employees who worked on a holiday but did not receive the premium rate (the holiday designation was not applied to their time entry). Second, employees whose paid-not-worked holiday hours were incorrectly counted toward the OT base, inflating their overtime.
For shift workers whose schedules cross midnight, verify that the system correctly assigns the holiday designation based on the day the shift started (or ended, depending on your employer policy). Midnight-crossing shifts are a frequent source of holiday premium errors in manufacturing, warehousing, and transportation environments.
Expected outcome: Every employee who worked on a holiday received the correct premium rate, and paid-not-worked holiday hours are correctly excluded from the OT base for FLSA-default employees.
4. Check PTO and Sick Leave OT Exclusions
Prerequisites
- Pay-code eligibility matrix from Procedure 2
- List of approved PTO and sick leave for the period
Confirm that PTO and sick hours are excluded from the OT base for FLSA-default employees and included for any employee groups whose policy requires it, per the Procedure 2 matrix. This check catches the most financially significant error in holiday/OT payroll: PTO hours inflating the overtime base.
Review every employee in the pay period who had both PTO or sick hours and overtime in the same week. For each, verify the system calculated OT based on the correct set of hours (worked-only for FLSA default, all-paid for policy-override groups). If the system included PTO in the OT base for an FLSA-default employee, the paycheck will overstate overtime.
This error is easy to miss because the paycheck total looks reasonable. An employee paid for 44 hours with 8 PTO hours might appear to have 4 hours of legitimate OT when in fact they worked only 36 hours. The difference is real money on every affected paycheck, every pay period, for every misconfigured employee.
Expected outcome: PTO and sick hours are confirmed excluded from the OT base for FLSA-default employees and correctly included for policy-override groups, with any discrepancies flagged for correction.
5. Validate Double-Time Triggers for California Employees
Prerequisites
- California double-time rules from Procedure 4 active in the system
For each California employee in the pay period, confirm that daily hours exceeding 12 were rated at 2.0× and that the 7th-consecutive-day rule fired correctly where applicable. This validation step is specific to California and any other active double-time jurisdictions identified in Procedure 1.
Pull the CA employee subset from your audit report. For each employee, review every day where total hours exceeded 8. Verify the system applied 1.5× for hours 9 through 12 and 2.0× for hours beyond 12. For any employee who worked 7 consecutive days, verify the 7th-day trigger applied 1.5× to hours 1 through 8 and 2.0× beyond 8 on that day.
If any CA employee's double-time rate is missing or incorrect, trace the issue to the jurisdiction assignment (is the employee assigned to a CA work location?), the daily OT layer (is it active?), or the 7th-day trigger (is the workweek start date correct?). Correct and recalculate before proceeding to submission.
Expected outcome: All California employees' daily double-time and 7th-consecutive-day rates are verified as correct, with any discrepancies traced to root cause and corrected.
6. Resolve Exceptions Before Submission
Prerequisites
- Exception classifications from Steps 2 through 5
For each exception identified in Steps 2 through 5, determine the correct resolution category and act on it. Data-entry errors (wrong hours, missing location tags, incorrect PTO coding) should be corrected at source by the employee's manager and resubmitted through the approval workflow. Configuration errors (wrong ruleset, missing stacking rule, incorrect pay-code toggle) should be escalated to the administrator responsible for Procedures 1 through 4 for correction and re-testing.
Legitimate edge cases (an employee who voluntarily worked overtime on a holiday under a CBA provision, a multi-state employee whose work locations shifted mid-week) should be documented with a written justification, approved by a supervisor, and tagged as a manual override in the system. Do not suppress the flag; approve it with documentation.
Reprocess the audit report after all corrections are applied. The clean report should show zero unresolved exceptions. If new exceptions appear after corrections (cascading recalculations can shift other employees' totals), review and resolve those before finalizing.
Expected outcome: All exceptions are resolved through source correction, configuration fix, or documented manual override, and a clean re-run of the audit report shows zero unresolved flags.
7. Export the Finalized Audit Report
Prerequisites
- Zero unresolved exceptions from Step 6
Generate and archive the clean audit report from EasyClocking by WorkEasy Software as the compliance record for the pay period. The report must include: the date and time of the final run, the total employee count reviewed, the exception count at initial run, the resolution action for each exception, any manual overrides with justifications, and the final zero-exception confirmation.
Store the report in your compliance document repository with a naming convention that includes the pay period end date and the report version (e.g., "Audit_Report_2024-PP26_v3_Final"). This report is the first document a DOL investigator or plaintiff's attorney will request in a wage-and-hour dispute. It must be complete, retrievable, and self-explanatory.
Set a reminder to run this procedure before every payroll submission. The audit is not a quarterly or annual exercise; it is a per-period requirement. Teams that run this audit consistently before every submission catch configuration drift and data-entry patterns that would otherwise compound into significant liability over time.
Expected outcome: A finalized, clean audit report is archived in the compliance repository for the pay period, with all exceptions documented, resolved, and traceable.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Configure Overtime Threshold Rules by Jurisdiction

1. Identify All Active Jurisdictions

2. Map Statutory Overtime Thresholds for Each Jurisdiction

3. Enter Employer-Policy Overrides

4. Assign Rulesets to Employee Groups

5. Set Overtime Rate Multipliers

6. Run a Threshold Validation Test

7. Save and Version the Ruleset

How to Map Pay Codes to Overtime Eligibility

1. Export the Complete Pay-Code List

2. Classify Each Code as Hours Worked or Hours Paid but Not Worked

3. Flag Jurisdiction and Policy Exceptions

4. Enter Classifications in the Pay-Code Eligibility Matrix

5. Configure PTO and Sick Leave Exclusion Logic

6. Test the Matrix with a Mixed Pay-Period Scenario

7. Document the Matrix and Obtain HR Sign-Off

How to Stack Holiday Premium and Overtime Rates in the Same Pay Period

1. Define the Holiday Premium Rate

2. Establish the Rate-Stacking Rule

3. Set the Regular Rate of Pay Calculation

4. Map the Stacking Rule to Employee Groups

5. Test a Same-Day Holiday-Plus-Overtime Scenario

6. Test a Holiday-Week Overtime Scenario

7. Export the Rate-Stacking Configuration Summary

How to Apply Multi-Jurisdiction Double-Time Logic for Holiday and Overtime Interactions

1. Activate the California Daily Overtime Layer

2. Configure the 7th-Consecutive-Day Rule

3. Layer California Daily Overtime Over Weekly FLSA Overtime

4. Handle Holiday Hours Under California Rules

5. Set Up Multi-State Employee Routing

6. Test a California Holiday-Week Double-Time Scenario

7. Validate the 7th-Consecutive-Day Scenario

How to Audit Pay Period Outputs for Overtime and Holiday/PTO Compliance

1. Run the Pre-Submission Audit Report

2. Review Overtime Exception Flags

3. Verify Holiday Premium Applications

4. Check PTO and Sick Leave OT Exclusions

5. Validate Double-Time Triggers for California Employees

6. Resolve Exceptions Before Submission

7. Export the Finalized Audit Report

How These Procedures Connect

Next steps