Billing of services of price sheet B of the MSB between MSB and NB — NB view
Process flow from the perspective of the NB
Process steps
Invoice
NB MSBCheck identifiers
- 31009 — MSB invoice · AS4
Flow
Message from MSB · AS4
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
Response
NB MSBCheck identifiers
Flow
Message to MSB · AS4
Response per decision tree
33003,33004→ E_0273 · NB · Check invoice for a service of price sheet B of the MSB
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
Notification that the original response was correct
NB MSBCheck identifiers
- 29001 — Rejection of REMADV · AS4
Flow
Message from MSB · AS4
Response per decision tree
29001→ E_0274 · MSB · Check non-payment advice
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
Response
NB MSBCheck identifiers
Flow
Message to MSB · AS4
Response per decision tree
33003,33004→ E_0277 · NB · Check invoice for a service of price sheet B of the MSB again
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
Cancellation of the original invoice
NB MSBCheck identifiers
- 31004 — Cancellation invoice · AS4
Flow
Message from MSB · AS4
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
Response
NB MSBFlow
Message to MSB · AS4
Response per decision tree
33002→ E_0275 · NB · Check whether a response to the cancellation is required
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_0273 | Check invoice for a service of price sheet B of the MSB |
| E_0274 | Check non-payment advice |
| E_0275 | Check whether a response to the cancellation is required |
| E_0277 | Check invoice for a service of price sheet B of the MSB again |
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.
- View MSB — MSB
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 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
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.