Overview
Biometric devices eliminate buddy-punching and manual attendance errors. Octal HR connects to devices over your local network or the internet, pulls raw punch logs automatically, and converts them into attendance records — checking employees in and out based on your shift schedules.
Supported devices
| Brand | Models | Type | Status |
|---|---|---|---|
| ZKTeco | K40, F22, SpeedFace V5L, uFace 800 | Fingerprint / Face | Supported |
| Anviz | C2Pro, W2, CrossChex | Fingerprint / Face / Card | Supported |
| Hikvision | DS-K1T341AM, DS-K1T671 | Face recognition | Supported |
| eSSL | i9, MB160, ESSL x990 | Fingerprint / Card | Supported |
| Suprema | BioStation 2, FaceStation 2 | Fingerprint / Face | Beta |
| Generic RFID reader | Any Wiegand-compatible reader | Card | Supported |
Don't see your device? Contact support with the device model. Most ZKTeco and ZKOSS-protocol devices work even if not listed. We add new device support within 2 business weeks on Growth/Enterprise plans.
Connection modes
Local network (LAN) — Recommended
Device and Octal HR server are on the same network. Octal HR's on-premises agent polls the device via IP. Fastest sync; no internet dependency. Requires a PC running the Octal HR Device Agent to be on 24/7.
Cloud push (ADMS)
Device sends punch data directly to Octal HR cloud via ADMS protocol over the internet. No agent PC needed. ZKTeco devices support this natively. Slight delay (up to 60 seconds per punch) but works across locations.
USB / file import
Download the device's attendance log as a CSV or DAT file and upload manually. Fallback option for devices without network connectivity. Not recommended for daily use — error-prone and time-consuming.
Adding a device in Octal HR
Enrolling employees on the device
There are two ways to register employees' biometrics:
- Enrol directly on device — The employee places their finger/face on the device. The device assigns a user ID matching the employee's Octal HR employee ID. Recommended for initial setup.
- Remote enrolment (ZKTeco only) — HR sends an enrolment request from Octal HR; the device prompts the employee to scan their biometric on next tap. Useful for adding new joiners without admin access to the device.
Tip: Use employee ID (not sequential device user numbers) as the device user ID. This ensures punch logs map correctly to Octal HR employee records during sync.
Sync schedule
Octal HR syncs punch logs from connected devices on a configurable schedule:
- Real-time (Cloud Push mode): Punches arrive within 60 seconds
- Every 15 minutes (LAN mode, recommended): Balanced between latency and network load
- Hourly / Daily: For low-bandwidth environments
Change the sync frequency under Attendance → Devices → [Device] → Sync Settings. A manual Pull Now button is available for on-demand sync at any time.
Multi-location setup
Each company location needs its own device(s). Best practices:
- Assign each device to its correct location — punch logs are filtered by location for shift matching
- Employees who work across locations should be enrolled on devices at all locations
- Set a home location per employee; non-home punches are flagged as Remote Attendance for manager review
- Use Geo-fencing (mobile GPS) as a supplement for staff who travel between sites frequently
Testing the full flow
After setup, verify end-to-end:
- Have one employee punch in on the device.
- Go to Attendance → Live View — the punch should appear within the configured sync interval.
- Check the employee appears as Present for today under Attendance → Daily Report.
- Confirm the punch time matches the device log (no time zone offset). Set the device time zone under the device's network settings and ensure it matches your Octal HR tenant time zone.
Time zone mismatch is the most common setup issue. Always verify the device clock is set to PST (UTC+5) before enrolling employees.