ERP for universities: teaching on a live system

Why teach on a live ERP system

Teaching on a live ERP system means students post real documents in a working ledger and see the consequences: a sale that moves stock, tax and receivables at once, a closed period that refuses a late posting, an audit trail that names the user. It matters because graduates are hired to work inside these systems, and integration and controls are hard to teach from a textbook alone.

A textbook presents accounting one topic at a time: a chapter on receivables, another on inventory, another on VAT. In practice those topics are one event. When a student raises an invoice in an ERP, revenue, output tax, the customer balance, cost of sales and stock all change together, and the student has to understand why. That single experience teaches integration more convincingly than any diagram.

This guide is for heads of department, programme leaders and lecturers in accounting, auditing, operations, HR and information systems. It covers what a live system adds, course-level ideas for each discipline, what an institution should require from a teaching environment, including data privacy for student accounts, and how the Skyline Nexus ERP academic access programme works.

What textbook-only courses miss

Textbook exercises are closed: the question gives every number, and there is one right answer. Real accounting work is open: the numbers come from documents other people created, some of them wrong, and the job is to find out which. A live ERP brings that openness into the classroom without the risk of a real business.

There is also a memory effect. A student who has watched a balance sheet refuse to balance because of a mis-coded supplier invoice they posted has a concrete reason to remember double entry that a worksheet drill does not provide.

• Integration: one document affects several ledgers and reports at once, and a fault in master data spreads to every transaction that uses it.
• Controls in operation: approval thresholds, period locks, required fields and user permissions actually stop things, rather than being described.
• Evidence and audit trail: every change leaves a record of who did what and when, which is the raw material of audit and forensic work.
• Volume and data: dozens or hundreds of transactions that must be filtered, exported and analysed, not five neat journal entries.
• Consequences over time: an error posted in week two is still there at the month-end close, and the student has to correct it properly.

Accounting courses: from double entry to the close

In introductory financial accounting, an ERP works well as a mirror of what students write by hand. Students journalise a short case on paper, then enter the same transactions as documents and compare the system's journals with their own. Differences become the lesson: why did the system post cost of sales when I only raised an invoice?

In intermediate courses, give students a company to run for a simulated month or quarter and ask for the financial statements at the end, with reconciliations. Standards topics fit naturally: inventory cost formulas under IAS 2, where FIFO and weighted average are permitted and LIFO is not; revenue recognition timing under IFRS 15 when a delivery and an invoice fall in different periods; depreciation methods and the asset register under IAS 16.

In management accounting, use cost centres, projects and budgets. Students set a budget, run the period, and explain the variances from a budget-versus-actual report, which connects the calculation they learned to where the actual figures come from.

Auditing courses: evidence, controls and fraud risk

Auditing is where a live system adds the most, because audit is about evidence and a textbook cannot produce evidence. The instructor prepares a company, plants errors and irregularities, and gives students read-only or auditor-level access with a brief to find them.

Frame the exercises with the standards students will use in practice. ISA 315 (Revised 2019) asks auditors to understand the information system and the IT general controls; ISA 500 covers the reliability of information produced by the entity; ISA 530 covers audit sampling; and ISA 240 requires journal-entry testing to address the risk of management override. ISA 240 (Revised), issued by the IAASB in July 2025, is effective for audits of periods beginning on or after 15 December 2026, so students entering practice will meet it early in their careers.

• Test the controls: find out who can create, approve and post a journal, and whether the same person can do all three.
• Journal-entry testing: filter entries posted at weekends or after the close, round amounts, and amounts just below the approval threshold.
• Cut-off: select sales and purchases either side of the period end and check them against delivery dates.
• Reconcile system reports to each other: sales per the ledger against the sales listing, stock per the ledger against the stock valuation report.

Operations, supply chain and HR courses

Operations and supply chain courses can run the physical side of the same company. Students set reorder levels, raise purchase orders, receive goods into more than one warehouse or branch, transfer stock between locations and count it. The questions they answer are operational (stock-outs, slow-moving items, lead times) but every movement has a financial shadow, which is exactly the conversation operations and finance graduates will have at work.

HR and people-management courses can use the HR module for the employee lifecycle: recruitment, onboarding records, attendance, leave requests and approvals, performance reviews and training. Payroll brings finance back in, because a processed payroll becomes a journal for salary expense and salaries payable. Payroll rules are country-specific, so the lecturer should decide whether to teach payroll mechanics locally or to treat payroll as a case in how a sub-system feeds the ledger.

Information systems and IT courses

For accounting information systems, management information systems and IT audit courses, the ERP itself is the subject. Students look at how the system is configured rather than at the transactions.

