Contract termination — LFN view
The LFN sends a contract termination to the LFA. The LFA checks the contract termination and informs the LFN of the result.
Process flow from the perspective of the LF (LFN)
Process steps
Contract termination
LFN LFACheck identifiers
- 55016 — Contract termination · AS4
Flow
Prozessauslöser
START_KUENDIGUNGThe backend triggers this step with this event.
Message to LFA · 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 to contract termination
LFN LFAZ33Check identifiers
Flow
Message from LFA · AS4
Response per decision tree
55017,55018→ E_0614 · LF · Check contract termination
APERAK checks
55017,55018→Z33— APERAK check: Is referenced message known ?
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
Load data for processing
- Read balancing
GET /getAccountingBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read energy supply contract
GET /getEnergySupplyContractBasic
- Read balancing
Decision trees of this process
| EBD | Name |
|---|---|
| E_0614 | Check contract termination |
Process information
Wording of the consolidated version, profile ch. 1.2.1, pp. 7–8.
Preconditions
- In the case of a consuming market location: LFN holds the power of attorney of the final customer to issue the contract termination on their behalf.
- In the case of a generating market location or a tranche: LFN holds the power of attorney of the EZ to issue the contract termination on its behalf.
- The MaLo-ID of the market location is known or, in the case of a tranched market location, the MaLo-ID of the tranche is known.
Results
Immediately upon confirming the contract termination to the LFN, the LFA is also obliged to trigger the use case “End of supply from LF to NB” with the NB.
Error case
Result in the error case
- In the case of a consuming market location: The electricity supply contract concluded between the final customer and LFA for the named consuming market location has not been terminated.
- In the case of a generating market location or a tranche: the electricity purchase contract concluded between the EZ and LFA for the named generating market location or the named tranche has not been terminated.
- If required, the LFN sends a contract termination to the LFA again.
Error cases
- The LFA is not assigned to the market location or tranche specified by the LFN at the contract termination date.
- The contractual situation of LFA does not permit the requested contract termination of LFN.
Further requirements
- In the case of a consuming market location:
- A substitute supply is not a contractual relationship requiring termination; a contract termination is therefore not necessary (cf. § 38 para. 4 EnWG). If a LFN nevertheless sends the E/G a contract termination for the earliest possible point in time or for a fixed point in time in the future, the E/G consents to the contract termination provided there are no grounds for rejection.
- Notwithstanding the option available to the final customer at any time to terminate their electricity supply contract in writing, LFA may not reject a contract termination notified in accordance with this use case solely by invoking non-compliance with a contractually agreed form. In this case it must also accept and process a contract termination in electronic form using this use case.
- Note: The use case does not cover the case in which the final customer terminates the electricity supply contract with LFA themselves. If the final customer terminates in advance, LFA must initiate the use case “End of supply from LF to NB” towards NB immediately upon drafting the termination confirmation for the final customer.
- In the case of a generating market location or a tranche:
- Notwithstanding the option available to the EZ at any time to terminate its electricity purchase contract in writing, LFA may not reject a contract termination notified in accordance with this use case solely by invoking non-compliance with a contractually agreed form. In this case it must also accept and process a contract termination in electronic form using this use case.
- Note: the use case does not cover the case in which the EZ itself terminates the electricity purchase contract towards LFA. If the EZ terminates in advance itself, the use case „End of supply from LF to NB“ must be triggered by LFA towards NB immediately upon drafting the termination confirmation to the EZ.
- In the interest of a smooth switching process and in order to avoid subsequent clarification cases, it is advisable to generally precede a use case “Start of supply” with the use case “Contract termination”.
- In the case of a consuming market location:
Trigger
- In the case of a consuming market location: LFN receives the order from the final customer for the contract termination of the existing electricity supply contract.
- In the case of a generating market location or a tranche: LFN receives the order from the EZ for the contract termination of the existing electricity purchase contract.
Runs beforehand: Determination of the MaLo ID of the market location — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Contract termination“ to LFA (step 1).
Objective
- The electricity supply contract concluded between the final customer and the LFA for the named consuming market location has been terminated, or
- the electricity purchase contract concluded between EZ and LFA for the named generating market location or the named tranche has been terminated.
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 LFA — the transferring supplier · market role 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.
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.
Applies to: 1