LF (54)
E_0206 — Check termination
Check termination
| Attribute | Value |
|---|---|
| Designation | Check termination |
| Market role | LF |
| Regulatory determination / chapter | MaBiS |
| Section | 7.79.1: AD: Termination of invoice processing of metering point operation via LF by MSB |
| Check identifiers | checked: 17006 · response: 19009, 19010 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Does a contractual relationship for invoice processing via the LF exist? | no | A01 | Cluster: Rejection No agreement on the billing of MSB via the LF |
| — | — | yes | A02 | Cluster: Consent Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | No agreement on the billing of MSB via the LF | 19010 |
A02 | Consent | Consent | 19009 |
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 202610); »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.
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.