DH-126 Creating an accounting point relation

The information must be reported as soon as the DSO makes the change in its own system.

Start of occurrence can be 90 days in the past  at the earliest or maximum 90 days in the future.

When the change allowing the reporting of related accounting point information retroactively is implemented, retroactive corrections to related accounting point information will be permitted from 1.1.2023, for a separately defined period, after which the normal time limits will be applied. The operator will also have the possibility to allow retroactive corrections in exceptional situations beyond the normal time limits.

Step

Description

Participation of accounting points in netting calculation

Datahub takes the accounting points into netting calculations when a relation is reported if the production accounting point has production device(s) with a total maximum power of no more than 100 kVA. If the production accounting point has production device(s) without maximum power information, the accounting points are not taken into netting calculations.

Retroactive netting calculation during correction processes

If related accounting point information is corrected retroactively and the netting situation of the accounting points changes, Datahub will perform the calculations for the accounting points in connection with the update.

Origin of information

Information stored

Information reported by the party

All reported information is stored in Datahub.

Information processed by Datahub

Information on the participation of accounting points in netting calculation and, where applicable, the results of netting calculation performed based on the reported event.

DSO

Notification of a successful or rejected creation of an accounting point relation.

ACK

Supplier

When the relation information update is reported for the future (i.e., start of occurrence is in the future), the updated accounting point information is reported to the supplier associated with the accounting points on the reported start of occurrence.

In case of a retroactive update (i.e., start of occurrence is not in the future), the updated accounting point information is not reported to the supplier. Note: Possible (new) notifications will be added in a later version.

DH-122-2

Third party

When the relation information update is reported for the future (i.e., start of occurrence is in the future), the updated accounting point information is reported to the third parties associated with the accounting points with consideration to the parties’ rights to information on the reported start of occurrence.

In case of a retroactive update (i.e., start of occurrence is not in the future), the updated accounting point information is not reported to third parties. Note: Possible (new) notifications will be added in a later version.

DH-122-3

Information is incorrectly reported

Datahub performs the netting calculations with wrong information.

The accounting points must be recorded in Datahub on the reported date of entry into force.

EC.MPT.108/
EC.MPT.115

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 points must be part of the same reported metering grid area.

EC.MPT.157

One of the reported accounting point types must be ‘Consumption’ and the other must be ‘Production’.

EC.MPT.136

The notified accounting points cannot already have related accounting points.

EC.MPT.156

The reported consumption accounting point cannot be part of an energy community whose surplus allocation method is ‘SMB’.

EC.MPT.172

If both of the reported accounting points are part of an energy community, both must be part of the same energy community.

EC.MPT.177