Timesheets and pay
A rostered shift is a plan. A timesheet is a fact. Keeping those two apart, and paying people from the second one, is the difference between a pay run you approve in an afternoon and a pay run you reconstruct.
Workers clock in and out on their phone and the location comes with it. If they are not where the shift is, that gets flagged for somebody to look at — it does not stop them working. A support worker standing on the wrong side of a car park is a question, not a locked door.
Where the actual hours differ from the rostered ones, the differences are gathered in one place and approved together, and every decision lands on the audit trail as you go. A coordinator finishes a day, instead of opening thirty records to find the four that moved.
Classifications, penalties, allowances, sleepovers, travel time and kilometres all get applied to the hours you approved. Leave sits on the same record, so somebody being away is not a thing you reconcile afterwards.
The pay run reads the approved timesheets directly. Nothing is exported to a spreadsheet and imported back — which is the exact step where two sets of numbers stop agreeing and nobody can say when.
The part that is hard to copy
The same shift becomes the timesheet, the billable, the claim line and the payslip. Nothing is re-keyed at any of those handovers, so the money you claim and the money you pay come from one fact — instead of from two systems that agree right up until the fortnight they do not.
Not modules you buy separately. They read the same records, which is why nothing between them ever needs reconciling.
Build a week that already passes the award
Read about it →What the breach costs, before you publish
Read about it →Bulk claims that match their own remittance
Read about it →Notes tied to the goal they were for
Read about it →Clocks that run whether or not anyone remembers
Read about it →Authorisation that expires on its own
Read about it →Evidence that accumulates instead of being assembled
Read about it →