...
The SAS Guide to Contract Errors lists the errors and information that may assist in correcting errors.
The DESBTDTET Data Management team can provide assistance to RTOs with any issues pertaining to the submission of compliant data and the interpreting and correction of validation errors.
...
AVETMISS Error Validation Report
STS Online Validation Report
The Smart and Skilled eReporting –Technical Specifications and Business Validations lists validation errors and information that may assist in correcting errors. If the link no longer works, this document is available in STS Online by clicking on the Supporting Documents page, under Smart and Skilled Contract Management.
...
Common Errors
...
Fix
...
Training Activity Data has been finalised for Commitment Id [{0}]. No further data can be accepted
...
The final data for this student has been successfully submitted and the Commitment ID has a status of finalised. No further data will be accepted.
More of a notification - The coordinator will need to tick the following box in the student enrolment on aXcelerate:
“AVETMISS: Do NOT report AVETMISS for this Student”
This will ensure the enrolment no longer reports and will not be included in the next submission.
...
The required number of Core Units of Competency for this qualification as specified in the training package have not been submitted. (Error ID: 1113)
...
These errors generally appear together, and will occur where:
All units in the qualification are not being reported
All units are currently reporting as Not yet started (85)
Enrolment has been cancelled, outcome Withdrawn (40) has been applied for some/all units however the ‘Hours’ field is set to 0 (this converts the Withdrawn outcome to NR and therefore does not report)
To fix:
Check Unit Outcomes in the enrolment and update where required
If Withdrawn, update ‘Hours’ field
...
The Units of Competency supplied are not in accordance with the Training Package rules for this Qualification [QUAL CODE]. (Error ID: 1110)
...
At least one Unit of Competency must be reported with an outcome code of 20, 30, 40, 41, 51 or 70 before enrolment data is accepted for subsidised training. (Error ID: 1132)
...
Earliest Unit of Competency Start Date cannot be changed after commencement of training
...
This error will occur where:
The earliest unit start date reported has been changed in this data upload from the date reported in the initial data upload. The earliest unit of competency start date triggers the commencement payment and cannot be changed
A unit/s start date was changed to a date that is before the first CA was ever reported in the enrolment. The start date will need to be fixed by being a date after the first CA was ever reported on the enrolment.
To fix:
Go to student log and find the first unit or units that show CA - look at the date of this. Likely this unit or units have had their start date or outcome changed down the track
Check start dates to confirm correct date
If a change is required, the Quality team can email the Department who will initiate an override on their end
...
No valid program identifiers found for client ID (Error ID: 1510)
...
This error will occur where:
The course code has not been entered at the qualification setup level in aXcelerate.
Compliance will need to fix this and add the course code
Training Activity Data clarification required Email
Sometimes while data passes initial Smart and Skilled validations, on further review of the data by the department inaccuracies may be found and the data may be rejected. The following are some errors we have received via email to the Quality team previously:
Common Errors
Fix
Incorrect training activity data has been reported
Quality team to follow instructions on email. They usually detail what was reported incorrectly.
Example:Commitment ID was created with a Disability Status, however the status was not reported in NAT00080 file.
Action required: This means our data in aXcelerate collected from the enrolment form does not match what has been entered into the Commitment ID. This is to be reviewed and updated accordingly by the coordinator.
Example:
Common Errors | Fix | |||||
---|---|---|---|---|---|---|
Multiple claim – this Module/Competency has been claimed previously | This error will occur where:
To fix:
| |||||
State funding not approved – Previously held qualification | This error will occur where:
Having previously completed a qualification in most instances deems the student ineligible for funding. Exemptions include:
How do I fix it?
| |||||
The postcode/suburb combination is not a Delivery Area on the Australia Post list | This error will occur where:
To fix:
| |||||
Invalid Tuition Fees Supplied | This error will occur where:
To fix:
| |||||
Student’s residential postcode is not in Queensland | The first time this error appears the Coordinator will need to fix address/postcode in aXcelerate and mark off in green on avetmiss spreadsheet. This error is likely to occur the next few times the report is run - in this case Compliance need to email DESBT (contractmanagement) along with the student’s ID that proves their address. The error will keep appearing unless Compliance email DESBT with evidence | |||||
AISS search not conducted | This error will occur where:
To fix:
| |||||
At school flag of Y is inconsistent with Labour force status identifier of '01' | This error will occur where:
To fix:
| |||||
Survey Contact Status ID must not be blank | In the enrolment, the field ‘Study reason’ should have an answer selected. Don’t leave as ‘not specified’. To check what the student answered for this go to their portfolio and look at the enrolment form application. Whatever the student answered for ‘What is your primary reason for wanting to study with us’ enter that answer in the study reason field on aXc | |||||
You have assigned a Queensland Subsidy Contract Number but the State Fund Source Code is not compatible. Please check the allocation of this Fund Source code. It may affect your payments. | This error will occur where:
To fix:
| |||||
Training Agreement status was not active for the end date supplied for module/competency. | This error will occur where:
To fix:
| |||||
Warning - Training Contract has been terminated and Training has not been finalised. | This error will occur where:
To fix:
Note: This way around is not great, as we may not be able to claim and report outcomes (Withdrawns, Competencies etc) if the agreed date has already passed. There should be communication with the trainer/employer/AASN around what agreed date is required to allow time for processing on our end for reporting and claiming outcomes (withdrawns, comptencies, completions etc). We will not get paid if the dates are not suitable. | |||||
Your organisation is not recorded as the SRTO for this Apprentice/Trainee for the duration of the training activity. | This error will occur where:
Fix:
| |||||
Withdrawn (40) outcome not supported - No record of Apprentice/Trainee training contract cancellation, withdrawal or change of SRTO. | This error will occur where:
Fix: Check if cancellationImportant* Look at the supporting details_2 column on the avetmiss spreadsheet. This will help you see what the unit in question is currently being reported as with start and end dates vs what this unit was previously reported as. This information will help you figure out if the unit is a false multiple or if a ct was missed. *rare situation: The unit is seen on the USI transcript and it was completed at an RTO in another state. For some reason interstate data doesn’t always record so our data doesn’t recognise it was completed even though the transcript says it was. In this case Coordinator is to email Compliance and they will email DTET to clear this error. This error will occur where:
To fix:
| |||||
State funding not approved – Previously held qualification | This error will occur where:
Having previously completed a qualification in most instances deems the student ineligible for funding. Exemptions include:
How do I fix it?
| |||||
The postcode/suburb combination is not a Delivery Area on the Australia Post list | This error will occur where:
To fix:
| |||||
Invalid Tuition Fees Supplied | This error will occur where:
To fix:
| |||||
Student’s residential postcode is not in Queensland | The first time this error appears the Coordinator will need to fix address/postcode in aXcelerate and mark off in green on avetmiss spreadsheet. This error is likely to occur the next few times the report is run - in this case Compliance need to email DTET (contractmanagement) along with the student’s ID that proves their address. The error will keep appearing unless Compliance email DTET with evidence | |||||
AISS search not conducted | This error will occur where:
To fix:
| |||||
At school flag of Y is inconsistent with Labour force status identifier of '01' | This error will occur where:
To fix:
| |||||
Survey Contact Status ID must not be blank |
If nothing nothing is identified as mentioned above then try the fix below: In the enrolment, the field ‘Study reason’ should have an answer selected. Don’t leave as ‘not specified’. To check what the student answered for this go to their portfolio and look at the enrolment form application. Whatever the student answered for ‘What is your primary reason for wanting to study with us’ enter that answer in the study reason field on aXc | |||||
Date of birth is invalid Gender must be F, M, X Country of birth ID is invalid Survey Contact Status ID must not be blank | If multiple errors like this show at the same time it’s because there’s a symbol incorrectly used in the students name (same as above). Once the symbol is corrected then these multiple errors will clear | |||||
You have assigned a Queensland Subsidy Contract Number but the State Fund Source Code is not compatible. Please check the allocation of this Fund Source code. It may affect your payments. | This error will occur where:
To fix:
| |||||
Training Agreement status was not active for the end date supplied for module/competency. | This error will occur where:
To fix:
| |||||
Invalid Contract/Training Schedule number suppliedWarning - Training Contract has been terminated and Training has not been finalised. | This error will occur where:
Fix:
| |||||
Invalid Contract, qualification or Training contract registration number supplied (User Choice/traineeship) | Several reason why this error will occur:
Fix:
| |||||
All other errors |
Info |
---|
Note: New Validations have been introduced October 2022, which may appear on the AVETMISS Validation Error Report:
Example error received for student #10597336: |
Data Quality Errors
The AVETMISS data which Strategix submits to DESBT is forwarded on by DESBT to NCVER each quarter. During this process each quarter, there may be validation errors that arise, which are the Data Quality Errors received from stac@desbt.qld.gov.au.
When received, the errors are to be corrected and the data for the relevant collection year must be re-submitted. Note: Depending on the enrolment data, this may be more than one collection year. Once we respond to DESBT, they will re-run the validation on their end and let us know if any further errors pop up.
...
Common Errors
...
Fix
...
DQ_Overlaps
...
This error will occur where:
Multiple records of the same subject have been reported for the same student with overlapping dates
To fix:
Check the Activity Start Dates and Activity End Dates for the subjects, and ensure the dates do not overlap
...
DQ_Postcodes_StateID
...
This error will occur where:
The student’s post code is either missing or an invalid combination of post code and suburb
May not have been checked/updated after enrolment has been received
To fix:
Use aXcelerate’s in-built address function to populate the post code once the suburb is entered
Check post code and suburb against https://auspost.com.au/postcode
Ensure both the Postal and Street Address fields are entered
...
DQ_ProgramAudit
...
This error will occur where:
A student has been reported as Completed in the Program Completed (NAT00130) file, however, the number of reported competencies do not equal the competency count as outlined in the relevant Training Package rules on http://Training.gov.au (TGA).
To fix:
Find which units are not reporting - Compare aXcelerate enrolment against error list from department
Once identified, find out why they are not reporting -
Review all units to see if the Do NOT report AVETMISS checkbox is ticked on the unit level (start with any CT’s). If there is no logical reason or record of why this should be ticked, untick
Check the Student Log in the enrolment to confirm when competencies were applied. If a competency was applied for a previous collection year, it may not have been re-reported as of yet
Check any transitions (if applicable) were processed correctly
...
All other errors
View file | ||
---|---|---|
|
New South Wales
When NSW data is downloaded from aXcelerate, it is then uploaded to NCVER for validation and formatting purposes before being uploaded into the STS portal.
Below is a list of the common errors that have appeared at each stage of the process, and the potential fixes that have worked previously.
NCVER Validation
...
Potential Errors
...
Fix
...
Activity End Date (XXXXXXXX) must not be before the Collection Period Start Date
...
No fix required - This error must be ignored
...
Record for this Client Identifier (C00XXXXXXX) contains publicly funded data. Please be aware that this data must be submitted via your state training authority and cannot be submitted via AVS.
...
No fix required - This error must be ignored
...
Outcome ID - 70 should not be used for this Activity End Date (XXXXXXXX), unless reporting an Interim collection for future dated activity.
...
No fix required - This error must be ignored
...
All other errors
...
Guidance on fixing all other errors is located on https://www.ncver.edu.au/rto-hub/rto-fact-sheets:
Fixing common validation errors
Identify and fix validation errors
To fix:
Note: This way around is not great, as we may not be able to claim and report outcomes (Withdrawns, Competencies etc) if the agreed date has already passed. There should be communication with the trainer/employer/AASN around what agreed date is required to allow time for processing on our end for reporting and claiming outcomes (withdrawns, comptencies, completions etc). We will not get paid if the dates are not suitable. | |
Your organisation is not recorded as the SRTO for this Apprentice/Trainee for the duration of the training activity. | This error will occur where:
Fix:
|
Withdrawn (40) outcome not supported - No record of Apprentice/Trainee training contract cancellation, withdrawal or change of SRTO. | This error will occur where:
Fix:
|
Invalid Contract/Training Schedule number supplied. | This error will occur where:
Fix:
|
Invalid Contract, qualification or Training contract registration number supplied (User Choice/traineeship) | Several reason why this error will occur:
Fix:
|
All other errors |
Info |
---|
Note: New Validations have been introduced October 2022, which may appear on the AVETMISS Validation Error Report:
Example error received for student #10597336: |
Data Quality Errors
The AVETMISS data which Strategix submits to DTET is forwarded on by DTET to NCVER each quarter. During this process each quarter, there may be validation errors that arise, which are the Data Quality Errors received from stac@DTET.qld.gov.au.
When received, the errors are to be corrected and the data for the relevant collection year must be re-submitted. Note: Depending on the enrolment data, this may be more than one collection year. Once we respond to DTET, they will re-run the validation on their end and let us know if any further errors pop up.
Common Errors | Fix | ||||
---|---|---|---|---|---|
DQ_Overlaps | This error will occur where:
To fix:
| ||||
DQ_Postcodes_StateID | This error will occur where:
To fix:
| ||||
DQ_ProgramAudit | This error will occur where:
To fix:
| ||||
All other errors |
|
New South Wales
When NSW data is downloaded from aXcelerate, it is then uploaded to NCVER for validation and formatting purposes before being uploaded into the STS portal.
Below is a list of the common errors that have appeared at each stage of the process, and the potential fixes that have worked previously.
NCVER Validation
Potential Errors | Fix |
---|---|
Activity End Date (XXXXXXXX) must not be before the Collection Period Start Date | No fix required - This error must be ignored |
Record for this Client Identifier (C00XXXXXXX) contains publicly funded data. Please be aware that this data must be submitted via your state training authority and cannot be submitted via AVS. | No fix required - This error must be ignored |
Outcome ID - 70 should not be used for this Activity End Date (XXXXXXXX), unless reporting an Interim collection for future dated activity. | No fix required - This error must be ignored |
All other errors | Guidance on fixing all other errors is located on https://www.ncver.edu.au/rto-hub/rto-fact-sheets: |
STS Online Validation Report
The Smart and Skilled eReporting –Technical Specifications and Business Validations lists validation errors and information that may assist in correcting errors. If the link no longer works, this document is available in STS Online by clicking on the Supporting Documents page, under Smart and Skilled Contract Management.
Common Errors | Fix |
---|---|
Training Activity Data has been finalised for Commitment Id [{0}]. No further data can be accepted | The final data for this student has been successfully submitted and the Commitment ID has a status of finalised. No further data will be accepted. More of a notification - The coordinator will need to tick the following box in the student enrolment on aXcelerate: “AVETMISS: Do NOT report AVETMISS for this Student” This will ensure the enrolment no longer reports and will not be included in the next submission. |
The required number of Core Units of Competency for this qualification as specified in the training package have not been submitted. (Error ID: 1113) | These errors generally appear together, and will occur where:
To fix:
|
The Units of Competency supplied are not in accordance with the Training Package rules for this Qualification [QUAL CODE]. (Error ID: 1110) | |
At least one Unit of Competency must be reported with an outcome code of 20, 30, 40, 41, 51 or 70 before enrolment data is accepted for subsidised training. (Error ID: 1132) | |
Earliest Unit of Competency Start Date cannot be changed after commencement of training | This error will occur where:
To fix:
|
No valid program identifiers found for client ID (Error ID: 1510) | This error will occur where: The course code has not been entered at the qualification setup level in aXcelerate. Compliance will need to fix this and add the course code |
Training Activity Data clarification required Email
Sometimes while data passes initial Smart and Skilled validations, on further review of the data by the department inaccuracies may be found and the data may be rejected. The following are some errors we have received via email to the Quality team previously:
Common Errors | Fix |
---|---|
Incorrect training activity data has been reported | Quality team to follow instructions on email. They usually detail what was reported incorrectly. Example:
Action required: This means our data in aXcelerate collected from the enrolment form does not match what has been entered into the Commitment ID. This is to be reviewed and updated accordingly by the coordinator. Example:
Action required: Review start and end dates, rectify and submit updated training activity data for the noted student(s). This is generally either the start and end date being too close together (within 2 days) or more than 4-5 units with the same start date. |
Student Fee Change | The fee adjustment(s) may be for one or more of the following reasons:
Action required:
|
Training Activity Data clarification required | Follow instructions on email to find what data need to be clarified, and how to respond. Email generally requests a response to be highlighted accordingly. Example 1:
Action required:
Example 2:
Action required:
|
...
Potential Errors | Fix |
---|---|
Duplicate Enrolment across RTO's | This error will occur where:
To fix:
|
Duplicate Enrolment within lodgement | This error will occur where:
To fix:
|
The Outcome Code is 05 or 105 and the enrolment end date has past but is less than 28 days before the lodgement date. | This error will occur where:
To fix:
|
Out of Commencing Period Error | This error will occur where:
To fix:
|
Enrolment End Date is before the Enrolment Start Date | This error will occur where:
To fix:
|
Reported UoC End Date is greater than CPS Training Activity End Date | This error will occur where:
To fix: Let the Quality team know Refer to the Training Activity End Date in the Contractual Details (found on TAMS > Contracts > My Contracts > Open CPS) :
To fix:
|
UoC/Module Hours do not match the hours as defined by STARS | This error will occur where:
To fix:
NCVER nationally agreed nominal hours *STARS = Student Training Activity Reporting System |
Enrolment Text File Warnings:
...