# Billing of grid usage — NB view ## Process flow from the perspective of the NB \nSystem diagram: Abrechnung der Netznutzung — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nTriggered by incoming\nmessage: 17103\n\nProcess trigger received\n\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\n1. lfd. Messwerte\n\n\nLF\n\nAS4\n13002, 13009, 13006…\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Netznutzungsrechnung\n\n\nLF\n\nAS4\n31002, 31001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Antwort\n\n\nLF\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Mitteilung, dass die\nursprüngliche\nNetznutzungsrechnung kor…\n\n\nLF\n\nAS4\n29001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Antwort\n\n\nLF\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Storno der ursprünglichen\nRechnung\n\n\nLF\n\nAS4\n31004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n7. Antwort\n\n\nLF\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abrechnung der Netznutzung — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n1. lfd. Messwerte\nAS4 · PI 13002, 13009, 13006…\n\nUpdate transaction\nUpdate process data\n\n2. Netznutzungsrechnung\nAS4 · PI 31002, 31001\n\nUpdate transaction\nUpdate process data\n\n3. Antwort\nAS4 · PI 33001, 33002 · E_3018\nE_3018 — Netznutzungsabrechnung prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Mitteilung, dass die ursprüngliche Netznutzun…\nAS4 · PI 29001 · E_3035\nE_3035 — Prüfung sonstiger für den Abrechnungszeitraum relevante Daten…\n\nUpdate transaction\nUpdate process data\n\n5. Antwort\nAS4 · PI 33001, 33002 · E_3036\nE_3036 — erneut Netznutzungsrechnung prüfen\n\nUpdate transaction\nUpdate process data\n\n6. Storno der ursprünglichen Rechnung\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\n7. Antwort\nAS4 · PI 33001, 33002 · E_3038\nE_3038 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### ongoing meter reading values
**Check identifiers** - [13002](/en/schnittstellen/202610/pruefi/MSCONS/PI_13002) — Meter reading (gas) · AS4 - [13009](/en/schnittstellen/202610/pruefi/MSCONS/PI_13009) — Energy quantity (gas) · AS4 - [13006](/en/schnittstellen/202610/pruefi/MSCONS/PI_13006) — Meter reading value cancellation · AS4 - [13008](/en/schnittstellen/202610/pruefi/MSCONS/PI_13008) — Load curve (gas) · AS4
**Flow**
  1. **Triggered by incoming message** - [17103](/schnittstellen/202610/pruefi/ORDERS/PI_17103) 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. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202610/ausloeser-nb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  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.
### Grid usage invoice
**Check identifiers** - [31002](/en/schnittstellen/202610/pruefi/INVOIC/PI_31002) — NN invoice · AS4 - [31001](/en/schnittstellen/202610/pruefi/INVOIC/PI_31001) — Instalment invoice · AS4
**Flow**
  1. Message to **LF** · AS4
  2. **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
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `33002` → [E_3018](/en/referenz/202610/ebd/E_3018) · Check grid usage settlement
  2. **APERAK checks** - `33001`, `33002` → `Z33`
  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 with the data of the incoming message.
### Notification that the original grid usage invoice was correct
**Check identifiers** - [29001](/en/schnittstellen/202610/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message to **LF** · AS4
    **Response per decision tree** - `29001` → [E_3035](/en/referenz/202610/ebd/E_3035) · Check of other data relevant to the billing period and/or retroactive notifications
  2. **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
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `33002` → [E_3036](/en/referenz/202610/ebd/E_3036) · Check grid usage invoice again
  2. **APERAK checks** - `33001`, `33002` → `Z33`
  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 with the data of the incoming message.
### Cancellation of the original invoice
**Check identifiers** - [31004](/en/schnittstellen/202610/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message to **LF** · AS4
  2. **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
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `33002` → [E_3038](/en/referenz/202610/ebd/E_3038) · LF · Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required)
  2. **APERAK checks** - `33001`, `33002` → `Z33`
  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 with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_3018](/referenz/202610/ebd/E_3018) | Check grid usage settlement | | [E_3035](/referenz/202610/ebd/E_3035) | Check of other data relevant to the billing period and/or retroactive notifications | | [E_3036](/referenz/202610/ebd/E_3036) | Check grid usage invoice again | | [E_3038](/referenz/202610/ebd/E_3038) | Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required) |
## Process information
  1. ### First message The party involved on this page is itself the sender of: „ongoing meter reading values“ to **LF** (step 1).
## 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/geli-gas-2-0-abrechnung-der-netznutzung) — LF *The source provides no use case profile for this process — objective, precondition and result are not recorded there.* *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.* :::caution{title="Step sequence reconstructed"} For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification. ::: The source does not yet name the event that triggers these steps. Applies to: [2](#schritt-2) 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), [5](#schritt-5), [7](#schritt-7) 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: [6](#schritt-6)