# Billing of services in metering — MSBN view
## Process flow from the perspective of the MSB (MSBN)
\nSystem diagram: Abrechnung von Dienstleistungen im Messwesen — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSBN\n\nMarket partner\n\n\n\n3. Rechnung\n(Geräteübernahme)\n\nMSBA\n\nMessage\n31003\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n4. Antwort auf Rechnung\n(Geräteübernahme)\n\n\nMSBA\n\nMessage\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n9. Storno der ursprünglichen\nRechnung\n\n\nMSBA\n\nMessage\n31004\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\n10. Antwort auf Storno\n\n\nMSBA\n\nMessage\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={""} titel="MSBN" />
## Process steps
### Invoice (metering point operation)
This step runs between other market partners and is not relevant for this view.
**Write endpoint**
- Transaction created — [Create process data](/en/api/202604/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out
Creates a new transaction in the backend with the data of the incoming message.
**Load data for processing**
- [Read metering location](/en/api/202604/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it
- `LESEN_RECHNUNG_BASIS`
**Response per decision tree**
- `33002` → `E_2015`
**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.
### Invoice for interim or control meter reading
This step runs between other market partners and is not relevant for this view.
**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.
**Load data for processing**
- [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
- `LESEN_RECHNUNG_BASIS`
**Response per decision tree**
- `33002` → `E_2019`
**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.
## Process information
### First message
**MSBA** sends “Invoice (device takeover)” (step 3). 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 MSBA](/en/prozessdoku/202604/MSB--MSBA/awh-wim-gas-2-0-abrechnung-von-dienstleistungen-im-messwesen) — the transferring MSB · market role MSB
- [View NB](/en/prozessdoku/202604/NB/awh-wim-gas-2-0-abrechnung-von-dienstleistungen-im-messwesen) — 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.
:::
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: [3](#schritt-3), [9](#schritt-9)
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: [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: [9](#schritt-9)
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: [3](#schritt-3), [9](#schritt-9)
For these decision trees of the process there is no source in this format version:
- `E_2015`
- `E_2019`
- `E_2014`
- `E_2016`
- `E_2018`