It’s that time of year again — time to collect, store, validate, identify, and fix errors before exporting your RTO data to NCVER. Often the most frustrating step can be identifying and fixing errors, and even the most highly trained administrator can succumb to validation errors.
Winter may have gone but AVETMISS reporting is here. To ease your concerns and support you in the upcoming weeks, we’ve collated a list of the top 5 common AVETMISS reporting errors and their solutions.
To bypass this error, exclude all state-managed training via your Student Management System before uploading and validating your data, ensuring you’re only submitting your Fee-For-Service (FFS) to NCVER.
There are two ways to go about this:
1. Prepare two separate submissions — submit your state managed data to your State Training Authority (STA), and your FFS training data to NCVER.
2. Create a combined submission for your STA (unfortunately this option is not valid for RTOs based in WA, NSW or QLD).
This error occurs when Activity End Date is set to a date after the Collection Year End Date. To resolve this issue, select Outcome Identifier-National which is represented by the number 70.
To circumvent an invalid USI format error, verify all USIs prior to reporting here.
If you’re still receiving an error, check the following:
This error occurs when the program name in your AVETMISS data for Program Identifier does not match the program name listed on training.gov.au. Make sure the program name in your NAT00030 file is identical to the program name listed on www.training.gov.au.
As with the error above, subject name in NAT00060 files and subject identifier in NAT00120 files must be identical to the data listed on TGA. Begin by searching your program on here and use the subject name and subject identifier outlined.
Remember, there’s always support available through NCVER.
Phone: 08 8230 8400
Toll-free phone: 1800 649 452
Or submit a request here.
VET moves fast. Stay informed, with blogs straight to your inbox.