Reporting and compliance
The report is a by-product.
SECR and ESOS are 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.
- 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
The library
Ten reports, and what each one is for.
Named by the question they answer rather than by the table they read. Every one of them is built today.
Billing and validation
Validation summary
Validation outcomes, bills needing review, identified overcharge, and the root-cause split.
Authorisation register
Bills ready for approval with supplier, period, amount, verdict and finance status.
Primary cause analysis
Flagged bills counted once, under the check group that actually caused the issue.
Query status register
Open, awaiting-supplier, resolved and closed query counts for operational review.
Cost and consumption
Recovery and disputes
Recovered value over time, open disputes, status mix and recovery rate.
Usage tracker
Consumption movement by group, site or meter over a selected period.
Carbon and compliance
SECR annual statement
Energy in kWh and emissions in tCO₂e by commodity, the mandatory year-on-year comparison, the kWh/m² intensity ratio, and a methodology note.
ESOS evidence pack
Twelve months of energy per MPAN and MPRN with significant consumers first, the meter inventory, and consumption-source quality: half-hourly metered against estimated.
Carbon report
CO₂e by commodity with the monthly trend, from consumption against standard UK GHG factors.
Data quality
Data completeness
Every meter-day short of the half-hours it owed, with expected, received and missing counts, ready to send to the supplier as a data request.
Statutory reporting
SECR and ESOS, from the data you already hold.
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.
- 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
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 sees only their own estate
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.
Bring last year's SECR statement
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.