Browser-side evidence tool hashing and ROC maths run on your device verifiable SHA-256 + QR
For independent UK energy suppliersBuilt for independent UK energy suppliers without large in-house compliance teams
Find billing compliance gaps in your own data — before Ofgem does.
PowerView UK screens your billing extract for Ofgem SLC 21B and SLC 21BA issues and produces a tamper-proof Exception Report your auditor can re-verify independently.
Upload one CSV. It is parsed in your browser — nothing is stored or sent. You get evidence-qualified review flags, an indicative £ estimate where the evidence supports it, and a SHA-256 + QR verification page.
Running now — in your browser, no upload
Instant exception check on a synthetic estate
No sign-up. CSV stays in your browser. Running a supplier? See the Founding Supplier pilot →
Other tools automate the workflow. We produce the evidence — with a published methodology and a cryptographic audit trail your Ofgem auditor can re-verify independently of us.
SLC 21B review · SLC 21BA evidence · PSR gaps · REGO · FMD
No upload to server
The evidence tool reads your CSV in the browser. The file itself is never transmitted.
SHA-256 local hash
crypto.subtle.digest runs on your machine. Only the resulting hash is recorded.
QR verifiable offline
Every pack carries a hash + QR an auditor can re-check independently.
Proof
Evidence you can hand to a regulator.
Upload one CSV. Get one verified Exception Report. Free.
1 CSV → Exception Report → indicative estimate where evidenced → SHA-256 verification
PowerView UK is an independent tool. No affiliation, endorsement or partnership with any supplier or with Ofgem.
Included, free
- 1 Exception Report (PDF)
- Hash-chain verification page
- Evidence-qualified estimate summary
Not included
- Workspace / dashboard access
- Repeat or scheduled checks
- Audit-ready evidence pack export
After the report
- Choose Starter or Compliance
- Continuous monitoring & alerts
- Full estate, not a sample
Sample data — illustrative entries, real output format
- #0042026-08-18T08:41:02Z
evidence_snapshot.created
prev41b8e0c9aa72…sha2569f3c1ab27de0… - #0032026-08-17T16:12:55Z
exception_report.exported
prev0c77d5f31be4…sha25641b8e0c9aa72… - #0022026-08-17T09:04:31Z
rego.chain_of_custody.linked
prevd2a6913f8c05…sha2560c77d5f31be4… - #0012026-08-16T07:58:10Z
billing_records.imported
prev000000000000…sha256d2a6913f8c05…
Want to see the engine run right now? Use the instant check at the top of the page — synthetic estate, ~30 seconds, nothing uploaded.
The assisted free check is the one place a file is sent to us, and only with your explicit authorisation. Prefer to keep everything local? Use the browser-only evidence tool.
How it works
From scattered REGOs to an audit-ready evidence pack
- 01
Import
Drop in one CSV of your billing extract — MPAN, readings, dates. It is parsed in your browser; nothing is uploaded.
- 02
Detect
PowerView creates SLC 21B review flags (365+ days without an actual reading, or an estimate issued after a valid reading) and, only where bill-level evidence is supplied, quantifies SLC 21BA aged under-billing with an indicative estimate.
- 03
Evidence
Every finding is hashed SHA-256 with a UTC timestamp and a QR link — an auditor can re-check it independently, months later.
- 04
Audit Pack
One click produces an evidence bundle formatted for Ofgem fuel mix disclosure, plus the full hash-chained audit trail.
Formatted for Ofgem fuel mix disclosure. Detection and triage tooling — it flags SLC 21BA / SLC 21B exceptions for your team to review, it does not replace regulatory judgement. PowerView UK is not affiliated with Ofgem. You remain responsible for submission.
Why PowerView
Three capabilities built specifically for independent UK energy suppliers
Your billing platform is built to bill. PowerView is built to prove — months later — that the evidence behind a submission was never altered, with ECO4, WHD and FiT tracked against the same customer records.
PowerView sits above the CIS, not inside it — no migration, no vendor lock-in.
Comparisons are based on publicly available information. Product and vendor names are used for identification only — no affiliation or endorsement is implied. PowerView UK is not affiliated with Ofgem.
Works with whatever billing system you already run
If your billing system doesn't include a compliance evidence layer, PowerView sits above the CIS, not inside it — no migration, no vendor lock-in.
- CSV in — no migration, no vendor lock-in
- Same engine for in-house, legacy or spreadsheet-based estates
- Switch billing platform without losing your audit history
Hash-chained evidence an auditor can re-check
Every record is SHA-256 hash-chained and daily-anchored, so an auditor can verify nothing was edited after the fact. The approach is established in UK landlord compliance (llcr.uk); we have not found it offered in energy.
History is append-only — nobody, including us, can edit or delete it
ECO4, WHD and FiT tied to customer data
Today that means spreadsheets plus separate Ofgem portals. PowerView tracks all three schemes against your beneficiaries and statutory deadlines.
- ECO4, WHD and FiT deadlines in a single tracker
- Beneficiaries linked to account ref, MPAN/MPRN and PSR flags
- Delivery status and evidence exportable per scheme
REGO evidence
Fuel Mix Disclosure evidence
A missing REGO can create significant financial and regulatory exposure. REGOs are evidence supporting the renewable share reported through Fuel Mix Disclosure. Voluntary certificate market — no fixed penalty per REGO. PowerView hashes your evidence snapshot SHA-256 + QR + timestamp, client-side only.
Based on Ofgem FMD audit requirements — evidence must be held and match reported generation.
ROC buy-out exposure
ROC Buy-Out Exposure Calculator
Enter your supplied volume to see the buy-out exposure. It is calculated in your browser from the published obligation and buy-out price for the RO year you pick.
Formula: Supplied Volume (MWh) × ROCs/MWh × buy-out price per missing ROC.
0.472 ROCs/MWh (Ofgem official 2026-27) · £69.34 per ROC (Ofgem official 2026-27)
Obligation levels and buy-out prices as published for the stated RO year (Ofgem, Renewables Obligation: buy-out price and mutualisation ceilings). Indicative only — not a substitute for your own RO reconciliation. The mutualisation ceiling and any late-payment or recycle-fund effects are NOT modelled: this is the buy-out cost of unmet ROCs only, and your final RO liability may differ. Confirm the current year's figures against the Ofgem publication before relying on them.
Note: ROC buy-out liability and any Ofgem enforcement exposure should stay separate. Enforcement depends on wider compliance failure, reporting, conduct and remediation. Ofgem do publish information about suppliers who are late or failed payers of ROCs by required deadlines.
ROC calculation context quoted with permission — credit EPI. Thanks to Energy Price Intelligence for accuracy check.
- Who you are buying from
- Annalu Pomarico, sole trader — Saint Helens, Merseyside, UK
- Where your data lives
- United Kingdom (London) — sub-processor register published
- Certification
- Cyber Essentials (IASME/Danzell) — Assessment Submitted 20 Aug 2026 — In Process, pending assessor review. No certification held yet. Data hosted UK (London). See step-by-step status
- Independence
- Not affiliated with, endorsed by or acting for Ofgem
Proof of architecture
How privacy works
Every rule PowerView runs is a fixed, published condition you can audit line by line — nothing inferred, nothing learned from your data. Where you opt in to the assisted free check, the file is processed under UK DPA 2018 for that single report and then deleted on our published retention schedule.
- 1
File stays in your browser
You choose a CSV. It is parsed in memory by your own browser — nothing is uploaded or stored.
- 2
Hash created locally
The Web Crypto API produces a SHA-256 digest plus a UTC ISO-8601 timestamp on your device.
- 3
Only the hash is saved
The 64-character digest is written to the append-only, hash-chained audit log. The underlying data never leaves you.
Runs in your browser — no network call
// PowerView evidence snapshot (client-side)
const buffer = await file.arrayBuffer();
const digest = await crypto.subtle.digest(
"SHA-256",
buffer,
);
const hash = [...new Uint8Array(digest)]
.map((b) => b.toString(16).padStart(2, "0"))
.join("");
// only `hash` + UTC timestamp are recorded
// the file itself never leaves this deviceVerify it yourself: open DevTools → Network, run a snapshot, and confirm no request carries your file.
Inside the workspace
The screens your compliance lead actually works in
Captured from the running product with a synthetic supplier estate loaded. Every account, MPAN and name below is generated — no customer data is shown.
Every SLC 21B flag and evidence-qualified SLC 21BA finding, with the evidence attached
SLC 21B review flags — 365+ days without an actual reading, or an estimate issued after a valid reading — plus SLC 21BA aged under-billing quantified only where bill dates, consumption periods and validated consumption evidence are supplied.
Detection and triage — your team keeps regulatory judgement
ECO4, WHD and FiT against statutory dates
One tracker for all three schemes, tied to beneficiaries and their account references, with delivery status and evidence exportable per scheme.
Alerts sent 08:00 London time
A hash chain an auditor can verify on demand
Each action is written once, linked to the hash of the entry before it and anchored daily. Running the verification returns a pass or the exact point the chain breaks.
Append-only — no edit path exists
Annalu Pomarico
Founder, PowerView UK — Saint Helens, Merseyside
I build PowerView UK myself. There is no sales team and no call centre — when you book a demo, you talk to the person who wrote the audit engine. If something in the evidence is wrong, I am the one who fixes it and tells you what changed.
Small suppliers are held to the same standards as the large integrated groups with a fraction of the headcount. PowerView exists so proving compliance takes an afternoon, not a quarter.
Read it before you talk to me
A real Exception Report, end to end
The same anonymised PDF a supplier receives: SLC 21BA and SLC 21B exceptions, £ at risk, the SHA-256 evidence hash and the QR verification link. No form, no email gate.
Features & entitlements
Plans that scale with your supplier estate
Flexible pricing per supplier organisation, from £350 one-time for a small estate. Audit Lite is one-time, Starter and Compliance are monthly. Plan access and the MPAN ceiling are enforced by the database itself, so they hold even if the interface is bypassed.
£350 one-time · no subscription
See exactly what PowerView finds before committing to a monthly plan.
Excl. VAT. One-time payment.
- SLC 21BA and SLC 21B exception engine
- Exception Reports with SHA-256 verification
- Immutable hash-chained audit trail
- Up to 10,000 MPANs (enforced in the database)
£1,200 per month
Excl. VAT. Billed monthly. Cancel anytime.
- Everything in Audit Lite
- Dashboard + supplier tracking
- REGO expiry alerts
- Up to 5 users
£3,000 per month
Excl. VAT. Billed monthly. Cancel anytime.
- Everything in Starter
- Fuel mix disclosure report
- Full audit pack download — every piece of evidence linked
- Supplier risk scoring and export
- Unlimited users and roles
Custom annual contract
- SSO and custom role mapping
- Automated data ingestion pipelines
- Dedicated compliance success manager
- SLA-backed support
- Support during regulatory investigations
Founding supplier programme
FOUNDING SUPPLIER PROGRAMME
3 places only · 50% off for 12 months
- Direct access to the founder
- Priority onboarding
- Influence the product roadmap
Trust & security
Controls, evidence and data handling
Your data is isolated at the database
Every record is fenced to your organisation by the database itself, not by application code. A bug in our app cannot expose another supplier's records.
The audit trail cannot be rewritten
Entries are append-only and SHA-256 hash-chained. Nobody — including us — can edit or delete history without the chain failing verification.
UK data residency
Compliance data and uploaded files are stored in the United Kingdom (London). Our full sub-processor register is published.
Evidence an auditor can re-check
Every Exception Report carries a hash, a UTC timestamp and a QR link to an independent verification page.
Deletion on a published schedule
Free-check files are processed for that single report and then purged automatically under our UK DPA 2018 retention policy.
Tested against the real thing
Cross-tenant isolation, audit-chain tampering and billing integrity are covered by an automated end-to-end suite run on every release.
The full technical annex — database isolation model, test coverage, sub-processor register and retention schedule — is published on the security page, and the platform status page is here.
Talk to the person who built it.
Fifteen minutes, your data, your questions. Or start entirely offline with the client-side evidence tool — nothing to sign, nothing uploaded.
PowerView UK is an independent tool. No affiliation, endorsement or partnership with any supplier or with Ofgem. Named suppliers are cited only as ideal customer profile.