Bringing Housing Finance and Purchase-to-Pay onto One Oracle Platform
Many housing associations run their ledger in one system and their purchasing in another. This is how we bring both onto Oracle Fusion Cloud as one controlled platform, and what changes for finance, budget holders and requisitioners.
A typical housing association finance estate has grown in two halves.
Finance runs the ledger, payables, receivables, fixed assets and statutory reporting in one system, used by a few dozen people. Purchasing runs in a separate purchase-to-pay tool used by a few hundred requisitioners and approvers across repairs, assets, development and central services. Invoices pass between the two, and so do the questions: has this been receipted, which scheme does it belong to, who approved it, why does the commitment report not match the ledger?
Replacing both at once is not twice the work. Done well, it removes the gap between them.
This article sets out how we approach that replacement on Oracle Fusion Cloud ERP and Procurement for a housing provider, and the design decisions that matter most.
Start from a housing structure, not a blank page
Most of the time in a finance implementation goes on design. We shorten that by arriving with a starter housing chart of accounts rather than a blank template. It already carries the dimensions housing finance teams report on: fund and cost centre, scheme, block and property, with components and grants linked to the property they belong to.
That starting point is then shaped to the organisation in a short series of workshops, run on a working Oracle environment rather than on slides. Finance leads make decisions while looking at real screens, real approval routes and real reports. Three themes cover most of it:
Structure and entities
Legal entities, ledger, segments and the housing dimensions every transaction carries.
Approvals and controls
Who can raise, approve, receipt, match and pay, by value, entity, cost centre and category.
Reporting and budgets
Management packs, Board and funder reporting, budgets and forecasts against actuals.
Our guide to housing chart of accounts design covers the structure in more detail.
A group of companies in one ledger
Many housing associations sit at the head of a small group: the registered provider plus a development or commercial subsidiary. Each company has to keep its own legal entity, its own accounts and its own VAT position, but the group still needs one view.
In Oracle Fusion each company keeps its own legal entity inside one shared ledger structure. Intercompany charges balance automatically, eliminations run in the system, and group reporting comes from the same data the companies report from. No consolidation spreadsheet sits between them.
This matters beyond year-end. When the group changes shape, through a new subsidiary, a merger or a transfer of stock, the platform takes the change without a rebuild. At Riverside, PCL One has carried one Oracle platform through successive changes to the group, with new members joining the same platform rather than starting again.
Purchase-to-pay that budget holders will actually use
The finance team is small. The people who raise requisitions, approve spend and receipt goods are many, and most use the system for a few minutes a week. If purchase-to-pay is hard to use, people work around it, and the controls that finance designed stop working.
So the P2P design focuses on the occasional user:
- Requisitioning from catalogues and approved suppliers, with the scheme, block or property picked once and carried through to the invoice.
- Approval routes that follow value, entity, cost centre and category, with delegation and escalation so nothing waits on someone on leave.
- Receipting that is quick enough to happen on the day, which is what makes three-way matching work.
- Invoice capture with document recognition, matching against the order and receipt, and exceptions sent to the person who can resolve them.
- Budget holders seeing commitments and actuals against budget in one place, without asking finance for a report.
Training follows the same thinking. Occasional requisitioners and approvers need a few hours, finance users a day or two, and super-users a few days, because they help shape and test the system from the design stage onwards.
Controls designed in, not added later
Housing finance answers to auditors, funders, the Board and the Regulator of Social Housing. The new platform has to make evidence easier to produce, not harder.
- Segregation of duties between requisition, approval, supplier maintenance, invoice processing, payment and accounting, enforced by role.
- A full audit history on configuration, approvals and transactions, from source document to financial statement.
- Period controls, reconciliations and exception reports that support month-end and year-end close.
- VAT and Making Tax Digital configured within the controlled solution, with regulatory change assessed through each quarterly Oracle update.
Because these are configured rather than coded, routine changes such as a new approval limit or a new cost centre can be maintained by trained administrators after go-live, without a change request to a supplier.
What the organisation keeps, and what moves
A finance replacement should not try to absorb everything. Oracle becomes the system of record for accounting, dimensions, budgets and financial reporting. The housing management system keeps resident-level rent, arrears and statements, and posts summarised financial entries to the ledger. CRM keeps the customer record. Repairs and asset systems keep the works detail and send costs for capitalisation.
Drawing that line early keeps the scope honest and the integrations simple. We cover how those connections are built in our article on connecting Oracle Fusion to housing systems through your integration hub.
Five checkpoints the organisation approves
We run the implementation through five approval gates, each one owned by the housing provider rather than by us: discovery complete, design agreed, system testing passed with data reconciled, user acceptance complete, and the go-live decision. Workstreams overlap between the gates wherever dependencies allow, so the programme does not wait for one phase to finish before the next can start.
The gates keep the organisation in control. The overlap keeps the programme moving.
One platform, one version of the numbers
PCL One implements Oracle Fusion Cloud ERP and Procurement for housing providers, from the first design workshop to the last day of hypercare, with the same team throughout.
The best finance replacement is the one your requisitioners barely notice and your auditors immediately do.