DH-210 Reporting metering data
The rule of thumb is that only new and changed metering data should be reported to Datahub. There is no need to report metering data for entire 24-hour periods. Datahub sends metering data by the same period as it was received in Datahub. Changes in status are also interpreted as a change to metering data, even if the metering data itself remains the same. Datahub rejects unchanged metering data per time series if the delivered time series (transaction) contains only unchanged metering data in terms of both measured value and status.
It is usually the obligation of the metering responsible party at the metering point to report data to Datahub. At accounting points, the metering responsible party is always the DSO. The metering responsible party is often different from the DSO, for example, at exchange points, where the metering responsible party could be the main grid owner.
Time limits for reporting metering data
Time limits for reporting metering data to Datahub are determined in accordance with the decree of the Ministry of Economic Affairs and Employment of Finland concerning information exchange related to electricity delivery settlement. Preliminary metering data for the previous day must be reported to Datahub by midnight on the following day. In accordance with the Government Decree on the Settlement and Measurement of Electricity Supplies (767/2021), starting from 1 January 2026 metering data must be collected from new generation meters at least every six hours and the metering data must be delivered to Datahub without undue delay if the DSO has designated Datahub as the point of delivery for this data. The metering data delivery practices applicable from 1 January 2026 are described in the document Datahub - E66 Batch Interface Guidelines.
In accordance with the imbalance settlement schedule, a DSO’s final metering data for imbalance settlement must be reported to Datahub for a delivery date of 11 days ago by 24:00 (EET/EEST), after which time the balance window for the delivery date in question will close. Datahub will have the next day to carry out imbalance settlement calculations and report the calculation results to eSett. During this time, Datahub processes and validates metering data, carries out calculations and submits the data to eSett. Sufficient time should be reserved for these actions in order to comply with imbalance settlement time limits in all situations.
It is not permitted to report future metering data or very old metering data (older than 6 years).
Metering data validation
The responsibility for validating metering data and submitting accurate metering data to Datahub lies with the metering responsible party. Datahub carries out simple validation for metering data in cases where the DSO’s validation is not at a sufficient level. The most significant validation carried out by Datahub is status validation, the rules for which are set out in section Status processing.
Datahub performs validation on negative and excessive values, depending on the type of metering point. A value is deemed to be excessive if it is more than ten times (hourly measurement) or 2.5 times (15 minute measurement) the electric power that was reported for the accounting point. Production capacity is used respectively as a benchmark for production units. If the electric power for an accounting point is not reported to Datahub, the fuse size should be reported, whereupon electric power will be calculated from the fuse size.
Metering data can be sent with an accuracy of at most 1 Wh, and Datahub validates the number of allowed decimal places depending on the unit used. For example, in the kWh unit, data can be reported with a maximum of three decimal places.
Metering time series data rejected in validation will not be stored in the database and will return time series-specific rejection information. The table below lists validations carried out by Datahub by metering type.
Metering type | Reasons for rejection |
Accounting point consumption | Erroneous status, negative values, values which exceed electric power by a factor of 10 (hourly measurement) or 2.5 (15 minute measurement), wrong number of decimal places |
Accounting point production | Erroneous status, negative values, values which exceed production capacity by a factor of 10 (hourly measurement) or 2.5 (15 minute measurement), wrong number of decimal places |
Reactive energy output/input | Erroneous status, negative values |
Exchange point metering | Erroneous status, negative values, wrong number of decimal places |
Production unit metering | Erroneous status, negative values, values which exceed production capacity by a factor of 10 (hourly measurement) or 2.5 (15 minute measurement), wrong number of decimal places |
Status processing
The table below outlines the statuses used in Datahub from weakest to strongest and also the time limits according to which the status must be replaced with a stronger status. The guidelines published by Finnish Energy regarding meter data status processing have been taken into account in Datahub’s status processing.
Status | Explanation | Permitted replacement statuses |
Missing | Used if no data has been obtained from the meter and preliminary data is sent as zero use. The status of data denoted as ‘Missing’ must always be replaced with a stronger status within 5 days. | (As necessary) Missing, Uncertain, Estimated, OK, or Corrected OK |
Uncertain | Used when it is assumed that data may become more detailed or change later on. The ‘Uncertain’ status is most typically used when it is necessary to estimate missing metered data, but it is assumed that the data will be obtained later on. Data assigned an ‘Uncertain’ status must primarily be replaced with a stronger status before the balance window closes. Also used for reading metering profiles when the profile is calculated based on an annual use estimate. | Uncertain, Estimated, OK, or Corrected OK |
Estimated | Used when it is necessary to estimate metered data and it is known that no data or more detailed data will be obtained later on. | Estimated, (As necessary) OK, or Corrected OK |
OK | Used for metered data obtained from the meter, if there is no reason to assume that the meter value is erroneous. Also used for reading metering profiles when time series values are calculated from the meter reading. | (As necessary) OK, (As necessary) Corrected OK |
Corrected OK | Used when metered data previously sent with an ‘OK’ or ‘Estimated’ status nevertheless has to be corrected. | Values may be changed, but it is not possible to replace the status with a weaker status. |
In exceptional situations, the status may remain uncertain even after the closure of the imbalance settlement window.
Statuses may be replaced with an equally strong or a stronger status. Datahub will not reject metering data if the status is not within the time limits set out above. Datahub will however reject metering data if attempts are made to replace metering data with a status that is against permitted replacement statuses. Monitoring will be used to identify and take action to stop market parties who deviate from the above-mentioned rules.
In sum calculations, such as calculating a supplier’s metered sum delivery, the status of the sum time series is determined in accordance with the time series that has the weakest status of all of the time series used in the calculations.
Monitoring of metering data reports
Datahub sends reminders to the DSO or metered data responsible, if the DSO has delegated this role to a third party. If parties fail to comply with the reporting time limits and status processing instructions set out above, reminders will be sent when:
Preliminary metering data for the day of delivery (the previous day) has not been reported at all by the end of the day
Data assigned a ‘Missing’ status has remained unestimated for 5 days after delivery or
There is still metering data with an ‘Uncertain’ status after the balance window has closed.
In the first two cases set out above, reminders will be sent once a day until metering data is corrected or submitted, for a maximum of 30 days. In the last case, a reminder will be sent only once, because in some situations there is a reason to retain an ‘Uncertain’ status even after the balance window has closed. However, reminders of metering data with ‘Uncertain’ status will not be sent for reading metered metering points.
Reminders will only be sent once the relevant time limit has been exceeded. The industry will largely trust the DSOs to comply with agreed rules and to implement the necessary processes for these purposes in their own system. The purpose of reminders is to draw attention to non-compliance with rules. If a DSO does not change its operating methods despite repeated reminders, action will be taken. Reminders will be sent only for valid metering points and only if the accounting point grid agreement is valid.
The DSO users must determine in the Datahub user interface whether electricity can be transmitted in only one direction or both directions at an exchange point. For exchange point measurements, metering data delivery is monitored separately for each direction. If metering data is reported as belonging to “the wrong direction” for an exchange point, this will be reported to the DSO.
In addition to aforementioned reminders, DSOs will be notified if other than zero values are reported to disconnected accounting points. In these cases, the DSO must find a reason for non-zero values and correct either the metering data or the accounting point status. Reminders are sent once a day until the information is corrected, for a maximum of 30 days.
Forwarding metering data
All metering data sent to Datahub is automatically forwarded to all parties entitled to receive the data. If the DSO has delegated metering data reporting to a service provider, the metering data reported by the service provider can be forwarded to the DSO. Datahub forwards metering data to only one system for each party. If a party needs metering data in more than one of its own systems, the party is responsible for distributing the metering data between its own systems. If for some reason a party does not require automatic data transmission in its own operations, the party can opt out of data transmission in the Datahub user interface. In such cases the party can use the separate metering data retrieval event (DH-220).
The metering data forwarding message includes the time when time series data was stored in Datahub. Based on this information, the recipient can determine whether the received metering data has been included in the balance when metering data is reported near the closing of the balance window. Metering data is always forwarded with the same resolution as it is reported to Datahub.