Billing of a service rendered for the ESA — ESA view
The process describes the communication between MSB and ESA on the billing of a service rendered for the ESA and, where applicable, the automated complaint case. An invoice correction always comprises a cancellation invoice and a new invoice.
Process flow from the perspective of the ESA
Process steps
Invoice for a service provided for the ESA
ESA MSBCheck identifiers
- 31009 — MSB invoice · AS4
Flow
Message from MSB · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Response
ESA MSBCheck identifiers
Flow
Message to MSB · AS4
Response per decision tree
33003,33004→E_0264
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Notification that the original invoice was correct
ESA MSBCheck identifiers
- 29001 — Rejection of REMADV · AS4
Flow
Message from MSB · AS4
Response per decision tree
29001→E_0265
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Response
ESA MSBCheck identifiers
Flow
Message to MSB · AS4
Response per decision tree
33003,33004→ E_0266 · ESA · Check invoice for a service rendered for the ESA again
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Cancellation of the original invoice
ESA MSBCheck identifiers
- 31004 — Cancellation invoice · AS4
Flow
Message from MSB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Response
ESA MSBFlow
Message to MSB · AS4
Response per decision tree
33002→ E_0267 · ESA · Check whether a response to the cancellation is required
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0266 | Check invoice for a service rendered for the ESA again |
| E_0267 | Check whether a response to the cancellation is required |
Process information
Wording of the consolidated version, profile ch. 4.5.1, pp. 77–78.
Preconditions
- The ESA has ordered a transmission of values via the use case „Request and order placement of values by the ESA“.
Results
The ESA will pay the invoice for the MSB issued by the MSB.
Further requirements
- The case of an invoice of the MSB that has been complained about or turns out to be incorrect (the cancellation of the original invoice is carried out either without a prior complaint by the ESA or on the basis of a prior complaint by the ESA) forms part of the standard process and, apart from clarifications, must be handled fully automatically. In the event of a complaint, the so-called “all-or-nothing principle” applies, according to which an invoice is either accepted in full as correct or rejected in full. The processes to be handled in the event of a conflict as part of receivables management or the dunning procedure are not shown and are to be resolved bilaterally.
- An invoice references the underlying order placement.
Trigger
- Costs for device parameterisation have been incurred or
- the billing of the transmission of values is due.
Runs beforehand: Termination of the transmission of values to ESA by ESA, Termination of the transmission of values to ESA by MSB, Transmission of values from MSB to ESA — these processes name the one shown here in their result.
First message
MSB sends “Invoice for a service rendered for the ESA” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The MSB has been informed that the ESA accepts the invoice.
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 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.
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 this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button.
For these decision trees of the process there is no source in this format version:
E_0264E_0265