SDA 90-day claiming: A readiness checklist for providers
The NDIS reform timetable now gives SDA providers a concrete claim-operation deadline. The Department of Health, Disability and Ageing says the National Disability Insurance Scheme Amendment (Securing the NDIS for Future Generations) Act 2026 passed Parliament on 19 August 2026 and received Royal Assent on 20 August 2026. Under the current reform guidance, from 1 December 2026 the time to make a claim for supports under a participant's plan will reduce from 2 years to 90 days. For SDA teams, this should be treated as a workflow redesign, not a finance reminder. Recurring accommodation claims, vacancy payment evidence, my provider status, plan-manager handoffs, participant invoices, RRC records and owner reporting all need a tighter operating rhythm before the new window starts.
Treat 1 December as an operating deadline
Current NDIS payment guidance still says providers need to submit payment requests within 2 years after an NDIS support has been delivered. The newer reform pages say that window will reduce to 90 days from 1 December 2026. SDA providers should therefore keep current claims moving under the current rule while preparing their systems, calendars and evidence checks for the shorter timeframe.
The change is about claim submission timing. It does not change SDA dwelling enrolment, SDA pricing categories, participant SDA eligibility, written service agreement obligations or the need to be recorded as a my provider where NDIS guidance requires that relationship. Those controls still have to be right before a claim is submitted.
A useful readiness test is simple: can the provider see every unclaimed SDA day, its age, its blocker, the owner of the blocker and the evidence needed to submit before day 90?
Build the claim clock from service delivery
SDA claims often run in monthly batches, but the 90-day window is counted from when the support was delivered. Providers should not let the month-end batch date become the only timing control. The operating record should age each claimable day from the participant-dwelling service period and show when the claim became ready, submitted, paid, rejected or held.
This matters most when a claim is delayed by something outside finance: a new plan in PACE, a missing my provider relationship, an unsigned agreement, a pricing mismatch, a vacancy evidence question, a plan manager invoice query or an NDIA payment enquiry. Those states need escalation dates well before the statutory window becomes the problem.
Timestamp every claimable day
Track support delivery date, claim-ready date, submission date, payment date and rejection or hold date by participant, dwelling and support item. Do not rely only on invoice month.
Separate readiness from submission
Use states such as service delivered, evidence pending, portal relationship pending, plan dates unclear, ready to claim, submitted, paid, rejected, held, corrected or written off.
Lock the payment pathway
Record whether the participant is NDIA-managed, plan-managed or self-managed, which portal action applies, who submits the claim and who owns follow-up if the pathway changes.
Escalate relationship blockers early
For SDA, home and living, behaviour supports and plan management, NDIS guidance links payment to my provider status. Set prompts to check relationship status before the first claim period ages.
Keep plan-manager handoffs visible
If the participant is plan-managed, track when the invoice was sent, whether the ABN and SDA invoice fields are complete, whether the plan manager queried it and whether the claim was lodged.
Reconcile inside the window
Match payments, partial payments, rejections and open claims weekly enough that a failed monthly batch still leaves time to correct and resubmit.
Filter owner reporting
Owners can see expected, submitted, paid, rejected and held income states. They should not receive participant plan details, NDIS numbers, nominee notes or claim evidence packs.
Clean up evidence before batching
NDIS record-keeping guidance says providers need complete and accurate records of supports delivered, and that claims must be complete, truthful and accurate. It lists invoices, support logs, rosters, case notes and service agreements as examples of records, and notes that written service agreements are required for SDA.
For SDA, the evidence pack should be structured around the claimable accommodation period: participant name and NDIS number, dwelling address and postcode, plan dates, SDA support item, price basis, service agreement, occupancy or vacancy evidence, claim quantity, invoice or payment request details, and any correction history.
Batch uploads should be treated as outputs from that record, not as the source of truth. If the bulk file is corrected without fixing the underlying participant, dwelling, agreement or pricing record, the same error can reappear in the next claim cycle.
Control exceptions without hiding late risk
The NDIS payment request page says all claims are submitted in the myplace provider portal except specific replacement-support claims, and that bulk payment requests must be used for supports delivered to participants with plans in the new computer system. It also says validation can fail because of incorrect information such as date, price or fund management type.
The troubleshooting page tells providers to check my provider status, funding management type, available budget, plan dates, pricing alignment and duplicate status before escalating. These checks should become standard SDA exception reasons, not free-text notes.
Do not merge late-risk claims into a general accounts receivable queue. A day-75 unsubmitted claim with a missing relationship request needs a different management response from a day-10 claim waiting for ordinary payment processing.
Connect 90-day readiness to reform records
The NDIS reform pages also flag stronger record retention and payment visibility. The NDIA page says record-keeping periods will be 3 years for participants, 5 years for nominees and 7 years for providers. The Department page says providers will need to keep records relating to payment and receipt of NDIS funds for 7 years, with more detail to come.
That means SDA teams should keep a reform register beside the claim register. The register should capture the official source URL, date checked, change date, internal policy owner, affected claim types, system impact, training status and unresolved interpretation questions. This keeps preparation factual while guidance continues to be updated.
The safest message to teams is practical: claim promptly, prove the accommodation period, keep the evidence accessible, escalate blockers by age and do not promise owners that expected SDA income is secure until the claim status supports that statement.
How StepFree fits the workflow
StepFree SDA can help providers connect dwellings, participants, service agreements, claim schedules, my provider checks, payment outcomes, vacancy evidence, RRC ledgers and owner-safe reporting in one operating workflow.
That structure is useful because the 90-day claiming change cuts across teams. Operations owns move-in and occupancy records, finance owns claim submission and reconciliation, compliance owns evidence quality, and relationship managers own participant or plan-manager follow-up. A shared claim clock makes the next action visible before the deadline becomes a loss.
Conclusion
The 90-day NDIS claiming timeframe is not just a future policy date for SDA providers. It is a reason to tighten the claim clock now. Track every claimable day from service delivery, fix evidence before batching, separate blocked claims from ordinary payment timing, escalate my provider and plan-manager issues early, and keep owner reports tied to verified claim states. Providers that can see late-risk claims daily will be better placed when the new window starts on 1 December 2026.
StepFree SDA can help providers prepare for 90-day claiming with claim-age queues, evidence packs, payment exceptions, RRC reconciliation and privacy-safe owner reporting in one SDA operations workflow.