Higher Education Support (Administration) Guidelines 2022

The Guidelines organise around recurring administrative concepts from the Act. Key defined and operational concepts include:

• Student services and amenities fee (SSAF). The Guidelines specify what providers must publish to enable a person to calculate the SSAF when it is determined (s 6(1): amount GST inclusive, period, and persons/categories), prohibit considering payment timing/manner or Commonwealth HELP payments when determining the SSAF (s 6(2)), allow differentiating fees by reasonable categories (s 6(3)), constrain part‑time fees to no more than 75 per cent of full‑time fee (s 7(1)), regulate the earliest payable day relative to enrolment closing date (s 8(1)), and prescribe publication and variation procedures including departmental notification (ss 9-11, 10(2)).

• Census date. The Guidelines repeatedly treat the census date as the critical administrative cut‑off for enrolment, HELP liability, and student notices. Providers must publish census dates and EFTSL values on their website on or before the earliest enrolment date (s 22(1)). When determining a census date, providers must ensure it is not less than 20 per cent into the period between commencement and completion (s 25). Variations to published census dates require Ministerial approval and must not disadvantage students (s 23).

• EFTSL (Equivalent Full‑Time Student Load). The Guidelines define how to determine unit EFTSLs by reference to the unit’s proportion of the standard full‑time study load for one year (s 26(1)-(3)). They permit credit points as a mechanism to allocate relative unit values and require arithmetic precision so the aggregated EFTSLs for a full‑time year add as close as possible to 1.0 (s 27(2)-(5), s 27(3) note). Special rules apply for domestic students undertaking units at overseas higher education institutions,the EFTSL assigned must equal the EFTSL that would be allocated if the unit were undertaken at the Australian provider (s 28(1)-(2)). Accelerator program courses have an EFTSL determined by the time taken to complete the course on a full‑time basis (s 28A).

• Commonwealth Assistance Notice (CAN). The Guidelines prescribe the content that must appear on a CAN (s 17). That includes identifying information (student name, provider, student ID, CHESSN or USI where relevant), EFTSL and unit‑level details, amounts of HELP assistance, SA‑HELP/OS‑HELP/STARTUP‑HELP amounts where applicable, and mandatory prominent statements about HELP balances and the accuracy of assistance information (s 17(2)-(9)).

• Special circumstances. For remission, withdrawal and HELP adjustments, the Guidelines set out provider satisfaction tests for “circumstances beyond the person’s control” (must be not due to the person’s action or inaction and unusual, uncommon or abnormal; s 12), circumstances that did not make full impact until on or after the census date (s 13), and circumstances making it impracticable to complete requirements, with examples across medical, family, employment or course changes (s 14).

• Electronic communications and identifiers. The Guidelines require provider information systems used for electronic notices to be accessible to students, secure, able to store records for subsequent reference, create date fields and printable receipts for HELP requests, and enable unique student identification and approval of electronic communications (ss 29-30). Providers issuing identifiers must verify identity, take precautions against unauthorised use, and advise students of their responsibility to protect identifiers (s 30(3)).

These concepts are operational rules rather than policy statements. Throughout, the Guidelines implement and interpret various cross‑references to the Act,principally sections in Pt 3 and Pt 4 of the Act (for example, ss 19‑37, 169‑5, 169‑25, 169‑28, 36‑13, 36‑21, 174‑5).

The Guidelines allocate duties and informational obligations principally between higher education providers, students (including Commonwealth Supported Students and those seeking HELP assistance), and the Department. The instrument also engages the Minister and the Student Identifiers Registrar indirectly.

• Higher education providers. Providers bear the principal operational burden. They must determine SSAF amounts and publish them in specified form and by specified dates (ss 6, 10). Providers must limit and justify fee variations, provide departmental notice before varying SSAFs (s 9(1)(b)), publish census dates and EFTSL values on their websites on or before the earliest enrolment date (s 22(1)), calculate EFTSLs by reference to study load or credit points (ss 26-27), ensure information systems meet prescribed technical and security features if they use electronic communications (s 29), and implement methods for unique student identification and verification where electronic signatures are relied upon (s 30).

