SCHADS broken shifts and travel: NDIS rostering checks before payroll export

Fair Work's SCHADS pay and allowances guidance says vehicle allowance can apply when an authorised employee uses their own vehicle for work, including travel between work locations while on active duty. It also explains that travel between clients may be paid time and does not break a shift. Source: Fair Work pay and allowances in SCHADS.

The buyer question is whether the roster and mobile workflow can keep the travel segment visible: origin and destination context, duty status, worker vehicle evidence, kilometres if recorded, participant support context, and the manager decision that made the timesheet exportable.

That evidence should also stay close to the support-worker mobile app workflow so late notes, field evidence, and handover context do not become a separate spreadsheet correction.

Fair Work's SCHADS hours guidance says broken-shift allowance depends on whether the employee works a broken shift with one or two unpaid periods, and points providers to the current SCHADS pay guide for allowance amounts. Source: Fair Work hours of work in SCHADS.

The SCHADS Award itself remains the legal source. It sets the detailed broken-shift clause, allowance clause, span rule, shift-allowance treatment, and break-between-shifts requirement. Source: SCHADS Award MA000100.

Effica should support the review workflow rather than claim to interpret the award for the provider. Good software keeps the roster facts, timesheet facts, configured pay category, exception reason, reviewer, and export boundary visible for the right payroll reviewer.

The NDIS support catalogue explains which supports providers can use when requesting payment, maximum-price context, and claim-type information including travel. Source: NDIS support catalogue.

The NDIS guide to getting paid says payment claims need details such as participant, support dates, support item reference number, and support item price. Source: NDIS guide to getting paid.

That is why the payroll lane and the claiming lane should stay linked but distinct. Payroll review asks whether the worker record, time, travel, allowance, overtime, and export mapping are ready. NDIS claim readiness asks whether delivered support evidence, support item context, funding route, approval state, and claim-type context are ready.

Before choosing software, ask whether broken-shift warnings explain the source facts: work periods, unpaid breaks, span, minimum-payment period, rest-between-shifts risk, travel segment, worker agreement context, public-holiday or overtime context, reviewer, and export outcome.

Also ask how the system handles corrections. A payroll-ready queue should show whether an exception is unresolved, approved, corrected, exported, rejected by the downstream payroll process, or held for manager review. Without that state, the team may still need spreadsheets to explain what happened.

NDIS provider portal guidance says bulk payment requests can be submitted through the provider portal and that providers should use the official self-help guide for submissions and rejection troubleshooting. Source: NDIS provider portal guidance. That claiming workflow is adjacent to payroll, not a substitute for payroll review.

Effica is being built to keep roster exceptions, mobile evidence, timesheet approval, payroll export readiness, and claim-readiness context in the same operating trail. That helps managers review the right facts before money moves.

It should not replace Fair Work, the SCHADS Award, NDIS pricing documents, payroll advice, accounting advice, legal advice, or provider judgement. The official sources remain the rules source. Effica supports the workflow around those checks.

For teams still stitching this together with roster exports, payroll spreadsheets, separate kilometre notes, and month-end claim review, the practical next step is a workflow walkthrough that follows one exception from roster to payroll and finance.