enargo — rebuild the invoice, prove the difference
enargo
[ clip 4 render pending — resting frame in use ]
UK non-domestic energy · invoice validation

Rebuild the invoice. Prove the difference.

enargo reconstructs every charge on a UK non-domestic energy invoice from published and contracted rates, compares the reconstruction with what the supplier billed, and assembles an evidenced claim for each difference it can prove.

01 — The problem

The bill is arithmetic on somebody else's reference data.

Every charge is calculated from a published rate, a contract version and a classification held on an industry system. Any of them can be wrong, and the error compounds quietly across every site, for years.

LLFC mismatch MIC band TDR band gas AQ meter multiplier
02 — The engine

One computation. Two date ranges.

Backwards

A historical audit across up to six years of invoices. What was overcharged becomes a claim.

Forwards

Every new invoice validated before it is paid, so an error never compounds again.

03 — Evidence

A claim a supplier cannot wave away.

→ deterministic recalculation — same inputs, same figure, in any year → decimal arithmetic, never floating point → settlement-correct time: 46/50-period days, gas day from 05:00 → every figure traceable to the charging statement or contract version
the country the estate the yard the meter
scroll — the camera descends
What the meter's invoice looks like, rebuilt
Invoice reconstruction · worked example
HH electricity · 1 site · 1 billing period · 15 components modelled
Charge component Billed Reconstructed Variance
Distribution (DUoS) unit ratesLLFC mismatch — line loss factor class £18,204.11 £16,932.40 +£1,271.71
Capacity charge (kVA)MIC band — charged above agreed capacity £3,960.00 £2,772.00 +£1,188.00
Metered consumptionMeter multiplier applied twice £9,412.00 £941.20 +£8,470.80
Transmission (TNUoS)Superseded tariff version £5,880.42 £5,468.36 +£412.06
Climate Change LevyReconstruction agrees with the bill £2,145.60 £2,145.60 £0.00
Proven variance, this period £39,602.13 £28,259.56 £11,342.57

Worked example, synthesised from the charge-component catalogue. Not a client invoice.

£0.0m
recovered for clients to date
0
meter points under continuous validation
0
regulated charge components reconstructed
0
of billing history audited on day one

Placeholder figures — send the real numbers and they go straight in.
04 — The portal

Findings, claims and coverage in one place.

Your team sees what was found, what it is worth, what evidence sits behind it and what is still waiting on data.

Findings 42 open · £186,402 in review · 8 awaiting LOA ⌘K
FindingSiteComponentVarianceStatus
F-1042Bolsover DCDUoS · LLFC£1,271.71Proven
F-1041Wakefield 2Capacity · MIC£1,188.00Proven
F-1038Leeds CentralConsumption · multiplier£8,470.80In review
F-1035Hull DepotCCL · exemption£412.06Cleared
05 — Engagement

Start with the audit. Stay for the validation.

The audit

A fixed engagement across your billing history. You see the findings and the evidence before anything is claimed.

The subscription

A SaaS fee per meter point per year. Every invoice validated before payment, for as long as you hold the estate.

For consultants and TPIs

Run validation for your own clients on the platform, under your own brand, with tenancy separated in the database.

06 — Proof placeholders — awaiting your material
client logos
Case study 01 · named client
£000k

Sector, site count, what was wrong, what was recovered and how long it took. One paragraph, in your words.

Case study 02 · named client
£000k

Sector, site count, what was wrong, what was recovered and how long it took. One paragraph, in your words.

Team · track record
00 yrs

Where the team has done this before, and at what scale. Credentials that make the engine believable.

[ clip 5 pending — spectrum-thread pull-back loop replaces this still ]

Send us one invoice and one contract.

We reconstruct it and show you the reconstruction beside the bill. If there is nothing in it, you will know inside a week.

Book an audit call→ hello@enargo.co.uk · placeholder address
How it works

From a mailbox of PDFs to a claim with evidence attached.

Six steps. The first four are ours to do; the last two are where you decide what happens. Nothing is claimed on your behalf until you have seen the evidence behind it.

01

Invoices arrive

Forward the billing mailbox, or drop a folder in. PDFs are read charge by charge, CSV and industry data files are parsed, and consolidated invoices are decomposed back to the meter point they belong to.

→ email forwarding→ supplier PDF extraction→ CSV and flat-file feeds→ consolidated bill decomposition
02

Your estate is established

Meter points, sites, contracts and letters of authority, each held with the dates it applied from. Contracts are versioned, so a rate change mid-period is a fact the engine knows rather than an assumption it makes.

→ MPAN / MPRN validation→ site and portfolio structure→ contract versions with effective dates→ LOA status per supplier
03

The invoice is rebuilt

Every regulated charge is recalculated from the published charging statement that was in force, every contracted charge from the contract version that applied, at half-hourly resolution where the data supports it.

→ 15 charge components, electricity first→ half-hourly and non-half-hourly→ decimal arithmetic throughout→ 46 / 50-period clock-change days
04

Differences are explained

A variance on its own is not a finding. Detectors attribute each difference to a cause — a classification, a band, a multiplier, a stale rate — and triage tells you which are worth pursuing and which are noise.

→ structural detectors: LLFC, MIC, TDR, AQ, multiplier→ cause, not just delta→ triage by expected value→ false positives closed with a reason
05

A claim is assembled

Each finding becomes a claim with an evidence pack: the reconstruction, the rate and version it used, the source document, the affected periods and the figure. You approve it before it goes anywhere.

→ reconstruction, line by line→ rate provenance and version→ affected periods and sites→ your approval, before submission
06

Then it keeps running

The audit ends; the engine does not. The same calculation runs on each new invoice before you pay it, so the error you recovered this year cannot quietly return next year.

→ validation before payment→ recurrence watch on closed findings→ coverage: what is not yet validated, and why→ per meter point, per year

One invoice and one contract is enough to start.