• Students. Students are recipients of publication and notice duties. They are the persons who pay SSAFs when liable (s 6(1)), who must be able to work out the SSAF from published information (s 6(1)), and who receive Commonwealth Assistance Notices containing prescribed content (s 17). Students’ rights include being informed of decisions and their right to review (s 15 note referencing AAT Act s 27A; s 17(9) referencing rights under the Act). Students who study part‑time are entitled to an SSAF of no more than 75 per cent of the full‑time maximum for comparable categories (s 7(1)).

• Department of Education (and Minister). The Department is the recipient of provider notifications about intended SSAF variations (s 9(1)(b) requires written advice to ssaf@dese.gov.au or other notified email). The Minister must give written approval for certain variations to published census dates or EFTSL values before the provider may vary them (s 23(1) refers to paragraph 169‑25(4)(b) of the Act).

• Student Identifiers Registrar and USI framework. The Guidelines recognise and incorporate the Unique Student Identifier (USI) and Student Identifiers Registrar established under the Student Identifiers Act 2014 into CAN content (s 4 definitions; s 17(2)(d)). Providers issuing identifiers must verify identity and secure identifiers (s 30(3)).

• Overseas higher education institutions and accelerator providers. Special rules affect domestic students studying with overseas institutions when credit is counted towards an Australian course: EFTSLs must mirror the EFTSL that would have been assigned if the unit were taken at the Australian provider (s 28). Accelerator program courses have bespoke EFTSL treatment and publication obligations (ss 21(2), 22(2), 28A).

• Administrative-review bodies. The Guidelines explicitly reference administrative review rights and procedural requirements, including the provider’s method of publication for decisions and the need to inform affected persons of review rights under the Administrative Appeals Tribunal Act 1975 (s 15 and its notes).

Who pays: students who are liable for SSAFs and those taking units that generate HELP debts. Who decides: providers set fees, publish EFTSLs and census dates, and operate information systems within the constraints of the Guidelines; the Minister must approve certain variations; the Department receives notice of variations.

The Guidelines allocate specific duties to higher education providers and set out rights for students. The wording is prescriptive on content, timing and procedural safeguards.

Duties of higher education providers

• Publish sufficient SSAF information at the time of determination (s 6(1)): amount (GST inclusive), period to which it relates, and persons/categories required to pay. Providers must not take into account payment timing or the Commonwealth’s HELP payments when determining the SSAF (s 6(2)). Providers may differentiate fees across reasonable categories including zero fees (s 6(3)).

• Limit SSAF for part‑time students (s 7): a part‑time student (study load of less than 75 per cent of normal full‑time load per s 7(2)) must be charged no more than 75 per cent of the full‑time maximum determined by the provider.

• Set the payable day: the SSAF payable day must not be earlier than the last day a student required to pay can enrol (the enrolment closing date specified by the provider) for the course/period to which the fee relates (s 8(1)-(2)).

• Vary fees and dates only in limited circumstances and with notice: providers may vary a SSAF or the payable day only where necessary because of circumstances that did not apply when originally determined or to correct administrative errors, and must advise the Department in writing at least five working days before making the variation (s 9(1)(a)-(b)). Variations in the two months before course commencement are further limited to those not disadvantaging any person (s 9(2)). Providers must publish any varied fee or payable day no later than two weeks after variation (s 11(2)).

• Publication timelines for SSAF: providers must publish SSAF details and the required notice by 1 October for fees payable in the following First Half Year and by 1 April for fees payable in the Second Half Year (s 10(2)).

