Skip to content

Supplier settlement

Jump to bottom
RGx01 edited this page Jun 26, 2026 · 2 revisions

Supplier Settlement (Octopus / Kraken DCC)

From 3.0, EMT can reconcile each block against the settled half-hourly consumption your supplier actually bills from, fetched directly from the Kraken platform that powers Octopus Energy. This is the most accurate figure available — it is the same data that appears on your bill — and it removes any small drift between your local meter readings and what you are charged.

This is entirely opt-in. If you leave EMT in local-metering mode (cad), nothing here applies and EMT behaves exactly as it did in 2.x. See Upgrading from v2.

What it gives you

  • Settled import and export per half-hour, sourced from your supplier rather than inferred from a sensor.
  • Unit rates and standing charges pulled from your account on a schedule, so tariff changes are picked up automatically.
  • Automatic reconciliation — blocks start from your local readings (provisional) and are corrected to the settled figures as the data lands, typically a day or two later.

ℹ️ Settlement is about accuracy of an already-recorded block, not a second source of truth. Your local readings still drive the live Overview; the settled data corrects the historical record once it is available.

What you need

Requirement Notes
An Octopus Energy (or other Kraken-platform) account The API is read-only — EMT never changes anything on your account.
Your account's API key Found in your Octopus account dashboard under developer/API access.
Data-source mode cad+api Set in the Setup Wizard. Keeps your local readings and adds supplier settlement.

ℹ️ Local readings are still recommended alongside the API (cad+api) so the live Overview and provisional blocks work between settlements. A pure-API mode exists for sensorless installs but gives no live figures between blocks.

Setting it up

Supplier settlement is configured through the Setup Wizard (or Change Setup if you are adding it to an existing install — see Managing Billing Periods).

  1. In the wizard, choose your supplier and enter your API key. Credentials are stored by the add-on — there is no YAML to edit.
  2. Choose data-source mode cad+api.
  3. EMT verifies the key and discovers your account (meter points, MPANs) automatically. If you configured the Octopus API in an earlier build before the supplier field existed, EMT infers Octopus from your existing credentials — no re-entry needed.

Changing or removing credentials

  • Keep or replace — re-running setup lets you keep the stored key or enter a new one without retyping if it is unchanged.
  • Disconnect — a disconnect/clear action removes the stored credentials and returns EMT to local-metering behaviour. Your recorded data is kept.

Choosing what drives your bill

A billing source toggle decides whether your bill totals come from your meter sensor or the supplier API:

Billing source Bill is driven by
Meter sensor Your local cumulative readings (the 2.x behaviour).
Supplier API (DCC) The settled half-hourly figures from your supplier.

The toggle is available in the wizard and on the Data Management page under Billing Settlement Source. The card only appears once a valid supplier account and key are configured.

ℹ️ DCC wins once settled. With the API source selected, a block shows your provisional local figure until the settled data arrives, then updates to the settled value. There is no separate per-block toggle — provisional simply gives way to settled.

How reconciliation works

  • Provisional first — when a block finalises, it uses your local readings (or Octopus Home Mini telemetry, if that is your live source) so you always have a current figure.
  • Settlement sweep — EMT periodically pulls newly-settled half-hours and corrects the matching blocks. A horizon back-stop means older blocks are swept up as their settled data becomes available, not just the most recent ones.
  • Retry — transient API failures are retried automatically; settlement resumes after a restart without losing its place.

ℹ️ Settled data is typically available a day or two after the consumption occurred — this is a supplier-side timing characteristic, not an EMT delay.

Corrections are gated until settled

In API billing modes, manual rate corrections (see Data Management) are blocked on a block until that block has been DCC-settled. This prevents a manual edit from fighting the authoritative figure that is about to arrive. Once a block is settled, corrections behave as normal.

Octopus Home Mini

If you have an Octopus Home Mini, EMT can use its real-time demand feed as a live-power source for the Overview gauges and 48-hour history — no separate CAD sensor required. Mini figures are provisional: they give you a live and near-term number, and DCC settlement corrects the historical record once it lands.

⚠️ Export accounting via the Home Mini is not available in 3.0 (planned for a later release). Use a local export sensor or the settled export figures for export totals.

Privacy and rate limits

  • The API key is read-only and is used only to fetch your own consumption, rates and standing charges.
  • EMT polls conservatively and backs off on transient errors, staying within the platform's rate limits under normal use.

Related pages

Energy Meter Tracker

Home

Getting Started

Supplier Integration

Using EMT

Data Management

Reference

Clone this wiki locally