What Happens When Some Claims in a Bulk Submission Are Rejected?

Only the rejected rows are affected — the rest of the bulk submission is processed and paid normally. The results file returned after processing shows a Success or Fail outcome for each individual line, so providers can identify exactly which claims failed without the entire batch being held up. Rejected rows are corrected and re-uploaded as a new, smaller file containing just those records.

How does partial rejection work within a bulk batch?

Each row in a bulk payment request is assessed independently against the same checks a single claim would face — plan funding, price limits, support item eligibility, claim details. A formatting or data error in one row doesn’t cascade to the rest of the file; the NDIA processes what it can and flags what it can’t.

What’s the process for fixing rejected rows in a batch?

Open the View Payment Request tile and locate the recent bulk upload.
Identify the Payment Request Number(s) showing an error.
Download the bulk upload file and correct only the affected rows.
Keep the same Claim Reference number for corrected rows where possible.
Save the corrected rows as a new CSV — don’t include the rows that already succeeded.
Re-upload using the bulk upload function.

Should a provider resubmit the entire batch if some lines fail?

No — resubmitting successful rows alongside corrected ones risks creating duplicate claims for the lines that already succeeded. Only the failed rows need to be included in the corrective upload.

What’s the difference between a rejected row and one held for review within a batch?

A row that’s rejected has failed a check and needs correction and resubmission. A row held for manual review is still pending a decision — it isn’t a failure, and every other row in the batch (including other successful ones) is still processed and paid on normal terms regardless of that one held line.