Loading
Because attendance is captured operationally and payroll is calculated financially, from two sources that were never joined. The difference is reconciled by hand, monthly, by someone who has to choose which to believe.
The record of who worked when: attendance against rostered shifts, with variances visible as they happen rather than at the end of the month.
Attendance lands against the shift it belongs to. Planned against actual is visible per person and per team, so a pattern of consistent overtime shows up in week two rather than in the pay run.
Someone rostered for 37.5 hours records 44. The variance appears on the attendance report immediately, and the approval that authorises the extra hours is on the record before payroll runs.
No biometric or geofenced capture. Clock-ins are app and web based, which some field operations will find insufficient.
Approved hours become the payroll line in Books and project cost in Loop. Capacity planning reads the roster.
Yes, per team and per person, including rotating patterns.
They stay visible and unpaid until approved. Nothing is silently included in a run.
Through a regularisation request, which is approved and recorded rather than typed over the original.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.