Modeling the NDIS 90-Day Claim Limit in Python

Résumé

Pixel shares a developer-focused guide to modeling the NDIS 90-day claim limit in Python, including day counts, working-day deadlines, and a slack score for each unpaid line. It explains the shift taking effect on 1 December 2026 and shows how providers can identify claims at risk using code and a SQL query.

DEV Community

Modelling the NDIS 90-day claim limit in Python: day counts, working-day deadlines and a slack score for every unpaid line

Originally based on our guide to the NDIS 90-day claim rule on rostery.com.au. This version is rewritten for developers, finance analysts and anyone who builds the reports behind NDIS claiming. General information only, not legal or financial advice. The day count and some edge cases below are our reading of the Act; the NDIA hasn't published guidance on them. Australia's National Disability Insurance Scheme (NDIS) pays providers for supports delivered to participants under their plans. Until 30 November 2026, a claim for a support can be made up to 2 years after the support. From 1 December 2026 that limit drops to 90 days. The change is one amendment to section 45A(5) of the NDIS Act, made by the Securing the NDIS for Future Generations Act 2026, and it has no transitional rule for older supports. For a provider's systems, that turns a rarely checked limit into a deadline on every line. Every completed support now has its own clock, and the clocks run in parallel. If your job is the reporting layer, the question you'll be asked is simple: which unpaid lines are going to run out of time, and how soon? There's already a good spreadsheet answer to that question. Our Medium piece on the NDIS claim ageing report buckets lines by age and runs a weekly meeting around them. This post takes a different route. It models the rule in code, so you can test it, put it behind an API or a scheduled job, and rank lines by how much room they really have rather than by age alone. The code uses the Python standard library only. There's a SQL version of the core query near the end. What the rule says, as requirements Before writing any code, it helps to turn the law into requirements a test can check. The window. A claim must be made "before the end of the following period starting on the day the support is provided": 90 days from 1 December 2026 (section 45A(5) as amended). Day 1. Section 36 of the Acts Interpretation Act 1901 says a period that begins on a day includes that day. So the support day is day 1 and day 90 is 89 days later. A support on Tuesday 1 December 2026 has day 90 on Sunday 28 February 2027. The switchover. The amendment applies to claims made on or after 1 December 2026, with no carve-out for older supports. Anything delivered on or before 2 September 2026 is already past day 90 on 1 December, so it has to be claimed by Monday 30 November while the 2 year limit still applies. Who claims. Section 45A(2): the person managing the funding, or the provider where the NDIA manages it. For plan-managed supports the plan manager claims; for self-managed supports the participant does. The 90 days apply to all of them. The exception. Section 45A(6) still lets the NDIA treat a late claim as made in time if exceptional circumstances justify it and the claim was made within a reasonable period. The NDIA hasn't said what it will accept, so the model treats a missed deadline as a miss. Weekends. Section 36(2) of the Acts Interpretation Act lets something due on a weekend or holiday be done on the next working day, but the NDIA hasn't said how its claiming system counts. Our original guide recommends treating the last working day before day 90 as the deadline, so the model keeps two dates: the legal one and a working one. Two more details shape the data model. First, a bulk claim file has a start and an end date for each line (SupportsDeliveredFrom and SupportsDeliveredTo). The Act counts from "the day the support is provided" and doesn't say which day of a multi-day support counts. The NDIA's Guide to getting paid asks for claims within 90 days of the support "being delivered in full". Until the NDIA settles it, the cautious choice is to count from the first day. Second, a rejected payment request can't be edited. You lodge a new one, and on our reading the new request is a new claim that must itself fall inside the 90 days of the original support. Rejection doesn't reset the clock. The data model One row per support line is enough. The...
Modeling the NDIS 90-Day Claim Limit in Python
Powered by Readybot.io

Les dernières actus de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …