Should a missing checkout reduce salary?
Investigate the source record and apply the agreed policy first. An incomplete punch alone does not establish unpaid absence.
HR operations guide
Missing biometric punches: a review checklist
Investigate missing biometric punches through device logs, employee PIN mapping, connection status and approved corrections before payroll.
A missing punch is an incomplete record to investigate. It can reflect a missed check-in, an unmatched identity, a delayed sync or the wrong date; do not automatically turn it into an unpaid absence.
Identify where the punch disappeared
Find the employee, date and expected arrival or departure. Check whether the terminal has the source punch. If it does, compare the timestamp and user ID with the imported or received record. If it does not, ask the employee and supervisor for the agreed supporting evidence.
Separate a whole-device outage from a single-person exception. Multiple missing records in the same period suggest a connection or collection issue. One unmatched user ID suggests employee mapping. Do not repeatedly edit attendance while the source remains unexplained.
Check the integration path
For Cloud Push / ADMS, review last device activity and pairing configuration. For a LAN-only terminal, the local connector needs access on the private network. For USB reports, verify the exported date range and timestamp format before importing.
Match the stored employee biometric PIN to the enrolled user ID. OPleo excludes PIN 000 and remote employees from device matching. Exact terminal model, firmware and real punch delivery still need acceptance testing; a supported connection mode is not proof that every terminal works.
Correct the record with evidence
Ask the attendance owner to review the source time, employee identity and policy. Use the supported manual attendance workflow where appropriate. Maintain a correction register with original source, reason, reviewer and resulting record; confirm any product audit-history requirement in a demo.
After delayed logs arrive or a file is reimported, compare the resulting employee-day record with the correction. Check duplicates and earliest/latest punches. Never invent a checkout time simply to make a row look complete.
Prevent recurring exceptions
Run an exception review before payroll cutoff and after an offline period. Give employees a clear reporting route and deadline. Keep connector ownership and device PIN maintenance separate from payroll approval so problems reach the right person.
Test a normal day, missing departure, unknown PIN, duplicate import and offline recovery using redacted records. If overnight work matters, test date attribution explicitly rather than assuming a daily first/last punch model fits the shift.
Questions about hr operations guide
Does OPleo store fingerprints?
OPleo processes device user IDs and punch timestamps. Fingerprint and face templates remain on the physical terminal.
Bring your real workflow to the demo
Use a redacted example, your attendance setup and the decisions your team needs to make. We can review fit before you move live records.
Book a workflow demo