What NDIS plan managers actually need on an invoice

An invoice that comes back from a plan manager costs you about twenty minutes. Someone has to read the email, work out which of the fourteen invoices in that batch it refers to, find the missing field, fix it, re-issue, and then remember in three weeks to check it was actually paid. Do that four times a month and you have spent most of a day of admin salary on paperwork that should have gone out right the first time.

The frustrating part is that plan managers are not being difficult. A plan manager is holding someone else's money and has to be able to show the NDIA what they paid it out for. They cannot approve a claim they cannot match to a participant, a plan, a support item and a date. Give them those four things clearly and almost everything else is optional.

The four things that decide whether you get paid

In rough order of how often each one is the reason an invoice bounces:

1. The participant's NDIS number. Not just their name. Plan managers often hold two participants with the same surname, and a name alone means someone has to go looking.
2. The support item number. The line has to say which item in the NDIS Pricing Arrangements you are claiming against. A description like "Physiotherapy session" with no item number is a claim the plan manager cannot lodge.
3. The date of service. The date the visit happened, not the date you got round to invoicing. These are frequently weeks apart, and the plan manager checks the service date against the plan period.
4. Your ABN and the total. It is a tax invoice. The ATO wants the supplier's ABN legible on the document, and the plan manager's accounts system wants a total it can reconcile.

After that, in descending order of usefulness: the practitioner's name and AHPRA registration, the plan period, the plan manager's own reference if they have given you one, and the duration of the session. Add the participant's date of birth if you serve a facility where two participants really do share a name.

Who the invoice is addressed to is not who was treated

This is the single most common structural mistake, and it is worth being pedantic about. An NDIS plan has one of three management types: self-managed, plan-managed, or NDIA-managed. A plan-managed participant's invoice goes to the plan manager — a different organisation, with a different email address and a different accounts team — while the patient on the invoice is still the participant.

Software that only has one "bill to" field forces you to choose between addressing the invoice correctly and naming the person who was treated. AspireOS separates them: the funding card on a patient's file (/patients) records the plan management type and links the plan manager or support coordinator as a contact, and the invoice prints a "Patient details" block and an "Invoice to" block as two different things. If nobody other than the patient pays, the second block simply does not render — it is never filled with a placeholder.

Support item numbers belong on the service, not in your head

The same forty-five minutes of physiotherapy bills under a different item number depending on who is funding it — one number under a health fund, another under a Medicare chronic disease management plan, another as an NDIS support item. If the code lives in the admin's memory, then the admin going on leave is a billing incident.

In AspireOS each service you sell (Settings → Billing & finance → Services) carries a set of item codes keyed by funding type. When a visit on that service is invoiced, the code matching that patient's funding is stamped onto the line and prints in its own column on the document. There is a separate field for the short-notice cancellation item, because a cancellation claims under a different code and you do not want the operator picking that by hand at 8pm.

Treat the codes any system hands you on day one as examples, including ours — AspireOS pre-fills its starter services with common item numbers and offers them as suggestions in the editor, which is a convenience, not an assurance. Confirm the current item numbers for your discipline against the NDIS Pricing Arrangements and Price Limits before you rely on them. Those numbers change, your software does not automatically know that, and no vendor should let you believe otherwise.

Price limits and travel are where honest practices get burnt

NDIS supports have price limits. Bill above one and the plan manager will either short-pay you or send it back, and if it slips through, it can be clawed back later. Travel has its own limits again, and they are not the same limits — and travel is a bigger number in a mobile practice than most owners think, which is its own conversation.

The fee schedule in AspireOS (Settings → Billing & finance) holds a base fee, a per-kilometre rate and a provider-travel rate per hour for each funding stream, plus two optional caps: a maximum charge for the base line and a separate maximum for the travel line. Set them and the pricing engine clamps the invoice to them, so an unusually long session or a bad-traffic day cannot quietly produce a line above the ceiling. Leave them blank and no cap is applied — which is the right default for a private fee, and the wrong one for NDIS.

On GST: supports delivered to a participant under their plan are generally GST-free, and most physiotherapy line items will not carry GST. "Generally" is doing real work in that sentence — the treatment of some supports, and of things you on-sell like equipment, is not obvious. AspireOS carries a GST flag per line and a practice-level tax posture, so the document tells the truth either way; what it cannot do is be your accountant.

The monthly claim is a batch, not forty invoices

Most practices bill NDIS work in a run — one funding stream, one date range, sometimes one practitioner. Raising those one at a time from a list of completed appointments is where the misses happen, because you are relying on someone's eye to notice the visit that has no invoice against it.

The batch tool on /invoices takes a date range and filters by entry type, appointment status, whether the visit has a note or a case attached, location, patient name or tag, practitioner, and service. It previews what it will raise before it raises anything, and the preview and the raise run through the same matcher — so the count you check is the count you get. If a batch skips visits, it tells you how many and why rather than silently raising fewer.

Once raised, invoices can be pushed to a connected Xero organisation or exported as a Xero sales-invoice CSV from Settings, one row per line, so the bookkeeping side is not a re-key. The funding-aware billing tour walks through the rest of it.

A short checklist to run against your own invoices

• Participant number, plan period and plan management type on the document — not just on your patient file
• Support item number in its own column, per line
• Date of service distinct from date of issue
• Addressed to the plan manager, naming the participant as the patient
• Practitioner name and AHPRA registration
• Your ABN, the GST treatment, and a total that survives a copy-paste
• Bank details or PayID, so paying you is not a follow-up email
• Your invoice number, and their reference if they gave you one

None of this is clever. It is just the difference between an accounts team that pays you on the first pass and one that puts your invoice in the pile they will get to. The practices that get paid fastest are not the ones with the best follow-up process. They are the ones who never needed one.