# Billing of services of price sheet A of the MSB between MSB and LF — LF view The process describes the communication between MSB and NB or LF on the billing of services in price sheet A of the MSB 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 Leistungen des Preisblatts A des MSB zwischen MSB und LF — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Rechnung\n\nMSB\n\nAS4\n31009\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nEBD check: E_0519, E_0210\nE_0519 — Rechnung der\nLeistungen des Preisblatts A\nprüfen\nE_0210 — Rechnung\nverarbeiten\n\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n2. Antwort\n\n\nMSB\n\nAS4\n33001, 33003, 33004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Mitteilung, dass die\nursprüngliche Rechnung\nkorrekt war\n\n\nMSB\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\nMSB\n\nAS4\n33001, 33003, 33004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Storno der ursprünglichen\nRechnung\n\n\nMSB\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\nMSB\n\nAS4\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abrechnung Leistungen des Preisblatts A des MSB zwischen MSB und LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nMSB\n\n\n1. Rechnung\nAS4 · PI 31009\n\nCreate transaction\nCreate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n2. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0519\nE_0519 — Rechnung der Leistungen des Preisblatts A prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Mitteilung, dass die ursprüngliche Rechnung k…\nAS4 · PI 29001 · E_0520\nE_0520 — Nicht-Zahlungsavis prüfen\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n4. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0521\nE_0521 — erneut Rechnung der Leistungen des Preisblatts A 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_0522\nE_0522 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Invoice
**Check identifiers** - [31009](/en/schnittstellen/202610/pruefi/INVOIC/PI_31009) — MSB invoice · AS4
**Flow**
  1. Message from **MSB** · 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.
  3. **Decision tree** - `31009` → [E_0519](/en/referenz/202610/ebd/E_0519) — Check invoice for the services of price sheet A - `31009` → [E_0210](/en/referenz/202610/ebd/E_0210) — Process invoice
### Response
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202610/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202610/pruefi/REMADV/PI_33004) — Electricity refusal line item · 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 **MSB** · AS4
    **Response per decision tree** - `33003`, `33004` → [E_0519](/en/referenz/202610/ebd/E_0519) · LF · Check invoice for the services of price sheet A
  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 was correct
**Check identifiers** - [29001](/en/schnittstellen/202610/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message from **MSB** · AS4
    **Response per decision tree** - `29001` → [E_0520](/en/referenz/202610/ebd/E_0520) · MSB · 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** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202610/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202610/pruefi/REMADV/PI_33004) — Electricity refusal line item · 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 **MSB** · AS4
    **Response per decision tree** - `33003`, `33004` → [E_0521](/en/referenz/202610/ebd/E_0521) · LF · Check invoice for the services of price sheet A 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 **MSB** · 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 **MSB** · AS4
    **Response per decision tree** - `33002` → [E_0522](/en/referenz/202610/ebd/E_0522) · 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_0519](/referenz/202610/ebd/E_0519) | Check invoice for the services of price sheet A | | [E_0520](/referenz/202610/ebd/E_0520) | Check non-payment advice | | [E_0521](/referenz/202610/ebd/E_0521) | Check invoice for the services of price sheet A again | | [E_0522](/referenz/202610/ebd/E_0522) | Check whether a response to the cancellation is required |
## Process information Wording of the consolidated version, profile ch. 3.5.1, pp. 95–96.
  1. ### Preconditions - The current fees of price sheet A of MSB have been transmitted by MSB to NB or LF within the use case „[Transmission of price sheet A of MSB from MSB to NB and LF](/en/prozessdoku/202610/LF/GPKE-Teil3-uebermittlung-preisblatt-a-des-msb-vom-msb-an-nb-und-lf)“. - The article IDs relevant for the billing are listed in price sheet A of MSB. - Towards NB the following applies: NB has, via the - Use case “Order placement of a configuration from NB or LF to MSB” a chargeable configuration was ordered and the order placement was confirmed by MSB or - Use case “Control command from NB or LF to MSB” instructed a chargeable control command and the instruction was confirmed by MSB. Note: if price sheet A of MSB states criteria for the instructed control command specifying when the control command is chargeable, these criteria must also be met. - Towards LF the following applies: LF has, via the - Use case “Order placement of a configuration from NB or LF to MSB” a chargeable configuration was ordered and the order placement was confirmed by MSB or - Use case “Control command from NB or LF to MSB” ordered a chargeable control command and the order placement was confirmed by MSB. Note: if price sheet A of MSB states criteria for the ordered control command specifying when the control command is chargeable, these criteria must also be met.
  2. ### Results The NB or LF will pay the invoice issued by the MSB.
  3. ### Error case #### Error cases - The invoice contains items that are not included as an article ID in price sheet A of the MSB. - The price of an article ID stated in the invoice does not match the price of the corresponding article ID stated in price sheet A of the MSB.
  4. ### Further requirements - The case of an invoice of the MSB 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 NB or LF or on the basis of a prior complaint by the NB or 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 references the underlying order placement.
  5. ### Trigger - The billing of one or more services from the MSB for the NB or LF is due.
  6. ### First message **MSB** sends “Invoice” (step 1). From here on, it is the turn of the party involved on this page.
  7. ### Objective The MSB has been informed that the NB or LF accepts the invoice.
## 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 MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-abrechnung-leistungen-des-preisblatts-a-des-msb-zwischen-msb-und-lf) — MSB *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)