Reconcile NDIA claim results

Upload the NDIA bulk results file, read the accepted and rejected lines, and void a batch.

Last updated · 3 July 2026

For an NDIA batch you do not record a payment by hand. Instead you upload the bulk payment results file from the NDIS, and the platform matches each line and records its outcome against the batch. This action is only available on NDIA batches, and only if your role has payments edit access.

The Upload claim results drawer for an NDIA batch after a results file is chosen, showing a summary grid of Matched, Accepted, Partial, Rejected and Unmatched counts, an Unmatched references list, a warning that existing outcomes will be overwritten, and an Import button. — 1 Choose the NDIA bulk results file. Only .csv files are accepted.
2 The file is matched against the batch: how many matched, then accepted, partial, rejected and unmatched.
3 Any unmatched references are listed so you can chase them up.
4 Import records each outcome; it is disabled when nothing matched.

Open Upload claim results

Go to Finance ›Payments , find the NDIA batch in the Invoice batches table, and select the Upload claim results (upload) icon in the Action column. The Upload claim results drawer opens.

Choose the results file

Select the NDIA bulk payment results file. Only .csv files are accepted, and a file larger than 10 MB is rejected with Results file is larger than 10 MB. Export the results file again and retry. If the file cannot be read, a Results file not recognised message appears.

Once the file is read, a summary grid shows how it matched against the batch:

Count	What it means
Matched	How many lines matched, shown as a count like 8 of 10.
Accepted	Lines the NDIA accepted in full.
Partial	Lines the NDIA paid only part of.
Rejected	Lines the NDIA rejected.
Unmatched	Lines in the file with no matching batch row. Their references are listed below the grid.

Each matched line comes back as accepted, partially paid or rejected. Below the grid, watch for:

Import warnings, for example a paid amount the platform could not read, or an NDIA line that paid more than the claimed amount. These do not block the import.
Existing outcomes will be overwritten, if this batch already has imported results.
N previously imported row(s) are missing from this file, listing rows that kept an outcome from an earlier import but are not in this file. They keep their existing outcome; re-export and re-import the full results file if this one is meant to supersede it.
Nothing to import, if no line in the file matches this batch. Check you have the right file.

Import the results

Select Import. The button is disabled when nothing matched. On success the toast confirms how many lines were recorded, splitting out partials, for example “6 accepted · 2 partial · 1 rejected recorded”, and the batch’s Status column shows the same accepted and rejected counts below its badge (with a partial count too, when there is one).

Note

Rejected lines need to be corrected and re-billed. Fix them from the finance register, then generate a fresh batch for the affected items.

Void a batch

If a batch was issued in error, select the Void batch (ban) icon in the Action column. A Void this batch? dialog explains that Rows return to billing and the batch is kept for audit. Recorded references are cleared. Confirm with Void batch. The rows return to the Billing register to be billed again, and a toast confirms how many rows returned to billing.

Watch out

Voiding is blocked once a batch has been actioned. The button is disabled, with the reason in its tooltip, when the batch is already void, when it has recorded payments and can no longer be voided, or when claim results have been imported for this batch and it can no longer be voided. You also need payments edit access to void.