GHG Protocol Updates 2026: What Changes in Scope 2 & Scope 3 Accounting (and Why It Matters)

A neutral, compliance-grade briefing on what is required today under existing GHG Protocol guidance and what is proposed/in consultation for 2026–2027—focused on evidence, controls, and audit-ready traceability.

Executive Summary

The GHG Protocol has opened public consultations on Scope 2 topics and the electricity sector consequential work, with consultation announced on Oct 20, 2025. Source The same announcement states the consultation window was initially through Dec 19, 2025 and was later extended to Jan 31, 2026. Source The announcement states that a second public consultation on scope 2 topics will follow in 2026 and that final publication of the new standard is expected in 2027. Source The consultation was initially through Dec 19, 2025 and was later extended to Jan 31, 2026. Source The proposal described by the GHG Protocol announcement retains dual location-based and market-based reporting methods and proposes targeted improvements. Source A central feature described is a new hourly matching and deliverability requirement for market-based reporting. Source The same announcement describes practicality measures including load profiles, exemption thresholds, a legacy clause, and a phased implementation timeline. Source The GHG Protocol announcement states that a second public consultation on scope 2 topics will follow in 2026, with final publication of the new standard expected in 2027. Source

For Scope 3, a stable baseline you can state confidently is that value-chain emissions are categorized into 15 categories as described in the GHG Protocol Corporate Value Chain (Scope 3) Standard (2011). Source The GHG Protocol Scope 3 Calculation Guidance reinforces that the 15 categories are intended to provide companies with a systematic framework for measurement. Source

The “boring but expensive” reality is that any move toward higher temporal and geographic integrity for Scope 2 claims increases data and controls requirements, while Scope 3’s persistent bottleneck remains boundary clarity, traceability, and evidence management across suppliers. Source If you report under IFRS S2 or ESRS, it is important to treat GHGP updates as influential but not automatically incorporated unless references are revised. Source

Download Full Market Intelligence Report (PDF)

Energy Solutions Market Intelligence

Energy Solutions publishes decision-grade, compliance-first analysis for ESG reporting and carbon accounting. This report frames GHG Protocol updates as a governance and controls challenge rather than a protocol tutorial. Source

In This Article

1) What is changing (2025–2027 timeline)

What is officially announced vs what is still proposed

The GHG Protocol announced on Oct 20, 2025 that it opened public consultations on Scope 2 and the electricity sector consequential work. Source The same announcement states the consultation window was initially through Dec 19, 2025 and was later extended to Jan 31, 2026. Source The announcement states that a second public consultation on scope 2 topics will follow in 2026 and that final publication of the new standard is expected in 2027. Source

Existing Scope 2 Guidance vs proposed revisions

The current baseline for Scope 2 accounting is set out in the GHG Protocol Scope 2 Guidance (PDF), which defines the location-based and market-based methods. Source The proposed revisions described by the GHG Protocol announcement retain dual reporting (location-based and market-based) and propose targeted improvements. Source Because the consultation materials are proposals, they should be treated as “proposed/in consultation” rather than final requirements until publication. Source

Compliance classification for this article

2) Scope 2 today (baseline rules you must already follow)

Definition and why it matters to finance and procurement

The Scope 2 Guidance defines Scope 2 accounting approaches and distinguishes the location-based method from the market-based method. Source The location-based method reflects average grid emissions intensity, while the market-based method reflects contractual instrument-based attributes. Source

Dual reporting requirements (location-based + market-based) and when they apply

The Scope 2 Guidance states: “Companies with any operations in markets providing product or supplier-specific data in the form of contractual instruments shall report scope 2 emissions in two ways…”. Source Dual reporting therefore applies when your operations are in markets that provide product or supplier-specific data via contractual instruments. Source

Why Scope 2 methods affect comparability and decision-usefulness

The Scope 2 Guidance defines that location-based reporting reflects grid-average intensity while market-based reporting reflects contractual attributes. Source Because those methods are based on different attribution logic, the two methods can produce different emissions totals for the same underlying electricity consumption. Source For finance and assurance teams, this means the method choice affects comparability across peers and across years when procurement strategies and instruments change. Source

