NDIS Code Confusion: Sequence Numbers, Suffixes, and Billing Risk
This episode breaks down the hidden structure behind NDIS support codes, why sequence numbers can trip up claims, and how shifting category rules create billing and audit risks. It also covers the new 2026–27 therapy suffixes, travel caps, remote loadings, and the move from manual spreadsheets to automated billing systems.
Chapter 1
Code Anatomy and the Sequence Number Trap
Will, EnableUs Community
So, I was looking at this, this absolute monster of a code string the other day. It was, uh, let me find it, yeah, zero one, underscore, zero one one, underscore, zero one zero seven, underscore, one, underscore, one. It looks like some kind of, I don't know, encrypted password, right? But it is actually the NDIS code for standard weekday self care assistance.
Winter, EnableUs Community
Oh, the classic zero one, underscore, zero one one. It, it looks like a total mess, but there is actually a method to the madness. It is a five part mechanical structure. That first zero one is the support category, which is Assistance with Daily Life. And then you have that zero one one, which is the sequence number. Then zero one zero seven, that is the registration group. And those last two ones at the end? Those are the outcome domain and the support purpose.
Will - BackUp Voice
Right, but, but here is the thing. That sequence number, the zero one one? It is a total trap. Providers look at that and think, oh, okay, there is a logical pattern here. If zero one one is weekday self care, then zero one two must be something related, right? No. The NDIA allocates those three digit sequence numbers so inconsistently across the catalog. If you try to guess a code or swap numbers from memory, you are going to get hit with a rejected claim. It is a massive billing risk.
Winter, EnableUs Community
Yes. It is. And it gets even worse because of how the categories have shifted. We went from the original fifteen categories, then PACE expanded it to twenty one, and now for twenty twenty six to twenty seven we are sitting at nineteen categories. This PACE fragmentation means something like social and community participation is split across multiple, overlapping categories depending on exactly how you deliver the service. You cannot just rely on what worked in your head last year.
Will, EnableUs Community
Oh, tell me about it. I, I remember the days when everyone had their favorite codes written on post it notes or in a messy spreadsheet. But a code that was completely active and valid in twenty twenty five to twenty six can just silently become a legacy item or get deactivated entirely for twenty twenty six to twenty seven. If you claim a deactivated code, it is not just a rejection, it can actually flag your organization for an audit.
Chapter 2
Scaling Suffixes: Operational Math and Tech Fixes
Winter, EnableUs Community
Exactly, and the biggest shake up for twenty twenty six to twenty seven is what they are calling therapy unbundling. They have introduced these five specific suffixes: underscore C A for cancellations, underscore N F for non face to face work, underscore P T for provider travel, underscore R R for reports requested by the NDIA, and underscore T H for telehealth.
Will - BackUp Voice
Wait, so instead of just ticking a box in the portal to say, hey, this was travel, it is now an entirely separate line item code? Like, a distinct code with underscore P T at the end?
Winter, EnableUs Community
Yes, exactly. It is a standalone line item. And the math on this is super specific. Take provider travel, underscore P T. It is capped at exactly fifty per cent of the standard hourly service rate. So, for a dietitian, where the standard rate is around one hundred and seventy nine dollars, the travel rate works out to exactly eighty nine dollars and fifty cents per hour. Or for exercise physiology, fifty per cent of the rate is exactly eighty one dollars per hour.
Will, EnableUs Community
Wow, so if your system is still trying to use the old claim modifiers, or if your service agreements do not clearly itemize these separate components, your billing is going to break. But, I mean, how are busy providers actually supposed to keep track of all this? The official NDIA support catalogue is just this giant, flat Excel spreadsheet that is painful to search.
Will - BackUp Voice
Well, a lot of smart operations managers are bypassing that raw Excel sheet entirely. They are using third party lookup tools. Things like Teiro's searchable catalogue, Carevo's line items guide, or MyCareSpace. It lets them look up active codes and pricing limits without getting lost in rows of data.
Winter, EnableUs Community
Those lookup tools are great for a quick check, but honestly, as an organization scales, manual cheat sheets or search tools still fail. Think about geographic loadings. If you are in a remote area, you can charge a forty per cent loading. In a very remote area, it is a fifty per cent loading. If you have staff manually trying to calculate fifty per cent travel caps, plus fifty per cent very remote loadings, and then appending underscore P T to a twelve digit code, you are begging for human error.
Will, EnableUs Community
Right, so the, the gold standard is automated billing software. A system where the support worker just logs what they did, say, a face to face session plus thirty minutes of travel in a remote postcode, and the system automatically calculates the rates, applies the forty per cent remote loading, and outputs the correct base code and the underscore P T line item. No manual guessing.
Winter, EnableUs Community
That is the operational divide right there. On one side, you have providers struggling with manual sheets, constantly fixing rejected claims, and stressing about audits. On the other, you have providers who treat these codes as a precise language and build systems to automate them. That is how you stay compliant and financially sustainable in twenty twenty six to twenty seven.
Will - BackUp Voice
Definitely. Well, that is a wrap on this episode. Talk to you all next time.