Agency, plan-managed or self-managed: how the invoice actually differs

This is for coordinators and finance staff working out why one participant’s invoice looks nothing like another’s. It covers what actually has to appear on the face of each invoice type, what evidence sits behind it, and the one thing about mixed funding that trips almost everyone up eventually.

NDIS funding has three management types, and each one sends the money — and the paperwork — somewhere different.

• Agency-managed: the NDIA pays the provider directly. There is no invoice to the participant at all; instead the provider submits a payment request against the participant’s plan.
• Plan-managed: a plan manager, engaged by the participant, pays the provider on the participant’s behalf. The provider issues a genuine tax invoice to the plan manager.
• Self-managed: the participant pays the provider themselves, then claims the cost back from the NDIA (or pays and keeps records for their own plan review). The invoice goes to the participant, not to anyone else.

Same support, same worker, same shift — completely different destination for the bill. That is the whole source of confusion, and it is worth being precise about it because getting the wrong document to the wrong destination is the single most common reason money gets stuck.

This is the lane that catches people out because there is no invoice in the ordinary sense. What goes to the NDIA is a bulk payment request, referencing the participant, the support item, the date of service and the claimed amount, batched with every other agency-managed claim for the period. There is no participant-facing document because the participant is not the payer.

We have covered the mechanics of building and submitting that file, and what to do when lines come back rejected, in separate guides — see NDIS claiming without the spreadsheet gymnastics and why NDIA bulk payment requests get rejected. Worth knowing here is just this: the request goes to the provider’s own claiming channel, and it goes into the provider portal by hand. It is not automatic and it is not a direct feed into NDIA systems — someone still has to generate the file and lodge it.

What comes back afterwards matters as much as what went in. The NDIA’s outcome file tells you, line by line, whether each claim was paid in full, part-paid, or rejected — and if rejected, why, in the NDIA’s own words. Reading that file properly (rather than just checking the bank balance) is what lets you release only the rejected lines back into a fresh claim instead of re-submitting the whole batch, or worse, not noticing a rejection at all until someone asks where their money is.

Here the invoice looks like invoices anywhere else, because it is a genuine commercial document going to a plan management business’s accounts team. It needs:

• The provider’s ABN and registration details
• The participant’s full name and NDIS number
• The support item and its NDIS support-item number, matched to the current price-guide rate for that band
• Date(s) of service
• The quantity or duration (hours, sessions, kilometres for travel)
• GST treatment (most NDIS supports are GST-free, but check the item)
• A payment term — plan managers typically pay on an agreed cycle, not on receipt

The evidence behind the invoice is what makes it defensible if it is ever queried: session notes or attendance records showing the support was actually delivered, matching the item claimed, at a rate that does not exceed the participant’s plan budget or the price-guide cap for that support. A tax invoice with the right numbers on it but no service record behind it is a liability, not an asset.

Plan managers also expect a clean paper trail on their end: an invoice inbox, a provider list, the claims sent to the NDIA on the participant’s behalf, and a statement showing running budget position. If you are dealing with plan managers regularly, standardising your invoice format so it drops straight into their process — rather than needing manual re-keying — saves both sides real time.

Self-managed invoices go to the participant (or their nominee) directly, and they need to read like an invoice to any ordinary customer, because that is what the participant is in this transaction. Same core details — ABN, support item, date, quantity, rate — but the audience is different: this document may sit in the participant’s own records for their plan review, or get uploaded by them into their own claiming portal. Clarity matters more here, not less, because there is no plan manager checking the arithmetic before payment goes out.

Self-managed participants also often want visibility before an invoice becomes final — the ability to see what is coming, and approve or query it, rather than have it arrive as a surprise deduction from their plan. Giving them that visibility is not just good service; it heads off disputes before they start.

The thing that catches even experienced finance staff: management type is set per support category, not per participant. A participant can be plan-managed for core supports and self-managed for capacity building, or agency-managed for one category and plan-managed for another, all inside the same plan, at the same time. There is no rule that says a participant is “a plan-managed client” full stop — they are plan-managed for that line item.

This means a single roster week for one participant can generate three different documents heading to three different places: a bulk payment request line for one shift, a tax invoice to a plan manager for another, and a direct invoice to the participant for a third. The support delivered might look identical from the roster’s point of view. The billing treatment is not. Getting this wrong — sending a plan-managed invoice to the participant, or trying to bulk-claim a support category the participant self-manages — is one of the more common causes of claims sitting unpaid, not because the support was not delivered, but because the paperwork went to the wrong address.

Whichever lane the money travels through, the underlying evidence expectation is the same: a record that the support was actually delivered, on the date claimed, at the rate claimed, within the participant’s approved budget for that category. That is a shift record, a progress note, a signed attendance — something that would satisfy an auditor asking “how do you know this happened.” The invoice is just the front of the transaction; the service record is what backs it up if anyone ever asks. If that trail is the weak point in your service, what an NDIS auditor asks for covers where each piece of it should already be sitting.

Corella tracks each participant’s budget by category, generates the right invoice for the right lane — tax invoice to a plan manager, direct invoice to a participant, or a line in the NDIA bulk payment file for agency-managed supports — and reads back the NDIA’s outcome file so rejected lines can be identified and re-claimed rather than lost. It does not submit directly to the NDIA; that step still goes into the provider portal by hand. For the mechanics of building that bulk file and handling rejections, see the separate guides linked above.