Housing Finance Reporting in Power BI and Microsoft 365: Dashboards People Trust
Many housing associations already run on Microsoft 365 and want their finance reporting in Power BI. This is how we connect Oracle Fusion to Power BI so budget holders, finance and the board work from the same governed numbers instead of rebuilt spreadsheets.
Housing finance teams already hold the data their organisation needs.
A new finance system is the moment to turn that data into reports the system produces each month, so the time finance spends assembling packs by hand goes into explaining the numbers instead. Budget holders, finance and the board then work from one governed set of figures.
Our standard approach is to design the reporting layer with the ledger, not after it.
Two layers, each with its own job
Oracle Fusion holds the accounting record and produces the operational reports finance relies on during the month: trial balance, budget against actual, open commitments and the period-close checks. These reflect posted and committed transactions as they happen.
Power BI sits on top for analysis and presentation: board dashboards, trends across years, combined views with housing and repairs data, and the visuals people open on a phone. It reads governed data from the ledger on a schedule.
Keeping the two jobs separate keeps each one working well: finance closes the month in the ledger, and dashboards stay a view of the ledger rather than a second copy of it.
Governed datasets, not one-off exports
Every Power BI report draws on a small number of certified datasets agreed with the housing association's data team:
- A data dictionary that defines each measure once, such as "available budget" or "committed spend".
- The same dimensions as the chart of accounts: entity, cost centre, scheme, block and property.
- Clear separation of actuals, commitments, original budget, revised budget and forecast versions.
- Named owners for each dataset, its refresh schedule and its refresh alerts.
Report writers then build on certified measures, so local analysis does not produce competing definitions of the same number.
Role-based dashboards
Finance team
Control information across the organisation: close status, exceptions, aged balances and variances.
Budget holders
Their own cost centres only: budget, commitments, actuals and forecast, with a drill to the transaction.
Board and executive
Trends, key performance indicators and the approved board snapshot for each period.
Row-level security (rules that limit each person to the rows they are allowed to see) is applied through the whole data path, so a budget holder's dashboard shows only their area, and export permissions follow the same rules.
Honest about how fresh the data is
A scheduled refresh is not real time, and our standard approach is to say so on the page. Each dashboard shows the time its data was taken and flags when a refresh has not run. People can then decide whether a number is current enough for the question in front of them.
Where something must be current to the minute, such as an open purchase order or an invoice on hold, the user goes to the ledger report, which reflects transactions as they are processed.
From a variance to the transaction behind it
A variance on a dashboard is only useful if someone can explain it. The design includes drill-through (clicking a number to open the detail behind it) from a variance to the account and then to the transactions, invoices and purchase orders behind it. A reconciliation report ties each reporting dataset back to the trial balance, so finance can show that the dashboard and the ledger agree.
Part of the Microsoft estate
For an organisation on Microsoft 365, users sign in to Oracle Fusion and Power BI with the same Microsoft account through single sign-on with multi-factor authentication, managed in Microsoft Entra ID. Reports can be shared in Teams and SharePoint under the same permissions. Power BI licences and tenant settings stay with the housing association and are confirmed early in the project.
Retiring the spreadsheets, one report at a time
We agree a reporting catalogue in design: each report, its owner, its audience and the reconciliation that proves it. The first system-produced version of each report is checked against the old spreadsheet and signed off by its owner. Only then is the spreadsheet retired.
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.
One set of numbers, seen the way each role needs
PCL One implements Oracle Fusion Cloud ERP for housing providers and designs the reporting layer alongside it, from the first design workshop to the last day of hypercare (the intensive support period after go-live).
A dashboard earns trust when anyone can trace its number back to the ledger.