Payroll and exports

The payroll period export

Pick a date range and export it as CSV. The numbers come from punch data — what people actually clocked — not from what was scheduled, which is the distinction that matters when somebody stayed late.

The export computes, per person:

• Hours worked, with unpaid breaks deducted.
• Regular versus overtime hours, split at the threshold from your own max hours per week compliance rule — so the definition of overtime is yours rather than a hard-coded 40.
• Their rate, and the resulting regular, overtime and total pay.

It also returns warnings alongside the rows — a shift never clocked out of, a missing rate — rather than quietly producing a number that looks fine. Read them before you run payroll.

Manager and up, since it exposes pay for the whole organization.

Column presets

The same rows, arranged for whoever is importing them:

• Generic — every column, including rates and computed pay. Use this one for your own records.
• Gusto — name, email, regular hours, overtime hours.
• QuickBooks — employee, regular hours, overtime hours, rate.
• ADP — name, regular hours, overtime hours.

The narrower presets are shaped to match what those systems import comfortably; check against your own provider's current import template before a first run, since they change theirs from time to time.

Exporting a week

From the schedule page, download the week as CSV: one row per shift, with day, date, start and end, person, position, hours, rate and cost. Ordered day then time.

This is the plan rather than the record — useful for a printed rota, a board pack, or anywhere the question is "what are we running this week". For "what did we actually pay", use the payroll export.

Calendar feeds

Any team member can generate a private iCal feed of their own shifts and subscribe to it from Google Calendar, Apple Calendar or Outlook. It updates as the schedule does.

The URL is a bearer secret — anyone who has it can read that person's shifts. Revoking invalidates it immediately and a new one can be generated. See Guide for employees.

Doing it on a schedule

Everything above is also reachable through the API, with a scoped key, so a fortnightly payroll pull can be a cron job in your own infrastructure rather than a recurring calendar reminder for a human.