Data stuck in the machine
Punches sit in the biometric device and someone exports and keys them in by hand every month.
Stop chasing attendance. Automate it from device to payroll
Connect any attendance device you already own, biometric, face, RFID, turnstile or mobile, to ERPNext and Frappe HR. Attendance marks itself by shift, and payroll runs with PF, ESI, PT and TDS built in. No manual registers, no re-keyed punches, and no month-end scramble. Works with your existing hardware. ZKTeco and ESSL out of the box, most other devices through an API or a custom connector.
ZKTeco / ESSL
Out of the Box
Automatic
PF, ESI, PT, TDS
Real-time
Shift Auto-Attendance
The attendance and payroll problems this ends
If any of these describe your month, an ERPNext attendance and payroll integration pays for itself quickly.
One flow from the gate to the payslip
Every punch becomes attendance by shift, and attendance becomes accurate, statutory-ready payroll.
Employee attendance sync
Punches from any device land in ERPNext in near real time and mark attendance automatically against each employee's shift.
Outcome: no manual registers and live attendance.
Payroll automation
Attendance, leave and overtime feed the payroll entry, which computes PF, ESI, PT and TDS and generates every salary slip in one run.
Outcome: payroll in hours, not days.
Shift management
Shift types and rosters drive auto attendance, judging on time, late entry, early exit, overtime and week-offs for you.
Outcome: fair, rule-based attendance.
Almost any attendance device can connect
ERPNext only needs an IN or OUT log with an employee ID and a timestamp, which is why the list below is long. Each device is tagged by how it connects and the effort involved, so there are no surprises later.
Biometric and access hardwareTable 1 of 4
| Device or method | Examples / best for | How it connects | Effort |
|---|---|---|---|
| Fingerprint terminals | ZKTeco, essl | LAN sync tool (ZK) or API | Low |
| Face recognition terminals | ZKTeco SpeedFace, essl, Hikvision | Sync tool or vendor API push | Low |
| Palm vein and iris scanners | Mantra, secure sites | Vendor API push or file import | Medium |
| RFID, smart card and NFC readers | HID, generic card readers | API push or import | Low |
| Proximity and QR turnstiles | Gate entry systems | API push or import | Medium |
| Access control and boom barriers | Any system logging IN and OUT | API push or import | Medium |
| Time clocks and swipe machines | Matrix COSEC, Suprema, Realtime, Spectra, Secureye, Bio-Rad | Vendor API push or import | Medium |
| ADMS push protocol devices | Devices that HTTP post punches | Direct push to the check-in API | Low |
Three connection routes cover all of the above: a simple CSV or Excel import, an API push from the device or vendor cloud, or the official LAN sync tool for ZK protocol devices. If your device is not listed, it almost certainly still works. Tell us the make and we will confirm the route and effort before you commit.
See it working, screen by screen
Representative views of biometric sync, auto attendance, payroll and the shift roster. These are illustrative mockups, not live ERPNext screenshots.
Attendance sync: every punch, in ERPNext within seconds
Check-ins from ZKTeco, ESSL and the mobile app arrive in Employee Checkin, matched to the employee by device ID, ready to become attendance.
Log check-ins automatically from hardware device registers
Synchronize punches in near real-time without files or scripts
Employee Checkins
Illustrative dashboard mockup, not a live ERPNext screenshot.
From a punch to a payslip, step by step
The core capture, attendance and payroll engine is native to Frappe HR. Devices plug into it.
🗺️ Map employees
Set each employee's device ID so punches match the right person.
📅 Assign shifts
Give each employee a shift with its auto attendance rules.
👆 Bring in punches
The sync tool or an API push writes IN and OUT logs into Employee Checkin.
✅ Mark attendance
Auto attendance reads the check-ins and the shift and marks attendance.
💰 Run payroll
Attendance and leave feed the Payroll Entry and salary slips.
What teams typically gain
The exact figures depend on your headcount and current process. These are the outcomes a well-run rollout targets.
Days to hours
attendance flows straight into payroll, so a run that took days closes in hours.
Near zero manual entry
punches sync on their own, removing the monthly export and rekey.
One view of every location
HR sees live attendance across all sites in one system.
Statutory accuracy built in
PF, ESI, PT and TDS are computed by the system, cutting disputes and rework.
The questions buyers actually ask
Honest answers about connections, locations, existing payroll systems, data security, and custom shifts.
Almost certainly yes. The free sync tool is built for ZK protocol devices, but any device that can push to an API, export a file, or send punches through its vendor cloud can feed ERPNext. Tell us the make and model and we will confirm the route and effort before you commit.
Yes. Each site can push punches through the API or its vendor cloud into one central ERPNext, or run a sync tool per location. HR then sees live attendance for every site in a single view.
Not necessarily. ERPNext can run payroll natively with full Indian statutory support, or it can sync attendance and leave to your existing payroll system if you prefer to keep it. We scope whatever fits your plan.
Data sits in your own ERPNext instance, on your cloud or on-premise. Access is role-based, device sync uses a scoped API user, and payroll is protected by permissions and an audit trail. We design the access model with your team during setup.
These are configured to match how you run today, including shift grace periods, leave policies, overtime rules and salary components, so the system reflects your real policy rather than a generic template.
Live in about four weeks for a single site
A typical single location rollout. Multi-location and complex device estates are scoped after a short discovery call.
| Phase | What happens |
|---|---|
| Week 1 · Discovery | We confirm devices, shifts, leave rules and salary structures, and map employees. |
| Week 2 · Device and shifts | Attendance sync is set up and shifts configured, with live check-ins flowing in. |
| Week 3 · Payroll | Salary structures, PF, ESI, PT and TDS are configured and a test payroll is run. |
| Week 4 · Go live | First live attendance and payroll cycle, with your team trained and supported. |
How we engage: clear scopes, quoted after discovery
We price by scope, not guesswork. Pick the starting point that fits, and we confirm a fixed quote after a short discovery call.
| Scope | What it covers | Pricing |
|---|---|---|
| Attendance sync | Device connection and employee mapping, shift setup and auto attendance, live attendance across the site. | After discovery |
| Attendance + payroll | Everything in attendance sync, plus salary structures, Payroll Entry, PF, ESI, PT, TDS and go live support. | After discovery |
| Multi location rollout | Multi site device strategy, central attendance and reporting, custom connectors and a phased plan. | Per estate |
Why Hybrowlabs
Scale your ERP implementation with a trusted, certified platform engineering partner.
Deep ERPNext and Frappe expertise
We implement ERPNext and Frappe HR day in and day out, so the setup follows platform best practice and survives upgrades.
Built for Indian payroll
PF, ESI, PT, TDS, Form 24Q and Form 16 are familiar ground, so statutory payroll is configured correctly from day one.
Any device, honestly scoped
We tell you upfront whether a device is plug-in, an API push or a custom build, and we quote a fixed scope so there are no surprises.
Frequently Asked Questions
Common technical and commercial questions about ERPNext attendance and payroll modules.
ZKTeco and ESSL work with the official sync tool. Face recognition, palm and iris scanners, RFID and NFC readers, turnstiles, access control, ADMS push devices, mobile, kiosk and web all connect too, through an API push, a vendor cloud or a custom connector. ERPNext only needs an IN or OUT log with an employee ID and a timestamp.
We price by scope. A single-site attendance sync, a full attendance and payroll setup, and a multi-location rollout are different sizes of work. After a short discovery call we give you a fixed quote.
A typical single-site attendance and payroll rollout goes live in about four weeks. Larger or multi-location projects are phased and scoped after discovery.
Yes, natively, with salary structures, payroll entry, salary slips and statutory reports, including Form 24Q and Form 16 inputs.
We train your HR and payroll team during rollout and support you from the first live payroll cycle onwards. Ongoing support is agreed as part of the engagement.
Usually not, if it supports the ZK protocol or can export or push logs. We test your device first and only recommend a change if the hardware genuinely cannot share its punch data.
Ready to automate yourAttendance & Payroll?
Connect ZKTeco, ESSL, or custom devices directly to ERPNext. Move from a punch to a payslip in near real-time, removing manual register entries and payroll delays.
