Through the supplier
The supplier passes on data it already holds for billing and settlement.
The customer’s contractThe standards
Does it apply to you
Reporting under it
Start here
Dates and penalties
Doing it
What you must file
Doing it
Start here
Setting targets
Who and where
The UK duty
Doing it
The baseline
Europe
Reporting more widely
Carbon markets and trade
Packaging and net zero
Carbon accounting
Choosing
Carbon
Compliance and offsets
Software
Templates
Careers
Software · energy data, cited
Energy data software collects consumption from meters, smart meters, sub-meters and bills into one record that keeps each figure’s source, unit and period.
This page sets out who holds a business’s energy data, the routes and permissions to reach it, what half-hourly settlement changes from 2027, and the tests a pipeline should pass; it ranks no product.
What the software does
Energy data software is the pipeline that gets consumption from where it is measured into one store that every report can trust.
The dashboards on top are covered on energy monitoring software; this page is the layer beneath them.
The test of a pipeline is not how quickly it shows a chart but whether each figure can be traced to its meter or bill, its unit and its period.
SECR asks for energy in kWh covering all forms of energy, under Schedule 7, so the store must hold every source, not only electricity.
Supplier feeds, smart meters, own meters, bills.
Readings as received, half-hourly where available.
Gaps flagged, estimates labelled, units checked.
Source, unit, period and conversion basis kept.
kWh, then emissions on the activity-year factor.
Dashboards, ESOS, SECR, carbon reports, APIs.
Where the data lives
A business’s supplier holds its settlement data, the smart meter communications network is run by the DCC, and any sub-meters belong to the business itself.
The DCC was licensed in 2013 and, by its own account, does not have access to individual meter readings, which are encrypted in transit.
Government’s 2018 review said smart meters can store at least thirteen months of half-hourly consumption data.
NESO’s Carbon Intensity API publishes half-hourly grid intensity, which is useful for timing demand but is not the factor used in a report.
Energy data sources
Access and consent
A party that is not the supplier or network operator can become a DCC “Other User” under the Smart Energy Code and obtain consumption data only with the consumer’s consent, according to the code administrator’s guidance.
That consent must be Unambiguous Consent, and the Other User must tell the consumer the purpose and period of collection and the right to withdraw, under Section I.
The 2018 review says those controls apply to domestic, microbusiness and other non-domestic smart meters alike.
The code also has a separate Meter Data Retriever role for parties operating in the half-hourly settlement market, which is not the same as a business’s own access.
The supplier passes on data it already holds for billing and settlement.
The customer’s contractA registered Other User reads the smart meter with consent.
Smart Energy Code Section ISub-meters and loggers the business owns.
The business’s own dataHalf-hourly settlement
Market-wide half-hourly settlement moves every Great Britain electricity meter point to settlement in half-hour periods, with migration complete by 7 May 2027 under Ofgem’s P487 decision.
The cutover to a four-month settlement timetable, from 14 months, is 2 July 2027, according to the MHHS Programme.
Ofgem asked for a report at M14 on bringing the later milestones forward, so these dates may move.
MHHS changes how suppliers settle; it does not on its own deliver half-hourly data to a business, so a pipeline must still name its route for each meter.
From kWh to carbon
DESNZ publishes one set of conversion factors a year, for activity falling entirely or mostly within that year, so a pipeline must store the activity year with every reading.
The tool beside this shows the same electricity use against the 2025 and 2026 factor sets, which differ by about a quarter.
DESNZ’s methodology paper treats Gross CV as the default basis for fuels, so a gas reading converted to kWh should state its basis.
Live grid intensity belongs in a separate field from the reporting factor, so the two are never confused.
Same kWh, two factor sets
A company that changed nothing sees 26.0% less on this line because the factor moved.
DESNZ attributes most of the fall to grid decarbonisation and 6 to 7 percentage points to methodology.
Factors: DESNZ 2026 methodology paper, Table 9 · 2026 major changes report.
Generated electricity is Scope 2; transmission and distribution losses are Scope 3.
With losses selected, the illustration uses the printed consumed total in DESNZ Table 9, spanning both scopes. It is not your SECR figure; nothing is stored or sent.
Open energy data
Ofgem’s Data Best Practice Guidance obliges the licensees it covers to treat their data assets as Presumed Open, made available for all to use unless they evidence a reason to withhold it.
The reasons are limited to privacy, security, legal or regulatory obligations and commercial sensitivity, assessed in an Open Data Triage.
The rule binds licensees such as network operators, not an energy-using business, so a company’s own meter data stays its own.
For a pipeline, open network and grid data is a useful context layer beside the business’s private consumption data.
Presumed Open
Presumed Open
Presumed Open
Platforms, in their own words
This site’s vendor registry is built around carbon and ESG platforms, and one of them describes meter-level data in its own words, as an input to its emissions tracking.
Specialist energy data providers and metering companies are not in the registry, which says nothing about them.
The full registry, with each vendor’s own claims on ESOS and SECR, is on carbon reporting software.
| Platform | What its own site says |
|---|---|
| Measurabl | Enable Scope 1, 2, and 3 emissions tracking derived from meter to space assignments for accurate, decision-ready reporting. |
Data quality
ESOS reference period
12 monthsRegulation 22ESOS units
kWh or £Environment Agency guidanceSECR scope
All forms of energySchedule 7Settlement timetable
4 monthsFrom 2 July 2027ESOS totals energy over a 12-month reference period under regulation 22, and the Environment Agency’s guidance accepts kWh or pounds, so the same readings must total to different periods without re-keying.
The GHG Protocol’s completeness principle is why a missing month must stay visibly missing rather than silently become zero.
An energy management system under ISO 50001 builds its baselines on the same data, so errors here travel into every indicator.
Settlement data is revised as the timetable runs, from 14 months today to four months after 2 July 2027; a pipeline should keep each revision with its date rather than overwrite the figure already reported.
The tests before you sign
Each question beside this names the rule or source it comes from and what a passing answer looks like.
Run them on your own meters, because a demonstration never has a broken feed, a cubic-metre gas bill or a site where you are not the customer of record.
Nothing on this page is a rating, ranking or recommendation of any product.
Energy data demo questions · tick the ones you need
The pass tests are our reading of the cited provisions.
Nothing you tick is stored or sent.
Every figure in an energy report is only as good as the reading behind it, so keep the source, the unit, the period and the gaps.
Takeaways
| The fact | What to do |
|---|---|
| Every GB meter point moves to half-hourly settlement by May 2027 | Ask each data provider which route it uses for each meter |
| Smart meter data through the DCC needs consent | Keep a dated consent record per meter, with a withdrawal route |
| Reporting factors are set per activity year | Store the activity year and keep live intensity separate |
| ESOS and SECR total different periods from the same data | Hold readings by period, with gaps shown, not zeroed |
Start with the routes to your data, then take the demo questions to vendors.
Frequently asked
Software that collects energy consumption data from meters, smart meters, sub-meters and bills, checks it and stores it with its source, unit and period, so monitoring, ESOS, SECR and carbon reporting all draw on the same record. It is the data pipeline beneath energy monitoring dashboards.
From its energy supplier, or through a party registered as a DCC “Other User” under the Smart Energy Code, which may obtain consumption data only with the consumer’s Unambiguous Consent.
Government guidance says those controls apply to domestic, microbusiness and other non-domestic smart meters alike.
No. A non-licensed party reaching smart meter data through the DCC needs the consumer’s Unambiguous Consent, and must tell the consumer the purpose and period of collection and their right to withdraw.
The DCC itself does not have access to individual meter readings.
The move of every Great Britain electricity meter point to settlement in half-hour periods.
Suppliers must qualify by 28 October 2026 and migrate all meter points by 7 May 2027, and the market cuts over from a 14-month to a four-month settlement timetable on 2 July 2027, according to Ofgem and the MHHS Programme.
Not by itself.
MHHS changes how suppliers settle; whether a business sees half-hourly data depends on its meter and how its supplier or data provider passes the data on.
Ask any data provider which route it uses.
Some of it.
Ofgem’s Data Best Practice Guidance obliges the licensees it covers to treat their data as Presumed Open, subject to an Open Data Triage for privacy, security, legal and commercial sensitivities.
A business’s own consumption data is not made public by that rule.
Not for SECR or location-based figures in the ordinary way.
NESO publishes half-hourly Great Britain grid intensity by API, which is useful for operational decisions, but reported emissions use the DESNZ conversion factor for the year in which the energy was used.
The source (meter, bill or estimate), the unit and conversion basis, the period it covers, and any estimate flag with its method.
A gap must stay a gap, not become a zero, because ESOS and SECR totals depend on complete periods.
They overlap.
Monitoring software is the dashboard and analysis layer; energy data software is the collection and storage layer underneath it.
Many products do both, but the data layer is what an auditor or ESOS assessor will test.
Often not.
A business with a few sites can download data from its supplier and keep monthly totals in a spreadsheet.
Software earns its place with many meters, half-hourly data, sub-metering or several reporting duties drawing on the same numbers.
No. The page is built from Ofgem, Elexon, Smart Energy Code and government sources cited, and quotes vendors only in their own words.
Sources
Every rule and date on this page traces to the regulator, code or guidance listed here.
Suppliers qualified by 28 October 2026; all meter points migrated by 7 May 2027.
M16, 2 July 2027: from the 14-month to the four-month settlement timetable.
Migration began 22 October 2025.
Other Users obtain consumption data only with the consumer’s consent.
Appropriate Permission and Unambiguous Consent.
Controls apply to domestic, microbusiness and other non-domestic meters.
Licensed in 2013; does not have access to individual meter readings.
Licensees treat their data as Presumed Open, subject to Open Data Triage.
The rules around data in energy licences.
Half-hourly GB grid intensity: operational, not the reporting factor.
One factor set a year.
The activity-year rule; Gross CV as the default basis.
Energy in kWh and “all forms of energy”.
Total energy consumption over a 12-month reference period.
Total energy consumption in kWh or in pounds.
Energy performance indicators and baselines.
Completeness and transparency: a gap is not a zero.