# E_0552 — Check complaint
Check complaint
| Attribute | Value |
|---|---|
| Designation | Check complaint |
| Market role | MSB |
| Regulatory determination / chapter | GPKE |
| Section | 6.35.1: AD: Complaint about a configuration from NB to MSB |
| Check identifiers | Response: [19130](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19130) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0552: Reklamation prüfen\n\n\n\nE_0552\nReklamation prüfen\nChecking role: MSB\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\n\n20\nIst der Wirkungszeitraum bereits\neingetreten?\n\n\nA02\nCluster: Rejection\nWirkungszeitraum noch nicht\neingetreten\n\n\n30\nIst die Reklamation der\nKonfiguration berechtigt?\n\n\nA03\nCluster: Rejection\nReklamation unbegründet. Bestellte\nKonfiguration ist eingerichtet\n\n\n40\nKann die Konfiguration korrigiert\nwerden?\n\n\nA04\nCluster: Rejection\nKonfiguration kann trotz Bestellung\nnicht vorgenommen werden.\nHinweis: Das identifizierte Problem\nist in der Antwort zu\nbeschreiben/benennen\n\n\n50\nKann die Konfiguration sofort\nkorrigiert werden?\n\n\nA05\nCluster: Consent\nKonfiguration wurde sofort\nangepasst.\n\n\nA06\nCluster: Consent\nKonfiguration konnte nicht sofort\nkorrigiert werden.\nHinweis: Geplanter\nBehebungszeitpunkt muss\nangegeben werden.\n"} kapitel={"GPKE · 6.35.1: AD: Reklamation einer Konfiguration vom NB an MSB"} name={"Reklamation prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 20 | Has the effective period already begun? | no | A02 | Cluster: Rejection Effective period has not yet begun |
| — | — | yes | → Step 30 | — |
| 30 | Is the complaint about the configuration justified? | no | A03 | Cluster: Rejection Complaint unjustified. Ordered configuration has been set up |
| — | — | yes | → Step 40 | There is a deviation between the ordered and the set-up configuration. |
| 40 | Can the configuration be corrected? | no | A04 | Cluster: Rejection The configuration cannot be carried out despite the order placement. Note: The identified problem must be described/named in the response |
| — | — | yes | → Step 50 | . |
| 50 | Can the configuration be corrected immediately? | yes | A05 | Cluster: Consent Configuration was adjusted immediately. |
| — | — | no | A06 | Cluster: Consent Configuration could not be corrected immediately. Note: The planned time of remedy must be stated. |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A02` | Rejection | Effective period has not started yet |
| `A03` | Rejection | Complaint unjustified. Ordered configuration is set up |
| `A04` | Rejection | Configuration cannot be carried out despite the order placement. Note: The identified problem must be described/named in the response |
| `A05` | Consent | Configuration was adjusted immediately. |
| `A06` | Consent | Configuration could not be corrected immediately. Note: The planned point in time for the remedy must be stated. |
*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.*
:::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.
:::