NB (69)
E_0607 — Check deregistration
Check deregistration
| Attribute | Value |
|---|---|
| Designation | Check deregistration |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.3.1: AD: End of supply from LF to NB |
| Check identifiers | checked: 55004 · response: 55005, 55006 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Was it stated in the business transaction that this is a consuming market location or a dormant market location? | yes | → Step 20 | — |
| — | — | no | → Step 500 | — |
| 20 | Is this the deregistration of a market location that is to be separated out of a customer installation? Note: The transaction reason supplement states „dormant market location“ | yes | → Step 30 | — |
| — | — | no | → Step 50 | — |
| 30 | Is the market location named in the use case a „dormant market location“ of a customer installation (§ 20 para. 1d EnWG or § 10c EEG)? | no | A01 | Cluster: Rejection The market location named in the deregistration is not a customer installation. |
| — | — | yes | → Step 50 | — |
| 50 | Was the lead time met? | no | A02 | Cluster: Rejection Lead time not met |
| — | — | yes | → Step 60 | — |
| 60 | Is the transaction reason cancellation of a future assignment due to cancelled contractual relationship present? | yes | → step 90 | — |
| — | — | no | → Step 70 | Note: One of the following transaction reasons applies: move-in/move-out (relocation) move-out due to decommissioning end of the ESV without subsequent supply cancellation of a future assignment due to move-out of the customer cancellation of a future assignment due to decommissioning end due to contract termination by LF end due to contract termination by customer/LFN |
| 70 | Is the transaction reason end of ESV without subsequent supply present? | yes | → Step 80 | — |
| — | — | no | → Step 100 | Note: One of the following transaction reasons applies: move-in/move-out (relocation) move-out due to decommissioning cancellation of a future assignment due to move-out of the customer cancellation of a future assignment due to decommissioning end due to contract termination by LF end due to contract termination by customer/LFN |
| 80 | Was there a confirmed registration for replacement supply / default supply at this market location with a start of supply date that began within 3 months of the end date of supply from this deregistration? Note: An end of supply with the reason „End of the ESV without subsequent supply“ can only occur if this market location was also registered by the NB with the LF within the last 3 months via the use case „Start of replacement supply / default supply“. | no | A05 | Cluster: Rejection The market location was not registered for substitute / basic supply within the last 3 months. It can therefore not be a termination of a ESV. |
| — | — | yes | → Step 100 | — |
| 90 | Is the cancellation of a future assignment made for the same point in time that was confirmed to the supplier in the start of supply? | no | A06 | Cluster: Rejection The cancellation of a future assignment must be stated for the same point in time as confirmed in the start of supply. |
| — | — | yes | → Step 100 | — |
| 100 | Has the assignment of the requesting supplier to the market location for the identical deregistration date already been ended by a confirmation in the following process steps? Case: SD: end of supply from LF to NB, process step 2 " End of the assignment of the LF to the market location or tranche " SD: end of supply from NB to LF, process step 2 " Response to announcement of the end of the assignment of the LF to the market location or tranche " SD: start of supply, process step 4 " Response to request for ending the assignment of the LFA to the market location or tranche " or the confirmation results from the expiry of the deadline | yes | → Step 110 | — |
| — | — | no | → Step 140 | — |
| 110 | Is the requesting LF still assigned to the market location on the day after the deregistration date? | yes | → Step 140 | — |
| — | — | no | → Step 120 | — |
| 120 | Is there a transaction reason indicating that the connection user has moved out? This is the case for the following transaction reasons: move-in/move-out (relocation) move-out due to decommissioning | no | A09 | Cluster: Rejection End of supply as of the deregistration date has already been confirmed. |
| — | — | yes | → Step 130 | — |
| 130 | Does the already confirmed deregistration contain a transaction reason that does not indicate that the connection user has moved out? This is the case for the following transaction reasons: end due to contract termination by LF end due to contract termination by customer/LFN end of ESV without subsequent supply cancellation of a future assignment due to cancelled contractual relationship deregistration due to missing allocation authorization deregistration due to missing allocation authorization owing to change of ZRT | no | A10 | Cluster: Rejection End of supply as of the deregistration date has already been confirmed for the same reason. |
| — | — | yes | → Step 140 | — |
| 140 | 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.10.2026 00:00 |
| — | — | no | A11 | Cluster: Consent Confirmation of the deregistration |
| 500 | Is the specified date “End of supply” the 1st of a calendar month 00:00? | no | A21 | Cluster: Rejection The end of supply must fall on the 1st of a calendar month at 00:00. |
| — | — | yes | → Step 520 | — |
| 520 | Is the deregistration available at least one month before the allocation end? | no | A22 | Cluster: Rejection Lead time not met |
| — | — | yes | → Step 530 | — |
| 530 | Is this a tranche? | yes | → Step 540 | — |
| — | — | no | → Step 560 | — |
| 540 | Is this a tranche subject to mandatory direct marketing? | yes | → Step 550 | — |
| — | — | no | → Step 560 | — |
| 550 | Is there a simultaneous deregistration of the further tranches? | yes | → Step 560 | — |
| — | — | no | → Step 560 | Note: Check of the 100% assignment last WT at the end of the month before the allocation start |
| 560 | Is the transaction reason cancellation of a future assignment due to cancelled contractual relationship present? | yes | → Step 570 | — |
| — | — | no | → Step 580 | Note: One of the following transaction reasons applies: move-out due to decommissioning cancellation of a future assignment due to decommissioning end due to contract termination by LF end due to contract termination by customer/LFN |
| 570 | Is the cancellation of a future assignment made for the same date (point in time) that was confirmed to the supplier in the start of supply? | no | A23 | Cluster: Rejection The cancellation of a future assignment must be stated for the same point in time as confirmed in the start of supply. |
| — | — | yes | → Step 580 | — |
| 580 | Has the assignment of the requesting supplier to the market location for the identical deregistration date already been ended by a confirmation in the following process steps? Case: SD: end of supply from LF to NB, process step 2 " End of the assignment of the LF to the market location or tranche " SD: end of supply from NB to LF, process step 2 " Response to announcement of the end of the assignment of the LF to the market location or tranche " SD: start of supply, process step 4 " Response to request for ending the assignment of the LFA to the market location or tranche " or the confirmation results from the expiry of the deadline | yes | → Step 590 | — |
| — | — | no | → Step 620 | — |
| 590 | Is the requesting LF still assigned to the market location on the day after the deregistration date? | yes | → Step 600 | — |
| — | — | no | → Step 610 | — |
| 600 | Is the transaction reason “move-out due to decommissioning” present? | no | A25 | Cluster: Rejection End of supply as of the deregistration date has already been confirmed for the same reason. |
| — | — | yes | → Step 610 | — |
| 610 | Does the already confirmed deregistration contain a transaction reason that does not indicate that the connection user has moved out? This is the case for the following transaction reasons: end due to contract termination by LF end due to contract termination by customer/LFN cancellation of a future assignment due to cancelled contractual relationship deregistration due to missing allocation authorization deregistration due to missing allocation authorization owing to change of ZRT | no | A26 | Cluster: Rejection End of supply as of the deregistration date has already been confirmed for the same reason. |
| — | — | yes | → Step 620 | — |
| 620 | 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.10.2026 00:00 |
| — | — | no | A27 | Cluster: Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | The market location named in the deregistration is not a customer installation. | 55006 |
A02 | Rejection | Lead time not met | 55006 |
A05 | Rejection | The market location was not registered for substitute/basic supply within the last 3 months. It can therefore not be the termination of a ESV. | 55006 |
A06 | Rejection | The cancellation of a future assignment must be specified for the same point in time as confirmed in the start of supply. | 55006 |
A09 | Rejection | End of supply as at the deregistration date has already been confirmed. | 55006 |
A10 | Rejection | End of supply as at the deregistration date has already been confirmed for the same reason. | 55006 |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 | 55006 |
A11 | Consent | Confirmation of the deregistration | 55005 |
A21 | Rejection | The end of supply must fall on the 1st of a calendar month at 00:00. | 55006 |
A22 | Rejection | Lead time not met | 55006 |
A23 | Rejection | The cancellation of a future assignment must be specified for the same point in time as confirmed in the start of supply. | 55006 |
A25 | Rejection | End of supply as at the deregistration date has already been confirmed for the same reason. | 55006 |
A26 | Rejection | End of supply as at the deregistration date has already been confirmed for the same reason. | 55006 |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 | 55006 |
A27 | Consent | — | 55005 |
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 14 result codes of the decision tree are contained in the generated process E_0607.bpmn.