Understanding the "Casuals" Location in Your Roster Template

Every users profile in Tempus carries a “default location”. For a permanent staff member who only ever works one site, this seldom matters. For a casual who works across several locations within the same organisation, it can cause a real problem with how their 8% PAYG is coded.

⚠️ Note: The Casuals location is a coding location, not a rostering one. A casual's actual shifts stay recorded against whichever site they were rostered to and worked at.

The Problem with Relying on a Default Location

Say a casual works shifts across Location A, Location B and Location C within the same pay run, but their profile is set to default to Location A. Left as is, the whole of their 8% PAYG for that pay run is coded to Location A, even if most of the hours they actually worked that period were at Location C. It is the default location on the profile, not the work actually performed, that decides where the cost lands.

Why We Use a Separate Casuals Location

Rather than letting the 8% PAYG land on whichever default location happens to be set, which may have little to do with where the casual actually worked that period, it is coded instead to a location called Casuals. This does not split the cost across sites on its own. It stops the amount from being misallocated to an arbitrary default, and holds it in one place instead, ready for the organisation to split correctly if they choose to.

Splitting the Coded Amount Yourself

From there, it is a discipline that sits with the organisation, not with Tempus. Using the data available in either the Timesheets Report or the Pay Run Audit Report, the organisation can split the pooled Casuals figure across the real sites however they see fit, at the accounting package stage in their own accounting software (e.g. via a manual journal entry).