Group reporting

Continuous group reporting: from data to control

Sumledger

Continuous group reporting means the finance team updates and checks the group's reporting data throughout the month, rather than leaving all the work until month-end. It does not mean every new figure has been reconciled, or that the month-end close disappears. The benefit is spotting discrepancies earlier and knowing what remains unresolved.

Hero image with the Norwegian title “Løpende konsernrapportering” and subtitle “Oppdaterte data. Avklarte avvik. Kontrollerte tall.” Illustration featuring fictional Almvik Holding.

Continuous group reporting means the finance team updates and checks the group’s reporting data throughout the month, rather than leaving all the work until month-end. It does not mean every new figure has been reconciled, or that the month-end close disappears. The benefit is spotting discrepancies earlier and knowing what remains unresolved.

For CFOs and controllers in a privately held group, this raises a practical question: which figures can management use now, and which need to be checked first? The answer requires more than frequent data imports. It requires a shared report definition, ownership of discrepancies and a clear distinction between preliminary insight and approved reporting.

What is continuous group reporting?

Continuous group reporting is a way of working that spreads data collection, checks and explanations throughout the period. Companies report into a reusable group structure. The finance team follows up on changes in source data, account mapping and group adjustments before the formal close.

“Continuous” describes the working rhythm, not a guarantee of real-time or final figures. A report can include the latest posted transactions and still be missing accruals, intercompany entries or an agreed classification. Report recipients should therefore know both which data the report is based on and what has been checked.

A useful report note might read: “Updated with posted transactions. Accruals in one subsidiary and reconciliation of intercompany transactions remain outstanding.” That is more useful for decision-making than a green status with no explanation of what it covers.

Three points in time that must not be confused

When was the data updated?

This is when new data was retrieved from the accounting system. Check the entities covered, the period and the last successful update. A recently updated group report may still contain older data from one company if that source was not included.

The import time does not tell you when the underlying event took place, either. An invoice may be posted several days after delivery. More frequent imports make posted data available sooner, but they do not make posting backlogs invisible or irrelevant.

When was the underlying data checked?

Reconciliation against the source must cover the same period, selection and posting status. Account mapping needs a separate assessment: matching totals do not mean every account sits on the right report line. Intercompany entries and group adjustments require their own checks.

Read more about how Sumledger supports group reporting across companies. The point is to be able to trace the data behind the figures, not just display a combined total.

When was the report approved for use?

Approval applies to a specific set of data and a specific purpose. A preliminary overview for operational management is not necessarily the same deliverable as the monthly report to the board.

Agree who will assess material changes after approval. If source data is updated, the finance team needs to be able to identify which report lines and explanations require reassessment. An earlier approval should not automatically be taken as approval of new figures.

A controller scenario: the intercompany invoice arrives later

Consider a privately held group where the controller tracks performance throughout the month. This example illustrates a workflow; it is not a customer story.

One subsidiary has posted an intercompany invoice as revenue. The counterparty has not yet posted the expense. The latest posted transactions from both companies have been imported. The group overview is therefore up to date, but the intercompany transaction has not been resolved on both sides.

The controller records which companies, period and intercompany entry the difference relates to. The person responsible for the counterparty’s bookkeeping is asked to clarify whether the invoice has been received, which period it belongs to and whether a correction is needed. The group’s accounting policies determine the treatment; a discrepancy should not be hidden with an arbitrary offsetting entry.

Once the source has been updated, the affected check is repeated. The elimination and its impact on the report are then assessed. If management has already received an explanation of the change in profit, the controller must also assess whether that explanation still holds.

Here, ongoing work means the discrepancy becomes visible before the closing deadline. It does not mean the system alone can determine whether the invoice is correct or whether all eliminations are complete.

Spread checks throughout the month

A sensible rhythm follows risk and decision-making needs. Not every group needs a daily review of every report line. Start with the items that often lead to rework at month-end.

When data is updated: check coverage

Check that the expected companies and periods are included. Investigate missing or delayed data before interpreting changes as business performance. New accounts and unexpected dimension values should be assessed when they appear, not only when the report is due to be sent.

During the period: resolve known discrepancies

Assign an owner and agreed follow-up to each material discrepancy. Distinguish between source errors, mapping errors and the need for a group adjustment. They can affect the same report line but require different actions.

Use meeting time for issues that need collaboration. A controller should not have to spend an entire status meeting reading out data everyone already has access to. Keep open questions visible until their resolution is documented.

At month-end: complete and document

Check accruals, reconciliations, mapping, intercompany transactions, eliminations and other group adjustments according to the group’s needs. Document which outstanding matters have been resolved and which, if any, have been accepted with a stated reason.

Ongoing checks do not replace year-end reporting or statutory assessments. They should make the underlying data easier to understand before those tasks are carried out.

A simple control log you can use now

You do not need a new system to try this way of working. Choose one recurring report and record the following in the tool you already use:

  • Scope: company, period and report line.
  • Data basis: source system, selection and last update.
  • Check: what has been reconciled or assessed, and against which data.
  • Outstanding matter: a specific difference or question, not just “needs checking”.
  • Responsibility: who will resolve the matter and when it will be followed up.
  • Resolution: conclusion, documentation and the need for another check if anything changes.

This is a recommended working routine, not a description of specific fields or automation in Sumledger. Keep the log short enough to be used in practice. The aim is for a colleague to understand what remains outstanding without asking the person who built the report.

When is Excel or ERP reporting sufficient?

If the group uses one accounting system with reporting that meets its needs, the existing solution may be right. The same applies to a documented Excel model with limited intercompany transactions, few changes and low handover risk.

The need for a shared control layer becomes clearer when work is repeated across companies and systems: collecting data, explaining mapping, investigating transactions and checking group adjustments. Assess this work before comparing product feature lists. See also control across ERP systems.

Sumledger connects accounting systems to a shared control layer for group reporting, financial control, consolidation and eliminations. Data is imported every hour. That is not the same as real-time reporting or automatic approval. Access to transactions, vouchers and attachments depends on the available source data.

Start with one report, not a new calendar

You do not need to wait until the new year. Choose a report you use regularly, agree which checks can be brought forward and retain clear responsibility for the final deliverable.

Track whether more discrepancies are resolved before month-end, how much rework remains and whether a colleague can explain the underlying data. Compare periods with a similar scope. More updates are not a result in themselves; the goal is a group figure that is better explained and checked.

Would you like to assess how this could work across your companies and accounting systems? Book a 20-minute demo, starting with the report you actually need to check.

See how ongoing group reporting could work for you

Explore how this could work across your companies and accounting systems, starting with the report you actually need to check.

Book a 20-minute demo

Read next

Related articles

Sumledger blog hero about five control steps from system integration to an explainable group number.
Financial controllingSumledger

From system integration to an explainable group number

Five control steps that make ERP data comparable, reconciled and explainable in group reporting.

Measure manual reporting work. Illustration featuring fictional Almvik Holding.
Group reportingSumledger

What does manual group reporting cost?

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.