LF (54)
E_0093 — Check LF-AASZR
Check LF-AASZR
| Attribute | Value |
|---|---|
| Designation | Check LF-AASZR |
| Market role | LF |
| Regulatory determination / chapter | MaBiS |
| Section | 7.55.1: AD: Transmission of the supplier substitute energy sum time series |
| Check identifiers | Response: 21000 |
| EBD version | 4.2 |
| As at | 2026-06-23 |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the time series received after expiry of the clearing deadline for the KBKA? | yes | A01 | Cluster: Refusal Deadline exceeded |
| — | — | no | → Step 2 | — |
| 2 | Is the MaBiS-ZP active in the balancing month under consideration? | no | A02 | Cluster: Refusal Selected time period not permitted |
| — | — | yes | → Step 3 | — |
| 3 | Does the version of the time series of MaBiS-ZP for this balancing month and MaBiS-ZP already exist? | yes | A03 | Cluster: Refusal Time series already exists |
| — | — | no | → Step 4 | — |
| 4 | Is the version of the time series of the MaBiS-ZP higher than the highest version of the time series processed so far for this balancing month and this MaBiS-ZP? | no | A04 | Cluster: Refusal Version not permitted |
| — | — | yes | → Step 5 | — |
| 5 | Do the energy quantities of the LF-AASZR match the expected energy quantities? | no | A05 | Cluster: Rejection Energy quantity incorrect / not plausible |
| — | — | yes | A06 | Cluster: Consent Time series accepted |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Refusal | Deadline exceeded |
A02 | Refusal | Selected time period not permitted |
A03 | Refusal | Time series already exists |
A04 | Refusal | Version not permitted |
A05 | Rejection | Energy quantity incorrect / not plausible |
A06 | Consent | Time series accepted |
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.
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.