Billing of services — MSBA view
The process describes the billing of the charges for:
- the temporary continuation of the metering point operation
- the device takeover (transfer of use by lease or rent)
- the device takeover (purchase) or
- Additional or control readings. MSBN of the metering location or gMSB of the metering location checks the invoice (e.g. for reference to the correct metering location and to the applicable time period of the metering point operation). If the check is positive, a confirmation of the payment must be communicated. Confirmations relating to several invoices must be combined. If the check is negative (case of complaint), the so-called “all-or-nothing principle” applies, under which a single invoice within an invoice file that may contain several invoices is either accepted as correct in full or rejected in full. An invoice correction always comprises a cancellation invoice and a new invoice. Both the cancelled invoice(s) and the re-billed invoice(s) are combined into one file. A rejection of the payment must be substantiated. Rejections relating to several invoices must be combined. The processes to be handled in the event of a conflict as part of receivables management or the dunning procedure are not described here. Likewise, the mapping of the onward billing to the AN or ANN is not described.
Process flow from the perspective of the MSB (MSBA)
Process steps
Invoice (metering point operation / device takeover)
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)Check identifiers
- 31003 — WiM invoice · AS4
Flow
Load data for processing
- Read metering location
GET /getMeterLocationBasic LESEN_RECHNUNG_BASIS
- Read metering location
Message to MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object) · 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 (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)Check identifiers
Flow
Message from MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object) · AS4
Response per decision tree
33003,33004→ E_0259 · MSB · Process invoice
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 (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)Check identifiers
- 31004 — Cancellation invoice · AS4
Flow
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_RECHNUNG_BASIS
- Read market location
Message to MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object) · 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 (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object)Flow
Message from MSB (corresponds to MSBN at the metering location object or gMSB at the metering location object) · AS4
Response per decision tree
33002→ E_0261 · MSB · Process cancellation
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
Wording of the consolidated version, profile ch. 3.7.1, pp. 79–80.
Preconditions
A valid agreement on the billing of the billing object exists between the MSB.
Results
The invoice for the device or for the special meter reading has been paid.
Error case
Result in the error case
The invoice for the device or the special meter reading has not been paid.
Error cases
The MSBN of the metering location or the gMSB of the metering location has received an incorrect invoice.
First message
The party involved on this page is itself the sender of: „Invoice (metering point operation / device takeover)“ to MSB (corresponds to MSBN on the metering location object or gMSB on the metering location object) (step 1).
Objective
The MSBN of the metering location or the gMSB of the metering location has received the charges for the services from the MSBA of the metering location.
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 MSBN — the receiving MSB · market role 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 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.