The usual arrangement
The device works. Everything after it is manual.
A biometric attendance system is two things sold as one. The first is the reader on the wall — an ESSL or equivalent unit that identifies a person by fingerprint or face and writes a timestamp, in place of a register at the gate or a card everyone ends up sharing. The second is the software behind it, which decides what those timestamps are worth: the shift each punch belongs to, the overtime it earns, the leave it sits against, and the monthly figure a salary is calculated from. The first half can be bought in an afternoon. The second is where the month actually gets closed.
Most plants already own the hardware — ESSL on one wall, a different brand on another, whatever was bought the year each block went up. The readers are mounted, people punch, the logs are there. The problem starts after that: somebody exports a file at month end, opens it next to the shift roster and the leave register, and reconciles three sources by hand under a payroll deadline.
That reconciliation is where the disputes come from. A missing punch and an approved leave look the same in a raw log. Night shift lands on the wrong day. Overtime gets computed against a standard day instead of the shift the person actually worked. By the time it is corrected, it has been corrected in Excel, and no system remembers why.
The devices were never the gap. The gap is that nothing connects them to the rules that decide what a day is worth.
What the system handles
Attendance is a payroll problem, not a hardware one.
Shifts, including the awkward ones
General, rotating and night shifts, with the day boundary in the right place so a shift that ends at 6am belongs to the night before.
Overtime, by your rules
OT calculated against each shift's own hours, with grace periods, late marks and half-days applied the way your policy already works — not the way a product decided.
Leave, tracked against the log
Casual, sick and earned leave reconciled against actual punches, so an approved leave and a missing punch stop looking identical.
Payroll export, not payroll retyping
The month closes into the format your payroll already accepts. Nobody exports from the device software and fixes it in Excel.
Running now
In production at a manufacturing company.
ESSL readers feed a system we built and run today. Attendance is not a standalone tool in it — it sits inside the ERP that also carries the approvals, the documents and the reporting, so a shift, a leave approval and a payroll line are the same record seen from different places.
The same project replaced a paper process: printing a document, walking it for signature, filing the copy. Attendance was the part that had to be exact first, because it is the part people notice in their salary.
Why not a standalone app
A second system means a second version of the truth.
Attendance software that lives on its own has to be reconciled with everything else — HR records, leave approvals, payroll, the plant roster. Every reconciliation is a chance for the two to disagree, and they always eventually disagree. Built into the system that already holds those records, there is nothing to reconcile: the approval that grants a leave is the same row that explains the missing punch.
Which is also why attendance is usually where we start. It is narrow, it is verifiable within a month, and it proves the thing works before anyone commits the rest of their operations to it.
Questions we get asked
The answers before the first call.
What is a biometric attendance system?
A biometric attendance system records when each person starts and stops work by reading a fingerprint or face at a device on the wall, instead of a register or a card. The device is the easy half. The half that decides pay is the software behind it: applying your shift, overtime and leave rules to that punch log and closing the month into a file payroll accepts.
Do we have to replace our ESSL devices?
No. We integrate the readers already on your walls. The device keeps doing what it does well — reading a finger and writing a punch — and the rules that decide pay move into a system that knows your shifts, your grace periods and your leave policy.
We do not use ESSL — will this work with our devices?
Yes. ESSL is what we name because it is what we run in production, not because it is a requirement. We work from whatever the reader exposes — its SDK, its push protocol, or the database it writes to — and the shift, overtime and leave rules sit above that layer rather than inside it. Changing the brand on the wall changes the connector, not the system. Tell us the model and we will confirm before you commit to anything.
Will it handle night shifts and rotating shifts?
Yes, including the day boundary. A shift that ends at 6am belongs to the night before, and overtime is calculated against each shift's own hours rather than a single company-wide day. Grace periods, late marks and half-days follow the policy you already run.
Does it work with our payroll software?
That is the point of the build. The month closes into the format your payroll already accepts, so nobody exports from the device software and repairs it in Excel first.
Is this running anywhere today?
Yes — it is in production at a manufacturing company, handling shifts, overtime, leave and the monthly payroll export. It is usually where we start with a new client because it is narrow, verifiable within one month, and it proves the approach before anyone commits the rest of their operations to it.
Who owns the system once it is built?
You do — the software, the data and the devices. The attendance database runs in an account in your company's name, the punch history exports in a format anyone can read without our software in front of it, and the biometric templates stay exactly where they are, on the readers you already bought. Nothing about the arrangement makes the hardware ours. Source code, infrastructure, credentials and the written description of your shift, overtime and leave rules are handed over as part of the build, so your own IT person or another vendor can maintain it. That matters more here than on most projects, because attendance decides what people are paid and it has to keep working in a month when nobody is available to fix it. No lock-in, and no retainer you cannot end.
Tell us what you are running now.
Which ESSL models, how many locations, and how the month closes today. That is enough for us to say whether this is a small integration or a bigger problem wearing an attendance costume.