How Does NDIS Bulk Claiming Work?

Bulk claiming lets providers submit many payment requests in a single CSV upload through the myplace provider portal, instead of lodging each claim individually. A provider billing 10 participants with one service booking a week for a month would otherwise lodge 40 separate claims; with bulk upload, that becomes a single file with 10 claim lines. The NDIA processes the file and returns a results file the next business day showing which lines succeeded and which failed — failed lines are corrected individually and re-uploaded, without needing to resubmit the whole batch.

How does the bulk payment request process actually work?

Build the request file in the NDIA’s Bulk Payment Request CSV template — one row per claim line, formatted to the exact field rules (dates, support item codes, ABN, unit prices).
Upload the file through the myplace provider portal.
NDIA processes it overnight. The results file is available the next morning, showing a Success or Fail outcome per line.
Fix and reload only the failed rows. A new CSV containing just the corrected records is uploaded — you don’t need to resubmit successful lines.

Why do providers use bulk claiming instead of single claims?

Scenario	Single claims	Bulk upload
1 participant, 1 booking/week, for a month	4 individual claims	1 file, 4 lines
10 participants, 1 booking/week each, for a month	40 individual claims	1 file, 10 lines
Rejected claim	Individually resubmitted	Corrected row re-uploaded in a new file
Error rate	Higher — manual entry per claim	Lower — NDIA guidance notes bulk upload reduces single-claim error messages, duplication, and payment delays

What happens if some claims in a bulk submission fail?

Only the failed rows are affected. The rest of the batch is processed and paid normally — a single formatting error in one row doesn’t hold up the other 39. If a claim within the batch is flagged for manual review rather than rejected outright, that specific claim is held while every other claim in the batch is still paid on standard NDIA payment terms.

There’s an important distinction in how failures behave: a claim that shows a Rejected status through the bulk process cannot be edited in place — it stays rejected permanently and needs a brand-new payment request. A claim with a formatting or data error, by contrast, can usually be corrected in the returned CSV and re-uploaded.

What are the most common bulk claiming errors?

Extra characters or stray data outside the claim rows/columns, which can cause the entire file to fail loading
Incorrect date formatting (the template expects a specific format)
Support item codes that don’t match the current NDIS Support Catalogue
Claim data exceeding a participant’s remaining plan budget
Missing or invalid ABN for plan-managed claims

How can providers reduce bulk claim errors before submission?

Validate every row against the participant’s live plan and current price limits before generating the file, not after the results file comes back.
Keep the file strictly within the template’s row/column structure — a single stray character elsewhere in the file can invalidate the whole upload.
Use the same Claim Reference number when correcting and re-uploading a failed row, so it’s traceable back to the original submission.
Reconcile the results file against your billing system immediately, rather than assuming a successful upload means every line was paid at the claimed amount.