Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

OVERVIEW

Status

CURRENT DRAFT NEEDS REVIEW

Classification*

INTERNAL

Department

ALL STAFF

Review

Notes

 

*See Information classification policy


Guide on How to Fix Errors Procedure

This section is divided up into two sections:

  • aXcelerate Validation Warnings/Errors – This section contains direction for guidance with common errors or warnings which may appear in aXcelerate due to its built in validation rules. These rules are not as strict as those found in the national or state validation software, therefor there may be additional errors once the data has been extracted/downloaded from aXcelerate and uploaded to state or national reporting authorities.

  • State/National Validation Warnings/Errors – This section contains guidance with common errors or warnings which may appear on error reports from state or national reporting authorities.

aXcelerate Validation Warnings/Errors

When an AVETMISS report is run, aXcelerate runs the data through some validations to check the data for discrepancies and identify possible errors prior to the data being submitted to state or national authorities.

The following is an example of how the errors appear from aXcelerate’s checks:

The errors relate to data contained in each NAT file and by fixing one error for a student may fix another error in another NAT file that is directly related. For example of a student’s address is incorrect there may be an error in the NAT00080 file and the NAT00085 file as both files may contain some information that relies on or relates to each other.

The following table is a list of common errors and what may be done to fix them in aXcelerate prior to the NAT files being downloaded.

Error Example

Reason/Issue

Fix

Activity End Date for TLIA2013 (DD/MM/YYYY) must not be in the future for final outcome 20

Or

Activity End Date for CHCLEG001 (14/05/2020) must not be in the future for final outcome 60

A final outcome (CT, Competent or RPL) has been awarded and the outcome date is in the future, this is not a possible combination.

The end date should be the actual date the outcome was determined. The administrative assistant must correct the date in aXcelerate.

Mandatory field Funding source (national) must not be blank

Missing funding codes. These are required in order for the data to be submitted. Any enrolments not containing funding codes will never be reported.

Update the funding fields attached to the students’ enrolment.

Mandatory field USI must not be blank

The student who has been reported with accredited training is Missing USI.

Important: A missing USI is a breach in reporting requirements.

Must obtain a USI, we cannot choose to not report competencies for VET accredited training. The only allowance for not reporting an outcome is where the Fees have not been paid.

USI for this contact has not yet been verified in aXcelerate

A USI has not been verified. A USI must be verified to ensure that training data is not submitted against a USI which belongs to someone else.

Important: An unverified USI is a breach in reporting requirements.

The USI must be verified prior to submitting the data.

Activity End Date for MSS402051 (12/12/2019) has elapsed for interim outcome 70

The student has a CA outcome and it is dated in the past.

Either the subject:

  • Should have a Competent outcome or

  • Has a proposed end date which needs to be set to a future date.

Mandatory field Delivery mode identifier must not be blank

and

Mandatory field Predominant delivery mode must not be blank

The Subject is missing a Predominant delivery mode and/or delivery mode

The student has a subject or subjects which are missing their delivery mode information and this needs to be updated.

Activity Start Date for TLIB2008 (01/12/2019) must not be in the past for not-started outcome 85

A subject which has an outcome of Not Yet Started has a date which is in the past, this is not a possible combination.

Either the subject:

  • Should have a Continuing Activity (outcome 70) or

  • Requires its proposed end date to be set to a future date.

Activity End Date for CHCCOM005 (22/11/2019) must not be before the Activity Start Date (26/12/2019)

Either:

  • The end date for a subject has been set to a date before the correct start date or

  • The start date has been set to a date after the correct end date.

Update the end or start date to the correct date, both should match when either commencement activity or the outcome was awarded/occurred.

State/National Validation Warnings/Errors

National (For Total Data submission)

See the following NCVER links for guidance on amending validation errors and warnings:

Errors

Fix

Activity Start Date (XXXXXXXX) must not be more than 5 years before the Collection Period Start Date

This error will occur where:

A student has been enrolled in the same qualification/unit for more than 5 years.

Note: this information only applies to Fee For Service training, state funding rules may be different.

To fix:

  1. Double check the Activity Start and End Dates fields

  2. If correct, Strategix will need to apply for an exemption*:

    1. All other errors must first be corrected, with only this error remaining

    2. You then need to submit a request in writing (to support@ncver.edu.au) outlining the period and error you are requesting an exemption on

    3. Your request must also provide details as to why the exemption is required i.e. explanation as to why the student has taken 7 years to complete the single unit of competency

    4. This will then be sent off for review and the outcome of the review advised in writing. Note: If approved, you will be required to complete this exemption request for all subsequent submissions in which this error is triggered for this client

*Information sourced from email received from NCVER Support to Complaince on 15 Nov 2023. See information for student Ruth Taylor for more guidance.

'Time between Activity End Date (XXXXXXXX) and Activity Start Date (XXXXXXXX) must not be greater than 5 years'

Queensland

The DESBT 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.

The list of error fact sheets can help in rectifying errors (updated October 2022).

AVETMISS Error Validation Report

Common Errors

Fix

Multiple claim – this Module/Competency has been claimed previously

