5 Payroll Controls Employers Should Review After the Federal Court Underpayment

A payroll system can process the hours entered into it correctly and still produce the wrong entitlement.

That is the more useful lesson from the Federal Court of Australia’s recent payroll underpayment issue.

The Court identified a payroll configuration issue affecting casual employees who recorded fewer than four hours on their timesheets. Those employees were not paid the four-hour minimum engagement entitlement required by the relevant enterprise agreements. The issue affected 248 current and former employees after August 2018.

The obvious response is to check whether timesheets are accurate. But that only checks part of the payroll process.

The harder question is whether the rules sitting between time recorded and pay calculated are working properly.

Payroll Leadership Institute of Australia (PLIA) has published a detailed analysis of the Federal Court payroll underpayment case and the broader governance lessons it raises. (Link this anchor to the Google Site analysis article.)

For payroll teams reviewing their own controls, these are five areas worth testing.

1. Check minimum engagement rules

Minimum engagement provisions are easy to miss because the employee's timesheet can be completely accurate.

Consider a simple example:

An employee clocks 1.5 hours.

The timesheet records 1.5 hours.

Payroll receives 1.5 hours.

The applicable employment condition requires a four-hour minimum engagement.

The employee should therefore be paid for four hours.

Nothing necessarily went wrong with the clock-in, timesheet or transfer of attendance data.

The problem occurs if payroll treats hours worked as automatically equal to hours payable.

That distinction should be tested anywhere a Modern Award, enterprise agreement or other applicable employment condition contains a minimum engagement or minimum payment rule.

Don't just ask whether the rule exists in the Award or agreement. Ask whether the payroll process actually recognises the circumstances that trigger it.

For example:

• Which employees does the rule apply to?

• Does it apply to every engagement or only particular types of work?

• What happens when someone clocks fewer than the minimum hours?

• Is the adjustment automatic or dependent on somebody noticing it?

• Can a roster or timesheet override the entitlement?

A clean timesheet is not evidence that the employee has been paid correctly.

2. Check how Awards and agreements have been translated into payroll logic

Payroll teams generally know which Award or enterprise agreement applies to their workforce.

The control question is different:

Has that instrument been translated correctly into the system that calculates pay?

Depending on the workforce, that could include rules covering:

• minimum engagements

• overtime thresholds

• weekend penalties

• public holiday rates

• allowances

• split shifts

• meal and rest breaks

• classifications

• higher duties

• different roles or work locations

This is where payroll assurance needs to get more specific than "we reviewed the Award".

Take overtime as an example. It is not enough to know that overtime exists. Payroll needs to know exactly when the entitlement is triggered, which hours count towards the threshold, what rate applies and whether another employment condition changes the calculation.

The same applies to classifications. Having the correct hourly rate configured is little help if an employee has been assigned to the wrong classification or performs work that changes the rate that should apply.

The exercise is essentially a translation test:

Employment condition → payroll rule → calculated outcome.

Each part needs to agree with the next.

3. Deliberately test awkward payroll scenarios

Normal payrolls are often poor tests of payroll configuration.

An employee works their usual roster, on their usual days, in their usual role. The system produces the expected result.

That tells you the ordinary case works.

It tells you very little about the edges of the rule.

A better payroll control is to deliberately create unusual scenarios and calculate what the employee should receive before comparing that amount with the system result.

For example, test:

• a 90-minute casual shift

• a three-hour weekend shift

• work performed on a public holiday

• an employee crossing an overtime threshold

• a classification changing during a pay period

• a split shift

• an employee working two different roles

• an employee working across different locations

• a shift that triggers an allowance

• a manual adjustment to ordinary hours

These are the cases most likely to expose assumptions buried inside payroll configuration.

You don't need to test every employee. Build a small library of scenarios that represent the unusual conditions in your workforce and re-run them periodically.

If a rule only fails when something unusual happens, testing nothing but ordinary pay periods gives it plenty of room to hide.

4. Treat payroll changes as a reason to re-test

Payroll configuration is not something that can be set once and assumed to remain correct.

The underlying conditions change.

An Award can be varied. An enterprise agreement can be replaced. An employee can move classification. A business can open another workplace, introduce new shift structures or start using employees differently.

The system itself can change too.

Common triggers for payroll re-testing include:

• Award changes

• new or updated enterprise agreements

• payroll software migrations

• payroll configuration changes

• new employee classifications

• changed rostering practices

• new locations or departments

• changes to allowances

• new work patterns

• manual overrides becoming common

Some changes look minor from an operational perspective but can alter how an entitlement should be calculated.

A useful control is therefore simple:

Whenever the legal rule, employee structure or payroll system changes, re-test the affected entitlement calculations.

That re-test should happen against a known expected outcome.

Don't simply confirm that the new field, rate or configuration has been entered. Run a scenario through payroll and check the resulting pay.

5. Reconcile entitlements, not just inputs

Payroll reconciliation often focuses heavily on whether the information flowing into payroll matches the source data.

That is necessary, but it answers only one question.

Input reconciliation asks:

Did payroll receive the same hours that were recorded?

If the timesheet says eight hours and payroll receives eight hours, that control passes.

Entitlement reconciliation asks:

Did those eight recorded hours produce the amount the employee was entitled to receive?

That second test can catch problems that the first one cannot.

An employee may have eight perfectly recorded hours but still be underpaid because the wrong penalty rate, allowance, overtime rule, classification or minimum payment condition was applied.

This is why payroll assurance should not stop at confirming that information moved correctly from rostering or timekeeping into payroll.

The calculation itself needs to be challenged.

A practical sample review might take a selection of employees, independently work out what each employee should have received under the applicable conditions, and compare that figure with the payroll result.

Where there is a difference, work backwards.

Was the underlying employment condition identified correctly? Was the employee configured correctly? Did the system apply the rule? Was there a manual override?

That tells you much more than simply confirming that the timesheet matched the pay run.

Payroll Control Review

A payroll team looking at its controls after the Federal Court issue could start with these questions:

• Are minimum engagement and minimum payment rules configured for the employees they apply to?

• Are current Award and enterprise agreement conditions reflected in payroll configuration?

• Have unusual shift and pay scenarios been deliberately tested?

• Are overtime, penalties, allowances and classifications tested as calculations, rather than simply checked as system settings?

• Are manual overrides reviewed?

• Are payroll rules re-tested after system or configuration changes?

• Does payroll reconciliation check employee entitlement as well as hours entered?

• Is there a clear process for updating payroll when an Award or enterprise agreement changes?

• Can the payroll team explain why the system produced a particular payment, not simply confirm that it processed successfully?

The Federal Court issue is a useful reminder because the failure was not simply about whether an employee's hours had been captured.

It was about what payroll did with those hours.

For employers, that is the control worth examining.

The Payroll Leadership Institute of Australia (PLIA) provides education and commentary focused on payroll governance, compliance and the development of the payroll profession.