Electricity Bill Validation
The bill arrives and gets paid. Nobody checks whether it is correct, because checking it means knowing in advance how it should have been calculated. We already do.
Upload
Drop the bill in, the rest is automatic
A PDF or an e-invoice XML is dropped onto the panel; the lines are parsed automatically and compared with the expected bill. No manual entry, no spreadsheet to fill.
- PDF and e-invoice XML supported
- Lines matched against tariff names
- The result appears on the same screen, in seconds
Bill Upload
drag and drop- Energy charge half-hourly price × consumption£41,698.86 ✓ Matched
- Network (DUoS) published tariff£6,204.31 ✓ Matched
- Excess capacity not due under agreed capacity£2,317.40 +£2,317.40 diff
- Climate Change Levy correct base£3,201.66 ✓ Matched
Overpayment found £2,317.40
Line by line
The expected bill is built first, then compared with the one that arrives
Half-hourly consumption × the price for that period, network charges, capacity, reactive and levies. Each line is calculated separately; when the PDF is uploaded, the difference is written per line.
- Time-weighted price and levies automatically
- Wrong tariff and capacity charge detection
- A one-page dispute record for the supplier call
The expected bill is built automatically every month from the site’s tariff and contract terms; period prices and levies are taken from published data. The uploaded PDF is split into lines; if the difference on a line is above zero the row is coloured and the total counts up below.
Bill Validation
August · line by line| Line | Expected £ | Billed £ | Difference £ |
|---|---|---|---|
| Energy (time-weighted) | 41,890 | 41,890 | 0 |
| DUoS / TNUoS | 8,702 | 12,199 | 3,497 |
| Capacity (agreed) | 1,560 | 1,560 | 0 |
| Excess capacity | 0 | 1,145 | 1,145 |
| Reactive | 0 | 0 | 0 |
| Overcharge found | 4,642 |
Deviation
Missing a deviation is worse than raising a false one
Each month the gap between expected and billed is kept as a percentage. Months over the threshold are flagged; small but recurring differences show up cumulatively.
- Threshold ±2% by default, set per site
- Recurring small-deviation warning
- A full record for year-end reconciliation
The threshold is ±2% by default; a fixed amount in pounds can be set for a small site. If a deviation repeats on the same line three months running, the system folds it into a single warning; the period, line and amount for the supplier letter come ready.
From Expected to Billed
August · line differences- 52,152£ Expected
- +3,497£ DUoS / TNUoS
- +1,145£ Excess capacity
- +0£ Reactive
- 56,794£ Billed
Price
Most of the bill is not the energy
On a half-hourly contract the price changes through the day; the same kWh costs more in the evening peak. The time-weighted price is calculated with your own profile and compared with the tariff.
- Half-hourly price and consumption overlaid
- Weighted price on your own profile
- Load-shifting opportunity, in pounds
The card overlays half-hourly consumption on that period’s price; the weighted price is calculated with your own profile. A load-shifting trial runs on the same screen: if part of the selected hours moved to the night, how much the bill would change is written in pounds.
- Daily price report by e-mail every morning
- Monthly market report with next month’s levy outlook
- Contract terms held in the system
Consumption and Price
yesterday · half-hourlyPrices from the published half-hourly series; consumption from the main meter.
What is compared against what
Validation plate
- Consumption
- kWh
- Half-hourly meter data · via letter of authority
- Energy charge
- £
- Consumption-weighted price × contract terms
- Network charges
- £
- Published distribution and transmission tariffs
- Levies
- £
- Capacity Market, CfD and related pass-through
- Capacity
- £
- Agreed capacity vs measured maximum demand
- Reactive power
- £
- Power factor against the charging threshold
- Taxes
- £
- CCL and VAT · on the correct taxable base
Every validation runs against the values published for the period being checked, not against today’s.
One thing worth being direct about: the platform’s tariff library was built for the Turkish market, where it is maintained continuously. For Great Britain the network tariffs, levy rates and CCL bands are loaded as part of onboarding, the method below is the same, but the reference data for your region is set up before the first validation runs, not assumed to be there.
Common questions
Our finance team already checks the invoices. What would change?
Finance checks that a bill is consistent: do the lines add up, is the VAT right, when is it due. What they cannot check is whether the lines are correct, that needs the consumption data, the published prices and the contract terms in front of you at the same time. We are already looking at all three.
How do you read our bill?
PDFs in a configured format are read directly. Where the format is not recognised you enter the lines yourself and validation runs identically. Identifying details, supply number, meter, period, are taken from the bill itself, which stops the wrong bill being validated against the wrong site.
What happens when you find a deviation?
An alarm record opens and an email goes out saying which line deviated and by how much. The next step is yours: query it with the supplier or ask for an explanation. We show the deviation; we do not raise the dispute on your behalf.
Can you check bills retrospectively?
If the meter data goes back that far, yes. Without the data there is no validation, we do not produce a calculation that has no source.
Will it generate false alarms?
Thresholds are adjustable per site; by default 0.1% and £250 must both be exceeded before anything is raised. Our bias is nonetheless clear: we would rather report a suspicious line than stay quiet about one. A missed deviation costs more than an extra notification.
Let us measure what is happening on your site.
In a one-hour call we look at your existing setup and set out exactly which measurement points are needed and what you would be able to see.