• CAN content and timing: providers must give CANs to persons who meet the statutory requirements (s 16) and ensure notices include the specified list of student, unit and assistance details (s 17(1)-(6A)). CANs that relate to units for Commonwealth Supported Students or those who sought FEE‑HELP assistance must be given within 28 days of the earliest census date indicated (s 18(1)). CANs for SA‑HELP or OS‑HELP and STARTUP‑HELP have specific timing rules (s 18(2)-(4)).

• Publish census dates and EFTSL values: providers must publish these on their websites on or before the earliest enrolment date for the unit or accelerator program course (s 22(1)). Where providers publish EFTSLs for accelerator program courses they must also publish how the EFTSL was determined (s 22(2)).

• EFTSL calculation: providers must determine EFTSL values by reference to study load (s 26(1)-(3)), may use credit points (s 27(4)), and must calculate proportions such that aggregated EFTSLs for a full‑time year add as close as possible to 1.0 (s 27(3)).

• Information system requirements: electronic systems used for giving or receiving notices must be accessible, secure, able to store and make documents available, generate date fields and printable receipts, and enable unique student identification and approval (ss 29-30). Where providers issue identifiers, they must verify identity, take precautions against unauthorised access, and advise students they are responsible for protecting the identifier (s 30(3)).

Rights of students

• Information and notice: students have the right to receive CANs with mandated content (s 17) and to be informed of decisions and review rights (s 15 note).

• Time to receive notice: CANs must be provided within set timeframes (s 18), providing students with certainty about liabilities and HELP balances in a defined window relative to census dates and debt incurrence.

• Right to correct information: notices must include information about the person’s right to request correction under relevant Act provisions (s 17(9)).

• Protection against disadvantage through variation: the Guidelines constrain providers from varying SSAFs, payable days, census dates or EFTSL values in ways that disadvantage students; variations are permitted only under narrow circumstances and with Ministerial or departmental involvement where required (ss 9, 11, 23).

These duties and rights are operational rather than novel entitlements. They create administrative compliance obligations for providers and procedural protections for students tied to statutory timetables and data content requirements.

The Guidelines do not themselves introduce new criminal offences or specify monetary penalties. The instrument is a set of administrative directions made under s 238-10 of the Act (s 3), and therefore operates as subordinate legislation implementing the Act. Enforcement and penalty mechanisms are therefore to be found in the Act and other statutes rather than in these Guidelines. The Guidelines do, however, create administrative compliance hooks and reporting/notification obligations that interact with enforcement mechanisms in the Act.

What the Guidelines require in enforcement terms

• Notification obligations. Providers must give written notice to the Department before varying a SSAF (s 9(1)(b): at least five working days’ prior notice to the email address specified) and obtain the Minister’s written approval before varying published census dates or EFTSL values in circumstances requiring such approval (s 23(1) referencing paragraph 169‑25(4)(b) of the Act). Failure to provide required notices may expose providers to whatever compliance processes the Department and Act authorise.

• Recordkeeping and IT security. The Guidelines mandate specific features for any information system used for electronic communications (s 29). Non‑compliant systems increase the risk of procedural non‑compliance with the Act’s notice requirements, which could trigger administrative follow‑up.

• Administrative review. The Guidelines reinforce the pathway for review via the Administrative Appeals Tribunal Act 1975. The provider must determine the method for publication of its decision and must notify affected persons of the decision and their right to seek AAT review (s 15 note referencing s 27A of the AAT Act). Time limits for applying for review are set out in the Act and reiterated in the note (see s 15 note referencing s 209‑10 of the Act).

• Statutory remedies and compliance tools (contextual). While the Guidelines are silent on penalties, the Act provides mechanisms for compliance, including registration conditions, funding consequences, directions and other administrative remedies. The Guidelines’ detailed procedural prescriptions increase the Department’s ability to identify non‑compliance (for example by checking whether providers meet publication and timing obligations in ss 10 and 22).

Implementation risk and uncertainty

