Does any biometric terminal work?
No universal compatibility is claimed. Verify model, firmware, connection mode and real punches in your own acceptance test.
HR operations guide
Connect biometric punches with employee records, leave and payroll review; validate device mapping, connection paths and rollout evidence.
A biometric attendance system collects punches. HR software supplies employee identity, approved leave, policy and the payroll review around those punches. The connection needs a tested data path and a clear exception owner.
The useful attendance payload is the enrolled user ID and punch timestamp. Map the ID to an employee in the correct organisation. OPleo processes attendance identifiers and times; biometric templates remain on the terminal.
Document where each employee checks in and who maintains the mapping. A new starter or changed terminal ID can create unmatched punches even when the connection works. Keep remote arrangements distinct from office device matching.
Supported Cloud Push / ADMS devices send attendance through a paired connection. Legacy LAN-only devices need the local connector on the private network. USB reports provide another import path for supported exports.
Record the exact terminal model, firmware and connection mode. Test an enrolled employee’s arrival and departure, then inspect the resulting employee-day record. Implementation evidence for a protocol is not physical verification of every device model.
Test a duplicate upload, unknown PIN and offline period. Check whether late-arriving logs reach the expected date and how corrections interact with imports. Assign connector uptime and missed-log reconciliation to a responsible person.
Do not expose a LAN terminal publicly to make connectivity convenient. Plan the private-network connector path and access with your installation owner. Confirm your own device and report format before expanding to more terminals.
Reconcile incomplete punches with approved leave and manual corrections. Confirm calendar, salary and late grace before reviewing payroll. A working device connection does not establish correct net pay.
Use a representative payroll month as the rollout acceptance point. Keep specialist overtime and shift rules explicit. For hybrid teams, approved remote dates and portal check-in need testing alongside the office terminal.
No universal compatibility is claimed. Verify model, firmware, connection mode and real punches in your own acceptance test.
The supported legacy LAN path uses a local connector on the same private network. Test actual terminal reachability and logs before rollout.
Use a redacted example, your attendance setup and the decisions your team needs to make. We can review fit before you move live records.
Book a workflow demo