Employment Hero Award Not Calculating Correctly: Fixes

All blogs & guides

Checked against Employment Hero’s Help Centre and current Australian guidance on 13/08/2026.

The short version

1. A pre-built award still needs the correct classification, work types, shift conditions, pay-period boundaries and roster inputs.
2. Public-holiday and midnight-spanning shifts are essential test cases because they expose rule-boundary errors.
3. Unlocking an Employment Hero rule set transfers ongoing maintenance to the business.

Full detail below.

The symptoms you’re probably seeing

If your Employment Hero award rates are not calculating correctly, begin with the employee assignment and the inputs that drive the rule set. As a Certified Employment Hero Partner, we test the full path from award coverage and classification through Work Types, Shift Conditions, Tags, rule-set periods and roster data. Common symptoms include:

• Saturday or Sunday shifts paying the base rate instead of the penalty rate
• Overtime that never triggers, even once someone’s clearly worked past the threshold
• Casual loading that’s missing entirely, or stacked on top of a rate that already includes it

If your numbers are wrong in a different way, superannuation for example, that’s a different setting entirely. Our guide on superannuation calculating wrong covers that one specifically.

Employment Hero award not calculating: why errors happen

A rule-set or classification mismatch is a useful first hypothesis, especially after onboarding, a duty change or a rushed Employment Hero payroll implementation. The Employment Hero platform also relies on Work Types, Shift Conditions, Tags, rule-set periods and complete roster inputs. Any one of those can produce a plausible but incorrect result without an error message. If the configuration and inputs test correctly, reproduce the case and escalate it to Employment Hero support.

That’s also why these errors are so easy to miss. The pay run finalises, the numbers look believable, and nobody notices until an employee questions their payslip or an audit turns it up months later.

The pattern of the error is a useful clue before you even open a pay run. A rate that’s wrong in the same specific way every time (always base rate on a Saturday, overtime that never triggers no matter how long a shift runs) points at one of the three rule-set inputs below. Numbers that are wrong inconsistently, correct one week and off the next for the same employee, usually point somewhere else, like a manual override or a one-off correction that was never removed.

Checks to run yourself

Run these in order, then test the Work Types, Shift Conditions, Tags and roster data used by the affected shift.

Check 1: Award coverage and employee assignment

First confirm whether a Modern Award, enterprise agreement or award-free arrangement applies. Employment Hero cannot decide coverage from a job title. For an award-covered employee, confirm the relevant employment agreement, award package, classification and pay-rate template are assigned. An employee left on ordinary pay settings will not receive the award rule outputs expected from the roster.

Check 2: Classification level vs actual duties

Within a Modern Award, the classification level, not the award alone, sets the base rate and, in some awards, the casual loading percentage and allowance eligibility. This is the setting that drifts fastest, because it’s usually set once at onboarding and rarely revisited. An employee promoted from a junior to a senior role, or moved from casual to permanent, keeps their original classification in the system unless someone updates it manually. Wrong looks like a base rate, and everything calculated off it, sitting one or two classification levels behind what the person does. Right looks like classification reviewed and updated at every duty change or pay-point movement, matched against the award’s own classification descriptors instead of a job title.

Check 3: Rule set period, weekly vs fortnightly anchor day

Overtime and averaging thresholds in most awards are defined over a period, an ordinary hours cap for the week or its fortnightly equivalent, anchored to a specific day the period resets. If the rule set period doesn’t match how the business rosters, the threshold gets checked on the wrong cycle. A business that rosters and averages hours fortnightly, but has its rule set configured to reset weekly, or with the anchor day misaligned to the real start of the roster week, will see hours split across two periods and never accumulate enough in either one to trigger the loading. Right looks like the rule set period and anchor day matching both the award’s own averaging provisions and the roster cycle the business runs on.

Setting	What wrong looks like	What right looks like
Coverage and assignment	Award-covered employee left on ordinary settings	Coverage confirmed and the correct award package, classification and template assigned
Classification level	Outdated level, doesn’t match current duties	Reviewed and updated at every duty or pay-point change
Rule set period	Doesn’t match the real roster cycle	Period and anchor day match the actual roster

Award clauses that need deliberate test cases

The pre-built rules are a strong starting point, but the roster still has to exercise the conditions that matter to the business.

Under the current Hospitality Industry (General) Award, a full-time or part-time employee’s split shift can span no more than 12 hours. The gap between the two parts must be at least two hours, and a split-shift allowance applies. Part-time employees also have a three-hour minimum ordinary engagement. Ordinary shifts generally require a 10-hour break, reduced to eight hours only on a roster changeover. Annualised wage arrangements sit in clause 24; clause 25 is the separate managerial salary absorption provision. We translate the employee’s agreed hours, split shifts and salary arrangement into test cases before relying on the rules.

SCHADS needs a different set. Broken shifts, sleepovers, 24-hour care and on-call periods can interact on the same roster. From the first full pay period on or after 1 June 2026, work immediately before and after a sleepover can total up to 12 ordinary hours by agreement, with no more than eight ordinary hours on either side. Work beyond the applicable limit is overtime. We test each supported roster pattern, including the sleepover and surrounding work, before go-live.

Public-holiday shifts and shifts crossing midnight belong in every award test pack. Both cross rule boundaries that a simple weekday shift will not reveal. The 2026 award rates also increased 4.75% from the first full pay period on or after 1 July; the full payroll-year context is in our 2026-27 payroll changes guide.

Unlocking and plan entitlement need checking before customisation

Employment Hero locks installed award packages by default. Unlocking permits custom rules, but the business then owns the customisation and its ongoing maintenance. Locking the package again can revert custom work. We clone and document the business-specific decisions, test them with Employment Hero’s Test Rules tool and retest after every relevant award update.

Employment Hero’s Help Centre also uses different product labels for award installation: its award setup guide refers to Premium Payroll, while other plan material has used Plus. We confirm the entitlement against the client’s account and contract before promising an award build. Our pre-built awards guide explains the business decisions that sit between installing a package and trusting a pay run.

When these checks don’t fix it

If the numbers are still wrong, or the error spans several pay cycles, this is no longer a quick settings fix. Confirm what the award requires for the role, identify the affected period and reconcile any amount owed. Payd Co handles that through award rule-set audits and payroll implementation support, with the award interpretation, test evidence and correction documented together.

Payd Co’s support window opens at 9:00am AEST and closes at 5:00pm AWST, so east- and west-coast pay teams can reach the same managed support process across the business day.

How do I tell whether this is configuration or an Employment Hero product issue?

Reproduce the affected shift after checking coverage, classification, Work Types, Shift Conditions, Tags, rule-set period, roster input and any manual overrides. If the configured test still differs from the current award or agreed arrangement, retain the test evidence and escalate it to Employment Hero support. Do not assume either configuration or the product is at fault before that comparison.

Do I owe back pay if the rule set was wrong?

Possibly, depending on how long the misconfiguration has run and how many employees it’s touched. An underpayment running for months is a back-payment liability under the award, and it deserves proper reconciliation instead of a quiet setting fix. Correcting the setting only stops the liability growing; it doesn’t clear what’s already owed.

Which awards need broader payroll test coverage?

Awards with interacting penalties, allowances, minimum engagements, averaging periods or special roster rules need broader tests. HIGA and SCHADS are useful examples, as are relevant construction and manufacturing awards. The appropriate test pack depends on the clauses and working patterns used by the business; these examples are not a ranking of legal risk.