Biometric attendance

Biometric attendance software for ZKTeco and mixed device setups

Connect supported Cloud Push devices, legacy local-network devices or USB exports while keeping biometric templates on the physical device.

OPleo records a device user ID and punch time; it does not copy fingerprint or face templates. Compatible ADMS devices can push current punches to OPleo. Older LAN-only devices use a connector running within the office network, and USB reports remain a practical historical fallback.

Integration paths and the current evidence boundary

The product setup guide names ZKTeco K50 and MB360 as intended models for compatible firmware. A model name alone does not establish Cloud Push/ADMS capability: confirm the exact firmware, server settings and connection path on your own terminal.

Repository evidence includes automated checks for representative USB reports, PIN matching and exclusion of remote employees. FEATURE-COVERAGE.md explicitly records that no physical K50 export was supplied and parser checks use synthetic punches. No model/firmware combination is presented here as physically tested.

Software implementation evidence is distinct from physical terminal verification.
PathImplemented integrationAcceptance evidence still needed
Cloud Push / ADMSDevice serial and pairing key; attendance ingestion routesExact model/firmware, real punch received, last activity and matched employee-day record
Legacy LAN connectorPrivate-network connector, test/list users and attendance pullTerminal reachability, enrolled PIN list, real punch and reconnect behavior
USB reportPIN and embedded timestamp parsing with automated representative fixturesRedacted export from the actual terminal; dates, mapping and reviewed attendance result

Map one employee, record a punch, then verify the handoff

Enrol an office employee on the terminal and save the same User ID/PIN on their employee record. Choose the supported connection mode and configure the serial/pairing key or private LAN connector. PIN 000 and remote employees are excluded from device matching.

Record a real arrival and departure. Review device activity, mapped employee, date and punch times in attendance; investigate unmatched IDs and missing punches before payroll. Repeat with a duplicate upload, an offline period and an unmapped PIN to verify recovery and exception handling.

The screenshots below show employee setup and downstream payroll review. They do not demonstrate a connected physical terminal. For rollout sign-off, retain a redacted export or push payload, exact model and firmware, connection mode, test date and reviewed resulting attendance record.

Move current records in a controlled pilot

Start with a redacted employee list and one reviewed attendance/payroll month. Deduplicate employee IDs, confirm salary and currency, map departments and supervisors, and check portal emails. Confirm the supported entry or import format before assuming an old workbook can upload unchanged.

Configure working weekends, office times, leave allowance and late grace. Pilot normal attendance, a missing punch, approved leave and a late arrival. Compare the preview with the same source month and record why each difference occurs.

Name the owner of attendance corrections and the payroll approver. Agree a cutover date and one authoritative record for new activity; retain historical files under your record policy. Expand after the pilot is reconciled and staff can use the request and review workflows.

Keep the terminal private on the office network for LAN mode. OPleo records user IDs and attendance times; fingerprint and face templates remain on the physical device. Assign an owner to connector uptime and missed-log reconciliation.

Inside the product

See the actual OPleo product screens

Captured from OPleo’s product components with fictional demo records. These are product views, not customer results; each capture shows a separate workflow state.

01 — Establish the employee record

Actual OPleo employee table with employee identifiers, department and joining date
Genuine employee component with fictional demo data. Confirm identifiers and reporting lines before moving attendance or issuing portal access.

02 — Review attendance-derived payroll

Actual OPleo payroll report with working days, rates, deductions and payable salary for a fictional employee
Genuine OPleo payroll component captured with fictional demo data. This shows the downstream payroll review, not a live biometric connection or a hardware test.

Questions about biometric attendance

Do biometric templates leave the device?

No. OPleo works with device user IDs and attendance punches, not fingerprint or face templates.

Can Wi-Fi devices work?

Yes. Wi-Fi and Ethernet both work when the selected connection path can reach the device.

Bring your real workflow to the demo

Use a redacted example, your attendance setup and the decisions your team needs to make. We can review fit before you move live records.

Discuss your attendance setup