• The practical effect of the Guidelines is to create objective benchmarks against which the Department can measure provider compliance. Providers who fail to meet publication deadlines (s 10(2), s 22(1)), who vary fees or dates without the required departmental notice or Ministerial approval (ss 9, 23), or who operate deficient information systems (ss 29-30) may attract Departmental compliance action under powers in the Act, although the Guidelines do not set the sanctions themselves.

• The Guidelines place contractual and operational exposure on providers. Because the Guidelines prescribe the content of CANs (s 17), inaccurate or incomplete notices may result in statutory disputes under the Act about liability for HELP and the validity of enrolment transactions, and may drive applications for review.

In short, enforcement is through the Act and administrative review mechanisms; the Guidelines create the procedural baseline that determines whether enforcement or remedial action is warranted.

The Guidelines are explicitly tethered to the Act and to a small number of other statutes by definitions, cross‑references and procedural notes. The instrument operates as interpretive and procedural subordinate legislation: it fills out how providers must comply with specified Act provisions.

Primary statutory connections

• Higher Education Support Act 2003 (the Act). The Guidelines are made under s 238‑10 of the Act (s 3). Many provisions in the Guidelines are express procedural implementations of Act sections: for example, ss 6 and 10 implement subparagraph 19‑37(6)(a)(i) and paragraph 19‑37(5)(b) of the Act regarding SSAF publication and determination; ss 12-14 implement paragraphs 36‑13(3) and 36‑21(1) on special circumstances; Parts 4 and 5 implement various Pt 4 and related Act provisions, including relevant guidance on CANs and work experience definitions (e.g. ss 16-18 implement subsections 169‑5(1), (1A), and 169‑5(2)-(3) of the Act; ss 26-28 implement s 169‑28). The Guidelines are therefore an executable set of compliance rules for meeting statutory obligations under the Act.

• Student Identifiers Act 2014. The Guidelines adopt terms from the Student Identifiers Act,“Student Identifiers Registrar” and “Unique Student Identifier (USI)”,and require the inclusion of CHESSN or USI details on CANs where applicable (s 4 definitions; s 17(2)(d)). They also require providers issuing identifiers to verify identity and secure identifiers (s 30(3)), tying provider practice to the Registrar’s framework.

• A New Tax System (Goods and Services Tax) Act 1999. The Guidelines reference GST and require the SSAF amount published to be GST inclusive (s 4 definition of GST and s 6(1)(a)). This ties fee presentation to the federal GST regime for correct consumer disclosure.

• Administrative Appeals Tribunal Act 1975. Section 15 note references s 27A of the AAT Act, and the provider is required to notify affected persons of their right to review. The Guidelines therefore engage administrative review pathways.

Internal consistency and cross‑reference mechanics

• The Guidelines operate by translating Act references into operational checklists. For example, the Act requires that providers publish SSAF information; the Guidelines specify the items that must be published, the deadlines (s 10(2)), and the electronic access requirements (s 10(3)). Similarly, where the Act mentions EFTSL values and census dates, the Guidelines set the exact publication timing and how to calculate EFTSLs (ss 22, 26-27).

• Where the Guidelines require Ministerial approval for changes to published census dates or EFTSL values, they reference the process in the Act (s 23(1) refers to paragraph 169‑25(4)(b) of the Act). The Guidelines thereby allocate decision authority among the provider, the Minister and the Department, in line with the Act’s allocation of powers.

Limitations on the Guidelines’ legal effect

• The Guidelines are subordinate instruments; they do not create standalone criminal offences or civil liabilities beyond the Act’s framework. They are procedural directions for providers to meet statutory standards. Any sanction for non‑compliance will arise under the Act or other laws.

• The Guidelines contain notes which reference legal entitlements or other statutes (for example the AAT Act and the GST Act). Those notes are explanatory, and where the Guidelines set mandatory text or timing they take precedence as the operational rule under the Act.

Operational takeaways

• Providers must align their IT systems, identification procedures, publication schedules and fee‑setting methodologies with both the Guidelines and the Act. The Guidelines reduce ambiguity by specifying components that the Act leaves open, and in doing so make compliance a matter of ticking off the instrument’s checklists.

