Multi-State Public Holidays: Applying the Right Penalty for NDIS Payroll

Ask most payroll officers which days are public holidays this year and they will name a handful of national dates. Ask them whether those dates are the same in every state and the answer gets less confident. For a care or NDIS provider that operates across more than one state or territory, that uncertainty is not academic. It is the difference between paying a support worker correctly and quietly breaching the SCHADS Award on the same shift.

Public holidays in Australia are not set by a single national body. They are declared and gazetted by each state and territory government. That means the public holiday calendar is genuinely different depending on where a shift is worked, and a provider that applies one calendar to a workforce spread across borders will get some pay runs wrong without ever noticing. This article explains why the calendars differ, what goes wrong when providers ignore it, and how to apply the correct public holiday penalty automatically.

Why do public holidays differ between Australian states?

The starting point is constitutional. Public holidays are declared under state and territory legislation, so each jurisdiction maintains its own list. A handful of days are observed nationally, but many are local, and the local ones are where multi-state payroll comes undone.

A few examples make the pattern clear:

• Labour Day is a public holiday in every state, but on different dates. It falls in March in some states, May in others, and October in others again. There is no single national Labour Day.
• Regional show days such as the various agricultural show days are gazetted in specific states, and in some cases only in specific regions or towns within a state.
• Local one-off events such as Picnic Day, Melbourne Cup Day, May Day and Bank Holiday exist in some jurisdictions and simply do not appear in others.
• Substitute days are applied differently. When a fixed-date holiday such as Christmas Day or Anzac Day falls on a weekend, states decide independently whether and how to move the observed public holiday to the following weekday.
• Part-day public holidays, such as the evening of Christmas Eve and New Year's Eve, are gazetted in some jurisdictions and not others, with penalty rates that apply for only part of the day.

The consequence is that the same calendar date can be a full public holiday in one state, a part-day holiday in a second, and an ordinary working day in a third. For a provider running shifts in each of those states on that date, three different pay treatments are correct at the same time.

What goes wrong when providers use one public holiday calendar?

The natural instinct for a growing provider is to set up one public holiday list, usually based on the head office state, and apply it to every shift. It feels tidy and it works until the business crosses a border. From that point on, a single calendar produces errors in both directions on the same pay run.

Over-payment. When the head office calendar marks a day as a public holiday but that day is an ordinary working day in the state where a shift was actually worked, the provider applies a public holiday penalty that is not owed. On the SCHADS Award that means paying 250% (or 275% for casuals) for what should have been an ordinary shift. The worker is not harmed, but the provider erodes its own margin and, for NDIS work, may bill or absorb a cost that does not reconcile against the funded rate for that day.

Under-payment. The more serious error runs the other way. When a day is a gazetted public holiday in the state where the shift is worked, but the head office calendar does not list it, the provider pays ordinary rates for a public holiday shift. That is an underpayment and a breach of the award. Underpayments accumulate quietly across every affected worker and every affected date, and they surface later as back-pay liabilities, interest and potential penalties.

These are the same category of failure we cover in how to avoid SCHADS underpayment claims and wage theft prevention for care employers. Public holidays just make the error harder to see, because it only appears on a handful of dates a year and only for workers in particular states.

How should penalties be applied for a multi-state workforce?

The correct principle is simple to state and harder to operate manually: the public holiday penalty is determined by where the shift is worked, not where the provider is registered and not where the worker lives. A support worker delivering a shift in one state on a day that is a public holiday there is entitled to the public holiday rate for that state, regardless of the head office location.

Under the SCHADS Award, when a day is a public holiday in the location of the shift, the penalty rates are well established:

The rates themselves are not the difficult part. The difficult part is deciding, for each shift, whether the day counts as a public holiday at all. To do that reliably across a multi-state workforce, a provider needs three things working together:

1. A per-location public holiday calendar that knows the gazetted holidays for every state and territory the provider operates in, including different Labour Day dates, local show days, substitute days and part-day holidays.
2. A clear rule for which location governs each shift, so that every shift is tied to the state where it is delivered rather than a default head office state.
3. Automatic penalty selection, so the payroll engine looks up the correct calendar for the shift's location and date, then applies the right rate without anyone remembering to override it.

Trying to run all three by hand, on a spreadsheet, for a workforce spread across states is precisely where errors creep in. It relies on someone knowing that a given date is a show day in one state but not another, remembering it every pay run, and applying it only to the affected workers. That is not a sustainable control.

How does CareIQ apply the right public holiday automatically?

CareIQ was built for providers that operate across more than one state, so public holidays are resolved per site rather than per company. When a shift is costed, the platform does not ask "is today a public holiday for this business?" It asks "is this day a gazetted public holiday in the state where this particular shift is being worked?"

The mechanism works like this:

• Public holidays resolve to the client site. CareIQ uses the state of the client or site where the shift is delivered. If a site state is not set, it falls back to the company's registered state, so there is always a defensible answer. This mirrors the way CareIQ already handles multi-site rostering and per-site local time, so a provider operating in, for example, Perth and Sydney gets the right treatment for each location.
• A complete Australian calendar out to 2030. CareIQ holds the full public holiday calendar for every state and territory well into the future, so future rosters are costed correctly and managers can see public holiday penalties before a shift is even worked.
• Yearly validation. The calendar is validated each year against official state and territory sources, so newly gazetted dates, moved substitute days and part-day holidays are captured rather than assumed from last year's list.
• Automatic penalty application. When the shift is costed for the timesheet, the engine applies the correct public holiday penalty based on the shift's location and date. There is no manual override to remember and no separate calendar to maintain per state.

The result is that public holiday penalties stop being a thing someone has to catch. They become a property of the shift itself, derived from where the work happens, and calculated the same way every pay run.

What are the compliance risks of getting it wrong?

Public holiday errors are attractive to auditors and to the Fair Work Ombudsman precisely because they are systematic. If a provider has misconfigured its public holiday handling, the error repeats on every affected date for every affected worker, which turns a small per-shift discrepancy into a material liability over a year or more.

The risks fall into a few buckets:

• Award breach and back-pay. Missing a state public holiday means paying ordinary rates where the penalty was owed. Corrected retrospectively, this becomes back-pay plus interest across every affected shift, and it is exactly the pattern that underpayment investigations look for.
• Margin leakage and billing mismatches. Applying a public holiday penalty in a state where the day is ordinary inflates labour cost and can push the cost of a shift out of line with what can be billed, which matters when reconciling NDIS invoices against delivered supports.
• Audit and evidence burden. When public holiday treatment is manual, a provider cannot easily show why a given shift was paid the way it was. A per-site calendar with a clear source and yearly validation gives an auditor a defensible, consistent basis for every public holiday decision.
• Scaling fragility. A manual single-calendar approach that works in one state silently breaks the moment the provider takes on a client in a second. Growth becomes the trigger for non-compliance rather than a sign of a healthy business.

None of these risks require bad intent. They are the ordinary result of treating a per-state legal reality as if it were a national one. The fix is not more vigilance from the payroll team. It is a system that ties each shift to the right jurisdiction and applies the correct public holiday penalty on its own.

For providers that already understand how the SCHADS Award works, multi-state public holidays are the last mile. The rates are known and stable. What varies is whether the day counts as a public holiday where the shift was worked, and that is a question about location and calendar, not about pay rates. Get the location right and the correct rate follows automatically.