Your NDIS Claims Are Registered. Are They Actually Reconciled?
Your NDIS Claims Are Registered. Are They Actually Reconciled?
Mandatory registration is confirmed. A tighter claim and record-retention standard is still before a Senate committee — but the reconciliation gap it will expose is already there.
From 1 July 2026, Supported Independent Living and NDIS digital platform providers are required to be registered with the NDIS Quality and Safeguards Commission. Most of the compliance conversation this week has been about the registration mechanics — nominated bank accounts, identity verification, enrolment paperwork. Finance teams have been ticking that box for weeks.
But registration was never the hard part. The hard part is what happens after a claim is lodged — and for a lot of NDIS providers, that part still doesn't hold up to scrutiny. And there's a second layer of change worth understanding clearly, because it's easy to confuse what's already law with what's still a proposal working its way through Parliament.
|
1 July 2026
Confirmed and in effect: mandatory registration for SIL and platform providers with the NDIS Quality and Safeguards Commission.
|
Not yet law
Still proposed: the 7-year record retention duty and the 90-day claim window sit in a Bill before a Senate committee, reporting extended to 14 August 2026.
|
What Actually Changed on 1 July
The registration requirement itself is straightforward on paper. SIL and platform providers now need to be enrolled with the NDIS Quality and Safeguards Commission, provide a nominated and validated bank account for payments, and — where claims exceed a set threshold — hold supporting documentation ready to produce on request.
None of that is difficult to satisfy from a compliance checklist perspective. What it does, though, is put a much brighter spotlight on the data sitting behind every claim your organisation submits. When claims exceeding the threshold require supporting documentation, "supporting documentation" means your rostering system, your service delivery records, and your finance ledger need to tell the same story — consistently, and on demand.
For a lot of providers, they don't.
The Gap Between Rostered, Delivered, and Claimed
In organisations running multi-site SIL or high-volume platform-based service delivery, three separate systems typically hold three separate versions of the truth: the rostering platform (ShiftCare, Careview, or similar) records what was scheduled; the service delivery log records what actually happened, often with variations for cancellations, short notice changes, or worker substitutions; and the finance system records what was claimed and what was paid.
Reconciling those three layers by hand, in a spreadsheet, at month-end, is how most NDIS finance teams still operate. It works — until claim volume grows past a level one or two people can manually cross-check, or until an auditor asks for the trail behind a specific claim from four months ago and the answer takes a week to assemble rather than an afternoon.
The finance teams who feel comfortable under the new registration regime aren't the ones with the tidiest enrolment paperwork. They're the ones who can produce a clean claim-to-payment trail for any individual participant, any week, on short notice — because the reconciliation happens continuously, not at quarter-end when someone finally has time.
The 90-Day Claim Window: Proposed, Not Yet Confirmed
Here's where it's worth being precise, because a lot of sector commentary this year has blurred this distinction. The 90-day claim window and the 7-year record retention duty aren't part of what commenced on 1 July. They're contained in the National Disability Insurance Scheme Amendment (Securing the NDIS for Future Generations) Bill 2026, introduced to Parliament on 14 May and currently with the Senate Community Affairs Legislation Committee. That committee's reporting deadline has already been pushed back once, from mid-June to 14 August 2026, and several disability advocacy organisations have formally submitted that the Bill shouldn't proceed in its current form. Whether it passes, and in what shape, is genuinely still open.
That's not a reason to ignore it. If it passes broadly as drafted, the claim window drops from the current two-year lodgement period down to 90 days, and record retention becomes a 7-year statutory duty with a civil penalty attached to non-compliance — a materially tighter standard than providers operate under today. The sensible position for a finance function is to treat these as highly likely, well-signalled changes worth preparing for now, while being accurate in board and team communications that they aren't locked in yet. Telling your leadership team "this is already the law" when it's still before a Senate committee is the kind of thing that undermines trust in your finance function's judgement later, even if the substance of the change turns out to be right.
Where AI Genuinely Helps — and Where It Doesn't
This is the part of the conversation that gets oversold constantly, so let me be specific about what AI actually does well here and where it doesn't replace anything.
What it does well: pattern-matching across large volumes of claim, roster, and payment data to flag anomalies before a claim is lodged — a shift claimed with no corresponding roster entry, a payment received that doesn't match the claimed amount, a participant plan category mismatch. That's a genuinely useful early-warning layer, and it scales in a way manual review can't.
What it doesn't do: replace the judgement calls around what's "reasonable and necessary" under a participant's plan, or absorb responsibility for a claim that turns out to be wrong. The finance team is still accountable for every claim submitted under their ABN. AI-assisted reconciliation reduces the volume of things a human needs to check manually — it doesn't reduce who's on the hook if something slips through.
The why behind building this kind of tooling is straightforward: NDIS finance teams are being asked to hold a higher standard of evidence with the same headcount they had last year. The how — the specific matching logic, the anomaly thresholds, the integration approach between rostering and finance systems — is exactly the kind of build we do with clients at PFL, and it varies enough by provider size and system stack that there's no generic answer worth publishing.
A Practical Check for Your Own Process
Before assuming your organisation's reconciliation is solid, there's a simple test worth running: pick five claims at random from three months ago, and see how long it takes to produce the full trail — the roster entry, the service delivery confirmation, the claim submitted, and the payment received — for each one. If that takes an afternoon, you're in reasonable shape. If it takes a week, involves chasing three different people, or surfaces a claim you can't fully account for, that's the gap the new registration regime is about to expose.
A few specific things worth checking as part of that test: whether cancelled or short-notice-changed shifts are consistently reflected in what gets claimed, rather than the original roster being claimed by default; whether your finance system flags a payment that doesn't match the claimed amount, or whether that only gets caught if someone happens to notice; and whether your record retention practice would comfortably cover a 7-year window if the proposed retention duty passes in something close to its current form, rather than sitting in an old email inbox or a former staff member's file structure.
None of this needs to be solved with a major systems overhaul. For a lot of providers, the highest-value fix is simply establishing a standing monthly reconciliation discipline — checking a sample of claims against roster and payment data every month, rather than only looking closely when an audit or a funding review forces the issue. That habit alone catches most of the drift before it becomes a pattern large enough to attract scrutiny.
Is Your Claim Trail Actually Audit-Ready?
Mandatory registration is here, and a materially tighter claim and record-retention standard is well-signalled even before it's confirmed law. PFL provides senior-level outsourced finance, management reporting, and AI automation for Australian NFP, NDIS, and SME organisations — including building the claim-to-payment reconciliation layer that holds up under audit.
Talk to PFL →
Comments
Post a Comment