DH-122 Accounting point information update

The information update must be reported as soon as the DSO makes the change in its own system. Start of occurrence of the update is either the current day or maximum 10 years in the past.

If the accounting point update is done as answer to an update request by another party, the update should be reported in 30 days at the latest.

Information about accounting point update is still accepted after this period but there will be intervention in the case of notifications that are sent late on a repetitive basis.

Step

Description

Connection capacity of the accounting point

Datahub calculates the connection capacity based on fuse size if connection capacity is not otherwise specified.

Origin of information

Information stored

Information reported by the party

All reported information is stored in the database.

Datahub stores and forwards information on a post office located in Finland in upper case, even if the post office name is reported differently to Datahub.

Information processed by Datahub

Connection capacity, if not specified in the message.

DSO

Notification of a successful or rejected accounting point update.

ACK

Supplier

Accounting point’s supplier

If the update includes changes to valid information, the information contained in the update will be forwarded to the supplier associated with the accounting point at the effective time of the update.

If an accounting point information update is reported retroactively more than 6 weeks after the supplier’s agreement has ended, the update will not be forwarded to the supplier even if the supplier’s agreement would have been valid at the start of occurrence of the update.

DH-122-2 (Accounting point information update)

DH-122-4 (Annual consumption estimate update)

Accounting point’s supplier who requested the update

The DSO’s response to the supplier’s update request. As a response to the supplier’s request, the update is forwarded even if it does not contain any changes.

If an accounting point information update is reported retroactively more than 6 weeks after the supplier’s agreement has ended, the update will not be forwarded to the supplier even if the supplier’s agreement would have been valid at the start of occurrence of the update.

DH-122-2 (Accounting point information update)

DH-122-4 (Annual consumption estimate update)

Third party

Accounting point’s third party

If the update includes changes to valid information, the information contained in the update will be forwarded to third parties associated with the accounting point at the effective time of the update, taking into account their rights to the accounting point information.

DH-122-3 (Accounting point information update)

DH-122-5 (Annual consumption estimate update)

Accounting point’s third party who requested the update

The DSO’s response to the third party’s update request. As a response to the third party’s request, the update is also forwarded even if it does not contain any changes.

DH-122-3 (Accounting point information update)

DH-122-5 (Annual consumption estimate update)

Information is reported incorrectly

Suppliers and third parties can make incorrect agreements with a customer. Incorrect meter values in, for example, imbalance settlement or load control.

The accounting point is recorded in Datahub and is valid on the agreement start date. 

EC.MPT.115

The notified time of entry into force of the accounting point is midnight.

EC.MPT.107

The accounting point must not have the status ‘Removed from use’ or ‘Deleted’.

EC.MPT.120

The metering grid area must belong to the reporting distribution system operator.

EC.MPT.103

The accounting point is part of the reported metering grid area.

EC.MPT.116

If the accounting point sub-type is the production unit’s own use, the accounting point type must be ‘Consumption’.

EC.MPT.148

If the accounting point type is production, the metering method must be continual metering.

EC.MPT.149

The accounting point status cannot be updated to change to ‘Connected’, ‘Disconnected’ or ‘Deleted’. Updates to this status are made using the Connection, Disconnection or Accounting point deletion events.

EC.MPT.119

If the accounting point is being updated to the ‘Removed from use’ status, the accounting point cannot have agreements in the system which are valid or entering into force on the date of the update’s entry into force.

EC.MPT.121

The accounting point’s creation event cannot be used to report information about a related accounting point or energy community.

EC.CPF.024

If the accounting point is part of an energy community at or after the moment of the update’s entry into force, its status cannot be changed to ‘Removed from use’ before the accounting point has been removed from the energy community.

EC.MPT.174

If the accounting point has a related accounting point at or after the moment the update enters into force, the status of the accounting point cannot be changed to ‘Removed from use’. No validation is conducted if the related accounting point is already of the status ‘Removed from use’ or ‘Deleted’.

EC.MPT.181

If a production accounting point is part of netting calculation at or after the time the update enters into force, not all production devices may be removed from the accounting point.

EC.MPT.179

If a production accounting point is part of netting calculation at or after the time the update enters into force, production devices with an aggregate rated capacity greater than 100 kVA cannot be reported for the accounting point using an update event.

EC.MPT.180

If a production accounting point has a related accounting point at or after the time the update enters into force, but the accounting points are not part of netting calculation, production devices with an aggregate rated capacity of exactly 100 kVA or below cannot be reported for the accounting point using an update event.

EC.MPT.180