CURRENTLY REQUIRED: minimum “audit-ready” evidence you should already be able to show

The Scope 2 Guidance establishes the concepts of location-based and market-based accounting, which implies you must be able to explain which method you used and why. Source When you operate in markets where contractual instruments exist, the guidance states you shall report Scope 2 in two ways, which implies your reporting package should include both outputs and reconcile inputs (electricity activity data and instrument attributes) to each output. Source Where market-based reporting is used, the guidance defines it as reflecting contractual instrument-based attributes, which implies you should retain instrument documentation and how attributes were applied to consumption. Source Where location-based reporting is used, the guidance defines it as reflecting average grid emissions intensity, which implies you should retain the grid factors used and the boundary logic for each consumption location. Source

Scope 2 baseline: what to avoid (common compliance failure modes)

If you present only one Scope 2 total in a context where the guidance requires dual reporting, that is a governance risk because the guidance explicitly states dual reporting applies when contractual instruments are available in relevant markets. Source If market-based reporting is described but the organization cannot explain which contractual instruments were applied, that undermines the meaning of “market-based reflects contractual instrument-based attributes” as defined by the guidance. Source If location-based reporting is described but the organization cannot explain which grid-average intensity factors were used for each location, that undermines the meaning of “location-based reflects average grid emissions intensity” as defined by the guidance. Source

3) Proposed Scope 2 update themes (expected in 2026 draft direction)

Retained dual reporting + “targeted improvements” (proposed)

The GHG Protocol consultation announcement states that proposed revisions “retain dual location-based and market-based reporting methods” and propose “targeted improvements.” Source This means the proposal does not describe a move to single-method reporting. Source

Core direction: higher time-and-place integrity for market-based claims (proposed)

The GHG Protocol announcement describes a central feature of the proposal as a new hourly matching and deliverability requirement for market-based reporting. Source The same statement frames this as a proposal and therefore not yet a final standard requirement. Source

What “hourly matching and deliverability” implies for organizations (interpretation constrained to proposal text)

The proposal description introduces an hourly matching requirement, which implies that the temporal resolution of evidence for market-based claims may need to be closer to hourly periods rather than purely annual totals if finalized. Source The proposal description introduces a deliverability requirement, which implies that the geographic and network relevance of contractual instruments may become more scrutinized for market-based reporting if finalized. Source The proposal also describes practicality measures such as load profiles and exemption thresholds, which implies there may be defined pathways for organizations that cannot immediately support full granularity in all cases if finalized. Source

PROPOSED / IN CONSULTATION: what you should not claim yet

The GHG Protocol announcement describes proposed revisions and does not state that the proposal is already effective as a final standard. Source Therefore, you should not describe hourly matching and deliverability as “required today” unless and until it is finalized and published as stated in the expected publication timeline. Source

Practicality measures (proposed)

The consultation announcement describes practicality measures including load profiles, exemption thresholds, a legacy clause, and a phased implementation timeline. Source These measures are described as part of the proposal and should be treated as “proposed direction” until final publication. Source

Table A — Scope 2: current requirements vs proposed update direction

Topic Currently required under existing guidance Proposed / in consultation / expected direction Evidence URL
Dual reporting Dual reporting is required when markets provide product/supplier-specific data via contractual instruments. Proposed revisions retain dual location-based and market-based reporting methods. Source Source
Location-based method Location-based reflects average grid emissions intensity. Proposal focuses on targeted improvements; location-based remains part of dual reporting as described. Source Source
Market-based method Market-based reflects contractual instrument-based attributes. Proposal describes hourly matching and deliverability requirements for market-based reporting. Source Source
Practicality / transition concepts Not specified in this article beyond existing guidance baseline. Proposal describes load profiles, exemption thresholds, legacy clause, and a phased implementation timeline. Source
Timing Scope 2 Guidance exists today as the baseline reference. Second consultation in 2026; final publication expected in 2027. Source Source

