# Billing of services — MSBA view The process describes the billing of the charges for: - the temporary continuation of the metering point operation - the device takeover (transfer of use by lease or rent) - the device takeover (purchase) or - Additional or control readings. MSBN of the metering location or gMSB of the metering location checks the invoice (e.g. for reference to the correct metering location and to the applicable time period of the metering point operation). If the check is positive, a confirmation of the payment must be communicated. Confirmations relating to several invoices must be combined. If the check is negative (case of complaint), the so-called “all-or-nothing principle” applies, under which a single invoice within an invoice file that may contain several invoices is either accepted as correct in full or rejected in full. An invoice correction always comprises a cancellation invoice and a new invoice. Both the cancelled invoice(s) and the re-billed invoice(s) are combined into one file. A rejection of the payment must be substantiated. Rejections relating to several invoices must be combined. The processes to be handled in the event of a conflict as part of receivables management or the dunning procedure are not described here. Likewise, the mapping of the onward billing to the AN or ANN is not described. ## Process flow from the perspective of the MSB (MSBA) \nSystem diagram: Abrechnung von Dienstleistungen — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_VERSAND_RECHNUN\nG\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n1. Rechnung\n(Messstellenbetrieb /\nGeräteübernahme)\n\n\nMSB (entspricht MSBN…\n\nAS4\n31003\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nMSB (entspricht MSBN…\n\nAS4\n33003, 33001, 33004\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_RECHNUN\nG\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n3. Storno der ursprünglichen\nRechnung\n\n\nMSB (entspricht MSBN…\n\nAS4\n31004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Antwort\n\n\nMSB (entspricht MSBN…\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abrechnung von Dienstleistungen — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nMSB (entspricht MSBN am O…\n\n\nSTART_VERSAND_RECHNUNG\nTrigger event\n\n1. Rechnung (Messstellenbetrieb / Geräteübernahm…\nAS4 · PI 31003\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 33003, 33001, 33004 · E_0259\nE_0259 — Rechnung verarbeiten\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_RECHNUNG\nTrigger event\n\n3. Storno der ursprünglichen Rechnung\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\n4. Antwort\nAS4 · PI 33001, 33002 · E_0261\nE_0261 — Storno verarbeiten\n\nUpdate transaction\nUpdate process data\n"} titel="MSBA" /> ## Process steps ### Invoice (metering point operation / device takeover)
**Check identifiers** - [31003](/en/schnittstellen/202610/pruefi/INVOIC/PI_31003) — WiM invoice · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_RECHNUNG`](/en/api/202610/ausloeser-msb/start-versand-rechnung) \",\n \"coErgaenzung\": \"\",\n \"hausnummer\": \"\",\n \"landescode\": \"\",\n \"ort\": \"\",\n \"ortsteil\": \"\",\n \"postfach\": \"\",\n \"postleitzahl\": \"\",\n \"strasse\": \"\",\n \"zusatzInformation\": \"\"\n },\n \"messlokationsId\": \"\"\n }\n ],\n \"RECHNUNG\": [\n {\n \"bearbeitungsdatum\": \"\",\n \"faelligkeitsdatum\": \"\",\n \"gesamtbrutto\": {\n \"wert\": \"\"\n },\n \"rechnungsdatum\": \"\",\n \"rechnungspositionen\": [\n \"\"\n ],\n \"rechnungsstatus\": \"\",\n \"rechnungstyp\": \"\",\n \"referenzDokumentennummer\": \"\",\n \"steuerbetraege\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"pruefidentifikator\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_RECHNUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. **Load data for processing** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - `LESEN_RECHNUNG_BASIS`
  3. Message to **MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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** - [33003](/en/schnittstellen/202610/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33004](/en/schnittstellen/202610/pruefi/REMADV/PI_33004) — Electricity refusal line item · AS4
**Flow**
  1. Message from **MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)** · AS4
    **Response per decision tree** - `33003`, `33004` → [E_0259](/en/referenz/202610/ebd/E_0259) · MSB · Process invoice
  2. **APERAK checks** - `33003`, `33001`, `33004` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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/202610/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_RECHNUNG`](/en/api/202610/ausloeser-msb/start-versand-rechnung) \",\n \"coErgaenzung\": \"\",\n \"hausnummer\": \"\",\n \"landescode\": \"\",\n \"ort\": \"\",\n \"ortsteil\": \"\",\n \"postfach\": \"\",\n \"postleitzahl\": \"\",\n \"strasse\": \"\",\n \"zusatzInformation\": \"\"\n },\n \"messlokationsId\": \"\"\n }\n ],\n \"RECHNUNG\": [\n {\n \"bearbeitungsdatum\": \"\",\n \"faelligkeitsdatum\": \"\",\n \"gesamtbrutto\": {\n \"wert\": \"\"\n },\n \"rechnungsdatum\": \"\",\n \"rechnungspositionen\": [\n \"\"\n ],\n \"rechnungsstatus\": \"\",\n \"rechnungstyp\": \"\",\n \"referenzDokumentennummer\": \"\",\n \"steuerbetraege\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"pruefidentifikator\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_RECHNUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. **Load data for processing** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - `LESEN_RECHNUNG_BASIS`
  3. Message to **MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)** · AS4
    **Response per decision tree** - `33002` → [E_0261](/en/referenz/202610/ebd/E_0261) · MSB · Process cancellation
  2. **APERAK checks** - `33001`, `33002` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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_0259](/referenz/202610/ebd/E_0259) | Process invoice | | [E_0261](/referenz/202610/ebd/E_0261) | Process cancellation |
## Process information Wording of the consolidated version, profile ch. 3.7.1, pp. 79–80.
  1. ### Preconditions A valid agreement on the billing of the billing object exists between the MSB.
  2. ### Results The invoice for the device or for the special meter reading has been paid.
  3. ### Error case #### Result in the error case The invoice for the device or the special meter reading has not been paid. #### Error cases The MSBN of the metering location or the gMSB of the metering location has received an incorrect invoice.
  4. ### First message The party involved on this page is itself the sender of: „Invoice (metering point operation / device takeover)“ to **MSB (corresponds to MSBN on the metering location object or gMSB on the metering location object)** (step 1).
  5. ### Objective The MSBN of the metering location or the gMSB of the metering location has received the charges for the services from the MSBA of the metering location.
## 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 MSBN](/en/prozessdoku/202610/MSB--MSBN/WiM-Teil1-abrechnung-von-dienstleistungen) — the receiving MSB · market role 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.* 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: [1](#schritt-1), [3](#schritt-3) 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) 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), [3](#schritt-3)