> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engrate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Imbalance

> Read the imbalance that the market settles for your balance groups.

The market settles the imbalance of each of your balance groups: for each settlement period, how much more or less energy the balance group injected or withdrew than its trade schedule. Engrate gives you this imbalance as the market settles it, so you can check an imbalance invoice against it.

## Series

An imbalance series holds the imbalance of one balance group in one scheduling area. A market can also send the adjustments that it included in the imbalance, as more series. See [Imbalance series](https://docs.engrate.io/api-reference/imbalances/models/imbalance-series.md) for how to tell the series apart.

On a total, a positive volume means that the balance group was long, and a negative volume means that it was short. See [Imbalance record](https://docs.engrate.io/api-reference/imbalances/models/imbalance-record.md) for how to read the sign.

## Finality

The market can settle a period more than once. It sends a first run after the period, and can send later runs when it has more data or corrects a run. Engrate keeps every run. Each record has the `finality` of its run and, in `stated_at`, the market's timestamp for that version.

To get one value for each series and settlement period, use the record with the highest `finality`, then the latest `stated_at`. See [More than one record per settlement period](https://docs.engrate.io/api-reference/imbalances/models/imbalance-record.md#more-than-one-record-per-settlement-period).

## In each market

### Germany

The transmission system operator of each control area settles the balance groups in that area, as balance coordinator (Bilanzkoordinator). For each month, it sends the imbalance (Bilanzabweichung) of each balance group in its control area. It sends a later run of a series only when a value in it changes. When it settles a month without changing the series, the series keeps only its `preliminary` records, also after the balance coordinator has billed that month.

Each German imbalance series is the total of one balance group in one control area:

| Field | Value | Example |
| - | - | - |
| `external_id` | The id of the MaBiS metering point (MaBiS-Zählpunkt) that the balance coordinator gives the series. Its form differs between control areas. | `DE5338575724849YW15PBW6J3X0ZYEJP1` |
| `scheduling_area` | The EIC of the control area (Regelzone) | `10YDE-RWENET---I` |
| `balance_group` | The EIC of the balance group (Bilanzkreis). A sub-balance group (Sub-Bilanzkreis) has series of its own. | |
| `component_kind` | `total` | |
| `component_value` | `ALL` | |
| `market_dimensions` | Empty | `{}` |

A balance responsible party usually has a balance group in each control area where it trades. These balance groups can have the same EIC. Then the same `balance_group` value comes with a different `scheduling_area` for each of them. The adjustments in the German imbalance are not available yet.

The imbalance of a balance group already includes the imbalance of its sub-balance groups, and a sub-balance group can have sub-balance groups of its own. Do not add the series of a sub-balance group to the series of a balance group above it, or you count it twice. The balance coordinator bills only the settlement balance group (Abrechnungsbilanzkreis) at the top.

A series appears when the balance coordinator activates it for your balance group. When the volumes of a month arrive before the activation, Engrate stores them when the activation arrives. Their `known_at` stays the time when Engrate received them.

The balance coordinator sends no finality code. Engrate assigns each run a finality from the day the balance coordinator stated it, counted in German working days:

| The balance coordinator states the run | Finality |
| - | - |
| Before the 42nd working day after the settlement month | `preliminary` |
| From the 42nd working day after the settlement month | `final` |
| From the 8th working day of the 5th month after the settlement month | `correction` |

The market's timestamp of a run, in `stated_at`, is when the balance coordinator completed that version (Versionsangabe).

### Netherlands

TenneT, the transmission system operator, settles the imbalance (onbalans) of each balance responsible party (balanceringsverantwoordelijke) in the Netherlands, one day at a time. It updates the imbalance of a day every day until the imbalance is final. TenneT invoices the final imbalance. After that, the imbalance of a day changes only when TenneT recalculates it, for example after a grid operator corrects its metering data.

Each Dutch imbalance series belongs to one balance responsible party:

| Field | Value | Example |
| - | - | - |
| `external_id` | An id that Engrate gives the series. It stays the same in every update of the imbalance. | |
| `scheduling_area` | The EIC of the Netherlands | `10YNL----------L` |
| `balance_group` | The EAN of the balance responsible party. TenneT settles each balance responsible party as one balance group. | |
| `component_kind` | `total` for the imbalance, `adjustment` for the net adjustment that TenneT included in it | |
| `component_value` | `ALL` | |
| `market_dimensions` | Empty on the imbalance. On the net adjustment, the key `business_type` holds TenneT's code for the net adjustment. | `{"business_type": "A19"}` |

TenneT always sends the imbalance. It sends the net adjustment only to some balance responsible parties, so the imbalance can be your only series. The adjustment of each kind of balancing energy can also appear, but is not documented yet.

TenneT marks each update of a day as non-final or final. Engrate gives each update the finality of its mark:

| Code | Market term | Finality |
| - | - | - |
| `A01` | Non finalized state | `preliminary` |
| `A02` | Definitive state | `final` |

When TenneT recalculates a final imbalance, it adds a note (`TEN-100408`) to the update. Engrate gives such an update the finality `correction`, whatever its mark. When TenneT postpones the final imbalance by a working day (`TEN-100407`), the later final stays `final`.

TenneT can send a preliminary update after the final one. The final value stays current, because the highest finality comes first.

The market's timestamp of an update, in `stated_at`, is when TenneT created that update.

## In the API

See [List Imbalance Series](https://docs.engrate.io/api-reference/timeseries/list-imbalance-series.md) and [List Imbalances](https://docs.engrate.io/api-reference/timeseries/list-imbalances.md) in the API reference.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.