At minimum, the system should support general ledger, accounts receivable, accounts payable, cash management, tax, fixed assets, journals, financial periods and audit trails. But having these functions is only the starting point.

Finance teams should also be able to understand every transaction in the context of the school - and a transaction should never become a dead-end number in the general ledger.

A single family account may include tuition, boarding, transport, extracurriculars, excursions, levies, deposits, scholarships, sibling and staff discounts, credits, refunds and instalment arrangements - and different students may be billed differently again.

Finance should be able to see the full path from charge to invoice to payment to outstanding balance, without opening three systems and a spreadsheet.

Schools rarely have one universal billing model, and billing rules change from year to year - even between students. The system should carry those variations instead of finance maintaining them by hand.

The goal is not unlimited complexity. It is controlled flexibility - legitimate variation without an administrative maze.

A budget should not become obsolete the moment the school year begins. Schools need to compare budget, actual and forecast continually, so leadership can see where spending is ahead or behind plan and how changing assumptions affect the year-end position.

• →What if enrolment is lower than forecast?
• →What if staffing costs increase?
• →What if a capital project runs over budget?

Purchasing is spread across academic departments, facilities, IT, administration and sport. Without a clear process, finance struggles to say whether a purchase was requested, approved, within budget, ordered, received, invoiced and paid.

Financial control should happen before money is spent - not only after finance receives the invoice.

A healthy operating result does not automatically mean healthy cash flow. Schools carry real timing differences between when fees are billed, when families pay, and when major expenses fall due.

Finance needs visibility into cash balances, expected receipts, overdue family accounts, upcoming supplier payments, payroll requirements and capital commitments - moving from retrospective cash reporting to forward-looking cash management.

Schools carry significant financial responsibility and need strong internal controls. The system should preserve evidence of who performed or approved each important action - so audit means following the transaction, not reconstructing it from email chains.

A group may operate several campuses, separate schools, foundations, building funds, trusts or trading entities. Leadership needs consolidated reporting; finance still needs entity-level detail. The ideal outcome is one consolidated view without losing either.

One of the strongest signs of an inefficient finance environment is a simple management question triggering a lengthy reporting exercise.

Different roles need different views of the same financial data - not separate versions of a spreadsheet.

Financial processes depend on information from student management, admissions, enrolments, payment providers, payroll, banking, procurement and parent-facing systems.

When systems cannot exchange information reliably, people become the integration layer: someone exports a file, someone changes it, someone imports it, someone reconciles it, someone investigates why the totals differ.