NDIS Bulk Payment Requests: Why Batches Reject and How to Fix Them

Two types of rejection: batch-level and line-level

When you upload a bulk payment request (BPR) to the NDIA myplace portal, there are two ways the submission can fail.

A batch-level rejection means the entire file was rejected before NDIA processed any individual lines. myplace returns an error immediately on upload. None of your claims have been processed. You need to fix the file and resubmit the whole thing.

A line-level rejection means the file was accepted and processed, but one or more individual claim lines were declined. The rest of the submission may have been paid. You identify line-level rejections through the myplace upload results CSV, where the affected lines have a non-Successful response code and a zero or reduced Payment Amount.

Understanding which type of failure you are dealing with determines what you need to fix.

Batch-level failures

Wrong ABN in the header

The BPR file format requires your organisation's ABN in the header row. If the ABN in the file does not match the ABN registered to your NDIS provider account in myplace, the batch is rejected before any lines are processed.

Fix: Confirm your registered ABN in myplace under your provider profile. Update the ABN in your billing system's organisation settings. Regenerate the BPR export and resubmit.

Incorrect provider registration number

Similar to the ABN, the provider registration number in the file header must exactly match your registered number. Leading zeros matter. Transpositions matter.

Fix: Check the exact format of your registration number in myplace and compare it to what your billing system is inserting into the file. Correct the configuration in your billing system and regenerate.

Date format errors

The BPR format requires dates in a specific format (typically DD/MM/YYYY). If your billing system exports dates in a different format (MM/DD/YYYY, YYYY-MM-DD, or with different separators), myplace may reject the batch.

Fix: This is a configuration issue in the billing software. The export should handle date formatting automatically. If you are seeing this error from a Teiro export, contact support -- this indicates a formatting regression in the export module.

File encoding issues

The BPR file must be saved in a specific character encoding (typically UTF-8 without BOM, or a Windows encoding myplace accepts). Files edited in Excel and re-saved sometimes acquire a Byte Order Mark (BOM) or change encoding, which can cause myplace to reject the file.

Fix: If you are modifying the CSV file in Excel before uploading, stop. Upload the file exactly as exported from your billing system. If myplace is rejecting an unmodified Teiro export on encoding grounds, contact support with the error message.

Support item codes from an old catalogue version

NDIA updates the NDIS support catalogue periodically. Support item codes that were valid in a previous catalogue version are sometimes retired or renumbered. A BPR that includes retired item codes may be rejected at the batch level or produce line-level rejections. The current support catalogue is published alongside the NDIS Pricing Arrangements and Price Limits.

Fix: Check the current NDIS support catalogue on the NDIS website. Compare the item codes in your service agreements against the current catalogue. Update any SA line items that reference retired codes before generating the next BPR.

Line-level failures

Participant number mismatch

The NDIS participant number on a claim line does not match any active participant in NDIA's system. This happens when participant numbers are entered incorrectly, when a number has changed (rare but possible after administrative corrections), or when the participant's plan has ended and they are no longer an active NDIA participant.

Fix: Verify the participant's NDIS number directly with the participant or their nominee. Correct the number in the participant record in Teiro and regenerate the affected lines in a new BPR.

Duplicate transaction reference

A claim line with the same provider claim reference was already submitted and paid in a previous BPR. NDIA will not pay the same reference twice.

Fix: Do not reuse provider claim references across billing runs. If a line was genuinely not paid in the previous run (check the payment response), the error may indicate a reference collision -- the same reference was used for two different claim lines. Teiro assigns unique references automatically; if you are seeing this error from a Teiro export, contact support.

Amount over Pricing Arrangements cap

The submitted rate for this support item exceeds the current NDIS Pricing Arrangements and Price Limits cap. NDIA will pay the cap amount, not the submitted amount. This appears as a partial payment in the payment response, not a full rejection.

Fix: Update the service agreement rate for this support item to the current Pricing Arrangements cap. The amount over the cap cannot be recovered. Future claims will submit at the correct rate.

Invalid support purpose

The support category claimed does not match the registered support purposes for your organisation, or the participant's plan does not fund this support category.

Fix: Check whether your provider registration covers the support registration group required for this support item. If your registration does not cover it, you cannot claim it. If your registration covers it but the participant's plan does not fund it, the service cannot be billed under NDIS.

How to isolate which lines caused a partial batch rejection

When myplace accepts your file but returns partial payments, the myplace upload results CSV is your diagnostic tool. Download the results CSV and filter for lines where the Response Code is not "Successful." The remaining rows are your problem lines.

For each non-Successful line:

1. 1.Note the Provider Claim Reference and Response Code
2. 2.Look up the claim line in Teiro using the reference
3. 3.Identify the specific issue from the response code
4. 4.Fix the underlying data (participant number, SA rate, support item code)
5. 5.Include a corrected version of the line in your next BPR

Do not include corrected lines in the same BPR as new claims if this is avoidable. A separate resubmission for corrected lines makes the audit trail cleaner.

A note on Teiro and the myplace upload step

Teiro generates the BPR CSV and you upload it manually to the NDIA myplace portal. Teiro does not submit directly to NDIA. This means myplace's error messages are what you see when a batch fails -- Teiro does not receive or process these errors automatically.

When a batch-level rejection occurs, note the exact error message from myplace before closing the window. This is the information you need to diagnose and fix the issue. Teiro's support team can assist with interpreting myplace error messages if needed.

Book a demo to see Teiro's BPR export in practice, or sign up free for organisations with 5 or fewer active users.