How to Automate Payroll Compliance: 5 Procedures for HR and Payroll Teams | EasyClocking by WorkEasy Software

How to Configure Automated Payroll-Ready Time Capture

intermediate · One full pay period (parallel run required)

This procedure establishes a compliant, automated time-to-payroll data pipeline in a multi-location or remote environment. It is executed by the payroll operations lead or HRIS administrator during initial system implementation or after a workforce expansion event and produces a validated time capture configuration that feeds payroll without manual intervention.

1. Map Pay Rules to a Single Configuration Matrix
Prerequisites
- Current FLSA, applicable state wage-and-hour rules, and any union or CBA overtime thresholds documented
- Employee classification roster (exempt vs. non-exempt, full-time vs. part-time) finalized
Document every applicable pay rule in a single configuration matrix before touching any system settings. This matrix must cover:
- FLSA weekly overtime thresholds for non-exempt employees
- State-specific daily overtime rules (California's 1.5x after 8 hours, 2x after 12 hours, and 7th-day rules are the most complex)
- Break and meal period penalty requirements for applicable states
- Shift differentials, weekend premiums, and any CBA or union-specific overtime thresholds
- Pay frequency requirements by state (some states mandate semi-monthly or more frequent pay)
Pull the employee classification roster (exempt vs. non-exempt, full-time vs. part-time) and assign each classification group to the correct rule set. Do not map pay rules to job titles. Job titles do not determine overtime eligibility; only the FLSA classification and duties test determine whether an employee is exempt. EasyClocking by WorkEasy Software provides a pre-built pay rule matrix template covering FLSA, California, and common union thresholds as part of its implementation engagement, which you can use as the starting framework for this step.
Expected outcome: A completed pay rule matrix document listing every applicable rule, the employee classification it applies to, and the work location or state where it is enforced.
2. Configure the Pay Rule Engine
Prerequisites
- Pay rule matrix completed from the previous step
- Administrator access to the time system's pay rule engine
Enter each mapped rule from your configuration matrix into the time system's pay rule engine. For each rule, assign the correct employee classification group and work location. Key configuration items include:
- Overtime calculation method (weekly, daily, or both for California employees)
- Regular rate of pay calculation, including all remuneration required under FLSA (bonuses, shift differentials, non-discretionary incentives)
- Break and meal period tracking triggers that flag missed breaks for penalty-pay addition
- Shift differential rates tied to specific schedules or time windows
Test each rule against a known-good calculation before moving to the next. For example, configure the California daily overtime rule for a non-exempt employee, enter a test day with 10 hours worked, and verify the system calculates 8 hours at straight time, 2 hours at 1.5x. If the system produces a different result, correct the configuration before proceeding. Do not batch-configure all rules and test later; a single misconfigured rule can cascade errors across an entire employee group.
Expected outcome: Every pay rule from the configuration matrix is entered and individually tested in the time system, with each test producing the correct overtime, premium, or penalty calculation for a known input.
3. Set Rounding and Grace-Period Policies
Prerequisites
- FLSA rounding guidance reviewed
- State-specific rounding case law reviewed with legal counsel if applicable
Define punch rounding intervals and grace periods within FLSA-permissible limits. Under FLSA, rounding is permissible if it averages out over time and does not consistently favor the employer. Common compliant configurations include rounding to the nearest 5, 6, or 15 minutes.
Document the rounding policy in writing. This document must specify:
- The rounding interval applied (e.g., nearest 6 minutes)
- The direction of rounding (to the nearest interval, not always down)
- Any grace period for tardiness and how it interacts with the rounding rule
- Whether rounding applies to both clock-in and clock-out punches
Save this document alongside the pay rule matrix. Auditors reviewing FLSA compliance will ask for written rounding policy documentation. If your organization operates in states with stricter rounding rules (California courts have scrutinized rounding policies that, in practice, deprive employees of wages), consult with legal counsel before finalizing. Configure the rounding rule in the time system and verify it against the same test scenarios used for pay rules.
Expected outcome: A written rounding policy document is saved alongside the pay rule matrix, and the rounding configuration in the time system produces correct results on test punches.
4. Connect the Time System to Payroll
Prerequisites
- Payroll system API credentials and integration documentation confirmed
- Time capture device or app provisioned for all employee locations
Establish the integration between the time capture system and the payroll processor. EasyClocking by WorkEasy Software supports 20+ payroll and HR system integrations, including direct API connections and file-based exports. For API integrations:
- Enter the payroll system's API credentials into the time system's integration settings
- Map fields for hours type (regular, overtime, double-time), cost center, department, employee ID, and pay code
- Configure the sync schedule (real-time, daily, or on-demand before payroll cutoff)
For file-based integrations, map the export file columns to match the payroll processor's import template. Confirm that every field in the payroll import specification has a corresponding field in the time system export. Run a test export and import it into the payroll system's staging environment. Verify that hours, employee IDs, cost codes, and pay types land in the correct fields. A single misaligned column can route hours to the wrong employee or apply the wrong pay rate across an entire pay period.
Expected outcome: A test integration runs successfully, with a sample time file imported into the payroll system's staging environment and every field verified to land in the correct payroll column.
5. Run a Parallel Pay Period
Prerequisites
- Integration tested and verified in the staging environment
- All employees enrolled in the new time capture system
- Legacy process still operational for the duration of the parallel period
Process one full pay period using both the legacy manual method and the new automated system simultaneously. The parallel run is not optional. Skipping it is the most common cause of underpayment errors in live payroll after a system change.
During the parallel period:
- Employees punch into the new time system as if it were live
- Managers continue the existing manual or legacy process in parallel
- At period-end, generate the payroll output from both systems independently
Compare the outputs line by line for every employee. For each discrepancy, determine whether the error is in the new system configuration, the legacy process, or both. Document every discrepancy and its root cause in a reconciliation log. Pay particular attention to overtime calculations for employees who work across multiple states or locations, break penalty calculations for California and other penalty states, and employees with mid-period rate changes or classification changes.
Expected outcome: A completed line-by-line reconciliation log comparing legacy and new system outputs, with every discrepancy documented and root-caused.
6. Resolve Discrepancies from the Parallel Run
Prerequisites
- Reconciliation log completed from the parallel run
Correct every pay rule mismatch, integration mapping error, and rounding discrepancy identified during the parallel run. Prioritize discrepancies by impact:
1. Overtime calculation errors (highest compliance risk; direct FLSA exposure)
2. Break and meal period premium errors (state penalty exposure in California, Oregon, Nevada, and other applicable states)
3. Integration field mapping errors (wrong cost center or pay code; affects job costing and financial reporting)
4. Rounding discrepancies (lower individual impact but systemic across all employees)
For each correction, update the pay rule engine or integration mapping, then re-run the affected test scenarios to confirm the fix. Do not batch corrections and re-test at the end. Each correction should be verified immediately to avoid compounding errors. If more than a small number of discrepancies remain after the first correction pass, run a second parallel period before going live. The cost of a second parallel period is far lower than the cost of correcting live payroll errors after employees receive incorrect paychecks.
Expected outcome: All discrepancies from the parallel run are resolved, re-tested, and documented; the reconciliation log shows zero open items.
7. Document the Configuration Baseline
Prerequisites
- All parallel-run discrepancies resolved and verified
Save the finalized pay rule matrix, integration field map, rounding policy, and parallel-run reconciliation log as the system-of-record configuration document. This baseline serves two purposes:
- It is the reference document for any future configuration change. No pay rule, rounding interval, or integration mapping should be modified without comparing the proposed change against this baseline.
- It is the primary evidence document in a compliance audit. Auditors reviewing FLSA, state wage-and-hour, or union compliance will ask how pay rules were configured and validated. The baseline document, including the parallel-run reconciliation log, provides that evidence.
Store the baseline in a location accessible to the payroll manager, HR lead, and any external compliance advisor. EasyClocking by WorkEasy Software's implementation engagement delivers this configuration baseline as a structured deliverable at the end of onboarding, so your team has a versioned reference document from day one. Date-stamp the baseline and establish a review cadence: revisit the document whenever pay rules change, new states are added to the workforce footprint, or a new CBA is ratified.
Expected outcome: A version-controlled configuration baseline document is saved, accessible to all relevant stakeholders, and date-stamped for future audit reference.

Download the procedure above

How to Validate Time Data Before Each Payroll Run

intermediate · 2-4 hours per pay period

This procedure detects and corrects time capture errors (missing punches, unapproved overtime, break violations) before they reach payroll processing. It is executed by the payroll administrator or team lead on a per-period cadence and produces a clean, exception-free time file ready for payroll import.

1. Pull the Exception Report
Prerequisites
- Time capture system live and integrated with payroll (see How to Configure Automated Payroll-Ready Time Capture)
- Exception report template configured in the time system
Generate the time system's exception report covering all employees for the current pay period. EasyClocking by WorkEasy Software surfaces exceptions automatically, including missing punches, unapproved overtime entries, unresolved schedule variances, and break compliance flags. Filter the report by exception type so you can see the full scope before triaging.
If your organization spans multiple locations or states, generate the report at the location level first, then roll up to the company level. Location-level reports make it easier to route exceptions to the correct manager. Pull the report at a consistent point in the pay period, ideally 48 hours before payroll cutoff, to leave enough time for manager resolution. Pulling the report on the day of cutoff leaves no buffer for complex exceptions that require manager investigation.
Expected outcome: A complete exception report for the current pay period is generated and organized by location and exception type.
2. Triage Exceptions by Severity
Prerequisites
- Exception report generated from the previous step
Categorize every exception as either blocking or informational:
- Blocking exceptions must be resolved before payroll runs. These include missing punches (no clock-in or clock-out for a scheduled shift), overtime hours without manager approval, and missed meal or rest period records for employees in penalty states.
- Informational exceptions should be logged for trend analysis but do not hold payroll. These include minor schedule variances (clocking in a few minutes early or late within your rounding policy), approved PTO entries, and shift swaps that were pre-approved.
Do not skip the triage step. Treating all exceptions as equal leads to either payroll delays (investigating low-priority items) or compliance gaps (overlooking high-priority items in a long list). Record the triage decision for each exception in the exception log. Over time, patterns in informational exceptions reveal systemic capture problems. If one location consistently generates a high number of missing punches, the issue is likely a hardware placement or connectivity problem at that site, not individual employee behavior.
Expected outcome: Every exception is categorized as blocking or informational, with the triage decision recorded in the exception log.
3. Route Blocking Exceptions to Managers
Prerequisites
- Manager approval workflow active for all employee groups
- Blocking exceptions identified from the triage step
Send each blocking exception to the responsible manager with a resolution deadline of 24 hours before payroll cutoff. The notification should include the employee name, exception type, affected date and shift, and the specific action required (approve overtime, enter missing punch, confirm meal period waiver).
EasyClocking by WorkEasy Software's validation workflow automates this routing and enforces deadline tracking, so managers receive notifications with the exception details and a clear response deadline. If a manager does not respond by the deadline, escalate to their direct supervisor and the payroll manager. Do not resolve blocking exceptions on the manager's behalf without documented authorization. Payroll administrators who enter missing punches or approve overtime without manager confirmation create audit risk, because the time record no longer traces to the person with direct knowledge of the employee's actual hours worked.
Expected outcome: All blocking exceptions are routed to the responsible manager with a documented deadline, and an escalation path is triggered for any unresolved exceptions.
4. Validate Overtime Against Pay Rules
Prerequisites
- Pay rule matrix from the configuration baseline available for reference
Cross-reference all overtime hours in the current period against the pay rule matrix from the configuration baseline (see How to Configure Automated Payroll-Ready Time Capture). Confirm that:
- Weekly overtime is calculated correctly for all non-exempt employees at the FLSA threshold
- Daily overtime is applied for employees in states that require it (California, Alaska, Nevada, Colorado for certain industries)
- The regular rate of pay includes all required remuneration (non-discretionary bonuses, shift differentials) per FLSA requirements
- 7th-consecutive-day rules are applied for California employees
Pay special attention to employees who worked across multiple locations or states during the period. If an employee worked in both a daily-overtime state and a weekly-only state, the system must apply the correct rule for hours worked in each jurisdiction. This is where misconfiguration most often surfaces. If any overtime calculation does not match the expected output from the pay rule matrix, stop and investigate before proceeding.
Expected outcome: All overtime hours are verified against the pay rule matrix, and any calculation discrepancies are flagged for correction before payroll submission.
5. Confirm Break Compliance
Prerequisites
- Break and meal period premium pay rules active in the time system for all applicable states
Review break and meal period records for all non-exempt employees in states with mandatory break penalties. California, Oregon, and Nevada are the most common, but check your state roster against current requirements. For each non-exempt employee in a penalty state:
- Confirm that the required meal period was taken within the mandated window (California requires a 30-minute meal period before the end of the 5th hour of work)
- If a meal period was waived, confirm that a written waiver or attestation is on record
- Confirm that rest periods were provided per the applicable state schedule
- For any missed break, confirm that the premium pay (typically one additional hour at the employee's regular rate) is added to the payroll file
Break compliance is one of the most frequent sources of California wage claims. A single missed meal period premium, multiplied across employees and pay periods, can become a significant liability. If the system does not have break attestation or waiver capture enabled, flag this as a configuration gap and return to the setup procedure to correct it.
Expected outcome: Break and meal period compliance is verified for all non-exempt employees in penalty states, with premium pay added for any documented missed breaks.
6. Reconcile Approved Hours to the Payroll Import File
Prerequisites
- All blocking exceptions resolved and overtime/break validation completed
Compare the total approved hours by employee in the time system to the corresponding totals in the payroll import file. This step catches integration transfer errors that are invisible in exception reports. Common issues include:
- Hours dropped during the API sync or file export (employee appears in the time system but not in the payroll file)
- Duplicate entries (employee hours appear twice due to a sync retry)
- Pay code mismatches (overtime hours imported as straight time)
Run the comparison at the employee level, not just the company total. A company-level total can mask offsetting errors (one employee overstated, another understated, total looks correct). If the time system and payroll import file do not match for any employee, investigate before submitting. The reconciliation log from this step becomes part of the period's compliance documentation.
Expected outcome: A documented reconciliation confirming that approved hours in the time system match the payroll import file for every employee, with any discrepancies investigated and resolved.
7. Lock the Time Period
Prerequisites
- Reconciliation completed and payroll import file submitted
Close the pay period in the time system to prevent retroactive edits after payroll submission. Once locked, any change to a time record in the closed period should require a documented override with manager and payroll manager approval. This lock is a critical audit control. Without it, time records can be modified after payroll runs, creating discrepancies between what was paid and what the time system shows.
After locking, generate a final snapshot of the period's time data and store it alongside the reconciliation log. This snapshot is the authoritative record if any dispute or audit question arises about this period's hours. EasyClocking by WorkEasy Software's period lock prevents retroactive changes and logs any override attempts with the requesting user's identity and timestamp, creating the audit trail that FLSA recordkeeping requires.
Expected outcome: The pay period is locked in the time system, a final data snapshot is archived, and any future edits require a documented override process.

Download the procedure above

How to Execute a Compliant Period-End Payroll Close

intermediate · 1-2 hours per pay period

This procedure closes a pay period with complete, audit-defensible payroll records and zero manual cleanup items. It is executed by the payroll manager at the end of each pay period and produces a finalized payroll register, a signed-off exception log, and an archived time record set meeting FLSA's retention requirement.

1. Run the Payroll Register Variance Report
Prerequisites
- Per-period time validation completed (see How to Validate Time Data Before Each Payroll Run) with zero unresolved blocking exceptions
- Payroll register draft generated by payroll processor
- Prior-period payroll register available for variance comparison
Compare current-period gross pay by employee to the prior period, flagging any variance exceeding 10% for manual review. The 10% threshold is a practical screening filter; adjust it based on your organization's pay variability. Organizations with high overtime fluctuation (construction, warehousing) may need a higher threshold to avoid excessive false positives, while stable-schedule environments (offices, manufacturing lines) may use a tighter threshold.
Generate the variance report from the payroll processor using the draft payroll register. If your payroll processor does not offer a built-in variance report, export current and prior period registers to a spreadsheet and calculate the variance per employee. Focus on gross pay, not net, because net pay differences can be caused by tax table changes or benefit deductions unrelated to time capture accuracy.
Expected outcome: A variance report identifying every employee whose gross pay changed by more than the screening threshold, ready for investigation.
2. Investigate Flagged Variances
Prerequisites
- Variance report generated from the previous step
For each employee flagged in the variance report, confirm that the variance is explained by an approved event. Common legitimate variance causes include:
- Approved overtime hours in the current period that were not present in the prior period
- PTO or unpaid leave reducing total hours
- A mid-period rate change (promotion, annual increase, shift to a different pay grade)
- A classification change (part-time to full-time, or vice versa)
Document the explanation for each flagged variance in the period's exception log. If a variance cannot be explained by an approved event, do not proceed to payroll submission. Investigate whether the variance is caused by a time capture error (incorrect punch, missed exception), a pay rule misconfiguration, or a payroll processing error. Unexplained variances that reach employees as incorrect paychecks create correction work, employee dissatisfaction, and potential compliance exposure.
Expected outcome: Every flagged variance has a documented explanation tied to an approved event, or the variance is identified as an error and routed for correction before payroll submission.
3. Confirm Tax Withholding Accuracy
Prerequisites
- Current federal and state tax tables loaded in the payroll processor
- Employee work location data current in both the time system and payroll processor
Verify federal, state, and local withholding calculations against current tax tables. Pay attention to employees who may have crossed withholding thresholds during the period, such as:
- Employees who crossed the Social Security wage base due to cumulative year-to-date earnings
- Employees working in a state different from their home state (travel or temporary assignment), triggering reciprocal withholding or additional state filing
- New hires or terminated employees whose partial-period earnings may affect withholding calculations
This step is a verification check, not a recalculation. Your payroll processor handles the calculation; your role is to confirm the inputs are correct. If an employee's work state or filing status changed during the period and the payroll system was not updated, the withholding calculation will be wrong regardless of how accurately hours were captured. Cross-reference employee records in the time system against the payroll processor's employee master file to catch discrepancies.
Expected outcome: Tax withholding inputs are verified as current and consistent between the time system and payroll processor for all employees in the period.
4. Approve and Submit Payroll
Prerequisites
- All variances investigated and resolved
- Tax withholding accuracy confirmed
Obtain the required approval signature before submitting to the payroll processor. For organizations with more than 100 employees, best practice is dual approval: the payroll manager approves, and a finance lead or controller provides a second sign-off. This dual-approval control is both an internal fraud prevention measure and an audit-defensibility practice.
Submit payroll by the payroll processor's published cutoff. Late submissions can delay direct deposits and trigger employee complaints that distract from the next period's work. Document the submission time and the approvers' identities in the period's compliance record. If your payroll processor provides a confirmation receipt or transaction ID, save it. This receipt is your evidence that payroll was submitted on time if any dispute arises about payment timing.
Expected outcome: Payroll is submitted by the cutoff with documented dual approval and a saved submission confirmation receipt.
5. Archive Time Records
Prerequisites
- Payroll submitted and confirmation receipt saved
- Records retention folder or system configured for FLSA-compliant archiving
Export and store the finalized time file, exception log, reconciliation log, and payroll register in the designated retention system. FLSA requires employers to retain payroll records for at least two years (three years for records supporting overtime and minimum wage calculations). Name each file with a consistent convention that includes the pay period dates and the record type.
EasyClocking by WorkEasy Software's period-end close workflow archives time records automatically to a retention-compliant folder without requiring manual export steps. If you are using a manual archive process, confirm that the archived files are read-only or stored in a system that prevents modification. Archived records that can be edited after the fact lose their evidentiary value in an audit. Verify that you can retrieve the archived records within 24 hours; audit response windows are tight, and records stored in locations that require IT intervention to access create unnecessary delay.
Expected outcome: All period records (time file, exception log, reconciliation log, payroll register) are archived in a read-only, date-stamped format retrievable within 24 hours.
6. Generate the Period-End Compliance Summary
Prerequisites
- All period records archived
Produce a one-page summary of the period's key compliance metrics. This summary should include:
- Total hours by classification (exempt, non-exempt, full-time, part-time)
- Total overtime hours and the overtime percentage of total hours
- Break penalties paid (for applicable states)
- Number of exceptions resolved and any open items carried to the next period
- Any configuration changes made during the period
EasyClocking by WorkEasy Software generates this compliance summary automatically at period-end. This summary serves two audiences: management (who need visibility into labor cost trends and compliance risk) and auditors (who need a quick-reference document when reviewing a specific period). If any open items are carried to the next period, document them clearly, including the expected resolution date and the responsible party. Open items that carry across multiple periods without resolution are audit red flags.
Expected outcome: A one-page compliance summary is available for management review or audit production, documenting total hours, overtime, break penalties, exceptions resolved, and any open carry-forward items.

Download the procedure above

How to Respond to a Payroll Compliance Audit

advanced · Varies; typically the full response window provided by the auditing agency

This procedure produces complete, accurate payroll and time records in response to a DOL, IRS, or state labor agency audit inquiry. It is executed by the payroll manager and HR lead immediately upon receipt of an audit notice and produces a complete record production package within the agency's response window.

1. Confirm the Audit Scope
Prerequisites
- Audit notice received and response deadline confirmed in writing
- Legal counsel or HR compliance advisor notified
Identify the specific employees, pay periods, and regulatory provisions named in the audit notice before pulling any records. Audit notices typically specify:
- The regulatory basis (FLSA, state wage-and-hour law, IRS employment tax)
- The time period under review (e.g., the preceding two or three years)
- The employee population (all employees, a specific classification, or named individuals)
- The specific records requested (time records, payroll registers, classification documentation, pay policies)
Do not begin pulling records until you have confirmed the scope in writing with the auditing agency. Producing records outside the requested scope can expand the audit unnecessarily. If the notice is ambiguous, contact the assigned auditor to clarify. Document the scope confirmation in writing, including the auditor's name, contact information, and the response deadline. Share this confirmed scope with legal counsel immediately.
Expected outcome: The audit scope (employees, periods, provisions, records requested) is confirmed in writing, and the response deadline is documented and shared with all parties involved in the response.
2. Retrieve Archived Time Records
Prerequisites
- FLSA-compliant time and payroll records archived for the audit period (minimum two years)
- Access to the records retention system confirmed
Export time records for all employees and periods in scope from the retention system. If you have followed the period-end close procedure (How to Execute a Compliant Period-End Payroll Close), these records should be archived, date-stamped, and retrievable within 24 hours.
For each period in scope, retrieve the time file, exception log, reconciliation log, and payroll register. Confirm completeness by checking that every employee named in the audit scope appears in the time records for every period in scope. If any records are missing, document the gap immediately. Missing records are a more serious audit finding than records with minor errors, because missing records suggest a systemic recordkeeping failure. If records were maintained in a legacy system before your current time system was implemented, identify where those legacy records are stored and begin retrieval concurrently.
Expected outcome: All time and payroll records for the audit scope are retrieved, with any gaps identified and documented.
3. Reconcile Time Records to Payroll Register
Prerequisites
- Time records and payroll registers retrieved for all in-scope periods
Verify that every hour in the time records maps to a corresponding payroll line item for each employee and period in scope. This reconciliation is the core evidentiary exercise of the audit response. Auditors will look for:
- Hours in time records that do not appear in payroll (potential underpayment)
- Hours in payroll that do not appear in time records (potential record fabrication or system error)
- Overtime hours calculated differently in the time records vs. payroll register
- Break penalty pay in payroll without corresponding break records in the time system
For any gap between time records and payroll, prepare a written explanation memo. Common explanations include manual corrections processed outside the time system, retroactive pay adjustments, or system migration gaps. Each explanation should reference a specific approval or authorization document. Unexplained gaps are the items that generate audit findings and potential penalties.
Expected outcome: A completed reconciliation showing time-to-payroll alignment for every employee and period in scope, with written explanation memos for any gaps.
4. Prepare the Classification Evidence File
Prerequisites
- Employee classification roster for the audit period available
- Job descriptions and offer letters accessible in the HR records system
Compile the documentation supporting the FLSA classification (exempt vs. non-exempt) for every employee classification type named in the audit scope. This file should include:
- Job descriptions specifying the duties, responsibilities, and supervisory authority for each position
- Offer letters or employment agreements stating the classification and compensation basis (salary vs. hourly)
- The FLSA classification rationale, documenting which exemption test (executive, administrative, professional, computer, outside sales) applies and how the employee's duties satisfy it
Misclassification is one of the most common and most costly FLSA audit findings. If any classification is questionable, flag it for legal counsel's review before including it in the response package. Do not attempt to reclassify employees retroactively as part of the audit response without legal guidance, as retroactive reclassification creates back-pay obligations and must be handled carefully.
Expected outcome: A classification evidence file is compiled for every employee type in scope, with each classification supported by a job description, offer letter, and documented exemption rationale.
5. Draft the Response Package
Prerequisites
- Reconciliation completed, classification evidence file compiled, and all gap explanation memos drafted
Organize all records into the format requested by the auditing agency. Common formats include:
- Chronological by employee (all records for Employee A across all periods, then Employee B)
- Chronological by pay period (all employees for Period 1, then all employees for Period 2)
- By classification (all exempt employees, then all non-exempt employees)
Include a cover memo summarizing the record set: the total number of employees, the total number of periods, the record types included, and any known gaps with their explanations. The cover memo should be factual and concise. Do not include legal arguments, justifications, or defensive language in the cover memo; that is counsel's role, not the payroll team's. Organize the package so an auditor unfamiliar with your systems can navigate it without assistance. Label each section clearly, include a table of contents for packages exceeding 50 pages, and provide a glossary of any codes or abbreviations used in your time or payroll system exports.
Expected outcome: A complete, organized response package with a cover memo, table of contents (if applicable), and clearly labeled sections, ready for legal review.
6. Review with Legal Counsel
Prerequisites
- Draft response package completed
Submit the draft response package to legal counsel or your HR compliance advisor for review before producing it to the auditing agency. Counsel's review should cover:
- Whether the records produced match the audit scope (not overproducing or underproducing)
- Whether any gap explanation memos create unintended admissions
- Whether classification rationale documentation is legally sufficient
- Whether any records should be withheld under attorney-client privilege or work product doctrine (rare in wage-and-hour audits, but counsel should assess)
Allow adequate time for this review. If the audit response deadline is tight, share the draft with counsel as sections are completed rather than waiting for the full package. Counsel may request modifications to explanation memos or additional documentation. Incorporate all requested changes before finalizing.
Expected outcome: Legal counsel has reviewed the response package and approved it for production, with all requested modifications incorporated.
7. Produce Records to the Agency
Prerequisites
- Legal counsel has approved the response package
Deliver the finalized response package to the auditing agency by the deadline using the agency's specified submission method (mail, electronic upload, in-person delivery). Before sending:
- Confirm the submission method and address or portal with the assigned auditor
- Create a timestamped copy of the complete package for your records
- If submitting electronically, save the upload confirmation or email delivery receipt
- If submitting by mail, use a tracked delivery method and retain the tracking number
After submission, document the production in a brief internal memo noting the date, method, recipient, and contents. If the auditor requests follow-up records or clarification after your initial production, repeat steps as needed, routing all follow-up production through legal counsel before delivery. Retain the submission copy and all audit correspondence for at least the duration of the audit plus any statute-of-limitations period, as advised by counsel.
Expected outcome: The response package is delivered by the deadline with a retained timestamped copy and documented proof of delivery.

Download the procedure above

How to Identify and Correct California Payroll Errors

advanced · Complete within one pay cycle of error identification

This procedure diagnoses and remediates the most common California-specific payroll compliance failures, including daily overtime miscalculation, missed meal and rest period premiums, and final paycheck timing violations. It is executed by the payroll manager or HR compliance lead when a California employee complaint, audit flag, or internal review surfaces a potential error.

1. Identify the Error Type
Prerequisites
- California-specific pay rules configured in the time system (daily OT at 1.5x after 8 hrs, 2x after 12 hrs, 7th-day rules)
- Meal and rest period premium pay rules active for all non-exempt California employees
Classify the flagged error before calculating any correction. California payroll errors fall into distinct categories, each requiring a different correction methodology:
- Overtime miscalculation: California requires daily overtime at 1.5x after 8 hours, 2x after 12 hours, and 7th-consecutive-day overtime. Errors occur when the system applies only weekly overtime (the FLSA default) without the California daily overlay.
- Missed meal or rest period premium: Non-exempt employees who miss a required meal or rest period are owed one additional hour of pay at their regular rate per missed period. Errors occur when the time system does not flag missed breaks or when the premium is not added to payroll.
- Final paycheck timing: California requires immediate payment of final wages upon involuntary termination and payment within 72 hours for voluntary resignation (or immediately if the employee gave 72+ hours of notice). Waiting-time penalties accrue daily for late final paychecks.
- Other California-specific violations: These include reporting time pay, split-shift premiums, and pay stub itemization errors.
Correctly classifying the error determines the remediation path. Do not combine different error types into a single correction; each type has distinct penalty calculations and documentation requirements.
Expected outcome: The error is classified into a specific category (overtime miscalculation, missed meal/rest premium, final paycheck timing, or other), and the correction methodology for that category is identified.
2. Pull Affected Pay Periods
Prerequisites
- Prior payroll registers for the affected periods available
- Employee's California start date and classification history confirmed
Retrieve time records and payroll registers for all periods in which the error may have occurred. Use the employee's California start date as the lookback start, extending back to the earliest period potentially affected. For overtime miscalculations, the lookback may cover the employee's entire California tenure. For missed meal premiums, review every period since the break tracking configuration was last changed.
Do not limit the lookback to only the period where the error was reported. California wage claims can reach back to earlier periods, and correcting only one period when the error is systemic across multiple periods increases your exposure. Pull the records for every potentially affected period and review them as a set. If other California employees in the same classification or location were subject to the same pay rules, pull their records as well. A configuration error that affects one employee almost always affects others.
Expected outcome: Time records and payroll registers are retrieved for all potentially affected periods and employees, with the lookback scope documented.
3. Recalculate Correct Pay
Prerequisites
- Time records and payroll registers retrieved for all affected periods
Apply California's daily and weekly overtime rules, meal and rest period premium rates, and any applicable waiting-time penalties to determine the total underpayment. For each affected period:
- Recalculate daily overtime for every workday, applying 1.5x after 8 hours and 2x after 12 hours
- Apply 7th-consecutive-day rules for any applicable workweek
- Calculate meal and rest period premiums at one hour of regular rate pay per missed period
- If the error involved a final paycheck, calculate waiting-time penalties at the employee's daily rate for each day of delay, up to the statutory maximum
Document the recalculation methodology in detail. Show the original pay, the corrected pay, and the difference for each affected period. This documentation becomes part of the remediation record and will be reviewed by the employee, management, and potentially an auditor or attorney. EasyClocking by WorkEasy Software's California pay rule library includes pre-configured daily overtime, 7th-day, and meal/rest premium rules that prevent this class of error at the configuration layer.
Expected outcome: A detailed recalculation showing original pay, correct pay, and the underpayment amount for each affected period and employee, with the methodology documented.
4. Prepare a Correction Memo
Prerequisites
- Recalculation completed for all affected periods
Document the error type, affected periods, recalculation methodology, and total correction amount in a signed memo. The correction memo should include:
- Employee name, ID, classification, and California work location
- Error type and how it was discovered (employee complaint, internal audit, system flag)
- Each affected pay period with the original pay amount and the corrected pay amount
- The recalculation methodology, referencing the specific California Labor Code sections or Wage Orders that apply
- The total correction amount
- The date the correction payment will be issued
This memo is retained in the employee's payroll file permanently. It serves as evidence that the employer identified the error, investigated it, and corrected it promptly. Prompt self-correction, documented thoroughly, is a mitigating factor in any subsequent enforcement action. Have the payroll manager sign the memo and obtain a countersignature from the HR lead or finance lead.
Expected outcome: A signed correction memo is prepared and ready for filing, documenting the error, affected periods, methodology, and correction amount.
5. Issue the Correction Payment
Prerequisites
- Correction memo signed and filed
- Off-cycle payroll run authorized by the payroll manager
Process the correction as a separate off-cycle payroll run. Do not fold the correction into the next regular payroll cycle. California waiting-time penalties accrue daily for unpaid wages; delaying a known correction to the next regular pay date extends the penalty period unnecessarily.
The correction payment must appear as a distinct line item on the employee's pay stub, identified as a California wage correction. Do not label it as a bonus, adjustment, or miscellaneous payment. Incorrect labeling can create tax reporting issues and makes it harder to demonstrate compliance in a subsequent review. Process the correction with the same tax withholding treatment as regular wages for the periods in which the hours were originally worked. If multiple periods are being corrected, consult with your payroll processor or tax advisor on the correct withholding methodology for lump-sum retroactive payments.
Expected outcome: A separate correction payment is processed and delivered to the employee, with a pay stub line item clearly identifying it as a California wage correction.
6. Update Pay Rule Configuration
Prerequisites
- Root cause of the configuration error identified during the recalculation step
Correct the time system pay rule that produced the error. Return to the configuration procedure (How to Configure Automated Payroll-Ready Time Capture) and update the specific rule. Common corrections include:
- Enabling daily overtime for California employees who were only subject to weekly overtime rules
- Activating meal and rest period tracking and premium calculation for California non-exempt employees
- Adding 7th-consecutive-day overtime rules for the correct employee groups
After updating the rule, re-run the validation procedure (How to Validate Time Data Before Each Payroll Run) for the current open period to confirm the correction is active. Test the updated rule against the same scenarios that produced the original error. If the same input now produces the correct output, document the rule change in the configuration baseline. If it does not, investigate further before closing. Fixing one employee's paycheck without fixing the underlying configuration guarantees the same error will recur for every California employee subject to that rule.
Expected outcome: The time system pay rule is corrected, tested against the original error scenario, and the configuration baseline is updated to reflect the change.
7. Notify the Employee in Writing
Prerequisites
- Correction payment processed and pay stub generated
Provide the employee a written explanation of the correction within the same pay cycle as the correction payment. The notification should include:
- A plain-language explanation of the error and how it was discovered
- The affected pay periods
- The correction amount and how it was calculated
- The date the correction payment was issued
- A copy of the corrected pay stub
The notification should be professional and factual. Do not include apologies that could be construed as admissions or defensive language that minimizes the error. State what happened, what you did to correct it, and what you did to prevent recurrence. If the employee has questions, direct them to the payroll manager or HR lead. Retain a copy of the notification, with the employee's acknowledgment of receipt if possible, in the employee's payroll file alongside the correction memo.
Expected outcome: The employee receives a written explanation of the correction and the corrected pay stub within the same pay cycle, with a copy retained in the employee's payroll file.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Configure Automated Payroll-Ready Time Capture

1. Map Pay Rules to a Single Configuration Matrix

2. Configure the Pay Rule Engine

3. Set Rounding and Grace-Period Policies

4. Connect the Time System to Payroll

5. Run a Parallel Pay Period

6. Resolve Discrepancies from the Parallel Run

7. Document the Configuration Baseline

How to Validate Time Data Before Each Payroll Run

1. Pull the Exception Report

2. Triage Exceptions by Severity

3. Route Blocking Exceptions to Managers

4. Validate Overtime Against Pay Rules

5. Confirm Break Compliance

6. Reconcile Approved Hours to the Payroll Import File

7. Lock the Time Period

How to Execute a Compliant Period-End Payroll Close

1. Run the Payroll Register Variance Report

2. Investigate Flagged Variances

3. Confirm Tax Withholding Accuracy

4. Approve and Submit Payroll

5. Archive Time Records

6. Generate the Period-End Compliance Summary

How to Respond to a Payroll Compliance Audit

1. Confirm the Audit Scope

2. Retrieve Archived Time Records

3. Reconcile Time Records to Payroll Register

4. Prepare the Classification Evidence File

5. Draft the Response Package

6. Review with Legal Counsel

7. Produce Records to the Agency

How to Identify and Correct California Payroll Errors

1. Identify the Error Type

2. Pull Affected Pay Periods

3. Recalculate Correct Pay

4. Prepare a Correction Memo

5. Issue the Correction Payment

6. Update Pay Rule Configuration

7. Notify the Employee in Writing

How These Procedures Connect

Next steps