Reconcile site ESG totals to the reporting entity

Before adding site submissions, build a bridge from the records received to the operations and period that the report actually covers. Identify missing sites, overlapping records, excluded activity and adjustments separately. Keep every change traceable to evidence and a decision owner.

This guide is for reporting teams consolidating ESG information across factories, offices, warehouses or branches. It assumes the entity boundary has been approved. It helps test the roll-up; it does not choose the organisational boundary or supply a universal aggregation rule for every metric.

Use two lists with different purposes

The expected coverage list names the entities, sites, sources and relevant dates that should contribute to the chosen metric. The received-record list shows what departments actually sent. Comparing the two finds omissions that a neat total cannot reveal.

For BRSR, the disclosed standalone or consolidated boundary should be applied consistently across the report. Source: SEBI master circular, Annexure 17, general guidance 2. Record the approved boundary version on the consolidation schedule. Differences between metric populations still require the appropriate definitions and explanation.

Give each expected input a stable identifier and a coverage status: received, partial, missing, excluded with reason or awaiting a decision. Do not make the received spreadsheet itself the master site list.

Resolve overlap before calculating the entity result

Ask what physical activity or population each record represents. Common checks include:

• Does a main-meter total already contain the sub-meter readings?

• Has the same invoice appeared in both a finance extract and a facilities schedule?

• Does a shared-premises total include another entity's activity?

• Do consecutive bills overlap or leave a gap at year-end?

• Has an employee transfer produced two records for the same person at the same reference date?

• Is a site total already included in a regional or subsidiary subtotal?

Retain the overlapping records for explanation, but identify which record contributes to the final total. Do not delete source evidence merely to remove a duplicate from the calculation.

A hypothetical electricity reconciliation

Fictional example, not a Nitium client case. A standalone reporting entity is preparing purchased-electricity consumption for 1 April 2025 to 31 March 2026. Its initial submissions contain:

• Factory main meter: 600,000 kWh

• Factory production sub-meter: 180,000 kWh

• Separate office meter: 100,000 kWh

The unreviewed sum is 880,000 kWh. The source map confirms that the production sub-meter is entirely within the factory main-meter coverage. Removing that duplicated contribution leaves 700,000 kWh.

The expected coverage list then identifies an omitted warehouse with 40,000 kWh of supported consumption. Separately, a dedicated sub-meter and the reviewed premises arrangement establish that 40,000 kWh within the factory main-meter total belongs to an unrelated tenant outside the reporting boundary.

The documented bridge is:

880,000 kWh received − 180,000 kWh duplicated + 40,000 kWh omitted warehouse − 40,000 kWh outside-boundary tenant = 700,000 kWh.

Assume for this example that all quantities cover the same year, the source measurements are reliable and the boundary treatments have been approved. The warehouse addition and tenant subtraction happen to offset. That coincidence does not make either correction optional: they establish which operations the final number represents.

The result is an electricity-consumption schedule. It is not total energy, an emissions figure or proof of regulatory compliance. Renewable classification and any emissions calculation require the relevant additional records and method.

Choose the aggregation rule for the metric

Use the reporting definition to decide how inputs combine:

• Quantities: sum comparable, non-overlapping activity within the same period and boundary after documented unit conversion.

• Point-in-time people counts: reconcile the population at the stated date and address duplicates. Adding monthly headcounts does not produce an annual headcount.

• Ratios and percentages: retain their numerators and denominators. Do not add site percentages or take a simple average unless that operation matches the intended measure.

• Policies or process statements: identify coverage and exceptions. A policy at one site does not automatically establish implementation across all sites.

For example, two fictional sites with 8 of 10 and 9 of 30 people meeting the same defined criterion have combined coverage of 17 of 40, or 42.5%. Averaging 80% and 30% gives 55%, which answers a different question. This arithmetic illustration is not a prescribed BRSR indicator.

Keep a reconciliation bridge

Record the submitted value and unit, adjustment amount, adjustment type, reason, source reference, affected site/period, reviewer and resulting total. Keep boundary decisions separate from arithmetic corrections. An unexplained balancing entry should remain an open issue.

• Expected and received populations reconcile, including missing inputs

• Every contributor has a unit, period and boundary

• Overlaps are removed from calculations while evidence remains available

• Adjustments have support and approval

• The metric's aggregation rule is appropriate

• The final result agrees with the reporting schedule and relevant narrative

Use our BRSR evidence-file guide for the source-to-disclosure trail. Nitium's BRSR reporting support can help organise collection and gaps across the agreed entity scope. Discuss a site-consolidation problem or email contact@nitium.in with a non-confidential description of the mismatch.

Sources checked 5 October 2026. This workflow does not validate source measurements, determine entity-specific accounting treatment or provide independent assurance. Different indicators can require different populations and methods.