−85%
Prep time per entity
← All case studies
Finance reporting automation Internal work sample
Group Budget vs Actual reporting suite
Released roughly 1,400 hours of finance capacity a year by replacing fragmented reporting files with one controlled Budget vs Actual suite. Preparation time per entity fell by 85%.
−60%
Reporting cycle
35 → 6 days
Delivery lead time
~1,400 hrs/yr
Capacity released
35 Before — fragmented per-entity work files
bespoke file per entity
6 After — parameter-driven Power Query templates
one maintained codepath serves all entities
Both values as documented in the CV; measured on the live monthly reporting cycle, 2026.
Evidence inputs
- Recurring group reporting across a multinational, multi-entity environment with heterogeneous inputs.
- Excel · Power Query
Transformation
- Replaced fragmented work files with a parameter-driven Power Query template.
- Standardised inputs so one controlled process serves multiple entities and input methods.
- Used entity and period parameters to direct one maintained query path to the relevant source.
Controls & assurance
- Used parameters instead of bespoke entity files to keep the suite maintainable at scale.
- Kept the solution in finance's existing Excel and Power Query environment, with reviewable logic and no additional licence requirement.
Output
- Preparation time per entity fell by 85%; reporting cycle time fell by 60%; delivery lead time fell from 35 to 6 days.
Business value
- Released roughly 1,400 hours a year of finance capacity (EUR 50k–60k value) while improving speed, consistency and reviewability.
- Problem
Fragmented entity files made monthly reporting slow, inconsistent and difficult to review.
- Approach
Replaced fragmented work files with a parameter-driven Power Query template.
- Outcome
Preparation time per entity fell by 85%; reporting cycle time fell by 60%; delivery lead time fell from 35 to 6 days.
Business value
Released roughly 1,400 hours a year of finance capacity (EUR 50k–60k value) while improving speed, consistency and reviewability.
Transformation route
- 01
Replaced fragmented work files with a parameter-driven Power Query template.
- 02
Standardised inputs so one controlled process serves multiple entities and input methods.
- 03
Used entity and period parameters to direct one maintained query path to the relevant source.
Decision log
- Used parameters instead of bespoke entity files to keep the suite maintainable at scale.
- Kept the solution in finance's existing Excel and Power Query environment, with reviewable logic and no additional licence requirement.
This case study proves
- Power Query (M) Data & Reporting Strong
- Excel (advanced) ERP & Systems Strong
- Management reporting & budgeting Finance Strong
What I learned
- Standardising inputs created the scale benefit; the automation then applied one process across entities.
Future improvements
- Connect refresh to the group data model and validate inputs before processing.