Integration · Biometric ↔ HRMS
Biometric Attendance Integration (eSSL, ZKTeco ↔ HRMS & Payroll)
Punches from eSSL and ZKTeco devices collected automatically from every location, matched to people and shifts, and delivered to your HRMS or payroll as clean attendance records.
What is biometric attendance integration?
Biometric attendance integration connects fingerprint, face or card devices such as eSSL and ZKTeco to your HRMS, payroll or custom software, so punches from every location are collected automatically, matched to employees or members and shifts, checked against your rules, and turned into reliable attendance records and payroll inputs without manual exports.
Last updated:
This integration is part of Co-Mate's system integration services. We have delivered it for a co-learning space in Kerala; see the Echo Study Space case study.
Who this is for
Who needs biometric devices integrated?
Organisations that already own biometric devices but still move the data by hand.
Typical buyers
- HR and payroll teams
- Operations heads of multi-site businesses
- Owners of co-working, co-learning, gym and membership spaces
Signs you need it
- Someone downloads punches from each device by USB or desktop software every month.
- Attendance is cleaned in Excel before payroll, and corrections are not tracked.
- Each location's devices are managed separately, with no central view.
- Members or staff dispute attendance because records are incomplete.
What we build
Which data flows from the devices?
Data mostly flows from devices to your system, with user enrolment sometimes flowing the other way.
| Data | Direction and behaviour |
|---|---|
| Punch records | Device → system. Each punch with user ID, timestamp, device and verification method. |
| User mapping | System ↔ device. Device user IDs mapped to employees or members; new users can be pushed to devices. |
| Device status | Device → system. Online/offline state, last sync time and storage capacity, for monitoring. |
| Processed attendance | Within system. Punches matched to shifts and rules into present, late, overtime and absent records. |
| Payroll inputs | System → payroll. Approved worked days, overtime and deductions exported or synced. |
What usually goes wrong with biometric attendance data?
Raw device data is messy, and most "attendance problems" are really data-handling problems.
- Unmapped users: device user IDs that do not match employee or member records. We keep a maintained mapping and flag unknown IDs.
- Double punches: people scan twice. Rules collapse repeated punches within a short window.
- Night shifts: punches after midnight are attributed to the wrong day. Shift-aware matching fixes it.
- Clock drift: device clocks drift and timestamps become unreliable. Device time is checked and corrected during sync.
- Silent failures: a device stops sending and nobody notices until payroll. Monitoring raises an alert the same day.
How is biometric data protected?
Fingerprint and face templates stay on the devices; the integration moves only punch records (who, when, where). That keeps the most sensitive data out of your servers and out of transit. Punch data itself is transferred over encrypted connections, access is limited to authorised HR and operations roles, and retention follows your policy and local regulations.
How does an engagement work?
Five phases, each with a clear output you can review before the next one starts.
- 1
Discovery
We list device models, firmware, locations and network setup, and how attendance is used today.
- 2
Architecture & scope
You get the connection method per device, user-mapping plan, attendance rules and target-system design.
- 3
Build in milestones
One device first, then each location, then rules and exports, verified against manual records.
- 4
Launch
Rollout across all sites, user mapping completed, and HR trained on exceptions and corrections.
- 5
Support & scale
Device additions, rule changes, monitoring and support during payroll periods.
Which engagement model fits?
There are three ways to work with Co-Mate; the right one depends on how settled your scope is and how long the system will keep evolving.
| Model | Best for | How it works |
|---|---|---|
| Fixed-scope project | A defined first version or a specific integration with clear requirements. | We agree modules, milestones and acceptance criteria up front, then deliver against them. Changes are scoped and agreed before work starts. |
| Dedicated engineering team | Larger programmes, evolving roadmaps or several systems built in parallel. | Senior engineers work as an extension of your team on your priorities, with sprint planning, demos and shared tooling. |
| Ongoing retainer / support | Systems already live that need maintenance, monitoring, hosting support and steady improvements. | A reserved block of engineering time each month, with agreed response times for issues and a backlog of improvements. |
Device integration is usually a fixed-scope project. Multi-site organisations often keep a retainer for new sites, devices and rule changes.
Which devices and systems do we connect?
We connect devices to the system that should own attendance: an HRMS we build, your existing HR or payroll software, or your own application.
- eSSL biometric devices
- ZKTeco biometric devices
- Face recognition terminals
- RFID / card readers
- Custom HRMS
- Payroll software
- Tally
- Zoho
- Odoo and ERPNext HR
- Membership and booking software
Product names are used only to describe compatibility. They belong to their owners; Co-Mate is not affiliated with or endorsed by them.
Tech & monitoring
Connection options
Manufacturer SDK, device push to a secure endpoint, or the vendor's attendance server database.
No lost punches
Incremental collection with duplicate detection, so offline periods are recovered cleanly.
Security
Devices on restricted networks, encrypted transport, and no biometric templates stored outside the devices.
Monitoring
Alerts when a device goes offline, stops sending punches or runs low on storage.
Where do we work?
Anywhere. Co-Mate is a remote-first engineering studio in Kerala, India, delivering for businesses worldwide.
GCC
Our working day covers the whole GCC business morning and early afternoon.
Europe & UK
Strong overlap with European and UK working hours for calls, reviews and releases.
US & Americas
Scheduled overlap with US mornings for workshops, demos and decision meetings.
India, APAC & Australia
Same or near time zone, so day-to-day collaboration is simple.
Discovery workshops, demos and training run online. You talk directly to the senior engineers who design and build your system, not to an account manager relaying messages.
Related case studies
- Facility & manpower services
Workforce-to-site auto allocation system
An employee management system that automatically plans and allocates employees to client work sites, replacing spreadsheet rostering and phone-call coordination.
Read the case study - Co-learning & study spaces
Automatic biometric attendance for Echo Study Space
An integration between eSSL biometric attendance devices and the space's software, so member check-ins are recorded automatically instead of by hand.
Read the case study