Implementation plan
Housing finance implementation plan: phases, gates and a 1 April go-live
A stage-gated plan to move a UK housing association's finance and procure-to-pay onto Oracle Fusion, ready for the first day of the new financial year, with five gates your team approves.
The plan combines design, configuration, integration, migration, testing, training and change, with formal entry and exit criteria at every gate. Workstreams overlap wherever the dependencies allow, and contingency is kept before the go-live date.
Built on Oracle Fusion Cloud, using standard configuration.
Short answer
How long does a housing association finance system implementation take?
PCL One's example plan for Oracle Fusion finance and procure-to-pay goes live at the end of month 12 from mobilisation, ready for 1 April. It runs through discovery, design, build and migration, system and user testing, readiness and cutover, then hypercare, with formal approval gates your team signs and contingency kept before go-live.
Last updated
The route at a glance
An example plan, counted in months from mobilisation. Production goes live at the end of month 12, ready for 1 April.
Months 1–2
Mobilise and discover
Governance, data inventory, interface planning
Gate: Discovery complete
Months 2–4
Design
Workshops on a working system
Gate: Design agreed
Months 3–7
Build, integrate, migrate
Interfaces and two mock migrations
Months 5–10
System, then user testing
Your scenarios, your sign-off
Gate: System testing passed; user testing complete
Months 10–12
Readiness and cutover
Rehearsed runbook, final load
Gate: Go-live approved
From 1 April
Hypercare
First month-ends and the first quarter-end
Gate: Agreed success measures met
Phase by phase
Months 1–2
Mobilise and discover
- Governance, the plan and a shared RAID log
- Detailed discovery and process confirmation
- Security and access design
- Data inventory and integration planning; supplier specifications, access and test slots requested
You name your sponsor, process owners and data owners.
Months 2–4
Design
- Design workshops on a working system, starting from a housing chart of accounts with fund, cost centre, scheme, block and property
- Three workshop themes: structure and entities; approvals and controls; reporting and budgets
- Configuration built up as decisions are made: finance, procure-to-pay, approvals, reporting, security and fixed assets
You make the design decisions, on real screens.
Months 3–7
Build, integrate and migrate
- Interfaces built to documented data contracts
- Migration cycles for master data, opening balances, payables and receivables, open purchase orders, and fixed assets with their components
- Two mock migrations, each reconciled and signed off
- Training needs and materials prepared
You review the data and sign off each reconciled load.
Months 5–10
Test: system testing, then user testing
- System and integration testing of linked processes, interfaces, recovery and migrated data
- User acceptance testing with your real business scenarios
- Reporting validated; hands-on coaching and the first training waves
You test, and your business owners sign off.
Months 10–11
Cutover readiness
- Cutover rehearsed with the runbook that will be used on the day
- Role-based training for every user before go-live
- Operational readiness and go or no-go criteria agreed
You approve go-live against the agreed criteria.
Month 12
Cutover and go-live
- Freeze, final migration and delta loads, with a signed reconciliation and rollback points
- The old year closes as normal in the current systems; the new system opens on 1 April
- Opening balances approved by your finance team
You approve the opening balances.
Five gates your team approves
Each gate has entry and exit criteria agreed in advance. Each is your decision, passed on evidence rather than on a promise.
| Gate | When | What your team confirms |
|---|---|---|
| 1. Discovery complete | End of month 2 | Sponsor, owners and the decision calendar in place; data inventory and the interface list agreed |
| 2. Design agreed | End of month 4 | Design signed off: chart of accounts, entities, approvals and controls, reporting and budgets |
| 3. System testing passed, data reconciled | End of month 7 | Linked processes and interfaces pass system testing; the second mock migration reconciled and signed |
| 4. User testing complete | End of month 10 | User acceptance testing signed off against formal exit criteria |
| 5. Go-live approved | Month 12 | Cutover rehearsed; final data reconciled; interfaces accepted live; users trained; rollback points defined |
Data migration inside the plan
We begin with ownership, extraction rules and data-quality profiling, rather than loading legacy issues into the new system.
- Source-to-target mappings, cleansing responsibilities, how much history to keep and the reconciliation criteria are agreed together.
- Two mock migrations run during build and testing, then the final cutover cycle.
- Each cycle produces record counts, control totals and an exceptions report. Balances, open payables and receivables, purchase orders and fixed assets are reconciled to agreed legacy reports.
- Large component populations are validated with automated checks and sampled business verification.
- Cutover uses a controlled freeze and delta loads, with a signed reconciliation and rollback decision points.
Training, phased with the plan
Super-users join from design, and every user is trained for their role before go-live, in a separate test and training environment kept apart from live data.
Design
Impact assessment; super-users named and in the workshops
Build
Training needs and materials: user guides, quick-reference guides, short videos
User testing
Hands-on coaching and the first training waves
Before go-live
Role-based training for every user, on site and remote, with train-the-trainer for super-users
After go-live
Refresher and new-starter learning, with floor-walking and virtual support
Who does what
PCL One leads the delivery as the single accountable partner. Your team provides the decisions, the people who own the data and processes, and the sign-offs.
| Activity | PCL One leads | Your team provides |
|---|---|---|
| Governance and design | Plan, workshops, configuration baseline | Sponsor, process owners, decisions |
| Configuration and reports | Build, controls, dashboards | Rules, approval limits, report layouts |
| Data | Profile, map, load, reconcile | Data owners, sign-off |
| Interfaces | Deliver the housing system, hub and bank interfaces | Specifications, access and acceptance, including your suppliers' contacts |
| Environments | Roles, single sign-on, multi-factor authentication | Users, identity, network |
| Testing | Plans, system testing, defect management | Testers, user acceptance sign-off |
| Training and change | Materials, delivery, coaching | Release staff, name super-users |
| Cutover and go-live | Runbook, loads, rollback | Opening balances, go or no-go |
| Hypercare and handover | Triage, knowledge transfer, documentation | Super-users, service owner |
Your time, only when it counts
Indicative effort for your team. The same people often cover several roles, and demand peaks in user testing and the cutover window.
| Your role | Indicative time |
|---|---|
| Programme sponsor | 1–2 hours a week, plus a decision at each gate |
| Project manager | 2–3 days a week in active delivery |
| Finance, procure-to-pay, assets, tax and IT leads | 1–2 days a week in design; half a day to a day a week in configuration |
| Data lead and data owners | 1–2 days a week; 2–3 days a week in load windows |
| Housing system, platform and security leads | 1–2 days a week; security half a day a week in testing |
| Test coordinator and testers | Coordinator 1–2 days a week; testers 2–3 days a week in user testing |
| Training lead and super-users | Training lead half a day to a day a week; super-users 2–3 days of training |
| Cutover team | Cutover lead 2–3 days a week, with dedicated cover in the cutover window |
The PCL One team
- Programme sponsor and project manager
- Oracle finance solution lead and procure-to-pay lead
- Data migration lead
- Integration architect
- Security lead
- Test and user acceptance lead
- Change and training lead
Stable from discovery to hypercare, supported by PCL One's Oracle ERP practice and service management.
The risks, and how the plan handles them
Every dependency has a plan, and impacts are assessed together before anything changes.
- Legacy data quality: early profiling, clear cleansing ownership and repeated mock migrations
- Dependence on the housing system, integration hub and bank suppliers: early specifications, dated dependencies, test stubs where needed, and escalation through the programme board
- Limited business availability: an agreed decision calendar, with named deputies for every key decision
- Scope growth: impact-assessed change control, so scope, timetable, cost and quality are weighed together
- Oracle's quarterly updates: release-impact assessment and regression testing
- Adoption: super-users from design, process ownership and role-based training
Go-live at the year boundary, then hypercare
Your old year closes as normal in the current systems, and opening balances are ready on day one of the new year.
Legacy system, in order:
- Last week of March: Final payment run
- April: March close
- Early May: Read-only for audit
New system, in order:
- Last week of March: Open items loaded
- April: Opening balances signed with auditors
- Early May: First month-end close
- Last week of March: Legacy system passes open items to New system
- April: Legacy system passes balances to New system
1 April: the new financial year (between Last week of March and April)
Hypercare runs through the April month-end, the May month-end and the June quarter-end, with daily triage at first, close monitoring of integrations and payment runs, and knowledge transfer into business as usual. It ends when the agreed success measures are met, with a plan for any open defects, documentation handed over and the service accepted.
Go live on 1 April: changing finance systems at the year boundaryConfident go-live: cutover and hypercare for housing financeImplementation accelerators for housing finance
Implementation plan: questions housing associations ask
What does an implementation plan to a 1 April go-live look like?
A stage-gated plan of about 12 months, counted from mobilisation. Months 1 to 2 mobilise and discover; months 2 to 4 design on a working system; months 3 to 7 build the interfaces and run the migration cycles; months 5 to 10 run system testing, then user testing and the first training waves; months 10 to 11 rehearse the cutover; month 12 is cutover, ready for 1 April. Workstreams overlap where dependencies allow, contingency is kept before the go-live date, and hypercare follows through the first month-ends.
What are the approval gates in the plan?
Five, each approved by the housing association against entry and exit criteria agreed in advance: discovery complete, design agreed, system testing passed with the data reconciled, user testing complete, and go-live approved. Each gate is passed on evidence rather than on a promise, and anything that would change scope, timetable, cost or quality is assessed together through change control first.
What are the main risks in a housing finance implementation, and how are they managed?
Legacy data quality, handled by early profiling, clear cleansing ownership and repeated mock migrations. Dependence on the housing system, integration hub and bank suppliers, handled by early specifications, dated dependencies, test stubs and escalation through the programme board. Limited business availability, handled by an agreed decision calendar with named deputies. Scope growth, handled by impact-assessed change control. And Oracle's quarterly updates, handled by release-impact assessment and regression testing.
How much time does a housing association's own team need to give?
Indicatively: the sponsor 1 to 2 hours a week plus a decision at each gate; a project manager 2 to 3 days a week; finance, procure-to-pay, assets, tax and IT leads 1 to 2 days a week in design; data owners 1 to 2 days a week, more in load windows; testers 2 to 3 days a week in user testing; and super-users 2 to 3 days of training. The same people often cover several roles, and demand peaks in user testing and the cutover window.
Can a housing association go live with a new finance system on 1 April?
Yes. Most housing associations close their year on 31 March, so starting the new system on 1 April gives each year one system, one ledger and one audit trail. The legacy system makes its final payment run in the last week of March, open items load over the cutover days, and opening balances load in April once the legacy March close is done, signed off with the auditors.
How much history should we migrate into a new finance system?
Bringing every year of history into a new ledger is rarely worth the cost. Most housing providers bring opening balances, open items, the full asset register and one or two years of summarised history, and keep older detail in an archive their auditors can still search. The answer is agreed with your data owners in discovery and written into the migration scope.
What support do we get after go-live?
Hypercare runs through the first month-ends, with daily triage at first, close monitoring of integrations and payment runs, and the people who built each part supporting it. It ends against agreed success measures, not on a fixed date: month-end closes on the finance timetable, supplier payments on time and in full, clean housing management and CRM interfaces, budget holders tracking the new year's budget, and super-users handling first-line queries.
Bring your go-live date
Tell us when your year ends and where your data and design stand. We will lay the phases and gates onto your dates and show what each needs from your team.
PCL One (PayrollCloud Limited)
International House, 12 Constance Street
London E16 2DQ
United Kingdom