Book a demo
Menu
AVETMISS reporting

Your NCVER report, built from the records you already keep.

RTO Grow builds all ten NAT files to AVETMISS 8.0 straight from your student records. Problems are flagged long before you build, and every file is checked before you lodge.

Book a demoStart a free trial

All ten NAT files · Built to AVETMISS 8.0 · Checked against 69 rules before you lodge

“Replaced 8 systems.”
DoraCompliance Manager · Full Tilt Training Solutions
What you get

Everything your report needs, on one page.

All ten NAT filesBuilt to AVETMISS 8.0 for the VET Provider collection
Held listStudents grouped by the reason they're held
Pre-flight checkEvery missing detail counted and linked
69-rule check12 for the files, 57 for each record
USI checks"Verify all" checks the USI Registry
Lodgement recordEvery build saved and filed in your Evidence Registry
How it works

Clear, check, build, lodge.

  1. 1Clear the held list"Verify all", "Chase all" and "Release all" clear each group.
  2. 2Pick the periodChoose the collection year and period, or set your own dates.
  3. 3Check who's in"Who is in this build" shows every student and field with its NCVER code.
  4. 4Validate and buildClick "Check", fix any errors, then build your NAT files.
  5. 5Lodge and recordUpload the ZIP at NCVER's AVS portal and click "Recorded as submitted".

See your report built.

From the held list to a ZIP ready for NCVER's AVS portal.

Held list

Everyone ready before you build.

Students who aren't ready to report sit on a held list, grouped by the reason. Click "Verify all" to check USIs against the USI Registry, "Chase all" to email every student who needs one, or "Release all" once they're verified. Imported history is only reported when you say so.

USIOn file, not checkedVerify all
No USIEmail every student who needs oneChase all
VerifiedVerified but not releasedRelease all
Staff holdHeld on purpose, each with a reasonHeld
ImportedRecords from your old systemHeld
Who is in this build

See exactly who's in the build.

"Who is in this build" shows every student and every field with its NCVER code, before anything is built. Need to keep a student out for now? Untick them and give a reason. It goes on their history, and you release them later, again with a reason.

Untick a student, with a reasonHeld, reason on their history

69-rule check

Validated before you lodge.

Click "Check" and RTO Grow checks your data against 69 rules. Errors stop the build until they're fixed. Warnings you can acknowledge and go ahead. Fix an error without leaving the page: click "Quick fix" on the row, correct the field, and validate again.

  • 12 rules for the files as a whole
  • 57 rules for each record
  • Errors stop the build
  • Warnings can be acknowledged
Who reports

Built from one record.

The same rule decides who reports everywhere in RTO Grow: a course that reports, an enrolment and offering set to report, and a student who's ready. When a student's USI is verified, their enrolment becomes ready to report automatically.

USI verifiedEnrolment ready to report

Lodgement

A record of every lodgement.

Build your files and RTO Grow gives you a ZIP to upload at NCVER's AVS portal, with the steps to follow. Every build is saved, with a submission record stamped AVETMISS 8.0 and a copy filed in your Evidence Registry. Nothing goes to NCVER without you.

Also included

The small things that save the day.

  • Any reporting periodPick a preset like January to September, or set your own dates.
  • Your team stays in chargeYou review the build, upload it to AVS yourself and record the lodgement.
  • Who can run itOwners, admins and staff in your office.
  • Real people when you need themSupport requests are handled the same day.
Reporting is changing

AVETMISS today. STARS next.

AVETMISS is being replaced by the VET Information Standard. Instead of uploading NAT files, your system will report straight to STARS, the new platform built by DEWR and run by NCVER. We're following the rollout so you don't have to.

  1. 1Today: AVETMISS™RTO Grow builds and checks your NAT files, and is on NCVER's compliant software register.
  2. 2Now: STARS rolloutNCVER is moving the sector across in stages. We track every update.
  3. 3Your switch-overWe connect RTO Grow to STARS before your RTO moves. Same system, no new software.
  4. 4End of 2028The whole sector reports to the VET Information Standard.

Quick answers.

What is AVETMISS?

AVETMISS is the national data standard for VET reporting. RTOs report to NCVER using it, as a set of NAT files. RTO Grow builds yours to AVETMISS 8.0.

Which NAT files does RTO Grow build?

All ten for the VET Provider collection: NAT00010, 00020, 00030, 00060, 00080, 00085, 00090, 00100, 00120 and 00130.

How do we lodge with NCVER?

Build your files in RTO Grow, upload the ZIP at NCVER's AVS portal, and click "Recorded as submitted" once it's lodged.

Can we fix errors without leaving the page?

Yes. Click "Quick fix" on any error, correct the field, and validate again. Warnings can be acknowledged and the build goes ahead.

Can we keep one student out of a build?

Yes. Untick them in "Who is in this build" and give a reason. Release them later whenever they're ready.

What happens to students we imported from our old system?

They're held as imported history and only reported when you release them, so nothing is reported twice.

Who can run the report?

Owners, admins and staff in your office.

See your report built.

Book a demo and we'll build a NAT file set from a demo RTO in front of you.

Book a demo