SupportAbility Virtual Assistant: rostering, claims and the NDIS bulk upload, run for you

Nobody searches “supportability virtual assistant” out of curiosity. You search it because you run an NDIS service on SupportAbility, and the person building the roster, chasing the unsigned case notes, prepping the claims and running the fortnightly bulk upload through PRODA is you, somewhere between a participant call and a staff issue you didn’t see coming. The platform holds the whole operation. It just doesn’t run itself.

And SupportAbility is genuinely good at the NDIS-shaped problem: it rosters against a participant’s funding, ties activities to support items, generates the bulk payment request for the NDIA, and keeps service agreements where you can find them. But almost every one of those strengths ends in a human step. An activity won’t claim cleanly until the case note is signed. A bulk file won’t upload itself to PRODA. A rejected line won’t fix and resubmit on its own. Those steps only happen if someone does them, every roster, every fortnight, without fail. That someone doesn’t have to be you.

The daily rhythm a VA runs in your SupportAbility

Start with the roster, because in NDIS the roster is the business. Your VA works the Activity calendar: shifts built against each participant’s funded supports, staff assigned by the right qualification and availability, clashes and accidental double-bookings caught before they become a participant left waiting on a doorstep. When a support worker calls in sick at 6:40am, the VA is already finding the backfill rather than you discovering the gap at 9. Rostering against funding, not just against time, is the part that protects you later: a shift built against a support category that’s already exhausted is a claim that will bounce, so the VA checks allocated-versus-spent as they build, not after the fact.

Through the day, the case notes. This is the quiet revenue leak in almost every provider we place into. SupportAbility ties billing to completed activities, and an activity sitting with a draft or unsigned case note is an hour of support you delivered and can’t yet claim. Your VA works that list: which activities are missing notes, which support worker owes them, a polite chase, a follow-up if it’s still open the next day. Done daily, the pile never builds. Done never, you hit claim day with a backlog of unbillable shifts and a choice between chasing notes for a week or writing off the revenue.

Then the participant admin that keeps everything claimable. Service agreements kept current in each record, new funding loaded against the right support items when a plan is reviewed, service bookings checked so they haven’t lapsed, and the allocated-versus-spent view watched so nobody discovers mid-period that a participant’s core support budget ran dry three weeks ago. None of this is glamorous. All of it is the difference between a claim that pays and a claim that rejects.

Fortnightly, the big one. Claim preparation, then the upload. Your VA reviews the period’s claimable activities for the correct support item number, the current price against the NDIS price guide, and the right claim type, so the batch is clean before it goes near the portal. SupportAbility generates the bulk payment request file; the VA runs it through the PRODA provider portal under the access your organisation grants, then reconciles the remittance back against the activities so every claimed shift is accounted for and nothing was silently dropped. This is the job that genuinely eats a coordinator’s afternoon, and it’s the most valuable hour a SupportAbility VA gives you back.

And the bit after the upload that most people forget exists: rejections. Some lines always bounce, and they bounce for fixable reasons, a stale service booking, a wrong item number, a date outside the plan dates, an exhausted budget category. Your VA reads the rejection, fixes the cause, and resubmits, instead of letting rejected claims sit until they age past the claimable window and become a write-off. Over a year, working rejections properly is real money recovered rather than quietly lost. For the claiming side beyond SupportAbility, see NDIS billing support on our NDIS page.

Around the agency claiming, the invoicing that doesn’t go through the NDIA at all. Plan-managed and self-managed participants get invoiced to the right plan manager or the participant directly, sent promptly, and chased on a cadence you approve so the gap between delivering support and getting paid stays as short as the rules allow.

The honest bit

A few things worth saying plainly, because a page that pretends the tool is magic isn’t worth reading.

SupportAbility will not write or sign your case notes. It holds them, flags them, and refuses to bill cleanly without them, but the note itself is the support worker’s, and a VA can chase it forever without being able to create it. So the VA’s value here is relentless follow-up and process, not authorship. If your support workers don’t write notes at all, a VA makes the gap visible and chases hard, but they can’t conjure the content, and we won’t pretend otherwise.

The bulk upload is only as good as the data behind it. A clean PRODA upload depends on accurate service bookings, current plan dates and correctly allocated funding, and SupportAbility surfaces those but doesn’t guarantee them. Most of the value of a VA on claiming is the unglamorous discipline of keeping that data right all month, so claim day is boring instead of a fire.

And PRODA access is yours to grant and govern. Your VA uploads under the access your organisation provides through PRODA and the NDIA portal, within your delegation; they don’t hold independent authority over your provider registration, and they shouldn’t. That’s a feature, not a limitation.

What stays with you

This is NDIS, so the line matters and we draw it hard. The VA does operational and administrative work only. What is clinically or operationally reasonable and necessary, what goes in a participant’s plan, how a support is delivered, anything that touches duty of care, and any decision a registered or qualified person must own, all stay with your team. Incident reporting and the judgement inside an incident stay with you. Item-number and pricing decisions are checked by the VA against the current price guide but signed off by you. Plan-management or financial advice to a participant is never the VA’s to give.

The permission model backs this up. SupportAbility’s role-based access means a VA is placed on an admin or finance-style access level that reaches the roster, funding, claiming, bulk upload and invoicing, while clinical-record depth, incident authoring and user administration stay outside what their login can touch. You decide what that access level can see before they start. The wall isn’t a promise we made you trust, it’s an access level you set, and confidentiality signed on day one sits on top of it.

What it costs and where to start

SupportAbility admin sits on the admin tier, $12-17 AUD an hour excl GST, typically 10 to 15 hours a week, which works out around $500-1,100 a month. If the VA also runs front-of-house enquiries and intake the hours sit at the upper end. Specialist reporting work is $18-25. Placement takes 7 to 10 business days, with 5 to 7 days supervised inside your SupportAbility before any solo claiming, a 30-day recalibrate-or-replace guarantee, and no lock-in beyond 14 days notice.

If you want the wider NDIS view, the NDIS plan managers page goes deeper on the sector, the medical and NDIS billing task page covers the claiming side in detail, and the VA cost guide has the full pricing picture. Otherwise book a discovery call with Jenn, who has placed 87+ VAs into Australian businesses since 2024 and will tell you straight if your provider isn’t ready for one yet. Bring your last bulk upload and the list of activities still waiting on case notes. That’s usually where the hours are hiding.