Payroll Attendance
Payroll → Employees → Payroll Attendance (/attendance) — the paid days, loss of pay (LOP) and minute totals each pay run is computed from. Unlike Employee → Attendance (uploads and corrections), this page shows what payroll will actually pay by. Requires payroll:read to view and payroll:manage to import or edit.


What it is
Payroll attendance is a per-employee roll-up for a period, kept by payroll so a run is computed from a stable record rather than the live HRMS calendar. It gets there in one of two ways:
- Sync ZapHRMS — pulls the rows straight from ZapHRMS for the period shown. It runs in the background and a strip under the toolbar tracks it. The button appears only for organizations whose payroll is integrated with ZapHRMS.
- Import CSV — upload attendance from a spreadsheet or another system.
When a pay run is computed, the figures for each employee are frozen onto the run (calendar days, working days, week offs, holidays, present days, paid and unpaid leave, LOP and the late and overtime minutes) and are available to payslip templates. A later correction therefore needs the run to be re-computed — see Pay Runs.
The period
The period is any from-and-to date, not just a calendar month. Pick a pay run to use its dates, so a 26th-to-25th cycle reads as one period; the arrows move both dates by a month. An imported summary only shows when the period matches the one it was imported for.
The table
| Column | Meaning |
|---|---|
| Code / Name / Department | The payroll employee |
| Calendar days | Days in the period |
| Working | Days the employee was expected to work — everything that is not a week off or a holiday. With no rows, payroll falls back to the working days of others at the same location, and to the length of the period if there are none |
| Week offs / Holidays | Non-working days in the period |
| Present | Days actually attended — what a per-day allowance is paid on. Week offs, holidays and leave are not attendance |
| Leave | Leave days (hover for Paid vs Unpaid) |
| Absent | Days absent |
| LOP | Loss-of-pay days: an absent day is a full LOP day, the unworked half of a half day is half, and leave without pay is LOP |
| Late / Overtime | Total minutes late and overtime minutes |
Paid days are not shown here. The pay run works them out as the period less LOP, and the pay group's proration basis decides whether week offs and holidays are in the period — Calendar days and Fixed 30 pay them, Working days does not.
A row can be edited in place (Edit summary) to correct the totals for the period, and the per-day detail can be opened from the row. Edits are saved as attendance for payroll only; they do not change the HRMS calendar.
Getting data in and out
- Import CSV accepts two shapes: Day rows (detailed attendance keyed by employee and date) and Summary (per-employee totals for the period shown — enough for payroll calculation). The summary exported from ZapHRMS Team Attendance imports as it is. Importing a complete period in one format replaces the other for the affected employee.
- Export → Day rows — the period's stored day rows in the format the import reads. Correct them in a spreadsheet and import the file back: a row is keyed on employee and date, so the second import fixes the period rather than duplicating it.
- Export → Summary — the roll-up as shown. It can be imported back as the authoritative payroll input for the period.
The i icon at the top opens the same notes in the app.
Relationship to ZapHRMS
| ZapHRMS | Payroll |
|---|---|
| Attendance (uploads, manual punches, overrides) | Payroll attendance for the period |
| A manager approves corrections in Team Attendance | No approval here — approved corrections flow into the next sync or summary export |
| Live calendar | Pay-period record |
:::tip When a day moves after compute
If an employee's leave is approved after a run is COMPUTED, sync (or import) the period again, then open the run and use Re-compute (see Pay Runs). Prefer fixing the source in ZapHRMS over editing payroll attendance by hand.
:::