FAQs: NDIS Suffix Codes (_CA, _CA2, _NF, _NF2, _PT, _TH, _RR)

This article answers frequently asked questions about how NDIS suffix codes and special claim types are used by Support Coordinators and Allied Health Professionals within Careview.

What has changed?

From 1 July 2026, the NDIA introduced suffix codes for specific NDIS support items to show exactly how a service was delivered or claimed. A base support item may now feature related suffixes for Non-Face-to-Face (_NF), Telehealth (_TH), Provider Travel (_PT), NDIA Requested Reports (_RR), or Short-Notice Cancellations (_CA).

On 3 July 2026, the NDIA introduced additional numbered suffixes, including _NF2 for Non-Face-to-Face and _CA2 for Short-Notice Cancellations.

Careview automatically determines the correct suffix to apply to your claim or invoice based on the Contact Type selected in your Allied Health or Support Coordination case notes.

Do I need to create separate Service Supports for each suffix?

No. Do not create separate Service Supports or Stated Supports for suffix items. Continue to set up the base support item on the service contract. Suffix items are used when recording the delivered service, invoice line, Streamline line, bulk invoice line, or applicable case note.

Where do I set up the suffix?

The suffix can be set up in the Note Contact Type Settings. Please refer to the user guide Create a Case Note Contact Type for details.

Which suffix should I select?

Contact type purpose	Claim Type	Suffix
Standard or direct service	STAN	No Suffix
Non-Face-to-Face	NF2F	_NF, _NF2
Telehealth	THLT	_TH
Provider Travel	TRAN	_PT
NDIA Requested Report	REPW	_RR
Cancellation - no show due to health reason	CANC - NSDH	_CA, _CA2
Cancellation - no show due to family issues	CANC - NSDF	_CA, _CA2
Cancellation - no show due to unavailability of transport	CANC - NSDT	_CA, _CA2
Cancellation - other	CANC - NSDO	_CA, _CA2

The suffix must match the Claim Type. For example, use _NF with NF2F, not with a cancellation claim type.

Should I add the suffix to the Description?

The suffix does not need to be added to the Description field for Careview to apply the suffix behavior.

The Description field is used to help your team identify the contact type. You can use any clear description that makes sense for your organisation, especially where you have more than one suffix for the same type of claim, such as _NF and _NF2 or _CA and _CA2.

To apply the suffix behavior, select the correct value in the suffix field when setting up the Note Contact Types in your settings.

How do suffix items work for Plan Management invoices?

When entering a Plan Management invoice line, select the applicable suffix item number where required, such as _NF, _PT, _TH, _RR, _CA, _NF2, or _CA2. Careview will use the matching base support item or stated support item when required from the service contract for funding validation, while keeping the suffix item number for the delivered service and claim output.

What if a plan has a Service Support or Stated Support?

If a plan has a Service Support or Stated Support for the service, it should be set up using the base support item, not a suffix item. Suffix items such as _CA, _NF, _PT, _RR, _TH, _CA2, and _NF2 should be selected when recording the delivered service, invoice line, Streamline line, bulk invoice line, or applicable case note. Careview will use the matching base Service Support or Stated Support for funding validation, while retaining the suffix item for claim/output purposes.

What if a support item does not have a suffix item?

Not every NDIS support item has suffix items.

Careview only applies a suffix if it officially exists in the NDIS catalogue for that specific base item. If there is no suffix for that code, Careview will automatically default to the standard base item and process your claim normally. The system will never generate an invalid code.

When does Careview start using suffix item numbers?

Suffix item numbers apply to delivered service dates on or after 1 July 2026.

Case notes with a delivered date before 1 July 2026 continue to use the standard support item numbers without the suffix.

Do I need to update old case notes?

No, you do not need to update old case notes just because the suffix field has been added.

Review and update the Note Contact Types your team will use for new case notes delivered on or after 1 July 2026.

How do I apply the 50% Provider Travel rate for these support items with suffix?

To apply the 50% rate, simply use the standard base item and tick the Claim travel at 50% rate checkbox when entering your Provider Travel (_PT) entry. Careview will automatically apply the 50% rate to the provider's travel time.

Do regional rates still apply?

Yes. Rates are determined based on the service region set on the participant's profile, or by the additional CoS rates apply setting on the service support item itself.

What should I review before creating claims or invoices?

Review each Note Contact Type used for billable Support Coordination case notes.

Recommended setup:

Keep standard/direct-service contact types with No Suffix.
Set up separate contact types for Non-Face-to-Face, Telehealth, Provider Travel, NDIA Requested Report, and Cancellation if your team uses those claim types.
Make sure each contact type has the matching Claim Type and Suffix.
Avoid mixed-use contact types where the same contact type could mean different claim types.
Create a test case note and check the claim or invoice preview before processing a live batch.

What should I check in the claim or invoice output?

For a suffix contact type, check that the output shows:

The support item number with the expected suffix, such as _NF, _NF2, _TH, _PT, _RR, _CA or _CA2.
The matching suffix item description.
The expected rate for the delivered date and region.
No suffix on standard/direct-service case notes.

If the suffix is not shown, confirm that the selected base Service Support has a matching suffix item in the current NDIS support catalogue.