If you deliver supports to Agency-managed NDIS participants, bulk claiming is how you get paid. Done well, it’s a few minutes at the end of a cycle. Done badly, it’s a spreadsheet marathon that ends in rejected lines and delayed payments. This is the plain-English version of how it works.
What is a bulk claim?
Rather than submitting one claim at a time, a bulk claim lets you request payment for many delivered supports at once by uploading a single file (a bulk payment request) to the NDIS via the provider portal or PACE. Each line in that file represents one support delivered to one participant, priced against an NDIS support item.
The bulk claim workflow, end to end
- Deliver the support. A worker completes a shift or service for a participant.
- Record the hours. Verified start and finish times become the billable quantity — this is where accurate timesheets matter.
- Match to a support item. Each support maps to an NDIS support item number with a price cap set by the current Pricing Arrangements and Limits.
- Check the budget and plan. The participant must have funds in the right support category, and the delivery date must fall within an active plan.
- Generate the claim file. Assemble the lines into the NDIS bulk upload format (a CSV with specific columns).
- Submit and reconcile. Upload to the portal, then match the payment summary back against what you claimed — and re-submit anything rejected.
Why claims get rejected
The portal validates every line automatically, and it’s unforgiving. The most common reasons a line bounces:
- Expired or wrong support item code — the item was superseded in the latest price guide, or the wrong code was used.
- Price above the cap — the claimed rate exceeds the current limit for that item.
- No funds / wrong category — the participant’s budget for that support category is exhausted.
- Outside plan dates — the support was delivered before or after the active plan window.
- Not endorsed — for some supports you must be the participant’s endorsed provider before claiming.
A single rejected batch can hold up a chunk of your cash flow for weeks, so the goal is to catch these before you submit.
Getting it right the first time
The providers who claim smoothly all do the same things: they keep support-item pricing current, they track each participant’s remaining budget as supports are delivered, and they validate the claim file against live rules before uploading — not after the portal rejects it.
How StaffLoop helps
StaffLoop is built for this. It keeps support-item pricing in sync with the current NDIS Pricing Arrangements, tracks each participant’s budget so you’re warned before a shift would exceed a funded cap, and generates a PACE-ready bulk claim CSV validated against active codes — so you download, upload, and get paid, instead of chasing rejections.
New to bulk claiming or moving onto PACE? Our guide to the NDIS PACE transition covers what’s changed and how to avoid the new validation traps.
This article is general information, not financial or compliance advice. Always confirm current requirements with the NDIA and the latest NDIS Pricing Arrangements and Limits.
