ERP for Melbourne universities: managing multi-campus complexity.

Melbourne is home to a remarkable concentration of higher education. The University of Melbourne, Monash, RMIT, Deakin, La Trobe, Swinburne, Victoria University, and the Australian Catholic University together educate hundreds of thousands of students across dozens of campuses, operate multi-billion-dollar research portfolios, and manage corporate groups that include hospitals, publishing arms, continuing education companies, and joint ventures with industry partners. Behind every one of these institutions sits a finance and administration operation that rivals a mid-cap ASX company. And the ERP that runs it has to cope with complexity that generic implementations simply weren’t designed for.

This guide covers what Victorian universities need from an ERP implementation, which platforms are worth considering, and how to avoid the mistakes that turn a multi-year digital transformation into a multi-year headache.

Why University ERP Is Different

Universities are not commercial businesses wearing an education badge. The operating model produces four distinct finance challenges that any ERP implementation has to handle from day one.

• Research fund accounting. Research grants from ARC, NHMRC, MRFF, CRC, and industry partners are restricted funds with acquittal obligations. The ERP must track income, expenditure, commitments, salary on-costs, and indirect cost recovery against each project, and generate acquittal reports in the format each funder requires. Treating a grant like a general revenue account guarantees a reportable compliance failure.
• Student finance. Student fee cycles, FEE-HELP and HECS-HELP administration, scholarship management, census dates, and the complex interplay with Callista or PeopleSoft Campus Solutions all sit somewhere between the student system and the ERP. Bad integration means students see incorrect balances, finance teams run parallel spreadsheets, and reconciliation becomes a full-time job.
• Multi-entity consolidation. Most Victorian universities operate through a group of controlled entities: a foundation, a commercial arm, one or more trading subsidiaries, hospitals or clinics, research institutes, and joint ventures. Each entity needs its own statutory accounts while the group needs consolidated reporting for TEQSA, the Department of Education, and sector benchmarking.
• TEQSA and HEIMS reporting. The Tertiary Education Quality and Standards Agency requires specific financial and operational data on a defined cadence. HEIMS submission for student load, FEE-HELP liability, and other regulatory data demands data structured in ways commercial ERP systems don’t produce out of the box.

Which Platform Fits

Microsoft Dynamics 365 Finance & Operations

A strong option for Victorian universities in the mid-to-upper enterprise bracket. D365 F&O handles multi-entity consolidation natively, integrates well with Microsoft 365 (which most universities already run), and the Power Platform layer provides flexibility for research fund accounting and TEQSA reporting extensions. Integration with Callista or PeopleSoft Campus Solutions is a known pattern with mature connectors. The platform scales across a university group including hospitals and commercial arms.

SAP S/4HANA

A solid choice for the largest Victorian universities with complex research portfolios and international operations. SAP’s Public Sector Management module handles fund accounting natively, which maps well to research grant administration. The platform’s strength is deep financial and supply chain capability; the trade-off is implementation complexity and cost. Several Group of Eight universities globally run SAP.

TechnologyOne

Purpose-built for the Australian higher education sector. TechnologyOne’s Student Management and Financials products are designed around sector-specific requirements including TEQSA reporting, Callista integration, and research grant lifecycle management. The platform’s main strength is domain alignment; the main consideration is flexibility when institutional requirements diverge from the sector template.

Oracle Cloud ERP

Best suited for universities that have already chosen Oracle elsewhere in their technology stack, or that need the PeopleSoft Campus Solutions path of least resistance. Oracle Cloud Financials and the Grants module provide strong research accounting capability, and integration with PeopleSoft is natively supported.

The Research Grant Problem

This is where most generic ERP implementations fail universities. Standard accounting software tracks income and expenses by account code. Research grant management needs to track them by project, funder, and reporting category. Simultaneously. And against commitments that may span years.