The instrument is styled as the Higher Education Support (Administration) Guidelines 2022 (s 1). The text supplied contains no schedule or record of prior amendments, revocations, or commencement dates beyond the text itself. The only explicit statement of authority is that the instrument is made under section 238‑10 of the Act (s 3). Because the Guidelines are subordinate legislation, any formal amendment or repeal would be recorded in the Federal Register of Legislation and in the instrument’s amendment history on the register; that history is not included in the text provided.

What the absence of an amendment log in the text implies operationally

• The instrument as provided must be read on its face as the active 2022 Guidelines, but users should not assume continuity or absence of subsequent amendment. The text contains internal references to dates (for example the “First Half Year” and “Second Half Year” defined to commence on 1 January 2013 or later years in s 4), indicating that some temporal scaffolding carries forward from earlier instruments or rules, but the instrument as supplied gives no account of prior or subsequent legislative changes.

• The Guidelines themselves impose reporting and notice requirements which presuppose ongoing Departmental administrative interaction (for example s 9(1)(b) prescribes the email address ssaf@dese.gov.au “or such other new email address as notified by the Department”). That drafting anticipates future administrative changes without listing an amendment history.

Practical consequence for compliance and legal research

• Practitioners and compliance officers should treat the Guidelines as subordinate legislation whose authoritative text and amendment history must be verified on the Federal Register of Legislation or via Departmental instruments. Because the Guidelines do not contain their own amendment schedule, any change in departmental email addresses, Ministerial approval procedures, or later amending instruments will be formally recorded elsewhere.

• The Guidelines’ references to other laws (Act, Student Identifiers Act, GST Act, AAT Act) remain operative. Any amendments to those primary statutes would affect the operation of the Guidelines even if the Guidelines themselves were unchanged.

In sum, the instrument’s text does not present a self‑contained amendment history. It is a current administrative instrument made under the Act, and its amendment record must be checked in the official legislative register when precise change history or commencement details are required.

The Guidelines themselves do not include or refer to any litigation history. The instrument contains no list of cases, no judicial interpretations, and no references to determinations or precedent. The only procedural avenue for contesting provider decisions explicitly mentioned in the text is administrative review: the provider’s method of publication for decisions must be determined by the provider and persons affected must be notified of their right to seek review under the Administrative Appeals Tribunal Act 1975 (s 15 notes). The Guidelines further require CANs to contain information about a person’s right, under subsections 169‑10(2) to (4) of the Act, to request correction of information contained in the notice (s 17(9)).

Implications of no litigation record in the text

• The Guidelines are framed as administrative directions for providers to implement the Act. Where disputes arise (for example over SSAF liability, CAN content, or whether circumstances are beyond a person’s control), the Act and established administrative law processes govern resolution. The Guidelines specify procedural thresholds that may be the subject of challenge , for example, whether a provider satisfied itself that a person’s circumstances were “beyond the person’s control” under s 12 , but they do not record any prior litigated interpretations.

• Where the Guidelines set objective content or timing requirements (for example publication dates, required CAN content), disputes about non‑compliance will likely be handled through administrative complaint mechanisms, departmental oversight and, if necessary, the AAT rather than being litigated under the Guidelines themselves. The instrument’s references to the AAT Act suggest administrative review is expected to be the principal forum for contesting provider decisions that rest on the Guidelines’ provisions.

How practitioners should approach this gap

• Absent a litigation history in the instrument, practitioners should rely on the Act and administrative law principles for adjudication of disputes and should not expect the Guidelines to be read as settled through judicial decisions. When advising clients, consider the procedural hooks the Guidelines create , publication timing, notice content, IT security, and variation rules , as the likely grounds for administrative review or departmental action rather than as matters that have been definitively litigated.

