AVETMISS 8.1: the funding identifiers RTOs should prepare for

AVETMISS Release 8.1 applies to activity from 1 January 2027. Two Specific Funding identifiers now need attention from RTOs and student management system vendors.

The AVETMISS Data Element Definitions edition 2.4 defines code 71 for the Free TAFE waiver. When that identifier is used, Funding source, national must be code 11.

NCVER's Specific Funding Identifier system file, revised 30 June 2026, also publishes code 75 for the Advance Entry Trades Training Program. Its effective period runs from 1 July 2026 to 30 June 2028.

These are substantive data rules. A system that does not recognise the identifiers can reject valid funded activity or produce an invalid return.

Code 71 is more than a new dropdown option

The Free TAFE identifier carries a relationship to another reported field. A conforming system needs to validate the pair:

• Specific Funding Identifier 71; and
• Funding source, national 11.

Adding the label without the cross-field rule is incomplete. The relationship should be checked when the record is entered and again when NAT00120 is generated.

Code 75 is already effective

Code 75 started on 1 July 2026. Its published end date is 30 June 2028.

That means a reference list needs effective dates, not only a set of values. A code can be valid for one activity period and invalid for another. Collection-year-aware validation is the safer model as Release 8.0 and Release 8.1 overlap in system development and historical reporting.

There is a source inconsistency to resolve

The current Specific Funding text file lists code 75, but it does not list DED edition 2.4's code 71.

Both are current NCVER publications. A software vendor should not silently pick one and discard the other. The safe sequence is to retain both sources, seek clarification from NCVER, record the answer, and then publish a reviewed versioned classification set.

What RTOs should ask their software supplier

Before 2027 activity begins, ask whether the system:

1. selects AVETMISS rules by collection year;
2. supports Specific Funding Identifier 71 and its funding-source relationship;
3. supports code 75 with its published effective dates;
4. validates the fields before export; and
5. has tested representative files through AVS and any relevant funded-program pathway.

RTOs should continue using the rules applicable to the activity and reporting period. Do not apply a 2027 identifier early merely because it appears in a future specification.

RTObase is tracking this as a reviewed reporting change. We will only claim Release 8.1 readiness after the source inconsistency is resolved and the versioned rules have passed representative validation.

This article is a general operational summary, not legal advice. Confirm reporting treatment against the linked NCVER sources and the requirements of the relevant funding authority.