# Conditions IFTSTA
EDIFACT message type **IFTSTA** · format version **202604** · 151 conditions · 1 packages · 3 UB conditions · from 35 handbook file(s)
## Conditions
| Marker | Condition |
|---|---|
| **[1]** | If the transmission of information that cannot be coded is necessary. |
| **[3]** | If SG7 STS+Z01 is not present. |
| **[4]** | If SG7 STS+Z02 is not present. |
| **[5]** | If SG7 STS+Z03 is not present. |
| **[6]** | If the verification status is available to the BIKO for the 3-tuple (MaBiS-ZP, observation period, version of the aggregated time series), it must always be transmitted together with the data status. |
| **[7]** | If the data status "billed data" or "billed data correction BKA" is not present. |
| **[8]** | If the data status of a NZR from the BIKO to the NB is not present. |
| **[10]** | If the notification from the BKV/NB/ÜNB arrives after the deadline. |
| **[16]** | If MP-ID in SG1 NAD+MR in the role BKV |
| **[17]** | If the notification from the BKV arrives at the wrong aggregation level. |
| **[18]** | If SG15 STS+Z19 not present. |
| **[19]** | If SG15 STS+Z24 not present. |
| **[20]** | If MP-ID in SG1 NAD+MR in the role LF |
| **[23]** | If SG15 STS+Z25+Z31+A06 / A09 / A10 / A11 / A13 / A14 / A15 / A16 present. |
| **[26]** | If MP-ID in SG1 NAD+MR in the role NB |
| **[27]** | Only MP-ID from the electricity division |
| **[28]** | Only MP-ID from the gas division |
| **[29]** | If MP-ID in SG1 NAD+MR in the role ÜNB |
| **[30]** | If STS+Z20+Z32+A07:E_0207 is present in this SG15. |
| **[31]** | If in this SG16 KWH/K3 is present in QTY in DE6411. |
| **[32]** | If in this SG16 KWT/K5 is present in QTY in DE6411. |
| **[33]** | If DTM+163 is present in this SG16. |
| **[43]** | If STS+Z01+Z07 present, only codes from the EBD cluster "consent" are possible. |
| **[44]** | If STS+Z01+Z08 present, only codes from the EBD cluster "rejection" are possible. |
| **[45]** | If STS+Z03+Z07 present, only codes from the EBD cluster "consent" are possible. |
| **[46]** | If STS+Z03+Z08 present, only codes from the EBD cluster "rejection" are possible. |
| **[47]** | Only codes from the EBD cluster "rejection" are possible. |
| **[48]** | Only codes from the EBD cluster "consent" are possible. |
| **[49]** | If STS+Z25+Z30 present, only codes from the EBD cluster "consent" are possible. |
| **[50]** | If STS+Z25+Z31 present, only codes from the EBD cluster "rejection" are possible. |
| **[51]** | Only codes from the EBD cluster "refusal" are possible. |
| **[52]** | If STS+Z27+Z32 present |
| **[53]** | If STS+Z28+Z32 present |
| **[54]** | If STS+Z29+Z32 present |
| **[55]** | If STS+Z30+Z32 present |
| **[56]** | If in this SG15 STS the SG15 RFF+ACW is not identical to the SG15 RFF+ACW of the SG15 STS+Z27 |
| **[57]** | If in this SG15 STS the SG15 RFF+ACW is not identical to the SG15 RFF+ACW of the SG15 STS+Z28 |
| **[58]** | If in this SG15 STS the SG15 RFF+ACW is not identical to the SG15 RFF+ACW of the SG15 STS+Z29 |
| **[59]** | If in this SG15 STS the SG15 RFF+ACW is not identical to the SG15 RFF+ACW of the SG15 STS+Z30 |
| **[60]** | If, in addition to the schedule share, the curtailed energy for the identical value from RFF+ACW is also not o.k. |
| **[61]** | If, in addition to the curtailed energy, the schedule share for the identical value from RFF+ACW is also not o.k. |
| **[62]** | If STS+Z27+Z30 present, only codes from the EBD cluster "consent" are possible. |
| **[63]** | If STS+Z27+Z32 present, only codes from the EBD cluster "rejection" are possible. |
| **[64]** | If STS+Z28+Z30 present, only codes from the EBD cluster "consent" are possible. |
| **[65]** | If STS+Z28+Z32 present, only codes from the EBD cluster "rejection" are possible. |
| **[66]** | If STS+Z29+Z30 present, only codes from the EBD cluster "consent" are possible. |
| **[67]** | If STS+Z29+Z32 present, only codes from the EBD cluster "rejection" are possible. |
| **[68]** | If STS+Z30+Z30 present, only codes from the EBD cluster "consent" are possible. |
| **[69]** | If STS+Z30+Z32 present, only codes from the EBD cluster "rejection" are possible. |
| **[70]** | If, in addition to the counterproposal for the schedule share, the counterproposal for the curtailed energy for the identical value from RFF+ACW is also not o.k. |
| **[71]** | If, in addition to the counterproposal for the curtailed energy, the counterproposal for the schedule share for the identical value from RFF+ACW is also not o.k. |
| **[72]** | If a counterproposal can be created |
| **[76]** | If MP-ID in SG1 NAD+MR in the role ESA |
| **[77]** | If STS+Z37+Z14 is present in this SG14 |
| **[78]** | If STS+Z38 is not present in this SG14 |
| **[79]** | If STS+Z37 not present in this SG14 |
| **[80]** | If STS+Z38+Z14 is present in this SG14 |
| **[83]** | If STS+Z37+Z13+A04/A05/A06:E_0472 is present in this SG14 |
| **[84]** | If STS+Z38+Z13+A02: E_0499 is present in this SG14 |
| **[85]** | If STS+Z37+Z32+A01: E_0501 is present in this SG14 |
| **[86]** | If MP-ID in SG1 NAD+MS in the role LF |
| **[91]** | If DE1131 = E_0472 in this STS |
| **[92]** | If DE1131 = E_0501 in this STS |
| **[93]** | If STS+Z37+Z13 present, only codes from the EBD cluster "failed" are possible. |
| **[94]** | If STS+Z37+Z14 present, only codes from the EBD cluster "successful" are possible. |
| **[95]** | If DE1131 = E_0499 in this STS |
| **[96]** | If DE1131 = E_0487 in this STS |
| **[97]** | If STS+Z38+Z13 present, only codes from the EBD cluster "failed" are possible. |
| **[98]** | If STS+Z38+Z14 present, only codes from the EBD cluster "successful" are possible. |
| **[99]** | If DE1131 = E_0487 in this STS, only the code A01 is possible. |
| **[100]** | If STS+Z43+Z47 present, only codes from the EBD cluster "change of the data" are possible. |
| **[101]** | If STS+Z43+Z48 present, only codes from the EBD cluster "no change of the data" are possible. |
| **[103]** | If in this STS DE1131 is not present |
| **[107]** | If STS+Z37+Z32 present, only codes from the EBD cluster "rejection" are possible. |
| **[114]** | If MP-ID in SG1 NAD+MS in the role MSB |
| **[115]** | If MP-ID in SG1 NAD+MS in the role NB |
| **[117]** | If MP-ID in SG1 NAD+MR in the role MSB |
| **[118]** | If DE1131 = E_0526 in this STS |
| **[119]** | If DE1131 = E_0528 in this STS |
| **[120]** | If DE1131 = E_0529 in this STS |
| **[121]** | If DE1131 = E_0536 in this STS |
| **[129]** | If STS+Z20+Z32+A99:E_0524 is present in this SG14 |
| **[130]** | If STS+Z20+Z32+A99:E_0531 is present in this SG14 |
| **[131]** | If STS+Z37+Z13+A04/A05/A06:E_1003 is present in this SG14 |
| **[132]** | If STS+Z37+Z32+A01: E_1002 is present in this SG14 |
| **[133]** | If DE1131 = E_1003 in this STS |
| **[134]** | If DE1131 = E_1002 in this STS |
| **[135]** | If in this SG15 DE9013 = A99 in STS+Z21 |
| **[136]** | If STS+Z38+Z13+A02: E_1005 is present in this SG14 |
| **[137]** | If DE1131 = E_1005 in this STS |
| **[138]** | If DE1131 = E_1020 in this STS |
| **[139]** | If DE1131 = E_1020 in this STS, only the code A01 is possible. |
| **[140]** | If in this STS DE9013 <> A01 |
| **[141]** | If in this STS DE9013 = A01 |
| **[142]** | If DE1131 = E_0535 in this STS |
| **[143]** | If more than one reason applies and the preceding DE9013 of this STS are not sufficient |
| **[144]** | If RFF+Z45 is not present in this SG15 |
| **[145]** | If RFF+Z17 not present in this SG15 |
| **[146]** | If code EM is present in DE3155 in the same COM |
| **[147]** | If code TE / FX / AJ / AL is present in DE3155 in the same COM |
| **[148]** | If STS+Z43+Z48+A99:E_0595 is present in this SG15 |
| **[149]** | If STS DE1131 <> E_0278 in this SG14 |
| **[150]** | If STS DE1131 <> E_0281 in this SG14 |
| **[151]** | If STS+Z20+Z32+A99:E_0278 is present in this SG14 |
| **[152]** | If STS+Z20+Z32+A99:E_0281 is present in this SG14 |
| **[153]** | If DE1131 = E_0286 in this STS |
| **[154]** | If STS+Z15+Z13+A99: E_0286 is present in this SG14 |
| **[490]** | if the value in this DE, at position CCYYMMDDHHMM, is a point in time within the period stated in the table in chapter 3.5 “Overview of German statutory summer time (MESZ)” in the columns: “Summer time (MESZ) from” representation in UTC and “Summer time (MESZ) to” representation in UTC. |
| **[491]** | if the value in this DE, at position CCYYMMDDHHMM, is a point in time within the period stated in the table in chapter 3.6 “Overview of German statutory time (MEZ)” in the columns: “Winter time (MEZ) from” representation in UTC and “Winter time (MEZ) to” representation in UTC. |
| **[492]** | if MP-ID in NAD+MR from division electricity |
| **[493]** | if MP-ID in NAD+MR from division gas |
| **[494]** | The date stated here must be the point in time at which the document was created, or a point in time before that |
| **[495]** | The point in time must be ≤ the value in DE2380 of DTM+137 |
| **[496]** | The point in time must be > the value in DE2380 of DTM+137 |
| **[501]** | Note: From QUOTES BGM DE1004 |
| **[502]** | Note: From REQOTE BGM DE1004 |
| **[503]** | Note: Self-installation of a iMS or a mME is waived |
| **[504]** | Note: Use of the ID of the MaBiS-ZP |
| **[505]** | Note: Use of the ID of the metering location |
| **[506]** | Note: Use of the ID of the market location |
| **[510]** | Note: In addition to the information about the rejection, the data status, which has remained unchanged, must also be provided for information. |
| **[512]** | Note: From MSCONS BGM DE1004 |
| **[519]** | Note: From ORDERS BGM DE1004 |
| **[520]** | Note: Point in time at which the switch takes place, if it comes about |
| **[521]** | Note: Point in time from which the MSBN actually takes over the metering point operation |
| **[522]** | Note: Point in time from which the gMSB takes over the metering point operation |
| **[523]** | Note: Value from BGM DE1004 of the MSCONS to which the status information refers |
| **[524]** | Note: Value from BGM DE1004 of the MSCONS that contains the counterproposal |
| **[525]** | Note: Each SG14 contains status information on one MSCONS only |
| **[530]** | Note: State here the work or power that the sender of the IFTSTA would have expected in the delivery note for the period / performance period it specified. |
| **[531]** | Transaction number used by the MSBN in step 1 of the SD so that the LF can use it when ordering a configuration from the MSBN, subject to the MSB switch at the metering location being successful. |
| **[532]** | Note: Use of the ID of the grid location |
| **[533]** | Note: Use of the ID of the controllable resource |
| **[534]** | Note: Only one piece of information may be transmitted in DE3148 |
| **[535]** | Note: From UTILMD IDE DE7402 |
| **[537]** | Note: The code is necessary because this use case also applies in all use cases in which the information to be transmitted in this segment does not result from a decision tree. |
| **[902]** | Format: Value may only be positive or 0 |
| **[903]** | Format: Possible value: 1 |
| **[906]** | Format: max. 3 decimal places |
| **[911]** | Format: Possible values: 1 to n, starting at 1 for each message and ascending consecutively |
| **[931]** | Format: ZZZ = +00 |
| **[932]** | Format: HHMM = 2200 |
| **[933]** | Format: HHMM = 2300 |
| **[934]** | Format: HHMM = 0400 |
| **[935]** | Format: HHMM = 0500 |
| **[939]** | Format: the character string must contain the characters @ and . |
| **[940]** | Format: the character string must begin with the character + and may only be followed by digits |
| **[950]** | Format: market location ID |
| **[951]** | Format: Metering point identifier |
| **[960]** | Format: Grid location ID |
| **[961]** | Format: SR-ID |
## UB conditions
UB conditions combine several markers into a single expression. In the handbook rows they appear like a condition, but they resolve into the markers they contain.
| Marker | Printout |
|---|---|
| **[UB1]** | ([931] ∧ [932] [490]) ⊻ ([931] ∧ [933] [491]) |
| **[UB2]** | ([931] ∧ [934] [490]) ⊻ ([931] ∧ [935] [491]) |
| **[UB3]** | ([931] ∧ [932] [492] ∧ [490]) ⊻ ([931] ∧ [933] [492] ∧ [491]) ⊻ ([931] ∧ [934] [493] ∧ [490]) ⊻ ([931] ∧ [935] [493] ∧ [491]) |
## Condition packages
Condition packages bundle prerequisites.
| Package | Prerequisites | Conditions |
|---|---|---|
| **[1P]** | -- | Note: This is the standard package if no condition applies, e.g. in the COM segment. |
This page carries the free text of every condition that the application handbook of message type **IFTSTA** references in this format version. A row of the handbook writes `Muss [704]`; what [704] requires is here.
The list applies **to the message type**, not to a single check identifier. This is not a simplification but the form of the source: the condition list is present identically in every handbook file of the format.
:::caution{title="Why no assignment to individual check identifiers is given here"}
The intermediate format from which this documentation reads the handbook rows assigns conditions to a **column** — and this assignment is shifted against the original. Measured on 05.09.2026 against UTILMD electricity: the handbook lists `STS DE9013` as `X [360]` (approval codes only) for check identifier **55017** and `X [359]` (rejection codes only) for **55018**; the intermediate format puts `[360]` on 55016 and `[359]` on 55017 **and** 55018. The same applies to `FTX Muss [83]`: at 55018 in the handbook, at 55017 in the intermediate format.
Independently confirmed by the change lists of the source: change IDs 25242, 25821, 25822, 25445 and 25243 explicitly locate [83], [351] and [352] in „Use case 55018 Rejection of contract termination“. No entry assigns them to 55016 or 55017.
That is why the **text** of every condition is given here and nowhere the claim as to which condition applies to which check identifier. Anyone who needs that looks it up in the original application handbook.
:::
:::note{title="9 conditions do not appear in every handbook file"}
The list of conditions is meant to apply across the whole format, but it does not everywhere: the following markers occur in fewer than all 35 files of this format. They are given here nonetheless — leaving out a condition because one file does not carry it would mean letting a reference point into the void again.
[490], [491], [932], [933], [934], [935], [UB1], [UB2], [UB3]
:::
As measured on 05.09.2026, **no** `ahb_expression` in this source points to a package marker — the condition packages are listed on this page because the source carries them, not because a handbook line refers to them.