# Billing data for grid usage settlement — NB view The NB transmits the billing data for grid usage settlement to the LF. The LF checks the data and gives the NB a quality response message on the content of the data. If the LF expects different data content, it states this in the response message. In this case, the NB informs the LF of the processing status of its response message. ## Process flow from the perspective of the NB \nSystem diagram: Abrechnungsdaten Netznutzungsabrechnung — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ABR_NN\n\nAPI\n\n1. Abrechnungsdaten\nNetznutzungsabrechnung\n\n\nLF\n\nAS4\n55218\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Rückmeldung auf\nAbrechnungsdaten\n\n\nLF\n\nAS4\n55220\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\n\nEBD check: E_0595\nBestellung prüfen\n\n\nTrigger follow-up process:\n21047\n\n\nTriggered by incoming\nmessage: 55220\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"} gesamt={"\nSequence diagram: Abrechnungsdaten Netznutzungsabrechnung — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nSTART_ABR_NN\nTrigger event\n\n1. Abrechnungsdaten Netznutzungsabrechnung\nAS4 · PI 55218\n\nUpdate transaction\nUpdate process data\n\n2. Rückmeldung auf Abrechnungsdaten\nAS4 · PI 55220 · E_0610\nE_0610 — Abrechnungsdaten Netznutzungsabrechnung 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_0620\nE_0620 — Rückmeldung prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Billing data for grid usage settlement
**Check identifiers** - [55218](/en/schnittstellen/202604/pruefi/UTILMD/PI_55218) — Bill. data NNA · AS4
**Flow**
  1. **Prozessauslöser** [`START_ABR_NN`](/en/api/202604/ausloeser-nb/start-abr-nn) Ausprobieren The backend triggers this step with this event.
  2. Message to **LF** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/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** - [55220](/en/schnittstellen/202604/pruefi/UTILMD/PI_55220) — Response message/request bill. data NNA · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `55220` → [E_0610](/en/referenz/202604/ebd/E_0610) · LF · Check billing data for grid usage settlement (Based on EBD: E_0408_Check change from the NB)
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `55220` → `Z10` - `55220` → `Z16` - `55220` → `Z43` — APERAK check: Does object property match? - `55220` → `Z33`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/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/202604/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** - `55220` → [E_0595](/en/referenz/202604/ebd/E_0595) — Check order placement
  7. **Trigger follow-up process** - [21047](/en/schnittstellen/202604/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/202604/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. **Triggered by incoming message** - [55220](/en/schnittstellen/202604/pruefi/UTILMD/PI_55220) — Response message/request bill. data NNA 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/202604/ausloeser-nb/start-versand-bearb-meldung) \",\n \"positionsdaten\": [\n \"\"\n ],\n \"statusObjekt\": \"\"\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/202604/ausloeser-nb/start-versand-statusmeldung) \",\n \"positionsdaten\": [\n \"\"\n ],\n \"statusObjekt\": \"\"\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_0620](/en/referenz/202604/ebd/E_0620) · 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/202604/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_0610](/referenz/202604/ebd/E_0610) | Check billing data for grid usage settlement (Based on EBD: E_0408_Check change from the NB) | | [E_0620](/referenz/202604/ebd/E_0620) | 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.1.1, pp. 65–66.
  1. ### Preconditions - This is a consuming market location.
  2. ### Results If grid usage settlement takes place towards the LF, the NB carries out the use case "Transmission of the energy and demand values measured so far" in the event of an intra-year assignment of the LFN or E/G to the market location (via the use case „[Start of supply](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferbeginn)“ or „[Start of replacement supply / default supply](/en/prozessdoku/202604/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung)“) and if the market location is billed with an energy price and a demand price as part of grid usage settlement.
  3. ### Error case #### Error cases This is a generating market location or a tranche.
  4. ### Further requirements Note: There are situations in which an invoice correction can occur because of the exchange of the billing data for grid usage settlement. This is the case, for example, when a change (case b) into the past affects the period of an invoice.
  5. ### Trigger - Execution after the process step - for assigning the LFN to the market location as part of the use case „[Start of supply](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferbeginn)“ (case a). - for assigning the LF to the market location as part of the use case „[Creation](/en/prozessdoku/202604/NB/GPKE-Teil2-neuanlage)“ (case a). - for assigning the E/G to the market location as part of the use case „[Start of replacement supply / default supply](/en/prozessdoku/202604/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung)“ (case a). - for ending the assignment of the LF to the market location as part of the use case „[End of supply from LF to NB](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferende-von-lf-an-nb)“ (case a). - for ending the assignment of the LF to the market location as part of the use case „[End of supply from NB to LF](/en/prozessdoku/202604/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/202604/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-von-lf-an-nb)“, provided a change of the billing data for the grid usage settlement is to be made (case b). - Execution independent of the processes above, - provided the NB itself determines that billing data for the grid usage settlement towards the LF has changed (case b) (e.g. change of the grid usage settlement model from energy price/base price to energy price/demand price). - provided the NB assumes that there is a data discrepancy between NB and LF (case b). **Runs beforehand:** [Start of replacement supply / default supply](/en/prozessdoku/202604/NB/GPKE-Teil2-beginn-der-ersatz-grundversorgung), [Order placement for a change of billing data from LF to NB](/en/prozessdoku/202604/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/202604/NB/GPKE-Teil2-bestellung-einer-aenderung-von-abrechnungsdaten-zur-bilanzkreisabrechnung-von-uenb-an-nb), [Start of supply](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferbeginn), [End of supply from LF to NB](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferende-von-lf-an-nb), [End of supply from NB to LF](/en/prozessdoku/202604/NB/GPKE-Teil2-lieferende-von-nb-an-lf), [Creation](/en/prozessdoku/202604/NB/GPKE-Teil2-neuanlage) — these processes name the one shown here in their result.
  6. ### First message The party involved on this page sends this itself: “Billing data grid usage settlement” to **LF** (step 1).
  7. ### Objective The billing data for the grid usage 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/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung) — LF *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.*