Monitor a device and unrecognised punches

What this achieves

A terminal that stops reporting does not announce itself — the days it should have recorded never appear at all. This is where you confirm a device is still in contact and find punches that arrived under a number nobody is associated with.

Required role: Administrator.

Steps

Go to Time & Attendance → Attendance Machines.
Check the Last seen column across your devices.
Open a device to see its detail.
Read Recent punches to confirm what has arrived.
Read Device users to see which numbers are associated with which employees.
Read Unrecognised punches for punches made under a number that is not.

Last seen is the health check

Every device carries a last-seen time, and a device that has never reported says so rather than showing a blank.

Scan this column rather than waiting for somebody to report a missing day. A terminal knocked off its network on a Friday costs you a week of attendance for everybody who uses it, and the first complaint usually arrives after the pay period closes.

Example: the terminal at the Manchester site shows a last-seen time three days old while the London one is current. Nobody at Manchester has raised anything, because from their side the terminal still beeps when they use it.

Device status

Option	Description
Active	The device is accepted.
Inactive	The device is not currently accepted.

A device set inactive stops being accepted without being removed, which is the difference between pausing a terminal and retiring one.

Recent punches

The punch feed lists what has arrived from this device, each entry recorded as a check in or a check out. It is the fastest confirmation that a newly configured terminal is working, and the fastest way to tell a device problem from a reconciliation problem.

If punches are arriving here but attendance days look wrong, the device is fine and the question belongs with your attendance rules rather than your hardware.

Device users

Each person is identified on the terminal by a number, and this panel shows which of those numbers belongs to which employee. Where a number has no employee against it, the entry reads as an unknown employee.

Creating these associations is not done from this screen. Treat the panel as the record of what is currently associated, and keep your own list of who has been issued which number on the device.

Unrecognised punches

Where somebody punches with a number that is not associated with an employee, the punch is kept and listed here. The panel states the important part: nothing is lost, and these resolve once the number is associated.

Watch this list after any change to who uses a terminal. A new starter enrolled on the device but not yet associated punches in and out perfectly well, and none of it reaches their attendance until the association exists.

Example: a new warehouse starter at HC Corp UK Ltd is enrolled on the terminal on their first morning. Their punches arrive as unrecognised, so the days are held rather than lost, and nobody is credited with them in the meantime.

A queue that keeps growing is the signal that numbers are being issued on terminals faster than they are being recorded in Humavera.

Removing a device does not remove its punches

The removal confirmation states this: punches already recorded are kept, and the device stops being accepted. Removing a terminal that has been miscounting does not clean up what it already sent — correct those days through attendance corrections.

What happens next

Punches from a device build the same attendance days as self-service check-in, so reviewing, correcting, and approving them is unchanged. Where a device has been down, expect corrections rather than punches: the days it missed have to be raised and approved by hand.