5 SCHADS Payroll Mistakes That Cost NDIS Providers (and Their Staff)

Published 8 June 2026 · 7 min read · Payroll & Compliance

Ask any NDIS provider what keeps them up at night and "getting the pay right" is near the top of the list. The SCHADS Award — the Social, Community, Home Care and Disability Services Industry Award (MA000100) — is one of the most complex modern awards in the country. A single Sunday sleepover that tips a worker over 38 hours can attract several different pay rules at once. Get it wrong one way and you underpay your staff; get it wrong the other and you quietly bleed margin on every shift.

Here is the uncomfortable part: many rostering and timesheet tools do not interpret SCHADS on their own. They either store the rates you manually type in, or rely on a separate payroll add-on to do the award interpretation. Either way, the award logic lives outside your roster — and that gap is where these five mistakes come from.

Mistake 1: Assuming "we export to payroll" means "SCHADS-compliant"

Plenty of rostering apps let you export hours to a payroll system. That sounds like a solution, but exporting raw hours just moves the problem downstream. Someone — your bookkeeper, your accountant, or a payroll officer — still has to apply the correct penalty rates, overtime and allowances. The award interpretation has to happen somewhere. If your roster does not do it — and does not connect to something that does — a human is doing it manually, every pay run, under time pressure.

Mistake 2: Configuring rates by hand, per employee, per time band

Some systems make you build a "pay group" or rate table for every employee and every time band, then maintain it forever as the award changes. This is the single biggest source of quiet errors. Every manual rate is a chance to fat-finger a number, miss an annual award increase, or apply the wrong stream. The work of staying compliant never ends — it just sits on whoever set up the rates.

A genuine SCHADS engine works the other way around: you tell it the shift (day, time, length, employee classification) and it applies the award's rules automatically. There is no rate table for you to maintain because the award logic is built in.

Mistake 3: Missing the weekly overtime split

Under SCHADS, work beyond 38 hours in a week is overtime — and it is not a single rate. The first two hours are paid at 1.5x and everything after that at 2x (that split applies in the disability and home-care stream; in the Social and Community stream it is the first three hours). If your system simply pays "ordinary rate" for all hours worked, you are underpaying overtime. If a worker picks up extra shifts across multiple participants, the overtime has to be tracked across the whole week, not shift by shift. Manual tracking almost always misses this.

Mistake 4: Forgetting sleepovers, broken shifts and allowances

SCHADS is full of components that are easy to overlook because they do not look like "normal" hours:

• Sleepover allowance plus the correct treatment of any hours worked during the sleepover
• Broken shift allowance when a worker's day is split into separate periods
• First aid allowance for staff who hold and are required to use the qualification
• Travel time and kilometre reimbursement between participants
• Casual loading of 25% on top of the base rate, stacked correctly with penalties

Each of these is a line item that is easy to forget when pay is assembled by hand — and every forgotten allowance is an underpayment waiting to be discovered at audit.

Mistake 5: Ignoring mandatory meal breaks

Long shifts trigger meal-break entitlements. Two things go wrong here. First, an unpaid meal break that is not deducted means you are paying for time that should not be paid. Second — and more serious — if a worker does not get their required break, that can attract a penalty payment. A system that does not track breaks cannot get either right, so providers end up exposed on both sides.

Why this matters more than ever

Getting SCHADS wrong is no longer just an awkward conversation. From 1 January 2025, intentional underpayment of wages can be a criminal offence in Australia under the Closing Loopholes reforms. Even unintentional errors expose you to Fair Work back-pay claims that can stretch back years. And every dollar of penalty or allowance you miss in the other direction is margin gone on a sector where margins are already thin.

The providers who sleep well are not the ones with the best spreadsheet. They are the ones whose system applies the award for them, the same way, every single pay run.

The bottom line

"Does it do payroll?" is the wrong question. The right question is: does it interpret the award, or does it just store the numbers I gave it? SCHADS is too complex and too high-stakes to run on manual rate tables and good intentions. The cost of getting it wrong now runs both ways — underpayment risk on one side, lost margin on the other — and the only reliable fix is software that knows the award so your team does not have to.