> For the complete documentation index, see [llms.txt](https://docs.silverband.com.au/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silverband.com.au/home/paradigm-knowledge-base/tcsi-reporting/avetmiss-reporting.md).

# AVETMISS Reporting

## Overview

This article provides an overview of AVETMISS, the national standard for the collection of VET data. Each AVETMISS NAT file outlines the workflow on how to use Paradigm to generate each reporting file and submit it to NCVER's AVETMISS Validation Software for validation.

The Australian Vocational Education and Training Management Information Statistical Standard (AVETMISS) for VET providers is the data standard for the National VET Provider Collection and the VET in Schools Collection, which collects training information from government-funded and privately-operated training providers.

The VET Provider Standard is presented in two documents: the *AVETMISS VET Provider Collection specifications* and the *AVETMISS data element definitions*. The collection specifications describe the files and fields to be collected. The data element definitions define the fields or data elements used in the collection.

The current version of the Standard is release 8.0, which applies to all training activity from 1 January 2018. You can find the link to download it below

## Further Reading

* [AVETMISS VET Provider Collection specifications: release 8.0](https://www.ncver.edu.au/rto-hub/statistical-standard-software/avetmiss-vet-provider-collection-specifications-release-8.0)
* [AVETMISS data element definitions: edition 2.3](https://www.ncver.edu.au/rto-hub/statistical-standard-software/avetmiss-data-element-definitions-edition-2.3)
* [AVETMISS reporting in 8 steps](https://www.ncver.edu.au/__data/assets/file/0012/10272/CS-Fact-Sheet-AVETMISS-reporting-in-8-steps.pdf)&#x20;
* [RTO Fact sheets](https://www.ncver.edu.au/rto-hub/rto-fact-sheets)

## Workflows

{% content-ref url="/pages/VaI6GYshPpYyEMSCNp7I" %}
[National Reporting (NCVER)](/home/paradigm-knowledge-base/tcsi-reporting/avetmiss-reporting/national-reporting-ncver.md)
{% endcontent-ref %}

{% content-ref url="/pages/5RJtKoBhZMWH7U5n53fx" %}
[Victorian VET (SVTS)](/home/paradigm-knowledge-base/tcsi-reporting/avetmiss-reporting/victorian-vet-svts.md)
{% endcontent-ref %}

## Troubleshooting | FAQs

<details>

<summary>NAT00060 File Unit of Competency Missing in the Report</summary>

### NAT00060 File Unit of Competency Missing in the Report

The Unit of Competency is tracked and recorded in Paradigm as Assessments in the Base Unit down to the Scheduled Unit Level. To ensure that the Unit of Competency appears in the report, the Code Id should be added to the Assessment Details section of the Base Unit. You can refer to the steps below:

1. Load the Base Unit record for the missing Unit of Competency in the report
2. Go to the ASSESSMENTS ASSOCIATED WITH UNIT section and edit the assessment item
3. Copy the Unit of Competency Code to the **Code Id** field and save<img src="https://1246578764-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC21t2SaV2eKaLxvtR27D%2Fuploads%2F9Hb6Nk5Qf2GUY7G5AVsT%2Fimage.png?alt=media&amp;token=ce414242-3aba-42ba-a7d4-369f26974df7" alt="" data-size="original">
4. After entering the **Code Id** in the Base Unit level, load the Scheduled Unit and go to the ASSESSMENTS section, (<mark style="color:red;">**1**</mark>) edit the assessment item again and check if the **Assessment Code** field has been updated to the Unit of Competency Code. For already Scheduled Units, copy the Unit of Competency code again in the **Assessment Code** field (<mark style="color:red;">**2**</mark>) Kindly also fill out the highlighted fields below for compliance, and then (<mark style="color:red;">**3**</mark>) save the assessment.

   ![](https://1246578764-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC21t2SaV2eKaLxvtR27D%2Fuploads%2FpufAKkQ5ShUYwnLETrEa%2Fimage.png?alt=media\&token=71e65a09-077d-437c-bcf7-d01d86a59a37)

[Raise a Support Ticket](https://silverband.atlassian.net/servicedesk/customer/user/login?destination=portals) if the instructions above do not solve the issue.&#x20;

</details>
