Utility data for Scope 2 reporting without a second data project
The same bill data that drives an audit also feeds Scope 2 emissions inventories. How to capture it once and use it for both.
Karthik Iyer, VP, Engineering · March 2, 2026 · 6 min read
Key takeaways
- Scope 2 inventories need kWh by site and period; the utility bill is the primary source document for it.
- The GHG Protocol asks for both a location-based and a market-based figure, so contract and supplier data must be captured with the usage.
- Capturing bills once into a normalized dataset serves AP, audit and sustainability reporting at the same time.
Two teams, one set of bills
In many companies the sustainability team and the finance team ask for the same utility data on different calendars. Finance wants charges by account and period for accruals. Sustainability wants kilowatt-hours by site and period for the annual inventory. Each team builds its own collection process, often by email requests to facilities or by manual download from utility portals.
The two processes work from the same bills. The duplication is not a data problem, it is an organizational one, and it creates two versions of usage that never quite reconcile.
What a Scope 2 inventory needs
The GHG Protocol Scope 2 Guidance sets out two methods that companies report side by side. The location-based method multiplies electricity use by the average emissions factor of the grid where it was consumed. The market-based method reflects the electricity the company has chosen to buy, using supplier-specific factors, contractual instruments such as renewable energy certificates, or a residual mix where nothing specific applies.
In both cases the starting point is the same: metered kWh by facility and period, mapped to a grid region. The market-based method adds the retail supplier or product, any renewable purchase, and the instruments retired against the usage. Those details appear on bills and supply contracts and should be captured with the usage.
Capture once, normalize once
A bill-capture pipeline that extracts account, meter, service address, period, kWh, kW and charges for the audit already holds the Scope 2 inputs. The additional step is normalization: aligning the billing period to the reporting calendar, handling estimated reads, and flagging gaps and corrections.
Corrections matter here. A rebilled period or a credit that changes the kWh needs to flow through to the inventory, or the reported figure and the actual figure drift apart. An audit-grade dataset, where every revised bill replaces the prior one, is exactly what an emissions inventory needs.
Getting to the reporting tools
Many organizations use ENERGY STAR Portfolio Manager for building-level tracking, and Green Button data standards are supported by a number of utilities for customer data access. A normalized dataset can be exported to either. The aim is to feed the tools sustainability already uses rather than to introduce a new one.
Emission factors themselves come from outside the bill: published grid factors such as the U.S. EPA's eGRID for location-based figures, and supplier-specific factors where available. Keep the factor source and year recorded next to each calculation so the number can be reproduced.
Where the data quality risk sits
The common gaps are closed and vacant sites with residual usage, sub-metered tenant spaces, accounts paid by landlords, and estimated reads that were never trued up. These are also the accounts where audit findings concentrate, so fixing them improves both outcomes.
A useful discipline is a quarterly reconciliation of kWh by site against the prior year. Large swings usually point to a data gap, a meter change or a billing error rather than a real change in consumption, and they deserve a look before the annual inventory is locked.