Reaching 1 April as a Smaller Housing Association: The Same Gates in a Shorter Plan
A smaller housing association does not need a large programme to change its finance system well. It needs the same controls, a scope that fits its size and a partner who starts from a proven housing design. This is how we plan for a 1 April go-live.
The year end sets the deadline for most housing finance projects.
Changing finance system on 1 April means closing the old year in the old system and opening the new year in the new one, with a clean split at the year boundary. For a smaller association, with fewer entities, fewer users and a simpler set of interfaces, that date can be reached with a shorter plan than a large group would need.
The plan is shorter because there is less to do, not because steps are skipped.
Why a smaller association can move faster
- Fewer legal entities and a simpler group structure mean a quicker chart of accounts design.
- A smaller finance team means fewer design workshops and quicker decisions.
- Fewer interfaces to build and test.
- Smaller data volumes, so each migration rehearsal runs and reconciles faster.
The work that does not shrink is the work that protects the finance operation: reconciled data, tested processes, trained users and a rehearsed cutover (the switch from the old system to the new one). Those stay in full.
Start from a design already live in UK housing
We start from a housing design already in use, with a chart of accounts built around entity, cost centre, scheme, block and property. The association's team reviews what exists and decides the differences, rather than documenting shared requirements from a blank page. After design sign-off, configuration tools apply the design in about two weeks.
Our article on how we deliver faster explains each of these accelerators.
A focused day-one scope
Reaching 1 April safely means deciding early what must work on day one and what can follow. A typical split:
Day one
General ledger, payables and receivables, fixed assets with components, budgets and forecasts, requisitions and purchase orders, approvals, core reporting, and the interfaces finance needs every week.
Following releases
Supplier catalogues, contract management, advanced analytics and AI features, and interfaces that can run on a controlled interim process for a short time.
Specialist systems that already work well can stay in place at go-live and be integrated for reporting, which keeps them off the critical path.
Workstreams that overlap
Design, configuration, interface build and data migration run alongside each other wherever the dependencies allow. Data profiling starts in the first weeks, so cleansing decisions are made on real findings. Interface specifications and access are requested at mobilisation, so outside suppliers have time to respond and the plan stays on track.
The same approval gates
A shorter plan keeps the same checkpoints as a larger one: discovery complete, design agreed, system testing passed with data reconciled, user acceptance testing (UAT, where the association's own staff test real scenarios) complete, and the go-live decision. Each one is the association's to approve.
Our standard approach is that go-live needs reconciled balances, passed critical scenarios, working access controls, trained finance users and a rehearsed recovery path.
A fallback date agreed up front
We agree a later fallback date at the start, for use only if a critical readiness criterion is not yet met. Having it on the plan from day one means the go-live decision is made calmly, on the evidence.
After go-live, hypercare (the intensive support period after go-live) covers the first payment cycles and the first month-end close, then hands over to the agreed support service.
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.