NDIS SIL Invoicing: 0138, Audits, and Software Choices

Will, EnableUs Community

If your, um, if your supported independent living claim bounced back rejected on July first twenty twenty six, it probably came down to five digits. Providers who were still using manual Xero templates with the old zero one one five code found out real fast that plan managers were straight up rejecting those claims.

Winter, EnableUs Community

Yeah, because from July first, the NDIA switched Supported Independent Living claiming over to code zero one three eight. Specifically, uh, support item zero one eight two one zero one three eight one one for weekly SIL. And if your invoicing system didn't catch that update automatically, you were left manually updating every single line item across your entire participant roster.

Will, EnableUs Community

It was a total mess for teams doing manual entry. And it highlights why understanding how your software handles different payment streams is so critical. I mean, you have got self managed participants where you invoice them directly, plan managed where you send invoices to a plan manager, and NDIA managed where you make payment requests straight through the portal.

Winter, EnableUs Community

And the rules around those streams keep tightening. Like, according to NDIS guidance, by October first twenty twenty six, plan managers are actually required to reject invoices from unregistered SIL providers who have not even applied for registration. So if your invoicing tool does not capture your registration status or application number, that money just gets stuck.

Will, EnableUs Community

Right. And it is not just getting paid today, it is keeping the money tomorrow. Under the NDIA payment assurance program, they can review your claims months or years later. If you get audited, you have to answer one simple question almost instantly: what evidence supports this invoice?

Winter, EnableUs Community

Exactly. The NDIA rules state you need complete, accurate records showing the participant name, NDIS number, exact dates of service delivery, the quantity or hours, and the support type. If you cannot trace an invoice line item directly back to a rostered shift and verified shift notes, you could face funding clawbacks.

Will, EnableUs Community

I, uh, I know you have spent time watching provider admin teams deal with this firsthand, haven't you?

Winter, EnableUs Community

Oh, absolute nightmare. I watched an admin manager spend nearly three hours re entering support logs into general accounting software just to generate invoices after a pricing catalogue change. Staff were literally copying dates and hours from a shift note log in one window and typing them into invoice boxes in another window. That is where human error creeps in, and that is where claims get knocked back.

Will, EnableUs Community

Duplicate data entry is just asking for a payment query or a compliance flag.

Winter, EnableUs Community

So that brings up the big question every provider faces. Do you go all in on a specialised, NDIS specific management platform, or do you stick with general accounting software like Xero or MYOB?

Will, EnableUs Community

Well, it really depends on your size and operational setup. A dedicated NDIS platform ties your participant records, service agreements, rosters, shift notes, and invoicing workflows into a single ecosystem. A support worker finishes a shift, logs the notes, and those hours flow straight through to invoicing without anyone re typing a single number.

Winter, EnableUs Community

Which is fantastic for data accuracy. But what if you are a smaller provider who already relies on general accounting software for payroll, bank reconciliation, and business activity statements?

Will, EnableUs Community

Then you look at a hybrid approach. You use specialised software to manage participant delivery and shift logs, and integrate it directly with your general accounting software to handle the broader financial side. But you have to be really careful with how those systems talk to each other.

Winter, EnableUs Community

Yes! Especially around privacy. You want your rostering system to pass verified shift hours over to your invoicing ledger automatically, but you do not want sensitive clinical notes or personal case notes flowing into your general accounting tool where general finance staff or external bookkeepers can see them. Role based permissions are non negotiable there.

Will, EnableUs Community

That is such an important point. Software integration should streamline your invoicing without creating privacy risks for participants. And beyond compliance, your software choices directly impact cash flow.

Winter, EnableUs Community

How so?

Will, EnableUs Community

Well, good software gives you actual visibility into your aged receivables by funding type. If your plan managed invoices are taking forty five days to pay, but your self managed ones take seven, you need reports that flag that instantly so your team can follow up before cash flow gets squeezed.

Winter, EnableUs Community

Mm, totally. And when the NDIS drops a new pricing update, like the twenty twenty six to twenty twenty seven Support Catalogue, you need to know how easily your software updates maximum price caps and item descriptions. If you have to manually edit fifty different custom items in your system every July, your software is working against you.

Will, EnableUs Community

Before buying anything, test standard everyday tasks. Get a demo. Try creating an invoice, fixing a shift discrepancy, and pulling up the exact support notes attached to a claim. Don't fall for a fancy feature list if the day to day workflow is clunky.

Winter, EnableUs Community

At the end of the day, software cannot fix broken internal processes or make a non compliant claim valid. But the right system gives your team confidence that every service is logged, every invoice is audit ready, and your cash flow stays healthy.

Will, EnableUs Community

Spot on. Good chatting, Winter.

Winter, EnableUs Community

Talk soon.