The biometric reader at your gate, feeding attendance and payroll.
Keep the fingerprint or face reader you already have. Upload its export, give it a push URL, or use its ADMS cloud setting — every tap lands on the attendance register, and a day a reader went silent is caught before payroll, not after it.
60 days free · no card · all three features
Biometric Devices
Readers at the gate, pushing punches as they happen.
Phones check in with GPS and a selfie; readers push over the network. Both land in the same register.
Tap the phone to open the live demo.Tap any row. It is a live demo, with demo data.
Three things it is bought to put an end to.
The reader and the salary sheet never meet
The device holds every tap. Somebody downloads it, reformats it and types it into the salary sheet at month end.
A dead reader docks a whole shift
A reader that went offline on Tuesday looks exactly like forty people absent on Tuesday.
Nobody knows whose ID is whose
Reader ID 117 was somebody who left in March and somebody else who joined in May, and the export does not say which.
Biometric attendance, on the screen you will use it on. Try it here.
Demo data. Keep scrolling and it walks you through 4 screens, or tap any row, open a record and try it yourself. Everything here is the real interface, drawn small.
Each reader with its site, its timezone and when it last sent a tap.
Biometric Devices
Readers at the gate, pushing punches as they happen.
| Device | Serial | Site | Status | Last punch |
|---|---|---|---|---|
| Main gate | ZK-8841022 | Head office | Online | 9:12 am |
| Store — Koramangala | ZK-8840317 | Koramangala | Online | 9:05 am |
| Store — Indiranagar | ZK-8839904 | Indiranagar | Offline 2 h | 7:02 am |
Phones check in with GPS and a selfie; readers push over the network. Both land in the same register.
Biometric Devices
Readers at the gate, pushing punches as they happen.
Phones check in with GPS and a selfie; readers push over the network. Both land in the same register.
The whole module, listed out.
Nothing here is coming soon. It is what an account opens with on day one of the trial.
Three ways in
Whichever your reader can do.
- Upload its export — Excel or CSV, up to 100,000 rows — each day or each week; taps already received are skipped, so the same file twice is safe
- Or give each reader its own push URL, shown once, so every tap arrives as it is made
- Or use the ADMS cloud setting on eSSL and ZKTeco readers that take only a server address and a port — identified by serial number, and accepted only from the network addresses you list
- Several readers, each with its own site and timezone
Enrolment
Reader IDs mapped to people, with dates.
- Each reader’s user ID linked to a person from a date; overlapping links are refused
- A bulk mapping by employee code
- A tap under an ID nobody holds is kept and listed as unmatched, never dropped — back-date an enrolment and it is picked up
- Deactivating a person, or their exit, closes their enrolment
From taps to a day
The same rules as a phone check-in.
- First tap in to last tap out; the taps in between are kept
- Late marks, overtime, comp-off and short leave follow the same policies as a phone check-in
- A daily digest of people who tapped only once
- HR can repair up to 93 days for 200 people at a time, without using up anybody’s monthly correction allowance
Gaps and payroll
A silent reader is a gap, not an absence.
- A working day a reader was expected on and sent nothing is flagged, and HR is notified
- A missing punch is never turned into an absence on its own
- The payroll month cannot be sent for approval while a gap is open — it is cleared by uploading the export, repairing the days, or noting the site was shut
- An alert when a reader goes quiet
What is kept
A punch is evidence.
- Punches are kept for eight years
- An upload cannot be undone, because a punch is a record rather than a draft
- No fingerprint or face template is ever stored, and nothing is sent to the device
- Taps that arrive before readers are switched on for the company are held until somebody releases them
HR & Payroll, by how many of you there are.
This is the price of the whole HR & Payroll module, which this page is one part of — it is not sold on its own. Yearly, with the monthly figure beside it.
Up to 10 users
₹24,999/year
or ₹2,499 a month
Saves ₹4,989 a year
Up to 50 users
₹49,999/year
or ₹4,999 a month
Saves ₹9,989 a year
Up to 100 users
₹89,999/year
or ₹8,999 a month
Saves ₹17,989 a year
Above a hundred people, tell us how many of you there are. All three features are free for 60 days, and when a trial ends nothing is deleted — see pricing for what the week after looks like.
2 written guides, open to everybody.
The same documentation the product ships with, published in full. No form, no account.
Easier to read now than to discover in week three.
- Biometric attendance is part of HR & Payroll, not a product on its own. There is no biometric-only plan; the price below is the whole module’s.
- There is no hardware. Facto Lite does not sell, install or configure readers, and it does not certify models: the reader is yours, and it has to be able to export a file, call a URL or use its ADMS cloud setting.
- A company records from phones or from readers, not both at once. The switch is made per company from a date, by us on request; somebody away from a reader is covered by HR repairing their days.
- There is no software to install on a PC at the site, so a reader with no internet connection reaches Facto Lite only through its export file.
- Only people with a Facto Lite account can be enrolled. Taps between the first and the last are kept but not counted, so breaks are not deducted from them.
Asked before, answered here.
Does it store fingerprints?
What happens on a day the reader sends nothing?
Is there an extra charge for readers?
Upload one month of your reader’s export.
Sixty days, all three features, no card. Map your reader IDs, upload last month’s file, and see what the register says before anybody is paid from it.