Chart of accounts
Chart of accounts transformation for UK housing associations
Your chart of accounts decides what your finance team can report without a spreadsheet.
In housing it has to carry rents, service charges, tenures, schemes, assets and group consolidation at the same time. We design that structure in Oracle Fusion Cloud Financials, map every legacy code to it, and keep your housing and planning systems posting on day one.
Starts from a chart already live at one of the UK's largest housing groups.
Short answer
How should a housing association design its chart of accounts?
In housing the chart of accounts has to carry rents, service charges, tenures, schemes, assets and group consolidation at the same time, because it decides what finance can report without a spreadsheet. PCL One designs that structure in Oracle Fusion Cloud Financials, maps every legacy code to it and keeps housing and planning systems posting on day one.
Last updated
Three questions shape every design
- Question 1
Which reports must your board, the regulator and budget holders get straight from the ledger?
- Question 2
Where do costs need property, tenure or project detail?
- Question 3
Which systems feed finance today, and which codes do they send?
What a housing chart of accounts has to answer
One ledger serves several audiences. The chart has to support each of them from the same postings.
Statutory accounts
FRS 102 and the Housing SORP, with social and non-social activity split cleanly.
Regulatory returns
Figures for the Regulator of Social Housing, including the financial viability returns.
Service charges
Costs at estate, block and property level, split by tenure, ready for apportionment and year-end reconciliation.
Budgets and rent setting
The cost centres your planning tool and housing system already use.
Group reporting
Registered providers, commercial subsidiaries and joint ventures, consolidated and non-consolidated.
The structure we start from
We start from a chart already live at one of the UK's largest housing groups, then adjust it to your operating model. Each dimension has one job.
| Dimension | What it answers |
|---|---|
| Company | Which legal entity, and which consolidation group it rolls into |
| Cost centre | Who holds the budget; scheme, department and business stream sit in its hierarchy |
| Property group | Which estate, block, house or garage, for service charges and cost per property |
| Tenure | General needs, affordable, supported, shared ownership, leasehold, market rent, commercial; rolled up to social and non-social |
| Account | The natural account; its hierarchy carries statutory and management groupings |
| Intercompany | The counterparty company for group transactions |
| Project | Development schemes, contracts and programmes across accounts and cost centres |
| Spare | Room for a reporting need you have not met yet |
Three design choices matter most.
The cost centre comes before the property, so costs with no property detail stay at cost centre level and property costs roll up to it.
Tenure has its own dimension, so allocations can split estate and block costs across tenures.
Department and business stream live in the cost centre hierarchy, so a reorganisation changes a hierarchy and leaves the codes alone.
From legacy codes to the new chart of accounts
Six steps take every legacy code to its place in the new structure, and prove the result before go-live.
Steps, in order:
- Collect: Every legacy code, with its use
- Ask the reporting questions: Which views must stay stable
- Design: Tested against real transactions
- Cleanse: Retire unused, merge duplicates
- Map: Finance One holds the translation
- Prove: Trial balance rebuilt each mock load
- Collect. Every legacy chart, analysis code and attribute, with how often each is used.
- Ask the reporting questions. Which views must stay stable, where budget responsibility sits, where spreadsheets reshape data today.
- Design. Purpose, hierarchy, posting rules and a default for each dimension, tested against real transactions.
- Cleanse. Retire codes unused in recent years. Merge duplicates across organisations.
- Map. Each new account records the legacy codes it replaces. Finance One holds the translation for every feeding system.
- Prove. Rebuild the trial balance at full code level in each mock load, and reconcile line by line.
Your systems keep their codes
Your housing management system, purchase-to-pay tools and planning model keep posting with today's codes.
The Finance One integration accelerator translates them into the new chart and validates each posting before it reaches the ledger. You can redesign the ledger and change the feeding systems later, on your own timetable.
Coding controls at source
Related values limit each choice to what fits the one before it.
Pick a company and only its cost centres appear. Pick a cost centre and only its properties and tenure appear. Miscoding drops, and finance spends less time on correcting journals at month end.
Coding that stays right: controls in a housing chart of accounts
Who does what
PCL One
- Leads the design workshops and writes the solution design
- Builds the chart, hierarchies and coding rules in Oracle Fusion
- Maps legacy codes and loads balances at full code level
- Sets up the change process for new codes after go-live
Your team
- Names the finance lead who signs off each dimension
- Confirms the reporting views the board and regulator need
- Supplies the legacy code lists and the property hierarchy from the housing system
- Approves new codes after go-live
Proof from UK social housing
At Riverside, which manages more than 75,000 homes, over 17,000 of them under the One Housing name in London and the South East, PCL One rationalised the chart of accounts from hundreds of legacy codes into a standard structure with a multi-dimensional reporting hierarchy, and migrated and validated its historical transactions. The month-end close has accelerated.
Two charts into one: finance after a housing mergerChart of accounts design for clearer housing reporting
Chart of accounts: questions housing associations ask
How long does a chart of accounts redesign take?
Design runs alongside the finance implementation, in the design phase of your plan, and the chart is then proved through each mock load. Starting from a structure already live in UK housing shortens the design, because your team reviews and adjusts it.
Do our housing and planning systems have to change?
No change is needed at go-live. Finance One maps the codes those systems send today into the new chart and checks each posting. You can move each system to the new codes later, once the finance platform is stable.
Can we report service charges by block and tenure?
Yes. Property group holds estates and blocks, tenure has its own dimension, and allocations split shared costs across tenures. Budget holders see the same structure your service charge team uses for apportionment and year-end statements.
What happens to our historic reporting?
Each new account records the legacy codes it replaces, and history is migrated at full code level. Prior-year comparisons run in the new structure, and the legacy code stays traceable for audit.
We are merging. Should we wait for one chart?
Design one chart now and give each organisation its own company and ledger in it. On merger day, balances move to the surviving entity by a controlled journal and history stays reportable.
Start with the reports you need
Bring your current chart and your three most-used reports. We will show you how they look in the new structure.
PCL One (PayrollCloud Limited)
International House, 12 Constance Street
London E16 2DQ
United Kingdom