.png&w=3840&q=75)
Ask a financial planning and analysis manager at a large university what keeps them up at night during budget season, and the answer is rarely "not enough data." It's usually the opposite. Too much data, spread across faculties, cost centres, and funding sources, none of it talking to the others until someone in finance manually forces it to.
Higher education budgeting looks deceptively similar to corporate budgeting from a distance. Up close, it isn't.
A university runs several budgets at once under one roof: tuition-funded operating budgets, government subsidy allocations, research grants with their own reporting conditions, endowment income, and capital projects that span years rather than fiscal cycles. Each of these has its own rules, its own timeline, and often its own spreadsheet. Consolidating them into something a council or board can actually read is where most institutions lose weeks they don't have.
A capital project for a new science block, for instance, doesn't respect the university's financial year. Neither does a three-year research grant with its own drawdown schedule and reporting requirements. Fold enough of these into a budget process built around a twelve-month view, and the budget stops being an accurate picture of the institution's finances. It becomes an approximation, patched together department by department, with the patching work falling squarely on a finance team that's usually a fraction of the size of the institution it serves.
The consolidation problem doesn't shrink, it compounds
Small institutions can get away with spreadsheet budgeting for a while. Large ones can't, because the problem isn't linear. Every additional faculty, campus, or cost centre doesn't just add one more spreadsheet to the pile. It adds another point where a formula can break, a version can go stale, or a number can quietly stop matching the one three tabs over.
North-West University runs this problem at genuine scale: 60,000 students spread across multiple campuses, with a wide network of budget planners feeding into one consolidated institutional view.
Before implementing a dedicated system, the university's financial planning team relied entirely on spreadsheets. As Farai Chingono, Manager of Financial Planning & Analysis at North-West University, put it plainly: "You can imagine the possibility of errors if you are using spreadsheets."
At that scale, the question isn't whether errors happen. It's how long it takes to find them, and how much of the budget cycle gets consumed doing so.
The University of Cape Town faced a version of the same problem and has described the shift in similar terms. Moving from spreadsheets to a near one-click consolidation process gave the finance team the agility to respond quickly rather than spend the bulk of budget season reconciling.
An ERP isn't the same thing as a planning platform
It's tempting to assume that budgeting is solved the moment an institution implements a major financial system. In reality, recording transactions and planning the future are two very different jobs.
Most enterprise systems are designed first and foremost to process and report on what has already happened. Planning, forecasting, scenario modelling, and collaborative budget ownership often require a different set of capabilities entirely.
The University of the Witwatersrand discovered this when evaluating different approaches to budgeting. The institution found that moving numbers into a system was not the same thing as solving the underlying challenge of consolidation, collaboration, and planning.
This matters for finance teams assuming their next system upgrade will automatically solve budgeting challenges. It usually doesn't.
Budgeting, forecasting, and reporting are specialised disciplines with their own requirements around modelling, workflow, visibility, and control. Treating them as a checkbox within a broader finance system often leaves institutions managing the same budgeting challenges in a different interface.
Why staff budgeting needs more detail
At most universities, salaries and related staff costs make up the majority of operating expenditure. That single fact should shape how an institution budgets, because a tool that only handles budgets at the department or cost centre level is missing the detail that actually drives the number.
Employee-level budgeting, the ability to plan by individual staff member rather than as a lump sum against a cost centre, was one of the deciding factors in Wits's original decision to move away from spreadsheets in 2009. Sixteen years later, it's still central to how the university plans.
For an institution where people costs represent the bulk of the budget, being able to see and adjust at that level of granularity isn't a nice-to-have. It's the difference between a budget that reflects reality and one that's a reasonable guess dressed up as a plan.
New staff shouldn't need a semester to learn the system
Universities experience regular turnover in finance and planning teams, whether through natural attrition, academic-year hiring cycles, or people moving between institutions.
Whatever system a university relies on for budgeting needs to be something a new team member can learn quickly, not something that requires a dedicated specialist and an extensive handover.
Thapi Moyakhe joined North-West University three years ago with no prior experience of the university's budgeting platform. She has since become a system administrator.
"I was able to learn the system and really master it quickly," she says. "I think that speaks highly about how user-friendly it is."
That kind of onboarding speed matters more in higher education than in many other sectors, precisely because so many people entering numbers into the budget, including faculty administrators, department heads, project leads, and researchers, are not finance professionals.
What this actually calls for
Put the pattern together and the shape of the problem becomes clear.
Higher education needs a budgeting environment that can consolidate reliably across a large and often decentralised structure, go deeper than departmental totals into individual staff costs, support non-financial budget owners across faculties, and operate independently of assumptions about what the institution's core finance system can or cannot do.
None of that is exotic. It's what a dedicated planning platform is built to do.
The institutions that have made the switch, from Wits's sixteen-year relationship with IDU to North-West University's rollout across 60,000 students, tend to describe the same outcome: less time spent chasing numbers across spreadsheets and more time spent actually planning.
If your budget season currently runs on a network of shared spreadsheets held together by whoever remembers which version is correct, it's worth asking what that process is really costing you. Not just in hours and errors, but in the analysis, insight, and strategic planning your team never gets time to do because they're too busy reconciling data.
See how IDU approaches budgeting for higher education: Budgeting & Planning for Higher Education