Payroll export
Payroll needs to know who worked what. The schedule knows. In most departments those two facts are connected by somebody re-typing a spreadsheet.
What makes this error-prone by hand
The published schedule is not what happened. Between publication and the end of the period there are swaps, late leave, open shifts picked up by someone else, and admin edits. Each one is correct in the product and invisible in whatever was printed at the start of the month.
So re-typing from the published schedule is reliably wrong, in a way that favours nobody consistently — which is worse than a systematic error, because there is no pattern to catch.
What the export contains
One row per worked assignment, drawn from the live schedule:
| Field | What it is |
|---|---|
| Person | The staff member who actually worked it |
| Date | The shift's start date |
| Shift | The template's name, as the department calls it |
| Start, end | Actual span, including multi-day shifts as one row |
| Hours | Duration, computed from the span |
| Type | Day, night, call, or whatever the site defines |
Multi-day shifts appear as one row with their real span, not as three single-day rows that have to be recombined. Shift type comes through so differentials can be applied by whatever rules your payroll runs on.
What it deliberately does not do
It does not compute pay. Rates, differentials, overtime rules and contract terms are payroll's business and they vary by employer, by contract and by jurisdiction — a scheduling product that guessed at them would be confidently wrong. The export provides the hours and the shift classification; the rules stay where they belong.
Common questions
Does the export reflect swaps?
Yes. It is computed from the live schedule, including every accepted swap, granted leave request and claimed open shift, so it describes what happened rather than what was originally published.
What format is it?
CSV, one row per worked assignment, with the person, date, shift, start and end, hours, and the shift's type. It is designed to be loaded or mapped into a payroll system rather than to integrate with one specific vendor.
Related
- Audit trails — for the question behind a payroll query, which is usually "when did this change".
- Schedule publishing