Billing of services in metering — MSBA view
Process flow from the perspective of the MSB (MSBA)
Process steps
Invoice (metering point operation)
MSBA NBCheck identifiers
- 31003 — WiM invoice
Flow
Load data for processing
- Read metering location
GET /getMeterLocationBasic LESEN_RECHNUNG_BASIS
- Read metering location
Message to NB
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
Response to invoice (metering point operation)
MSBA NBFlow
Message from NB
Response per decision tree
33002→E_2014
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
Invoice (device takeover)
MSBA MSBNCheck identifiers
- 31003 — WiM invoice
Flow
Load data for processing
- Read metering location
GET /getMeterLocationBasic LESEN_RECHNUNG_BASIS
- Read metering location
Message to MSBN
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
Response to invoice (device takeover)
MSBA MSBNFlow
Message from MSBN
Response per decision tree
33002→E_2015
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
Invoice for interim or control meter reading
MSBA NBCheck identifiers
- 31003 — WiM invoice
Flow
Load data for processing
- Read metering location
GET /getMeterLocationBasic LESEN_RECHNUNG_BASIS
- Read metering location
Message to NB
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
Response to invoice
MSBA NBFlow
Message from NB
Response per decision tree
33002→E_2016
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
Cancellation of the original invoice
MSBA NBCheck identifiers
- 31004 — Cancellation invoice
Flow
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_RECHNUNG_BASIS
- Read market location
Message to NB
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
Response to cancellation
MSBA NBFlow
Message from NB
Response per decision tree
33002→E_2018
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
Cancellation of the original invoice
MSBA MSBNCheck identifiers
- 31004 — Cancellation invoice
Flow
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_RECHNUNG_BASIS
- Read market location
Message to MSBN
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
Response to cancellation
MSBA MSBNFlow
Message from MSBN
Response per decision tree
33002→E_2019
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
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.
The source does not yet name the event that triggers these steps.
Applies to: 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.
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.
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.
For these decision trees of the process there is no source in this format version:
E_2014E_2015E_2016E_2018E_2019