Supported devices and how each connects
Each device is registered in Attendance → Devices with a protocol, an office location and its connection details. Some devices push punches to Verdeshell as they happen; for others Verdeshell pulls punches on a schedule.
| Device or system | Protocol in Verdeshell | How punches arrive |
|---|---|---|
| ZKTeco terminals | ZKTeco ADMS | The terminal pushes punches to Verdeshell's push address |
| ZKTeco EasyTimePro / BioTime cloud | ZKTeco EasyTimePro | Verdeshell pulls punches from the vendor cloud on a schedule |
| Hikvision access-control and attendance terminals | Hikvision ISAPI | Verdeshell pulls punches from the device on a schedule |
| Suprema devices managed by BioStar | Suprema BioStar | Verdeshell pulls punches from the BioStar server on a schedule |
| Any other device or middleware | Generic HTTP | The device posts each punch as JSON with its device key |
How a punch becomes attendance and payroll
- Enrol employees on the device using their biometric ID. Verdeshell gives every employee a unique numeric biometric ID (or uses the one you set), and you can download the enrolment roster as a CSV to load onto your devices.
- The device sends or Verdeshell fetches the punch. Every punch is logged with its time in your company's timezone and the device it came from.
- The punch is matched to an employee by biometric ID and written to that person's attendance record. Duplicates are recognised and not counted twice.
- Attendance rules apply. The attendance policy and the employee's shift — including overnight shifts — decide present, late, half-day or absent for the day.
- Payroll reads attendance. Days absent without approved paid leave become loss of pay, worked out on the monthly divisor your company chooses.
Punches that do not match anyone
A punch from an ID nobody holds is not thrown away. The Biometric Punch Logs screen lists every punch a device reported with its outcome — processed, unmatched, duplicate, rejected or error — and shows a banner when unmatched punches are waiting.
- Assign an unmatched punch to the right employee, which also records that biometric ID against them, and it is reprocessed onto their attendance.
- Reprocess punches one at a time or in bulk after you fix an employee's biometric ID on their profile.
- The log shows the name the device itself holds for the ID, so a row reading only a number can still be traced to a person.
Device diagnostics
A reader that stops reporting usually goes unnoticed until payroll week. In Verdeshell the devices list shows when each device was last seen, and for pull devices when the last poll was attempted, whether it succeeded, how many punches it brought in, and the reason if it failed.
- Test connection checks a device's details before you rely on it, and explains a failure in plain words — for example that the portal rejected the username or password — without ever echoing the credential back.
- Rotate API key issues a new key for a push device if the old one may have leaked.
- Deactivate a device you have retired; it simply stops recording.
A face-recognition kiosk for shared devices
Where buying another terminal is not worth it — a small branch, a site office, a reception desk — a tablet or laptop with a camera can run Verdeshell's face-recognition kiosk in the browser. The kiosk is paired once with a device key, then recognises enrolled employees and records check-in or check-out on the spot. Kiosk punches land on the same attendance record as device and mobile punches.
Plans and setup
Biometric device integration and the face kiosk are included in the Starter plan; there is no per-device fee. Device registration is done by your HR admin, tenant admin or tenant owner from the web. Book a demo to check your device models with the Verdeshell team before your trial.