# Billing of metering point operation with iMS towards the NB — MSB-MALO view The process describes the communication between the MSB of the market location and the NB on the pro rata billing of metering point operation with iMS towards 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 MSB (MSB-MALO) \nSystem diagram: Abrechnung Messstellenbetrieb mit iMS gegenüber dem NB — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\n1. Rechnung\n\nNB\n\nAS4\n31009\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nNB\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\nNB\n\nAS4\n29001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort\n\n\nNB\n\nAS4\n33001, 33003, 33004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n5. Storno der ursprünglichen\nRechnung\n\n\nNB\n\nAS4\n31004\n\nUpdate transaction\n\n\nUpdate process data\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 Messstellenbetrieb mit iMS gegenüber dem NB — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nNB\n\n\n1. Rechnung\nAS4 · PI 31009\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0566\nE_0566 — Rechnung Messtellenbetrieb mit iMS gegenüber dem NB prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Mitteilung, dass die ursprüngliche Rechnung k…\nAS4 · PI 29001 · E_0567\nE_0567 — Nichtzahlungsavis prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0568\nE_0568 — erneut Rechnung Messtellenbetrieb mit iMS gegenüber dem NB prü…\n\nUpdate transaction\nUpdate process data\n\n5. Storno der ursprünglichen Rechnung\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\n6. Antwort\nAS4 · PI 33001, 33002 · E_0569\nE_0569 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="MSB-MALO" /> ## Process steps ### Invoice
**Check identifiers** - [31009](/en/schnittstellen/202604/pruefi/INVOIC/PI_31009) — MSB invoice · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202604/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202604/pruefi/REMADV/PI_33004) — Electricity refusal line item · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `33003` → [E_0566](/en/referenz/202604/ebd/E_0566) · NB · Check invoice for metering point operation with iMS towards the NB
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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 invoice was correct
**Check identifiers** - [29001](/en/schnittstellen/202604/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message to **NB** · AS4
    **Response per decision tree** - `29001` → [E_0567](/en/referenz/202604/ebd/E_0567) · MSB · Check non-payment advice
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202604/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202604/pruefi/REMADV/PI_33004) — Electricity refusal line item · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `33003` → [E_0568](/en/referenz/202604/ebd/E_0568) · NB · Check invoice for metering point operation with iMS towards the NB again
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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/202604/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. **Load data for processing** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_RECHNUNG_BASIS`
  2. Message to **NB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202604/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `33002` → [E_0569](/en/referenz/202604/ebd/E_0569) · NB · Check whether a response to the cancellation is required
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/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_0566](/referenz/202604/ebd/E_0566) | Check invoice for metering point operation with iMS towards the NB | | [E_0567](/referenz/202604/ebd/E_0567) | Check non-payment advice | | [E_0568](/referenz/202604/ebd/E_0568) | Check invoice for metering point operation with iMS towards the NB again | | [E_0569](/referenz/202604/ebd/E_0569) | Check whether a response to the cancellation is required |
## Process information Wording of the consolidated version, profile ch. 6.1, pp. 86–87.
  1. ### Preconditions - The current fees applicable to NB for metering point operation with iMS have been transmitted by the MSB of the market location to NB within the use case „Transmission of price sheet „Metering point operation with iMS towards NB“ from MSB to NB“. - The MSB is the MSB of the market location. - For a market location with one assigned metering location, that metering location must be equipped with a iMS. - For a market location with at least two assigned metering locations, at least one metering location must be equipped with a iMS. - The services provided at the market location by MSB have been exchanged between MSB and NB using the (group) article ID within the master data processes.
  2. ### Results The NB will pay the invoice issued by the MSB of the market location.
  3. ### Error case #### Error cases - The MSB is not the MSB of the market location. - The process applies to a metering location with mME or kME. - The process applies to a metering location with iMS, where this metering location is not relevant for determining the energy quantity of the market location. - The information required for the invoice has not been transmitted via the master data processes. - The information required for the invoice has been transmitted via the master data processes, but was not taken into account accordingly in the invoice. - The invoice contains items that are not included as an article ID in the price sheet „Metering point operation with iMS towards 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 price sheet „Metering point operation with iMS towards the NB“. - The article ID of the invoice does not take into account the master data transmitted by the MSB of the market location for the billing of the metering point operation with iMS towards the NB. - A metering location equipped with iMS that has already been billed via another market location is billed at this market location.
  4. ### Further requirements - The case of an invoice 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 on the basis of a prior complaint by the NB) 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.
  5. ### Trigger Invoicing for metering point operation is due from the MSB of the market location to the NB.
  6. ### First message The party involved on this page is itself the sender of: „Invoice“ to **NB** (step 1).
  7. ### Objective The MSB of the market location has been informed that the NB 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 NB](/en/prozessdoku/202604/NB/WiM-Teil1-abrechnung-messstellenbetrieb-mit-ims-gegenueber-dem-nb) — 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 source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [5](#schritt-5) 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: [2](#schritt-2), [4](#schritt-4), [6](#schritt-6) 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)