Award Interpretation Software

What is award interpretation?

Award interpretation is the process of working out what a Modern Award entitles an employee to be paid for a given set of hours. Australia has more than 120 Modern Awards, each setting minimum rates, penalty loadings for weekends, evenings and public holidays, overtime thresholds, casual loading, and a list of allowances. Interpreting an award means taking a record of hours worked and applying every relevant rule to it to produce the correct minimum pay.

For most employers this is invisible because a payroll system does it automatically. But under complex awards — and the SCHADS Award is one of the most complex in the country — the interpretation is genuinely hard: overtime that accrues across a whole day rather than a single shift, sleepovers paid as an allowance plus overtime when the worker is woken, broken shifts that attract a separate allowance, and travel between clients that is paid but easily missed. Getting the interpretation right is the difference between a defensible pay run and a systemic underpayment.

Why rule engines fail on real-world timesheet data

A payroll rule engine is, by design, deterministic: it expects each row to arrive in a known shape — a start time, an end time, a pay code, a classification — and then applies the award maths. That works beautifully when the data is clean. The problem is that real provider data rarely is.

NDIS and aged-care providers export timesheets from a dozen different systems, each with its own column names, date formats, and conventions. One export labels a sleepover in the cost-rate column; another buries it in a note. An overnight shift is split across two rows in one system and folded into one in another. Allowance lines have no times at all. Casual overtime is sometimes already applied and labelled, sometimes not. A rule engine fed this data either rejects it, requires a manual mapping step for every new format, or — worst of all — silently mis-classifies a row and produces a confident wrong number.

This is the gap CrossVault closes. Instead of demanding one canonical schema, it uses AI to read the timesheet the way a knowledgeable payroll officer would — recognising a sleepover however it is labelled, connecting the rows of a split overnight shift, spotting an allowance line with no time, and understanding pay that has already been applied. It interprets the document first, then interprets the award. See the timesheet validator for the full feature set.

Interpretation plus explanation, not just a number

A bare pay figure is hard to act on and impossible to defend. CrossVault's interpretation is built to be checked. For every line it flags, it returns a plain-English reason — "this 2am call-out during a sleepover should be a one-hour minimum payment at the overtime rate", "these two same-day shifts combine to cross the daily overtime threshold" — anchored to the SCHADS clause behind it.

That matters for two reasons. First, your payroll officer reviews a short list of genuine, explained exceptions instead of re-deriving the award on every line or trusting a black box. Second, you end up with a record of what was checked and why each entitlement was calculated the way it was — the evidence Fair Work expects an employer to be able to produce. For the award rules themselves, our SCHADS compliance guide walks through the obligations CrossVault interprets against.