How to Read a myplace Upload Results CSV
An annotated guide to every column in the myplace upload results CSV -- what "Payment Amount vs Requested Amount" means when they differ, what response codes mean, and how to find the original claim line.
What the myplace upload results CSV is
When NDIA processes a bulk payment request (BPR), they return a myplace upload results CSV via the NDIA myplace portal. This CSV file contains one row per claim line from your original submission, with NDIA's decision on each line: how much was approved, how much was paid, and -- if the two differ -- why.
This is a reference article. It explains each column in plain English so you can read the file and understand what each row is telling you.
Column by column
Registration Number
Your organisation's NDIS provider registration number. This should match the registration number in the header of your original BPR submission. If it does not match, the file may have been returned for the wrong provider.
Participant NDIS Number
The NDIS number of the participant this claim line relates to. Use this to find the participant record in your billing system when investigating a discrepancy.
Supports Delivered From / Supports Delivered To
The service date range for this claim line, as submitted in your BPR. Confirm these match your shift records. If NDIA has applied a rate cap or rejected a line, check whether the dates correspond to the correct plan year and SA period.
Support Item Number
The NDIS support catalogue item code for this claim line (for example, 01002010711 for Assistance with Daily Life activities). Verify this matches the support item code you submitted. NDIA occasionally returns lines with a corrected item code if the submitted code was retired or superseded, though this is rare.
Claimed Amount
The amount you submitted for this line in your original BPR. This is your figure, not NDIA's.
Payment Amount
The amount NDIA approved and paid for this line. When Payment Amount equals Claimed Amount, the line was paid in full. When Payment Amount is less than Claimed Amount, NDIA has reduced the payment -- see the Response Code column for the reason.
Response Code
The most important column when investigating a discrepancy. Common response codes:
- Successful. The claim was approved and paid in full.
- Rate greater than price limit. NDIA reduced the payment to the current Pricing Arrangements cap. Your submitted rate exceeded the cap.
- Insufficient funds. The participant's funding for this support category was exhausted. Zero or partial payment.
- Duplicate transaction. NDIA has already paid a claim with this provider claim reference. Do not resubmit.
- Participant not found. The NDIS participant number on this line does not match any active participant in NDIA's system. Check the participant number on your record.
- Claim outside plan dates. The service date falls outside the participant's current plan period. The SA must align with the plan dates.
- Invalid support item. The support item code is not valid in the current NDIS support catalogue. The code may have been retired.
- Registration group mismatch. Your provider registration does not cover the registration group required for this support item.
Provider Claim Reference
The unique reference number you assigned to this claim line in your BPR submission. This is the key you use to match the payment response row back to the original claim line in your billing system. If you are reconciling manually, sort both your BPR and the payment response by this column and compare row by row.
If the provider claim reference in the results file does not appear in your billing system, the claim was either submitted outside your current system or the reference was altered between export and upload.
Worked example: one participant, one billing period
Imagine a participant (NDIS number 430100001234) with an agency managed plan. You submit three claim lines for a fortnightly period:
- Line A: Support Item 01002010711, 10 hours at $65.09, Claimed Amount $650.90, Provider Claim Reference TRO-2026-0041
- Line B: Support Item 01004010711, 3 hours at $91.53, Claimed Amount $274.59, Provider Claim Reference TRO-2026-0042
- Line C: Support Item 04104012561, 1 session at $193.99, Claimed Amount $193.99, Provider Claim Reference TRO-2026-0043
The payment response returns:
- TRO-2026-0041: Payment Amount $650.90, Response Code Successful. Paid in full.
- TRO-2026-0042: Payment Amount $271.50, Response Code Rate greater than price limit. NDIA applied a Pricing Arrangements cap of $90.50 per hour. You will receive $271.50 rather than $274.59. The $3.09 difference cannot be recovered from NDIA. Update your SA rate for this support item.
- TRO-2026-0043: Payment Amount $0.00, Response Code Insufficient funds. The participant's capacity building budget was exhausted. Contact the participant's support coordinator to discuss a plan review.
This example shows how a single submission can produce three different outcomes. The provider claim reference is what connects each response row to the corresponding shift and SA line in your billing system.
What to do with rejected lines
A rejected line (Payment Amount of zero, non-Successful response code) should not be resubmitted with the same data. NDIA rejected it for a reason. The correct process is:
- 1.Read the response code to understand the reason
- 2.Fix the underlying issue -- incorrect participant number, retired support item code, rate above cap, expired plan dates
- 3.Resubmit a corrected line in the next BPR
Resubmitting the identical line produces the identical rejection. The fix must happen in your billing system first, so the corrected data flows through to the next export.
For a full breakdown of batch and line-level rejection reasons, see NDIS Bulk Payment Requests: Why Batches Reject.
Book a demo to see how Teiro handles payment response import and reconciliation, or sign up free for organisations with 5 or fewer active users.