Review and approve attendance

What this achieves

The daily attendance grid shows reconciled attendance for a day — who was present, their first and last punch, their hours, and anything flagged. Approving days is what signs the record off before it is used downstream.

Required role: Administrator or Manager.

Steps

Go to Time & Attendance → Attendance.
Set the Date, and filter by Department, Location, or Status if you need to.
Read the rows, and click one to see that day’s punches.
Resolve anything under Flags.
Select the days you are signing off and select the approve action for the selected count.

Reading a day

Option	Description
Present	Worked as expected.
Partial	Worked, but short of the expected day.
Absent	No attendance recorded and no leave.
On Leave	Covered by approved leave.
Holiday	A holiday for that employee.
Weekend	A non-working day under their policy.
Remote	Worked remotely.

The distinction between Absent and On Leave is the one to watch. Absent means nothing explains the gap; on leave means it is accounted for. A run of absences usually means leave was never requested, not that someone did not turn up.

Example: if an HC Corp UK Ltd warehouse employee shows absent for a day everyone believed was booked off, the leave request is missing rather than the attendance being wrong.

Exceptions

Flags are what need a human. Each names a specific problem.

Option	Description
Missing punch	A check-in without a matching check-out, or the reverse.
Outside geofence	A punch taken outside the allowed area.
Face check failed	A face check did not pass.
Excessive overtime	Overtime beyond what the policy expects.
Overlapping punches	Punch pairs that overlap.
No show	Scheduled but no attendance recorded.

Work the exception queue before approving. Approving a day with an unresolved flag signs off a record you know to be questionable.

Correcting a punch

Opening a day shows its punches, and administrators can edit a punch time directly from there. A reason is required — the field will not accept a change without one, and it asks why HR is changing the time.

That reason is the audit trail. Write what happened, not “correction”.

Example: “Delivery ran late, employee confirmed 18:15 finish” explains the change to whoever reads it next year. A blank-sounding reason does not.

Employees have their own route for this — a correction request that routes through approvals. Direct editing is for corrections you are making on their behalf.

An employee’s month

Clicking an employee’s name opens their monthly calendar, which is the view to use when a pattern matters more than a single day — repeated lateness, a run of missing punches, or overtime building up week after week.

Approving in bulk

Days can be selected and approved together. Bulk approval is efficient and it is also where mistakes scale, so filter to a clean set first — approve the unflagged days in bulk, and handle flagged ones individually.

Correcting stops being possible once payroll has taken the day

A day payroll has already processed cannot be corrected here — not by a correction request, and not by editing the punch directly. Humavera refuses the change and says the day needs an off-cycle payroll adjustment instead.

So the window for this screen closes when the period is calculated, not when the period ends. Review and correct inside that window; afterwards the attendance record stands as it is and the money is dealt with on the payroll side.

Example: HC Corp UK Ltd’s March days are open to correction until the March run calculates. After that, an error found in March is Priya Raman’s off-cycle adjustment rather than Olivia Bennett’s punch edit.

What happens next

Approved attendance is the signed-off record, and the days sitting in the period are what a pay run reads when it calculates. Time reports read from reconciled attendance across a range, and their unapproved count is the fastest way to see what is still unsigned before a period closes.