A single NHMRC Project Grant involves salary on-costs (across multiple researchers and cost centres), consumables, equipment, travel, indirect cost recovery, and student stipends. All of these must be captured against the same project, compared to the budget, and reported in NHMRC’s required format at year-end. If any allocation is wrong, the acquittal is wrong, and the institution’s relationship with its largest funder is at risk.

Purpose-configured ERP solves this by building the grant structure into the chart of accounts with multi-ledger capability. When a salary journal is posted, the system splits on-costs across the relevant grants automatically. When a purchase order is raised, project and category coding is mandatory. When indirect cost recovery runs, the journal is generated automatically against the configured recovery rate. The result is a grant acquittal the research office can trust. Because the data entered the system correctly in the first place.

Student System Integration

The Callista or PeopleSoft Campus Solutions integration is one of the highest-risk interfaces in any university ERP implementation. Student fee balances, scholarship awards, HECS-HELP liability, and payment receipts must flow between the student system and the ERP reliably and in real time. Students log in expecting to see accurate balances; academic advisers need to see enrolment and finance in one view; finance teams need to reconcile tuition revenue against student load.

Successful integration starts with mastering the data model on both sides. Specifically, how Callista structures students, enrolments, fees, and payments versus how the ERP structures customers, contracts, and invoices. The next step is designing the interface architecture with clear responsibility: which system is the source of truth for each data element, how reconciliation is performed, and what the error handling looks like when a message fails. Then comes the build and testing, including reconciliation of tuition revenue across multiple census dates and stress testing with realistic volume.

Multi-Campus and Multi-Entity Reality

A Victorian university group commonly includes the university itself, a commercial entity (often running short courses and executive education), a foundation for philanthropic activity, hospitals or clinical entities (for medicine, dentistry, veterinary science), research institutes, and joint ventures. Each is a separate legal entity with its own statutory reporting, but the group needs consolidated views for executive decision-making, TEQSA reporting, and sector benchmarking.

The ERP must handle this natively. Entity structures should reflect the actual governance, with intercompany transactions automated (so a service rendered by the commercial entity to the university is recognised as revenue in one and expense in the other with appropriate eliminations). Consolidated reporting must produce group views without manual aggregation. Security must restrict access appropriately. Staff in the commercial entity shouldn’t see research project detail, and vice versa.

Multi-campus complexity adds another layer. Different campuses may have different fee structures, different research cost recovery rates, and different operational cost centres. Identity management must treat the student and staff member as the primary identity, with campus as a context that affects what they see and do. Single sign-on, federated identity, and role-based access are not optional extras. They’re the foundation of any workable university ERP.

Data Migration from Legacy Systems

Victorian universities commonly run a mix of older ERP systems. TechnologyOne v18, Oracle EBS, PeopleSoft Financials. With decades of transactional history. Migrating requires careful planning because university data is inherently complex: grants have acquittal periods spanning years, student fee balances can involve retrospective adjustments, and historical cost centre structures have often been reorganised multiple times.

A zero data loss approach means migrating not just current financial data, but historical grant records, completed research projects, student fee histories, and scholarship awards. For universities operating on the same ERP platform for twenty years, this can mean tens of millions of transactions. The migration process should include comprehensive data mapping, automated reconciliation at every stage, parallel running of old and new systems for at least one full financial period, and a tested rollback plan. Reconciliation of grant balances, student tuition balances, and consolidated group financials must be perfect at cutover. Everything built on the ERP depends on it.

Getting It Right the First Time

University ERP implementations fail when they’re treated as generic accounting upgrades. The university ends up with a system that produces lovely consolidated accounts but can’t track a research grant, can’t reconcile tuition revenue against HEIMS submission, and can’t produce an acquittal report without a spreadsheet and a pot of coffee.

The right approach starts with university-specific discovery: understanding your research portfolio, grant acquittal cycles, student finance model, multi-entity structure, and TEQSA reporting requirements before any platform is configured. The technology serves the workflow, not the other way around. And the workflow, in a university, is shaped by generations of academic governance, funder requirements, and sector-specific practice that the average ERP consultant has never encountered.