Group reporting
Group reporting and year-end: what do you need?
Sumledger · November 3, 2026
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.

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.
The short answer: reporting is not the whole year-end process
Ongoing group reporting brings financial figures together across companies and explains them so management can monitor performance and make decisions. Year-end work includes closing the accounting year and preparing the required financial statements and tax information under the applicable rules. Consolidation can feature in both processes without making them the same job.
A tool can therefore support monthly group reporting well without covering statutory accounts and tax. Equally, software that handles year-end requirements may not give the finance team the ongoing visibility it needs. Evaluate the deliverable you actually need to produce, not just the product category on a supplierâs homepage.
This guide concerns system selection and responsibilities, not the legal requirements that apply to your group. Those depend on your companies, countries and reporting framework.
Three jobs that often become one software request
âWe need better control of group financesâ is a reasonable starting point, but an imprecise specification. Separate the need into three parts before inviting vendors to demonstrate their products.
1. Controls before posting
The question here is whether a transaction should be approved, documented or corrected before it becomes part of the accounts. Examples include a supplier invoice missing supporting evidence, incorrect coding or uncertainty about approval authority.
The required output is a correctly processed transaction. If this is the bottleneck, evaluate the workflow in or around the accounting system. A combined group report does not replace controls that should have taken place earlier.
2. Ongoing group reporting
The question here is what the figures mean together and whether they can be explained. Finance needs to address entity scope, account mapping, periods, intercompany items, eliminations and group adjustments. Available transactions and vouchers may be essential evidence for the explanation.
The required output is a report management can use, with understandable differences between local and group figures. Retrieving data is one step. Reconciliation, mapping and group entries are separate steps that need to be checked individually.
3. Statutory year-end accounts and tax
The question here is which closing assessments, documents and filings the business needs to deliver. A solution may cover financial statements, notes and tax work, but its scope must be confirmed for the relevant entities and countries.
The required output is more than a presentation of profit and loss and the balance sheet. Do not retire an existing year-end tool until you know how every necessary task will be handled, who will handle it and which system they will use.
A practical scenario: the CFO wants to stop collecting reports
Consider a privately owned group whose subsidiaries use different accounting systems. This is an illustrative scenario, not a customer story. Its accountant handles year-end work in a solution that works well. Yet the CFO spends much of each monthly close collecting local reports, checking account mapping and explaining intercompany differences in Excel.
The CFO asks for âa new consolidation systemâ. During the first demonstration, it becomes unclear whether the request concerns monthly management reporting or a replacement for the entire year-end process. Both parties discuss consolidation but are assessing different deliverables.
A better brief would be: âWe want to keep a functioning year-end process, but reduce the manual work between local accounts and the monthly group report.â The vendor can then demonstrate a relevant report line, its underlying mapping, applicable eliminations and group adjustments, and available evidence.
The accountant should also help define the handover to year-end work. What information will be transferred? Which adjustments need to go back to the accounting systems? Which belong only at group level? The aim is to avoid recording the same change in two places without reconciling them.
Map the work before comparing systems
A simple task map makes the evaluation more precise. Use one row for each actual deliverable and record the current solution, owner, unmet need and what must be retained.
Deliverable
Question to resolve
What a demonstration should show
Approved local transaction
Where does the error arise, and who should approve?
The workflow through to correct posting
Monthly group report
Why does bringing the figures together require manual work?
Source figures, mapping, group entries and explanation
Input for year-end work
Which version and adjustments are transferred?
A reconcilable dataset with clear ownership
Financial statements and tax information
Which tasks and countries must the solution cover?
Specific deliverable scope, not just an income statement
Do not fill the map with features you might need someday. Start with the last report that took unnecessarily long, or a task where responsibility was genuinely unclear. That provides a stronger basis for a decision than a long, unprioritised wish list.
When is an additional tool better than a replacement?
If year-end work runs smoothly but reporting during the year is cumbersome, a separate reporting and control layer may be more relevant than replacing the entire toolchain. It still needs to solve a specific problem that existing systems do not already cover.
If all entities use the same ERP and its built-in reporting meets the need, improving that setup may be the best choice. If the Excel model is simple, documented and requires little work, a new system may not provide sufficient additional value either.
A separate control layer becomes more relevant when finance repeatedly brings data together across systems, maintains shared reporting logic and explains differences between entities. Read more about group reporting across systems and the path from system integration to an explainable group figure.
Define the handover between monthly reporting and year-end
Whatever systems you choose, one person should own the description of what is handed over at year-end. That does not mean doing all the work. It means ensuring that the interface is understood and documented.
Agree which periods and entities the dataset covers, which account mapping was used, and how group adjustments and eliminations are represented. Record where a correction should be made and who checks its effect. Preserve an identifiable dataset so that a later update is not confused with the figures actually handed over.
Test a limited handover before making a full switch. Ask the recipient to explain how one selected report line was constructed and how a later correction would be handled. If this requires verbal help from the modelâs author every time, responsibilities are not yet clear enough.
Where does Sumledger fit?
Sumledger is a control layer for group finance across entities and accounting systems. Its scope includes financial control, group reporting, consolidation, eliminations and group adjustments, with analysis of available supporting data. Sumledger does not currently cover statutory year-end accounts and tax and should not be treated as a complete replacement for a tool you need for those tasks.
Start with the work that remains uncovered. Bring one report, an overview of your systems and a description of what you want to retain. Book a short demo to explore whether Sumledger fits between the local accounts and the group reporting you need throughout the year.
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.
Start with the reporting gap
Bring one report and explore whether Sumledger fits between your local accounts and group reporting throughout the year.
Book a short demoRead next
Related articles

Group finance reporting: 8 checks before sign-off
A practical CFO and controller sign-off: eight checks that make group numbers comparable, traceable and explainable.

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