Group reporting
What does manual group reporting cost?
Sumledger
The cost of manual group reporting is not just the hours spent assembling a report. It also includes rework, waiting and the time the CFO needs to explain a figure. Here is a practical way to measure the work before you consider a new system.

The cost of manual group reporting is not just the hours spent assembling a report. It also includes rework, waiting and the time the CFO needs to explain a figure. Here is a practical way to measure the work before you consider a new system.
Start with the workflow, not the licence fee
For a privately held group with several companies, Excel can be a good reporting tool. The problem begins when the finance team has to collect the same files again, repair links and reconstruct checks every month. The spreadsheet has become more than a format: it carries part of the groupâs control process.
A new system is not automatically a worthwhile investment. A simple process with few exceptions may work well in Excel or the existing ERP. Base the assessment on work actually performed, tasks that could change and controls that will still be needed.
A useful starting model is:
Monthly labour cost = active hours per task Ă internal hourly cost for the role.
Then add up the tasks. Record waiting time and risk separately. Waiting two days does not mean a controller spent two working days on the report, and a possible error is not a documented cost.
Break the work into five tasks
Track a normal month-end from the first data extraction until the report is ready for review. Use the same scope next month, and separate initial setup from recurring work.
1. Data collection
What to record: Exporting, receiving and checking source data
Control question: Are all companies and periods included?
2. Mapping
What to record: Linking local accounts and dimensions to the group structure
Control question: Does the report line mean the same thing across companies?
3. Group adjustments
What to record: Intercompany differences, eliminations and group journal entries
Control question: Are the basis and treatment documented?
4. Report preparation
What to record: Formulas, compilation and versions
Control question: Can the report be reproduced from the same underlying data?
5. Explanation
What to record: Following up variances and management questions
Control question: Can the figure be traced to its underlying details?
Do not use reconciliation as a catch-all term. Checking collected data, mapping accounts and making group journal entries address different problems. Combining them in a single time entry makes it hard to identify what an integration can actually reduce.
Include work in subsidiaries too. A report that takes one hour centrally may depend on many hours locally. At the same time, avoid counting the same task for both the local finance manager and the group controller.
A worked example with explicit assumptions
Suppose the CFO of a privately held group wants to understand why reporting keeps pushing analysis back. The controller records active hours through one month-end. The figures below are a hypothetical example, not customer data, a market estimate or a documented Sumledger saving.
- Data collection and source checks: 8 hours per month
- Mapping and report structure maintenance: 5 hours per month
- Intercompany differences, eliminations and group journal entries: 7 hours per month
- Report preparation and version management: 6 hours per month
- Variance explanation and follow-up: 4 hours per month
Total: 30 hours per month
At an assumed internal hourly cost of NOK 800, the calculated resource cost is NOK 24,000 per month. If the same work repeats twelve times, the annual value is NOK 288,000. This assumes a stable scope; year-end work, acquisitions and major changes are not automatically included.
NOK 288,000 is not a potential saving to compare directly with a licence fee. Some of those 30 hours are necessary professional checks. The controller must still assess variances, investigate intercompany differences and explain the report.
Instead, suppose a limited trial shows that ten hours can be freed up without weakening control. The calculated capacity value is then NOK 8,000 per month, or NOK 96,000 per year. That is still not a cash saving. Payroll costs do not fall if the team uses the time for better analysis.
Compare against the full cost of change
A credible business case includes more than the subscription. Request specific details on integrations, data access, setup, training and ongoing maintenance. Include the finance teamâs own time to establish and check the reporting structure.
Keep two assessments separate:
- Capacity: How many active hours can move from recurring data preparation to analysis or follow-up?
- Cash flow: Which actual payments will decrease, and which new payments will arise?
For a financial comparison, calculate the capacity value of time freed up and deduct new recurring costs. Show one-off costs separately. Call the result a capacity-based assessment, not a realised benefit.
If you calculate a payback period, the denominator must be positive and based on a comparable benefit. A hypothetical value of time and an actual cash payment answer different questions. The CFO should be able to see both without conflating them.
Measure waiting and rework without pricing everything
Time to a completed report can matter even when active hours are low. Missing data from one company can hold up the entire review. Record when data became available, when the first report version was ready and when the review was completed.
Also note the number of repeat extractions, manual corrections and report versions. Briefly explain why they occurred: the wrong period, a missing account, changed mapping or a late posting. This makes the required action concrete. Repeated extractions caused by an incorrect period call for a different response from an unresolved intercompany difference.
Do not assign an arbitrary monetary value to âfewer errorsâ. Describe the checks performed, the exceptions they caught and who assessed them. Better documentation can be valuable without converting it into an uncertain ROI percentage.
Test one report before drawing conclusions
Choose a recurring group report with known underlying data. Document the companies, period, reporting structure and relevant group journal entries before the trial. Then compare the same scope of work in the current process and the alternative.
A practical check is to trace one report line back to company, account and transaction. Include vouchers and attachments where supported by the source system and access permissions. Check how changed mapping or a late posting affects the result. Faster extraction is not enough if the controller must manually reconstruct the explanation afterwards.
Measure active hours, rework and traceability over several comparable reporting cycles. The first cycle often includes training and setup. Do not present the best individual cycle as normal operation.
Read more about the path from system integration to an explainable group figure.
When is a shared control layer relevant?
A shared control layer becomes relevant when group-level work repeats across companies and accounting systems, and the current workflow makes figures difficult to verify or explain. The number of companies alone does not determine the need.
Sumledger supports financial controlling, group reporting, consolidation, eliminations and group journal entries across existing accounting systems. Access to detail depends on source data and integration. It does not replace professional judgement or a separate system for statutory year-end accounts and tax.
See how group reporting in Sumledger fits the work you have mapped. If your existing ERP or Excel already provides a simple, traceable and stable process, keeping it may be the right choice.
Next step: bring one report and a time log
Before comparing systems, record one month-end. Separate necessary controls from recurring data preparation, and describe how you would use any time freed up. That creates a concrete discussion about needs, not just price.
Book a short demo to explore how Sumledger could support this specific workflow.
Relevant to explore
Group reporting
Unify reporting and consolidation for growing groups across companies and systems.
Financial control
Start at group level and drill down to company, account, transaction and voucher where data is available.
Multi-ERP control
Give finance one shared control layer even when subsidiaries use different ERP and accounting systems.
Shared reporting
Work from a shared reporting basis across your companies. Data is imported every hour so CFOs and controllers can follow performance and investigate variances.
Bring one report and a time log
Explore how Sumledger can support control and reporting across your group companies.
Book a short demoRead next
Related articles

From system integration to an explainable group number
Five control steps that make ERP data comparable, reconciled and explainable in group reporting.

Group reporting and year-end: what do you need?
Group reporting and statutory year-end work solve different problems. Before replacing finance software, establish whether the gap is ongoing visibility, controls before posting, or the year-end deliverables. Otherwise, a better reporting tool can become a poor system replacement.