The new 90-day NDIS claim cycle changes the problem from processing invoices quickly to seeing which claims are running out of time before they become a crisis.
Shaun Leisegang
4 min read
It’s a Tuesday. An invoice lands in the queue. The support was delivered 77 days ago.
Something’s off. The support item doesn’t line up with the plan. Someone starts calling the provider. Someone else sends an email. Nobody replies quickly, because nobody on the other end is watching this particular clock either.
Thirteen days left. Then ten. Then it’s gone.
The new 90 day claim cycle has taken revenue away from you.
And that’s just one invoice.
An NDIS provider or plan manager isn’t managing one invoice. They’re managing hundreds of these clocks at once, all running down at different speeds, most of them invisible until someone happens to look. Four hundred invoices in a month is not unusual. Four hundred deadlines, each one started by a different service date, each one carrying its own problem or none at all, and all needing to be processed within the new claim cycle.
From 1 December 2026, the National Disability Insurance Scheme Amendment (Securing the NDIS for Future Generations) Act 2026 cuts the time to claim a support from two years to 90 days, starting the day the support was delivered. Not the day the invoice reaches you. Not the day someone gets to it.
Two years was a buffer and a godsend for NDIS operators. It absorbed slow invoices, short-staffed weeks and the monthly claim run. Ninety days removes the buffer and keeps the volume.
One missed claim may not look significant. Multiply that across an entire claims book and the impact becomes very real.
What you lose is revenue that was earned, delivered, documented, and never claimed, because nobody could see it running out of time until it already had. Boards ask why money that was owed to the organisation simply expired.
Provider records now also have to hold up for seven years, with a civil penalty if they don’t. Getting the claim in on time is half the job. The other half is showing, years later, exactly what happened and when.
Most of what’s being said about the 90-day rule right now is about speed. Claim weekly instead of monthly. Add a pair of hands until the new year. Automate the checks so invoices move faster.
Speed helps. But adaptability matters more.
A traditional automation platform that reads invoices and checks them against the plan will get you through this 90 day claiming window.
The problem is what happens when the NDIA changes the rules again. A fixed workflow often means reassessing the process, going back to the vendor, changing the automation, testing it again and absorbing the additional cost.
Organisations that come through this well will be the ones that have built something that can see the whole claims book at once, tell them which claims are drifting toward day 90 before day 77, and adjust when the rules move under them again without additional costs.
That’s a different problem to solve than “process this invoice.” It’s a forecasting problem.
Start with what’s already sitting in your system. Official guidance hasn’t yet settled whether supports delivered before 1 December keep the old window. I wouldn’t put revenue on the answer either way. Clear the unbilled backlog before December and the question stops mattering.
Then build for what comes after December.
This is where Transformr earns its place. We built it as the Frontier Operating System applied to document-heavy processes, and NDIS claiming is one of the clearest examples of that model I’ve seen.
The agents keep working after the first check. They learn from the exceptions your team has already resolved, so the next similar invoice gets flagged as a likely problem on day one, not discovered as a crisis on day 77.
Reportr and Analysr give you the claims book as a whole, not four hundred separate invoices. Which support items keep causing hold-ups. Which providers are slow to respond. Which claims are drifting toward the deadline right now, across the whole portfolio.
And the rules themselves are configured, not hard-coded. When the NDIA changes what counts as a valid claim again, and it will, the model updates. You are not waiting on a rebuild while the clock runs.
People still make the calls that need a human. The provider who won’t respond. The judgement call a rule can’t make. What changes is how early they get the chance to make it, and how much of the book they can see at once instead of one invoice at a time.
The NDIA has redesigned its side of the claim. The providers who come out ahead will be the ones who stop treating claiming as an invoice-by-invoice race, and start forecasting it.
Tecala helps NDIS providers and plan managers get a clearer view of their claims book, identify approaching deadlines and address issues before claims run out of time.
With Transformr, organisations can spot exceptions earlier, understand where delays are happening and adapt their claiming processes as requirements change.
Use the contact form to request a Transformr assessment with Tecala.
From 1 December 2026, the time to claim a support is reduced from two years to 90 days, starting from the day the support was delivered. That means delays in receiving, checking or resolving an invoice can directly reduce the time available to lodge the claim.
The challenge is volume as much as speed. Providers and plan managers may be handling hundreds of invoices at once, each with a different service date and deadline. If an issue is only discovered late in the cycle, there may be very little time left to resolve it before the claim window closes.
Faster processing can help, but the article argues that visibility across the whole claims book is just as important. Organisations need to identify which claims are approaching the deadline, where delays are occurring and which exceptions need attention before they become urgent.
Automation can help identify exceptions earlier, surface patterns across the claims book and highlight claims that are drifting towards the deadline. The article also stresses the value of configurable rules so processes can adapt when requirements change, rather than relying on a fixed workflow that needs to be rebuilt.
Shaun Leisegang is Tecala’s Chief Automation, Data, and AI Officer, helping organisations improve their operations through intelligent automation, data and AI. He previously co-founded and led rapidMATION, which Tecala acquired in 2023, and brings experience across South Africa, the UK, Europe, the USA and Australia.
Bought an OCR tool and still processing invoices by hand? Straight Through Processing shows the real gap, and how to close it.
Read blog
Tecala Transformr, powered by ABBYY Vantage, combines purpose-built AI with autonomous AI Agents to transform document-heavy business processes.
Read blog