# Billing data for balancing group settlement — NB view The NB transmits the billing data for the balancing group settlement to the LF and, where applicable, to the ÜNB. The LF or ÜNB checks the data and gives the NB a quality response message on the content of the data. If the LF or ÜNB expects different data content, it states this in the response message. In this case the NB informs the LF or ÜNB of the processing status of its response message. ## Process flow from the perspective of the NB \nSystem diagram: Abrechnungsdaten Bilanzkreisabrechnung — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ABR_BK\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n1. Abrechnungsdaten\nBilanzkreis-abrechnung vom\nNB an LF\n\n\nLF\n\nAS4\n55126, 55672\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Rückmeldung auf\nAbrechnungsdaten\n\n\nLF\n\nAS4\n55156, 55673\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z16,\nZ43, Z33, Z44\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nEBD check: E_0619, E_0595\nE_0619 — Rückmeldung\nprüfen (Basiert auf EBD:\nE_0626_Rückmeldung auf\nÄnderung prüfen)\nE_0595 — Bestellung prüfen\n\n\nTriggered by incoming\nmessage: 55614\n\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\n3. Bearbeitungsstand zur\nRückmeldung\n\n\nLF\n\nAS4\n21047\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_ABR_BK\n\nAPI\n\n4. Abrechnungsdaten\nBilanzkreis-abrechnung vom\nNB an ÜNB\n\n\nÜNB\n\nAS4\n55613, 55674\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Rückmeldung auf\nAbrechnungsdaten\n\n\nÜNB\n\nAS4\n55614, 55675\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z16,\nZ43, Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nPI 55614\n\nEBD check: E_0618, E_0613\nE_0618 — Rückmeldung\nverarbeiten (Basiert auf EBD:\nE_0626_Rückmeldung auf\nÄnderung prüfen)\nE_0613 — Bestellung prüfen\n(Basiert auf EBD:\nE_0573_Bestellung zur\nStammdatenänderung\nprüfen)\n\n\nTrigger follow-up process:\n21047\n\n\nTriggered by incoming\nmessage: 55614\n\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\n6. Bearbeitungsstand zur\nRückmeldung\n\n\nÜNB\n\nAS4\n21047\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abrechnungsdaten Bilanzkreisabrechnung — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nÜNB\n\n\nSTART_ABR_BK\nTrigger event\n\n1. Abrechnungsdaten Bilanzkreis-abrechnung vom N…\nAS4 · PI 55126, 55672\n\nUpdate transaction\nUpdate process data\n\n2. Rückmeldung auf Abrechnungsdaten\nAS4 · PI 55156, 55673 · E_0611\nE_0611 — Abrechnungsdaten Bilanzkreisabrechnung prüfen\n\nCreate transaction\nCreate process data\n\nUpdate transaction\nUpdate process data\n\n2 alternative events\nTrigger event\n\n3. Bearbeitungsstand zur Rückmeldung\nAS4 · PI 21047 · E_0619\nE_0619 — Rückmeldung prüfen\n\nUpdate transaction\nUpdate process data\n\nSTART_ABR_BK\nTrigger event\n\n4. Abrechnungsdaten Bilanzkreis-abrechnung vom N…\nAS4 · PI 55613, 55674\n\nUpdate transaction\nUpdate process data\n\n5. Rückmeldung auf Abrechnungsdaten\nAS4 · PI 55614, 55675 · E_0612\nE_0612 — Abrechnungsdaten Bilanzkreisabrechnung prüfen\n\nCreate transaction\nCreate process data\n\nUpdate transaction\nUpdate process data · PI 55614\n\n2 alternative events\nTrigger event\n\n6. Bearbeitungsstand zur Rückmeldung\nAS4 · PI 21047 · E_0618\nE_0618 — Rückmeldung verarbeiten\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Billing data balancing group settlement from the NB to LF
**Check identifiers** - [55126](/en/schnittstellen/202610/pruefi/UTILMD/PI_55126) — Bill. data BG bill. cons. MaLo · AS4 - [55672](/en/schnittstellen/202610/pruefi/UTILMD/PI_55672) — Bill. data BG settl. gen. Malo · AS4
**Flow**
  1. **Prozessauslöser** [`START_ABR_BK`](/en/api/202610/ausloeser-nb/start-abr-bk) \",\n \"verwendungAb\": \"\",\n \"zeitraumId\": null\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ABR_BK\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. **Load data for processing** - [Read balancing](/en/api/202610/backend-lesen/getaccountingbasic#bilanzierung-lesen) `GET /getAccountingBasic` Try it - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. Message to **LF** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response message on billing data
