SIL claim cutoff and SDA: A continuity checklist
On 1 October 2026, the NDIA's SIL claiming guidance moved from transition planning into a practical payment-control point: supported independent living providers can only claim SIL supports if they are registered or applied to register before 1 October 2026. For SDA providers, this does not change the SDA claim itself. It does, however, create an operating dependency wherever an SDA home relies on a SIL partner, plan manager invoice workflow, shared-home roster, move-in pathway, unplanned exit response or participant transition plan. The useful response is a continuity checklist that keeps the SDA record clean while making support-provider risk visible before it turns into a vacancy, safety issue or owner-reporting surprise.
Treat the cutoff as a continuity trigger
The NDIS says SIL providers who have applied can continue claiming under the new 0138 support group while their application is assessed, and that unregistered SIL providers who did not apply by 1 October 2026 can only claim for services up to 30 September 2026. Plan managers are also told to reject invoices from SIL providers who are not registered and have not applied to register.
That is a SIL payment rule, not a shortcut for SDA teams to make legal conclusions about another provider. The SDA task is narrower and practical: identify which dwellings, residents, vacancies and move-ins depend on a SIL provider whose claim pathway may have changed, then record the evidence source and escalation owner.
The risk is highest where a participant's move-in depends on a specific roster, a shared home needs housemate-compatible supports, an owner expects quick occupancy, or an existing resident may be affected by a support-provider transition.
Separate SDA claims from SIL payment risk
SDA and SIL remain different supports. The NDIS Commission's supported accommodation guidance explicitly says there are no changes to registration requirements for SDA providers, while SIL providers must register from 1 July 2026 and meet the SIL Practice Standards. Keeping that distinction visible protects the SDA claim record from unsupported assumptions.
A finance team should not hold or alter an SDA claim simply because a SIL invoice is under review. Instead, it should maintain separate states: SDA claim-ready, SDA blocked, SIL partner status unknown, SIL application evidence requested, plan-manager invoice rejected, participant transition risk, or support continuity review.
That separation helps leadership act quickly without blurring participant housing rights, support choice, provider registration obligations and owner reporting.
Build the 1 October checklist
Use this checklist for every SDA home where SIL is part of the operating model, especially before accepting a referral, confirming a move-in date, reporting a vacancy forecast, or responding to a SIL invoice or claim rejection.
Map the SIL dependency
Record whether the dwelling relies on shared SIL, individual SIL, irregular support, overnight response, housemate compatibility, a specific provider, or a participant-managed support model that is not SIL.
Verify the source, not the rumour
Ask the SIL provider for its registration status, 0138 scope or application number where relevant. Store the source date and avoid relying on marketing copy, referral chatter or an old service agreement.
Check plan-manager invoice requirements
For plan-managed SIL budgets, confirm whether the invoice includes the correct support item code and the provider's registration or application number. Keep that check separate from SDA invoicing and RRC records.
Protect participant choice
If a SIL provider cannot continue, open a participant transition task with the support coordinator, nominee or authorised decision-maker. Do not let owner pressure or vacancy targets decide the support pathway.
Review service agreements
Check that SDA agreements, SIL service agreements and any tenancy documents describe different roles. Unplanned exit, notice-period and liability language should sit with the provider responsible for that support.
Create owner-safe states
Use labels such as support-provider evidence requested, SIL invoice review, move-in support dependency, transition plan underway or no current SDA claim impact. Do not disclose participant support details or private registration correspondence.
Plan for unplanned exits without mixing records
The NDIA's unplanned-exit guidance says registered SIL providers can claim in limited circumstances after a participant unexpectedly leaves a SIL arrangement, including specific situations involving death or an irretrievable breakdown affecting health and safety. It also points back to service agreements and Commission requirements.
SDA providers need a related but separate workflow. If a participant leaves an SDA home, the SDA vacancy rules, notice evidence, room availability, SDA Finder actions and owner reporting need to be managed through the SDA record. If a SIL provider is claiming an unplanned-exit item, that should not become evidence for an SDA vacancy payment unless the SDA requirements are independently satisfied.
The practical control is a paired exit register: one lane for housing and SDA vacancy facts, one lane for SIL support exit facts, with shared privacy and participant-transition notes only where authority exists.
When a support provider stops
The NDIS Commission says providers stopping services need to manage transitions efficiently, communicate with participants, the Commission and the NDIA, and support participants to transition to a provider of their choice. It also links service stoppage to continuity of supports, transitions to and from a provider, and privacy and dignity.
SDA providers should not take over a SIL provider's obligations by accident. They should record the continuity risk, confirm who is notifying the participant, decide whether dwelling access or safety arrangements change, and keep the participant's housing record stable while support options are reviewed.
For owners, the update should stay factual: move-in delayed pending support-provider confirmation, support transition may affect vacancy timing, or no change to current SDA claim state. The participant's support needs, provider application details and incident history should stay inside the appropriate restricted record.
How StepFree fits the workflow
StepFree SDA is built for the operating layer where dwellings, participants, providers, claims, vacancies, service agreements, support handoffs, exceptions and owner reporting meet.
For the SIL claim cutoff, that means providers can keep the SDA claim record intact while tracking support-provider status, application evidence, plan-manager invoice blockers, move-in dependencies, transition tasks and owner-safe labels in one workflow.
Conclusion
The 1 October SIL claim cutoff should not make SDA teams blur accommodation records with support-payment records. The stronger response is a controlled continuity checklist: map each SIL dependency, verify registration or application evidence from a source, separate plan-manager invoice checks from SDA claims, protect participant choice, prepare unplanned-exit lanes and keep owner reporting factual. That gives providers a practical way to manage support-provider disruption without overclaiming what has changed.
StepFree SDA helps providers connect support-provider dependencies, SDA claim readiness, vacancy workflows, transition tasks and owner-safe reporting in one structured operations record.