Glossary›Emissions accounting and measurement›Emissions inventory boundary vs reporting boundary

Glossary term

Cluster D · D28

Tier 1 · differentiator

Emissions inventory boundary vs reporting boundary

Definition

The inventory boundary defines which entities and emission sources are inside a greenhouse gas inventory, set under the GHG Protocol using operational control, financial control or equity share. The reporting boundary defines which entities are inside the statutory report, set by the accounting consolidation. They are drawn under different rules and do not automatically match.

GHG Protocol Corporate Standard (2004)

· chapters 3 and 4 ·

In force

In practice

This is the single most expensive structural error available to a first-time Australian reporter, and it is almost always discovered late, because both boundaries individually look correct.

The reporting boundary is not a choice. A captured entity’s sustainability report covers the same reporting entity and the same period as its financial report, so the consolidated group determines who is in. The inventory boundary is a choice, made once and disclosed. Under the GHG Protocol an entity selects a consolidation approach: operational control, financial control or equity share. Operational control is the dominant Australian practice, largely because it aligns with NGER.

The two diverge in predictable places.

Situation

Reporting boundary

Inventory boundary (operational control)

A joint venture the group does not operate

Inside the financial consolidation under equity accounting

Outside

A leased site the group operates but does not own

May sit quite differently in the accounts

Inside at 100 per cent

A subsidiary acquired mid-year

Contributes a part-year to the financial report

Needs an explicit part-year decision

None of those divergences is wrong. All of them are findings if they are not written down.

What the assurer does with it

The assurer performs a reconciliation between the two boundaries as a matter of course, and they build it from the financial side because that population is already audited. They take the group structure note or the consolidation schedule, list every entity, and ask the reporting team to mark each one in or out of the inventory with a reason.

They accept a difference that is explained by the stated consolidation approach and applied consistently. They reject an entity marked out with no reason, an entity treated differently from a structurally identical entity, and a boundary approach named in the basis of preparation that the inventory does not actually follow, which is common where the document says operational control and the model was built on ownership percentages.

The follow-up request where a divergence exists is usually the joint venture or associate agreement, because operational control turns on who directs the operating policies, and that is a documented fact rather than a judgement.

Commonly confused with

Scope 1, 2 and 3, which sit inside the inventory boundary rather than defining it. The boundary decides which entities are in; the scopes classify the emissions of the entities already in. Also confused with the capture test for mandatory reporting, which uses consolidated revenue, assets and headcount and has nothing to do with the inventory boundary.

Sources

1

Greenhouse Gas Protocol: A Corporate Accounting and Reporting Standard (2004 revised edition)

GHG Protocol

2

AASB S2 Climate-related Disclosures, compiled to December 2025

AASB

Review status

Review required

Last reviewed

15 September 2026

Editorial pass, unsigned

Reviewer required

Carbon accounting specialist and registered company auditor

Next scheduled review

1 July 2027

Part of

Cluster D, Emissions accounting and measurement

49 terms from the head term carbon accounting down to individual Scope 3 categories and the mechanics of factors, boundaries and data quality. The largest cluster in the glossary.

Where this sits commercially

Carbonhalo builds the boundary reconciliation from the audited consolidation outward, which is the direction the assurer will test it from.

Other terms in this cluster