Why Multi-Campus Schools Struggle With Month-End Close
Schools exist to educate students and help shape their trajectory. Naturally, most invest heavily in choosing the right Student Information System (SIS), one that can carry the weight of managing different student cohorts spread across different campuses.
In that selection process, finance tends to become secondary.
Not because it isn't a vital function in schools, but because the time and energy goes into finding a system strong enough to manage students and support the teachers managing them.
Finance is often left to play a supporting role within that same system: interacting with parents for payments and billing, acting as a centralised portal for booking parent-teacher meetings, paying for books and other amenities, and handling the administrative tasks teachers and parents need.
But the real question is this: is the same system actually built to carry the weight of what finance teams do, especially in schools with multiple campuses?
The answer is simply no.
Once implemented, a SIS works well for its intended ecosystem, helping stakeholders understand student cohorts and teachers, or giving parents the right information about their kids. But somewhere along the way, these systems recognise they also need a finance function, and tack it on as an afterthought.
The deeper issue is that finance teams are rarely given a say in what they actually need. What are their requirements? What are they trying to achieve? Instead, they're handed a finance module already built around someone else's priorities, and left to work within it. The choice was never theirs to make.
The result is a system, or worse, a spreadsheet-based process, that demands far too much manual work to hold together.
The Common Finance Problem in Multi-Campus School Systems
When we sit down with schools managing multiple campuses, we find almost immediately that their finance tools can only handle the basics. The missing piece is capability: these tools can't bring the right data at the right time, can't support end-of-month automation, and lack the granularity finance teams need as student numbers grow.
More invoices, more credit cards tied to teachers and departments, more revenue streams, all of it sitting inside fragmented systems.
The core issue is that finance teams aren't given tools built to grow with the school, and in many cases, as we discussed earlier, finance isn't given a choice in the first place.
What we've found is that when schools have this conversation with us, and we present a genuine alternative, the response is often surprise that one exists.
Finance teams don't have to choose between a strong student information system and a strong finance system. We help schools keep the platform that works for their students and pair it with a finance system built to do the work properly, with the two talking to each other. That combination, rather than a compromise between the two, is what we consistently find schools need.
School Finance Gaps: Is It the System or the People?
Our experience shows it's usually both, and it shows up in two common ways.
Scenario one: Schools with multiple campuses in different locations, all operating differently, because not all schools are the same. Each campus runs its own processes and structures, often operating in isolation, effectively behaving like its own independent organisation. Each has its own student information system, its own billing engine. The trouble starts when all of that data needs to come together: campuses are tracking different things, reporting differently, and by the time it's consolidated, finance has been operating in silos the whole way through.
Scenario two: A single finance team managing one complex SIS platform across every campus, but the platform itself doesn't support consolidation, it treats each campus as its own entity with its own finance function. The team wants to operate as one, but the system won't let them. So even with a centralised team in place, the accounting work becomes genuinely difficult, because structurally, they're still working independently.
What Factors Lead to a Poor Month-End Close for Multi-Campus Schools?
These gaps show up most clearly at close, and they compound into what we call close lag, the growing distance between when the month ends and when the numbers are actually final and correct.
Factor one: revenue recognition
One of the biggest reasons multi-campus schools experience month-end drag is revenue recognition. We covered this in depth in our previous article on getting revenue recognition right, where we looked at what changes when a system carries the rules instead of a person.
Most finance teams in schools have managed revenue recognition manually for years, not because they lack the skill, but because the systems available to them never supported anything else. Manual was the only option.
When the recognition rules for each funding stream, the standard, the method, the acquittal dates, the performance milestones, are configured into the system, the journals run automatically at close.
For schools, this gets complicated fast, because revenue reported each month should be tied to the service actually delivered to the student that month.
Take a common scenario: a student pays their annual tuition upfront. That revenue should be recognised progressively, potentially split evenly from February through November, or even calculated by the day. But because most schools lack the tools to track that automatically, they default to reporting the invoice as revenue in full, simply because tracking it properly is too hard. The result isn't just a longer close, it's revenue being reported in a way that doesn't actually comply with the accounting standards throughout the year.
Factor two: accounts payable
Accounts payable is another area lacking a disciplined, repeatable process across the sector. Tax invoices sit unprocessed and delay the close, because there's no consistent process for capturing and approving them on time.
Factor three: credit card reconciliation
Many schools issue credit cards to staff across departments and campuses, then wait on outstanding receipts before they can reconcile spend. That waiting period holds up close every month.
Factor four: payment plans and billing reconciliation
Schools that invoice tuition but also offer payment plans face a fourth compounding issue: reconciling billing, payment plans, and revenue recognition against each other. Matching what was invoiced, what was actually paid via a plan, and what should be recognised as revenue is a manual, time-consuming exercise, and it's often where the biggest lag in close actually comes from.
"For schools, it is really about how do we actually automate month-end, and how do we create good policies and good habits around it? That's one of the key areas: the whole billing, debtors management, and payment plans, and how all of that ties together and reconciles every day." — Nunzio Giunta, Founder, Giuntabell
Not sure how long your own close lag actually is? Take the free Close Lag Self-Assessment to see where your school stands before reading on.
How to Fix School Finance Systems: Where to Start
The first practical step is not a system change, it is a policy one: simplify billing. Complex discount structures and pricing tiers rarely add value for the school, they just add friction for finance. The simpler the billing policy, the less it costs to administer and the fewer exceptions finance has to chase every month.
From there, the priority is choosing a school finance system that is genuinely fit for purpose. A school running multiple campuses or entities needs a system that consolidates quickly, handles eliminations, and supports audit and financial reporting from a single source, not a finance ledger bolted onto a student information system as an afterthought.
Once that system is in place, the real work is habit. Reconciling invoicing and receipting daily, and bank accounts daily, is what gives a finance team genuine control. Left even a week, gaps start to open, and once a staff member moves on or details are forgotten, closing those gaps means investigation rather than routine reconciliation. Daily is the standard to aim for. Weekly, fully reconciled, is the absolute minimum.
School Finance System Implementation: A Realistic Timeline
For a school starting from a fully fragmented, multi-campus setup, a typical system implementation takes three to four months, depending on size and complexity. Go-live is not the finish line. The following six months is where the real reduction in close lag happens, as the team embeds the new habits and the system's capability, including newer AI-driven functionality, is put to work reducing manual effort further. After that, improvement continues. Reducing end-of-month friction is not a project with an end date, it is an ongoing discipline.
Where This Leaves Multi-Campus Schools
None of this is unusual, and none of it is unfixable. It is the predictable outcome of a finance function built as a secondary thought inside a system designed for something else entirely. The schools that move past it do not do so by working harder inside the same fragmented setup, they do so by simplifying policy, choosing a system built to consolidate from day one, and embedding daily discipline once it is live.
Not sure how many hours fragmented systems are already costing your finance team?
Take the free Close Lag Self-Assessment to see where you stand, and what a realistic path forward looks like.