How Biometrics Connect to Timekeeping#

The Journey of a Punch#

1. The employee scans at a terminal
   A registered device (for example a lobby face scanner) captures the scan and matches the face against your enrolled employees.
2. The attempt is recorded in Face Scan Logs
   Every attempt — matched or not — is logged with its confidence and status, so there's always an audit trail of what the device saw.
3. A successful match becomes a Raw Log
   The recognized punch is written as a time-in or time-out entry against the employee. Manual entries and file imports land in the same place.
4. Time Keeping consumes the raw logs
   For each payroll cutoff, attendance is assembled from these punches and reviewed before payroll is computed.

Station 1: Registered Devices#

Devices are managed under Manpower → API → Device Management. A terminal only feeds your timekeeping when it's registered here and active — each device has a name and location so you can tell your lobby scanner from the warehouse gate.

Device registration and keys: Device Management.

Station 2: Face Scan Logs — Every Attempt, Recorded#

Manpower → Timekeeping Logs → Face Scan Logs is the audit trail of the biometric layer. Each row is one scan attempt with the matched employee, the device it happened on, and how sure the system was:

• Match — the face was recognized confidently; this scan produced a punch.
• Ambiguous — two employees looked too similar to call safely, so no punch was recorded; the employee should simply scan again.
• Offline — the device couldn't reach the server at scan time; the scan syncs when the connection returns.

123

1. 1Status — Match, Ambiguous, or Offline
2. 2Confidence — how certain the recognition was
3. 3Online — whether the device was connected when it scanned

Columns and filters in detail: Face Scan Logs.

Station 3: Raw Logs — The Punches Themselves#

Manpower → Timekeeping Logs → Raw Logs Browse holds the actual time-in / time-out entries, whatever their origin. The Source column tells you how each punch arrived — from a device, a file import, or a manual entry — so a disputed punch can always be traced back.

123

1. 1Date range — the window you are inspecting
2. 2Source — device, import, or manual entry
3. 3Export — download the raw punches

See Raw Logs Browse.

No Terminal? Import or Encode Time#

Biometric devices aren't the only way in. Manpower → Timekeeping Logs → Time Importation takes a spreadsheet of time logs through a guided wizard (configure → upload → validate), and individual punches can be encoded manually — both end up as raw logs, identical in behavior to device punches.

The wizard step by step: Time Importation.

Station 4: Into Payroll#

Come cutoff time, Manpower → Payroll → Time Keeping assembles those punches into per-employee attendance for the period — the numbers a reviewer checks before payroll is computed. From there the flow continues in How to Process Payroll.

When a Punch Seems Missing#

1. Check Face Scan Logs first
   Was there a scan attempt at all? An Ambiguous status means the scan didn't produce a punch — the employee needs to re-scan.
2. Check the device
   An Offline scan syncs later — confirm the terminal is active in Device Management and has recent activity.
3. Check Raw Logs
   If the scan matched but no raw log exists in the date range, widen the date filter — punches near midnight can land on the neighboring day.
4. Encode it manually if needed
   A genuinely lost punch can be entered as a manual raw log; the Source column keeps the correction transparent.