4) Scope 3 today (baseline rules you must already follow)

Definition and canonical backbone (15 categories)

Scope 3 greenhouse gas emissions are categorized into 15 categories as described in the GHG Protocol Corporate Value Chain (Scope 3) Standard (2011). Source The GHG Protocol Scope 3 Calculation Guidance states that the 15 categories are intended to provide companies with a systematic framework. Source

Why Scope 3 is the audit and data-quality bottleneck

The 15-category framework is intended as a systematic structure for measurement across value-chain emissions. Source In practice, many Scope 3 categories require supplier-specific activity data and transparent calculation logic to become audit-ready, which increases evidence and traceability requirements across procurement and finance workflows. Source

CURRENTLY REQUIRED: category completeness and consistent categorization logic

The Scope 3 structure is defined as 15 categories, which means a compliant Scope 3 inventory is expected to be organized across those categories rather than an ad-hoc list of value-chain sources. Source The Scope 3 Calculation Guidance describes the 15 categories as a systematic framework, which implies consistent categorization decisions and repeatable measurement processes across reporting periods. Source

Table B — Scope 3: 15 categories + typical data owners (procurement/finance/ops)

Direction of travel: boundary clarity + systematic measurement discipline

The GHG Protocol Scope 3 Calculation Guidance frames the 15 categories as a systematic measurement framework for companies. Source In a compliance program, “systematic” typically means documented boundaries, consistent categorization decisions, controlled data sources, and repeatable calculation logic suitable for audit evidence. Source

What you can say with confidence vs what must stay labeled as “direction of travel”

You can state with confidence that Scope 3 is organized into 15 categories under the GHGP Scope 3 Standard (2011), because that structure is explicitly referenced as the canonical backbone in the IFRS S2 applying note. Source You can state with confidence that the categories are intended as a systematic framework, because the GHGP Scope 3 Calculation Guidance states that intent. Source You should label as “direction of travel” any expectations about tighter boundaries, higher supplier primary data usage, or standardized disclosure templates unless those expectations are explicitly stated in the provided sources. Source

How to Interpret "Systematic Framework" into Controls

If your Scope 3 approach is intended to be systematic, a practical implication is that you need a documented mapping of business processes to categories (e.g., procurement spend → Category 1) and the ability to reproduce that mapping consistently over time. Source If your Scope 3 approach is intended to be systematic, a practical implication is that you need traceability from reported totals back to the underlying activity datasets and factor assumptions used for each category. Source

Why Organizations Should Avoid Claiming Automatic Alignment with IFRS/ESRS

KPMG’s interpretive note cautions that any changes to the GHG Protocol will not be automatically incorporated into IFRS Sustainability Disclosure Standards or ESRS and that references would need to be revised. Source This means companies should treat “alignment” as a managed mapping exercise across frameworks rather than assuming automatic regulatory flow-through. Source

6) Compliance impact: what breaks in existing corporate workflows

Data architecture: what becomes harder if hourly matching/deliverability is adopted (proposed)

The GHG Protocol proposal described in the consultation announcement includes hourly matching and deliverability requirements for market-based reporting. Source If adopted, this would increase expectations for time-resolved electricity consumption and certificate attribute management (for example, aligning certificate attributes and consumption periods). Source The same announcement references practicality measures such as load profiles and exemption thresholds, which implies that implementation may differ by organizational size, data availability, or materiality thresholds as proposed. Source

What changes operationally for energy procurement teams (proposed)

If hourly matching is introduced for market-based reporting as described, energy procurement workflows may need tighter linkage between contract attributes and the time profile of consumption that the instruments are intended to cover. Source If deliverability is introduced for market-based reporting as described, procurement may need additional checks about whether instruments are considered deliverable to the consumption location under the proposal framing. Source The proposal’s inclusion of legacy clause and phased implementation suggests there may be a transition pathway for existing contracts if finalized. Source

What changes operationally for procurement and supply chain (Scope 3) owners (baseline)

