# Conditions MSCONS
EDIFACT message type **MSCONS** · format version **202610** · 169 conditions · 5 packages · 3 UB conditions · from 25 handbook file(s)
## Conditions
| Marker | Condition |
|---|---|
| **[1]** | Provided that it is requested via ORDERS |
| **[2]** | If the time interval between the first SG10 DTM+163 and the last SG10 DTM+164 spans at least one month |
| **[11]** | If SG9 PIA+5+7-0?:52.0.22/7-0?:54.0.16/7-0?:54.0.20/7-0?:54.0.22 |
| **[12]** | If not SG9 PIA+5+7-0?:52.0.22/7-0?:54.0.16/7-0?:54.0.20/7-0?:54.0.22 |
| **[17]** | If not SG9 PIA+5+1-b?:9.99.0 (b= channel: value according to the code list of OBIS codes and media) |
| **[18]** | If SG9 PIA+5+1-b?:9.99.0 (b= channel: value according to the code list of the OBIS codes and media) |
| **[22]** | If a split is present |
| **[23]** | If UNH DE0070 with 1 is present |
| **[24]** | In the case of splitting, in the message with the highest transmission number |
| **[27]** | If SG9 PIA+5+1-1?:1.9.0 is present |
| **[28]** | If SG9 PIA+5+1-1?:1.9.0 is not present |
| **[32]** | if MP-ID in SG2 NAD+MS in the role NB |
| **[33]** | if MP-ID in SG2 NAD+MR in the role LF |
| **[35]** | if MP-ID in SG2 NAD+MS in the role MSB |
| **[36]** | if MP-ID in SG2 NAD+MR in the role NB |
| **[38]** | if the ID of the metering location is stated in SG6 LOC+172 DE3225 |
| **[42]** | If MP-ID in SG2 NAD+MR in the role MSB |
| **[45]** | If SG9 PIA+5+7-b:99.41.16 (b=channel: value according to the code list of the OBIS codes and media) is present |
| **[46]** | If the value in SG6 LOC+172 DE3225 has exactly 11 digits |
| **[48]** | If SG9 PIA+5+7-0?:52.0.22 |
| **[49]** | If SG9 PIA+5+7-b?:70.16.16/7-b?:70.16.20/7-b?:70.16.22 (b=channel: value according to the code list of the OBIS codes and media) is present |
| **[50]** | If SG9 PIA+5+7-b?:70.18.16/7-b?:70.18.20/7-b?:70.18.22 (b=channel: value according to the code list of the OBIS codes and media) is present |
| **[51]** | If SG9 PIA+5+7-0?:33.86.0 is present, SG9 PIA+5+7-0?:52.0.22/7-0?:54.0.16/7-0?:54.0.20/7-0?:54.0.22 must no longer be specified by repeating SG9 LIN in the same message |
| **[62]** | If the value in SG6 LOC+172 DE3225 has exactly 33 digits |
| **[67]** | If this concerns the reference to a ORDERS |
| **[68]** | If BGM+7 present |
| **[69]** | If BGM+Z28 present |
| **[70]** | If BGM+BK present |
| **[71]** | If BGM+Z39 present |
| **[72]** | If SG9 PIA+5+1-b?:1.6.0/1-b?:3.6.0/1-b?:4.6.0/1-66?:13.6.0/1-66?:14.6.0 (b=channel: value according to the code list of the OBIS codes and media) is present |
| **[73]** | If SG9 PIA+5+1-b?:1.9.e/1-b?:3.9.0/1-b?:4.9.0/1-66?:13.9.0/1-66?:14.9.0 (b=channel: value according to the code list of the OBIS codes and media, e=tariff: value according to the code list of the OBIS codes and media) is present |
| **[77]** | If MP-ID in SG2 NAD+MR of the RB HKN-R |
| **[78]** | If SG9 PIA+5+1-66?:13.6.0/1-66?:14.6.0/1-66?:13.9.0/1-66?:14.9.0 is present |
| **[79]** | If SG9 PIA+5+1-66?:13.6.0/1-66?:14.6.0/1-66?:13.9.0/1-66?:14.9.0 is not present |
| **[80]** | If MP-ID in SG2 NAD+MR in the role ÜNB |
| **[83]** | If in the same SG9 LIN the entry STS+10+Z38 is not present |
| **[84]** | If in the same SG9 LIN the entry STS+10+Z39 is not present |
| **[85]** | If in the same SG9 LIN the entry STS+10+Z36 is not present |
| **[86]** | If in the same SG9 LIN the entry STS+10+Z37 is not present |
| **[87]** | If the value in DTM+163 DE2380 of the same SG6 LOC+172 with the same value in SG9 PIA+5 DE7140 is the earliest point in time specified |
| **[88]** | If the value in DTM+164 DE2380 of the same SG6 LOC+172 with the same value in SG9 PIA+5 DE7140 is the latest point in time specified |
| **[90]** | If BGM+Z41 present |
| **[91]** | If BGM+Z42 present |
| **[92]** | If SG10 QTY DE6063 with value 67 is present |
| **[93]** | If SG10 QTY DE6063 with value 220 is present |
| **[94]** | If SG10 QTY DE6063 with value 201 is present |
| **[95]** | If SG10 QTY DE6063 with value 20 is present |
| **[96]** | If SG10 QTY DE6063 with value Z18 is present |
| **[97]** | If this concerns the transmission of a value due to the change of the gas quality |
| **[98]** | If SG9 PIA+5+SOL:Z08 is present |
| **[99]** | If SG9 PIA+5+WID:Z08 is present |
| **[100]** | If in the same SG9 LIN the PIA+5+AUA:Z08 is present |
| **[101]** | If in the same SG9 LIN the PIA+5+FPA:Z08 is present |
| **[108]** | if SG9 PIA+5+7-b?:99.41.16/7-b?:99.42.16 (b=channel: value according to the code list of OBIS identifiers and media) is present |
| **[111]** | If SG10 DTM+9 DE2379 with value 303 is present in the same segment |
| **[113]** | if SG7 RFF+AGK (configuration ID) is present |
| **[117]** | Only MP-ID from the electricity division |
| **[118]** | Only MP-ID from the gas division |
| **[119]** | if the ID of the market location is stated in SG6 LOC+172 DE3225 |
| **[121]** | if BGM+Z43 (Redispatch outage energy transfer time series) is present |
| **[125]** | if SG9 PIA+5+7-0?:52.0.22/7-b?:53.0.16/7-b?:55.0.16/7-b?:55.0.20/7-b?:55.0.22 (b=channel: value according to the code list of OBIS identifiers and media) is present |
| **[126]** | if plausibility check notices exist |
| **[127]** | if a correction reason has to be stated |
| **[128]** | If this concerns a meter reading which is not a reading due to a change to the metering equipment or its configuration (e.g. customer reading). |
| **[129]** | If this concerns a meter reading due to a change to the metering equipment or its configuration (e.g. device replacement). |
| **[130]** | If, within the same LIN segment and in addition to this segment (SG10 DTM+7 usage point in time), the SG10 DTM+60 (execution / change point in time) or the SG10 DTM+9 (reading date) is also present, the value of the difference between the later and the earlier point in time of the DTM segments may only be < 24 hours. If the summer/winter time changeover takes place between the two points in time, the value of the difference may only be < 25 hours. If the winter/summer time changeover takes place between the two points in time, the value of the difference may only be < 23 hours. |
| **[131]** | if RFF+AGK (configuration ID) is not present |
| **[132]** | if LOC+172 (identification detail) DE3225 is not present |
| **[133]** | If, within the same LIN segment and in addition to this segment (SG10 DTM+7 usage point in time), the SG10 DTM+9 (reading date) with the code 102 in DE2379 is also present, the value of the difference between the value at position CCYYMMDD of the later and the earlier point in time of the DTM segments at position CCYYMMDD may only be 0 or 1 day. |
| **[134]** | If SG10 DTM+9 DE2379 with value 102 is present in the same segment |
| **[135]** | The value at position CCYYMMDD must be ≤ the value at position CCYYMMDD in DE2380 of DTM+137 |
| **[138]** | If this concerns a correction energy quantity for a value from a iMS |
| **[141]** | If MP-ID in SG2 NAD+MR in the role MGV |
| **[144]** | If the value in SG7 RFF+AGK DE1154 (configuration ID) is present |
| **[145]** | If the SG10 DTM+163 (start of metering period) is not present in the same S9 LIN. |
| **[146]** | If the value to be transmitted is a value at a point in time. |
| **[147]** | If the SG10 DTM+7 (point in time of use) is not present in the same S9 LIN. |
| **[148]** | If the value to be transmitted is a value within a time interval. |
| **[149]** | If the SG10 DTM+163 (start of metering period) is present in the same S9 LIN. |
| **[150]** | If BGM+Z69 (Redispatch daily curtailed energy transfer time series) present. |
| **[151]** | If BGM+Z27 (transaction data in the calendar year before start of supply) present. |
| **[152]** | If BGM+7 (process data report) present. |
| **[153]** | If SG9 PIA+5+7-0?:33.86.0 is present |
| **[154]** | If SG9 PIA+5+7-0?:33.47.0 is present |
| **[155]** | If the transmission file is exchanged for test purposes. |
| **[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 |
| **[501]** | Note: Only the values that are marked with the corresponding check identifier in the EDI@Energy code list of the OBIS codes and media are permitted. |
| **[502]** | Note: Once for the energy quantity from the start of the calendar year until the start of supply and at least once and up to twice for the two highest monthly demand values (because of KAV) from the start of the calendar year until the start of supply. |
| **[506]** | Note: Only for feed-in quantities and, for gas, for hourly energy data transmission |
| **[509]** | Note: If this is a correction energy quantity, the reference to the MSCONS in which the meter reading was transmitted in advance must be specified here. |
| **[510]** | Note: Use of the ID of the metering location |
| **[511]** | Note: Use of the ID of the MaBiS-ZP |
| **[512]** | Note: Use of the balancing group designation |
| **[513]** | Note: Use of the designation of the balancing area |
| **[514]** | Note: Use of the ID of the market location |
| **[515]** | Note: Use of the profile designation |
| **[516]** | Note: Use of the designation of the profile set |
| **[518]** | Note: Use of the ID of the tranche |
| **[519]** | Note: Only if the measured load curve of the metering location does not correspond 1:1 to the load curve of the market location. |
| **[520]** | Note: If there is a 1:1 relationship between metering location and market location and the measured load curve of the metering location corresponds 1:1 to the load curve of the market location, or if the measured load curve does not correspond to the load curve of the market location. |
| **[522]** | Note: Only for the transmission of the correction energy quantities in the time interval between two metered values. |
| **[523]** | Note: Only for the transmission of the energy quantity in the time interval between two metered values before the grid usage settlement. |
| **[524]** | Note: Only if it concerns the transmission of the billing calorific value and Z number for the period requested by the supplier via a business data request. |
| **[525]** | Note: Only for the transmission of the energy quantity in the time interval for a market location without a metering location (flat-rate installation) if one of the events from chapter 4.2 has occurred. |
| **[526]** | Note: Value from BGM+Z24 DE1004 of the ORDERS with which the allocation list was ordered. |
| **[528]** | Note: Value from BGM+Z28 DE1004 of the ORDERS with which the request for meter reading values was made. |
| **[529]** | Note: Value from BGM+7 DE1004 of the ORDERS with which the request for meter reading values was made. |
| **[530]** | Note: Value from SG4 IDE+24 DE7402 of the UTILMD with which the sender of the MSCONS transmitted the previous master data by means of UTILMD. |
| **[531]** | Note: Value from BGM+7 DE1004 of the MSCONS with which the meter reading was transmitted. |
| **[532]** | Note: Value from BGM+7/Z27/Z28/270/Z41/Z42/Z85 DE1004 of the MSCONS message that is being canceled |
| **[535]** | Note: Use of the ID of the electricity/gas grid coupling point |
| **[538]** | Note: The reference to the ORDERS is only to be specified if these values were also originally requested by the recipient by means of ORDERS. |
| **[541]** | Note: A correction reason is to be specified if: 1. a preliminary value already transmitted to the MP is replaced by a substitute value after cancellation, or 2. a substitute value already transmitted to the MP is replaced by a substitute value after cancellation, or 3. a true value already transmitted to the MP is replaced by a substitute value after cancellation, or 4. a true value already transmitted to the MP is replaced by a true value after cancellation. |
| **[544]** | Note: In the case of a quantity split (e.g. due to a delimitation) for SG6 LOC+172, a meter reading must be available and communicated for every OBIS code for the earliest specified point in time at the start of the time interval (across all repetitions of the LIN segments of the same SG6 LOC+172). |
| **[545]** | Note: In the case of a quantity split (e.g. due to a delimitation) for SG6 LOC+172, a meter reading must be available and communicated for every OBIS code for the latest specified point in time at the end of the time interval (across all repetitions of the LIN segments of the same SG6 LOC+172). |
| **[546]** | Note: A reference to the master data change of the device replacement is always to be specified if it is available to the sender. |
| **[547]** | Note: Code 270 is only to be used if a delivery note created before 1.4.2021 is canceled. |
| **[551]** | Note: A correction reason is to be specified if: 1. a preliminary value already transmitted to the MP is replaced by a substitute value, or 2. a substitute value already transmitted to the MP is replaced by a substitute value, or 3. a true value already transmitted to the MP is replaced by a substitute value, or 4. a true value already transmitted to the MP is replaced by a true value. |
| **[553]** | Note: Value from BGM+Z34 DE1004 of the ORDERS with which the complaint regarding values was made |
| **[554]** | Note: Use of the ID of the technical resource |
| **[556]** | Note: Value from BGM+Z45 DE1004 of the ORDERS with which the request for the curtailed energy by the anfNB was made. |
| **[557]** | Note: The reference to the original MSCONS is to be specified if it is the transmission of a counterproposal by the BTR. |
| **[558]** | Note: Value from BGM+Z45 DE1004 of the MSCONS to which the transmission of the counterproposal by the BTR refers. |
| **[559]** | Note: A correction reason is to be specified if: 1. a preliminary value already transmitted to the MP is replaced by a substitute value after cancellation, or 2. a substitute value already transmitted to the MP is replaced by a substitute value after cancellation, or 3. a true value already transmitted to the MP is replaced by a substitute value after cancellation, or 4. a true value already transmitted to the MP is replaced by a true value after cancellation. |
| **[560]** | Note: A correction reason is to be specified if: 1. a preliminary value already transmitted to the MP is replaced by a substitute value, or 2. a substitute value already transmitted to the MP is replaced by a substitute value, or 3. a true value already transmitted to the MP is replaced by a substitute value, or 4. a true value already transmitted to the MP is replaced by a true value. |
| **[566]** | Note: Only the values that were transmitted by the MSB in the previous master data exchange for this reporting point at the point in time are permitted. |
| **[567]** | Note: The configuration ID that was communicated in the previous master data exchange must be specified. |
| **[568]** | Note: Use is permitted only if it is a 1:n relationship between market and metering location and different substitute value determination procedures have been used and communicated at the level of the metering location. |
| **[569]** | Note: If a metering location has several meter readings (e.g. HT/NT), this time specification is to be used and the SG9 LIN is to be repeated. |
| **[570]** | Note: Use is permitted only if it is a 1:n relationship between market and metering location and different reasons for the substitute value determination exist at the level of the metering location and have been communicated. |
| **[571]** | Note: Use is permitted only if it is a 1:n relationship and different reasons for the substitute value determination exist at the level of the grid coupling points and have been communicated. |
| **[572]** | Note: Use is permitted only if it is a 1:n relationship and different substitute value determination procedures exist at the level of the grid coupling points and have been communicated. |
| **[573]** | Note: An energy quantity in the gas division is to be rounded to whole kilowatt hours in accordance with DVGW G685 worksheet 4 chapter 5.3. |
| **[574]** | Note: Value from BGM DE1004 of the ORDERS with which the order placement for the values in accordance with type 2 was made |
| **[575]** | Note: Use of the ID of the grid location |
| **[577]** | Note: This code is also to be used if, due to the termination of a metering location (decommissioning), the termination of the market location (decommissioning) takes place at different points in time, that is, the termination of the metering location takes place before the termination of the market location. The energy quantity is to be transmitted up to the end point in time of the market location, even though the last meter reading of the metering location lies at an earlier point in time. |
| **[578]** | Note: If this concerns the transmission of the demand value for the grid fees with an annual demand price system. |
| **[579]** | Note: If this concerns the transmission of the demand value for the grid fees with a monthly demand price system. |
| **[580]** | Note: If this concerns the transmission of the demand value for the grid fees with a daily demand price system. |
| **[581]** | Note: If this concerns the transmission of the monthly maximum in accordance with WiM. |
| **[902]** | Format: Possible value: ≥ 0 |
| **[904]** | Format: exactly 16 digits |
| **[905]** | Format: max. 3 digits |
| **[906]** | Format: max. 3 decimal places |
| **[907]** | Format: max. 4 decimal places |
| **[908]** | Format: possible values: 1 to n |
| **[909]** | Format: possible values: 0 to n |
| **[910]** | Format: Possible value: < 0 or ≥ 0 |
| **[917]** | Format: max. 4 digits before the decimal point |
| **[918]** | Format: Characters from the character set defined via UNOC, where only capital letters are permitted among the letters. |
| **[922]** | Format: TR-ID |
| **[925]** | Format: max. 5 decimal places |
| **[931]** | Format: ZZZ = +00 |
| **[932]** | Format: HHMM = 2200 |
| **[933]** | Format: HHMM = 2300 |
| **[934]** | Format: HHMM = 0400 |
| **[935]** | Format: HHMM = 0500 |
| **[937]** | Format: no decimal places |
| **[950]** | Format: market location ID |
| **[951]** | Format: Metering point identifier |
| **[960]** | Format: Grid location ID |
| **[2001]** | Segment group must be specified only once per UNH |
| **[2002]** | Segment group must be specified at least twice and at most three times per SG5 NAD+DP |
| **[2003]** | Segment group must be specified exactly two times per SG9 LIN |
## 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 |
|---|---|---|
| **[4P]** | [92] | [92] If SG10 QTY DE6063 with value 67 present |
| **[5P]** | [93] | [93] If SG10 QTY DE6063 with value 220 present |
| **[6P]** | [94] | [94] If SG10 QTY DE6063 with value 201 present |
| **[7P]** | [95] | [95] If SG10 QTY DE6063 with value 20 present |
| **[8P]** | [96] | [96] If SG10 QTY DE6063 with value Z18 present |
This page carries the free text of every condition that the application handbook of message type **MSCONS** 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="6 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 25 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.
[493], [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.