Start with employee and device mapping
Match each device identifier to the correct employee record. Confirm the device clock, location and punch direction before importing data. Keep raw events available for investigation; an incorrect mapping can make a technically successful import produce the wrong attendance result.
Apply working-time rules consistently
Pair events using the relevant shift and device configuration. Treat duplicate punches, breaks and overnight work as explicit cases. Distinguish recorded presence from approved payable time. The attendance policy should explain how late arrivals or missing events are reviewed rather than leaving those decisions to an undocumented spreadsheet formula.
Approve exceptions before the payroll cutoff
Show managers the records needing attention, together with their underlying timestamps. Record the reason for each correction and retain the original events. Only the approved attendance result should enter the payroll calculation; later corrections should follow a visible adjustment process.
Worked example
An employee taps twice at 09:00 and once at 18:00. Counting three events as three separate work periods is incorrect. Review duplicate handling and punch direction before calculating the day's attendance.
Practical checklist
- Verify employee IDs and device clocks.
- Preserve raw punches alongside interpreted attendance.
- Review missing and duplicate events before payroll.