The Scope 3 framework is explicitly structured into 15 categories, which implies procurement and supply chain teams often sit on key datasets for multiple categories such as purchased goods and services and upstream transportation. Source Because the Scope 3 Calculation Guidance frames the 15 categories as systematic, procurement workflows that rely on supplier data are more likely to be scrutinized for data completeness and reproducibility in assurance contexts. Source

Governance: who owns Scope 2 vs Scope 3 vs procurement vs finance vs assurance

Scope 2 dual reporting requirements depend on whether contractual instruments and supplier-specific data exist in the relevant markets. Source Scope 3 is structured into 15 categories intended as a systematic framework, which implies distributed ownership across procurement, finance, operations, HR, and product teams depending on category. Source

Practical Governance Model

  • Scope 2 owner: Energy procurement + sustainability data owners (due to contractual instruments and electricity attributes). Source
  • Scope 3 owner: Procurement + finance controls owners (because categories depend on spend/activity data and supplier evidence). Source
  • Assurance owner: Finance controllership / internal audit (because evidence requirements expand when claims become more granular). Source

7) Implementation Playbook

Readiness checklist (systems, contracts, supplier engagement, assurance)

Controls-and-evidence checklist (what auditors will ask for)

Minimum Viable Compliance vs Gold Standard

Minimum viable compliance focuses on meeting current dual reporting requirements and maintaining category completeness in the 15-category Scope 3 structure. Source A “gold standard” typically means improving internal evidence, traceability, and automation so proposed integrity requirements can be adopted with fewer manual workarounds if finalized. Source

12-week plan (readiness sprint) — what you can do without assuming final rules

12-month plan (controls build) — how to reduce assurance friction

The proposal describes a phased implementation timeline, which makes a 12-month controls build a reasonable governance concept for many organizations even before final publication, as long as it is described as preparation for a proposed direction. Source The Scope 3 guidance describes a systematic framework, which supports investing in repeatable data pipelines and documented category logic to reduce year-over-year rework. Source

8) Devil’s Advocate

Objections and Mitigations

  1. Objection: Hourly matching data is not available for all sites. When valid: where metering and supplier data do not support time-resolved allocation. Mitigation: rely on proposed practicality measures such as load profiles and phased implementation where applicable. Source
  2. Objection: Deliverability concepts may not align with current contract structures. When valid: when certificate procurement is decoupled from physical delivery constraints. Mitigation: assess procurement contracts and instrument attributes against proposed deliverability requirements to identify gaps early. Source
  3. Objection: Scope 3 category mapping creates double counting internally. When valid: when multiple teams report overlapping activity datasets. Mitigation: enforce the 15-category systematic framework and implement a single source of truth for category assignment. Source
  4. Objection: Suppliers (especially SMEs) cannot provide primary data. When valid: where suppliers lack measurement capability. Mitigation: focus first on material categories and supplier segments, using the systematic framework as a prioritization structure. Source
  5. Objection: Cross-framework mismatch (GHGP vs IFRS/ESRS) creates reporting friction. When valid: when internal teams assume automatic incorporation of GHGP updates into IFRS/ESRS. Mitigation: follow the caution that changes are not automatically incorporated and manage mapping explicitly. Source
  6. Objection: The cost of controls and evidence outweighs benefit. When valid: where reporting is assurance-scoped and data lineage is weak. Mitigation: treat targeted improvements and phased timelines as a planning input and invest in incremental controls aligned to the consultation timeline. Source

9) Outlook 2026–2030

The GHG Protocol announcement states that a second public consultation will follow in 2026 and final publication is expected in 2027. Source For organizations reporting under multiple regimes, any “alignment” claims should be controlled because changes will not be automatically incorporated into IFRS Sustainability Disclosure Standards or ESRS without revised references. Source Scope 3’s 15-category structure is expected to remain the stable backbone for categorization and disclosure mapping because it is referenced as the canonical structure derived from the GHGP Scope 3 Standard. Source

Data Visualizations

Chart 1 — Timeline: Scope 2 consultation and expected publication (2025–2027)

