Invoice Insights for NDIS Success

Will, EnableUs Community

Alright, g'day everyone! It's Will here, and welcome back to The EnableUs Community Podcast where we, well, refuse to let invoicing make us cry. Winter, you ready to go deep on invoice insights?

Winter, EnableUs Community

Absolutely, Will. I think we all know it: getting service bookings right is kind of the first domino. If you don't start with accurate bookings, you're stuck with a heap of problems later down the track, both for your cashflow and for your participants' experience.

Will, EnableUs Community

Yeah, and honestly, I've lost count of how many rejected claims I've seen just because of wonky service bookings. Like, let's break down why this matters so much—when a booking's wrong, say you've got the wrong support item, or it's doubled up, or maybe the dates don't line up, the portal just goes 'nope', and suddenly your payment's on ice.

Winter, EnableUs Community

It's actually incredible how one small mistake—like putting in a mismatched support type or missing a participant detail—can end up throwing off the whole invoice chain. And double bookings, they're sneakier than you think. We've heard from providers who accidentally overlapped shifts in the portal, then spent weeks reconciling what was, basically, an easy-to-avoid slip.

Will, EnableUs Community

Oh, don't get me started! Actually, quick story—I had a provider mate last year, he'd done everything right… or so he thought. Turns out, he set up a service booking on the wrong plan line item. Just missed it because the participant's plan had an extension, and, you know, things get moved around. Instead of being paid in five days, he didn't see the money for nearly a month! We helped him spot the mismatch, correct the support code and resubmit, but geez, it was a lesson in slowing down and checking the details.

Winter, EnableUs Community

And honestly, I think that's the biggest takeaway: before you even think about hitting submit, double-check the support codes, dates, participant name—everything needs to match exactly what the plan says. Making those pre-submission checks part of your routine just saves so much drama later on.

Will, EnableUs Community

Totally. Consistency is key, and honestly, it's worth building in reminders or even quick checklists. We've talked about that before—prepping for compliance doesn't just protect your business, it keeps the participant happy since they're not stuck waiting for an outcome. If you want to avoid headaches, start at the source. Literally.

Winter, EnableUs Community

Let's fold in price limits now, Will, because it's one of those things that seems simple but can knock out an invoice in a second. So, NDIS price limits are, well, pretty strict. If you go over—even by a cent—the portal blocks you. Your whole claim is in limbo until it's fixed. That messes with your cashflow immediately.

Will, EnableUs Community

Yeah, for sure. And I think lots of people underestimate just how unforgiving the portal can be. You might have calculated services based on an old price list, or—and I've done this—the rate changed mid-plan and you didn't update. Suddenly, you've exceeded the line item, and it's not just a warning, it's a full-scale rejection.

Winter, EnableUs Community

Remember that finance officer we spoke to last quarter? She found out—nearly at the end of the month—that most of their claims had been sneaky-rejected for going just above the max. It was one of those portal quirks: there'd been an update, and their batch uploader wasn’t rounding small differences. She sorted it by exporting all her claims, double-checking with the current NDIA price table, and resubmitting. They got paid, but honestly, the near-miss dodged a big, big payroll issue.

Will, EnableUs Community

Yeah, and while we're on quirks, sometimes the portal errors don't even tell you what the actual problem is. I mean, why can't it just say "price too high" instead of some code you gotta Google, right?

Winter, EnableUs Community

I know! It's a puzzle half the time. I always suggest: keep a running checklist before you upload claims—confirm the rate, double-check the support type, and make sure dates align. Batch claimers should also run a test with a single service; if it clears, that's your cue your batch should too.

Will, EnableUs Community

Building on what we talked about in earlier episodes, if you get knocked back by a portal error, don't keep doing the same thing expecting it'll magically go through. Pause, check for recent price guide updates and any portal change logs—they sneak them in—then update your batch accordingly. That's basically saved my neck a few times now.

Winter, EnableUs Community

And a top tip is—have a direct contact at the plan manager or finance officer you can reach quickly when you hit one of those unexpected roadblocks. Sometimes they spot changes at the coalface before NDIA publishes anything official. Communication seriously saves time.

Will, EnableUs Community

Love it. These little workarounds add up, but it's all about making peace with the portal and not just fighting it. When in doubt, triple-check or ask for help—saves hours at the back end.

Winter, EnableUs Community

Alright, we've covered bookings and price limits—let's hit batch claims and debtor follow-ups. Because, truly, batching is your best friend if you do it right. But if you skip even one double-check, it's also the fastest way to send out a hundred errors at once.

Will, EnableUs Community

Too right. When you're prepping a batch claim, think step-by-step: make sure your spreadsheet or software exports have all the details. That includes the NDIS support code, participant names, correct dates, amounts under the price cap—we said this before, but you really have to tick every single box. Oh, and for the love of spreadsheets, always preview before you upload to the portal.

Winter, EnableUs Community

It's not just about the first upload, either. Keep a log of what's gone through and what's pending. That way, if the portal spits out an error, you're not scrambling to figure out which invoice caused the rejection.

Will, EnableUs Community

And if you do find yourself with late payments—especially from plan managers—there's an art to following up that won't burn bridges. Like, day 10 after invoice submission, it's totally fair to send a quick, friendly check-in: "Hey, did my invoice come through alright, anything I can provide?"

Winter, EnableUs Community

Right, you don't want to go in all guns blazing—be patient at first. But, as we read in that follow-up doc, if you've got nothing back by business day 12, escalate a bit: ask for a proper status update and double up with another copy of the invoice so nothing can get lost in translation.

Will, EnableUs Community

Exactly. And if it's still dragging on—like, three weeks, no answers—go up the ladder to a senior at the plan management agency. And in rare cases, when that doesn't work, reach out to the participant themselves. But every step along the way, keep it professional, keep it documented, and stay polite. It really does protect those relationships while you fight for what's owed.

Winter, EnableUs Community

Yeah, and we've seen a fantastic example—a Melbourne provider we worked with—who cut their average outstanding payment days in half just by sticking to this follow-up routine. Each week, they logged every submission, chased late payments systematically, and always kept participants in the loop. It wasn't about hassling anyone; it was about transparency and professionalism. Those habits really add up over months.

Will, EnableUs Community

Couldn't agree more. Plus, you'll start building relationships with plan managers who you know pay promptly, and that reputation as a provider who’s on it, but not over the top, is gold. Winter, I reckon that’s a pretty solid recipe for smoother cashflow and less stress, hey?

Winter, EnableUs Community

Absolutely. And look, it's not about being perfect—you're gonna have setbacks. But if you follow a clear process and keep communication professional, you'll recover faster. Alright, that's it for this episode of Inside NDIS! Thanks for joining us—

Will, EnableUs Community

Yeah, legends, thanks for tuning in. There's always more to cover, and we'll be back soon with more hacks, horror stories, and, hopefully, a few laughs. Catch you next time, Winter!

Winter, EnableUs Community

See ya, Will. And thanks everyone. Keep those service bookings sharp and your follow-up even sharper. Bye for now!