Billing of services in metering — MSBN view
Process flow from the perspective of the MSB (MSBN)
Process steps
1 Invoice (metering point operation)
MSBA NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 31003 — WiM invoice
Invoice (device takeover)
MSBN MSBACheck identifiers
- 31003 — WiM invoice
Flow
Message from MSBA
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Load data for processing
- Read metering location
GET /getMeterLocationBasic LESEN_RECHNUNG_BASIS
- Read metering location
Response to invoice (device takeover)
MSBN MSBAFlow
Message to MSBA
Response per decision tree
33002→ E_2015 · Process invoice
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
5 Invoice for interim or control meter reading
MSBA NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 31003 — WiM invoice
7 Cancellation of the original invoice
MSBA NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 31004 — Cancellation invoice
Cancellation of the original invoice
MSBN MSBACheck identifiers
- 31004 — Cancellation invoice
Flow
Message from MSBA
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_RECHNUNG_BASIS
- Read market location
Response to cancellation
MSBN MSBAFlow
Message to MSBA
Response per decision tree
33002→ E_2019 · Process cancellation
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_2015 | Process invoice |
| E_2019 | Process cancellation |
| E_2014 | Process invoice |
| E_2016 | Process invoice |
| E_2018 | Process cancellation |
Process information
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.
Notes on this page
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.
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.
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
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
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.