Turning Supports into Cashflow: Submitting NDIS Payment Requests in MyPlace

From Supports to Cashflow – Getting Ready to Claim in MyPlace

Winter, EnableUs Community: Hey everyone, it’s Winter here, and welcome back to the EnableUs Community Podcast. Today we’re talking about one of those unsexy but absolutely make-or-break topics for NDIS providers: how you turn great support work into actual cash in your bank account through MyPlace payment requests.

Will, EnableUs Community: And I’m Will. I love this one because, honestly, you can be brilliant with participants, but if you stuff up MyPlace claims, you’re still going to be stressing about cashflow and chasing errors for weeks.

Winter, EnableUs Community: Yeah, and we see that a lot. Providers doing amazing personal care, community access, therapy – all the good stuff – then getting their claims rejected, or just delayed, because a few key pieces weren’t in place. So, in this episode, we’re going to walk through what you need set up before you even try to claim, how to choose between single and bulk payment requests, and then how to avoid rejections and fix mistakes fast.

Will, EnableUs Community: Let’s start with the foundations – the boring but critical stuff. Before you can claim anything in MyPlace, you need an active service booking that actually covers the dates you delivered the support. If you don’t have that service booking, or it doesn’t cover that period, MyPlace will just say, nope, not happening.

Winter, EnableUs Community: Exactly. And it’s not something you fix after the fact easily. Best practice is: service booking first, supports second, claiming third. I like to say, “no booking, no service, no claim.” So your admin or intake process should always include creating that service booking before supports start.

Will, EnableUs Community: The next piece is being recorded as the participant’s “my provider”, especially for NDIA-managed plans. When you’re set up as “my provider” in the system, the NDIA basically knows, cool, this provider is allowed to receive payments from this plan. That makes the validation smoother and brings payment times down to around two to three business days in most cases.

Winter, EnableUs Community: Yeah, and if you’re not listed as their “my provider”, the system can still process the claim, but it often goes through extra checks. That’s when you see claims taking up to ten business days instead of that nice quick two to three. So, if you’re wondering why one participant’s payments land in a couple of days and another’s drag on, that “my provider” status can be the reason.

Will, EnableUs Community: Another big prerequisite that people skip is checking the participant’s budget before you agree to services, and again before you actually claim. In MyPlace you can see the plan details and remaining funds in each category. If there’s not enough budget sitting there in the right support category, your claim is going to get rejected automatically.

Winter, EnableUs Community: So build that into your workflow. When you create or update the service booking, check that there’s enough budget in that category to cover what you’re planning to deliver. Then, when you go to submit claims, just quickly confirm there’s still room there. It’s a lot less painful than delivering weeks of support that can’t be paid because the budget’s already been used.

Will, EnableUs Community: Now, let’s talk about timing rules. There’s a two-year window to submit claims – and this is based on the support start date. So you’ve got up to two years from when you delivered the support to get that claim in. That rule came in on 3 October 2024, and on paper it sounds like, sweet, we’ve got ages.

Winter, EnableUs Community: But please don’t treat it like a two-year lolly jar that you only remember at tax time. Best practice is still to claim weekly or fortnightly. That way your cashflow is predictable, you spot any issues early, and you’re not trying to reconstruct six months of shifts from old rosters and text messages.

Will, EnableUs Community: And while we’re on timing, there’s another rule that trips people up: you generally can’t claim before you deliver the service. Prepayment is usually not allowed. You can’t invoice the NDIA for next month’s supports “just to get ahead”. The exception is some high-cost supports where prepayment is specifically approved, but for normal day-to-day supports, it’s strictly delivery first, claim second.

Winter, EnableUs Community: Last prerequisite we’ve gotta mention is your banking details. Payments don’t magically follow your new bank account if you’ve changed banks. MyPlace sends money to the account that’s in your provider profile. If that’s out of date, you can have fully approved claims that just fail at the payment step.

Will, EnableUs Community: I’ve seen providers panic because nothing is landing, and it turns out they changed banks months ago and never updated MyPlace. So make it a checklist item: whenever you change bank accounts, update it in MyPlace, and maybe do a regular quarterly check just to be safe.

Winter, EnableUs Community: Alright, so that’s your foundation: service booking in place, you’re set up as “my provider” where relevant, there’s budget in the right category, you understand the two-year window but you’re claiming regularly, no prepayment unless specifically allowed, and your banking details are spot on. With that done, we can jump into how you actually submit claims – single versus bulk – and which one makes sense as you grow.

Single vs Bulk Payment Requests – Choosing the Right Workflow

