PINs, fingerprints and who a punch belongs to
A machine does not know anybody's name. It knows a number — the PIN — and a fingerprint or a face that it has been taught to match to that number. Everything else is the server's job.
So a punch arrives as a PIN, a time and nothing else, and the PIN is the only thread back to a person.
Before you start
- The
employee.editpermission to give somebody a PIN. - A connected machine. See Connecting an attendance machine.
Steps
- Put the number in the attendance code field on the employee's record. It is the PIN they will type or that the machine will show.
- The machines at their branch are told the PIN and the name automatically, the next time each one asks for work.
- Enrol the fingerprint or the face at the machine itself. That part cannot be done from here: the template never leaves the machine, and somebody who uses two machines enrols at both.
What you should see
The machine shows the name when they punch, and the punch reaches the attendance grid attached to the right person.
Two things the machine reports are deliberately ignored:
- Its in/out flag. Which stretch of a shift a punch belongs to is decided by the shift's window, not by whichever button somebody pressed. This is the same rule the Mini App follows, and it is what lets a shift be corrected after the fact.
- The order of punches. A machine that sends yesterday's backlog today does not produce yesterday's attendance in the wrong order.
How somebody identified themselves — fingerprint, face, card, password — is kept, for looking up afterwards, and used for nothing else.
If something goes wrong
PINs nobody has claimed — somebody punched with a PIN no employee has. The punches are kept rather than dropped, and the list shows the PIN with how many are waiting.
Give the PIN to the right person from that list and the old punches join up to them. That is the whole reason they were kept: a new employee who used the machine for a week before HR got to their record does not lose the week.
A PIN was given to the wrong person. Change it. The punches follow the PIN, so they move with it.
Somebody left and the machine still knows them. Disabling the employee queues a deletion to the machines at their branch. A machine that is offline gets it when it comes back.
Two people were given the same PIN. They cannot be: an attendance code is unique within a company, and the second attempt is refused. Across companies it does not matter — a PIN is only ever read alongside the serial number of the machine that sent it.
Last checked 19/09/2026