LF (54)
E_0624 — Check request for termination of the assignment
Check request for termination of the assignment
| Attribute | Value |
|---|---|
| Designation | Check request for termination of the assignment |
| Market role | LF |
| Regulatory determination / chapter | GPKE |
| Section | 6.6.3: AD: Start of supply |
| Check identifiers | checked: 55010 · response: 55011, 55012 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 5 | Was the request received between the ÜT of the supply registration and 07:00 on the next working day? | no | A43 | Cluster: Rejection Deadline exceeded |
| — | — | yes | → Step 10 | — |
| 10 | Was the use case used for a consuming market location? | no | → Step 200 | — |
| — | — | yes | → Step 20 | — |
| 20 | Does an assignment for this market location exist on the day following the date named in the request to end the assignment? Note: If the customer is in the E/G, this question is likewise to be answered with yes | yes | → Step 40 | — |
| — | — | no | → Step 30 | — |
| 30 | Does LFA already have a confirmed allocation end? | yes | A30 | Cluster: Rejection Supply has already been ended on the date requested in the request to terminate the assignment, and a deregistration has already been sent by the LFA which has already been confirmed by the NB. |
| — | — | no | A31 | Cluster: Consent Consent to the request for termination of the assignment as of the date named in the deregistration already sent (which has not yet been answered). |
| 40 | Does the request for the termination of the assignment contain the transaction reason move-in/ move-out (relocation)? | no | → Step 70 | — |
| — | — | yes | → Step 50 | — |
| 50 | Is the customer from the request to end the assignment identical to the customer at the LFA? | yes | A32 | Cluster: Rejection This is not a move-in, since the customer from the request to terminate the assignment is identical to the customer at the LFA. |
| — | — | no | → Step 60 | — |
| 60 | Does the LFA have information that its customer has not moved out? | yes | A33 | Cluster: Rejection The LFA has the information that the customer has not moved out. |
| — | — | no | A34 | Cluster: Consent The LFA ends the supply and states its end of supply date in the response. |
| 70 | Is the LFA a supplier that is also a default supplier? | no | → step 90 | — |
| — | — | yes | → Step 80 | — |
| 80 | Is the market location in replacement supply on the day following the end date from the request for termination of the assignment? | no | → step 90 | — |
| — | — | yes | A38 | Cluster: Consent Substitute supply was ended as of the requested date. |
| 90 | Does the contractual relationship of the LFA with the customer at this market location / tranches continue to exist on the day after the end date from the request to terminate the assignment? | yes | A35 | Cluster: Rejection A contractual commitment exists |
| — | — | no | A36 | Cluster: Consent The contractual relationship was ended as of the requested date or an earlier date. |
| 200 | Does an assignment for this market location / tranche exist on the day following the date named in the request to end the assignment? | yes | → Step 220 | — |
| — | — | no | → Step 210 | — |
| 210 | Does LFA already have a confirmed allocation end? | yes | A41 | Cluster: Rejection Supply has already been ended on the date requested in the request to terminate the assignment, and a deregistration has already been sent by the LFA which has already been confirmed by the NB. |
| — | — | no | A42 | Cluster: Consent Consent to the request for termination of the assignment as of the date named in the deregistration already sent (which has not yet been answered). |
| 220 | Does the contractual relationship of the LFA with the customer at this market location / tranche continue to exist on the day after the end date from the request to terminate the assignment? | yes | A39 | Cluster: Rejection A contractual commitment exists |
| — | — | no | A40 | Cluster: Consent The contractual relationship was ended as of the requested date or an earlier date. |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A43 | Rejection | Deadline exceeded | 55012 |
A30 | Rejection | The supply has already been ended on the date requested in the request to end the assignment, and a deregistration has already been sent by the LFA, which has already been confirmed by the NB. | 55012 |
A31 | Consent | Consent to the request to end the assignment as of the date specified in the deregistration already sent (which has not yet been responded to). | 55011 |
A32 | Rejection | This is not a move-in, because the customer from the request to terminate the assignment is identical to the customer at the LFA. | 55012 |
A33 | Rejection | The LFA has the information that the customer has not moved out. | 55012 |
A34 | Consent | The LFA ends the supply and states its end-of-supply date in the response. | 55011 |
A38 | Consent | Substitute supply was terminated on the requested date. | 55011 |
A35 | Rejection | A contractual commitment exists | 55012 |
A36 | Consent | Contractual relationship was terminated as of the requested date or earlier. | 55011 |
A41 | Rejection | The supply has already been ended on the date requested in the request to end the assignment, and a deregistration has already been sent by the LFA, which has already been confirmed by the NB. | 55012 |
A42 | Consent | Consent to the request to end the assignment as of the date specified in the deregistration already sent (which has not yet been responded to). | 55011 |
A39 | Rejection | A contractual commitment exists | 55012 |
A40 | Consent | Contractual relationship was terminated as of the requested date or earlier. | 55011 |
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 202604); »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 13 result codes of the decision tree are contained in the generated process E_0624.bpmn.