Review the hours before choosing a file format
The dashboard’s payroll export uses the same daily engine as Timesheets. It includes applied corrections, configured break deductions and daily overtime allocation. A day with a blocking exception contributes no export rows. Open attendance is not silently converted into a plausible full shift.
This creates a useful review boundary, but it does not decide what a worker is owed. Payroll must investigate excluded records and resolve or otherwise handle genuine work under its own obligations before payment.
Choose the right data product
Scroll the table sideways to read all columns.
| Output | Purpose |
|---|---|
| Generic CSV/JSON hours export | Calculated shift hours, worker/site context and correction indicators |
| Named ERP-oriented layouts | Attendance hours for mapping into a specific receiving workflow |
| REST event API | Raw accepted attendance events, rather than reviewed daily hours |
| PDF/Excel reports | Human review and sharing through the report workflow |
Named layouts exist for SAP CATS, SuccessFactors, Oracle HCM and Workday. They are downloadable outputs, not certified native connectors. The receiving system may need transformation, configured identifiers, time types and validation.
Keep identity mapping explicit
A customer’s employee ID and payroll ID serve different purposes. The payroll ID keys the worker into named ERP-oriented formats. Workers without it are reported as unmapped and excluded from those formats. Generic exports can still include records without a payroll ID, so check the format and summary together.
Illustrative review: two workers have complete eight-hour records, but one lacks a payroll ID. A named-format file includes only the mapped worker. The reviewer must account for both the exported hours and the excluded worker before declaring the handoff complete.
Reconcile with the receiver
Check record count, employee count, work dates, hours, exclusions and the receiving system’s import response. Decide how a corrected period will be reissued without duplicating pay inputs. A downloaded file is not evidence of successful import.
Scheduled ERP delivery is not an available commercial promise at present. The signed-webhook dispatcher is implemented, but recurring dispatch scheduling remains an operational prerequisite. Use the documented download or pull workflow and confirm any delivery requirement during rollout.