A terminal knows people only by a code (for example 17). SolaHR knows employees. The mapping is the link between the two, and it is what turns a scan at the door into a day of attendance. This page explains the mapping, the import start date, how punches become attendance, the origin chips you see afterwards, live punches and snapshot photos.
#Device users
Open a device and its Device users tab. It lists everyone stored on the terminal, with the employee each one is linked to. Read users from device again refreshes the list ("Last read: ..."). What SolaHR reads is the code, name, card number, role and whether the person has a face, a fingerprint or a password. It never reads the fingerprint or face itself.
| Filter | Shows |
|---|---|
| All | Every user on the device |
| Not mapped | Codes that are not linked to an employee yet |
| Mapped | Codes that are linked |
A user that SolaHR once saw but the device no longer holds is marked not on device.
#Map device users to employees
- Open Device users (or the Map employees step when adding the device).
- SolaHR suggests the employee whose employee number equals the device code. This works best when you gave people the same number on the terminal as in SolaHR.
- Review the suggestions and click Confirm N matches.
- For the rest, use Change to pick another employee, or Link a code that is not in the list for a code the device has not reported yet.
- Remove mapping unlinks a code.
Good to know:
- If an employee is already linked to another code on the same device you get a warning; you can still link a second code (some people enrol on two terminals or two fingers under different codes).
- Punches from an unmapped code are not lost. They wait ("Has N punches waiting") and become attendance the moment you link the code: "Linked. N attendance days were written from waiting punches."
- Removing a mapping puts its punches back in the review list.
- If you have no employee number match, do not renumber the terminal in a hurry. Map by name instead, or push the employee to the device so both sides agree from the start (see Manage devices).
The Review tab lists the codes that still need attention, also for push and file-import devices: Unmapped codes with their number of punches and the period they cover. Tick several and click Link N selected. Reprocess pending writes the waiting days now.
#The "Import history from" date
In the last step of adding a device (and when you edit it) you choose Import history from.
| Setting | Effect |
|---|---|
| A date | Punches older than this date are ignored. |
| Empty | Everything stored on the device is imported. |
Choose the first day you want in SolaHR, usually the day you start using attendance (often the start of a payroll period). A terminal can hold thousands of old punches; importing years of history into the middle of a payroll month is rarely what you want. You can also bring older data in later with Import a punch file. Nothing is imported twice: a repeated punch is recognised and counted as a duplicate.
In the same step you choose Check for new punches every 1, 2, 5, 10, 15 or 30 minutes. Save and start sync starts reading; Save (sync stays off) does not.
#How a punch becomes attendance
Scan on terminal -> connector reads it -> SolaHR receives it -> code mapped? -> day written to attendance
|
no -> waits until you link the code
SolaHR applies the same rules as for any other record:
- Punches of a day are paired as in, out, in, out (or by the in/out flag, when the device gives one). All intervals of the day are kept and shown, for example
8:00-12:30, 13:30-17:10. - Times are read in the device's timezone, which you set on the device. If times are off by hours, fix the timezone; if they are off by minutes, use Sync time now (see Manage devices).
- A day that HR or the employee portal already recorded is not overwritten by a device punch. It shows in Rejected punches with the reason.
- Punches before an employee's start date, or while the employee is on an unpaid suspension, do not create attendance.
- A repeated scan within moments is ignored as a Duplicate scan.
- If payroll settings for the date are missing, the punch is kept and counted ("N waiting for payroll settings"); add the settings and Reprocess pending.
#The Activity tab
Activity lists every punch the device sent, newest first, and what happened to it:
| Outcome | Meaning |
|---|---|
| Added to attendance | With the day and in/out. |
| Waiting: map this person | With a Map this person link. |
| Not used | With a reason: before the start date, waiting for payroll settings, duplicate scan, employee suspended. |
#Each device card shows the same story
Punches received (last 7 days) → Matched to employees (for example "12 of 14 device users mapped") → Added to attendance → Waiting / not used. If the numbers shrink from one step to the next, the reason is in Activity or Review.
#Origin chips: where did this record come from?
Every attendance record carries a small chip with its origin. Click it to open Where this came from.
| Chip | Meaning |
|---|---|
| Device · device name · method · location | Built from punches on a terminal. The method is Face, Fingerprint, Card or Password when the device reported it. |
| Portal link | The employee checked in with their personal link on a phone. |
| Entered by HR | Created or changed by a person in SolaHR. |
For device records the window also lists the Device scans: the raw punches the day was built from (when, device code, direction). That is the place to check a disputed day. See Where an attendance record came from.
#Live punches
Most connections are polled: the connector asks for new punches every few minutes, so a scan appears in SolaHR after up to your chosen interval. Live events (a scan appears within seconds) exist only for a few connection types; each connection type shows its abilities (Read punches, Read users, Read clock, Set clock, Live events) when you choose it. At this release live events are limited and software-tested only: the ZKTeco direct connection does not have them, Anviz direct and the ZKTeco SDK type do in simulation, and push devices send each punch as it happens. For payroll, a delay of a few minutes does not matter, because attendance is computed per day.
#Snapshot photos
Some terminals take a photo at the moment of a punch. Where the terminal and the connection type support it and the connector sends it, SolaHR keeps the snapshot privately and shows it with the record as Snapshot taken by the device. Only people who may see both attendance and employees can see it, and it is never public. The ZKTeco direct connection does not carry snapshots; the ZKTeco SDK type is designed to (software-tested only). A snapshot is a normal photo, not a biometric template.
#Quarantine
Events SolaHR received but could not use ("Device not assigned to this connector", "Invalid time", "Missing user code") are kept in Quarantine, never silently dropped. Fix the cause and Replay, or Dismiss the event.