How-to guides Biometric devices
Check that a biometric scan reached Aajar
A five-minute test for when someone scans and their attendance does not show: where to look, and what each result means.
Use this when someone showed their face or finger, the terminal said it worked, but nothing appears in Aajar. Work through the steps in order; each one tells you where the scan stopped.
Step 1: look at the Punch log
- Open Biometric Devices and scroll to Punch log. Press Refresh now.
- Filter by Device or by the person, and look for a line with the time of the scan.
What you see, and what it means
| What the Punch log shows | Meaning | What to do |
|---|---|---|
| A line with the person's name and IN or OUT | The scan arrived and was matched. | Reload the Attendance page. It does not update by itself. Check the person's calendar there. |
| A line marked Unmatched | The scan arrived, but nobody has that Biometric ID. | Type the number shown in the line on the person under Employee biometric IDs. |
| A line marked repeat | A second scan within the repeat window (2 minutes by default). It is kept but not counted. | Nothing to do. |
| A line at the wrong time (hours early or late, or in the future) | The terminal's clock is wrong. | Fix the date, time and time zone on the terminal. Aajar reads the terminal's time as your organization's local time. |
| No line at all | The scan never reached Aajar. | Go to Step 2. |
Step 2: is the terminal talking to Aajar?
- On the device row, read the status. Online just now or a few minutes ago means it is connected. Never connected or hours ago means it is not reaching us.
- Read Latest scan on the same row to see when Aajar last received a scan from it.
- If it is not connected, press Setup and compare the server address, port and Comm Key with what is typed on the terminal. See the guide for your brand, or "Troubleshoot a biometric device that will not connect".
Step 3: is the person recognised by the terminal itself?
If the terminal showed "not registered", "verification failed" or did not beep, the scan never counted on the terminal either. Re-enrol the person on the terminal. Aajar only receives scans the terminal accepted.
Step 4: does the terminal send in real time?
Some terminals send scans in batches. In the terminal's cloud server or ADMS menu, look for a setting such as Transfer mode: Real-time or a transfer interval, and set it to real time or 1 minute. Some terminals also send only when they restart after the setting changes.
A quick test you can repeat
- Open the Punch log and note the time.
- Scan once on the terminal and wait one minute.
- Press Refresh now. The scan should appear. If it does, the connection is fine and any missing attendance is a matching problem (Step 1).