Energy billing
The report is a by-product.
SECR and ESOS ask for the same data you already validated bills against. Once the meters, the consumption and the invoices are in one place, the annual statement is a query rather than a project.
Statutory reporting
What the statement already contains.
Both schemes ask for things an energy team usually assembles by hand in the weeks before a deadline: consumption by commodity, a year-on-year comparison, an intensity ratio, a meter inventory, and an honest account of which readings were metered and which were estimated.
- Energy intensity66.28kWh per m²
- Carbon intensity10.781kgCO₂e per m²
- MethodologyIn the fileDESNZ factors, named
- The mandatory year-on-year comparison, computed rather than transcribed
- kWh/m² intensity, from floor areas held against the site
- Metered against estimated stated explicitly, because ESOS asks
- A methodology note in the file, so the number can be defended later
- Ten reports, over any scope and any period
- PDF, XLSX and CSV, with the assumptions written into the file
- Preview before you export, so nothing is a surprise
- Schedules and packs, so the monthly report sends itself
- Every figure traceable to the bill or the meter-day behind it
Ten reports, and what each one is for.
Schedules and packs
The monthly report nobody has to remember.
A schedule runs a report on its own and sends it. A pack groups several into one delivery, so a board paper or a client update arrives assembled rather than collected.
- Set the scope, the period and the recipients once
- Runs and sends on its own schedule
- Several reports in one pack, in a fixed order
- Group-scoped, so a client estate sees only its own sites
Why it is different here
A report is only as honest
as the data underneath it.
Most reporting tools present whatever they were handed. These read the same validated bills and the same coverage rules the validation engine uses, so a gap in the data appears as a gap rather than as a smaller number.
Tenant billing
The occupiers' share, from figures that were already checked.
Recharging energy cost to the tenants and occupiers of a site, from invoices that have already been validated.
Apportionment across tenants, sub-meter reads, and a recharge that carries the validated figure it was derived from rather than a share of a number nobody checked. The order matters: validate first, recharge second — which is the whole reason this sits on the same platform as the validation engine rather than beside it.
In build. It is described here because it is on the roadmap and named in the menu; nothing in this section is available today.
Questions
What people ask about the reports.
Where do the emissions factors come from?
UK Government (DESNZ) conversion factors, resolved per month against that month's own reporting-year set and falling back to the nearest earlier published set when a year is not published yet. Electricity uses the grid-average generation factor, natural gas the gross CV factor, and water the supply and treatment factors summed. The statement prints that note on its own first page, so the number can be defended without reconstructing how it was produced.
What period does the mandatory prior-year comparison use?
The same window, one year earlier, computed rather than transcribed from last year's filing. Consumption is pro-rated across each bill's service days that overlap the period, so a bill straddling the year end contributes only the days that fall inside it.
Last year's statement is the quickest thing to check this against.
We will rebuild it from your own data and show you where the two disagree, which is usually the most interesting half hour of the process.