LF (54)
E_0614 — Check contract termination
Check contract termination of the contract
| Attribute | Value |
|---|---|
| Designation | Check contract termination |
| Market role | LF |
| Regulatory determination / chapter | GPKE |
| Section | 6.2.1: AD: Contract termination |
| Check identifiers | checked: 55016 · response: 55017, 55018 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Was it stated in the business transaction that this is a consuming market location? | yes | → Step 20 | — |
| — | — | no | → Step 500 | — |
| 20 | Is the transmitted contract termination date before the message receipt? | yes | A01 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 40 | — |
| 40 | Has the contract already been terminated as of the requested termination date? | yes | A03 | Cluster: Consent The contract was already terminated as of the requested termination date. |
| — | — | no | → Step 50 | — |
| 50 | Has the contract already been terminated as of a date before the requested termination date? | yes | A04 | Cluster: Rejection No contractual relationship exists any longer as at the termination date. |
| — | — | no | → Step 60 | — |
| 60 | Is this a contract termination declared for a fixed date? | yes | → Step 70 | — |
| — | — | no | → step 90 | — |
| 70 | Can the contract be terminated on the transmitted termination date, observing the notice period and taking the receipt date of the contract termination into account? | yes | → step 90 | — |
| — | — | no | → Step 80 | — |
| 80 | Has the contract already been ended at a later point in time? | yes | A05 | Cluster: Rejection Contractual commitment where the contract has already been terminated with future effect. |
| — | — | no | A06 | Cluster: Rejection Contractual commitment |
| 90 | Was a power of attorney requested from the LFA for the contract termination? | no | → Step 120 | — |
| — | — | yes | → Step 100 | Note: The request for a power of attorney in a justified individual case is to be sent bilaterally to the LFA. The email address from the „SG4 NAD+Z12 contact person termination process“ of the communication data sheet of the LFN is to be used for this purpose. The response of the LFN is sent to the email address from the „SG4 NAD+Z12 contact person termination process“ of the communication data sheet of the LFA. |
| 100 | Has the power of attorney been received by the LFA? | yes | → Step 110 | — |
| — | — | no | → Step 100 | Note: As long as the power of attorney has not arrived at the LFA, the process waits at this check step. This check is to be carried out again at regular intervals until the power of attorney has arrived. |
| 110 | Does the LFA consider the power of attorney to be effective? | yes | → Step 120 | — |
| — | — | no | A08 | Cluster: Rejection The power of attorney submitted by the LFN is regarded as not effective by the LFA. Note: The LFA substantiates the rejection due to the lack of effectiveness of the power of attorney |
| 120 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | A09 | Cluster: Consent Consent |
| 500 | Is there a contract for the specified object? | no | A18 | Cluster: Rejection There is no contract for the object named. |
| — | — | yes | → Step 505 | — |
| 505 | Is the transmitted contract termination date before the message receipt? | yes | A10 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 550 | — |
| 550 | Has the contract already been terminated as of the requested termination date? | yes | A12 | Cluster: Consent The contract was already terminated as of the requested termination date. |
| — | — | no | → Step 560 | — |
| 560 | Has the contract already been terminated as of a date before the requested termination date? | yes | A13 | Cluster: Rejection No contractual relationship exists any longer as at the termination date. |
| — | — | no | → Step 570 | — |
| 570 | Is this a contract termination declared for a fixed date? | yes | → Step 580 | — |
| — | — | no | → Step 600 | — |
| 580 | Can the contract be terminated on the transmitted termination date, observing the notice period and taking the receipt date of the contract termination into account? | yes | → Step 600 | — |
| — | — | no | → Step 590 | — |
| 590 | Has the contract already been ended at a later point in time? | yes | A14 | Cluster: Rejection Contractual commitment where the contract has already been terminated with future effect. |
| — | — | no | A15 | Cluster: Rejection Contractual commitment |
| 600 | Was a power of attorney requested from the LFA for the contract termination? | no | → Step 630 | — |
| — | — | yes | → Step 610 | Note: The request for a power of attorney in a justified individual case is to be sent bilaterally to the LFA. The email address from the „SG4 NAD+Z12 contact person termination process“ of the communication data sheet of the LFN is to be used for this purpose. The response of the LFN is sent to the email address from the „SG4 NAD+Z12 contact person termination process“ of the communication data sheet of the LFA. |
| 610 | Has the power of attorney been received by the LFA? | yes | → Step 620 | — |
| — | — | no | → Step 610 | Note: As long as the power of attorney has not arrived at the LFA, the process waits at this check step. This check is to be carried out again at regular intervals until the power of attorney has arrived. |
| 620 | Does the LFA consider the power of attorney to be effective? | yes | → Step 630 | — |
| — | — | no | A16 | Cluster: Rejection The power of attorney submitted by the LFN is regarded as not effective by the LFA. Note: The LFA substantiates the rejection due to the lack of effectiveness of the power of attorney |
| 630 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | A17 | Cluster: Consent Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | Deadline exceeded | 55018 |
A03 | Consent | Contract has already been terminated as of the requested termination date. | 55017 |
A04 | Rejection | No contractual relationship exists any longer as of the termination date. | 55018 |
A05 | Rejection | Contractual commitment where the contract has already been terminated with future effect. | 55018 |
A06 | Rejection | Contractual commitment | 55018 |
A08 | Rejection | The power of attorney submitted by the LFN is regarded as not effective by the LFA. Note: The LFA gives reasons for the rejection due to the lack of effectiveness of the power of attorney | 55018 |
A99 (2 outputs) | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027 00:00 | 55018 |
A09 | Consent | Consent | 55017 |
A18 | Rejection | No contract exists for the specified object. | 55018 |
A10 | Rejection | Deadline exceeded | 55018 |
A12 | Consent | Contract has already been terminated as of the requested termination date. | 55017 |
A13 | Rejection | No contractual relationship exists any longer as of the termination date. | 55018 |
A14 | Rejection | Contractual commitment where the contract has already been terminated with future effect. | 55018 |
A15 | Rejection | Contractual commitment | 55018 |
A16 | Rejection | The power of attorney submitted by the LFN is regarded as not effective by the LFA. Note: The LFA gives reasons for the rejection due to the lack of effectiveness of the power of attorney | 55018 |
A17 | Consent | Consent | 55017 |
Notes on this page
Role of the numbers: »response« are the check identifiers that list this tree in the ebd_code column of the check identifier table (knowledge-collection · FV 202610); »checked« is the difference set to it from the return path of the process steps. The »response check identifier« column of the result codes assigns a cluster only because this tree carries exactly one checked message and exactly one response per pole; their pole comes from the use case title of the response.
Consistent with the generated process
All 16 result codes of the decision tree are contained in the generated process E_0614.bpmn.