Billing of services of price sheet A of the MSB between MSB and LF — MSB view
The process describes the communication between MSB and NB or LF on the billing of services in price sheet A of the MSB 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 MSB
Process steps
Invoice
MSB LFCheck identifiers
- 31009 — MSB invoice · AS4
Flow
Message to LF · AS4
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
MSB LFZ33Check identifiers
Flow
Message from LF · AS4
Response per decision tree
33003,33004→ E_0519 · LF · Check invoice for the services of price sheet A
APERAK checks
33001,33003,33004→Z33
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
Notification that the original invoice was correct
MSB LFCheck identifiers
- 29001 — Rejection of REMADV · AS4
Flow
Message to LF · AS4
Response per decision tree
29001→ E_0520 · MSB · Check non-payment advice
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
MSB LFZ33Check identifiers
Flow
Message from LF · AS4
Response per decision tree
33003,33004→ E_0521 · LF · Check invoice for the services of price sheet A again
APERAK checks
33001,33003,33004→Z33
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
MSB LFCheck identifiers
- 31004 — Cancellation invoice · AS4
Flow
Prozessauslöser
START_VERSAND_RECHNUNGThe backend triggers this step with this event.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_RECHNUNG_BASIS
- Read market location
Message to LF · AS4
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
MSB LFZ33Flow
Message from LF · AS4
Response per decision tree
33002→ E_0522 · LF · Check whether a response to the cancellation is required
APERAK checks
33001,33002→Z33
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0519 | Check invoice for the services of price sheet A |
| E_0520 | Check non-payment advice |
| E_0521 | Check invoice for the services of price sheet A again |
| E_0522 | Check whether a response to the cancellation is required |
Process information
Wording of the consolidated version, profile ch. 3.5.1, pp. 95–96.
Preconditions
- The current fees of price sheet A of MSB have been transmitted by MSB to NB or LF within the use case „Transmission of price sheet A of MSB from MSB to NB and LF“.
- The article IDs relevant for the billing are listed in price sheet A of MSB.
- Towards NB the following applies: NB has, via the
- Use case “Order placement of a configuration from NB or LF to MSB” a chargeable configuration was ordered and the order placement was confirmed by MSB or
- Use case “Control command from NB or LF to MSB” instructed a chargeable control command and the instruction was confirmed by MSB. Note: if price sheet A of MSB states criteria for the instructed control command specifying when the control command is chargeable, these criteria must also be met.
- Towards LF the following applies: LF has, via the
- Use case “Order placement of a configuration from NB or LF to MSB” a chargeable configuration was ordered and the order placement was confirmed by MSB or
- Use case “Control command from NB or LF to MSB” ordered a chargeable control command and the order placement was confirmed by MSB. Note: if price sheet A of MSB states criteria for the ordered control command specifying when the control command is chargeable, these criteria must also be met.
Results
The NB or LF will pay the invoice issued by the MSB.
Error case
Error cases
- The invoice contains items that are not included as an article ID in price sheet A of the MSB.
- The price of an article ID stated in the invoice does not match the price of the corresponding article ID stated in price sheet A of 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 NB or LF or on the basis of a prior complaint by the NB or LF) 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
- The billing of one or more services from the MSB for the NB or LF is due.
First message
The party involved on this page is itself the sender of: „Invoice“ to LF (step 1).
Objective
The MSB has been informed that the NB or LF 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 LF — LF
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 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.
Applies to: 5
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.