MSB (55 / 54)
E_0209 — Check termination
Check termination
| Attribute | Value |
|---|---|
| Designation | Check termination |
| Market role | MSB |
| Regulatory determination / chapter | WiM electricity |
| Section | 8.12.1: AD: Termination of invoice processing of metering point operation via LF by LF |
| Check identifiers | Response: 19009, 19010 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Does a contractual relationship for invoice processing via the LF exist? | no | A01 | Cluster: Rejection LF is not the payer of the metering point operation |
| — | — | yes | → Step 2 | — |
| 2 | Is the termination date after the cut-off date, which is calculated as follows: receipt date of the message - (6 weeks + 5 WT)? | no | A04 | Cluster: Rejection Deadline not met |
| — | — | yes | A02 | Cluster: Consent Consent |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | LF is not the payer for the metering point operation | 19010 |
A04 | Rejection | Deadline not met | 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 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 3 result codes of the decision tree are contained in the generated process E_0209.bpmn.