ESG & Reporting 6 min read · May 2026

Features to Demand in Utility Data Services for Scope 2 Emissions

Scope 2 emissions — the indirect greenhouse gas emissions from purchased electricity, steam, heat, and cooling — are the most directly traceable of the three scopes. They trace directly to utility invoices. Yet most organizations still calculate Scope 2 from incomplete, unvalidated, or manually assembled billing data. As Scope 2 reporting requirements evolve under SEC climate rules, CSRD, and investor frameworks, the quality of your utility data service becomes a strategic compliance issue.

Location-Based vs. Market-Based: What Your Data System Must Support

The GHG Protocol requires Scope 2 to be reported using both location-based and market-based methods where market-based instruments exist. Location-based reporting uses grid emission factors for each facility's region. Market-based reporting uses contractual instruments — renewable energy certificates (RECs), power purchase agreements (PPAs), and supplier-specific emission rates. Your utility data service must support both methodologies simultaneously and maintain the supporting documentation for each.

6 Features Your Utility Data Service Must Have for Scope 2

Complete invoice capture across all electricity accounts

Scope 2 calculations are only as complete as your invoice collection. A utility data service that misses accounts — due to provider gaps, data format issues, or manual collection failures — produces systematically understated Scope 2 figures.

Meter-level consumption with interval data

Monthly billing data gives you Scope 2 totals. Interval data gives you the granularity to apply time-of-use emission factors, identify demand reduction opportunities, and support 24/7 clean energy matching claims.

Automatic emission factor application and updates

eGRID regional emission factors update annually. Your data service should apply current factors automatically and flag when updated factors change prior-period figures materially.

REC and PPA tracking

Market-based Scope 2 calculations require documented tracking of renewable energy certificates — including generation source, vintage, and geography. Your service must maintain this documentation in audit-ready form.

Multi-site normalization

For organizations reporting across multiple sites in different grid regions, the system must apply the correct regional emission factors to each facility's consumption automatically — not rely on a single national average.

Audit trail and data lineage

Every consumption record should trace back to its source invoice, with timestamps, validation status, and any manual adjustments documented. Auditors reviewing Scope 2 disclosures will request this documentation.

Questions to Ask Any Utility Data Vendor

How do you handle gaps in invoice history?

Estimation methodologies matter. Understand what assumptions are applied when invoices are missing and how gaps are flagged in reporting outputs.

How often are emission factors updated and versioned?

A system using 2022 eGRID factors in 2026 is producing materially incorrect Scope 2 figures.

Can you support both location-based and market-based reporting simultaneously?

Many systems support one or the other. Regulatory compliance increasingly requires both.

What documentation does the system produce for third-party assurance?

ESG disclosures are increasingly subject to third-party assurance. Your utility data service should produce the supporting documentation that assurance providers need.