Contents
A family-owned conglomerate with businesses across the UK, Africa and Asia cut its monthly close from 15 days to 5. It did it by fixing its chart of accounts and group hierarchies first, then moving consolidation out of spreadsheets into SAP S/4HANA Group Reporting, with SAP Analytics Cloud handling planning and rolling forecasts. The software mattered. The order of the work mattered more.
This case is for CFOs and group finance directors still consolidating in Excel. It covers the problem, the approach, the results, the lessons, and a 90-day plan you can adapt.
When I sit with finance leaders in family-owned conglomerates, one theme comes up again and again. The teams still lean on Excel to pull the group numbers together. It worked for years. Once you run businesses across three continents, the cracks show, and what was manageable starts to feel unreliable.
One CFO told me quietly that by the time his team finished consolidating, the board had moved on to new questions. "We close in 15 days," he said, "but the world changes in five." A process problem with strategic consequences.
Each region sent its own spreadsheets. They looked different every time and sometimes arrived late. People spent days chasing numbers, fixing formats and checking balances that never matched. By the time the close was done, the board pack was out of date.
The numbers were questioned more often than not:
- Reconciliation took far too long
- Intercompany balances became arguments instead of answers
- Late reports left leadership without confidence in what it was shown
Auditors raised the same concerns about running a consolidation this size on disconnected spreadsheets. The CFO needed clear numbers for the board and instead spent his time explaining delays.
After a systems evaluation, the group chose SAP S/4HANA Group Reporting for consolidation across all entities, with SAP Analytics Cloud alongside it for planning and rolling forecasts.
The sequence mattered. Before any automation went live, the team spent time on data governance: aligning the chart of accounts, setting up group hierarchies, and naming an owner for each data element. Some found it slow. In hindsight it was what made everything else work.
Migration ran entity by entity rather than all at once, with Data Monitor checks and intercompany matching validated before each entity closed its first period in the new system.
| Common problem | Impact | What changed |
|---|---|---|
| Over-reliance on spreadsheets | Errors pile up; the team reconciles instead of analysing | Consolidation moved into SAP Group Reporting with structured data flows |
| Weak data governance | Inconsistent master data, mismatched results across subsidiaries | Chart of accounts aligned, owners and controls set, before automation |
| Consolidation mixed with planning | Compliance reporting confused with forecasting | Group Reporting for consolidation; SAP Analytics Cloud for planning |
| Cultural resistance | Finance stays in spreadsheet firefighting | Early communication, visible quick wins, changed performance measures |
| Uneven adoption across subsidiaries | Tools underused; visibility stays fragmented | Onboarding by entity, with usage tracked |
The change was obvious in the first close after go-live. What had taken 15 days finished in 5.
- Each region sent its own spreadsheets
- Intercompany balances became arguments
- Board pack out of date on arrival
- One structure for every entity
- Validations block errors before close
- Rolling forecasts in SAP Analytics Cloud
Faster close. Numbers flowed into one structure instead of being chased across spreadsheets. The month-end pressure eased.
Time back for the team. The late nights fixing Excel errors ended. Some admitted they almost missed the deadline drama. Most welcomed the steadier pace.
Audit-ready consolidation. Reports carried the structure auditors expect. Reviews got faster and arguments about version mismatches nearly disappeared.
Scenario planning. SAP Analytics Cloud added rolling forecasts that could test oil price swings, currency moves and the effect of entering new markets, updated whenever assumptions changed.
Better capital allocation. For the CFO the win was strategic: reliable numbers arrived while opportunities still mattered, not two weeks later.
"As Finance Manager in our family group, I rely on SAP to keep budgets clear and spending in check. It gives me numbers I can trust, and the management of the family can rely on for decisions."
Head of Global Financial Reporting, the group
Data governance before automation. The temptation is to start with technology. If chart of accounts alignment, intercompany partner codes and data ownership aren't sorted first, the results fall apart. This project got it right, and it paid off.
Keep consolidation and planning separate. Group Reporting handled consolidation; SAP Analytics Cloud handled planning and forecasts. Mixing them blurs accountability. Audit-ready rules stay in the ERP. Scenarios and versions stay in the planning tool.
Cultural change takes longer than the software. Moving people away from spreadsheet firefighting was hard. Some preferred the old ways because they were familiar. Over time most said they had more room for real analysis. Leaders had to guide the shift, patiently.
Train by entity. Every subsidiary needed clear training. Where teams understood why things were changing, adoption was smoother. Small misunderstandings left alone grew into rework.
If your own close is stuck in spreadsheets for the same reasons, my piece on why CFOs still reach for Excel explains the pattern, and the SAP FICO guide covers the finance modules underneath.
The CFO said quietly: 'We close in 15 days, but the world changes in five.' That is the problem this case solved.
This is the sequence from this programme, reduced to a plan another group can use.
| Days | Focus | Owner | Done means |
|---|---|---|---|
| 1-30 | Scope, owners, close calendar; align entities, currencies and calendars | Group financial controller | One-page ways of working published |
| 1-45 | Chart of accounts and group hierarchy alignment; intercompany partner codes | Group reporting lead with entity controllers | Mapping signed off by every entity |
| 30-60 | Data quality review; load opening and trial balances for the first entities | Data migration lead | Balances reconcile to the legacy close |
| 45-75 | Validations, Data Monitor checks and intercompany matching switched on | Group reporting lead | Test close runs with validations blocking errors |
| 60-90 | First entities close in the new system; weekly checkpoints on blockers | CFO and controllers | One clean period closed in Group Reporting |
The goal at day 90 is not everything. It is a solid foundation and one clean close.
Three things would be different if the same programme started today.
RISE with SAP would change the commercial shape. The S/4HANA side would sit in a single subscription with SAP-run operations. Check which components (Group Reporting, Analytics Cloud) your package actually includes, and model user growth across a multi-entity group carefully, because subscription growth is the line that most often surprises in year three.
Joule would speed up the work after governance. Natural-language questions for finance teams, drafted board commentary and anomaly flags on intercompany variances help once the chart of accounts, hierarchies and partner codes are in place. Joule does not replace the governance work. It speeds up what comes after.
The data layer would be SAP Business Data Cloud. SAP launched Business Data Cloud in February 2025, combining SAP Datasphere, SAP Analytics Cloud and SAP BW with Databricks. For groups with non-SAP subsidiaries, that is now the place to do cross-system harmonisation, rather than building it inside the planning model. My SAP Analytics Cloud guide covers the planning side.
The governance discipline, the separation of consolidation from planning, the patience for cultural change and entity-by-entity training all still apply. Those hold whatever platform sits underneath.
What should the first 90 days of a finance modernisation project focus on?
Scope, owners and a repeating close calendar. Align entities, currencies and calendars so consolidation rules have a stable home. Prioritise record-to-report. Publish one page on ways of working and hold short weekly checkpoints. The day-90 goal is a solid foundation and one clean close in the new system.
How do you migrate from spreadsheet consolidation to SAP Group Reporting without disruption?
Cut over by entity and dataset, not all at once. Load opening and trial balances first, switch validations on early, and run Data Monitor checks and intercompany matching before the group opens each period. Reconcile FX and intercompany partners every cycle. The biggest risk is assuming the data is cleaner than it is.
What is the right split between consolidation and planning in SAP?
Consolidation, intercompany elimination and currency translation belong in S/4HANA Group Reporting, with the audit-ready rules and statutory close. Driver-based plans, rolling forecasts and scenarios belong in SAP Analytics Cloud. The rule: if it has to be defensible to auditors, it stays in the ERP; if it is a working assumption, it belongs in the planning tool.
How do you speed up the monthly close without weakening controls?
Shorten the path and keep the gates. Find the two or three bottlenecks that take the most time each cycle, usually reconciliation loops and late journal approvals, and fix those first. Time-box reconciliations, and let validations block period close until intercompany breaks are cleared. Fix one bottleneck per close cycle.
Which KPIs prove value beyond days to close?
Fewer audit findings each period, forecast accuracy against actuals, and decision cycle time from a board question to a data-backed answer. Retire the vanity metric of reports produced; measure whether reports changed a decision.
How do you keep a clean core while meeting local entity requirements?
Prefer configuration and side-by-side extensions to changing the core. Review custom items every quarter and remove what is no longer used. Give every exception an owner and an expiry date. Say no to core changes by default; local requirements that genuinely need custom handling should be the exception, not the pattern.
Written by
