03 · Attendance

Punch data that payroll can trust.

Attendance is only useful if the number that reaches payroll is defensible. Shifts, capture, the rules that derive a day's status, and the regularisation trail are all one system — and payroll cannot run until the period is locked.

Punch acknowledgement
<500ms
Capture modes
4methods
Mobile capable
Offline
Before payroll runs
Locked

Capture

Four ways in, one record out.

Most workforces in this segment are mixed — desk staff, field teams and a factory or warehouse. All four capture methods write to the same attendance record with the same validation.

Mobile

GPS with geofence per branch or client site, works offline and syncs on reconnect, optional selfie and device binding to stop buddy punching.

Web

Browser punch for desk staff, with optional IP allowlisting per branch.

Biometric

Device integration by API or scheduled pull, with duplicate and clock-drift handling on ingest.

Bulk & manual

Supervisor marking for field teams and CSV upload for sites without connectivity.

Rules

A day's status is derived, not typed.

The rules engine turns raw punches into the statuses payroll consumes — and shows its working, so a disputed absence is a question with an answer.

ATT-1

Shifts & rosters

Fixed, rotational, split and flexible shifts with grace periods, minimum hours for a full or half day, and week-off patterns. Rosters assign by employee, team or branch, with a published schedule employees can see in advance.
ATT-2

Status derivation

Present, absent, half day, weekly off, holiday, on leave, on duty and overtime — derived from punches against the assigned shift and the attendance policy in force on that date.
ATT-3

Overtime

Eligibility by grade or employment type, computed against a configured threshold, at a rate you set, and routed for approval before it can reach payroll as an earning.
ATT-4

Regularisation

Missed punches, wrong shifts and on-duty days are corrected through a request with a reason, routed to the manager. The original record is never overwritten — the correction sits alongside it with its approval trail.
ATT-5

Holiday calendars

Per company and per branch, because a national holiday list is wrong the moment you open an office in a second state. Optional and restricted holidays supported.
ATT-6

Period lock

Attendance and leave lock on the cut-off date. After that, changes flow to the next period as an adjustment or trigger a retrospective recalculation — never a silent edit to a paid month.

Leave

Balances that survive an audit.

Leave is where accrual rounding, carry-forward caps and encashment rules quietly diverge between the policy document and the system. Every one of them is explicit configuration here.

  • Leave types with accrual frequency, pro-rata on joining, and eligibility after probation
  • Carry-forward caps, lapse rules and encashment eligibility per type
  • Negative balance permitted or blocked, configured per type
  • Holiday and week-off treatment inside a leave span — the sandwich rule, stated explicitly
  • Compensatory off earned against approved overtime, with its own expiry
  • Approval routing with delegation when a manager is themselves on leave
Payroll link

Loss of pay

Unpaid absence flows to payroll as loss-of-pay days, valued on the proration basis you configured — not on an assumption the engine made for you.

Payroll link

Encashment

Earned leave encashment computes on your policy’s basis, and at separation applies the exemption available under section 10(10AA) rather than taxing the whole amount.

Payroll link

Exit interaction

Leave applications are blocked beyond a confirmed last working day, and the balance at exit feeds the settlement automatically.

Mobile is the primary surface

For most of your workforce, attendance and leave are the product — they will open little else. Both work offline, sync on reconnect, and never lose a punch to a dead network in a basement or a client site.
NextPayroll — the calculation engine
Continue →