# E_0036 — Check balancing area aggregate time series (category B)
Check balancing area aggregate time series (category B)
| Attribute | Value |
|---|---|
| Designation | Check balancing area aggregate time series (category B) |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.25.1: AD: Transmission of the balancing area aggregate time series from ÜNB |
| Check identifiers | Response: [21002](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21002) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0036: Bilanzierungsgebietssummenzeitreihe (Kategorie B) prüfen\n\n\n\nE_0036\nBilanzierungsgebietssummenz\neitreihe (Kategorie B) prüfen\nChecking role: BIKO\n\nyes\n\nno\n\nno\n\nyes\n\nno\n\nyes\n\nyes\n\nno\n\nno\n\nyes\n\n\n1\nErfolgt der Eingang einer Zeitreihe\nnach Ablauf der Clearingfrist für\ndie KBKA?\n\n\nA01\nFristüberschreitung\n\n\n2\nIst der MaBiS-ZP zum\nbetrachteten Bilanzierungsmonat\naktiv?\n\n\nA02\nGewählter Zeitraum nicht zulässig\n\n\n3\nWird die Frist von 2 WT vor dem\nerforderlichen Versand der\nZeitreihe nach der Aktivierung\neingehalten?\n\n\nA03\nFristunterschreitung\n\n\n4\nLiegt die Version der Zeitreihe\ndes MaBiS-ZP für diesen\nBilanzierungsmonat bereits vor?\n\n\nA04\nZeitreihe bereits vorhanden\n\n\n5\nIst die Version der Zeitreihe des\nMaBiS-ZP höher als die bisher\nhöchste verarbeitete Version der\nZeitreihe für diesen\nBilanzierungsmonat und diesen\nMaBiS-ZP?\n\n\nA05\nVersion nicht zugelassen\n\nEnd\n"} kapitel={"MaBiS · 7.25.1: AD: Übermittlung der Bilanzierungsgebietssummenzeitreihe vom ÜNB"} name={"Bilanzierungsgebietssummenzeitreihe (Kategorie B) prüfen"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is a time series received after expiry of the clearing deadline for the KBKA? | yes | A01 | Deadline exceeded |
| — | — | no | → Step 2 | — |
| 2 | Is the MaBiS-ZP active in the balancing month under consideration? | no | A02 | Selected time period not permitted |
| — | — | yes | → Step 3 | — |
| 3 | Is the deadline of 2 WT before the required dispatch of the time series after the activation met? | no | A03 | Deadline undershot |
| — | — | yes | → Step 4 | — |
| 4 | Does the version of the time series of MaBiS-ZP for this balancing month already exist? | yes | A04 | Time series already exists |
| — | — | no | → Step 5 | — |
| 5 | 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 | A05 | Version not permitted |
| — | — | yes | End | — |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` | — | Deadline exceeded |
| `A02` | — | Selected time period not permitted |
| `A03` | — | Deadline undershot |
| `A04` | — | Time series already exists |
| `A05` | — | Version not permitted |
*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.
:::