Time and Attendance: Why a Door Swipe Is Not a Payroll Record

Safsale Editorial · U.S. Field Guides

An access event establishes that a credential was used at a reader. It does not, by itself, establish when an employee began or stopped working. Remote work, missed punches, shared entrances, paid breaks, and off-site assignments can all make the two timelines different.

Define the authoritative workflow

Document how employees report time, how supervisors review exceptions, and how payroll receives approved records. Access events may help investigate a discrepancy when their use is authorized and appropriate, but should not silently overwrite reported work time.

Protect the correction trail

A practical system preserves who changed a record and when. Give payroll, supervisors, and security only the access their roles require. Test account removal and permission changes when an employee transfers departments. Avoid collecting biometric identifiers simply because a terminal offers the feature; first establish need, alternatives, and the applicable privacy obligations.

Test a pay-period close before rollout

Use synthetic records for a missed punch, overnight shift, time-zone difference, and approved correction. Confirm that exports preserve the intended dates and that an integration retry does not create duplicate entries. Have payroll review the outcome before connecting live records.

The U.S. Department of Labor explains federal recordkeeping in its FLSA recordkeeping fact sheet. State and local requirements and the actual employment arrangement also need review. Hardware selection should follow the approved timekeeping process, not determine it.

Continue the field-guide series

Hiring a Security Equipment Salesperson: Use a Structured Work Sample

Planning a project? Contact Safsale with the site requirements, existing equipment, and questions that need manufacturer verification.