Attendance systems: the device is the easy part

A biometric machine costs a few thousand rupees and takes an afternoon to install. Almost every business we work with has one.

Almost every one of them also has somebody who, at the end of each month, exports a punch report, opens Excel, cross-checks it against a leave register, works out who was late and who did overtime, and hands a number to whoever runs payroll.

The device was never the problem. What happens to the punch record afterwards is.

What an attendance system is actually for

Where the value actually is

Capture

Biometric, face, mobile with location, or a web punch. Whatever suits the site.

Rules

Shift and week-off awareness, late marks, overtime, comp-off, loss of pay.

Payroll

Working days, overtime and LOP reaching the salary calculation without retyping.

Three stages, and most businesses have bought only the first.

Capture is solved and cheap — biometric, face, a mobile punch with location, a web login. Pick whatever suits your sites. It genuinely does not matter much, and the vendors who talk mostly about this are selling hardware.

The rules stage is where the work is. A punch at 09:42 means nothing until something knows this person's shift starts at 09:30, that a ten-minute grace applies, that Tuesday is their week off, that the four hours on Sunday were overtime and not a normal day.

The payroll stage is where the money is. If working days, overtime and loss-of-pay do not reach the salary calculation on their own, you have moved the manual work rather than removed it — and you have added a device to maintain.

What changed, and why "biometric plus Excel" got riskier

Two things landed at roughly the same time, and together they moved this from a convenience question to a compliance one.

The labour codes. The consolidation into four codes brings requirements that are attendance-derived rather than opinion: overtime payable at twice the ordinary wage rate, and a redefined wage base for statutory contributions. PF and ESI are calculated on that base, and the base depends on working days, overtime and deductions. Attendance that is not synchronised with payroll now risks miscalculating a statutory contribution, not just annoying somebody.

The DPDP Act. A fingerprint or a face scan is personal data, and a fairly sensitive kind. Collecting it needs notice and consent, and holding it needs real security — which most businesses running a decade-old attendance box have never thought about. We have written separately on what the DPDP rules mean in practice; the short version for attendance is that you need to know where the biometric templates are stored, who can reach them, and what happens when somebody leaves.

Neither of these is a reason to panic. Both are reasons that a spreadsheet sitting between your device and your payroll is now a liability rather than a saving.

This is not legal advice. We build systems, we are not labour law advisors, and the codes' implementation details continue to move. Confirm your specific obligations with somebody qualified. What we can tell you is which of them your software has to be capable of honouring.

Signs your current setup has stopped working

• Somebody spends more than a few hours each month reconciling attendance
• Overtime is calculated by hand, or worse, agreed by memory
• Employees dispute their attendance and there is no record they can see themselves
• Nobody can produce an attendance register quickly if an inspector asks
• Leave and attendance live in different places and disagree
• The person who understands the Excel file is a single point of failure
• Contract or shift staff are tracked entirely separately, on paper

Two or three of these is normal. Five means you are running a manual system with a biometric device attached to it.

What matters specifically in India

Shift and roster handling. Rotating shifts, night shifts, general shift, a factory running two or three of them. If the software assumes a nine-to-five, you will be working around it forever.

Week offs that are not Sunday. Common in manufacturing and retail. A leave request on someone's week off should not consume a day.

Overtime rules that hold up. Calculated from the shift definition, at the correct multiple, with a record showing how the figure was reached.

Loss of pay flowing through correctly. Pro-rated properly and landing in the payslip without anyone retyping it.

Contract and casual labour. Frequently the largest headcount on a factory floor and the group most often left out of the system entirely.

Multiple locations. Head office, factory, site. One view, one set of rules, different physical capture methods.

Attendance where there is no device. Field staff, drivers, service engineers. A mobile punch with location handles this; a wall-mounted machine cannot.

How to choose without buying the wrong thing

1. Test it against your actual roster. Not the demo data. Bring your shift patterns, your week offs, your grace period, and ask them to configure it while you watch.
2. Ask to see a payslip produced end to end. Punch record to salary figure, with overtime and LOP included. This single request separates the products that finish the job from the ones that stop at reporting.
3. Check the employee's own view. Being able to see your own attendance removes more disputes and more interruptions than any other feature.
4. Ask where biometric data is stored, and get the answer in writing. On the device, on your server, or on the vendor's cloud — each has different consequences under the DPDP rules.
5. Confirm the export. Your attendance records, in full, whenever you want them, without a support ticket.
6. Check it works when the internet does not. Factory connectivity is not always reliable; the device should buffer and sync.

Standalone, or part of something bigger

A dedicated attendance tool is cheap and quick, and it is the right answer if attendance is genuinely the only thing you want to fix.

But attendance, leave and payroll are the same data looked at three ways, and every boundary between systems is a place someone re-types a number. Once you are past about fifteen people, the integration is the value — which is the same conclusion we reached about leave management, and why our own AsteraPortal keeps shifts, attendance, leave and payroll in one place rather than shipping attendance as a separate product.

The honest summary

Buy the cheapest capture method that fits your sites. Spend your attention on whether the software can express your shift rules exactly, and whether the result reaches payroll without a spreadsheet in between. That is the whole decision.

If you want to see what that looks like with your own roster rather than a demo one, tell us how your shifts work and we will configure them during the walkthrough.