Skip to main content
The reconciliation view provides a side-by-side comparison of your latest submitted schedule values against the counterparty values reported in anomaly documents from the TSO.

Structure

A reconciliation response contains one ReconciliationSeriesItem per affected series. Each item includes:
  • Your values (our_values) — the quarter-hourly MW values from your latest accepted version
  • Counterparty values (counterparty_values) — the values the TSO received from the other party
  • Deltas (deltas) — per-interval difference (your value minus counterparty value)
  • Exchange priority flag (has_exchange_priority) — whether the counterparty holds Börsenvorrang

Exchange priority

When has_exchange_priority is true, the counterparty’s values take precedence per Bilanzkreisvertrag clause 12.b. The anomaly is informational — the TSO will impose the counterparty’s values regardless of what you submitted. See Exchange Priority for details on looking up which balance groups hold this status.

Null values

our_values and deltas are null when the anomaly has business type A28 (counterpart missing from your side) — meaning the TSO received a series from the counterparty that has no matching series in your submission.

Full reconciliation view comparing the latest submitted version against anomaly records for a schedule.

delivery_date
string
required

Delivery date in ISO 8601 format.

Example:

"2026-03-26"

schedule_uid
string
required

Parent Schedule identifier.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"

series
ReconciliationSeriesItem · object[]
required

Per-series reconciliation data.

tso
string
required

TSO identifier.

Example:

"50HERTZ_DE_TSO"