# E_0042 — Assign data status after receipt of a balancing group aggregated time series (category B)
Assign data status after receipt of a balancing group aggregated time series (category B)
| Attribute | Value |
|---|---|
| Designation | Assign data status after receipt of a balancing group aggregated time series (category B) |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.45.2: AD: Transmission of the data status for the balancing group aggregated time series from BIKO to ÜNB and BKV |
| Check identifiers | Response: [21003](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21003), [21004](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21004) |
| EBD version | 4.2 |
| As at | 2026-06-23 |
## Decision tree
\nDecision tree E_0042: Datenstatus nach Eingang einer Bilanzkreissummenzeitreihe (Kategorie B) vergeben\n\n\n\nE_0042\nDatenstatus nach Eingang einer\nBilanzkreissummenzeitreihe\n(Kategorie B) vergeben\nChecking role: BIKO\n\nno\n\nyes\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\nno\n\nyes\n\n\nno\n\n\nyes\n\nno\n\n\n1\nBefindet sich der MaBiS-ZP auf\nder Aggregationsebene RZ?\n\n\n2\nHat der BKV für den BK dieses\nMaBiS-ZP in diesem\nBilanzierungsmonat die\nAggregationsebene RZ\nabbestellt?\n\n\n3\nHat der BKV für diesen\nBilanzierungsmonat bereits\nmit-geteilt, dass die weiteren\nPrüfungen auf Ebene des BG\nstattfinden müssen?\n\nEnd\n\n\n4\nErfolgt der Eingang der Zeitreihe\nvor Ablauf der Frist für den\nErstaufschlag?\n\n\nA01\nDatenstatus „Abrechnungsdaten“\n\n\nA02\nDatenstatus „Prüfdaten“\n\n\n5\nHat der BKV für diesen\nBilanzierungsmonat bereits\nmit-geteilt, dass die weiteren\nPrüfungen auf Ebene des BG\nstattfinden müssen?\n\nEnd\n\n\n6\nErfolgt der Eingang der Zeitreihe\nvor Ablauf der Frist für den\nErstaufschlag?\n\n\nA01\nDatenstatus „Abrechnungsdaten“\nSetzen des Datenstatus für die der\nVersion des MaBiS-ZP auf der\nAggregationsebene RZ zugehörigen\nVersion des MaBiS-ZP auf der\nAggregationsebene BG\ncontinue with step 7\n\n\nA02\nDatenstatus „Prüfdaten“\nSetzen des Datenstatus für die der\nVersion des MaBiS-ZP auf der\nAggregationsebene RZ zugehörigen\nVersion des MaBiS-ZP auf der\nAggregationsebene BG\ncontinue with step 7\n\n\n7\nHat die zugehörige Version auf\nder Aggregationsebene RZ den\nDatenstatus Abrechnungsdaten?\n\n\nA01\nDatenstatus „Abrechnungsdaten“\n\n\nA02\nDatenstatus „Prüfdaten“\n"} kapitel={"MaBiS · 7.45.2: AD: Übermittlung Datenstatus für die Bilanzkreissummenzeitreihe vom BIKO an ÜNB und BKV"} name={"Datenstatus nach Eingang einer Bilanzkreissummenzeitreihe (Kategorie B) vergeben"}>
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the MaBiS-ZP at the RZ aggregation level? | no | → Step 2 | — |
| — | — | yes | → Step 5 | — |
| 2 | Has the BKV cancelled the subscription for aggregation level RZ for the BK of this MaBiS-ZP in this balancing month? | yes | → Step 4 | Setting the data status for the version of the MaBiS-ZP at aggregation level BG |
| — | — | no | → Step 3 | — |
| 3 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | → Step 4 | Setting the data status for the version of the MaBiS-ZP at aggregation level BG |
| — | — | no | End | — |
| 4 | Is the time series received before expiry of the deadline for the initial submission? | yes | A01 | Data status “Billing data” |
| — | — | no | A02 | Data status “Validation data” |
| 5 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | End | — |
| — | — | no | → Step 6 | Setting the data status for the version of the MaBiS-ZP at aggregation level RZ |
| 6 | Is the time series received before expiry of the deadline for the initial submission? | yes | A01 | Data status “Billing data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
| — | — | no | A02 | Data status “Validation data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
| from 7 | *The following actions are to be run through for each associated MaBiS-ZP at aggregation level BG:* | — | — | — |
| 7 | Does the associated version at aggregation level RZ have the data status billing data? | yes | A01 | Data status “Billing data” |
| — | — | no | A02 | Data status “Validation data” |
## Result codes
| Result code | Cluster | Meaning |
|---|---|---|
| `A01` (2 outputs) | — | Data status “Billing data” |
| `A02` (2 outputs) | — | Data status “Validation data” |
| `A01` | — | Data status “Billing data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
| `A02` | — | Data status “Validation data” Setting the data status for the version of the MaBiS-ZP at aggregation level BG that belongs to the version of the MaBiS-ZP at aggregation level RZ |
*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.
:::