By the SightShield team · · 3 min read
Why integration matters
An attendance machine on its own produces punches. HR still has to turn those punches into attendance, leave, overtime and salary. If the machine feeds your HR software directly, that monthly work largely disappears — and so do the errors from copying data between systems.
How the data usually flows
- The terminal records punches.
- The terminal’s own software or cloud (for example eTimeTrackLite, ZKBio Time or COSEC) collects punches from all terminals.
- That software pushes punches to the HR system through an API, or the HR system reads them from the attendance database.
- The HR system applies shifts, leave and holidays, and passes attendance to payroll.
What popular HR systems support
| HR software | Biometric integration (per their documentation) |
|---|---|
| Zoho People | Two methods: an API method where device software pushes punches, and a plugin method that reads the device software’s database; employees are mapped by biometric ID |
| Keka | Four integration types for biometric devices, including SQL-based push |
| greytHR | Biometric integration plus mobile options: geo-fence auto sign-in (minimum 50 m radius) and selfie attendance with face verification and liveness detection |
Check before you buy
- Does your HR software list the attendance brand or software as supported?
- Which method: API push, database read or file import? Database methods need a PC or server running continuously.
- Are employee IDs consistent between the terminal and the HR system?
- How are missed punches and corrections handled — in the HR software or on the terminal?
- Who supports the integration if it stops — the HR vendor, the terminal brand or the installer?
Common integration problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Employees missing from HR attendance | Device user ID does not match the HR employee code | Correct the ID mapping |
| Punches arrive late or not at all | Sync service stopped, PC switched off, or network down | Use cloud sync or a dedicated always-on machine; check the service |
| Duplicate punches | Same punch pushed twice, or people punching repeatedly | Set duplicate-punch filters in the software |
| Wrong times | Device clock not synchronised | Enable automatic time synchronisation |
| Night shift split across two days | Shift rules not set for overnight shifts | Configure overnight shift rules in HR |
A step-by-step plan
- Confirm the HR platform supports your device brand or software, and which method it uses.
- Standardise employee codes across HR and the devices.
- Configure shifts, weekly offs, holidays and overtime in the HR system.
- Connect the device software or cloud to HR and test with a small group.
- Run one payroll cycle in parallel with your old process.
- Document who to call if sync stops — device vendor, HR vendor or installer.
Mobile and field staff
For sales and field teams who never visit the office, HR apps increasingly offer mobile attendance with geo-fencing and selfie verification. A common setup is face terminals at offices and factories, and mobile attendance for field staff, all landing in the same HR system.
Attendance systems with HR integration →Quick answers
Can my biometric machine connect to Zoho People?+
Zoho People documents an API method and a plugin method for biometric devices. Compatibility depends on your device’s software.
Does greytHR support biometric attendance?+
Yes, along with mobile geo-fence sign-in and selfie attendance with face verification.
Do I need a computer running all the time for integration?+
For database or plugin methods, usually yes. Cloud attendance software that pushes data by API avoids this.
Which is better: attendance rules in the device software or in HR?+
Keep rules in one place, usually the HR system that runs payroll, and let the device software only collect punches.
Can we change HR software later without changing devices?+
Usually, if the new HR platform supports your device brand or software. Check before switching.