Solavel Docs
English

Attendance devices

Last updated

Attendance devices connects fingerprint, face and card terminals to SolaHR, and imports the punch files exported from them. Each person has a code on the device; once that code is linked to an employee, their punches become ordinary attendance records, with the same lateness, overtime and review rules as any other check-in.

Use it when staff clock in on a terminal at the door instead of (or as well as) the employee portal.

#Where to find it

Screen How to open it URL
Devices list Sidebar Time & Attendance → Attendance Devices /attendance/devices
One device Click a device /attendance/devices/{id}

The menu item needs View attendance and a plan that includes attendance. If the page says "The database update for this feature is pending.", the update has not reached your workspace yet.

#Three ways to bring punches in

Way Use it when Needs
Through Device Connect The terminal sits on your office network and you want punches to arrive on their own. A Windows PC or server that stays on, with the connector installed and paired.
Device pushes to SolaHR The terminal (or its software) can send punches to a web address. The push address and token that SolaHR shows once.
File import You export a punch file from the device now and then. Nothing to install; see Import a punch file.

Device Connect is a preview: the Windows connector is not code-signed yet, has been tested against simulators and one real terminal model, and features that depend on the manufacturer's SDK are not yet verified on all models. Compatibility depends on the terminal model and firmware.

#The Device Connect guide

Page What it covers
Device Connect overview What it is, how punches become attendance, what is preview.
Install and pair the connector The Windows installer and portable ZIP, pairing code, updating and removing.
Add a device The four steps, the model catalogue and devices the connector found.
Vendor SDK setup Setup required, Register_SDK_x64.bat, readiness checks.
Mapping and attendance Device users, employee mapping, activity and the attendance flow.
Manage devices Device health, edit, enable, disable, delete and push users, copying face and fingerprints, former-employee suggestions, owner-only actions.
Supported devices Models and honest compatibility levels.
Troubleshooting Offline connectors, unreachable devices, wrong times.

#Who can do what

Action Permission
See devices, mappings, review, activity and import history View attendance (hr.attendance.view)
Add or edit devices and connectors, test, link codes, read and edit device users, import files, reprocess, quarantine Manage attendance devices, Device Connect connectors, mappings and quarantine (hr.devices.manage): the Owner, the HR Manager and attendance managers who held it when the feature was introduced.
Set the device clock, restart a device, copy face or fingerprints between devices, give a device user a role above User Run advanced device commands (hr.devices.advanced): Owner only.
See the snapshot photo a device took at a punch View attendance and View employees.

Fingerprints and faces are never stored in SolaHR. Every change made to a device is written to the audit log.

#Devices that push punches

For a device that pushes to SolaHR, Add device shows a Push address and an Access token. The device (or your integrator) sends punches to that address with the token as a Bearer header. Copy the token now: it is shown only once. If it is lost, click New token; the old one stops working. A device that is Switched off has its pushes refused.

The list shows each device's Last seen (or Never), how many codes are Mapped, and how many punches are Unmapped or Rejected. Punches from a code that is not linked are kept and become attendance as soon as you link it. The device's Review tab lists Unmapped codes (tick several and click Link N selected) and Reprocess pending writes the waiting days.

#Where punches appear in Attendance

Each record made from a device carries a Device chip with the device name, the method (face, fingerprint, card, password) and the location; the records list can be filtered by Source and Location. See Where an attendance record came from.

#Import a punch file

Tab Import file: upload a CSV or Excel export (user id, date and time, state).

  1. Match the columns: Device code column, Date and time column, Separate time column (only when date and time are in two columns) and In / out column (optional; without it, the first punch of a day is in, the next out, and so on). Choose the Date order (Day / month / year or Month / day / year) and whether the First row is a header.
  2. Click Preview. The first rows are shown, with a note when codes are not linked yet.
  3. Click Import. The result says "N new punches, N already known, N days written", and lists unmapped, rejected and unreadable rows for the Review tab.

Importing the same file twice adds nothing. A file that is too large is refused; split it into smaller files. Times without a timezone are read in the device's timezone. Import history lists each file with Rows, New, Duplicates and Days written.

#Rejected punches

The Review tab lists Rejected punches with When and Reason:

Reason What to do
The day already has an entry made another way The day was recorded by HR or the portal; the device punch does not overwrite it. Correct the day in Attendance if needed.
Check-out without a check-in Add the missing check-in in Attendance.
Code not linked to an employee Link the code.
Employee not found The linked employee no longer exists; link the code again.
Duplicate scan Nothing; a repeat scan is ignored.

Punches for an employee on an unpaid suspension, or before their start date, do not create attendance.

#Worked example

{Organization name} has a ZKTeco terminal at the {Main warehouse name} warehouse. HR pairs a connector on the warehouse PC, adds the device "Warehouse door" with Location {Main warehouse name}, maps 14 of 15 device users to employees and starts sync. The morning check-ins appear in Attendance with a Device - Warehouse door chip. For last year's log, HR exports the terminal's data to Excel, imports it on Import file, and gets "612 new punches, 0 already known, 280 days written".