Ofgem Compliance Statement

Effective Date: 17/08/2026 | Version: 1.0 | Next Review: 17/08/2027

What PowerView checks, how it checks it, and the limits of what our findings mean.

1. Licence conditions we screen against

PowerView identifies potential exceptions requiring supplier review. It does not establish regulatory breaches and is not Ofgem-approved.

SLC 21BA — 12-month backbilling limit. Accounts still being charged with no actual meter reading in the preceding 12 months (or no actual reading at all).
SLC 21B — Billing based on meter readings. A bill based on an estimated reading issued after a valid actual reading on the same account. An estimated bill after an actual reading needs more context before it becomes a breach — we flag it for triage only.
Priority Services Register (vulnerable customers). Gap analysis between supplier-held vulnerability flags and DNO PSR records. Informational only; no licence determination is made.

Scope: domestic customers, and microbusiness customers where the supplier applies the same backbilling protection. Non-microbusiness I&C accounts are out of scope. Tested on sample data only, not yet tested against real billing records.

2. Methodology

Shadow billing versus actual

We rebuild an independent "shadow" view of each account from the raw meter reading history you supply and compare it against what was billed. Divergences are raised as exceptions with the reading dates, reading types and consumption values that produced them.

Exposure estimation

Exposure is calculated from the account's own unit rate and standing charge where present, otherwise from the prevailing Ofgem price cap, plus 5% domestic VAT. Every figure is an estimate and is labelled as such in the report.

Chain hash verification

Every action is written to an append-only audit log. Each entry stores the SHA-256 hash of the previous entry, forming a hash chain from a GENESIS record. Database triggers block all updates and deletions, including by privileged roles. Reports state how many records were verified and whether the chain is intact.

QR audit and report sealing

Each PDF is hashed on generation and carries a QR code linking to a public verification page. Re-hashing the file and comparing it with the stored hash proves the document has not been altered since sealing. Every report also passes an automated verification gate before it is released — reports that fail are blocked for human review, on all plans.

3. Disclaimer — PowerView is not Ofgem

PowerView UK (Annalu Pomarico, sole trader) is an independent software provider. We are not Ofgem, not a regulator, and not an accredited auditor. Our findings are not regulatory determinations, do not constitute Ofgem approval, and do not certify compliance. We help licensed suppliers evidence and meet Ofgem standards; the licence obligations, and any consequence of breaching them, remain with the supplier.