Plan-Managed NDIS Invoices: A Preparation Checklist

For a plan-managed participant, prepare the invoice for the plan manager, not for the NDIA claim pathway and not for a self-managed payment route. The practical checklist is to confirm the payer for each service date, identify the participant clearly, show the delivered support and quantity, and make sure every line can be matched to accurate support records before you send it. The official NDIS guide to getting paid distinguishes these payment pathways, so the first step is always routing the invoice to the correct payer.

If you need a document layout, an NDIS invoice template can help structure the invoice. It does not decide eligibility, claim type, item selection or compliance for you, so those checks still need to come from your own records and the current official rules.

Start by confirming the payer and service dates

Before you draft the invoice, confirm two basics from your records:

the participant was plan-managed for the support you delivered
the plan manager's invoicing details are current

That sounds obvious, but it helps prevent an avoidable error: preparing a correct-looking invoice for the wrong payment route. If management type is unclear, stop and confirm it before issuing anything.

Service dates matter just as much as payer details. The item, unit and pricing conditions you check must match the actual support date and circumstances. Do not rely on an old template or a previous invoice if the support date falls under different pricing material. Use the Current NDIS pricing arrangements for the real service date and the arrangement you actually agreed.

What a plan-managed invoice should show

The official NDIS record-keeping requirements say records should be complete and accurate, with key details such as participant name, NDIS number, date, quantity and support type. For invoice preparation, a practical set of fields to check is:

Field	What to include
Supplier details	Your business name
ABN	Your ABN, or the appropriate supplier-statement route if genuinely exempt
Invoice details	Invoice number and invoice date
Participant details	Full name, address and NDIS number from your records
Invoice recipient	Plan manager name and invoicing contact
Payment instructions	Your verified details for receiving payment
Service details	Service date, clear support description, quantity delivered
Billing details	Applicable item, claim type, unit amount, total amount, applicable GST status
Participant count	One participant only per invoice

This is a preparation checklist, not an exhaustive compliance guarantee. The point is to produce an invoice a plan manager can understand, match and process without guessing what was delivered or who it relates to.

Match the invoice to your delivered-support records

A plan-managed invoice works best when the invoice and your support records tell the same factual story. Claimed hours should match the hours actually delivered. Descriptions should reflect the real support, not a vague label copied from another job. If your service records use internal references, keep those references in your own workflow so you can answer questions later without overloading the invoice itself.

That matters because the invoice is only one part of the record set. Your operational records remain separate. The official guidance on record keeping is the benchmark for what those records need to contain, and a signed support log must still meet official requirements rather than being replaced by a worker note or a shortcut on the invoice.

If you provide repeated visits and want a system for keeping recurring invoices aligned with those records, see NDIS Invoices for Repeated Support Visits.

A fictional worked example using hours only

This example shows two delivered support visits. Confirm the applicable support item and agreed rate separately before calculating the amount due.

Assumptions:

currency is AUD
the participant is plan-managed
rates, item codes and claim type are looked up separately and are not shown here
all supports were actually delivered
all names and identifiers are fictional placeholders only

Field	Example entry
Supplier	Bright Path Support Pty Ltd
ABN	[ABN lookup or supplier statement if exempt]
Invoice to	Northside Plan Management
Participant	Jordan Lee
Participant address	[Participant address on file]
NDIS number	[NDIS number on file]
Invoice date	14 August 2026
Invoice number	BP-1048
Currency	AUD

Line items:

Service date	Description	Applicable item	Claim type	Quantity
05 August 2026	Community access support, delivered	[Support item lookup]	[Claim type lookup]	2.0 h
12 August 2026	Community access support, delivered	[Support item lookup]	[Claim type lookup]	1.5 h

Hours check:

2.0 h + 1.5 h = 3.5 h total delivered

Amount structure:

Unit price: [Current agreed rate lookup for service date and circumstances]
Line total 1: 2.0 h × [rate lookup]
Line total 2: 1.5 h × [rate lookup]
Invoice total before any applicable GST treatment: 3.5 h × [rate lookup if same item and same rate]
GST: [applicable GST status lookup]
Total payable: [calculate from looked-up item, unit and GST treatment]

Why this structure works:

the invoice goes to the plan manager for processing
the participant is clearly identified
there is only one participant on the invoice
delivered hours can be traced back to service records
item, unit and price are left for current official lookup instead of being guessed

Do not send placeholder fields as if they were final entries. Replace each lookup field only after checking the applicable official material and your own records.

Two edge cases worth checking before you send

Management type changed mid-period

You may support the same participant twice in one month and find that the payment arrangement changed between service dates. Do not assume one invoice can cover both dates under one payer path. Check the management type that applied on each date of service. If one line belongs under a different arrangement, separate the billing and follow the correct route for each pathway under the NDIS guide to getting paid.

An old template uses the wrong pricing context

Saved invoice layouts are useful, but they can carry forward the wrong item or unit if you reuse them without checking the support date. The fix is not to rewrite the support description to fit the old item. Instead, confirm the item, unit and pricing conditions that apply to the support actually delivered on that actual date using the Current NDIS pricing arrangements. Do not switch items simply because another path looks easier to process.

Keep the wording factual and the workflow simple

Short, factual wording can make an invoice easier to review than overloaded descriptions. A useful pattern for a line description is:

"[Delivered support description], service date [DD Month YYYY], quantity [X.X hours], applicable item [lookup], claim type [lookup]."

A short email to the plan manager can be just as direct:

"Please find attached an invoice for delivered supports for [Participant Name], NDIS number [on file], for the service dates listed on the invoice. Supporting service records are maintained separately and can be referenced as [record references on file] if needed."

That keeps the invoice readable while preserving your own separate recordkeeping workflow.

If a recipient later asks for a factual correction, document the change clearly and avoid duplicate submissions. The related guide on Correct an NDIS Invoice After a Payment Query covers that workflow.

Use software as a drafting tool, not as a compliance decision-maker

Software can reduce repetitive entry and make invoices easier to review. InvoiceSonic supports creating an invoice with business and client details, line items, tax and currency settings, payment instructions, PDF output, saved client details and tracked invoice status. On supported plans, it can also prepare recurring invoices on supported schedules for your review and sending. You can see the current plan options on the pricing page.

What that does not mean is automatic claim submission, automatic payment collection or compliance certification. For plan-managed NDIS billing, you still need to verify the payer pathway, check item and pricing details, maintain your own support records and compare any part-payment or full payment against actual payment records.

If you want a starting point for the invoice structure itself, use the NDIS invoice template and then review the finished document against your records before sending.

Final pre-send review

Before issuing the PDF, check that:

the invoice is addressed to the correct plan manager
the participant details are complete
only one participant appears on the invoice
each service date and quantity matches delivered-support records
the applicable item, claim type, unit and GST treatment have been verified
all placeholders and lookup notes have been replaced with final information
payment instructions are visible and accurate

Then keep the issued copy with its invoice number and your related record references. Record when and where you sent it. A delivery or send confirmation can show the invoice was transmitted to the destination address or system; it is not a payment confirmation. Check actual remittance or account records before treating the invoice as settled.

That is the core preparation checklist for a plan-managed NDIS invoice: route it to the right payer, identify one participant clearly, match every line to delivered support, and verify current item and pricing details before you send.