Budget Control for Housing Budget Holders: Punchout, Commitments and Development Costs on Oracle
In most housing associations, spend is committed by budget holders across repairs, development and central services, not by the finance team. This is how we design Oracle Fusion so those budget holders control spend when it is committed, and finance sees the same numbers they do.
Housing finance teams are small. The people who spend the money are not.
A housing association may have a few hundred budget holders and requisitioners: repairs managers ordering materials, development leads managing contractor costs on new schemes, and central services buying everything from IT to training. Each of them commits spend. Finance usually finds out when the invoice arrives, and the budget report catches up at month-end.
The goal is to move control from the invoice back to the requisition, where the decision to spend is actually made.
This article covers how we design budget control and procure-to-pay (P2P, the process from requisition to payment) on Oracle Fusion Cloud for a housing provider, and how development scheme costs carry through to the asset register.
Steps, in order:
- Requisition: Catalogue or punchout, coded once
- Funds check: Against the budget holder's budget
- Approval: Routed by value and cost centre
- Purchase order: Obligation reserved
- Receipt and match: Order, receipt and invoice agree
Budgets that check spend when it is requested
Oracle Fusion budgetary control checks available funds at the moment a requisition or purchase order is raised. Our standard approach is to set this up against the same cost centres and housing dimensions the budget was built on, so the check is meaningful to the person raising the request.
Approved requisitions are held as commitments and issued orders as obligations, both reserved against the budget. A budget holder can see their budget, what is committed, what is invoiced and what is left, in one place, without asking finance for a report.
Finance decides how strict each check is. A hard stop suits some budgets, such as tightly controlled central costs. A warning that still lets the request go forward suits others, such as responsive repairs, where the work has to happen. Those choices are made in design workshops, on a working Oracle environment, rather than on slides.
Punchout catalogues for occasional buyers
Most requisitioners use the system for a few minutes a week. If ordering is slow, people order outside it, and the controls finance designed stop working.
Punchout catalogues let a requisitioner open an approved supplier's own online shop from inside Oracle Procurement, pick items at contracted prices and bring the basket straight back as a requisition. Local catalogues cover regularly ordered items from other suppliers. In both cases the coding is defaulted from the requisitioner's role and cost centre, and the scheme, block or property is picked once and carried through to the invoice.
Punchout
Order from an approved supplier's own site at contracted prices, without leaving Oracle.
Local catalogues
Regular items from other approved suppliers, kept up to date by procurement.
Free-text requests
For one-off purchases, with extra approval so they remain the exception.
Approval limits that follow the budget
Each budget holder gets an approval limit by value, and approvals route by cost centre and spend category. Delegation and escalation keep requests moving when someone is on leave.
Once a purchase order is issued, receipting needs to be quick enough to happen on the day the goods or services arrive. That is what makes three-way matching work: the invoice is matched against the order and the receipt, within agreed tolerances, and only matched, approved invoices go forward for payment. Exceptions go to the person who can resolve them, not to a shared finance inbox.
Invoice capture uses document recognition to read supplier invoices and propose the match. Our standard approach is that a person confirms anything the system is unsure about, so automation speeds up the routine work without taking decisions away from the finance team.
VAT and Construction Industry Scheme (CIS) deductions are best handled at the point of purchase too. Our article on housing tax at the point of purchase covers how.
Development scheme costs that land in the right place
New-build and regeneration schemes run for months or years, and their costs need to be tracked against the scheme, not only against a cost centre. Oracle Project Costing captures each scheme as a project, with tasks for its stages, so contractor and professional fees are coded to the scheme from the purchase order onwards.
When homes complete, the costs are capitalised into the fixed asset register at component level (roof, kitchen, bathroom and so on), linked to the property they belong to. Grant funding is recorded against the same scheme, so the cost, the funding and the resulting assets can be reported together.
Our article on moving the housing asset register to Oracle covers the component structure in more detail.
Controls auditors can follow
- Segregation of duties between requisition, approval, supplier maintenance, invoice processing and payment, enforced by role.
- A full audit trail from requisition to payment, including who approved what and when.
- Approval limits and budget checks configured rather than coded, so trained administrators can maintain them after go-live.
Finance: for a large UK housing group, PCL One's Oracle programme cut month-end close from 18 days to under 5, with return on investment in under seven months.
Budgets ready for the new financial year
Most housing associations start their financial year on 1 April, which makes it a natural go-live date for a new finance system. Budgets for the new year then need to be loaded and checked before the first requisition is raised, so budget control works from day one.
Our article on going live on 1 April covers how to plan around the year boundary, and our procure-to-pay guide sets out the wider P2P design.
Control at the point of commitment
PCL One implements Oracle Fusion Cloud ERP, Procurement and Project Costing for housing providers, from the first design workshop to the last day of hypercare (the intensive support period after go-live), with the same team throughout.
Budget holders who can see what they have committed make better decisions than budget holders who wait for month-end.