| Label | Definition | Identifier | Serialisation |
|---|---|---|---|
| Errors not specifically identified | This code is used to identify errors that have not been specifically addressed in the Reason code list. It can be used at any level and refers to the level for which it has been identified. | 999 |
RDF/XML JSON-LD Turtle |
| Message fully accepted | The message has been fully accepted for application processing. | A01 |
RDF/XML JSON-LD Turtle |
| Message fully rejected | No part of the message has been accepted for application processing, e.g. Global position incomplete. | A02 |
RDF/XML JSON-LD Turtle |
| Message contains errors at the time series level | Part of the message contents, i.e. certain time series, has been accepted for application processing. It is necessary to look at the time series level to determine the time series that have been rejected. The time series is excluded from the global position. | A03 |
RDF/XML JSON-LD Turtle |
| Time interval incorrect | The schedule time interval is not within the contractual agreement or the period does not agree with the schedule time interval. | A04 |
RDF/XML JSON-LD Turtle |
| Sender without valid contract | The sender has no current valid contract with the TSO. The message consequently will be fully rejected. | A05 |
RDF/XML JSON-LD Turtle |
| Schedule accepted | The schedule of the recipient as presented has been completely accepted. | A06 |
RDF/XML JSON-LD Turtle |
| Schedule partially accepted | The schedule of the recipient as presented has been partially accepted. It is necessary to look at the time series level to determine the changes (time series rejected, modified, etc.). | A07 |
RDF/XML JSON-LD Turtle |
| Schedule rejected | The schedule of the recipient as presented has been totally rejected. The cause could be the non presentation of a counter part for the involved trades. | A08 |
RDF/XML JSON-LD Turtle |
| Time series not matching | Time series mismatches. | A09 |
RDF/XML JSON-LD Turtle |
| Credit limit exceeded | The contractual credit limit has been exceeded and as such the message has been rejected. | A10 |
RDF/XML JSON-LD Turtle |
| Time series fully rejected | The time series has been fully rejected. In the case of a confirmation report, this reason code is used in conjunction with either A26 or A30. | A20 |
RDF/XML JSON-LD Turtle |
| Time series accepted with specific time interval errors | The time series has been accepted but some time interval quantities have been rectified or zeroed out. | A21 |
RDF/XML JSON-LD Turtle |
| In party/Out party invalid | There is no contract for the parties indicated or the rules for cross border nominations are not being respected. The time series has been rejected. | A22 |
RDF/XML JSON-LD Turtle |
| Area invalid | The area is unknown or not allowed. The time series has been rejected. | A23 |
RDF/XML JSON-LD Turtle |
| A24 not applicable | This code is no longer applicable. | A24 |
RDF/XML JSON-LD Turtle |
| A25 not applicable | This code is no longer applicable. | A25 |
RDF/XML JSON-LD Turtle |
| Default time series applied | The time series has been rejected and replaced with a default time series profile. This reason code may not be used in conjunction with A30. | A26 |
RDF/XML JSON-LD Turtle |
| Cross border capacity exceeded | The cross border capacity has been exceeded. The time series has been rejected or adjusted. | A27 |
RDF/XML JSON-LD Turtle |
| Counterpart time series missing | This provides an indication that the time series has not got a counterpart time series. In the case of an Intermediate Confirmation Report this is advising the recipient that the time series may be rejected at nomination closure if the counterpart time series is not received. In the case of a Final Confirmation Report this is informing the recipient that the time series has been rejected because the counterpart time series has not been forthcoming. | A28 |
RDF/XML JSON-LD Turtle |
| Counterpart time series quantity differences | The time series has been rejected as it does not match that of the counterpart who is considered by market rules to be correct. | A29 |
RDF/XML JSON-LD Turtle |
| Imposed Time series from nominated party's time series (party identified in reason text) | The nominated party's time series has replaced the current time series. This reason code may not be used in conjunction with A26. | A30 |
RDF/XML JSON-LD Turtle |
| Resolution inconsistency | The resolution is not coherent with the time interval, or resolution not valid. | A41 |
RDF/XML JSON-LD Turtle |
| Quantity inconsistency | The quantity is not coherent. For example a time period with the same version number but different quantities or an non permitted number of digits after the decimal point, etc. | A42 |
RDF/XML JSON-LD Turtle |
| Quantity increased | The quantity has been increased in order to satisfy minimum constraints. | A43 |
RDF/XML JSON-LD Turtle |
| Quantity decreased | The quantity has been decreased in order to satisfy congestion constraints. | A44 |
RDF/XML JSON-LD Turtle |
| Default quantity applied | The default quantity has been applied as the current quantity does not satisfy contractual obligations. | A45 |
RDF/XML JSON-LD Turtle |
| Quantities must not be signed values | The quantity proposed is illegal since signed values are only permitted in specific circumstances. | A46 |
RDF/XML JSON-LD Turtle |
| A47 not applicable | This code is no longer applicable. | A47 |
RDF/XML JSON-LD Turtle |
| Modification reason | In an intraday transmission, the reason for the modification is as follows (in the reason text). | A48 |
RDF/XML JSON-LD Turtle |
| Position inconsistency | A position is missing or too many. | A49 |
RDF/XML JSON-LD Turtle |
| Senders time series version conflict | There is an error in the sender time series version, i.e. it could be superior to the message version or is inconsistent with the existing data. The time series has been rejected. | A50 |
RDF/XML JSON-LD Turtle |
| Message identification or version conflict | The message identification is already in the receiving system. Or a higher version already exists. Message rejected. | A51 |
RDF/XML JSON-LD Turtle |
| Time series missing from new version of message | A time series is not contained in a new version of the message. Message rejected. | A52 |
RDF/XML JSON-LD Turtle |
| Receiving party incorrect | The receiving party is incorrect. Message rejected. | A53 |
RDF/XML JSON-LD Turtle |
| Global position not in balance | The message does not balance out to zero. Market rules might require that the message is rejected. | A54 |
RDF/XML JSON-LD Turtle |
| Time series identification conflict | The identification of the time series is duplicated or incorrect. Time series will be rejected. | A55 |
RDF/XML JSON-LD Turtle |
| Corresponding Time series not netted | All corresponding time series must be netted. Time series rejected. | A56 |
RDF/XML JSON-LD Turtle |
| Deadline limit exceeded/Gate not open | The deadline for receiving schedule messages has passed. Message or time series rejected. | A57 |
RDF/XML JSON-LD Turtle |
| One to one nomination inconsistency | There is a one to one nomination inconstancy with the in/out parties or areas. Time series rejected. | A58 |
RDF/XML JSON-LD Turtle |
| Not compliant to local market rules | The level in which this is identified is not in compliance with local market rules. The level in question has been rejected. | A59 |
RDF/XML JSON-LD Turtle |
| Inter-area transit schedule exceeds nominated schedule | The inter-area transit schedule exceeds the nominated schedule for the same time interval. The inter-area transit schedule is rejected. | A60 |
RDF/XML JSON-LD Turtle |
| Currency invalid | The currency is not in compliance with ISO 4217. | A61 |
RDF/XML JSON-LD Turtle |
| Invalid business type | The business type does not belong to the valid set of business types for the process in question. | A62 |
RDF/XML JSON-LD Turtle |
| Time Series modified | The time series has been modified. | A63 |
RDF/XML JSON-LD Turtle |
| Resource Object Invalid | The Resource Object defined in the document is not valid. | A64 |
RDF/XML JSON-LD Turtle |
| Reserve object Technical limits exceeded | Reserve objects aggregated values are not within technical/prequalified limits | A65 |
RDF/XML JSON-LD Turtle |
| Planned reserves do not correspond with contractual data | Planned reserves do not correspond with contractual data. | A66 |
RDF/XML JSON-LD Turtle |
| Limit Data is not available | Limit Data is not available. | A67 |
RDF/XML JSON-LD Turtle |
| Reserve Object not qualified for reserve type | Reserve Object is not qualified for reserve type. | A68 |
RDF/XML JSON-LD Turtle |
| Mandatory attributes missing | Mandatory attributes missing. | A69 |
RDF/XML JSON-LD Turtle |
| Curtailment | The capacity in question has been curtailed. | A70 |
RDF/XML JSON-LD Turtle |
| Linked bid rejected due to associated bid unsuccessful | The bid in question has been rejected because an associated bid has been unsuccessful. | A71 |
RDF/XML JSON-LD Turtle |
| Original bid divided to permit acceptance | The original bid quantity has been divided to enable it to be accepted. | A72 |
RDF/XML JSON-LD Turtle |
| Bid accepted | The bid in question has been accepted. | A73 |
RDF/XML JSON-LD Turtle |
| Auction Status | The information in the Reason Text provides auction status information. | A74 |
RDF/XML JSON-LD Turtle |
| Right status information | The information in the Reason Text provides status information concerning the transmission rights in question. | A75 |
RDF/XML JSON-LD Turtle |
| Agreement identification inconsistency | There is an inconsistency between the contract type and the agreement identification. | A76 |
RDF/XML JSON-LD Turtle |
| Dependency matrix not respected | There is an inconsistency between the document contents and the dependency matrix. | A77 |
RDF/XML JSON-LD Turtle |
| Sender identification and/or role invalid | The identification of the sender or the sender/role combination is invalid. | A78 |
RDF/XML JSON-LD Turtle |
| Process type invalid | The process type does not figure in the list of valid process types for this document. | A79 |
RDF/XML JSON-LD Turtle |
| Domain invalid | The domain does not figure in the list of valid domains for this document and process. | A80 |
RDF/XML JSON-LD Turtle |
| Matching period invalid | The period is not within the expected limits. | A81 |
RDF/XML JSON-LD Turtle |
| In/Out area inconsistent with domain | The in and out area does not figure within the domain specified. | A82 |
RDF/XML JSON-LD Turtle |
| Disagree with matching results | The matching results provided are not consistent. | A83 |
RDF/XML JSON-LD Turtle |
| Confirmation ignored due to higher version already received | The report has been ignored since a higher version has been received. | A84 |
RDF/XML JSON-LD Turtle |
| Confirmation without adjustment (time series have been matched without change) | The report has been successfully matched without any changes. | A85 |
RDF/XML JSON-LD Turtle |
| Confirmation with adjustment (time series have been modified) | The report has been matched but required adjustment. | A86 |
RDF/XML JSON-LD Turtle |
| For action (only in intermediate confirmation - time series need mutual agreement and action) | The report in question is only for action in an intermediate stage. | A87 |
RDF/XML JSON-LD Turtle |
| Time series matched | The time series has been successfully matched. | A88 |
RDF/XML JSON-LD Turtle |
| Time series ignored (note: this can only apply to time series that are set to zero - see matching principles) | The time series has been ignored and not matched since it does not figure in a counterparty transmission. All are correctly equal to zero. | A89 |
RDF/XML JSON-LD Turtle |
| Modification proposal (intermediate confirmation) | The document is a proposal for change before finalization. | A90 |
RDF/XML JSON-LD Turtle |
| Expected document not received | The document that is expected has not been received within the expected timeframe. | A91 |
RDF/XML JSON-LD Turtle |
| Not possible to send document on time, but estimated delivery time is provided | The document that is due cannot be transmitted within the required timeframe. An estimated time of transmission is provided. | A92 |
RDF/XML JSON-LD Turtle |
| Not possible to send document on time, and furthermore no expected time of return to normal situation | The document that is due cannot be transmitted within the required timeframe. The time of transmission of the document is unknown. | A93 |
RDF/XML JSON-LD Turtle |
| Document cannot be processed by receiving system | The receiving system cannot process that document in question. | A94 |
RDF/XML JSON-LD Turtle |
| Complementary information | Additional text is provided in order to further explain a condition, for example to provide details of an outage. | A95 |
RDF/XML JSON-LD Turtle |
| Technical constraint | A technical constraint has been applied. | A96 |
RDF/XML JSON-LD Turtle |
| Force majeure curtailment | Curtailment due to Force Majeure. A code that enables the identification of the curtailment reason for settlement purposes. | A97 |
RDF/XML JSON-LD Turtle |
| Network security curtailment | Curtailment due to network security reasons A code that enables the identification of the curtailment reason for settlement purposes. | A98 |
RDF/XML JSON-LD Turtle |
| Auction cancelled | The auction has been cancelled. | A99 |
RDF/XML JSON-LD Turtle |
| Incomplete document | The document is incomplete and cannot be processed. | B01 |
RDF/XML JSON-LD Turtle |
| Accounting Point (tie-line) Time Series missing | The document is incomplete as a time series for an accounting point is missing. | B02 |
RDF/XML JSON-LD Turtle |
| Meter data Time series missing | The document is incomplete as a time series for meter data is missing. | B03 |
RDF/XML JSON-LD Turtle |
| Estimated values not allowed in first transmission | The document is in its initial form and estimated values are not allowed. | B04 |
RDF/XML JSON-LD Turtle |
| No quantity values allowed for a quality that is not available | No quantity values are allowed for a quality that is not available. | B05 |
RDF/XML JSON-LD Turtle |
| Time series accepted | Time series accepted. | B06 |
RDF/XML JSON-LD Turtle |
| Auction without bids being entered | The auction has terminated without any bids being submitted. The ReasonText may provide the identification of the auction in question. | B07 |
RDF/XML JSON-LD Turtle |
| Data not yet available | It is not possible to perform the necessary action since the required data for this action is not yet available. | B08 |
RDF/XML JSON-LD Turtle |
| Bid not accepted | The bid in question has not been accepted. | B09 |
RDF/XML JSON-LD Turtle |
| Initiator area problem | The problem concerns the initiator area. | B10 |
RDF/XML JSON-LD Turtle |
| Cooperating area problem | The problem concerns the cooperating area. | B11 |
RDF/XML JSON-LD Turtle |
| Communication status currently active | The status within the system indicates that the communication capability is currently active. | B12 |
RDF/XML JSON-LD Turtle |
| Communication status currently inactive | The status within the system indicates that the communication capability is currently inactive. | B13 |
RDF/XML JSON-LD Turtle |
| Communication status currently restricted | The status within the system indicates that the communication capability is currently restricted. | B14 |
RDF/XML JSON-LD Turtle |
| Problem associated with both areas | The problem concerns both areas. | B15 |
RDF/XML JSON-LD Turtle |
| Tender unavailable in MOL list | A tender that has been requested is no longer available in the MOL. | B16 |
RDF/XML JSON-LD Turtle |
| Price based on preliminary exchange rate | The price is based on a preliminary exchange rate. | B17 |
RDF/XML JSON-LD Turtle |
| Failure | A failure has occurred. | B18 |
RDF/XML JSON-LD Turtle |
| Foreseen maintenance | Maintenance is foreseen. | B19 |
RDF/XML JSON-LD Turtle |
| Shutdown | A shutdown has occurred. | B20 |
RDF/XML JSON-LD Turtle |
| Official exchange rate approved | The official exchange rate has been approved. | B21 |
RDF/XML JSON-LD Turtle |
| System regulation | The information provided regards a regulation for system purposes. | B22 |
RDF/XML JSON-LD Turtle |
| Frequency regulation | The information provided regards a regulation for frequency purposes. | B23 |
RDF/XML JSON-LD Turtle |
| Load flow overload | Situation in the grid, where loading of a certain grid element, e.g. overhead line, is above defined technical limits. | B24 |
RDF/XML JSON-LD Turtle |
| Voltage level adjustment | A TSO activity to maintain an acceptable voltage profile throughout the network. This is achieved by balancing of the respective reactive power requirements of the network and the customers. | B25 |
RDF/XML JSON-LD Turtle |
| Emergency situation curtailment | Curtailment due to emergency situation. A code that enables the identification of the curtailment reason for settlement purposes. | B26 |
RDF/XML JSON-LD Turtle |
| Calculation process failed | The calculation has not been performed. | B27 |
RDF/XML JSON-LD Turtle |
| No capacity constraint impact on the market | The market position is such as no capacity constraint is applied to limit the cross border exchanges. | B28 |
RDF/XML JSON-LD Turtle |
| Special Condition | Special condition need to be fulfilled. | B29 |
RDF/XML JSON-LD Turtle |
| Unverified | Missing or not validated data. | B30 |
RDF/XML JSON-LD Turtle |
| Verified | Data has successfully passed the verification process. | B31 |
RDF/XML JSON-LD Turtle |
| CGM inconsistency | Describes an element which was not found in the CGM. | B32 |
RDF/XML JSON-LD Turtle |
| Network dictionary inconsistency | Describes an element which was not found in the network dictionary. | B33 |
RDF/XML JSON-LD Turtle |
| Capacity reduced by TSO | Describes a capacity that was reduced by a TSO. | B34 |
RDF/XML JSON-LD Turtle |
| Overload | Describes an N-k or N state overload. | B35 |
RDF/XML JSON-LD Turtle |
| GLSK limitation | Describes a situation in which there is not enough power adjustment in the GLSK file to cover the capacity. | B36 |
RDF/XML JSON-LD Turtle |
| Voltage constraint | Describes an N-k or N state voltage violation. | B37 |
RDF/XML JSON-LD Turtle |
| Angle constraint | Describes an N-k or N state angle violation. | B38 |
RDF/XML JSON-LD Turtle |
| Stability | Describes a situation in which the dynamic behaviour of the network violated. | B39 |
RDF/XML JSON-LD Turtle |
| Loadflow divergence | Describes a network situation in which the provided capacity values are part of a load flow divergence situation. | B40 |
RDF/XML JSON-LD Turtle |
| Exclusion for SoS reasons | This is the adjustment applied to the capacity of a branch to have a minimum RAM (Remaining Available Margin) available for commercial exchanges. | B41 |
RDF/XML JSON-LD Turtle |
| Constraint by the market | A constraint due to market restrictions. | B42 |
RDF/XML JSON-LD Turtle |
| Ordinary | The contingency is ordinary (methodology for coordinating operational security analysis, article 6). | B43 |
RDF/XML JSON-LD Turtle |
| Exceptional | The contingency is exceptional (methodology for coordinating operational security analysis, article 6). | B44 |
RDF/XML JSON-LD Turtle |
| Out of range | The contingency is out of range (methodology for coordinating operational security analysis, article 6). | B45 |
RDF/XML JSON-LD Turtle |
| Internal congestion | A temporary congestion within a bidding zone or scheduling area. | B46 |
RDF/XML JSON-LD Turtle |
| Operational security constraints | Operational security constraints identified by TSOs. | B47 |
RDF/XML JSON-LD Turtle |
| Estimated value | Describes a situation where a calculation process has failed and extrapolated or interpolated values will be applied. | B48 |
RDF/XML JSON-LD Turtle |
| Balancing | Activated for balancing purposes. | B49 |
RDF/XML JSON-LD Turtle |
| Values shared | Values of this time series are also valid for counter-party. | B50 |
RDF/XML JSON-LD Turtle |
| Outside price limits | The offered price is not within the valid limits. | B51 |
RDF/XML JSON-LD Turtle |
| Previous timeframe data | In case of processing issue, sent data are based on the previous timeframe. | B52 |
RDF/XML JSON-LD Turtle |
| MOL merging succesful | The merging of the Merit Order List has been successfully processed. | B53 |
RDF/XML JSON-LD Turtle |
| MOL merging failed | The merging of the Merit Order List has failed. | B54 |
RDF/XML JSON-LD Turtle |
| Because of redispatching | Because of redispatching according to Article 2(26) of Commission Regulation (EU) 543/2013 | B55 |
RDF/XML JSON-LD Turtle |
| Because of countertrading | Because of countertrading according to Article 2(13) of Commission Regulation (EU) 543/2013 | B56 |
RDF/XML JSON-LD Turtle |
| Because of other remedial action | Not available because of any remedial action. | B57 |
RDF/XML JSON-LD Turtle |
| Insufficiency of reserves | The reserve capacity is not sufficient. | B58 |
RDF/XML JSON-LD Turtle |
| Unavailability of reserve providing unit | The unit providing the reserve is subject to technical unavailability. | B59 |
RDF/XML JSON-LD Turtle |
| Unavailability of automatic protection systems | Unavailability of tools to detect predetermined system conditions that have a high probability of causing unusual stress on the power system, for which pre-planned remedial action is considered necessary or for which automatic protective actions may be triggered such as special protection schemes or automatic load shedding. | B60 |
RDF/XML JSON-LD Turtle |
| Physical cable or converter restrictions | Limitation due to physical cable or converter restrictions. | B61 |
RDF/XML JSON-LD Turtle |
| Constraints in controller systems | Limitation due to constraints in controller systems. | B62 |
RDF/XML JSON-LD Turtle |
| Adjusted because of expected violation of operational security | The capacity is adjusted because of an expected violation of operational security limits of physical transmission assets. | B63 |
RDF/XML JSON-LD Turtle |
| Adjusted because already considered remedial actions are assessed as not sufficient | The capacity is adjusted because the remedial actions were assessed as not sufficient or ineffective to avoid the expected violation of operational security limit(s). | B64 |
RDF/XML JSON-LD Turtle |
| Time series partially accepted | The time series is partially accepted. | B65 |
RDF/XML JSON-LD Turtle |
| Demand fully netted | Demand was fully netted against other demand(s). | B66 |
RDF/XML JSON-LD Turtle |
| Bid activated in same direction | One or several bids were activated in the same direction within the same uncongested area as the demand. | B67 |
RDF/XML JSON-LD Turtle |
| Optimization in progress | The activation optimisation framework is being executed. | B68 |
RDF/XML JSON-LD Turtle |
| Wrong energy market timeframe | The given energy market timeframe is invalid or wrong. | B69 |
RDF/XML JSON-LD Turtle |
| Message partially accepted | The detailed transactions of the received document are partially accepted. It is necessary to look at the detailed (transaction) level to determine if the transaction is accepted, rejected etc. | B70 |
RDF/XML JSON-LD Turtle |
Energy Reference Data
