Your SIL Transition Pathway Before the October Deadline
We break down the new Registration Group 0137 for NDIS digital platforms, including the dual-trigger test for matching participants with workers and processing NDIS funds. The episode also covers the shift to Certification-level audits, worker screening enforcement, and how the new real-time payment system changes compliance for platform operators.
Chapter 1
The July 1 Deadline and the New Platform Definition
Will, EnableUs Community
So, uh, we are literally four days away. July 1, 2026. If you are running an NDIS digital platform—like an app or a website connecting participants with support workers—and you aren't registered with the Commission yet, the clock hasn't just run out. The- the- the door is actively shutting.
Winter, EnableUs Community
Four days, Will. That is... I mean, talk about down to the wire. For years, these gig-economy style platforms have operated in this, well, unregulated grey space, right? Connecting people, processing payments with NDIS funds, totally unregistered. And now, bang. July 1, it is over.
Will, EnableUs Community
Yeah, the, uh, the Commission is calling it Registration Group 0137. It's a completely new category: Providing an NDIS Digital Platform Service. But- but here's the thing. Not every website that lists support workers is caught in this. There's a very specific, dual-trigger definition we need to look at.
Winter, EnableUs Community
Right, because if you're just a directory, like a classifieds site where people find a phone number and handle the rest themselves, you're not a platform under 0137, right?
Will, EnableUs Community
Exactly. To get caught, your system has to do two things. First, it acts as an intermediary, matching the participant with the worker. And second—this is the clincher—the payments for those services must flow through your platform using NDIS plan funds. If you do both? You're in. If you're just a directory with no payment processing? You're out. But if you touch the money and the matching, you're a platform.
Winter, EnableUs Community
So, the money flow is the trigger. If NDIS funds touch your digital pipe, you are a platform provider. And that means mandatory registration. But it's not just a quick tick-a-box form, is it? We are talking about a Certification-level audit.
Will, EnableUs Community
Oh, absolutely. It is- it's Certification. Which is massive. If you're used to the Verification pathway—which is basically a desktop audit of your paperwork—Certification is a whole different beast. It's a full two-stage audit. Stage one is the design audit, stage two is the live operational audit. And the kicker? If your business does a bunch of simple things that only required Verification before, the second you add Registration Group 0137, your entire business, the whole audit, gets bumped up to Certification.
Winter, EnableUs Community
Ouch. So one platform element drags your entire service model under the microscope. That's going to catch a lot of operators off guard who thought they could just slide this in under their existing low-risk registration.
Chapter 2
Operational Realities and the Real-Time Payment Shift
Will, EnableUs Community
It will. And the operational realities of passing that Certification audit are... well, they're incredibly tech-heavy. It's not just about standard NDIS practice standards. Auditors are going to look at your actual code, your cybersecurity, how you handle data privacy, and—critically—how your system handles the NDIS Worker Screening Check.
Winter, EnableUs Community
Wait, so the platform itself has to enforce the screening? It's not just a matter of the worker asserting they have it?
Will, EnableUs Community
No way. Your tech has to prevent a worker from even accepting a booking if their NDIS Worker Screening Check isn't verified and active in your system. If your app lets an unscreened worker book a shift, you fail the audit. Period. It has to be hard-coded into the workflow.
Winter, EnableUs Community
That is a massive shift from the old "post a profile and hope for the best" model. But, Will, there's another major system launching on the exact same day, July 1. This new real-time digital payment system. How does that intersect with 0137?
Will, EnableUs Community
It's a- it's a double whammy. On July 1, the NDIS is rolling out this real-time payment system to crack down on fraudulent billing. So, if your platform processes claims, your APIs, your payment gateways, they all have to hook into this new real-time system and provide much, much stronger evidence for every single claim. You can't just send bulk invoices anymore. The burden of proof is digital, instantaneous, and strict.
Winter, EnableUs Community
So, if your tech stack isn't ready to talk to the NDIS real-time system, and you're not on the path to Certification, you're essentially locked out of the market come July 1. No NDIS funds will flow through your app.
Will, EnableUs Community
Exactly. If you are unregistered and haven't engaged with the transitional pathways yet, you need to act like an unregistered SIL provider. Get onto the NDIS Commission's portal, lodge that application immediately, and get an approved quality auditor lined up. The Commission does have transitional arrangements, but they're only for those who are actively in the pipeline.
Winter, EnableUs Community
Yeah, because if you're not in the pipeline, you can't legalise your operations post-July 1. You're shut down. Well, that is a pretty stark wake-up call for the tech side of the sector. If you need help mapping this out, the team at EnableUs is ready to jump in. But for now, that's the state of play. Speak soon.
Will, EnableUs Community
See ya.