LF (54)
E_0615 — Check registration E/G
Check registration E/G
| Attribute | Value |
|---|---|
| Designation | Check registration E/G |
| Market role | LF |
| Regulatory determination / chapter | GPKE |
| Section | 6.7.1: AD: Start of replacement supply / default supply |
| Check identifiers | checked: 55013 · response: 55014, 55015 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 20 | Is the market location in the recipient's basic supply area, or does a contractual agreement on replacement supply exist for the market location? | no | A02 | Cluster: Rejection No responsibility |
| — | — | yes | → Step 40 | — |
| 40 | Has the requested business transaction already been confirmed to the requesting party for the same point in time with an earlier notification? | yes | A04 | Cluster: Rejection Duplicate notification |
| — | — | no | → Step 50 | — |
| 50 | Is there a statutory obligation to provide basic or substitute supply, or a contractual obligation to provide replacement supply or transitional supply? | no | A05 | Cluster: Rejection no case of basic/default supply, no case of replacement supply and no case of transitional supply. |
| — | — | yes | → step 90 | — |
| 90 | 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 | A09 | Cluster: Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A02 | Rejection | Not responsible | 55015 |
A04 | Rejection | Duplicate notification | 55015 |
A05 | Rejection | no basic/default supply case, no substitute supply case and no transitional supply case. | 55015 |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.10.2026 00:00 | 55015 |
A09 | Consent | — | 55014 |
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 5 result codes of the decision tree are contained in the generated process E_0615.bpmn.