An AVETMISS readiness checklist before you export
The gaps that most often cause validation errors, and how Academywise surfaces and fixes them before your NAT files are generated.
Most AVETMISS problems aren’t caused by the export itself. They’re caused by data that was incomplete when it was entered months earlier. The best time to find them is before you generate your NAT files, not when the validator rejects them.
This checklist follows the readiness checks built into Academywise. For the authoritative rules, refer to NCVER’s AVETMISS documentation.
1. Programs (NAT00030)
Each qualification needs its national code, AQF level, field of education, ANZSCO occupation code, nominal hours and VET flag.
In Academywise: qualifications are imported from training.gov.au with ANZSCO, ASCED and level classification filled in automatically. training.gov.au doesn’t publish nominal hours, so those are entered once per course, and the readiness dashboard flags any that are missing.
2. Subjects (NAT00060)
Units need a field of education (six-digit) and nominal hours.
In Academywise: unit details come from training.gov.au and the readiness dashboard lists units without hours so they can be fixed inline.
3. Clients and USIs (NAT00080, NAT00085)
Every student needs complete demographic and address details, and a valid USI unless an exemption applies.
In Academywise: every USI is checked for format and check digit, with exemptions recorded as INTOFF or INDIV. The readiness dashboard lists students with missing or invalid USIs. Verification against the national USI Registry is built, but is in development pending government B2B access.
4. Enrolment activity and outcomes (NAT00120)
Each unit enrolment needs start and end dates, an outcome and an outcome date for final results, plus funding source codes.
In Academywise:
- Activity dates come from the timetable unless a staff member enters manual dates, and manual dates take priority.
- Final outcomes require an outcome date.
- RPL and credit transfer approvals write outcome 51 and 60 automatically.
- National and state funding codes resolve from the delivery campus’s state and student type, with per-unit and per-activity overrides.
5. Completions (NAT00130)
Completed qualifications need to be recorded with their completion date.
6. Run the validation-aware export
Academywise applies a set of NCVER AVS validation rules locally, covering USI uniqueness, funding source and location combinations, postcode and state rules, and future-dated activity. It then produces the ten NAT files as a ZIP. Every run is logged with its period and counts.
For state reporting, the AVETMISS for State export narrows the national dataset by state, venues, cadence and claimable status, and can exclude withdrawn and credit-transfer activity.
Looking ahead: VET Data Streamlining
National reporting is moving to the VET Information Standard and STARS. Academywise’s reporting dataset is transport-neutral: the same data that builds NAT files feeds a STARS mapper with local pre-validation. STARS submission is in development. Keep an eye on NCVER’s VET Data Streamlining updates for official timelines.
This guide describes how Academywise works and is general information only. It isn't legal or compliance advice. Always confirm your obligations with the official sources linked above.