NDIS payroll export to Xero Payroll AU: what providers should check before the pay run

The cleanest payroll export starts from approved support work, not every shift that was ever planned on the calendar. Roster changes, cancellations, late clock-outs, missing notes, travel, sleepovers, and allowances all need a review state before payroll data is handed off.

Xero's Payroll AU timesheets endpoint is the official resource to understand the timesheet object in Xero's API model. A provider workflow still needs to decide which Effica records are ready to become payroll input and which ones need manager review first. Source: Xero Payroll AU timesheets.

The companion Effica article on NDIS rostering software, timesheets, payroll, and claim readiness covers the same operating chain from shift evidence through finance review.

NDIS providers operating under SCHADS patterns often need payroll review around ordinary hours, broken shifts, sleepovers, overtime, allowances, and roster changes. Software should surface the records that need attention before export, while the provider remains responsible for payroll interpretation and advice.

Fair Work's SCHADS guidance explains hours-of-work concepts under the award, and the award itself remains the official legal source. Use those official sources for payroll rules; use operating software to keep the roster facts visible for the right reviewer. Sources: Fair Work SCHADS hours guidance and SCHADS Award MA000100.

That is why the pre-pay-run queue should show the shift type, span, worker, participant or house context, exception owner, approval state, and export target. The goal is not to hide payroll complexity; it is to make the right review visible before the pay run is finalised.

A common operating mistake is treating payroll export and NDIS claiming as if they are the same workflow. They share source evidence, but they answer different questions: what a worker should be paid, and what support can be invoiced or claimed for a participant.

The NDIS guide to getting paid is the official source for payment request context and rejected-claim review. A payroll export should never be used as a shortcut around claim-readiness checks such as support item, service date, quantity, participant funding context, approval, and evidence trail. Source: NDIS guide to getting paid.

Effica's NDIS billing software page and the article on NDIS billing software and Xero reconciliation cover the finance-side lane that should remain separate from payroll export.

Before connecting a payroll export, provider teams should decide who owns roster approval, which records are excluded, how earnings or allowance mappings are reviewed, when exceptions block export, and what evidence remains in Effica after payroll is handed off.

Xero's pay runs and earnings rates documentation are useful reference points for the downstream payroll objects a provider may need to align with. Sources: Xero Payroll AU pay runs and Xero Payroll AU earnings rates.

Effica should support this as workflow infrastructure: approved work in, exception review before export, payroll-ready output out, and an audit trail left behind. The software should support the operator; it should not claim to be payroll, industrial-relations, or NDIS claiming advice.