eSSL biometric attendance integration
Punches from your existing eSSL terminals land in SignHR attendance automatically — no nightly export, no middleware of your own.
SignHR accepts punch data directly from eSSL devices running eTimeTrackLite. The eTimeTrackLite service posts its device logs to a SignHR endpoint every couple of minutes; each record is matched to an employee, deduplicated against what has already arrived, and written into attendance against the correct shift and business date. You keep the hardware you already bought.
How it works
- 1
Register the device by serial number
Each terminal is registered against your workspace by its serial. That serial is how a punch is attributed to the right tenant and the right device, so multi-site setups with several terminals stay separated.
- 2
eTimeTrackLite posts its logs
The eSSL service sends batches of device log records to a workspace-specific ingest endpoint, authenticated with a token issued to you. It re-sends recent records roughly every two minutes, which is normal and expected.
- 3
Duplicates are discarded, not double-counted
Every record carries a device log ID, which SignHR uses as an idempotency key. Because the device deliberately re-sends recent punches, this matters: a re-delivered punch is recognised and dropped rather than creating a second entry.
- 4
Punches become attendance
Each punch is localised using the device's configured timezone, paired into sessions, and attributed to the right business date — so a night shift crossing midnight lands on the day it belongs to rather than splitting across two.
Where it stops
Every integration has edges. These are ours, stated here rather than discovered during implementation.
- Punch data flows in one direction. SignHR does not push employees, templates or fingerprints out to the terminal — enrolment stays on the device.
- The eTimeTrackLite service has to be running and able to reach the internet. If the PC it runs on is off, punches queue on the device and arrive when it comes back, not before.
- Where several terminals report without their serial number, punches attribute to the workspace's single active device. Multi-device sites should confirm each terminal sends its serial.
Questions
No — that is the point of this integration. If your terminals already run eTimeTrackLite, they point at SignHR instead of, or alongside, wherever they post today. The hardware, the enrolled fingerprints and the installation all stay as they are.
The eTimeTrackLite service posts every couple of minutes, so a punch typically appears within that window. It is not instantaneous, and it is not meant to be — the batching is what makes delivery reliable over a patchy connection.
Nothing is lost. Punches stay on the device and the service delivers them once connectivity returns. Because delivery is idempotent, a backlog arriving all at once does not create duplicate attendance.
Yes. Device punches, app punches and face or selfie attendance all write into the same attendance record, so a team with office staff on a terminal and field staff on their phones is one report, not two.
This integration feeds Time & Attendance.
Other integrations
Technical detail last checked against the product on 2026-08-07.