Why NDIS invoices get rejected, and how to stop it
By Mick Lutton · Updated 2026-07-07
Most rejected NDIS invoices fail for one of ten reasons, and they split into two groups: errors on the invoice itself (wrong or stale line item, rate over the cap, missing required fields, duplicate invoice number, maths that does not add up) and problems no invoice can fix (exhausted budget, service agreement mismatch, plan ended or changed). Fix the first group with better tooling; the second group needs a conversation before the shift, not after the invoice.
Errors on the invoice - preventable every time
1. Wrong or outdated line item code
The catalogue changes at least yearly, and codes that look right can be retired or replaced. The 2026-27 release rebuilt respite claiming entirely, so any template with last year's STA codes now produces rejectable invoices. Codes also differ between near-identical supports: 04_104 with the 0125 group is weekday community access, while 04_104 with the 0136 group is Saturday group support.
2. Rate above the current price limit
Plan managers must not pay above the PAPL cap. If your agreed rate was set at last year's cap and the invoice shows it against this year's code list incorrectly, or you charge weekday rates for a Sunday shift under a weekday code, it bounces. Current caps are on every line item page, version 2026-27 v1.0.
3. Missing required fields
No ABN, no participant NDIS number, no support dates, no unique invoice number: any one of these is enough for software on the plan manager's side to auto-reject. The full list is in NDIS invoice requirements.
4. Duplicate invoice number
A documented top-three rejection cause, and almost always self-inflicted: reissuing a corrected invoice under the same number, or two numbering sequences colliding after a spreadsheet copy. A corrected invoice needs a new number, with the original cancelled cleanly.
5. Quantity and total that disagree
Three hours at $73.58 is $220.74. Rounding per line differently to the invoice total, or fixing a rate without re-multiplying, produces the mismatch plan manager software flags first.
Problems beyond the invoice - not preventable by any tool
6. Participant budget exhausted
If the relevant budget category is empty, a perfect invoice still cannot be paid from it. You will not see the budget; only the participant, their nominee or plan manager can. For ongoing supports, agree on a heads-up arrangement when funds run low.
7. Service agreement mismatch
Claims outside what the agreement covers (different support type, more hours, different rates) get queried or refused. When the work changes, change the agreement first.
8. Plan ended, changed or in review
Supports delivered after a plan ends fall into a gap. Confirm plan dates for regular clients, especially around review time.
9. Wrong billing target
Invoicing the participant when the plan is plan-managed, or the wrong plan manager after a switch. Confirm who pays at the start, and again whenever a plan changes.
10. Supports that need a quote or prior approval
Some items are quotable rather than price-limited, and some supports need agreement before delivery. If approval was never given, the invoice is where that surfaces.
The honest summary
Causes 1 to 5 are mechanical and disappear with a current catalogue, cap checks, required-field checks and safe numbering. Causes 6 to 10 are relationship and paperwork problems; nothing that generates an invoice can fix them, so treat any tool promising "guaranteed payment" with suspicion.
Crestyn kills causes 1 to 5
Current 2026-27 v1.0 line items built in, caps flagged before you send, required fields always present, numbering that cannot duplicate, and an amend flow that voids the original properly. $14 a month, 30 days free, no card.
Quick answers
- Why did the plan manager reject my NDIS invoice?
- The usual causes: a wrong or outdated line item code, a rate above the current price limit, missing required fields (NDIS number, ABN, support dates), a duplicate invoice number, or the participant’s budget or service agreement not covering the claim.
- How long do plan managers take to pay?
- Commonly 2 to 10 business days once the invoice passes their checks. A rejected invoice restarts the clock, which is why prevention beats chasing.
- Can an app guarantee my invoice gets paid?
- No, and be wary of anything that claims it. An app can eliminate code, cap, field and numbering errors, but it cannot see the participant’s remaining budget or their service agreement.