Late punches should follow the rules from that day — not today’s rewrite
When a terminal reconnects days later, payroll still needs the policy that was in force when the punch happened.
Attendance systems often break trust in a quiet way: a rule changes on Monday, offline punches arrive on Thursday, and yesterday’s day is judged with today’s settings.
Finance and compliance usually ask the same question — what rule applied when this happened? If the answer is “whatever is configured now,” disputes get harder to close.
Neo keeps policy history with the record. When late events sync, they are judged against the rules that were live at the time of the punch. Changes leave an audit trail instead of silently rewriting the past.
If your sites go offline, or your overtime rules change mid-month, that history matters as much as the punch itself.
Want to see how this fits your sites?
We can walk through attendance, pairing, and device choices on a short call.