• Because the instrument integrates with broader statutory frameworks (Act, AAT Act, Student Identifiers Act), potential litigation or review outcomes will hinge on the interaction between those primary statutes and the Guidelines’ operational rules. The absence of litigation history in the text means that claims about how courts have interpreted these rules cannot be grounded in this instrument alone.

The Guidelines carry a number of specific operational traps and fine‑print requirements that can generate compliance risk if not attended to carefully. Below are concrete items that practitioners and compliance officers should check when implementing the Guidelines, with citations.

1. Publication must enable calculation and be GST inclusive (s 6(1), s 4 definition of GST)

• The provider must publish the SSAF amount as GST inclusive (s 6(1)(a)), and must publish enough information at the time of determination to enable a person liable to pay to work out the amount (s 6(1)). Publishing only net amounts or excluding GST in disclosures risks non‑compliance.

2. Do not factor timing or Commonwealth HELP payments into SSAF setting (s 6(2))

• When determining SSAF amounts, providers must not have regard to “any matter related to the manner or timing” of a person’s payment, nor to the Commonwealth’s HELP payment to the provider (s 6(2)). Using payment timing incentives or reliance on Commonwealth disbursement timing in fee design is prohibited.

3. Part‑time cap defined by study load, not by enrolment status (s 7)

• The 75 per cent cap for part‑time students is defined by study load being less than 75 per cent of the normal full‑time student load for the period (s 7(2)). Providers must ensure operational definitions of part‑time conform to study load percentages, not to informal enrolment labels.

4. Payable date cannot be earlier than enrolment closing date (s 8)

• The SSAF payable day must not be earlier than the last day a student required to pay can enrol (s 8(1)). Setting invoices or payable deadlines before the enrolment closing date breaches the Guidelines.

5. Variations limited, require departmental notice and, in some cases, Minister approval (ss 9, 23)

• Providers may only vary SSAFs or payable days in narrow circumstances (s 9(1)(a)) and must advise the Department in writing at least five working days before making the variation (s 9(1)(b)). Variations to published census dates or EFTSL values require Ministerial approval and must not disadvantage students (s 23(1)). Failure to obtain required approvals or to give required notice is a compliance risk.

6. Two‑month pre‑commencement window stricter (s 9(2))

• Any variation within the two months prior to course commencement must not disadvantage enrolled or prospective students (s 9(2)). Providers should define and document how they assess “not disadvantage” in case of challenge.

7. Online publication requires accessible information system (ss 10(3), 11(3), 22(1), s 29)

• If providers publish required information only via the Internet or electronic formats, they must also provide students with access to an information system through which the student can access the information (s 10(3), s 11(3), s 22(1)). The information system itself must be accessible, secure, able to store documents and generate receipts and date stamps (s 29). Simply posting PDFs on a public website without student access mechanisms may not meet the instrument’s requirements.

8. CANs have extensive mandatory content and prominent statements (s 17)

• CANs must include a long list of details (s 17(2)-(3), (5)-(6A)) and must prominently display required HELP statements (s 17(7)-(8)). Missing items or failure to display those statements prominently may amount to defective notices.

9. Timing: 28‑day windows for CANs and SA/OS/STARTUP notices (s 18)

• CANs for Commonwealth Supported Students and those seeking FEE‑HELP must be given within 28 days of the earliest census date indicated (s 18(1)); SA‑HELP/OS‑HELP/STARTUP‑HELP have their own deadlines (s 18(2)-(4)). Providers should map notice workflows to these statutory windows.

10. EFTSL arithmetic precision and aggregation requirements (ss 26-27)

• EFTSLs must be calculated to whatever number of decimal places required to make aggregated EFTSLs for a full‑time year add as close as possible to 1.0 (s 27(3)). Rounding and truncation practices for reporting must be carefully overseen to avoid aggregate errors.

11. Overseas unit EFTSLs must match domestic equivalent (s 28(2))

• For domestic students crediting overseas units, the EFTSL value must equal what would be assigned if the unit were taken at the Australian provider (s 28(2)). Providers cannot assign ad hoc or lower EFTSLs for overseas study without justification.