These exercises suit mixed teams of accounting and computing students, who learn quickly that each group needs the other: the accountants know what the numbers should be, and the computing students know how to extract and test them.

• Design a chart of accounts and map document types to ledger accounts, then prove the mapping with test transactions.
• Design roles for a small company with proper segregation of duties, then test them by trying to exceed each role's permissions.
• Plan a data migration: prepare master-data import files from a template, load them, and reconcile opening balances.
• Write test scripts for a process change and record expected versus actual results.
• Extract data to a spreadsheet or analytics tool and build a reconciliation or an exception report from it.

Building ERP into the curriculum

Programmes that work well do not treat the ERP as a separate module that students take once. They use one system across several years so that later courses build on skills students already have. A workable pattern is: first year, one or two lab sessions that mirror hand-written double entry; second year, a running company in the financial accounting and operations courses; final year, the audit exercise, a systems design project and a capstone that runs a company from set-up to year-end.

Plan the teaching load realistically. Each lab needs a prepared company, clear written steps for the first sessions and a way to check each student's work. Lecturers who have not used the system should run the whole exercise themselves before the term starts; most problems in ERP teaching are set-up problems that appear in the first week.

Assess the reasoning, not the clicking. A student who completes every screen but cannot explain why the trial balance shows a particular receivable has learnt data entry. Ask for short written explanations, reconciliations and a close memo alongside the system output. Our companion guide on ERP course projects for accounting students gives six ready-to-use assignments with learning outcomes and assessment criteria.

What an institution needs from a teaching ERP

A system that works well for a business does not automatically work well for a class of 120. Before committing a course to an ERP, check these requirements with the provider.

Ask also where the service is hosted, which languages the interface supports for your student body, and what happens at the end of the academic year: whether workspaces are archived, handed over to students or removed, and how that fits your own records-retention policy.

• Separate workspaces: a sandbox per student or per team, so one student's mistake cannot spoil another's ledger.
• Instructor visibility: a way for the lecturer to see what each student posted, ideally through an audit trail that records the user, the time and the old and new values.
• Resettable data: the ability to start a new cohort from a clean, prepared company rather than last year's leftovers.
• Role control: the power to give students exactly the permissions an exercise needs, such as read-only access for an audit case.
• Real accounting depth: a double-entry ledger, period close, reconciliations and statements, not only sales screens.
• Data privacy: student accounts treated as personal data, with a clear agreement on how that data is processed and deleted.

Data privacy for student accounts

Student user accounts contain personal data (at least a name, an email address and a record of activity), so the institution needs the same care it applies to any other learning platform. In the EU, the General Data Protection Regulation has applied since 25 May 2018. Its data-minimisation principle in Article 5(1)(c) means collecting only what the course needs; Article 25 requires data protection by design and by default; Article 28 requires a contract with any processor that handles the data on the institution's behalf; and Article 32 requires appropriate security. The UK applies the same principles through the UK GDPR.

In Canada, the federal Office of the Privacy Commissioner notes that universities are generally covered by provincial privacy laws rather than by PIPEDA, the federal private-sector law, although PIPEDA may apply in certain situations. Institutions should therefore check their own provincial requirements.

Two practical rules reduce the risk considerably. Use fictional companies with invented customers, suppliers and employees, never real business data, so the only personal data in the system is the students' own login. And create accounts with the institutional email address and the minimum profile fields, so nothing more is collected than the course requires.

The Skyline Nexus ERP academic access programme

Universities, colleges and business schools can apply for sponsored access to Skyline Nexus ERP for teaching and student projects; each application is reviewed and the scope (courses, number of student workspaces, duration) is agreed with the institution. To apply, use the enquiry form on this page and tell us the institution, the courses you want to teach, the approximate number of students and the teaching dates.

What students work with is the same cloud ERP businesses use, in which each business is its own workspace. The general ledger sits under Fiscal Authority: a chart of accounts with account types and normal balances, manual journals that must balance, fiscal periods that move from Open to Soft Close to Locked and refuse postings once closed, and a year-end close that posts closing entries to retained earnings. When an administrator switches on the auto-post settings, sales, purchases, payments, expenses and payroll create their journals automatically, so students can trace a document to its ledger entries.

For instructors, the Audit Trail records who created, approved, posted or reversed each entry with the old and new values, and the Activity Log records logins and changes by user. Roles are built from permissions grouped by area, with view-own and view-all variants, and users can be limited to specific locations. The Audit Pack exports a calendar year's chart of accounts, trial balance, balance sheet, profit and loss, journal entries and general ledger to one Excel workbook, which suits audit assignments. The interface is available in English and Arabic, with translations for many other languages.