ZKTeco punches, straight into Indian HRM payroll

What the ZKTeco Biometric integration does

Every punch, captured

Fingerprint, face, and card punches from your ZKTeco terminals land in Indian HRM attendance automatically, no pen-drive exports.

Plug in and go

ZKTeco ADMS push means the terminal connects to Indian HRM by itself. Enter the server address in the device menu, register the serial number, and punches start flowing. No PC software.

First-in, last-out logic

Multiple punches a day get collapsed into clean in and out times per shift, with overtime and short-hours flagged.

Shift and week-off aware

Punches map to the rostered shift and the employee's week-off days, so night shifts crossing midnight are counted correctly.

Payroll-ready days

Present, absent, half-day, and paid-leave days feed straight into payroll so PF at 12%, ESI, and LOP are calculated on real attendance.

Multi-device, multi-branch

Connect terminals across factory gates, branches, and site offices under one org, with each device tied to its location.

Setup in four steps

1. Register your ZKTeco device — Add each terminal in Indian HRM under Settings, Attendance Integration, using the serial number from Menu, System Info, Device Info, and pick the device timezone.
2. Point the device at the server — On the terminal, open Menu, Comm, ADMS (called Cloud Server Setting on some models) and enter the server address and port shown on your integration screen.
3. Match user IDs to employee codes — The user ID enrolled on the terminal must equal the employee code in Indian HRM. Punches with no match wait in a needs-mapping list instead of disappearing.
4. Run a test punch — Have one employee punch in, then confirm the record appears in Punch Logs within seconds.
5. Go live across branches — Repeat the same three settings on every terminal. Each device reports under its own serial, so multi-site attendance lands in one register.

Why customers use this integration

• Payroll teams stop chasing pen drives and reconciling Excel dumps at month-end. Punch data is already in the system.
• Late marks, early-outs, and overtime are visible the same day, not discovered on the 30th when it is too late to act.
• LOP and half-day deductions are backed by an actual biometric record, which cuts salary disputes and PF/ESI mismatches.
• A resigned employee removed in Indian HRM stops being a valid punch on every device, closing a common ghost-attendance leak.
• One dashboard shows attendance across all your ZKTeco terminals, whether you run one office or twelve sites in four states.

ZKTeco Biometric integration FAQs

Which direction does the data sync?

Punch logs flow up from the ZKTeco device into Indian HRM. Enrolment lives on the terminal: register each person there once with a user ID that equals their Indian HRM employee code, and the mapping takes care of itself from then on.

How often does attendance update?

ZKTeco terminals with push (ADMS) send each punch as it happens, and it usually shows in Punch Logs within seconds. If the line is down, the terminal holds punches in its own memory and sends the backlog when it reconnects.

Do I need to install anything on the device?

No firmware change on modern ZKTeco terminals. You set the server address and port in the device menu and register the serial number in Indian HRM. Legacy models without push can connect through your existing attendance software or a small script posting to the Indian HRM punch API.

What happens if the internet or device goes down?

ZKTeco terminals store punches locally in their own memory. When the connection returns, buffered punches sync and backfill the missed days, so no attendance is lost during an outage.

Why would a punch not match an employee?

Almost always a mapping gap: the device user ID is not linked to an Indian HRM employee code. Unmatched punches sit in a review queue where you assign them in one click, and the fix applies to future punches too.