How to export Gusto time data for a break audit

Gusto handles payroll for a large share of California small businesses, which means consultants doing California meal and rest break audits encounter it often. The export you need is not the one most people reach for first. This guide explains which report to pull, what fields a break audit requires, and how to handle the gaps that are common in Gusto data.

What a break audit needs from payroll data

A California meal and rest break audit is ultimately a shift-by-shift analysis. For each shift in the period under review, the audit needs to determine whether compliant meal periods occurred and whether rest breaks can be confirmed. That requires the following fields at minimum:

• Employee ID and name — to tie findings back to individuals and to separate hourly from salaried staff.
• Work date — so shifts can be sorted into workdays for the one-violation-per-day premium calculation.
• Shift start and end times — to calculate total hours worked and determine how many meal and rest periods were required.
• Meal period punches — the clock-out and clock-in times that mark when a meal break started and ended. Without these, compliance with the fifth-hour and tenth-hour rules cannot be verified from the data alone.
• Regular rate of compensation — needed to calculate the premium pay owed for any violation. After Ferra v. Loews, this must include nondiscretionary bonuses and similar pay, not just the base wage.
• Rest attestation (if tracked) — some employers capture a rest break attestation in their timekeeping system; include it if Gusto is configured to collect it.

Exporting from Gusto

Gusto organizes its reports into payroll summaries and time-tracking detail. For a break audit, you want the time-tracking or hours detail export at the punch or shift level, not the payroll register.

To pull the right export:

• In Gusto, navigate to the Time & Attendance or Reports section and look for a time-tracking or hours detail report.
• Select the full pay period (or the date range) you are auditing. If auditing multiple pay periods, export them separately or in a single range — confirm the export includes all days in scope.
• Download at the punch or shift level, not the summarized totals level. You need individual shift rows, not a single row per employee per period.

Gusto-specific notes and gotchas

Gusto's built-in time tracking is lighter than dedicated time-clock systems. Before treating the export as complete, check for these common issues:

• Meal breaks may not be separate punches. Depending on how the employer set up Gusto, meal periods may appear as a shift gap, as a manual deduction, or not at all. If meal timing is absent, the audit can only evaluate what the data shows — those shifts are reported as record gaps, not automatic violations.
• Separate hourly from salaried employees. Salaried-exempt employees generally do not generate hourly punch data. Include them in the data pull if the engagement covers them, but flag them clearly — they are audited differently (or not at all, depending on the scope).
• Automatic deductions vs. recorded punches. Some Gusto configurations apply a blanket 30-minute meal deduction to every shift rather than recording actual clock-in/out. A fixed deduction does not prove a compliant meal occurred; note this in the audit and treat those shifts accordingly.
• Regular rate field. The payroll register is still useful for pulling the regular rate or gross pay figures needed for the premium calculation. Export both — time detail for the timing analysis, payroll register for the rate data.

Using the export in BreakAuditor

BreakAuditor recognizes the column layout of Gusto time-tracking exports and maps the fields automatically on upload. If the columns in your Gusto export differ from the default layout (which can happen depending on Gusto plan or configuration), the field-mapping screen lets you reassign them manually. Once you confirm the mapping, you can save it so repeat audits for the same client run faster.

The output report separates findings into two categories:

• Detected violations — shifts where the data shows a non-compliant or missing meal period, with the estimated premium exposure per shift and per employee.
• Record gaps — shifts where the data is insufficient to confirm compliance (for example, no meal punch recorded). These are flagged for follow-up rather than counted as confirmed violations, keeping the report defensible.

This distinction matters when Gusto data is thin. A report that conflates gaps with violations overstates exposure; a report that ignores gaps understates risk. Keeping them separate gives the employer and counsel an accurate picture of both what the data proves and what it cannot confirm.

Frequently asked questions