Chart 2 — Scope 2 reporting: dual methods (current baseline)

Chart 3 — Scope 3 backbone: 15-category structure (baseline)

Frequently Asked Questions

1) Are Scope 2 location-based and market-based reporting both required today?

The Scope 2 Guidance states that companies with operations in markets providing supplier-specific data via contractual instruments shall report Scope 2 in two ways. Source

2) What is the difference between location-based and market-based Scope 2 methods?

The Scope 2 Guidance defines the location-based method as reflecting average grid emissions intensity and the market-based method as reflecting contractual instrument-based attributes. Source

3) What consultation dates are confirmed for the Scope 2 update process?

The GHG Protocol announcement states consultation was announced Oct 20, 2025, initially through Dec 19, 2025, and later extended to Jan 31, 2026. Source

4) Does the proposal remove dual reporting?

The GHG Protocol announcement states the proposed revisions retain dual location-based and market-based reporting methods and propose targeted improvements. Source

5) Is hourly matching/deliverability already required?

The hourly matching and deliverability requirement is described as a central feature of the proposal for market-based reporting in the consultation announcement. Source

6) What practicality measures are described in the proposal?

The announcement describes load profiles, exemption thresholds, a legacy clause, and a phased implementation timeline as practicality measures. Source

7) How many Scope 3 categories are there under the GHG Protocol structure?

Scope 3 emissions are categorized into 15 categories as described in the GHGP Scope 3 Standard (2011). Source

8) Do GHGP updates automatically become part of IFRS S2 or ESRS requirements?

KPMG notes that changes to the GHG Protocol will not be automatically incorporated into IFRS Sustainability Disclosure Standards or ESRS and that references would need to be revised. Source

9) When is the updated Scope 2 standard expected to be published?

The GHG Protocol announcement states a second public consultation will follow in 2026 and final publication is expected in 2027. Source

10) What is the correct way to describe “alignment” with IFRS S2 or ESRS when GHGP changes are proposed?

KPMG cautions that any changes to the GHG Protocol will not be automatically incorporated into IFRS Sustainability Disclosure Standards or ESRS and that references would need to be revised. Source

Methodology note

All factual or quantitative statements in this article use only the provided Numbers & Sources Pack and are followed by a full visible URL citation. Source Proposed items are labeled as proposed/in consultation and are sourced from the GHG Protocol consultation announcement. Source Cross-framework incorporation is not assumed and is treated as contingent on revised references. Source

Scope 3 category (1–15) Typical primary data owners Notes for controls and evidence Evidence URL
1) Purchased goods and servicesProcurement + Finance (AP)Supplier data and bill-of-material logic often required for material items.Source
2) Capital goodsCapex owners + FinanceAsset registers and supplier emissions factors drive calculation traceability.Source
3) Fuel- and energy-related activities (not in Scopes 1–2)Energy procurement + FinanceBoundary clarity needed to avoid overlap with Scope 2.Source
4) Upstream transportation and distributionLogistics + ProcurementCarrier activity data and route assumptions require version control.Source
5) Waste generated in operationsOps + EHSWaste streams and treatment assumptions should be documented.Source
6) Business travelTravel team + FinanceBooking data quality and factor versioning influence auditability.Source
7) Employee commutingHR + FacilitiesSurvey methods and estimation controls matter.Source
8) Upstream leased assetsReal estate + FinanceLease boundaries and energy data access are typical constraints.Source
9) Downstream transportation and distributionSales ops + LogisticsShipment responsibility boundaries must be explicit.Source
10) Processing of sold productsProduct + CommercialProcess assumptions and customer-specific data drive variability.Source
11) Use of sold productsProduct + EngineeringUse-phase modeling requires documented assumptions and validation logic.Source
12) End-of-life treatment of sold productsProduct stewardship + EHSEnd-of-life pathways and geography assumptions are evidence points.Source
13) Downstream leased assetsReal estate + FinanceData sharing with lessees and control definitions are key.Source
14) FranchisesFranchise ops + LegalData collection controls and reporting boundaries drive assurance effort.Source