On this page
What is attendance management software?
It records when an employee arrives and leaves and compares it with their shift, so lateness, early leave, absence and overtime are calculated rather than guessed. People look for it as a biometric attendance system, time and attendance software or shift scheduling software; they all describe one cycle.
In Anzma it is a module in the HR system. It takes employees from employee management and sends its monthly summary to payroll software, so attendance numbers are never retyped into a salary sheet or lost between two files.
We state the limits upfront: there is no native mobile app, and we do not ship a direct driver for every device brand. What exists is an open endpoint that receives punches, file import, and check-in from the browser, which together cover most real setups, as explained below.
- Punches from devices, files and the browser
- Shifts, holidays and rosters
- Lateness, absence and overtime calculated automatically
- A monthly summary that flows into payroll
How is a shift calculated from punch to payslip?
The system pairs an employee’s punches for the day into sessions according to that day’s shift, then compares them with the start and end times and the grace period. Time beyond the shift past a minimum counts as potential overtime, shortfalls count as lateness or early leave, and a working day with no punch, leave or holiday counts as absence.
A purely illustrative example: a 9 to 5 shift with 10 grace minutes. The employee punches in at 9:20 and out at 18:10. Result: 20 minutes late, depending on your grace policy, and 70 minutes of overtime after the shift waiting for approval. At lock, those figures feed payroll as a lateness deduction and overtime pay for the approved portion only.
The calculation runs daily as a scheduled job and can be rerun on demand after a punch is corrected. It is safe to repeat, so rerunning never doubles the effect.
| Item | Scheduled | Actual | Result |
|---|---|---|---|
| Arrival | 9:00 | 9:20 | 20 minutes late |
| Departure | 17:00 | 18:10 | 70 minutes overtime pending approval |
| Shift grace | 10 minutes | — | Per company policy |
| Effect on pay | — | — | Lateness deduction plus approved overtime |
How do you connect biometric devices?
Each device is registered under “Devices” and receives its own access token, shown once and stored only as a hash. The device, or the sync program that ships with it, then pushes punches to your company address through a documented API, with the employee code, timestamp and direction when available.
The endpoint is designed for ZKTeco-style devices and similar: it accepts up to 500 punches per request, ignores duplicates, and stores unknown codes as unmatched punches to link to employees later. It rejects punches older than 35 days or from an employee of another branch, so a leaked token cannot back-date or cross branches.
We do not provide a direct driver for every brand. If your device can push data over HTTP, or has sync software that does, it can connect; otherwise importing a file is a practical alternative. We check your device with you in the meeting before any commitment.
| Method | Supported? | Note |
|---|---|---|
| Biometric device through the API | Yes | A token per device, via the device or its sync software |
| CSV or XLSX import | Yes | Includes ZKTeco-style exports, with column mapping |
| Browser check-in | Yes | With optional geofence and IP rules |
| Manual entry by HR | Yes | A required reason, recorded in the audit log |
| Native mobile app | No | The web app works on a phone instead |
How are shifts, rosters and holidays managed?
A fixed shift has a start, end, break and grace; a flexible shift has core hours and a required total; a night shift crosses midnight; a split shift has two blocks in a day. Each shift has its own weekly rest day, defaulting from attendance settings.
Shifts are assigned to an employee or department over a date range, or you build a rotating weekly pattern in the roster calendar grid. A single day can be overridden. Official holidays live in a calendar per country or branch; Anzma seeds current-year holidays as data for you to review, and lunar-calendar holidays are entered each year.
Shift-based businesses such as factories, hotels and clinics gain most from rosters, because they build a month once and then adjust only the exceptions.
| Type | Description | Example |
|---|---|---|
| Fixed | Start, end, break and grace | Office 9 to 5 |
| Flexible | Core hours and a required total | Technical team |
| Night | Crosses midnight | Security or night operations |
| Split | Two blocks in a day | Restaurant or training centre |
How are exceptions and forgotten punches handled?
A missing punch is not guessed. The system lists it under “Exceptions” with its reason: an arrival with no departure, or overtime not yet approved. The owner reviews and decides. They can add a manual punch with a required reason recorded in the audit log, void a wrong one, then recompute.
Overtime counts toward pay only after approval, either requested by the employee through employee requests or approved in bulk by the owner. That rule stops overtime inflating just because someone stayed late without being asked.
Exceptions follow a predictable path so they are cleared before the monthly lock rather than after.
- 1
Exception detected
The daily calculation adds a missing punch or unapproved overtime to the list.
- 2
Owner reviews
They open the employee record and see their punches and the day’s shift.
- 3
Decision
Add a manual punch with a reason, approve the overtime, or treat the day as absence.
- 4
Recompute
The day is recalculated and leaves the exceptions list.
How are overtime, lateness and absence hours calculated?
Overtime is counted after the shift ends and past a minimum number of minutes you set, with holiday and rest-day overtime kept separate from daily overtime. Hours are multiplied by a rate that starts from the company’s country rules and can be adjusted by company policy, with values reviewed against the official source.
Lateness can follow tiers: minutes late and repeats in a month determine the deduction in minutes or days, with a monthly cap. Absence is deducted using the day basis set in payroll. These policies depend on what you configure, and we print no fixed rates here because the rules change.
An approved leave, a mission or an official holiday automatically counts as a day that is not absence, because the module reads approved leave.
Can attendance be recorded from a phone or remotely?
An employee linked to a user account can check in and out from the “My attendance” page in a browser, on a computer or phone. There is no native mobile app, but the page works on small screens.
Check-in can be restricted to a geofence around the branch coordinates with a radius you set, and/or to an allow-list of IP addresses, and you choose whether one rule or both must pass. The browser shares location with the user’s permission, so this is not a substitute for a biometric device where you need stronger assurance.
Managers get a “My team” view showing the team’s status today and month counters. Biometric devices suit workers on site; browser check-in suits office staff or limited field work.
How does attendance flow into payroll?
At month end each employee’s attendance is gathered into a summary with working days, absence, lateness minutes and approved overtime. The owner locks the summary once exceptions are cleared, and the payroll run reads fixed numbers that do not change after pay.
By default payroll refuses to approve a run before the lock, so you are not surprised by a gap between attendance and pay. If a correction is needed after locking, the summary is reopened with a dedicated permission and locked again, and the change stays recorded.
Reports cover lateness, absence, overtime and attendance summary, and can be exported by users with the export permission.
What do the daily board and the reports show?
The daily board shows who is in, late, absent or on leave, by branch and department, so a manager knows at half past eight who has not arrived instead of waiting for month end. From any row you open the employee’s record, punches and the day’s shift.
The monthly timesheet shows each day’s status for an employee: present, absent, leave or holiday, with lateness, overtime and actual minutes worked. Reports on lateness, absence, overtime and summary show which departments are late most often or which employees carry the most overtime.
A practical case: you notice one department exceeds its overtime budget every month, so you review its roster rather than just paying the hours. That helps you control cost before it climbs.
- A daily board of present, late and absent
- A monthly timesheet per employee
- Lateness, absence and overtime reports
- Export under its own permission
Does it suit multi-branch companies and different countries?
Yes. Each branch has its own geofence, IP list and timezone, and a device punch is interpreted in the employee’s branch time. If the device sends an offset it is honoured; if it sends none, the branch’s local time is assumed. A punch from an employee of a different branch than the device is rejected.
The weekly rest day differs between Egypt and Saudi Arabia and even between companies, so you set it per shift, and Anzma seeds official holidays that you review each year. A group with companies in two countries runs each with its own settings.
Branch and user limits follow the general plan; see pricing.
How does attendance software differ from a manual register?
A paper register or spreadsheet depends on whoever fills it in and checks it, and struggles with night shifts, changing rosters or lateness tiers. Disputes about when someone arrived stay unanswered. The software keeps every punch with its time and source and applies one rule to everyone.
Most importantly it locks the month and ties it to pay, so nobody changes a number after salary is released without a trace. Necessary manual edits require a reason and appear in the audit log.
| Aspect | Register or Excel | Anzma |
|---|---|---|
| Recording time | Handwritten | Device punch, file or browser |
| Night and changing shifts | Hard | Shifts and rosters |
| Lateness and overtime | Manual formulas | Automatic under one policy |
| Exceptions | Forgotten | A list cleared before lock |
| Link to pay | Manual copying | A locked summary read by payroll |
| Effect of edits | No trace | A reason and an audit log |
How are shifts used in a factory, clinic or school?
A factory with three shifts defines morning, evening and night, builds a rotating weekly pattern that moves each group between shifts, and assigns it to departments in one step. Night-shift overtime that crosses midnight is credited to the right day.
A clinic open in two sessions suits the split shift for a doctor who attends morning and evening, with reception on flexible shifts. A school tracking teachers and administrators needs only a start and end time, plus the term breaks in the holiday calendar.
It is one screen: build the roster, review attendance, lock the month. If you need a special shift for a season, add an override for a date range without touching the base roster.
How is attendance data protected and permissions controlled?
A device token is shown once and stored only as a hash; you can rotate it or disable the device and it stops at once. The endpoint is rate limited and rejects very old or far-future punches, so a leaked token cannot rewrite last month.
Permissions are granular: who sees the daily board, who adds or voids a manual punch, who approves overtime, who locks the monthly summary, who manages devices and tokens, and who changes policy. Employees see their own attendance, managers their team, HR everyone, and no one holds everything by default.
It is good practice to separate who approves overtime from who manages devices. Every manual edit carries its author and reason in the audit log for any later review.
How do you get started with attendance?
Start by entering employees with their codes, because the code is the key that matches device punches to names. Then create a default shift and your holidays, register your devices, and pilot one department for a week before rolling out. The module is not tied to a plan feature; the general limits apply, see pricing.
It fits shift-based operations including factory management software, clinic management software, school management software, contracting company software, hotel management software and gym management software. It is part of a complete HR system.
Setup time depends on size: hours for a single-shift company, days for several branches and shifts. Decide beforehand the lateness and overtime policy in your written rules, because the system applies what you configure and does not guess it. If your rules are unwritten, this is a good moment to document them.
To look at your biometric device and choose the best way to connect it, book a free online meeting.
Frequently asked questions
Does it connect biometric devices, and which kinds?
It receives punches through an API with a token per device, so it works with any device or sync program that can push punches over HTTP, including ZKTeco-style devices. We do not ship a direct driver for every brand. File import in CSV or XLSX is the alternative, and we will check your device with you before any commitment.
Can attendance be recorded from a phone?
Yes, from the browser on a phone through the “My attendance” page for an employee linked to an account, with optional geofence and IP rules. There is no native mobile app. Browser check-in gives weaker assurance than a biometric punch, so use it for office staff and limited field work.
How are overtime and lateness hours calculated?
The system compares each day’s punches with the shift and grace period: time beyond a minimum after the shift is overtime and a shortfall is lateness. Overtime multipliers and lateness deduction tiers come from company policy, with defaults reviewed against the official source. Overtime counts for pay only after approval.
Does it support night shifts and rosters?
Yes. It supports fixed, flexible, night shifts that cross midnight, and split shifts. Shifts are assigned over date ranges or built as rotating weekly patterns in the roster grid, with an override for a single day. Holidays are managed in a calendar per country or branch.
How are exceptions such as a forgotten punch handled?
A missing punch appears in the exceptions list with its reason. The owner either adds a manual punch with a required reason recorded in the audit log, approves the overtime, or treats the day as absence, then recomputes. Exceptions are cleared before the monthly summary is locked.
Does attendance flow into payroll automatically?
Yes. Each employee’s monthly summary is locked with absence days, lateness minutes and approved overtime, and the payroll run reads it. By default payroll requires the lock before approval so numbers cannot change after pay is released. This link needs the payroll module enabled.
Can check-in be limited to the branch location?
Yes. You set the branch coordinates and a radius, and/or an allow-list of IP addresses, and choose whether one rule or both must pass. Location depends on what the employee’s browser shares with permission, so it does not replace a biometric device where you need stronger assurance.
What if a device’s employee code does not match?
The punch is stored as unmatched rather than lost, and you link it later from the punch log to the right employee. Codes are matched exactly first, then ignoring prefixes and leading zeros, so 7, 0007 and EMP-0007 resolve to the same employee.
Is there free attendance software?
We do not offer free attendance software. The module is part of a paid platform sold in plans, shown on the pricing page. You can book a free online meeting where we show the daily board on your own data and check the biometric device you already own.
Part of the product line
HR software
Five modules on one employee record: file, contract, punch, leave and pay, with the payroll entry flowing into accounting and cost centres automatically.
Rate this page
Did you find this useful? Your rating helps others.
No ratings yet.


