Tertiary Education

A student lifecycle, not a single system

Tertiary providers are trying to move a person from prospect to graduate without losing the record that proves what happened. That path crosses recruitment, admissions, enrolment, learning, student finance, identity, communications and government reporting. The student management system is usually the student system of record. It is not the system of record for confirmations of enrolment, HELP entitlement, VET transcripts or VET product names.

University and higher-education work is organised around the course and unit of study, census, EFTSL, HELP, the handbook and Academic Board. VET work is organised around the qualification and unit of competency, the training plan, AVETMISS, the USI transcript and training.gov.au. Dual-sector providers answer to both TEQSA and ASQA, and often still run historically separate student systems. International delivery sits on all of those. It is a mode, not a third sector.

This page is for people who live those joins: student administration, international and admissions, RTO compliance, student systems, student fees and the operations staff who still move files between systems when the joins fail.

What providers are trying to do

Fill places within funding and enrolment settings. Enrol and bill correctly. Deliver and assess the accredited product. Keep students progressing. Report and remain registered. Confer awards. Protect visa integrity.

Universities weight recruitment, census, HELP, the handbook and academic governance. TAFEs and RTOs weight funding claims, training plans, AVETMISS, USI and audit evidence. Private CRICOS providers weight agents, CoEs, transfers and written agreements.

How the environment is usually arranged

Large providers typically run a university-scale SMS such as TechnologyOne Student Management, Tribal Callista or SITS, Ellucian Banner or PeopleSoft Campus Solutions, with a separate LMS, a curriculum or handbook source, a CRM or TAC pathway for domestic applications, and campus identity. Private RTOs and many CRICOS providers run a different class of SMS, such as aXcelerate, VETtrak, Wisenet or Meshed, often expecting SMS and LMS to sit closer together.

Government systems sit beside all of that and own their own records: PRISMS for CoEs and the agency hierarchy, TCSI for HELP and related entitlement, NCVER for VET activity, USI, eCAF, training.gov.au for VET product names, and Home Affairs for visas. Finance, payments, timetabling, academic integrity and reporting tools attach around the SMS. None of those products is interchangeable with the others just because a vendor says they integrate.

Where the work usually breaks

The expensive work is the handoff.

• An accepted application has to be re-entered before enrolment.
• The CoE in PRISMS and the enrolment in the SMS do not match.
• LMS gradebook and official SMS results diverge until someone imports a file.
• AVETMISS fails because the program name does not exactly match training.gov.au.
• TCSI rejects packets and HELP stays wrong until the SMS is corrected.
• Agent, student and commission data live in three places.
• Dual-sector or partner delivery still moves on CSV.
• Only one person can run the government return.
• Handbook, SMS and website describe different courses.

Those are records and process problems. They show up as late census, failed lodgement, unpaid or unlawful commission, a student who cannot get a transcript, or an audit that cannot reconstruct what staff believed had already been done.

Rules that change the work

TEQSA and the Higher Education Standards Framework govern higher education. ASQA and the 2025 Standards for RTOs govern VET. ESOS, the National Code, CRICOS and PRISMS govern overseas students. HESA, HELP, VSL and TCSI govern student finance reporting. A USI is required for a VET award and for HE conferral. This is not legal, regulatory or migration advice, and Ryoss Labs does not determine whether a provider is complying.

What matters for systems is simpler: some records are owned by government systems the institution does not control, and some dates cannot move because the academic calendar, a lodgement window or a visa clock does not move.

What is changing now

The National Code now bans paying an education-agent commission where the receiving provider accepts an onshore transfer after 31 March 2026. Students can still transfer. The receiving provider cannot pay commission on that acceptance, with stated exceptions for first enrolment, packaged-visa progression, study after the principal course finishes, and acceptances on or before that date. That change reaches agent contracts, CRM commission rules, finance, and the flags that mark a transfer in StudyLink or the SMS.

CRICOS providers must also complete the first PRISMS agent-commission collection, covering 1 January to 30 June 2026 and due 30 October 2026. Direct and indirect commissions and non-monetary benefits are in scope, and a nil return is still a return. That forces a three-way reconcile between finance, agent identity and CoEs.

ASQA has suspended new CRICOS provider applications and applications to add CRICOS courses from 19 May 2026 to 19 May 2027, with exemptions including government schools, public TAFE and HESA Table A providers. From 5 October 2026, BSB80120 Graduate Diploma of Management (Learning) is not available to overseas students. Later HESF governance changes and AVETMISS 8.1 are dated into 2027. The 2026 new overseas student commencements planning level is a visa-processing priority, not a hard enrolment cap.

What is worth improving

Leave the SMS in place unless there is a clear reason to replace it. The useful work is usually around it: CRM or StudyLink to SMS, SMS to LMS, SMS to PRISMS, SMS to TCSI, partner-provider files, commission packs, agent-portal rules that block an unlawful commission, identity for staff, agents and partner users, and the operational reports people currently rebuild in spreadsheets every census or lodgement week.

Integration is the usual starting point, including API development and automation where the transfer is repeatable, or robotic process automation where a government or vendor screen has no reliable API. Software development fits student or staff portals and the internal tools that replace a spreadsheet-critical process. Technology advisory is the wrap-versus-replace decision and the sequence around the academic calendar. Hosting and infrastructure matters when those integrations have to survive census and lodgement weeks.

AI only fits narrow jobs such as classifying documents, drafting an enquiry reply or retrieving handbook and policy text, and never as the authority for enrolment, results, visa or funding decisions.

We have particular experience in Australian education, where student systems, compliance reporting and the academic calendar all limit when and how things can change. If a join in that lifecycle is costing time or producing the wrong record, tell us about the work.