Submit AVETMISS without the dread.

RTObase maps your student and enrolment data to the AVETMISS Release 8.0 format automatically. When you're ready to submit, click "Generate NAT files". RTObase validates the data, highlights issues, and produces NAT files for your review and upload to NCVER AVS. No spreadsheet exports, no third-party converter.

Validation runs before any file is generated, so missing USIs, invalid postcodes, impossible dates and incomplete enrolment data are flagged up front against the exact record to fix. And if NCVER's AVS still rejects something after upload, you bring its validation report back into RTObase: a guided wizard maps every AVS error to the exact student and field, deep-links you straight to it, and lets you mark each one off as you go. You fix the source record, not the file, and re-validate without hunting client identifiers in a spreadsheet.

All the files required for a standard AVETMISS Release 8.0 submission, the organisation and delivery-location files, course and subject files, client and address files, disability and prior-education files, and the enrolment and program-completion files. They export together in the NCVER-prescribed format.

Where an RTO has completed USI Registry setup, RTObase can verify student USIs against the Australian Government USI Registry automatically, using the government's machine-to-machine (M2M) credential, the same setup the USI Registry requires. Successful checks are recorded in the student's activity feed. Manual attestation is available when the RTO verifies through the USI portal.

No. RTObase records every enrolment and outcome in AVETMISS-aware fields as it happens, so the NAT files come straight out of your live data. You download the validated files and upload them to NCVER's AVS. There's no intermediate converter, mapping spreadsheet, or re-keying.

VET Data Streamlining is moving national reporting toward API-based reporting through NCVER's STARS program. RTObase generates AVETMISS Release 8.0 files today and keeps enrolment, outcome and payment data in a structured model that is intended to support VDS-era reporting as official specifications mature.

Yes. Business and Custom include funding contracts, jurisdiction fields, reporting checks and authority-response records. Queensland has a documented ATA file layout, including LUI and prior-qualification checks, but still needs authority validation on upload. NSW includes Commitment ID and program-status fields; NSW and the other state outputs remain data extracts rather than verified lodgement formats. Staff upload through the authority’s required process. Fee-for-service NCVER reporting stays included on every plan.

Primary RTObase data is stored in Australian data centres and encrypted at rest and in transit. Selected subprocessors are used for features such as AI, communications, payments and analytics, as described in our Privacy Policy.