Attendance management system: capture, rules and payroll in one

The full chain that turns presence into payroll: a capture method (usually a biometric terminal), the rules that interpret punches (shifts, grace periods, late penalties, paid leave), and the outputs (a live register, reports and salary). If any layer is missing, people fill the gap with spreadsheets — which is the system silently failing.

The software is one layer; the system is all three. Plenty of attendance software only reads punches from one brand of machine and stops at a report — you still need the machine, the rules and the payroll from somewhere. When we say system, we mean the machine (through authorised dealers), the cloud software, the rule engine and the payroll are one purchase.

Judge each candidate on exact-model compatibility, the biometric recovery workflow, one register across branches, and whether attendance produces a salary figure or only an export. Require written confirmation and a test punch; a brand-level support claim is not enough.

The machine is a small one-time cost (entry fingerprint terminals sell for a few thousand rupees in the Indian market), installation is one-time through a local dealer, and software is recurring. AionHRMS prices the software as a flat annual subscription by headcount band with unlimited terminals and sites, invoiced only after go-live, so adding a terminal or a branch never grows the bill. One written quote can cover all three parts.

Usually yes. Terminals speaking iClock/ADMS — most eSSL and ZKTeco units — and Realtime terminals repoint to our server from their own settings menu, keeping the fingerprints already enrolled. Send the model and serial and we confirm before you spend anything.

No. The terminal talks to our server directly and you use a browser. There is no desktop client and no local database.

Both, for supported commands. Employee profiles and access instructions can be pushed to compatible devices. Biometric payloads are different: compatible iClock templates may be reused where formats agree, while Realtime biometrics are enrolled at the terminal. Door release also depends on the device model.

One account, with each branch as its own location holding its own terminals and administrators. Head office sees all of them together.

No. One flat annual subscription by headcount band covers every branch and every terminal in the account — a second location is not a second bill.

For a single office under about fifty people, almost any current fingerprint or face terminal will do the job, and the hardware choice barely matters. Spend the decision on the software instead: pick something cloud-based so attendance is not trapped on one PC, and something device-agnostic so your second office does not force a second system. That is precisely the gap AionHRMS fills.

Yes. Each employee carries their own duty times — single or double shift — and punches are assigned to the correct shift automatically, with break and overtime events captured distinctly. Late marks are counted against a grace period you configure, and salary is computed from the shift units actually present, with paid leave applied and advances settled. Different teams on different timings is the normal case, not an exception.

It computes salary. Each employee has duty times and a salary configuration; the system derives gross from shift units present plus paid leave, applies the late rule you configured, and settles recorded advances. The monthly payroll report and per-employee attendance calendar are the outputs. Filing of statutory returns is not done by AionHRMS.

Overtime-in and overtime-out are captured as distinct events and appear in the attendance record with their minutes. There is no overtime multiplier in the salary computation today; if you need overtime paid at a specific rate, tell our team before you commit.