The NDIA bulk upload is unforgiving. Column order, header spelling, date format and claim-type codes all have to be exactly right, and a file that is nearly correct is rejected in full. Rostery writes the file to the specification so the upload is not the risky part of your week.
Ndia claim files — how it works
Approved, validated invoices are bundled into a claim. Rostery writes the payment request file to the NDIA bulk-upload specification, with the columns in the order the portal expects, dates formatted correctly, and claim types and GST codes drawn from the invoice rather than typed.
You lodge the file through myplace or PRODA and upload the results file when it comes back. Results are matched to the individual lines that produced them, so a partly-paid claim shows exactly which line was reduced and by how much, and a rejection shows the NDIA reason code against the invoice it belongs to.
Why it matters for NDIS providers
A bulk file that fails validation costs a day. A file that passes but contains a wrong line costs more, because the error surfaces weeks later as a payment shortfall nobody can trace. Writing the file from validated records, and matching results back to lines, keeps both problems small.
- Written to specification: column order, headers and formats match what the portal expects.
- Built from validated records: only invoices that passed the pre-claim checks are eligible for a file.
- Results matched to lines: a reduction or rejection lands on the invoice line that caused it, not on a batch total.
What's included
- Claim batching. Approved invoices grouped into a claim with a payment request number.
- Specification-compliant export. The bulk upload file written in the format the NDIA portal accepts.
- Results import. The payment results file read back and matched against the claim.
- Per-line outcomes. Paid, part-paid and rejected recorded against individual invoice lines with reason codes.
- Re-claim handling. Corrected lines can be re-claimed without disturbing the ones that were paid.
Who it's for
Registered plan managers lodging bulk claims, particularly those submitting weekly or fortnightly batches where a single malformed file stops the whole run. It suits teams who want the claim file to be a by-product of the work already done rather than a separate assembly job.
Getting started
NDIA Claim Files is included in your Rostery plan and works the moment your data is in — there is no separate module to buy or set up. Book a demo and we will show it on your own workflows, and use Rostery's “Smart Switch” data migration to bring your existing clients, staff, shifts and notes across from your current software in minutes.
Terms used on this page
Related capabilities
Source
The rules this feature works to are set by NDIS — Pricing Arrangements and Price Limits, which is the authority on them and is updated more often than any page here.