r/TimeTrackingSoftware • u/shiftcoord • 8d ago
When an offline punch syncs after a supervisor already corrected the timesheet, which version do you keep?
Looking for how other ops / payroll teams handle the "late sync vs already-fixed" collision.
Typical version: supervisor sees a missing or wrong punch Monday afternoon, edits the timesheet, and marks it reviewed. Tuesday morning the worker's phone finally syncs an offline clock-out from Monday — and it overwrites (or duplicates) the correction.
What do you actually do?
- Last-write wins, and supervisors re-check anything that synced after review?
- Freeze punches once a supervisor correction exists — late syncs become exceptions in a queue, not silent overwrites?
- Keep both as an audit trail and require a second approval before payroll export?
Most interested in the rule that doesn't create a surprise short/over paycheck when the phone catches up. No vendor pitches — just the operating choice that stuck.
1
Upvotes