Will, EnableUs Community: Okay, let’s talk about your two main pathways in MyPlace: single payment requests and bulk payment requests. They both land money in your bank, but the workflow and the scale they suit are really different.

Winter, EnableUs Community: Yeah, so picture you’re a smaller provider or you’re just starting with one participant. A single payment request can feel more straightforward at first because you’re literally just filling out a form on the screen. You go to “My Payment Requests” from the MyPlace home page, then click “Create Payment Request”.

Will, EnableUs Community: From there, you search for the participant, either by their NDIS number or surname. Once you select them, MyPlace will show you the active service bookings you’ve got with that participant. Step one is always: pick the right service booking and make sure it covers the dates you actually worked and has enough remaining budget.

Winter, EnableUs Community: Then you start putting in the actual service details. You enter the date of service – and MyPlace wants that in a YYYY dash MM dash DD format – and you choose the NDIS Support Item Code from the dropdown. That support item has to match what you actually delivered and it has to fit under that service booking’s funding category.

Will, EnableUs Community: Next is quantity and unit price. Quantity might be hours, or units, depending on the support. And the unit price you put in has to be at or under the NDIS price limit for that exact support item. If you go even a few cents above the price guide, the system’s going to knock it back.

Winter, EnableUs Community: Where we see a lot of quality difference is in the description. People either leave it really vague, like just repeating the support item name, or they use it to clearly explain what actually happened. MyPlace doesn’t need an essay, but it definitely helps to be specific.

Will, EnableUs Community: So instead of writing “personal activities”, a stronger description would be something like, “Assisted with morning personal care including showering, dressing, medication administration and breakfast preparation.” That gives context. If someone reviews the claim later, they can see what you actually did that day.

Winter, EnableUs Community: If you’ve done multiple sessions or you’ve delivered different supports for the same participant, you just add more line items inside that same single payment request. Each line has its own date, support item, quantity, and description. Then at the bottom you’ll see the total amount you’re claiming before you hit submit.

Will, EnableUs Community: Now that’s fine if you’ve got a small caseload. But as soon as you’ve got more participants or more shifts, typing claims one by one quickly becomes a full-time job. That’s where bulk payment requests come in – and honestly, we recommend providers shift to bulk as soon as they’ve got any scale at all.

Winter, EnableUs Community: Bulk uploads are also handy because they work for all participants, regardless of which NDIA computer system their plan sits in. So you don’t have to remember, “Oh, this participant I do single claims for, that one I do bulk.” It’s one consistent process for everyone.

Will, EnableUs Community: The process starts by downloading the Bulk Payment Request template from the MyPlace provider portal resources page. It’s a CSV file, and it already has all the columns that MyPlace expects. The big tip here is: do not delete any of those columns, even if you think you don’t need them. If you start stripping columns out, the upload can fail or misread your data.

Winter, EnableUs Community: Once you’ve got the template, you enter one row per line item you’re claiming. So if you’ve got, say, ten shifts across three participants that week, that’s ten rows. Each row needs things like the participant’s NDIS number, the Support Item Number from the NDIS Price Guide, the start date and end date in that YYYY dash MM dash DD format, the quantity delivered, and the unit price.

Will, EnableUs Community: And, just like with single claims, every line also needs a description of the services you provided. Again, specific and clear is better than generic. All of those dates need to fall within the participant’s plan dates and the service booking period, or the system will come back with errors.

Winter, EnableUs Community: When you’ve filled in all your rows, save the file with a name that makes sense later. Something like “Bulk Claims Week Ending 15-Feb-2026” is way better than “claims-final-FINAL-2”. It means in three months’ time you can see exactly which period that upload covered.

Will, EnableUs Community: Then you head back into MyPlace, go to “Bulk Payment Requests”, choose “Upload File”, pick your CSV, and hit submit. MyPlace will run a validation check across all those rows and, usually, give you immediate feedback about any errors it spots – like wrong dates, invalid support items, or price issues.

Winter, EnableUs Community: What I love about the bulk process is that you can build it into a weekly or fortnightly rhythm. Your rostering or finance person exports the data, drops it into the CSV template, does a quick sense-check, uploads, and you’re done. One action, lots of claims, instead of a hundred tiny clicks in the portal.

Will, EnableUs Community: So if you’re still doing everything as single payment requests and you’ve got more than a handful of participants, this is your nudge to move to bulk uploads. It saves time, reduces human error from retyping, and keeps your cashflow moving because you’re more likely to claim consistently.

Winter, EnableUs Community: Alright, we’ve covered how to set things up and the two main workflows. In our last chapter, we’re going to get into all the ways claims go wrong – the common rejection reasons – and how to fix mistakes without blowing up your cashflow.

