NDIS Rejection Codes

Restricted documentation: This article relates to Native NDIS claiming and is intended for authorised quickclaim customers.

NDIS rejection codes explain why a submitted claim or payment request was not accepted.

Public APIs cannot submit NDIS claims. Rejection codes therefore primarily apply to claims submitted through the Native Payments API.

Rejections and HTTP errors

An HTTP error and an NDIS claim rejection are not the same.

• An HTTP error indicates that the API request could not be completed normally.
• An NDIS rejection means the claim was received and assessed but was not accepted.

A successful HTTP response does not guarantee that the claim was accepted. Your integration must also review the claim status, rejection code and rejection description.

Get the current code list

Rejection codes and descriptions can change. Use the Native Reference Data 3.0 API to retrieve the current reject_reason_codes.

Download the Reference Data 3.0 YAML specification

Use the retrieved Reference Data as the source of truth. The codes below are common examples and are not a complete replacement for the API response.

Common rejection codes

Code	Meaning	Recommended action
A01	Payment request rejected	Review the full response for a more specific reason
C03	Support dates are outside the service booking dates	Correct the service dates or select the correct service booking
C15	Provider is not registered for the support item	Confirm the provider’s registration groups and the support item
C27	Claims cannot be made for a future date	Wait until the support has been delivered and use valid service dates
C28	Claim is outside the participant’s plan dates	Correct the service dates or confirm the applicable plan
C38	Submitted price exceeds the support catalogue limit	Correct the rate using the applicable pricing arrangement
C39	Claim exceeds the permitted submission timeframe	Review whether the claim can still be submitted and contact the NDIA if required
P01	Amount exceeds the available service booking amount	Review the booking balance and claimed amount
P03	Amount exceeds the participant’s available budget	Review the participant’s budget and claimed amount
P04	A payment request already exists with the same details	Check claim history and do not submit a duplicate
R03	Reversal exceeds the original payment request amount	Confirm the original claim and reduce the reversal amount
S01	No matching plan was found for the NDIS number	Confirm the NDIS number, participant details and plan
V04	The claim was identified as a duplicate	Review claim history before taking further action
V11	Provider relationship is not valid for the support category or dates	Review the participant’s My Providers relationship
V13	The support category’s management type cannot be claimed by the provider	Confirm the plan-management type and claimant
V16	The selected support item has no available funding	Review the support item and participant budget
V17	The plan budget has insufficient funds	Review the available budget before resubmitting
V26	Support dates cross more than one plan	Split the claim so each request falls within one plan
V27	The applicable funding period has insufficient funds	Review the funding-period balance and claim dates
V31	The unit price exceeds the NDIS price limit	Correct the unit price using the applicable price limit
V36	Support dates fall outside the participant’s plan	Correct the dates so they fall within one plan period
V43	The support is agency managed for the claim period	Confirm that the correct provider and claiming method are being used

Always use the rejection code and description returned for the specific claim. Similar codes can require different actions depending on the participant, plan, support and service dates.

Investigate a rejected claim

1. Record the Payment Request Number and your original claim reference.
2. Record the claim status, rejection code and rejection description.
3. Retrieve the current rejection-code definition through Reference Data.
4. Review the participant, plan, support item and service dates.
5. Check the available budget or service booking where applicable.
6. Confirm provider registration, authority and participant relationships.
7. Correct the underlying issue before resubmitting.
8. Retain the original and replacement references for reconciliation.

Before resubmitting

Do not automatically resubmit every rejected claim.

Before resubmitting:

• Confirm that the original claim was rejected and not accepted or still processing.
• Correct the field or condition that caused the rejection.
• Check that the replacement will not create a duplicate.
• Preserve the relationship between the original and replacement requests.
• Review any claim-type or reversal requirements.

For duplicate codes such as P04 or V04, investigate the existing claim rather than submitting another request.

When to contact quickclaim

Contact support@quickclaim.io when:

• The code is not returned by Reference Data.
• The API response is missing the rejection description.
• The result does not match the submitted request.
• You need help confirming whether a request reached the NDIS.
• You are unsure whether it is safe to resubmit.

Include:

• Organisation ID
• quickclaim version
• Payments API version
• Payment Request Number
• Claim or batch reference
• Rejection code and description
• Request date and time

Do not include API keys, secrets or unnecessary participant information.