12. Accelerator program EFTSLs and disclosure (ss 21(2), 22(2), 28A)

• EFTSLs for accelerator program courses must be published with an explanation of how they were determined (s 22(2)), and must be measured by reference to full‑time completion time (s 28A). Providers operating accelerator courses must document time‑based calculations.

13. Identity and signature procedures require verification before issuing identifiers (s 30(3))

• Where providers issue unique personal identifiers, they must verify identity before issuing, take precautions against unauthorised access, and advise students they are responsible for protecting the identifier (s 30(3)). Lax verification exposes providers to data integrity and legal risk.

14. “Beyond a person’s control” is a reasonableness test with examples but flexible application (s 12)

• The Guidelines require providers to be reasonably satisfied that circumstances were not due to the person’s action/inaction and were unusual or abnormal (s 12). The test is fact‑sensitive and invites evidentiary evaluation; inconsistent application across cohorts could be challenged administratively.

15. Provider discretion over method of publication of decisions but obligation to notify affected persons (s 15)

• The provider chooses the publication method (s 15) but must notify affected persons of decisions and their review rights; simply publishing on a website without targeted notification could fail the obligation under s 15 note.

Attention to these details, along with documentation of the provider’s decision‑making and publication processes, is essential to manage administrative and legal risk. Each “gotcha” arises from a provision that tightens what might otherwise be a loose statutory requirement.

This section sets out practical, source‑grounded compliance steps for higher education providers based on the Guidelines’ prescriptions. Follow the cited provisions.

1. SSAF determination and publication

• At the time the SSAF is determined, publish the amount as a GST inclusive figure, the period to which the fee relates, and the persons or categories required to pay (s 6(1); s 4 definition of GST). Ensure that categories are reasonable and documented (s 6(3) note provides examples: mode of attendance, course type, equity status).

• Do not factor in the manner or timing of a student’s payment or Commonwealth HELP payments into SSAF calculation (s 6(2)). Record the fee rationale and the exclusion of these factors in your fee determination file.

• For part‑time students, ensure the fee does not exceed 75 per cent of the full‑time maximum for the period; define part‑time by study load less than 75 per cent of normal full‑time load and document how study load is calculated (s 7(1)-(2)).

• Publish SSAF information and the notice under s 19‑37(6)(a)(ii) by statutory deadlines: by 1 October for fees payable in the following First Half Year, and by 1 April for fees payable in the Second Half Year (s 10(2)). If publishing electronically only, provide students with access to an information system to view the information (s 10(3)).

2. Variation procedures

• Limit variations of SSAF or payable day to circumstances that did not apply at the time of determination or to correct administrative errors (s 9(1)(a)). For any intended variation, advise the Department in writing at least five working days before making the variation to ssaf@dese.gov.au or any new address notified by the Department (s 9(1)(b)). Keep copies of the written advice and any Departmental response.

• Variations in the two months before course commencement must be reasonably satisfied not to disadvantage any person; document the assessment of disadvantage and retain evidence (s 9(2)-(3)). Publish the varied fee or payable day no later than two weeks after making the variation and ensure electronic access if published online (s 11(2)-(3)).

3. Payable day and enrolment alignment

• Set the SSAF payable day to be no earlier than the enrolment closing date for the course or bridging course for overseas‑trained professionals to which the fee relates (s 8(1)-(2)). Maintain clear records of enrolment closing dates and proof of publication.

4. Commonwealth Assistance Notices (CANs)

• Ensure CAN templates include all required information at unit and notice levels as listed in s 17(2)-(6A), including CHESSN/USI where applicable and STARTUP/OS/SA help details. Prominently display the HELP balance and Commonwealth assistance statements required by s 17(7)-(8).

