Most organisations reporting on carbon end up working with one of two frameworks: ISO 14064 or the GHG Protocol. Both are respected, and both do the same underlying job, but they get there differently.
ISO 14064 provides a structured framework with detailed categorisation of emissions. The GHG Protocol takes a scope-based approach that follows emissions through the value chain, from a company’s own operations out to its suppliers and customers. Which one an organisation ends up using often comes down to what their regulator, investors, or industry expects, and increasingly, organisations need to report against both at once.
What ISO 14064 asks for
ISO 14064:2018 organises emissions into six categories, covering everything from direct emissions within an organisation’s own boundaries to indirect emissions from energy use and transportation. It’s a granular structure, built for organisations that need to show exactly where each tonne of carbon sits in their operation, not just a total figure.
EnergySys supports ISO 14064 through configuration, letting teams allocate emissions to each of the six categories and track them alongside the operational data that produced them, rather than as a separate, disconnected calculation.
What the GHG Protocol asks for
The GHG Protocol classifies emissions by scope. Scope 1 covers direct emissions from a company’s own operations. Scope 2 covers indirect emissions from purchased energy. Scope 3 covers everything else across the value chain, supply chain emissions, business travel, the use of sold products, and more.
Scope 3 is usually the hardest of the three to get right, since it depends on data an organisation doesn’t fully control. Reporting against it well means identifying where the largest emission sources actually sit in the value chain, then building a process that can keep tracking them as that chain changes.
Why organisations end up needing both
Increasingly, organisations don’t get to pick one framework and stick with it. A regulator might require ISO-aligned reporting while an investor or industry body expects GHG Protocol scopes. Rather than running two disconnected reporting processes, the more practical approach is one system that can produce both views from the same underlying data.
The regulatory pressure behind this is real and moving fast. KPMG’s guidance on Australia’s climate disclosure requirements confirms that mandatory climate-related disclosure under the Australian Sustainability Reporting Standards has applied to large entities since financial years beginning on or after 1 January 2025, with the assurance requirement phasing up to full, reasonable assurance of all climate disclosures by 2030. Australia isn’t unusual here: the EU’s Corporate Sustainability Reporting Directive and the US SEC’s climate disclosure rules are running similar timelines, each requiring Scope 1 and Scope 2 emissions data that can withstand independent, third-party assurance, not just a number in an annual report.
That assurance requirement exists because the alternative has a real cost. PwC’s Global Investor Survey found that 94% of investors believe corporate sustainability reporting contains some level of unsupported claims, greenwashing, in other words, up from 87% the year before. Getting the numbers right isn’t just a compliance exercise. It’s what determines whether investors, regulators, and customers trust the reporting at all.
That’s the model CarbonOptics has built on EnergySys for operators navigating Australia’s NGER scheme and the Safeguard Mechanism: a multi-framework emissions application that automates data collection, tracking, and regulatory reporting, built on the same platform as production allocation. That means one auditable source of truth for both operational and environmental data, rather than two separate systems that need reconciling by hand, and an audit trail that can stand up to the assurance requirements now being phased in.
The same underlying flexibility helped an Australian E&P operator configure their own carbon capture and storage reporting directly, without a heavy IT build, and adapt it as regulatory requirements have continued to evolve.
The practical case for one platform
Whichever framework an organisation reports against today, the requirements around it tend to change. Regulators update thresholds. Investors ask for more granular Scope 3 detail. A new market brings a new reporting standard with it.
Because EnergySys is configurable rather than fixed, teams can adapt their emissions reporting as those requirements shift, rather than waiting on a vendor to build support for whatever comes next. The same platform that tracks production, allocation, and revenue can carry the carbon data too, on one auditable record rather than several.
Explore how EnergySys supports emissions and CCUS data management, or get matched with an EnergySys partner who specialises in your reporting framework.