Avoiding Rejections and Fixing Mistakes Before They Hurt Cashflow

Winter, EnableUs Community: Let’s get into the fun part – or maybe the painful part – which is claim rejections. Because if you know the patterns, you can catch them before you hit submit.

Will, EnableUs Community: Yeah, and the patterns are actually pretty consistent. One of the big ones is claims where the service date sits outside the participant’s plan dates. So either the plan has already ended, or the claim date is before the plan starts. MyPlace will just reject those automatically.

Winter, EnableUs Community: So a simple safeguard is: before you submit, double-check that the dates you’re claiming fall within the current plan period. It sounds basic, but when you’re rushing or copying data across spreadsheets, it’s really easy to have one line item slip outside the plan dates.

Will, EnableUs Community: The next classic rejection is pricing. The system will tell you something like, “The unit price entered on this payment request is not a valid price,” or that it exceeds the allowed amount for that support item. And this can literally be a matter of a few cents over the NDIS Price Guide limit.

Winter, EnableUs Community: So your process needs to include regularly checking the current NDIS Price Guide and making sure your billing system is aligned with those limits. Don’t rely on an old spreadsheet from two years ago. And when in doubt, be conservative – don’t round up your prices beyond what’s published.

Will, EnableUs Community: Another one is duplicate claims. MyPlace will reject a claim if it looks like you’re trying to bill for the same service – same participant, same date, same item – more than once. Sometimes this happens when someone resubmits a claim to fix an error but doesn’t realise the first one actually went through.

Winter, EnableUs Community: A quick habit that helps is to check your payment request history before you resubmit. Just scan for that participant and that date and make sure you’re not accidentally doubling up. It’s especially important if you’ve got more than one person handling claims.

Will, EnableUs Community: And then there are the rejections or payment failures that aren’t about the claim itself but about your banking details. You can have everything correct on the claim – dates, prices, item codes – but if the bank account in your MyPlace provider profile is wrong or out of date, the money can’t land.

Winter, EnableUs Community: So build a “red flag checklist” into your process. Before submitting a batch, make sure: one, service dates sit inside plan dates; two, unit prices match the NDIS Price Guide; three, you’re not duplicating past claims; and four, someone has actually checked your bank details in MyPlace recently and confirmed they’re still current.

Will, EnableUs Community: Now, even with all of that, mistakes still happen. The good news is, MyPlace does let you cancel payment requests that are “pending” or even “paid” in order to correct them. If you see an error, don’t just let it roll through and hope it sorts itself out.

Winter, EnableUs Community: Yeah, if you catch an error, go into that payment request, choose “Cancel”, confirm, and then create a corrected claim with the proper details. It’s cleaner and it keeps your records accurate, which is really important if you’re ever audited or you need to explain something to a participant.

Will, EnableUs Community: For bulk uploads, the fix is usually to go back to your original CSV file, correct the rows that had issues, save it under a new name, and upload it again. That “new name” bit is important. Don’t reuse exactly the same filename, because it just creates confusion later about which file was the corrected version.

Winter, EnableUs Community: So maybe your first upload was “Bulk Claims Week Ending 15-Feb-2026”, and the corrected one becomes “Bulk Claims Week Ending 15-Feb-2026 – Corrected”. That way if you’re looking back through your records in six months, you instantly know which file to trust.

Will, EnableUs Community: If you put everything we’ve talked about together, you end up with a really solid claiming process: service bookings in place before supports, “my provider” status where needed, regular weekly or fortnightly claims, bulk uploads for efficiency, tight checks on dates and prices, and a clear process for fixing errors instead of letting them snowball.

Winter, EnableUs Community: And that’s when you feel the difference in your business. Cashflow stops being this constant stress because most of your claims are paid within that two to three business day window, and you’re not losing hours chasing preventable rejections.

Will, EnableUs Community: Alright, we’ll wrap it there. If you’re listening and thinking, “Oh, that’s us, we’re still keying everything in one by one,” maybe pick one thing from today – like moving to bulk uploads or tightening your pre-claim checks – and start there.

Winter, EnableUs Community: Yeah, don’t feel like you’ve gotta overhaul everything overnight. Just improve one part of your process at a time. Thanks so much for hanging out with us on the EnableUs Community Podcast.

Will, EnableUs Community: I’m Will, this has been fun, and we’ll be back with more quick, practical episodes to help you navigate the NDIS world with a bit less stress.

Winter, EnableUs Community: And I’m Winter. Take care, look after your participants and your cashflow, and we’ll catch you in the next episode. Bye!