Attendance

How a day is recorded

Each attendance record holds a check-in timestamp, a check-out timestamp, any break deduction, and a derived status. The status is computed from your policy rather than chosen by hand, so the register stays consistent regardless of who is administering it that week.

1. The employee checks in from the portal or the desktop app.
2. The system compares the time against the employee’s shift start plus the grace window.
3. At check-out, worked hours are computed and the configured break is deducted.
4. Status is derived: present, late, half-day or absent.
5. Leave and holidays override the status where they apply.

Shift settings

Shifts are assigned per employee, not per company, which is what makes rotating rosters and flexible teams workable in one system.

Late policy

A late mark on its own is usually not the outcome an employer wants; the policy is normally cumulative. Configure how many late marks convert into a half-day deduction and over what period they are counted.

A common configuration is three late marks in a calendar month equalling one half-day. Set the counting period to match your payroll cycle rather than a rolling window, or the deduction will land in an unexpected month.

Corrections

When somebody forgets to check in or out, an administrator with attendance permission adds or corrects the entry. The record keeps who corrected it and when, so the change can be traced at month end.

The payroll export

Export the register for any date range as CSV. The columns are stable, so a spreadsheet or payroll import mapping built once keeps working.

employee_code,name,department,present_days,absent_days,
late_marks,half_days,leave_days,holidays,worked_hours,
overtime_hours,period_start,period_end

If payroll runs inside Employee Desk, it reads the register directly; see data exports for the payroll files.

Related