Budget Holders Who Forecast for Themselves: Multi-Year Budgets, Versions and Approval
The people closest to the spending know best where the year will land. This is how we set up Oracle Fusion so housing budget holders enter, explain and submit their own forecasts, and finance reviews them instead of rekeying them.
Forecasts are most accurate when they come straight from the people who own the spend.
Moving forecasting into the finance system means budget holders enter their figures once, in the same structure as the ledger, and finance spends its time reviewing and challenging them. The board then sees the forecast as budget holders submitted and finance approved it.
Our standard approach is for budget holders to enter their own forecast in the system, with finance approving rather than retyping.
Keep the numbers apart
Good forecasting starts with a model that keeps different kinds of number apart. Each one is held separately:
Actuals and commitments
What has been posted, and what has been ordered but not yet invoiced. Budget holders can see these, and they change only through posting.
Original and revised budget
The budget the board approved, and any approved changes during the year, each kept as its own version.
Forecast versions
Each forecast round is saved as a version, so this quarter can be compared with the last one.
Multi-year view
Budgets and forecasts over several years, so the in-year picture links to the longer-term business plan.
What a budget holder actually does
- Opens their cost centres and sees budget, commitments, actuals to date and last forecast side by side.
- Enters the forecast for the rest of the year, line by line or by adjusting a starting point finance has prepared.
- Adds a short explanation for any movement above an agreed threshold.
- Submits the forecast for approval.
The screens are designed for occasional users. Most budget holders forecast a few times a year, so the task has to make sense without a manual open beside it.
Version control and approval
Every submission carries its version, who submitted it and when. Approval follows the organisation's scheme of delegation: a manager or head of service approves, finance reviews, and the approved version becomes the one reported. Rejected submissions go back with a comment, and the history of each change stays visible.
Because forecasts sit in the same structure as the ledger (the same cost centres, schemes and accounts), the approved forecast lines up with actuals without a mapping exercise.
Inputs from the rest of the organisation
Staff costs are often the largest line. Workforce planning inputs, such as current establishment and planned changes, can be brought in from the HR and payroll system as a starting point, so budget holders adjust a realistic figure rather than build one from scratch.
Driver-based budgeting and scenario modelling (for example, a different rent settlement or interest rate) can be added once the basic cycle is running smoothly. We aim to get the core cycle stable first, then add sophistication.
Reported the same way everywhere
The approved forecast feeds the ledger reports and the governed Power BI datasets, so the board pack, the finance team and each budget holder see the same version. Our article on housing finance reporting in Power BI covers how that reporting layer is built.
Short, role-based training
Budget holder training focuses on the few tasks they need: reading their position, entering a forecast, explaining a movement and submitting it. Super-users in each directorate help colleagues through the first forecast rounds after go-live.
Finance: month-end close from 18 days to under 5
At a large UK housing group, Oracle Fusion finance with PCL One cut month-end close from 18 days to under 5, with return on investment in under seven months.