eSSL punches to payroll, without the USB stick

What the eSSL Biometric integration does

Live punch pull

Every fingerprint, face, and card punch on your eSSL K30, X990, or MB460 devices lands in Indian HRM within minutes over the network, no SmartOffice export needed.

Direct connection, no middleware

The device pushes punches to Indian HRM on its own. No always-on PC, no SmartOffice server, no sync agent to babysit. You enter a server address on the machine once and it starts reporting.

Multi-branch consolidation

Devices at your Pune plant, Andheri office, and warehouse report into one attendance sheet, with each punch tagged to its location and shift.

Shift and regularization mapping

Raw punches are matched to rostered shifts, grace periods, and week-offs, so late marks, half-days, and OT are calculated the way your HR policy defines them.

Duplicate and buddy-punch guard

Repeat punches inside the debounce window are dropped, and mismatched device-to-employee IDs are flagged before they corrupt the muster.

Payroll-ready muster

Present, absent, and OT days feed straight into payroll runs, so PF, ESI, and net pay are computed on real device data instead of a typed spreadsheet.

Setup in four steps

1. Register the device in Indian HRM — Under Settings, Attendance Integration, create an entry with device type eSSL and the serial number printed on the machine (also shown in Menu, System Info). The serial is how the device identifies itself.
2. Point the machine at the server — On the device, open Menu, Comm, Cloud Server Setting and enter the server address and port shown on your integration screen. That is the only change made on the device.
3. Set the clock and timezone — Pick the device timezone in Indian HRM and set the machine clock to match. Punch times are read in that zone, so a wrong clock shifts every in and out time.
4. Match employee codes — The User PIN enrolled on the device must equal the employee code in Indian HRM. Any punch that does not match shows up in Punch Logs as needs mapping, so gaps are visible, not silent.
5. Run a test punch — Have one employee punch in and watch it appear in Punch Logs within seconds. Then roll the same steps out to every device.

Why customers use this integration

• No more walking to each machine with a pen drive at month-end. Punches arrive on their own.
• Attendance, PF, ESI, and OT are calculated on device-verified data, so payroll disputes drop.
• A resigned employee removed from Indian HRM stops counting: their punches land in the needs-mapping queue instead of the muster, closing the ghost-attendance leak.
• One dashboard shows live in-office headcount across every branch and eSSL device, useful for factory shop-floor and multi-site retail.
• Auditors get a clean punch-to-payslip trail for each employee, which holds up during a PF or labour inspection.

eSSL Biometric integration FAQs

Which way does the data flow between eSSL and Indian HRM?

Punches flow from the device into Indian HRM. Enrolment stays on the device: you enrol the fingerprint there once with a User PIN that matches the Indian HRM employee code, and every punch after that maps automatically. There is nothing to reconcile in a spreadsheet.

How often do punches sync?

In near real time. eSSL push firmware sends each punch as it happens, and it typically shows in Punch Logs within seconds. If the internet drops, the device stores punches in its own memory and sends the backlog when the connection returns, so nothing is lost.

Do I need a static IP or extra hardware?

No. The device is the one making the connection, so it works behind any normal broadband or 4G router without a static IP, port forwarding, or an always-on PC. You only need the machine to reach the internet. For extra safety you can restrict the integration to your office IP from the dashboard.

What happens if a device goes offline or a punch fails to match?

Offline devices are marked in the integration health panel, and punches are backfilled once the device reconnects, so no data is lost. Punches whose enrolment ID has no matching employee are held in an unmatched queue for HR to resolve, rather than being silently dropped.

Will it work with my older eSSL model?

Any eSSL device with push (ADMS / Cloud Server) support connects directly, which covers the K30, X990, iClock, MB20, MB460, and SF series on recent firmware. A very old model without push can still be connected through a small script or your existing attendance software posting to the Indian HRM punch API, so you are not forced to replace working machines.