Read time reports
What this achieves
Section titled “What this achieves”Time reports summarise reconciled attendance across a date range rather than a single day. They answer how much was worked, how much overtime accrued, and where exceptions are concentrating.
Required role: Administrator or Manager.
- Go to Time & Attendance → Reports.
- Choose the report type.
- Set the range with From and To.
- Choose how to Group by, and narrow by Department, Status, or Employee if you need to.
- Read the tiles and the table, or export with CSV or Excel.
The three reports
Section titled “The three reports”| Option | Description |
|---|---|
| Attendance | Days present and absent, hours worked, and attendance percentage. |
| Overtime | Overtime hours and days, and days flagged as excessive. |
| Exceptions | Days carrying flags, broken down by the kind of exception. |
Grouping
Section titled “Grouping”| Option | Description |
|---|---|
| Employee | One row per person. Use it for an individual conversation. |
| Department | One row per department. Use it to compare parts of the business. |
| Team | One row per team. |
Group by department first and by employee second. Starting at the individual level makes a pattern that belongs to a whole team look like one person’s problem.
Example: if overtime at HC Corp UK Ltd is concentrated in Operations rather than spread across all 18 people in it, the department view shows that immediately and the employee view does not.
Exceptions worth acting on
Section titled “Exceptions worth acting on”The exception columns name specific problems — missing punches, no-shows, and out-of-geofence punches among them — plus an Unapproved count.
A persistent count in one column usually points at configuration rather than behaviour. Repeated out-of-geofence punches often mean a geofence radius drawn too tightly, not a workforce punching from home.
Example: if one HC Corp UK Ltd location produces most of the out-of-geofence flags, check the radius on that site’s geofence before treating it as an attendance problem.
The Unapproved count is the operational one: it says how much of the period nobody has signed off. Run it before a period is calculated rather than after, because a day payroll has already processed can no longer be corrected in attendance.
Reports read reconciled attendance only
Section titled “Reports read reconciled attendance only”Everything here is built from reconciled days. A range that returns nothing usually means no reconciled attendance was found for those filters, and the empty state suggests widening the range.
A day that has not reconciled — because a punch is still unpaired and auto-close is off — is not in these figures. Clear the exception queue before treating a report as complete.
Exporting
Section titled “Exporting”CSV and Excel exports carry the current filters and grouping. Note the range and grouping on anything you circulate, because a figure without them invites the wrong conclusion.
What happens next
Section titled “What happens next”The reports are how a period is checked before it is paid, so the unapproved and exception views are worth running while the days can still be changed. Patterns worth acting on usually belong elsewhere: persistent overtime is a rostering or headcount question, and repeated exceptions are usually a policy or geofence setting.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved