Attendance audits

Go to Audit & Logs → Attendance audits to review check-in and check-out attempts recorded by the system. Records include attempts from biometric readers, the mobile app, and manual entry.

What is logged

Each attempt records:

Employee Name: who tried to check in or out.
Attendance date: the date and time of the attempt.
Device: the device type, such as fingerprint, facial, iris, nfc, mobile-app-scan, or web-admin-manual-registration.
Status: new_attendance for a check-in and attendance_exit for a check-out, both with a green badge, and failed with a red badge.
Failed code: the system error code when the attempt failed, such as duplicate_punch. Left blank when it succeeded.
Message: a readable description of the outcome or the failure.
Source: where the attempt came from, such as app-scan, nfc-scan, manual, or org-device-app. A manual entry also names the administrator who created it.
Created at: when the attempt was recorded.

Find and export records

Search by employee name or filter the records by:

Attendance Date
Log Date, which defaults to the last 30 days
Employee
Statuses
Devices
Sources
Manually Created By

Export the filtered results to Excel or PDF.

Common failure codes

The Failed code column shows the raw system code. The codes you are most likely to see:

Code	Meaning
`duplicate_punch`	A punch within the deduplication window, less than a minute after the previous punch
`no_ongoing_schedule`	The employee had no ongoing work schedule at the time
`schedule_not_for_attendee`	The scan matched a schedule the employee does not belong to
`cross_site`	A scan at a site the employee is not rostered at, for example a wrong site or a face false match
`ambiguous_overlap`	The scan fits two or more sessions, and a person needs to choose one
`off_roster`	The scan fits nothing, and the employee is not rostered that day
`employment_ended`	The scan came from someone whose employment has ended
`unknown_identification`	The number the reader sent is not assigned to any employee
`number_already_assigned`	The enrollment number is already assigned to someone else

Check the Message column for additional context about a failed attempt.

When to use attendance audits

Troubleshoot devices: identify repeated failures and their reasons.
Investigate attendance disputes: verify whether an attempt was recorded and what result it returned.
Review compliance records: examine the attempts captured by the system, including failures.

Audit logs: records of administrative actions.
Device logs: records of data submitted by each reader.
Devices & agents: assign unmatched enrollment numbers. These attempts appear with the unknown_identification code.