Required Invoice Fields
Every NDIS claim invoice needs to carry the same core information, whether it's submitted directly to the NDIA or through a plan manager. Missing or mismatched fields are the single most common reason a claim doesn't process on the first attempt.
| Field | What it needs to show |
|---|---|
| Provider details | Registered NDIS business name and ABN |
| Participant details | Full name and NDIS number, plus address for SDA invoices |
| Support item number | The exact line item from the current NDIS Support Catalogue, not a general description |
| Quantity and price | Units or hours claimed, at the agreed unit price, within the NDIS price limit for that item |
| Date of service | The actual date, or dates, the support was delivered |
| Claim type | Flagged where relevant: non-face-to-face support, provider travel, short notice cancellation, or an NDIS requested report |
| Total and GST | Total invoice amount, with the GST component shown separately if the support is taxable |
| Plan manager ABN | Included where a third-party plan manager is paying the claim rather than the NDIA directly |
One invoice can only relate to one participant. It can include multiple support items or multiple dates of service for that same participant, but batching several participants onto one invoice for convenience produces a document that can't be processed as submitted.
Want your invoicing checked against this list before it becomes a problem?
Book a free call and we will review how your current claims are structured against what the NDIA actually requires.
Book a 15-Min CallSupporting Documentation to Keep
The invoice itself is only half of what a claim needs. Behind every invoice, a provider should be able to produce the documentation that proves the support was actually delivered as claimed:
- The service agreement, showing the support type, quantity and agreed cost that the invoice is claiming against
- Approved quotes, where the support type requires one
- Rosters or timesheets showing who delivered the support and when, particularly for SIL and other rostered supports
- Session notes, case notes or progress reports for capacity building supports
- Signed logs from the participant, guardian or carer confirming the support was received
Different support types need different evidence. Core supports generally need start and end times recorded against the shift. SIL specifically needs rosters and timesheets that match the claimed hours. Capacity building supports need case notes showing progress against the plan goal the support relates to. Records should be stored securely, with a backup, since these are exactly what gets requested if a claim is ever reviewed.
Why Claims Get Rejected or Delayed
The most common causes of a rejected or delayed NDIS claim are a claimed line item that doesn't match what's authorised in the participant's plan, a service date that falls outside the plan's active period, a price that exceeds the current NDIS price limit for that support item, or a claim type that's flagged incorrectly for how the support was actually delivered. Each of these stops the claim before payment, and it then has to be corrected and resubmitted, which pushes the payment date out further than a simple invoicing error should.
We've covered PRODA access issues and the shift to the NDIA's PACE system separately in our bookkeeping and NDIS claims service page, since access problems are a second, completely separate reason claims stall that has nothing to do with whether the invoice itself was correct.
Claims getting knocked back more than they should?
We match every claim against the participant's plan before it's lodged, catching mismatches before they turn into a rejection.
Book a 15-Min CallThe Provider Payment Assurance Program
The NDIA doesn't just check claims at the point of lodgement. Under the Provider Payment Assurance Program, the NDIA can review a sample of claims that have already been paid and request the supporting documentation behind them, the service agreement, rosters, session notes or signed logs, depending on the support type. A provider needs to be able to substantiate a claim well after the fact, not only when it was first submitted. If a reviewed claim can't be substantiated, the NDIA can require repayment, even though the money has already landed in the provider's account.
This is the practical reason invoice accuracy and document retention matter as much as delivering the support itself. A support that was genuinely provided but poorly documented is treated the same as one that can't be proven, when it comes to a payment assurance review.
Getting Paid Without a Cash Flow Gap
NDIS claims generally need to be lodged within a set window, commonly around 30 days of the service being delivered, and a provider paying support workers weekly or fortnightly through SCHADS Award payroll can end up funding wages before the matching NDIA payment arrives if invoicing falls behind the roster. We've covered this claim window, and the PRODA and PACE access issues that commonly sit behind it, in more detail in our NDIS bookkeeping and claims page. Reconciling invoices against the roster promptly, rather than batching them at month end, is what keeps the payroll side and the claims side from drifting apart.
NDIS claims and payroll, handled by one Australian based team
We process NDIS claims alongside SCHADS Award payroll, so the roster, the invoice and the pay run all line up, not three separate processes run by three separate people.
Book a 15-Min Call