• Deliver CANs within statutory timeframes: within 28 days of the earliest census date for Commonwealth Supported Students and those seeking FEE‑HELP (s 18(1)); SA‑HELP notices by the later of 28 days after SA‑HELP debt incurrence or the date in s 18(1) where both fall in the periods in s 21(1) (s 18(2) note); OS‑HELP within 28 days of OS‑HELP debt incurrence (s 18(3)); STARTUP‑HELP within 28 days of the earliest census date (s 18(4)). Maintain delivery logs and date stamps.

• Include information about students’ right to request correction under the Act (s 17(9)). Keep an auditable corrections process.

5. Census dates and EFTSL publication and calculation

• Publish census dates and EFTSL values for units and accelerator program courses on the provider’s website on or before the earliest enrolment date for those units or courses (s 22(1)). For accelerator program EFTSLs, also publish how the EFTSL was determined (s 22(2)).

• When determining a census date, ensure it falls not less than 20 per cent into the period between commencement and completion for the unit or course (s 25). Document how the commencement/completion dates and percentage calculations were arrived at.

• Calculate EFTSL values by reference to study load (s 26(1)-(3)). Use credit points to allocate relative unit values where appropriate (s 27(4)), and calculate decimal precision so aggregated EFTSLs for a standard full‑time year add as close as possible to 1.0 (s 27(3)). Retain calculation workpapers showing the decimal methodology and rounding/truncation rules for reporting.

• For domestic students doing units at overseas institutions, assign the EFTSL equal to the EFTSL that would be assigned if the unit were undertaken at the Australian provider (s 28(2)). Keep equivalence comparisons and supporting documentation.

• For accelerator program courses, determine EFTSL by reference to the time taken to complete the course on a full‑time basis (s 28A). Record the full‑time completion time and the method used to convert time to EFTSL.

6. Work experience and exemptions

• For units that wholly consist of work experience in industry, ensure independence from provider‑staff involvement if the aim is to treat students as exempt: if interaction, placement organisation, ongoing monitoring and assessment are all performed by provider staff or persons engaged by the provider, the student is not an exempt student (s 20). Conversely, document that an industry placement provider, not provider staff, performs these functions if exemption is claimed.

• For the Schedule 1(d) definition of “work experience in industry”, ensure that ongoing and regular input, oversight, curriculum definition and standards management are not all performed by provider staff where the placement is asserted to be industry‑led (s 19).

7. Electronic communications and identifiers

• Design and test any information system used for electronic communications to meet s 29(1)(a)-(e): accessibility, security, storage for subsequent reference, unique student identifier and date generation for HELP requests, and printable receipts. Where the provider uses electronic means to give notices to students, ensure students are informed direct or via publications and are authorised to use the system (s 29(2)-(3)).

• Implement methods for students to uniquely identify themselves and indicate approval of electronic documents (s 30(1)-(2)). If issuing identifiers internally, verify identity before issue, take precautions to prevent unauthorised access, and advise students of their responsibilities (s 30(3)(a)-(c)). Keep verification logs and policies.

8. Records, audit trails and publication access

• Maintain auditable records of all publications, notices, departmental notifications, Ministerial approvals, CANs sent, and student acknowledgements. Where publications are online only, provide students with access to the specific information system that stores the records (ss 10(3), 11(3), 22(1)).

9. Document procedures and staff training

• Produce written SOPs that map each statutory deadline and required content element in the Guidelines to operational staff responsibilities. Train enrolment, finance and legal/compliance teams on the specific constraints, such as the ban on using payment timing in SSAF determinations (s 6(2)) and the 75 per cent cap for part‑time students (s 7).

10. Prepare for administrative review and complaints

• Establish internal review procedures for decisions covered by the Guidelines (noting s 15 and the AAT review route). Ensure affected students are notified of their right to review and the timelines for lodging reviews (s 15 note referencing s 209‑10 of the Act).

Adherence to these steps, and retention of contemporaneous documentation proving compliance with each cited section, will materially reduce the risk of administrative challenge and improve transparency in audit and reporting interactions with the Department.