# Billing of a miscellaneous service — LF view ## Process flow from the perspective of the LF \nSystem diagram: Abrechnung einer sonstigen Leistung — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Rechnung einer sonstigen\nLeistung\n\nNB\n\nAS4\n31011\n\nAPERAK check: Z24, Z25,\nZ26, Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n2. Antwort\n\n\nNB\n\nAS4\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Mitteilung, dass die\nursprüngliche Rechnung\neiner sonstigen…\n\n\nNB\n\nAS4\n29001\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n4. Antwort\n\n\nNB\n\nAS4\n33002, 33001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Storno der ursprünglichen\nRechnung\n\n\nNB\n\nAS4\n31004\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n6. Antwort\n\n\nNB\n\nAS4\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abrechnung einer sonstigen Leistung — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\n1. Rechnung einer sonstigen Leistung\nAS4 · PI 31011\n\nCreate transaction\nCreate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n2. Antwort\nAS4 · PI 33001, 33002 · E_1007\nE_1007 — Rechnung einer sonstigen Leistung prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Mitteilung, dass die ursprüngliche Rechnung e…\nAS4 · PI 29001 · E_1008\nE_1008 — Nicht-Zahlungsavis prüfen\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n4. Antwort\nAS4 · PI 33002, 33001 · E_1009\nE_1009 — erneut Rechnung einer sonstigen Leistung prüfen\n\nUpdate transaction\nUpdate process data\n\n5. Storno der ursprünglichen Rechnung\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n6. Antwort\nAS4 · PI 33001, 33002 · E_1010\nE_1010 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Invoice for another service
**Check identifiers** - [31011](/en/schnittstellen/202604/pruefi/INVOIC/PI_31011) — Invoice for other service · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `31011` → `Z24` - `31011` → `Z25` - `31011` → `Z26` - `31011` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response
**Check identifiers** - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202604/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33002` → [E_1007](/en/referenz/202604/ebd/E_1007) · LF · Check invoice for a miscellaneous service (Based on electricity EBD: E_0503_Check invoice for a miscellaneous service)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Notification that the original invoice for another service was correct
**Check identifiers** - [29001](/en/schnittstellen/202604/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `29001` → [E_1008](/en/referenz/202604/ebd/E_1008) · NB · Check non-payment advice (Based on electricity EBD: E_0504_Check non-payment advice)
  2. **APERAK checks** - `29001` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Response
**Check identifiers** - [33002](/en/schnittstellen/202604/pruefi/REMADV/PI_33002) — Refusal · AS4 - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33002` → [E_1009](/en/referenz/202604/ebd/E_1009) · LF · Check invoice for a miscellaneous service again (Based on electricity EBD: E_0505_Check invoice for a miscellaneous service again)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Cancellation of the original invoice
**Check identifiers** - [31004](/en/schnittstellen/202604/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `31004` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Response
**Check identifiers** - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202604/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33002` → [E_1010](/en/referenz/202604/ebd/E_1010) · LF · Check whether a response to the cancellation is required (Based on electricity EBD: E_0506_Check whether a response to the cancellation is required)
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/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_1007](/referenz/202604/ebd/E_1007) | Check invoice for a miscellaneous service (Based on electricity EBD: E_0503_Check invoice for a miscellaneous service) | | [E_1008](/referenz/202604/ebd/E_1008) | Check non-payment advice (Based on electricity EBD: E_0504_Check non-payment advice) | | [E_1009](/referenz/202604/ebd/E_1009) | Check invoice for a miscellaneous service again (Based on electricity EBD: E_0505_Check invoice for a miscellaneous service again) | | [E_1010](/referenz/202604/ebd/E_1010) | Check whether a response to the cancellation is required (Based on electricity EBD: E_0506_Check whether a response to the cancellation is required) |
## Process information
  1. ### First message **NB** sends “Invoice for another service” (step 1). From here on, it is the turn of the party involved on this page.
## 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/202604/NB/awh-sperrprozesse-gas-abrechnung-einer-sonstigen-leistung) — NB *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 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) 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: [1](#schritt-1), [5](#schritt-5)