Two DU files are created and validated in a HELP Due submission each year. The first file includes student details for debts incurred between 1 January and 30 June. The second file includes student details for debts incurred between 1 July and 31 December. Submission method The DU file is the only file in HELP Due submission. HELP Due is different to other submissions. The data is not submitted. Instead, information from a validated HELP Due submission is provided as a "snapshot" of information to support the following submissions: Student Student Revision SAHELP OSHELP OSHELP Revision. The creation of a "snapshot" is an automated process in the . When you report any of these submissions to the department, TFN data in the snapshots are encrypted to protect the privacy of students' personal information. You will need to use your encryption key provided by the ATO when you submit data that includes information from the HELP Due. Submissions are made using HEPCAT. More information about this process is in the . Structure Information about the structure and the elements in the DU file is in the for the relevant reporting year. One record for each student and course combination is required on the DU file. Each record must have a unique combination of values for: Student identification code () Course code () Commonwealth Higher Education Student Support Number (CHESSN) (). These elements are the key identifiers for each record on the DU file. The DU file also uses these values to identify matching records in a Student, OSHELP, SAHELP or related revisions submission. Revising HELP DUE data The provide detailed information on how to revise data reported in a DU submission. This includes how to: add new records to an existing submission update personal details for student records in an existing submission
Two DU files are created and validated in a HELP Due submission each year. The first file includes student details for debts incurred between 1 January and 30 June. The second file includes student details for debts incurred between 1 July and 31 December. Submission method The DU file is the only file in HELP Due submission. HELP Due is different to other submissions. The data is not submitted. Instead, information from a validated HELP Due submission is provided as a "snapshot" of information to support the following submissions: Student Student Revision SAHELP OSHELP OSHELP Revision. The creation of a "snapshot" is an automated process in the . When you report any of these submissions to the department, TFN data in the snapshots are encrypted to protect the privacy of students' personal information. You will need to use your encryption key provided by the ATO when you submit data that includes information from the HELP Due. Submissions are made using HEPCAT. More information about this process is in the . Structure Information about the structure and the elements in the DU file is in the for the relevant reporting year. One record for each student and course combination is required on the DU file. Each record must have a unique combination of values for: Student identification code () Course code () Commonwealth Higher Education Student Support Number (CHESSN) (). These elements are the key identifiers for each record on the DU file. The DU file also uses these values to identify matching records in a Student, OSHELP, SAHELP or related revisions submission. Revising HELP DUE data The provide detailed information on how to revise data reported in a DU submission. This includes how to: add new records to an existing submission update personal details for student records in an existing submission
HigherEducationStudent-2018-submission-guidelines.docx