# Billing of services in metering — NB view
## Process flow from the perspective of the NB
\nSystem diagram: Abrechnung von Dienstleistungen im Messwesen — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Rechnung\n(Messstellenbetrieb)\n\nMSBA\n\nMessage\n31003\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Antwort auf Rechnung\n(Messstellenbetrieb)\n\n\nMSBA\n\nMessage\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Rechnung für Zwischen-\noder Kontrollablesung\n\n\nMSBA\n\nMessage\n31003\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Antwort auf Rechnung\n\n\nMSBA\n\nMessage\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n7. Storno der ursprünglichen\nRechnung\n\n\nMSBA\n\nMessage\n31004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n8. Antwort auf Storno\n\n\nMSBA\n\nMessage\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={""} titel="NB" />
## Process steps
### Invoice (metering point operation)
**Write endpoint**
- Transaction created — [Create process data](/en/api/202604/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out
Creates a new transaction in the backend with the data of the incoming message.
### Response to invoice (metering point operation)
**Response per decision tree**
- `33002` → `E_2014`
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend once the message has been created.
### Invoice (device takeover)
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-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend with the data of the incoming message.
**Response per decision tree**
- `33002` → `E_2016`
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend once the message has been created.
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend with the data of the incoming message.
**Response per decision tree**
- `33002` → `E_2018`
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/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
This step runs between other market partners and is not relevant for this view.
**Response per decision tree**
- `33002` → `E_2019`
## Process information
### First message
**MSBA** sends “Invoice (metering point operation)” (step 1). 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 MSBN](/en/prozessdoku/202604/MSB--MSBN/awh-wim-gas-2-0-abrechnung-von-dienstleistungen-im-messwesen) — the receiving MSB · market role MSB
*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.
:::
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)
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: [5](#schritt-5), [7](#schritt-7)
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), [7](#schritt-7)
For these decision trees of the process there is no source in this format version:
- `E_2014`
- `E_2016`
- `E_2018`
- `E_2015`
- `E_2019`