Why July 1 Price Caps Aren’t Automatic Rate Hikes

Will, EnableUs Community

So I was talking to a provider last week who was genuinely convinced that when the NDIA publishes a new price limit, say on July 1, they are actually legally required to bump up their fees to that exact number right away.

Winter, EnableUs Community

Wait, required? Like, like it is a mandatory tariff or something?

Will, EnableUs Community

Yeah, exactly. They thought, oh, the ceiling moved from sixty four dollars to sixty seven dollars, so we have to charge sixty seven now. But it is, it is a cap. It is a maximum limit, not a mandated price tag.

Winter, EnableUs Community

That, that distinction gets missed constantly, doesn't it? People see the published limit and treat it like an automatic pay rise across the board, without even checking what is written in their actual signed service agreement.

Will, EnableUs Community

Right. And that is where the whole July 1 price trap happens. A provider sees the new pricing arrangements drop on July 1, they auto adjust their billing software to the new maximum rate, and then boom, the next month's invoice goes out with a higher hourly rate attached to it.

Winter, EnableUs Community

Without telling the participant or updating the contract first.

Will, EnableUs Community

Without saying a word. And from a compliance perspective, if your signed service agreement says you charge sixty four dollars an hour, and you issue an invoice for sixty seven dollars an hour without written agreement or a valid review clause, that claim is completely vulnerable to a clawback.

Winter, EnableUs Community

A complete clawback. Because you cannot just unilaterally change a contract rate just because a statutory cap changed. The cap gives you permission to negotiate up to that number, but it does not overwrite the legal document you signed with the person receiving support.

Will, EnableUs Community

Exactly. I have seen participant relationships just fall apart over this. Imagine you are a participant, you manage your budget really carefully, and suddenly your plan manager flags that your support worker's agency jumped their rate by three dollars an hour mid plan. No conversation, no revised document, just a higher charge on the monthly portal claim.

Winter, EnableUs Community

It destroys trust instantly. You feel like, um, like you are just an automated funding stream rather than a partner in your own care. And it is totally preventable if you fix the way agreements are drafted in the first place.

Will, EnableUs Community

How so? Like, what should providers actually be putting in those clauses?

Winter, EnableUs Community

Well, instead of putting vague text like rates will be charged in accordance with current NDIS price limits, which is super slippery, you put explicit unit rates. You list the exact support item code, the agreed hourly fee, and then you spell out the exact review trigger. You say something like, fees will be reviewed annually following the NDIA price review, and any proposed changes will be provided in writing thirty days prior.

Will, EnableUs Community

That thirty day window gives everyone room to breathe. It gives the participant time to look at their funding, check their budget, ask questions, or even say, look, my plan cannot absorb a price rise right now, can we keep it at the current rate?

Winter, EnableUs Community

And because it is a cap, you as a provider can legally choose to keep it at the current rate. You are allowed to charge less than the maximum limit if it preserves the working relationship and keeps the service sustainable for the participant.

Will, EnableUs Community

Yeah, that flexibility is literally built into the Scheme design. It is just that so many organisations treat the limit as the default, and then end up in these painful billing disputes that take weeks of administrative overhead to resolve.

Winter, EnableUs Community

And over what? A three dollar variance that could have been handled with a simple one page variation form and a conversation. It is just crazy to risk compliance audits and participant trust over sloppy contract administration.

Will, EnableUs Community

It really is.

Winter, EnableUs Community

So if the agreement is the foundation, the invoice is where the rubber meets the road. And man, the disconnect between those two documents is one of the top reasons claims get rejected or flagged by plan managers.

Will, EnableUs Community

Oh, absolutely. You will have a service agreement that lists support item 01 011 0107 1 1, but then the finance team submits an invoice under a completely different line item code or charges a flat rate that does not match the agreed unit calculation.

Winter, EnableUs Community

Or the description on the invoice says general core support, but the agreement specifically breaks down individual community access versus group activities. When those details do not line up perfectly, the plan manager or the NDIA portal holds the payment.

Will, EnableUs Community

And then the provider sits there wondering why their cash flow is stalled for three weeks, blaming administrative delays, when the root cause was just an internal mismatch between what sales signed and what accounts receivable billed.

Winter, EnableUs Community

That is why having a pre submission verification step is so crucial. Before any claim goes out to the NDIS portal or to a plan manager, someone needs to cross check three things. One, does the support item code match the active service agreement? Two, does the unit rate match the agreed rate? And three, is there sufficient budget allocated under that specific line item?

Will, EnableUs Community

It sounds like basic housekeeping, but when you are managing dozens or hundreds of participants, without an established internal review step, human error just creeps in everywhere. Someone clicks the wrong drop down menu in the roster software and suddenly fifty invoices go out with the wrong line item code attached.

Winter, EnableUs Community

And then you are stuck doing fifty manual credit notes and corrections. It is a nightmare. And it brings us back to communication. If you know pricing adjustments are coming up, whether it is from the annual NDIS review or an internal cost review, you have to talk to participants weeks in advance.

Will, EnableUs Community

Not days, weeks. Give them time to digest it. Give them an explanatory note that explains why the rate is shifting, how it impacts their remaining budget, and when the new schedule of fees will actually show up on their invoices.

Winter, EnableUs Community

Right, because if the first time a participant hears about a rate increase is when they open their monthly statement, you have already lost the high ground. They feel caught off guard. But if you send a letter in early June saying, hey, the NDIA has updated price limits taking effect July 1, here is how our agreement will be updated, and here is what it means for your support hours, it becomes a collaborative process.

Will, EnableUs Community

It turns a potential conflict into a trust building touchpoint. And while you are doing that, you have to look at your service agreement templates themselves. You cannot be using a template that was drafted in 2021 and just swapping out the names and dates.

Winter, EnableUs Community

Oh, tell me about it. The Quality and Safeguards Commission updates rules, cancellation policies change, short notice cancellation timeframes get updated by the NDIA, and providers are still handing out four year old contract templates with outdated terms.

Will, EnableUs Community

It is such a massive exposure point during an audit. If your master template contains obsolete cancellation rules or references old pricing mechanisms, every single agreement you execute from that template inherits those compliance flaws.

Winter, EnableUs Community

So the best practice is to schedule a routine review of your template documentation at least twice a year. Once right before the July 1 pricing release, and once mid year, or whenever the NDIA releases major policy updates.

Will, EnableUs Community

That way, your templates stay agile. You are never scrambling to fix systematic mistakes across hundreds of participant files because your master document was solid from day one.

Winter, EnableUs Community

At the end of the day, a service agreement is not just a piece of paper you check off to satisfy an auditor. It is the core framework for your relationship with the participant. Clear pricing, accurate invoices, and up to date agreements protect the provider's business, but more importantly, they give the participant clarity and control over their funding.

Will, EnableUs Community

Well said. Align those numbers, talk early, and review often. It keeps the focus right where it belongs, on delivering great support.