This error will occur where:

  1. The student has already successfully completed the same unit of competency/module regardless of whether it was claimed under a subsidised program; and/or

  2. A change is reported to an existing VET activity data record (i.e. amendment to training Activity start and/or Activity end dates, Outcome identifier, etc.) that has already been paid/reported under an agreement. When VET activity data is changed by a SAS, the system identifies the unit of competency/module as being claimed twice. This is known as a “false multiple”.

    • Note: We refer to these as Data Correction

To fix:

  • Check supporting_details_2 column on validation report for information on what has previously been reporting for the error

  • Apply any Credit Transfers (60) wherever possible

  • If you cannot report the unit as a credit transfer due to insufficient evidence, the unit of competency/module should be reported as fee-for-service

  • If believed to be a false multiple, note as Data Correction on the spreadsheet and wait 3-4 reports to see if it clears on its own

    • If the original record is in the current financial year a false multiple will rectify itself, however payment will not be reinstated until the following month (if applicable).

    • If the VET activity data falls outside of the current financial year, the false multiple error will not clear and will remain on the Validation Report. Will need to be reported as fee-for-service or contact DESBT

  • For any exceptions to this funding rule, send an email along with supporting documentation to contractmanagement@desbt.qld.gov.au.

State funding not approved – Previously held qualification

This error will occur where:

  • Certificate 3 Guarantee - if the student already holds a Certificate III or higher-level qualification.

  • Higher Level Skills – if the student already holds a Certificate IV or higher-level qualification.

Having previously completed a qualification in most instances deems the student ineligible for funding. Exemptions include:

  • Completed in school

  • Strategix accidentally reported a completion date, and has since corrected this (student only completed the qualification once)

How do I fix it?

  • If the student is ineligible for further Government funding, remove the fund source code and the agreement number and report the training and assessment as fee-for service.

  • If you believe the student is eligible for an exception to the eligibility criteria of the funding program, send an email along with supporting documentation to your Contract Manager at contractmanagement@desbt.qld.gov.au.

The postcode/suburb combination is not a Delivery Area on the Australia Post list

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 in the Update contact profile screen to populate the post code once the suburb is entered

  • Ensure both the Postal and Street Address fields are entered

  • Double check post code and suburb against https://auspost.com.au/postcode

Invalid Tuition Fees Supplied

This error will occur where:

  • No finance model is selected - The Tuition Fee/Plan: field updated with the finance model links through to the field "Client Tuition Fee: $XXX / subject" for the enrolment

  • Add in JT stuffff/ being overridden at the unit level etc..

To fix:

  • Double check what fees should be applied

  • Apply finance model where possible (if old finance model is deactivated, ask the Quality team to reactivate it temporarily)

AISS search not conducted

This error will occur where:

  • The AISS search either not done or

  • The AISS search was done, however the name or DOB is incorrect

To fix:

  • Check all student details and conduct new AISS check

  • Confirm funding eligibilty with new check

At school flag of Y is inconsistent with Labour force status identifer of '01'

This error will occur where:

  • The "At School:" field recorded in the VET Related Details (from the enrolment form) does not match the "Employment Status:" field - Refers to secondary school, and the employment status must be logical. For example, generally should not be At School but working Full Time.

To fix:

  • Double check details from enrolment form

  • Confirm with student if needed

  • Update either the "At School:" field or the "Employment Status:" field

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:

  • The enrolment fields “Funding Source (State):” and “Contract/Schedule:” do not match

To fix:

Training Agreement status was not active for the end date supplied for module/competency.

This error will occur where:

  • Traineeship extension form has not yet been processed by DESBT - May need to wait

To fix:

  • Check if student intends to continue course. If so, check the extension form has been signed and completed by the relevant parties and sent to DESBT for processing.

Warning - Training Contract has been terminated and Training has not been finalised.

This error will occur where:

  • Traineeship cancellation form has been processed by DESBT, and the enrolment on our end has not yet been finalised/withdrawn

To fix:

  • Review student progress on learning portal - ensure any Competencies or Withdrawns are pushed through to process withdrawal

  • Review Activity End Dates - ensure the date is within the training contract dates

    • Withdrawns can be back-dated to cancellation date

    • Competencies - Check with management

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:

  • Traineeship extension form has not yet been processed by DESBT OR

  • The traineeship completion form or cancellation form was completed with an agreed date that is before/after our Start and End dates.

Fix:

  • Check if student intends to continue course. If so, extension form has been signed and completed by the relevant parties and sent to DESBT for processing OR

  • Amendment form to correct the date.

More long-term solution to be discussed:

Withdrawn (40) outcome not supported - No record of Apprentice/Trainee training contract cancellation, withdrawal or change of SRTO.

This error will occur where:

  • Traineeship cancellation form has not yet been processed by DESBT.

Fix:

  • Check if cancellation form has been signed and completed by the relevant parties and sent to DESBT for processing.

Invalid Contract/Training Schedule number supplied.

This error will occur where:

  • Appears when contract/training number is blank and has not yet been received OR

  • Occasionally appears when an enrolment type is selected as Traineeship but actually isn't.

