# Transmission of balancing area clearing list from ÜNB to NB (incl. subscription) — View ÜNB The NB requests or, where required, subscribes to the BG-CL from the ÜNB. The ÜNB sends the requested BG-CL to the NB. The NB has the option of plausibility-checking the BG-SZR (category B) against the data of the BG-CL. The NB can give a response message to the BG-CL received from the ÜNB. This response message is made electronically in standardised form by means of a correction list for the BG-CL. Further steps for clarification take place via other communication channels. A NB can request the BG-CL immediately after receiving the BG-SZR (category B). Alternatively, the NB can apply for the list to be sent regularly (subscription). A BG-CL can be requested for every version of a BG-SZR (category B) that has been sent. A BG-CL is created for every BG-SZR (category B) and can also be requested separately. ## Process flow from the perspective of the ÜNB \nSystem diagram: Übermittlung Bilanzierungsgebietsclearingliste vom ÜNB an NB (inkl. Abonnierung) — view of ÜNB\n\n\nCustomer backend system\n\nMACO APP · ÜNB\n\nMarket partner\n\n\n\n1. Anforderung der BG-CL\n\nNB\n\nAS4\n17206\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Übermittlung der BG-CL\n\n\nNB\n\nAS4\n55195\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Rückmeldung zur BG-CL\n\n\nNB\n\nAS4\n55196\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung Bilanzierungsgebietsclearingliste vom ÜNB an NB (inkl. Abonnierung) — view of ÜNB\n\n\nBackend (customer)\n\n\nMACO APP · ÜNB\n\n\nNB\n\n\n1. Anforderung der BG-CL\nAS4 · PI 17206\n\nCreate transaction\nCreate process data\n\n2. Übermittlung der BG-CL\nAS4 · PI 55195\n\nUpdate transaction\nUpdate process data\n\n3. Rückmeldung zur BG-CL\nAS4 · PI 55196 · E_0017, E_0052\nE_0017 — Marktlokationen mit BG-CL abgleichen\nE_0052 — Marktlokationen mit BG-CL abgleichen\n\nUpdate transaction\nUpdate process data\n"} titel="ÜNB" /> ## Process steps ### Request for the BG-CL
**Check identifiers** - [17206](/en/schnittstellen/202610/pruefi/ORDERS/PI_17206) — Request for balancing area clearing list · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Write endpoint** - Transaction created — `ERSTELLEN_PROZESSDATEN` Creates a new transaction in the backend with the data of the incoming message.
### Transmission of the BG-CL
**Check identifiers** - [55195](/en/schnittstellen/202610/pruefi/UTILMD/PI_55195) — Balancing area clearing list · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Response message on the BG-CL
**Check identifiers** - [55196](/en/schnittstellen/202610/pruefi/UTILMD/PI_55196) — Response to balancing area clearing list · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `55196` → [E_0017](/en/referenz/202610/ebd/E_0017) · NB · Reconcile market locations with BG-CL - `55196` → [E_0052](/en/referenz/202610/ebd/E_0052) · NB · Reconcile market locations with BG-CL
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0017](/referenz/202610/ebd/E_0017) | Reconcile market locations with BG-CL | | [E_0052](/referenz/202610/ebd/E_0052) | Reconcile market locations with BG-CL |
## Process information Wording of the consolidated version, profile ch. 9.4.1, pp. 107–108.
  1. ### Preconditions For a single request: - The NB has the BG-SZR (category B) from the ÜNB. - The NB knows the MaBiS-ZP of the BG-SZR (category B). In the case of a subscription: - The NB only knows the version with a time delay after receipt of the BG-CL, since the BG-SZR (category B) is transmitted via the BIKO and not directly. - The NB knows the MaBiS-ZP of the BG-SZR (category B).
  2. ### Further requirements If a subscription is requested again while a subscription already exists, from the point in time of receipt the recipient of the subscription refers to the new subscription in all BG-CL resulting from it.
  3. ### First message **NB** sends “Request for the BG-CL” (step 1). From here on, it is the turn of the party involved on this page.
  4. ### Objective The NB has the requested balancing area clearing list (BG-CL). If the BG-CL has been subscribed to by the NB, the NB is registered with the ÜNB as a subscriber of the BG-CL. Where applicable, the ÜNB has the response message of the NB on the BG-CL that was sent.
## Other views of the process The same process through the eyes of the other parties involved: the same steps, each read from their point of view. - [View NB](/en/prozessdoku/202610/NB/MaBiS-uebermittlung-bilanzierungsgebietsclearingliste-vom-uenb-an-nb-inkl-abonnierung) — NB *The steps are the **possible** messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with **←** it receives, with **→** it sends. Collapsed steps run between other market partners.* The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created. Applies to: [1](#schritt-1) The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists. Applies to: [3](#schritt-3) For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button. Applies to: [1](#schritt-1), [2](#schritt-2), [3](#schritt-3)