Allied Health Claims Reconciliation Just Got Six New Line Items to Check
Allied Health Claims Reconciliation Just Got Six New Line Items to Check
Three weeks into the new pricing schedule, here's a practical AI-assisted way to catch reconciliation gaps before they become bad debts.
Monday's post looked at what the 2026-27 NDIS Pricing Schedule means for allied health billing specifically — the new suffix structure that splits a single therapy service into up to six separately coded line items. Worth being precise about scope: this particular suffix system is an allied health and therapy-specific change under the current Pricing Schedule, not a rule that's replaced claiming logic across the whole NDIS support catalogue. If your organisation also runs SIL, Core Supports or support coordination alongside allied health, those lines aren't carrying the same _CA/_NF/_PT/_RR/_TH suffixes — though SIL has its own separate structural change worth checking, covered below. For any practice billing therapy supports, though, three weeks in, the practical question isn't "did we bill correctly," it's "can we prove we billed correctly against a schedule that has more moving parts than the one we reconciled against last financial year."
What Changed in the Claims Structure
Since 1 July, applicable support items carry suffixes for each claim type: cancellation (_CA), non-face-to-face time (_NF), provider travel (_PT), NDIA-requested reports (_RR) and telehealth (_TH), each sitting alongside the direct service item. Supported Independent Living claims delivered from 1 July also move to a new registration code, 0138 — Assistance with Supported Independent Living — with its own associated non-labour travel cost item. None of this is a minor administrative tidy-up. It roughly doubles or triples the number of distinct line items a reconciliation process has to check against a single participant's plan in a given period.
|
5 suffixes
_CA, _NF, _PT, _RR and _TH — the new claim-type suffixes now sitting alongside the direct service code for allied health and therapy support items.
|
50%
The rate at which provider travel is now priced relative to the service's hourly rate — a specific, checkable figure reconciliation should be testing against.
|
Why Reconciliation Is Harder Now, Not Just Different
For a therapy practice, more line items per service means more opportunities for a claim to be rejected on a technicality — a wrong suffix, a travel claim submitted under the direct service code instead of _PT, a telehealth session that should have carried _TH but didn't. Each rejected or partially-paid claim then needs to be traced, corrected and resubmitted, which is exactly the kind of manual, repetitive matching work that used to be manageable when there was one code per service and is much harder to do reliably by eye now that there are up to six.
The bigger risk sits with claims that get paid incorrectly rather than rejected outright — a travel claim that's accepted but underpriced relative to the correct 50% rate, for instance, or a SIL claim still running under an old registration code. These don't throw an error. They just quietly leave money on the table or, in the reverse case, create a claim that doesn't match the participant's actual plan and support budget, which is the kind of discrepancy that surfaces badly during an NDIA compliance review rather than at the point of billing.
A multi-service NDIS provider I've spoken with — running both a small allied health therapy team and a handful of SIL properties — described exactly this pattern in the first few weeks after 1 July: claims were going through, cash was coming in, and nothing looked obviously wrong until someone sat down and matched a sample of paid claims against the actual service delivery notes. A handful of SIL claims were still running under the old registration code. A batch of therapy provider travel claims had been submitted at the old flat rate rather than the new 50%-of-service-rate calculation. None of it was fraud or even carelessness — it was software and habits that hadn't fully caught up to a schedule that changed faster than the internal process for checking it.
A Practical AI-Assisted Reconciliation Workflow
This is a matching problem at scale, which is where AI-assisted reconciliation genuinely earns its keep. The core idea: take your claims data — what was submitted, what was paid, at what rate, under which code — and check it systematically against the current pricing schedule's line items and rates, rather than against whatever template or macro your system was using in June. Done well, this flags three things automatically: claims sitting under an outdated code, travel or report-writing time recorded in service notes but not claimed at all, and paid amounts that don't match the schedule's current rate for that item.
The "why" here matters as much as the "what." A finance team checking this manually, line by line, across a full participant caseload simply won't keep pace with the volume, and will tend to sample-check rather than review everything — which means the same handful of errors can persist for months before anyone notices. An AI-assisted check that runs the same comparison consistently across every claim removes that sampling risk, even if a human still needs to review and action anything it flags.
What This Means for Cash Flow, Not Just Compliance
It's worth separating two different consequences of a reconciliation gap, because they call for different urgency. A claim rejected outright is a cash flow problem — the money simply doesn't arrive until it's corrected and resubmitted, and if that correction cycle takes weeks rather than days, it shows up directly in a provider's working capital position. A claim that's accepted but under-priced or mis-coded is a slower-burning problem — the cash does arrive, so nothing looks urgent, but it compounds quietly across a caseload and across months, and it's the kind of gap that's much cheaper to close now, three weeks in, than to unwind after two quarters of claims have gone through the same way.
There's a second-order risk worth naming honestly: a provider that's been paid against claims that don't correctly match a participant's plan and support budget isn't just leaving money on the table when the error runs the wrong way — it can also create an overpayment position that NDIA can and does claw back on review. Getting the reconciliation right isn't only about maximising revenue. It's about making sure whatever's been paid is actually defensible against the plan and the schedule if a claim is ever queried.
Where to Start This Week
- If you deliver allied health or therapy supports, pull every claim submitted since 1 July and check it against the current suffix structure — not just the rate, the code itself.
- If you deliver SIL, confirm those claims are running under the new 0138 registration code, not a carried-over prior code — this is a separate structural change from the therapy suffixes above.
- Spot-check provider travel claims against the 50%-of-service-rate calculation rather than assuming your system updated it correctly.
- Set a recurring monthly reconciliation check rather than treating this as a one-off clean-up — the schedule is reviewed annually, and this line-item structure looks to be here to stay.
Not confident your claims are reconciling cleanly against the new schedule?
PFL provides senior-level outsourced finance, management reporting, and AI automation for Australian NFP, NDIS, and SME organisations — including reconciliation reviews built around the current pricing schedule, not last year's.
Talk to PFL →
Comments
Post a Comment