**Check identifiers** - [55156](/en/schnittstellen/202610/pruefi/UTILMD/PI_55156) — Response message/request bill. data BG bill. cons. MaLo · AS4 - [55673](/en/schnittstellen/202610/pruefi/UTILMD/PI_55673) — Response message/request bill. data BG settl. gen. Malo · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `55156`, `55673` → [E_0611](/en/referenz/202610/ebd/E_0611) · LF · Check billing data for balancing group settlement (Based on EBD: E_0408_Check change from the NB)
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `55156`, `55673` → `Z10` - `55156`, `55673` → `Z16` - `55156` → `Z43` — APERAK check: Does object property match? - `55156`, `55673` → `Z33` - `55673` → `Z44` — APERAK check: Does object property match?
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
  6. **Decision tree** - `55673` → [E_0619](/en/referenz/202610/ebd/E_0619) — Check response message (Based on EBD: E_0626_Check response message to the change) - `55673` → [E_0595](/en/referenz/202610/ebd/E_0595) — Check order placement
### Processing status of the response message
**Check identifiers** - [21047](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. **Triggered by incoming message** - [55614](/en/schnittstellen/202610/pruefi/UTILMD/PI_55614) — Response message/request bill. data BG settl. consum. MaLo The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
  2. **Process trigger** - [`START_VERSAND_BEARB_MELDUNG`](/en/api/202610/ausloeser-nb/start-versand-bearb-meldung) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_BEARB_MELDUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_VERSAND_STATUSMELDUNG`](/en/api/202610/ausloeser-nb/start-versand-statusmeldung) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_STATUSMELDUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  3. Message to **LF** · AS4
    **Response per decision tree** - `21047` → [E_0619](/en/referenz/202610/ebd/E_0619) · NB · Check response message (Based on EBD: E_0626_Check response message to the change)
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Billing data balancing group settlement from the NB to ÜNB
**Check identifiers** - [55613](/en/schnittstellen/202610/pruefi/UTILMD/PI_55613) — Bill. data BG settl. consum. MaLo · AS4 - [55674](/en/schnittstellen/202610/pruefi/UTILMD/PI_55674) — Bill. data BG settl. gen. Malo · AS4
**Flow**
  1. **Prozessauslöser** [`START_ABR_BK`](/en/api/202610/ausloeser-nb/start-abr-bk) \",\n \"verwendungAb\": \"\",\n \"zeitraumId\": null\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\",\n \"transaktionsgrund\": \"\",\n \"transaktionsgrundergaenzung\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ABR_BK\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **ÜNB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response message on billing data
**Check identifiers** - [55614](/en/schnittstellen/202610/pruefi/UTILMD/PI_55614) — Response message/request bill. data BG settl. consum. MaLo · AS4 - [55675](/en/schnittstellen/202610/pruefi/UTILMD/PI_55675) — Response message/request bill. data BG settl. gen. Malo · AS4
**Flow**
  1. Message from **ÜNB** · AS4
    **Response per decision tree** - `55614`, `55675` → [E_0612](/en/referenz/202610/ebd/E_0612) · ÜNB · Check billing data for balancing group settlement
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `55614`, `55675` → `Z10` - `55614`, `55675` → `Z16` - `55614`, `55675` → `Z43` — APERAK check: Does object property match? - `55614`, `55675` → `Z33`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
  5. **Write endpoint** - `55614` → Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
  6. **Decision tree** - `55614`, `55675` → [E_0618](/en/referenz/202610/ebd/E_0618) — Process response message (Based on EBD: E_0626_Check response message to the change) - `55675` → [E_0613](/en/referenz/202610/ebd/E_0613) — Check order placement (Based on EBD: E_0573_Check order placement for master data change)
  7. **Trigger follow-up process** - [21047](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21047) — Processing status message After processing, the MACO APP starts this follow-up process itself.
### Processing status of the response message
**Check identifiers** - [21047](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. **Triggered by incoming message** - [55614](/en/schnittstellen/202610/pruefi/UTILMD/PI_55614) — Response message/request bill. data BG settl. consum. MaLo The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
  2. **Process trigger** - [`START_VERSAND_BEARB_MELDUNG`](/en/api/202610/ausloeser-nb/start-versand-bearb-meldung) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_BEARB_MELDUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_VERSAND_STATUSMELDUNG`](/en/api/202610/ausloeser-nb/start-versand-statusmeldung) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_STATUSMELDUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  3. Message to **ÜNB** · AS4
    **Response per decision tree** - `21047` → [E_0618](/en/referenz/202610/ebd/E_0618) · NB · Process response message (Based on EBD: E_0626_Check response message to the change)
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0611](/referenz/202610/ebd/E_0611) | Check billing data for balancing group settlement (Based on EBD: E_0408_Check change from the NB) | | [E_0612](/referenz/202610/ebd/E_0612) | Check billing data for balancing group settlement | | [E_0618](/referenz/202610/ebd/E_0618) | Process response message (Based on EBD: E_0626_Check response message to the change) | | [E_0619](/referenz/202610/ebd/E_0619) | Check response message (Based on EBD: E_0626_Check response message to the change) |
## Process information Wording of the consolidated version, profile ch. 3.1.2.1, pp. 69–70.
  1. ### Preconditions - The following applies to the transmission of the billing data for the balancing group settlement to ÜNB: transmission, provided that the aggregation responsibility - passes from the NB to the ÜNB or - lies with the ÜNB and the data is relevant for the ÜNB or - passes from the ÜNB to the NB.
  2. ### Results - The activation of MaBiS metering points may be required for the transmission of aggregated time series according to MaBiS. - If a master data change is required, NB carries out the use case "master data change" (here: SD “[Master data change originating from NB (responsible)](/en/prozessdoku/202610/NB/GPKE-Teil4-stammdatenaenderung-vom-nb-verantwortlich-ausgehend)”) (GPKE Part 4). - If it is a market location or tranche with balancing on the basis of quarter-hour values: NB carries out the use case “[Master data for balancing group integrity](/en/prozessdoku/202610/NB/GPKE-Teil4-stammdaten-zur-bilanzkreistreue)” (GPKE Part 4).
  3. ### Trigger - Execution after the process step - for assigning the LFN to the market location or tranche as part of the use case „[Start of supply](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferbeginn)“ (case a). - for assigning the LF to the market location or tranche as part of the use case „[Creation](/en/prozessdoku/202610/NB/GPKE-Teil2-neuanlage)“ (case a). - for assigning the E/G to the consuming market location as part of the use case „[Start of replacement supply / default supply](/en/prozessdoku/202610/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung)“ (case a). - for assigning the LFN to the generating market location or to the tranche as part of the use case „Establishing a 100% LF assignment to a generating market location“ (case a). - for ending the assignment of the LF to the market location or tranche as part of the use case „[End of supply from LF to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferende-von-lf-an-nb)“ (case a). - for ending the assignment of the LF to the market location or tranche as part of the use case „[End of supply from NB to LF](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferende-von-nb-an-lf)“ (case a). - on the processing status of the order placement as part of the SD „[Order placement of a change of billing data from LF to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-von-lf-an-nb)“, provided a change of the billing data for the balancing group settlement is to be made (case b). - on the processing status of the order placement as part of the SD „[Order placement of a change of billing data for the balancing group settlement from ÜNB to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-zur-bilanzkreisabrechnung-von-uenb-an-nb)“, provided a change of the billing data for the balancing group settlement is to be made (case b). - Execution independent of the processes above, - provided the NB itself determines that billing data for the balancing group settlement has changed (case b) (e.g. change of the annual consumption forecast). This does not apply to a change of the MSB as part of the WiM part 1. - provided the NB assumes that there is a data discrepancy between NB and LF or between NB and ÜNB (case b). - provided the NB transfers the aggregation responsibility to the ÜNB (case b). - provided the NB transfers the aggregation responsibility to the NB (case b). **Runs beforehand:** [Start of replacement supply / default supply](/en/prozessdoku/202610/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung), [Order placement for a change of billing data from LF to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-von-lf-an-nb), [Order placement for a change of billing data for balancing group settlement from ÜNB to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-zur-bilanzkreisabrechnung-von-uenb-an-nb), [Case 1: LF assignment for EEG market location without DV obligation or KWKG market location without DV obligation](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-1-lf-zuordnung-bei-eeg-marktlokation-ohne-dv-pflicht-bzw-kwkg-marktlokation-ohne-dv-pflicht), [Case 2: LF assignment for EEG market location with DV obligation](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-2-lf-zuordnung-bei-eeg-marktlokation-mit-dv-pflicht), [Case 3: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped without tranches](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-3-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-nicht-tranchiert-abgebildet), [Case 4: LF assignment for KWKG market location with DV obligation or non-EEG / non-KWKG market location and the market location is mapped with tranches](/en/prozessdoku/202610/NB/GPKE-Teil2-fall-4-lf-zuordnung-bei-kwkg-marktlokation-mit-dv-pflicht-bzw-nicht-eeg-nicht-kwkg-marktlokation-und-marktlokation-wird-tranchiert-abgebildet), [Start of supply](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferbeginn), [End of supply from LF to NB](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferende-von-lf-an-nb), [End of supply from NB to LF](/en/prozessdoku/202610/NB/GPKE-Teil2-lieferende-von-nb-an-lf), [Creation](/en/prozessdoku/202610/NB/GPKE-Teil2-neuanlage) — these processes name the one shown here in their result.
  4. ### First message The party involved on this page sends this itself: “Billing data balancing group settlement from the NB to the LF” to **LF** (step 1).
  5. ### Objective The billing data for the balancing group settlement have been exchanged.
## 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 LF](/en/prozessdoku/202610/LF/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung) — LF - [View ÜNB](/en/prozessdoku/202610/UENB/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung) — ÜNB · market role UENB *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.* For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body. Applies to: [3](#schritt-3), [6](#schritt-6)