This indicates that a valid API Key was not provided in your request.
Resolution
Refer to the Authentication section for details on how to include your API key correctly. Ensure your x-api-key header is present and valid in every request.
A required field is missing from your request. The reason field in the response provides exact details about the missing field name enclosed in single quotes.
Example: "Reason": "The 'PrincipalProviderNumber' field is not provided."
Resolution
Include the missing field in your request and try again.
Both referral details (such as referring provider number) and a referral override code (e.g. N – Not required) were included in the same request. Medicare only allows one.
Resolution
Include either referral details or a referral override code — not both.
The combination of ReferralTypeCode and ServiceTypeCode does not meet Medicare’s validation rules.
Resolution
Confirm both values exactly match one of the valid MBS combinations.
The Referral Issue Date is invalid — it may be in the future, after the service date, or before the patient’s date of birth.
Resolution
Ensure the referral issue date:
The provider number does not follow the required Medicare format.
Resolution
Provider numbers must be 8 characters in the format: 6-digit stem + 1 location character + 1 check digit
Example: 123456A7
The referring provider number matches the servicing provider number. Medicare requires different provider stems for each.
Resolution
Use a referring provider number with a different 6-digit stem from the servicing provider’s number.
A hospital-related referral override code (H) was provided, but required hospital fields were not included.
Resolution
If ReferralOverrideCode is H:
HospitalIndicator to YFacilityIDThe Service Date is in the future or outside Medicare’s permitted timeframe.
Resolution
Ensure the service date:
The Medicare card number or IRN (Individual Reference Number) is invalid.
Resolution
A Collection or Accession timestamp was provided without its corresponding value.
Resolution
If either CollectionDateTime or AccessionDateTime is provided, both must be included.
Medicare rejected the transaction due to missing or invalid dependent fields, or incomplete data required for claim validation.
Resolution
Review the reason or errorDescription field in the response for specific details.
An interactive patient claim contains more than 16 Medical Events.
Resolution
A Medical Event contains more than 14 services.
Resolution
The claim contains more than 16 services overall.
Resolution
One or more Medical Event IDs are duplicated or not in the correct sequence (01–16).
Resolution
A Service ID is repeated within the same claim.
Resolution
Ensure all Service IDs are unique within the claim.
The Account Paid Indicator is not Y or N, or is inconsistent with EFT details.
Resolution
Y (paid) or N (not paid)AccountPaidIndicator = YThe Account Reference ID contains invalid characters or is the wrong length.
Resolution
0-9, A-Z, a-z, @ # $ % + = : ; , . -Referral PeriodCode, Period, or TypeCode is missing or inconsistent.
Resolution
The claim cannot be submitted digitally because SubmissionAuthorityInd is missing or invalid.
Resolution
Set SubmissionAuthorityInd = Y to indicate the claimant authorised digital submission.
Still stuck? Reach out to the RebateRight team at support@rebateright.com.au — we’re happy to help.