Attendance

Clock-ins, late arrivals, and overtime — one record

Employees clock in and out in the browser. Late arrivals, half-days, and absences are marked automatically. Overtime flows straight into the next payroll run.

Clock in from a browser Overtime into payroll Corrections with a paper trail
Clock In & Out

One tap in the browser

No dedicated hardware. Employees open PawaHR, tap once, and the day's record starts. The same record is what payroll reads for overtime.

Clock in, clock out
Time & Attendance
Employees clock in when they start and clock out when they finish, in the browser on a phone or a computer. One record per person per day.
Auto clock-out at end of day
Time & Attendance
If someone forgets to clock out, the system closes the record at 23:59 EAT. The record shows it was auto-closed, so it's visible on the day and reviewable later.
On every employee's dashboard
Time & Attendance
A quick-action button for clock in and clock out sits on the employee's own dashboard, so nobody hunts for the page.
Status

Late, absent, on leave — marked automatically

Each day's status is decided by the day's record. No manual marking for the ordinary cases.

Late arrivals, after a grace period
Time & Attendance
Clock-ins after the day's grace period are flagged late. The flag is a fact about the day, not a deduction — payroll treats lateness as lateness, not as short pay.
Half-days and short hours
Time & Attendance
Days below the standard hours are marked as half-day, and days well below are marked insufficient — each on its own line, so HR doesn't have to guess what a short day means.
Leave days, on the same record
Time & Attendance
When a leave request is approved, the working days inside it are marked as on-leave in the attendance record — no separate calendar to keep, and a leave day never reads as an absence.
Corrections

Fix a wrong day, with a paper trail

People forget to clock out; sometimes a clock-in lands at the wrong time. Corrections are a request, not a silent edit — HR approves them, and the original stays on the record.

Self-correction requests
Time & Attendance
Employees request a corrected clock-in or clock-out time, with a reason. HR sees the request, approves or rejects it, and the decision is logged with the original and the new value.
HR overrides, logged
Security
HR can edit a record directly — for a walk-in correction or an obvious mistake. The original clock-in and clock-out are kept on the row, alongside who edited it and when.
Flags with a full history
Security
HR and managers can flag a record with a note. The flag history is preserved across re-flags, and after repeated flag/unflag cycles the record can only be re-flagged by an admin — one person can't quietly keep re-flagging the same day.
Overtime

Overtime priced by the day it falls on

Hours above the weekly threshold earn overtime, priced at 1.5× on normal days and 2× on rest days and public holidays, using each employee's own rest days. The total lands in the next payroll run.

See Payroll in Detail →
Per-employee rest days
Payroll
Not every team rests on Sunday. Each employee's profile can carry their own rest days, and overtime on those days is priced at the higher rate — the same engine, per person.
Public holidays, automatic
Payroll
Gazetted public holidays are already in the system, so overtime on them is priced at the higher rate without anyone re-entering the calendar each year.
To payroll, automatically
Payroll
Approved overtime flows into the next payroll run as its own line, visible on the payslip.
Team View

The right people see the right days

Employees see their own attendance. Managers see their department. HR and admins see the whole organisation, and admins can pull reports.

Own, team, or company
Time & Attendance
Employees see only their own record. Managers see their own department. HR and Admin see everyone, with filters by department, date range, and status.
Attendance reports
Reporting
Admins can pull a summary of any period — who was in, who was late, who was absent, who took leave — with a per-department breakdown, and export it to Excel.
Everything logged
Security
Every override, correction decision, and flag writes to the audit log — who did what, and when. If a day's record is ever disputed, the history of the row tells the story.
The Difference

What changes when attendance runs on PawaHR

Task Without With
Daily clock-ins
A book at the door, or nothing at all.
One record per person per day, in the browser.
Late & absent
Noticed by a supervisor, remembered at month end.
Marked on the day, visible to the right people.
Forgotten clock-out
Chased by message, edited in the book.
Auto-closed, visible, correctable with a reason.
Overtime
Estimated at the end of the month, argued over.
Priced per day, flows into payroll.
FAQ

Attendance questions, answered

What employers ask about attendance in PawaHR.

No. Employees clock in and out in the browser, on a phone or a computer. There's no fingerprint scanner or other hardware to buy.

PawaHR closes the record at 23:59 EAT and marks it as auto-closed. If the actual time was different, the employee can submit a correction request with a reason, and HR approves or rejects it.

No. Late arrivals are flagged on the attendance record; they don't reduce pay. If a company policy applies a deduction, that's set up separately as a custom deduction, so the employee always sees what was deducted and why.

Managers see their own department only. HR and admins see the whole organisation. Employees see only their own record. Everything is controlled by role, not by a setting.

No. Attendance is a clock-in record, not a location tracker. Geofencing isn't part of PawaHR today.

See attendance in action

Book a walkthrough and we'll show you a full day, from clock-in to overtime in payroll.