Tertiary Education

Systems integration, software and technical advisory for Australian universities, TAFEs and RTOs, focused on the joins between the student management system, the LMS, the CRM and government reporting.

For student administration, admissions and international teams, RTO compliance staff, student systems owners and the operations staff who still move files between systems when a join fails.

Where the work usually breaks

  • An accepted application is re-entered

    Offers and acceptances sit in a CRM or application portal and have to be keyed again into the student management system before enrolment can start.

  • The CoE and the enrolment disagree

    The confirmation of enrolment in PRISMS and the enrolment in the student management system drift apart, and nobody notices until a student, an agent or an audit asks.

  • Results exist in two places

    The LMS gradebook and the official results diverge until someone imports a file, which delays transcripts and progression decisions.

  • A government return depends on one person

    AVETMISS, TCSI or PRISMS reporting runs only while the one person who knows the steps is in, and a mismatched program name or a rejected packet stops the run.

  • Agent, student and commission data live apart

    Agent contracts, commission rules and student records sit in three systems, which makes the National Code limits on commission hard to apply and harder to show.

  • The handbook, the SMS and the website disagree

    Course information is kept in the handbook, the student management system and the website separately, so one course is described three ways.

What we do

  • Connect the student systems

    Integrations between the CRM or application pathway, the student management system, the LMS, PRISMS and TCSI, built so each record has one owner and failures are visible.

  • Automate the repeatable transfers

    Scheduled and event-driven transfers for enrolment, results and agent data, and robotic process automation where a government or vendor screen has no reliable API.

  • Build portals and internal tools

    Student, staff and agent portals, and the internal tools that replace a process now held together by a spreadsheet, writing back to the system of record.

  • Advise on wrapping or replacing

    An independent view on whether to replace a system or build around it, and a sequence that respects the academic calendar, census and lodgement windows.

  • Keep it running through peak weeks

    Hosting, access and monitoring for the integrations that have to survive census, lodgement and enrolment peaks.

Describe the problem to us

Book a free 15 minute call and tell us what is going wrong and which systems are involved.

What you end up with

  • An agreed owner for each record

    A written list of which system owns each student, enrolment, agent and result record, and how conflicts between them are settled.

  • Transfers that report their own failures

    Integrations and automation that log what they did, retry sensibly and alert a named person when a transfer or a lodgement packet fails.

  • Something staff can run without us

    Documentation, credentials and monitoring set up so student administration and IT can operate and change the result, including around census and lodgement weeks.

How a typical engagement works

  1. 01Discovery
  2. 02Design
  3. 03Build and test
  4. 04Handover
  5. 05Support

01Discovery

Follow a record through the lifecycle

We trace a student from enquiry to graduation, or an agent from contract to commission, and list every system, file and person the record passes through.

02Design

Decide what is wrapped and what changes

We settle which system owns which record, which joins to fix first and what can wait, treating census, enrolment and lodgement dates as fixed.

03Build and test

Build in stages around the calendar

Work is delivered in small stages kept clear of census, enrolment and lodgement peaks, and each integration is tested on realistic data before it touches a live record.

04Handover

Train staff and hand over

Student administration and IT staff are shown the changed process, and credentials, alerting and documentation are handed over so the result can be run without us.

05Support

Support as the rules change

After handover, support can continue in the background as vendors, government systems and reporting requirements change.

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.

Frequently Asked Questions

Do we have to replace our student management system?

No. Replacement is rarely the first step. Most of the useful work is around the system: the joins to the CRM, the LMS, PRISMS and TCSI, and the reports staff rebuild every census. We advise on replacement only where there is a clear reason.

Does it matter which student system we run?

It matters how the system can be reached. Large providers commonly run products such as TechnologyOne Student Management, Tribal Callista, SITS or Ellucian Banner, and private RTOs often run aXcelerate, VETtrak, Wisenet or Meshed. We look at the API, database or file options each one offers before choosing an approach.

Can you connect to PRISMS, TCSI and other government systems?

These systems own their own records and have their own submission rules, so the work is to prepare and check the data we send and to handle rejections. Where a government screen has no reliable API, robotic process automation can be an option, subject to the terms of use of that system.

Can you help with AVETMISS and other reporting?

We build and repair the data flows that feed a return, so program names, enrolments and results match what the return expects before the run. We do not advise on whether a provider complies with TEQSA, ASQA or ESOS requirements.

Is this regulatory or migration advice?

No. We implement systems and do not determine whether a provider is complying with its obligations. We work with the compliance, admissions and student administration staff who do.

How do you avoid disrupting census and lodgement periods?

Changes are planned around the academic calendar. Work is staged and tested in a separate environment, and kept away from census, enrolment and lodgement windows unless the provider asks otherwise.

How do the National Code commission changes affect our systems?

They reach agent contracts, CRM commission rules, finance and the flags that mark a transfer. We help the data line up so the rules can be applied and shown. Whether a particular payment is permitted is a question for the provider and its advisers.

Where is AI useful in a tertiary provider?

In narrow jobs such as classifying documents, drafting a reply to an enquiry or retrieving handbook and policy text. It is never the authority for enrolment, results, visa or funding decisions.

How do we get started?

Book a free 15 minute discovery call and describe the problem and the systems involved. We tell you whether and how we can help. The call carries no obligation, and you can send a written enquiry instead if you prefer.

Start with a conversation

Book a free 15 minute call. Describe the problem, the systems involved and what you already know, and we will tell you plainly whether we can help and what a sensible next step looks like. There is no obligation.