GRI Reporting for Groups

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Group reporting is often described as a simple extension of financial consolidation: identify the subsidiaries, issue a reporting pack and add the numbers. GRI reporting is more complex. The legal entities included in the published report are only one boundary. The organisation must also identify significant impacts across activities and business relationships, including relationships that are not controlled or financially consolidated. Individual Topic Standards may then require site-level, workforce-level, value-chain or other disaggregated information that cannot be understood from a single group total.

The practical challenge is to build one coherent reporting system without pretending every disclosure follows the same consolidation rule. A group policy can be described once, but local exceptions may determine whether the policy is actually implemented. A global total can show scale, but a site-specific impact can disappear inside it. A recently acquired entity may be in the year-end financial group but have only partial-year sustainability data. A non-controlled joint venture may be outside the entity list yet remain important to the impact assessment. These distinctions should be designed into the reporting instructions rather than repaired at the drafting stage.

A robust group methodology distinguishes three boundaries. The first is the list of entities included in the organisation's sustainability reporting under GRI 2-2. The second is the impact-assessment boundary under GRI 3, which extends across activities and business relationships and can include suppliers, franchisees, investees, customers or non-controlled ventures. The third is the disclosure-specific boundary: the entities, sites, people, value-chain population or activities represented in a particular metric or narrative.

Figure 1. Three boundaries a reporting group must not confuse: reporting entities, disclosure-specific consolidated data and the wider impact universe. They can overlap, but each decision must remain explicit and traceable.

Disclosure 2-2 establishes the group-level transparency. The organisation lists all entities included in its sustainability reporting. If it has audited consolidated financial statements or public financial information, it specifies differences between the financial and sustainability entity lists. If it consists of multiple entities, it explains the consolidation approach, including whether information is adjusted for minority interests, how mergers, acquisitions and disposals are treated, and whether the approach differs across GRI 2 disclosures or material topics.

The guidance says the organisation should report information for the same group of entities covered by financial reporting and separately identify additional sustainability-reporting entities. This is guidance, not permission to assume that every sustainability metric must follow financial accounting ownership percentages. GRI 2-2 explicitly anticipates differences across disclosures and material topics. Those differences need a documented rationale and clear public explanation.

Consolidated reporting does not mean every disclosure should name every subsidiary. The appropriate level depends on what the information user needs to understand the impact and how the organisation manages it. A group narrative works when it describes a genuinely common governance arrangement, policy commitment, methodology or control. Local detail becomes necessary when the impact, implementation, performance or limitation differs in a way that matters.

The group should issue a controlled consolidation instruction before requests are sent. It should define the entity census, common terms, local evidence, review responsibilities and treatment of boundary changes. The workflow below prevents local teams from making inconsistent decisions that are difficult to reverse after consolidation.

Figure 2. Group consolidation workflow from a locked entity list and common instructions through local submissions, consolidation, challenge of material differences and approved publication.

Create the entity census. Reconcile legal entities and operating sites to financial reporting, identify control and minority interests, and record acquisitions, disposals, dormancy and reporting contacts.

Approve the group data manual. Define terms, period, units, boundaries, conversions, intercompany treatment, estimates, restatements, evidence and local sign-off requirements.

Issue entity-specific packs. Each local team receives only the applicable disclosures, sites and populations, but uses the same row IDs and definitions as the group register.

Obtain local preparation and review. Require the responsible local owner to confirm completeness, methodology, exceptions and evidence before central consolidation.

Perform central validation. Reconcile populations, test duplicates and omissions, challenge variances, assess local exceptions, confirm currency/unit conversions and review boundary changes.

Consolidate by disclosure. Apply the approved method for each metric and retain the entity-level bridge from local submission to the group total.

Draft group and local narrative. Describe common arrangements once, then add entity/site detail where the impact or implementation differs materially.

Approve and publish the boundary note. Explain the GRI 2-2 approach, disclosure-specific differences, acquisitions/disposals and material limitations consistently with the Content Index and assurance scope.

GRI 2-2 requires the organisation to explain whether its consolidation approach involves adjustments for minority interests. It does not impose one universal percentage method for every sustainability disclosure. The appropriate treatment depends on what is being reported. A site operated and controlled by the group may be reported at 100% for operational energy or incidents even when the parent owns less than 100%, while an investment metric may use another defined basis. The method should not be selected simply to improve performance.

Boundary changes can affect the current total and the historical trend more than operational performance. The group should prepare a bridge showing the effect of entities entering or leaving, partial-year periods, methodological alignment and corrections. GRI 2-4 identifies disposals, mergers and acquisitions among possible reasons for restatement. Whether the group restates comparatives depends on its criteria and the availability and reliability of historical data, but the decision and effect should be documented.

Country teams often have legitimate legal, system or operational differences. The solution is not to force a false uniformity or allow uncontrolled local methods. A local exception should identify the group rule, the reason it cannot be applied, the alternative method, the affected population, the quantitative or qualitative effect, the reviewer and the expiry or remediation plan.

Use a controlled group glossary with examples and explicit do-not-include rules, not only a short definition.

Require local-to-group mapping tables for workforce categories, incident classifications, renewable energy instruments and other judgemental data.

Retain original local values and classifications before conversion so the group result can be reconstructed.

Run exception reports for unexpected zeros, category shifts, missing sites, duplicate intercompany populations and unit changes.

Separate legal compliance definitions from GRI reporting definitions where they answer different questions, and explain the chosen reporting basis.

Make the methodology owner responsible for approving definitions; do not allow each country to interpret the GRI requirement independently.

The note identifies the entity list, financial-reporting reconciliation, metric-specific differences, consolidation basis, impact boundary, acquisition date and comparative treatment. It still needs exact entity references and topic-specific limitations elsewhere in the report.

The group first reconciles the sustainability entity list to financial consolidation. It identifies the acquisition and disposal, then creates metric-level boundary instructions. The acquired subsidiary is included for environmental and workforce data from the acquisition date, with a clear partial-year limitation. The disposed entity is included to the disposal date, while ongoing remediation obligations remain in the management narrative. The non-controlled joint ventures are not aggregated into all GRI 2 metrics, but their activities are considered in the impact assessment and described where the parent is linked to significant impacts.

The group policy on human rights applies across controlled entities, but one regulated subsidiary has a different grievance channel. The report gives the group commitment and adds the local exception because it affects how concerns are raised. Biodiversity impacts are concentrated at two sites, so the group narrative is supplemented by site-specific information rather than only a global hectares total. The boundary register, local sign-offs and consolidation bridge allow reviewers to trace the published group figures back to each entity and exception.