Claiming, payment requests, and why claims get rejected

How claiming works

NDIS claiming is the process by which a provider requests payment from the NDIA (or from a plan manager, for plan-managed participants) for supports already delivered official source (opens in a new tab) . A claim is not a quote or an invoice in the traditional sense: it is a payment request submitted after the support has been delivered, matched to a specific support item code, participant, service booking, and date.

For agency-managed participants, payment requests go directly to the NDIA through the myplace provider portal or via bulk upload. For plan-managed participants, you invoice the participant’s plan manager, who then submits the claim to the NDIA on your behalf. Self-managed participants pay you directly from their own funds and handle the claiming themselves.

Making a payment request

To make a payment request you need several pieces of information: the participant’s NDIS number, the relevant service booking or plan period, the correct support item number , the quantity delivered (in the correct unit for that item), the date of delivery, and the amount being claimed official source (opens in a new tab) . Each of these fields must be accurate. The portal validates the claim against the participant’s current plan, checking that the item code is valid, the budget category has sufficient funds, and the date falls within the plan period.

Payment requests can be submitted individually through the portal interface or in bulk using a CSV upload for high-volume providers. Either way, the same validation rules apply, and errors appear as rejection messages that identify which field caused the failure.

Common reasons claims fail

Several patterns account for the vast majority of rejected claims. Understanding them helps you catch errors before submission rather than after.

Wrong support item code. Using a code that does not match the support delivered is the most common cause of rejection. This often happens when a provider copies a code from a previous claim without checking whether it is the right one for the current support type or time of day. Always verify the code against the current support catalogue before claiming.

Insufficient budget. If the participant does not have enough funds remaining in the relevant budget category for that claim, the request will fail. Budget depletion can happen faster than expected if other providers have claimed against the same budget, or if the participant’s plan is nearing its end date.

Stated-support mismatch. Some supports in a participant’s plan are stated , meaning the funding is locked to a specific support type or provider and cannot be used for anything else. Claiming against a stated-support budget with a different support item code, or as a different provider than the one named, will result in rejection.

Claim outside plan dates. Supports must be delivered and claimed within the participant’s plan period. A claim with a service date before the plan start or after the plan end will be rejected, even if the participant was otherwise eligible and the support was legitimate.

Fixing and resubmitting

Most rejected claims can be corrected and resubmitted once you identify the cause of the failure official source (opens in a new tab) . The rejection message in the portal will usually indicate which field triggered the error. Common fixes include: selecting the correct support item code, checking the participant’s remaining budget and plan dates, confirming with the participant or plan manager whether a stated support applies, and correcting the quantity or unit of measure.

If the rejection is due to budget exhaustion, the participant may need to contact the NDIA about an unscheduled plan review before you can claim. In that case, document the support delivery accurately and preserve the records until the budget situation is resolved.

Records to keep

Providers are required to keep records that support every claim they make official source (opens in a new tab) . At a minimum, records should document: what support was delivered, when and for how long, who delivered it, which participant received it, and that the participant consented to and received the support. Progress notes, shift records, and signed timesheets all serve this purpose.

Good records serve two functions: they justify the claim if the NDIA audits your payment requests, and they form part of your compliance obligations under the NDIS Practice Standards. Keep records for at least the period required by the NDIS rules, and store them securely given the sensitive nature of participant information.