# E_0512 — Check deregistration
Check deregistration
| Attribute | Value |
|---|---|
| Designation | Check deregistration |
| Market role | NB |
| Regulatory determination / chapter | On model 2 for the charging-session-specific balancing allocation of energy quantities |
| Section | 16.2.1: AD: Deregistration of a market location from model 2 by NB (LPB) |
| Check identifiers | Response: [55243](/en/schnittstellen/202610/pruefi/UTILMD/PI_55243) |
| EBD version | 4.3 |
| As at | — |
## Decision tree
\nDecision tree E_0512: Abmeldung prüfen\n\n\n\nE_0512\nAbmeldung prüfen\nChecking role: NB\n\nyes\n\nno\n\n\n1\nIst ein Fehler aufgetreten?\n\n\nA99\nCluster: Rejection\nSonstiges\nHinweis: Das identifizierte Problem\nist in der Antwort zu\nbeschreiben/benennen.\nNutzungsmöglichkeit Ende:\n01.04.2027, 00:00 Uhr\n\n\nA01\nCluster: Consent\nBestätigung der Abmeldung\n"} kapitel={"Zum Modell 2 zur ladevorgangscharfen bilanziellen Energiemengenzuordnungsmöglichkeit · 16.2.1: AD: Abmeldung einer Marktlokation aus dem Modell 2 durch den NB (LPB)"} name={"Abmeldung prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Has an 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 | A01 | Cluster: Consent Confirmation of the deregistration |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A99` | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027, 00:00 |
| `A01` | Consent | Confirmation of the deregistration |
*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.*
:::note{title="Not checked against a process"}
**No** consistency check was carried out for this decision tree — no generated BPMN found. Whether the MACO APP implements this tree completely is therefore not evidenced here.
:::