185
Entities modelled
Group financial intelligence model
ERP & group data architecture In progress
Designed a common reporting model to compare actual results, budgets and forecasts across 185 entities, different currencies and accounting systems.
-
The problem
The group lacked one model for actuals, budgets, forecasts and multi-currency trial balances across its ERP estate.
-
My role
Designed conformed entity, currency, scenario and period dimensions so measures resolve consistently.
-
Where it stands
Completed the blueprint and prototype logic; governed warehouse or semantic-layer implementation remains in progress.
Results and evidence
actual · budget · forecast
Scenarios
Business impact
Creates the foundation for consistent group intelligence and executive reporting.
How I did it
- 01
Set trial-balance line by entity, period and scenario as the model grain.
- 02
Applied IAS 21 currency translation as a modelled step rather than embedding it in source data.
Tools and working context
185 entities across heterogeneous ERP environments and multiple currencies.
- Tools
- Semantic layer design · Power Query · Power Pivot
- Business area
- Group reporting · Data architecture
- Skill type
- Data & Reporting · ERP & Systems
Why I made these choices
- Designed reusable group infrastructure rather than another one-off report.
- Prioritised a controlled model grain and conformed dimensions over report-specific shortcuts.
Skills used
- Power Pivot Data & Reporting Strong
- Semantic layer design Data & Reporting Applied
- Multi-entity governance & CFO stakeholder management Ways of Working Strong
What I learned
- A reusable model answers new questions without rebuilding each report.
What comes next
- Land standardised inputs and implement the model in a managed data store.