Payroll export
Hours out, in the shape Gusto expects.
Pick a pay period, get a CSV with Employee Name, Employee Email, Regular Hours, and Overtime Hours. The important part is not the columns — it is that the hours come from punches, not from what you scheduled.
- Category
- Payroll
- Setup
- No setup — export when you need it
- Who sets it up
- A manager or above
- Plans
- Every plan, including the free tier.
What you get
Gusto + Weekwright.
- Employee Name, Employee Email, Regular Hours, Overtime Hours — a four-column file, not a data dump you have to prune.
- Hours are computed from actual clock-in/clock-out data minus unpaid breaks. Scheduled hours are never used, because a shift someone left early is a scheduled 8 and a worked 6.
- Overtime is split per ISO week, not per pay period, because that is how overtime law actually works — a fortnightly period does not average away a 50-hour week.
- The weekly overtime threshold comes from your own MAX_HOURS_PER_WEEK compliance rule, so a 35-hour shop is not silently paid on a US 40-hour assumption.
Setup
How it works.
- 1
Open Insights → Payroll and choose the pay period and the Gusto preset.
- 2
Read the warnings, which appear ABOVE the table: missing punches, still-open shifts, breaks that overrun their shift. This is a file someone pays wages from, so it flags rather than guesses.
- 3
Check the numbers on screen, then download the CSV.
- 4
Import it into Gusto and reconcile the first run against your own records before trusting it.
Honest limits
What this does not do.
Every integration has edges. Better you read them here than discover them the week you go live.
- These column shapes are conventional, NOT certified by Gusto. Verify one file against your provider's own template before your first real payroll run — header names change and no test on our side can catch a mismatch with a spec we do not have.
- It is a file export, not an API sync. Nothing is pushed to Gusto automatically and no credentials are exchanged.
- It exports hours, not pay rules. Tips, deductions, benefits, garnishments, and multi-state tax handling stay in Gusto where they belong.
- A shift with a missing clock-out is reported as a warning and excluded rather than estimated. Fix the punch; do not let the export invent a number.
Common questions
Gusto FAQ.
Does Weekwright sync hours to Gusto automatically?
No. It produces a CSV in a Gusto-shaped column layout that you upload. We would rather ship an honest export today than an API integration whose failure mode is a wrong paycheque.
Are the exported hours scheduled or actually worked?
Actually worked — clock-in to clock-out, minus unpaid breaks. Scheduled hours are explicitly not used for payroll, because paying scheduled time overpays every shift someone left early and underpays every one they stayed late.
How is overtime calculated?
Per ISO week, using your organization's own weekly-hours compliance rule as the threshold (falling back to 40 if you have not set one). Splitting per week rather than per pay period is what keeps a two-week period from averaging a 50-hour week down to compliant.
One tool for the schedule, wired into the rest of your stack.
Free for a single location, no credit card. Every plan, including the free tier.