# Billing of a miscellaneous service — LF view The process describes the communication between NB and LF on the billing of another service that is contained in the price sheets for disconnection costs, late payment charges or reactive energy of the NB and, where applicable, the automated complaint case. An invoice correction always comprises a cancellation invoice and a new invoice. ## 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\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\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_0503\nE_0503 — 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_0504\nE_0504 — 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_0505\nE_0505 — 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_0506\nE_0506 — 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/202610/pruefi/INVOIC/PI_31011) — Invoice for other service · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/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/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202610/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_0503](/en/referenz/202610/ebd/E_0503) · LF · Check invoice for a miscellaneous service
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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/202610/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `29001` → [E_0504](/en/referenz/202610/ebd/E_0504) · NB · 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/202610/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/202610/pruefi/REMADV/PI_33002) — Refusal · AS4 - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202610/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_0505](/en/referenz/202610/ebd/E_0505) · LF · Check invoice for a miscellaneous service again
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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/202610/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202610/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_0506](/en/referenz/202610/ebd/E_0506) · LF · Check whether a response to the cancellation is required
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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_0503](/referenz/202610/ebd/E_0503) | Check invoice for a miscellaneous service | | [E_0504](/referenz/202610/ebd/E_0504) | Check non-payment advice | | [E_0505](/referenz/202610/ebd/E_0505) | Check invoice for a miscellaneous service again | | [E_0506](/referenz/202610/ebd/E_0506) | Check whether a response to the cancellation is required |
## Process information Wording of the consolidated version, profile ch. 3.4.5.1, pp. 98–99.
  1. ### Preconditions - The current fees for other services (price sheets disconnection costs, late payment charges and reactive energy) have been transmitted by NB to LF within the use case „[Transmission of price sheet NB to LF](/en/prozessdoku/202610/LF/GPKE-Teil2-uebermittlung-preisblatt-nb-an-lf)“. - An other service can be represented by one of the article IDs of the price sheets disconnection costs, late payment charges or reactive energy of NB.
  2. ### Results The LF will pay the invoice for the other service issued by the NB.
  3. ### Error case #### Error cases - The invoice contains items that are not included as an article ID in one of the price sheets for disconnection costs, late payment charges or reactive energy of the NB. - The price of an article ID stated in the invoice does not match the price of the corresponding article ID stated in the relevant price sheet.
  4. ### Further requirements - The case of an invoice for another service that has been complained about or turns out to be incorrect (the cancellation of the original invoice is carried out either without a prior complaint by the LF or on the basis of a prior complaint by the LF) forms part of the standard process and, apart from clarifications, must be handled fully automatically. In the event of a complaint, the so-called “all-or-nothing principle” applies, according to which an invoice is either accepted in full as correct or rejected in full. The processes to be handled in the event of a conflict as part of receivables management or the dunning procedure are not shown and are to be resolved bilaterally. - An invoice within the interruption and restoration of grid connection use references the underlying disconnection order. - Via the use case „Billing of another service“, late payment charges, - which have arisen in connection with a grid usage invoice, - as well as in connection with an invoice for another service, are invoiced. A unique reference to the underlying invoice must be specified. - If the final customer is itself the grid user (= grid user without an all-inclusive contract), it assumes the role of LF within the meaning of this process description, insofar as these provisions are applicable to it accordingly.
  5. ### Trigger - An other service has been ordered via the use case „[Interruption of grid connection use (disconnect) on the instruction of LF](/en/prozessdoku/202610/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)“ or - late payment charges have arisen at the NB or - the LF voluntarily takes over the billing of the reactive energy article ID towards the AN.
  6. ### First message **NB** sends “Invoice for another service” (step 1). From here on, it is the turn of the party involved on this page.
  7. ### Objective The NB has been informed that the LF accepts the invoice for the other service.
## 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/GPKE-Teil2-abrechnung-einer-sonstigen-leistung) — 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) 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)