NDIS Payment Reconciliation: How to Match NDIA Remittance Against Your Claims

What is the myplace upload results CSV

After you upload a bulk payment request (BPR) to the NDIA myplace portal, NDIA processes the claims and returns a myplace upload results CSV. This is sometimes called the remittance advice or the payment response CSV.

The file contains one row per claim line from your original BPR. For each row, it shows: the provider claim reference you submitted, the NDIS participant number, the support item code, the service dates, the amount you requested, the amount NDIA approved, and a response code explaining any difference between the two.

The myplace upload results CSV is how you find out what NDIA actually paid, which lines were partially paid, which were rejected, and why. Without it, you are reconciling against bank deposits alone, which makes it impossible to identify which specific claims account for which payments.

When the payment response arrives

NDIA typically processes BPR submissions within two to five business days of receipt. The myplace upload results CSV becomes available in myplace once processing is complete. NDIA does not send a notification when it is ready -- you need to check myplace.

For organisations on a fortnightly billing cycle, you are typically checking myplace once per fortnight to download the results CSV, then running a reconciliation pass in your billing system.

The provider claim reference: why it matters

Every row in a BPR submission must have a unique provider claim reference -- a number or code that you assign to identify that specific claim line. This reference carries through from the BPR you submit to the payment response NDIA returns.

The reference is how the two files are matched. When you import the myplace upload results CSV into your billing system, the system looks for the provider claim reference in the results file and finds the corresponding line in your submitted BPR. If the references match, the line is reconciled automatically.

If references are not unique -- for example, if your billing system reuses reference numbers across billing runs -- the matching will fail or produce incorrect results. If references in the payment file do not appear in your billing system at all, those lines cannot be auto-matched and require manual investigation.

Teiro assigns a unique provider claim reference to each claim line automatically and preserves it from submission through to reconciliation. The reference does not change between the export and the import.

Why partial payments happen

A partial payment occurs when NDIA approves a lower amount than you submitted. There are two common causes.

Rate cap enforcement. NDIA applies the current NDIS Pricing Arrangements and Price Limits (PAPL) cap to submitted claims. If your submitted rate exceeds the cap -- whether because the SA was written before a Pricing Arrangements update or by error -- NDIA pays the cap amount, not your submitted rate. The response code on that line will indicate the rate adjustment.

Plan funding exhausted. If the participant's funding bucket for a support category is empty, NDIA will pay zero for lines that exceed the remaining balance. This can affect one line (the last before the bucket empties) with a partial amount, and all subsequent lines in the same category with zero. The response code indicates a funding limit has been reached. Note: budget tracking and near-limit warnings in Teiro currently apply to agency managed lines. For plan-managed and self-managed participants, budget visibility is managed through the plan manager or participant directly.

Partial payments require a decision: write off the difference, adjust the SA rate, or -- in the case of funding exhaustion -- work with the participant and their plan manager to understand whether additional funding is available or whether service delivery needs to be scaled back.

What manual reconciliation actually costs

For organisations that reconcile without software support, the workflow looks like this: download the myplace upload results CSV from myplace, open it alongside the original BPR in a spreadsheet, sort both files by provider claim reference, check each row for amount matches, and flag any discrepancies for follow-up. For each flagged row, open the participant record and the relevant billing run to understand the context.

For an organisation with 50 active agency managed participants, a fortnightly billing cycle produces approximately 200 to 400 claim lines per run. Manual reconciliation of a run this size, done carefully and with proper documentation of discrepancies, takes between three and five hours. On a fortnightly cycle, this is six to ten hours per month on reconciliation alone.

The error rate in manual reconciliation is not trivial. Rows that are mismatched or skipped under time pressure become aged unreconciled claims that accumulate over months. Discrepancies that are not investigated promptly are often unrecoverable -- the window for querying a payment with NDIA closes, and the write-off is larger than it needed to be.

How automated reconciliation works in Teiro

When you import the myplace upload results CSV into Teiro, the system:

1. 1.Reads each row in the payment file
2. 2.Looks up the provider claim reference in your billing runs
3. 3.Marks matched lines as reconciled if the paid amount matches the submitted amount
4. 4.Flags lines where the paid amount differs from the submitted amount, with the discrepancy amount and the NDIA response code visible in the review queue
5. 5.Lists any lines in the payment file with no matching claim reference in Teiro for manual investigation

The reconciliation pass for a 200-line run takes a few minutes to import and process. The billing officer then reviews the flagged lines -- partial payments and unmatched references -- which typically represent five to fifteen percent of lines in a well-run operation.

What to do with anomalies

Partial payment: rate cap applied. Check whether your SA rate is above the current Pricing Arrangements cap for this support item. If it is, update the SA rate. The shortfall for this claim cannot be recovered from NDIA, but future claims will submit at the correct rate.

Partial payment: funding exhausted. Review the participant's remaining budget. If the plan year is not yet over, the participant may be eligible for a plan review to increase funding. If the plan year is ending, understand what services can continue to be delivered within the remaining budget.

Zero payment: claim rejected. Review the response code. Common rejection reasons include: incorrect participant NDIS number, duplicate transaction reference, support item code retired or incorrect, and claim outside the participant's plan dates. Each has a specific fix. See NDIS Bulk Payment Requests: Why Batches Reject for a full breakdown.

No match in billing system. A line in the results file with no matching claim reference in Teiro means either the claim was submitted from a different system or the reference was altered between submission and response. Pull the original BPR from myplace and compare it against what Teiro exported to find where the mismatch occurred.

Book a demo to see Teiro's reconciliation workflow, or sign up free for organisations with 5 or fewer active users.