Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration

eSSL Biometric ERP Integration: Punches From the Device Straight Into Attendance

For HR and plant administration teams with eSSL devices at the gate: punches that reach attendance on their own, matched to the right employee, ready for shifts and payroll.

A worker pressing a finger on a biometric reader at a factory gate

An eSSL biometric ERP integration is often the first integration a factory or hospital asks for. The devices are already on the wall and staff already punch in. The trouble starts when those punches have to reach attendance and payroll.

Usually someone exports a file from the eSSL software, cleans it in a spreadsheet and uploads it. Biometric IDs do not match employee codes, punches are counted twice, and a new joiner is missing until someone notices.

This page covers what that costs, an illustrative example from Hosur, and how the eSSL connection works with Apragya HR.

What file-based attendance costs

Weekly clean-up

HR spends hours fixing exports before they can be used.

Wrong person

A biometric ID that does not match an employee code goes unnoticed.

Double punches

Repeated uploads count the same punch twice.

Payroll disputes

Overtime and late marks are argued from different files.

An example: a Hosur component plant

Take an illustrative plant with 400 workers across three shifts and four eSSL devices. The eSSL server sits on the plant network, which allows no inbound connections from outside.

A punch, from the gate to attendance

  1. Worker punches

    The eSSL device records the fingerprint.

  2. eSSL server

    The punch lands on the plant's own server.

  3. Tenant Runner polls

    Inside the network, on a short interval.

  4. Matched to employee

    Biometric ID resolved through the device binding.

  5. Attendance updated

    Duplicates ignored; unknown IDs reported.

The runner only makes outbound connections, so no firewall rule had to change.

In the first week the connection reported eleven punches from biometric IDs that were not bound to anyone. They belonged to new contract workers, who were enrolled the same day. By payroll, attendance matched the gate, and no one had cleaned a file.

A grid of tagged fingerprint tokens with a few untagged ones in a tray
The untagged few were the new contract workers, enrolled the same day.

How biometric attendance integration with payroll works

Step 1 of 5

Register the device

Add each device in HR with its serial; it receives its own key.

  1. Register the device: Add each device in HR with its serial; it receives its own key.
  2. Bind employees: Map each biometric ID to an employee; a clash is refused.
  3. Run the connector: The eSSL connector polls the server, usually from a Tenant Runner.
  4. Push punches: Punches arrive singly or in batches after a reconnect, without duplicates.
  5. Use the attendance: Shifts, overtime and payroll read the same attendance.

Choosing fingerprint attendance software in India

Most biometric setups can export a file. The questions that matter are whether punches arrive without a person in the middle, whether an unknown ID is caught, and whether the plant network has to be opened for it.

File exports, against Apragya's eSSL connection

FeatureExport and uploadApragya with eSSL
How punches arriveA weekly filePolled on a short interval
Unknown IDsSilently droppedReported for enrolment
DuplicatesCounted twiceIgnored
Network changeNone, but manualOutbound only, through the runner
Payroll linkA second uploadThe same attendance record

Checked against public information on 16 September 2026.

What sets this eSSL eTimeTrack Lite integration apart

One employee record

Attendance sits beside leave, shifts and payroll.

Key per device

Each device has its own key, which can be rotated.

Tenant Runner

Reaches the on-premise eSSL server without inbound access.

Self-service

Employees see attendance and apply for regularisation from their phone.

Agents on paid plans

An agent can flag odd attendance patterns for HR to review.

Access by role

HR, supervisors and employees each see their part.

See attendance, shifts and how to connect eSSL biometric.

Getting started

  1. List your eSSL devices, their serials and the server address.
  2. Register each device in HR and keep its key safe.
  3. Bind biometric IDs to employees, starting from the device's enrolled list.
  4. Install a Tenant Runner if the server is on your own network.
  5. Watch the unknown ID count in each batch for the first two weeks.

eSSL installations differ, so the connector is set up and tested against your own server.

What it costs to start

Free
Up to 3 users
HR included, with CRM and Vendor Onboarding
1,000
AI Credits a month
On the free plan
INR 3,999
Starter, a month
Up to 10 users and 2,000 AI Credits

eSSL biometric integration, answered

Do we need to open our firewall?
No. The Tenant Runner connects outwards to Apragya, so no inbound rule is needed.
What happens if the network drops?
Punches are sent in a batch when the connection returns, and duplicates are ignored.
Will it work with our exact eSSL setup?
The connector is a starting point that is adjusted for your server address and fields, then tested.
Can we see which biometric IDs are not mapped?
Yes. Punches from unbound IDs are reported instead of being dropped.
What does it cost to start?
HR is part of the free plan, which covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter, at INR 3,999 a month, covers up to 10 users, adds a choice of enterprise apps, and is where ready-made AI agents start to run.

Let the gate fill the attendance register

Register one device, bind its employees and watch a shift's punches arrive.