Attendance that payroll can trust
Attendance management fails when it is only a daily register. In Zeba, punches, grace, night-shift dates, and regularizations are the same data payroll uses for payable days and LOP. That is the bar for Indian office and field teams - not another list of biometric buzzwords.
Work types drive punch rules
Assign WFO, WFH, Hybrid, or Field. Geofence requirements and live GPS during working hours follow that assignment. Field engineers and warehouse staff should not share the same check-in policy as a WFH role - Zeba makes that configuration explicit per employee.
Geofence and GPS
Geofence punches enforce where a valid check-in can happen. Check-in can record GPS distance. Live map visibility, when enabled, is limited to working hours so managers can verify duty without always-on tracking after shift end. The same distance trail can support reimbursement for tracked kilometres.
Grace, Present but Late, and night shifts
Grace windows turn a slightly late punch into Present but Late instead of a hard Absent when policy allows. Night shifts stay keyed to the shift date - punches after midnight do not invent a new attendance day. Those details prevent the classic payroll fight where the roster says night of the 10th and the register shows the 11th.
Regularization with an audit trail
Missed punches and exceptions go through regularization - request, approve, record - instead of silent edits. That keeps attendance defensible when salary is questioned. Unpaid absence still flows to leave and LOP so pay matches the calendar.
FAQ
Do all employees use the same attendance rules?
No. Work type (WFO / WFH / Hybrid / Field) controls geofence and live GPS toggles.
What does Present but Late mean?
The day counts as present after a punch inside the grace window, with a late status - useful for payroll and manager follow-up without marking Absent.
Why key night shifts to shift date?
So post-midnight punches stay on the correct duty day for attendance and pay, not the next calendar date.
