Exact answer: Pull the ADP Workforce Now time and attendance punch-detail export, not the payroll register or hours summary.

Fields that matter: employee ID, employee name, work date, shift in, shift out, Lunch Out, Lunch In, regular rate, premium-pay rows, rest attestations if tracked, and a source row or report identifier.

How it becomes a break audit: BreakAuditor maps those columns, tests California meal timing and rest-record gaps, credits premiums already paid, and returns a client-ready report with source-backed findings, correction rows, and an assumptions log. Use the California break audit checklist, preview the sample report, or request upload instructions.

California meal and rest break audits are only as accurate as the underlying timecard data. ADP Workforce Now stores the punch-level detail that an audit needs, but pulling the right export, and understanding ADP's formatting quirks, is a step that consultants frequently get wrong the first time. This guide walks through what to request, what to verify against the audit checklist, how the output compares to the sample report preview, and how to turn the file into a sample California break audit.

Have the ADP export already? One anonymized punch-detail CSV is enough to request a sample California break audit, including a branded PDF preview, correction rows, and an assumptions log. Get upload instructions, review the sample report, or confirm scope with the California checklist.

What a break audit needs

To flag late, short, or missing meal periods and calculate premium pay exposure under California's meal and rest break rules, an audit file must contain the following fields for each shift:

  • Employee ID and name: to link records across files and identify the worker unambiguously.
  • Work date: the calendar date the shift occurred.
  • Shift in and shift out times: the exact start and end of the employee's workday.
  • Meal punches (Lunch Out / Lunch In): when the employee clocked out for their meal period and back in. These are the key data points for testing California's fifth-hour and tenth-hour meal timing requirements.
  • Regular pay rate: needed to calculate any meal and rest break premium pay owed.
  • Rest attestation, if tracked: some employers log rest break attestations; include this column if it exists, but most ADP setups do not generate punch-level rest break records.

Illustrative anonymized preview

From ADP source fields to audit output

This sample row shows the output shape, not a real employee or legal conclusion. BreakAuditor preserves the source facts, normalizes the record, flags what needs review, and records assumptions where the export cannot prove an answer.

ADP source fieldsNormalized audit recordReview conditionCorrection outputAssumption recorded
Employee 1047; 06/12/2026; In 8:02; Lunch Out 13:18; Lunch In 13:48; Out 17:06; $24.009h 4m elapsed; 8h 34m recorded work excluding the meal; first meal began 5h 16m after shift startMeal timing requires review; source shows a late first-meal punchCorrection row identifies the date, source punches, rule tested, and reviewer action; premium treatment stays separate until payroll evidence is checkedNo waiver, on-duty agreement, or premium-payment conclusion without supporting records

See the full sample report Request ADP upload instructions

Exporting from ADP Workforce Now

ADP's time & attendance module includes a reporting area where you can build or run a punch-detail report. The goal is a CSV that has one row per punch event (or at minimum one row per shift with separate meal-out and meal-in columns), covering all employees for the pay period under review.

When configuring the export:

  • Select punch-detail or time-detail output, not a summary. Summary reports aggregate hours and will not show you when a meal period started relative to the shift start.
  • Include the date, all in/out punch times, and the employee's pay rate. If your ADP configuration tracks meal punches as separate columns (Lunch Out / Lunch In), verify those columns are included.
  • Cover the full pay period or date range in scope, partial exports are a common source of missed records near period boundaries.
  • Export as CSV. Excel-format exports can introduce implicit type conversions on date and time columns that are harder to parse reliably.
Export punch detail, not a payroll summary. The payroll register tells you total hours worked; the punch-detail export tells you when those hours happened. California's meal timing rules turn entirely on clock times, a summary cannot support an audit.

ADP-specific notes and gotchas

A standard ADP Workforce Now punch-detail export has several formatting characteristics that differ from what auditing tools and spreadsheets expect by default:

  • Names are "Last, First". ADP exports employee names in Last, First order. If you are cross-referencing records from another system that stores names differently, you will need to split and reorder these values. If you are presenting names in a report, the same applies.
  • Dates are MM/DD/YYYY. This is the ADP default. Many import pipelines expect ISO 8601 (YYYY-MM-DD). A date like 06/13/2026 may be misread as June 13 or parsed incorrectly if the importer assumes a different format, verify date parsing before running calculations.
  • Pay rates include a leading "$". ADP often exports numeric fields like rates as $22.50 rather than 22.50. The dollar sign must be stripped before the value can be used in arithmetic.
  • Lunch Out / Lunch In may be separate columns or separate rows. Depending on your ADP configuration and the report template used, meal punches may appear as distinct columns on a shift row or as separate punch-type rows in the export. Confirm the layout before writing any column mappings.
  • Rounding rules affect meal timing. ADP can be configured to round punch times, commonly to the nearest quarter hour or to a fixed rounding band. Rounded times can shift an apparent meal start enough to create a false violation or mask a real one. Where possible, configure the export to use raw (unrounded) punches for audit purposes, and document what rounding is in effect if raw punches are unavailable.
  • The payroll register is a different file. ADP produces both a time & attendance export and a payroll register. The payroll register is useful for confirming rates and earnings but typically contains only hours totals, it does not have the individual meal punch times a break audit requires. Make sure the client sends the time & attendance file, not (only) the payroll register.

Using ADP exports in BreakAuditor

BreakAuditor recognizes the column layout of a standard ADP Workforce Now punch-detail CSV. When the file is imported:

  • Last, First names are split and normalized automatically.
  • MM/DD/YYYY dates are parsed and converted to a consistent internal format.
  • Dollar-prefixed rates are stripped and converted to numeric values before any premium pay calculation.
  • Column mappings are saved per client so that repeat imports, for the next pay period or an extended look-back, require no re-configuration.

If the ADP export has non-standard column names or a custom report layout, those fields are mapped before the first import; the saved mapping is then reused for later review periods. If you are scoping a first client conversation, pair this page with the California break audit checklist and the sample report preview.