Fix:

  • Refer to the Training Downloads - Snapshot Changes report and Approved Contracts report in the Partner Portal. Once the contract details appear these can be added into the aXcelerate enrolment OR

  • Update enrolment type to "Other/Normal" if not a traineeship.

All other errors

SAS Guide to Contract Errors

Note: New Validations have been introduced October 2022, which may appear on the AVETMISS Validation Error Report:

  • Compares duplicate activity with overlapping start and end dates. Nationally recognised subjects will generate an error and all other subjects will generate a warning where duplicate records have overlapping activity dates. Record comparison is based on:

    • Training organisation identifier, Unique student identifier, Subject identifier; or

    • Training organisation identifier, Client identifier, Subject identifier (if USI is blank/INTOFF/INDIV).

  • Identifies duplicate activity where Outcome identifier = 20 (Competency) and/or 51 (RPL-G) for one or both of the reported records. Record comparison is based on:

    • Training organisation identifier, Unique student identifier, Subject identifier; or

    • Training organisation identifier, Client identifier, Subject identifier (if USI is blank/INTOFF/INDIV).

Example error received for student #10597336:
Duplicate record. A record already exists with this record's primary key.

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

New South Wales

When actioning NSW data it is possible to encounter errors at three points of the process, which are identified with instructions below.

First Possible Error Point - During the initial validation via the NCVER

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

Second Possible Error Point - Through the Validation Report on STS Online
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.

Third Possible Error Point - Email received from department

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 for the following reason(s):

Common Errors

Fix

Incorrect training activity data has been reported

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:

  • Unit(s) of competency (UoC) reported with incorrect UoC start and/or end dates

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:

  • Credit transfer (CT) and/or recognition of prior learning (RPL) outcomes have been added, changed or removed

  • The training start date affecting a student's eligibility for a Fee-Free Scholarship has been changed

  • The training start date affecting a student's eligibility for a Fee-Free Traineeship has been changed

  • The student's eligibility for a Fee-Free Traineeship has been validated

  • The student's eligibility for a Fee-Free Apprenticeship has been validated.

Action required: You must now charge the student the "new student fee". This can be viewed in the 'eReporting - Update Student Details' screen on https://online.training.nsw.gov.au/, where you can also view the "new subsidy" and "new loading(s)". Review any invoices sent and amend if needed.

Training Activity Data clarification required

Follow instructions on email to find what data need to be clarified.

Example:

  • 5 UoCs has been reported with the same started date 05/09/2022

Action required: Confirm that this Training Activity Data has been reported correctly by explaining how the student has Participated in Subsidised Training that exceeds mere attendance in multiple UoCs commencing on the same day.

Example:

  • The Training Activity Data shows that the Enrolled Student completed 2 UoCs in a short period of time i.e., same day or 1- 2 days.

Action required: Confirm that the Training Activity Data has been reported correctly by explaining how all of the training and assessments were conducted within a short period of time.  

IMPORTANT - If data is corrected or changed for any reason for a finalised enrolment (which has the “AVETMISS: Do NOT report AVETMISS for this Student” box ticked), this box must then be unticked.

If it is left ticked, it will not be included in the next submission and therefore the updated data will not be reported. This could result in non-payment.

South Australia

When actioning SA data it is possible to encounter errors at two points of the process, both are identified with instructions below.

First Possible Error Point - During the initial validation via the NCVER

Potential Errors

Fix

Activity End Date (19072018) must not be before the Collection Period Start Date

No fix required - This error must be ignored

Record for this Client Identifier (C007187131) 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 (30092019), 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

Second Possible Error Point - Through the Validation Report on STELA

The STELA NAT Upload Validations – Errors and Warnings (Excel) spreadsheet lists validation errors and information that may assist in correcting errors.

Third Possible Error Point - Through the Claims Errors

Western Australia

In Western Australia, there are 3 instances where errors may occur (outside of aXcelerate) throughout the submission process. These Errors can appear during the Student Text file upload and during the Enrolment Text file upload (pre and post validations).

Student Text File Errors: The list of errors is substantial and can be found in the department's “Text File Specifications” document. - View here: (Previous version can be viewed here.)

Refer also to the document for assistance with errors.

Enrolment Text File Errors:
Pre-validation Errors - The most common issues are able to be resolved by checking the items listed below. Also refer to the Text File Specifications.

  • Check for invalid data with each column against the Text File Specification

  • Data left blank when data is required in the field

  • Column width format (increase in length)

  • Additional blank columns

  • Full stops, excess spaces before and after field content

  • Check each line of data has a carriage return at the end

Post-validation Errors - Post validation issues can occur when RAPT/TAMS RTO portal has identified specific text file business rules or contractual requirements are not being met or an illogical field entry has occurred. The list of errors is substantial and can be found in Appendix 1 of the department's “Manual for Payments and Reporting” document.


STANDARDS AND REGULATORY REQUIREMENTS

Authority

  • List here

See Funding

Regulatory Documents

  • List here

List the Contract, audit evidence requirements, standards etc. and the applicable section or clause from each document

Approved By

Name here

Details / Decisions:


RELATED DOCUMENTS

  •  


 

  • No labels