Skip to content
Corella

Free tool · runs in your browser

Check a bulk payment file before the portal does.

Choose the 16-column CSV you’re about to upload. Every line is checked against the NDIA’s published rules — the header row, the numbers, the dates, quantity or hours, the codes and the ABN — and each problem says how to fix it.

When the NDIA’s answer comes back, read that here too: each rejected line in plain English, and a file of just those lines to claim again.

The file never leaves your browser. Nothing to sign up for.

Fix before upload

Line 3 · Hours

"02:30" has a leading zero. Write it without one: 2:30.

Fix before upload

Line 4 · NDISNumber

"43000002" isn't nine digits starting 43. Use the participant's own NDIS number — not a nominee's or a parent's.

Fix before upload

Line 6 · ABN of Support Provider

"12345678901" isn't a valid ABN — its check digits don't add up. Check it against the provider's invoice, or use REIMB or EXCLS if one applies.

From the example file below — made-up numbers.

The checker

Before you upload, and after the NDIA answers.

Two jobs in one place: catch what would stop the upload, then turn the NDIA's results file into a list of what to fix and a file to claim again.

A simplified check, not legal, financial or compliance advice. It reads the file in your browser — the file never leaves your browser — against the NDIA's published rules for the bulk payment request file. It can't see your service bookings, your participants' plans or your registration, which is where most rejections come from. This page is not made by or affiliated with the NDIA.

Choose the CSV you’re about to upload to the provider portal — or try the example file — and every problem the file itself can show appears here, line by line.

What it checks

The NDIA’s own rules, line by line.

From the NDIA's bulk payment requests self-help guide (December 2025) and its template. Where the guide disagrees with itself, the check says so rather than guessing.

The file

The filename (20 characters at most, with the .CSV), the sixteen-column header row exactly as the NDIA's template has it, 5,000 lines at most, 10MB at most, and rows that look empty but aren't.

Every line

The registration and NDIS numbers, both dates (readable, not in the future, start before end), the support item, the claim reference, quantity or hours (one of them, in the right format), the unit price, the GST code, the claim type and cancellation reason, and the ABN's check digits.

Across the file

The same claim reference twice, and two lines with the same participant, item, dates and amount.

The NDIA's answer

The results file (or the error file from a failed upload): each rejected line with its code in plain English, where the fix lives, and a file of just those lines to correct and upload again under a new name.

What it can’t check. It can't check anything the NDIA holds: service bookings, plan dates and budgets, your registration groups, the participant's providers list, or the price limit for each item on the day. Those are behind most of the rejection codes, and only the portal can answer them.

In Corella

The file made for you, and the answer read back.

Corella generates the NDIA's 16-column bulk file exactly, and when you upload the NDIA's outcome file it records what each line was actually paid — paid, part-paid or rejected, with the NDIA's own reason — so just the rejected lines can be claimed again under a fresh reference. You still upload the file to the provider portal yourself.

Common questions

Straight answers.

Does my file get uploaded anywhere?
No. The file is read in your browser: it never leaves your browser, nothing is saved, and closing the page clears it. The files it makes for you — the blank template and the re-claim file — are built on your own computer too.
What are the sixteen columns in an NDIA bulk payment request?
RegistrationNumber, NDISNumber, SupportsDeliveredFrom, SupportsDeliveredTo, SupportNumber, ClaimReference, Quantity, Hours, UnitPrice, GSTCode, AuthorisedBy, ParticipantApproved, InKindFundingProgram, ClaimType, CancellationReason and ABN of Support Provider — in that order, with those exact names. AuthorisedBy, ParticipantApproved and InKindFundingProgram are left blank.
What date format does the NDIA accept?
The NDIA's guide accepts YYYY-MM-DD or DD-MM-YYYY, and its error messages all ask for YYYY-MM-DD. Excel rewrites dates when it re-saves a file, often to a one-digit day, so format the date columns last and check them before you upload.
Should I use Quantity or Hours?
One or the other on each line, never both. Hours are written H:MM with no leading zero — two and a half hours is 2:30. Quantity is a number; the guide's template allows up to three digits with two decimals, while its error table asks for a whole number, so if a decimal quantity comes back rejected, claim it in hours.
Some lines were rejected. Do I upload the whole file again?
No. The NDIA's guide says to make a new file with only the lines that failed, fix them, and upload it under a new filename — the portal won't take a name it has seen before. You can keep the same claim references. The re-claim file on this page does exactly that.
Why was a line rejected when the file passed this check?
Because most rejections are about things only the NDIA can see: the service booking, the plan's dates and budget, your registration, the price limit on the day. The rejection code tells you which, and this page explains each one.
Does Corella make this file?
Yes. Corella generates the NDIA's 16-column bulk file, and when you upload the NDIA's outcome file it records what each line was actually paid — paid, part-paid or rejected, with the NDIA's own reason — and lets you release just the rejected lines to claim again under a fresh reference. The file still goes to the provider portal by hand: Corella doesn't send claims to the NDIA.

Sources: Bulk payment requests: self-help guide for providers — NDIA, December 2025 · Bulk payment request template — NDIA · How to use the provider portals — NDIS. Read 25 September 2026.

Rather not build the file by hand? Book a walkthrough.

Thirty minutes on a live instance: the claim file built from an invoice run, and the NDIA's answer read back line by line.