Independent energy bill validation
Every invoice, rebuilt from first principles.
We do not sample your bills or eyeball the totals. We rebuild each one from your contract, your meter data and the charges the industry actually published for that period, then compare it line by line and tell you what does not agree.
Invoice 4471-08
1 to 30 June 2026 · Half-hourly · 1 site
- Energy, dayInvoiced £1,284.60Expected £1,284.60
- Standing chargeInvoiced £93.00Expected £93.00
- DUoS, red bandInvoiced £417.82Expected £361.19
- Climate Change LevyInvoiced £142.05Expected £142.05
| Line | Invoiced | Expected |
|---|---|---|
| Energy, dayAgrees with the expected amount | £1,284.60 | £1,284.60 |
| Standing chargeAgrees with the expected amount | £93.00 | £93.00 |
| DUoS, red bandDoes not agree | £417.82 | £361.19 |
| Climate Change LevyAgrees with the expected amount | £142.05 | £142.05 |
Potential overcharge identified
£56.63
Published rate does not match the invoiced red-band rate.
Source verified · Published DUoS tariff · 2026/27The problem
A total that looks right is not the same as a bill that is right.
Most checking stops at the headline number, or at the unit rate. The charges that move without anyone noticing sit underneath: network bands, levies that reconcile a year later, a loss factor applied to the wrong meter class, a period that quietly overlaps the last one.
Rebuilt, not sampled
An expected bill is calculated for every invoice from the contract in force on each day of the period. Every invoice is checked, not one in ten.
Line by line, with a reason
Six grouped checks (identity, period, consumption, rates, arithmetic and credits) run in the order they cause each other, so a failure names its root cause instead of leaving you with a difference.
Nothing overwritten
Every run is kept. Re-validating a bill writes a new record beside the old one, so what was known, and when, is always answerable.
Non-commodity charges
The part of the bill nobody rebuilds.
Commodity is the easy half. The rest is published by the networks, the ESO and government, changes every charging year, and is where a spot check runs out of road. We model it from the source data.
- Distribution charges for all 14 GB networks, on the published tariff for the date
- Half-hourly charges applied per settlement period, not averaged across the month
- Levies that reconcile later handled as they actually settle: interim first, then the true-up
- Line losses grossed up from the industry loss factors for that meter and season
- Source figures stored and shown exactly as published, with only the final pence rounded
Charges modelled today
DUoS
Distribution Use of System
TNUoS
Transmission Network Use of System
BSUoS
Balancing Services Use of System
CfD
Contracts for Difference
CM
Capacity Market
AAHEDC
Assistance for Areas with High Electricity Distribution Costs
Nuclear RAB
Nuclear Regulated Asset Base levy
CCL
Climate Change Levy
Imbalance
Elexon cash-out
RCRC
Residual Cashflow Reallocation Cashflow
LLF
Line Loss Factors
How it works
Four steps, and you only do the first one.
- 1
Bring your bills and contracts
Upload an invoice or forward it in. Contracts are recorded once, with their rates and the dates each rate applies from.
- 2
We rebuild the bill
Consumption, contract rates and every published industry charge for those exact dates are assembled into an expected bill.
- 3
Line by line comparison
The two are compared under your own tolerance and check policy, and each difference is attributed to a cause.
- 4
Query, or approve and pay
Raise a query with the supplier and track it to resolution, or approve the bill and send it to your accounts-payable export.
Beyond the check
What happens after a bill fails.
A finding is only useful if it turns into money back. The workflow around validation is part of the product, not an add-on.
Queries that go somewhere
Raise a query straight from the failing line, with the evidence attached. Track it by age and status until the supplier credits it.
Market analysis
Compare what the market is offering against what you are paying, so a renewal conversation starts from your own numbers.
Controls that survive an audit
Roles you define, access scoped by site group, and an append-only trail of who changed what.
14 of 14
GB distribution networks modelled
48
Settlement periods checked per day, not one monthly average
11
Non-commodity charge types rebuilt from published data
See it against your own bills
A short call, then we validate a real invoice of yours and walk through what the engine found, line by line.