This guide explains Amir’s attendance workflow: defining work shifts, recording or importing entry/exit logs, calculating monthly attendance, and preparing data for payroll.
| Area | Purpose |
|---|---|
| Work shifts | Define start/end time, Thursday handling, floating entry window, break time, leave allowance, and overtime/mission coefficients |
| Attendance logs | Record daily entry and exit for each employee, make manual corrections, and review calculation details |
| Attendance import | Preview and import device or external files, with duplicate rows ignored or replaced |
| Monthly attendance | Summarize work days, presence, absence, overtime, mission, leave, Fridays, and holidays |
| Payroll creation | Create a payroll from confirmed monthly attendance and an active salary decree |
Important work-shift fields include:
Changing a shift’s paid leave can affect the leave balance of employees assigned to that shift. Review active employees before changing live shifts.
An attendance log stores employee, date, entry time, exit time, and description. After calculation, these values can be viewed or corrected:
Editing a log marks it as manually corrected. Use recalculation when you want the system to apply the current rules again.
During import, choose the import type, date range, and duplicate behavior. Duplicate rows can be ignored or replaced. Before final import, review the preview page, especially unknown device IDs that are not mapped to employees.
Monthly attendance is calculated for one employee, a start date, and a duration of 28 to 31 days. The monthly page also shows days without logs so absences and holidays can be reviewed.
After attendance is confirmed, and if the employee has an active salary decree, payroll can be created from the monthly attendance page. If attendance changes after payroll is created, review the payroll too.