Change history

Development proposal #039

Datahub’s new authorization service.

5.11.2025 process maps added.

• Authorization service

• Process maps for the authorization service

Development proposal #081

Datahub’s new authorization service.

5.11.2025 process maps added.

• Authorization service

• Process maps for the authorization service

Development proposal #216

Datahub’s new authorization service.

5.11.2025 process maps added.

• Authorization service

• Process maps for the authorization service

Development proposal #377

Datahub’s new authorization service.

5.11.2025 process maps added.

• Authorization service

• Process maps for the authorization service

Development proposal #337

New processes for authorization requests.

14.10.2025 Corrected contents of messages F30 and F31 in accordance with the schema.

• Code lists

• DH-800 End customer authorizations

  • DH-820 Customer’s authorization from customer

    • DH-820 Process maps

    • DH-821 Customer authorization notification to supplier

    • DH-822 Customer authorization notification to a third party

    • DH-824 Customer authorization notification to balancing service provider

  • DH-830 Party’s authorization request to customer

    • DH-830 Examples

    • DH-830 Process maps

    • DH-831 Supplier’s authorization request to customer

      • DH-831-1 Authorization request to customer – supplier

    • DH-832 Third party’s authorization request to customer

      • DH-832-1 Authorization request to customer – third party

    • DH-834 Balancing service provider’s authorization request to customer

      • DH-834-1 Authorization request to customer – balancing service provider

  • DH-850 Authorization request cancellation

    • DH-850 Examples

    • DH-850 Process maps

    • DH-851 Authorization request cancellation – supplier

      • DH-851 Authorization request cancellation (supplier)

    • DH-852 Authorization request cancellation – third party

      • DH-852 Authorization request cancellation (third party)

    • DH-854 Authorization request cancellation – balancing service provider

      • DH-854 Authorization request cancellation (balancing service provider)

  • DH-860 Request for authorization requests

    • DH-860 Examples

    • DH-860 Process maps

    • DH-861 Request for authorization requests – supplier

      • DH-861-1 Request for authorization requests – supplier

      • DH-861-2 Return of authorization requests – supplier

    • DH-862 Request for authorization requests – third party

      • DH-862-1 Request for authorization requests – third party

      • DH-862-2 Return of authorization requests – third party

    • DH-864 Request for authorization requests – balancing service provider

      • DH-864-1 Request for authorization requests – balancing service provider

      • DH-864-2 Return of authorization requests – balancing service provider

• Events, messages and roles

• F30 Authorization request information

• F31 Request for authorization request

• F32 Authorization request cancellation

Development proposal #049

• General interface specifications for the data interface

Development proposal #082

New interface for continuous delivery of metering data.

• DH-210 Reporting metering data

Development proposal #093

A supplier can cancel a retroactive agreement notification if the retroactive start requires handling by the supplier in the Datahub user interface.

• DH-311 Notification of a new agreement

• Retroactive error correction

Development proposal #110

The distribution system operator is notified of the termination of a sales agreement even in cases where the corresponding grid agreement has been terminated but has an open event for cancellation of the termination. In this case, the process does not create an open event for the termination of the grid agreement.

• Composite processes

• DH-330 Process maps

• DH-331 Notification of sales agreement termination

Development proposal #121

Event DH-344 has been removed.

• DH-344 Grid agreement termination notification upon cancellation

Development proposal #199

A supplier can cancel a retroactive agreement notification if the retroactive start requires handling by the supplier in the Datahub user interface.

• DH-311 Notification of a new agreement

• Retroactive error correction

Development proposal #271

New instructions for updating the annual consumption estimate.

• DH-120 Accounting point information maintenance

Development proposal #348

The Datahub operator can update a party’s business ID or name in the Datahub user interface, as long as the GLN remains unchanged.

• Datahub operator correction processes

Development proposal #351

Improving the flexibility of exchange point authorizations’ validity and renewal.

• Party authorizations

Development proposal #353

A notification is sent to the authorized party if the validity of the authorization is updated to match the agreement start date or is fully cancelled during the connection process.

• DH-412 Notification of supply connection

Development proposal #364

Improving the flexibility of exchange point authorizations’ validity and renewal.

• Party authorizations

Development proposal #376

In the agreement termination cancellation process, authorizations are reinstated if the original agreement termination has ended or cancelled them.

• DH-351 Cancellation of sales agreement termination

• DH-352 Cancellation of grid agreement termination

Development proposal #384

Improving the flexibility of exchange point authorizations’ validity and renewal.

• Party authorizations

Development proposal #406

It is no longer possible for a party to submit a customer authorization notification on their own behalf (DH-811, DH-812, DH-813). Instead of these notifications, new authorization requests (DH-830 messages) must be used, and the customer must personally approve the authorization request sent by the party in the new Datahub authorization service.

• DH-810 Customer’s authorization from a party

  • DH-811 Customer authorization notification – supplier

    • DH-811 Customer authorization notification (supplier)

  • DH-812 Customer authorization notification – third party

    • DH-812 Customer authorization notification (third party)

  • DH-813 Customer authorization notification – DSO

Development proposal #535

Changes required in the authorization processes due to the upcoming load control functionality.

• Code lists

• DH-800 End customer authorizations

• DH-825 Customer authorization notification to load control service provider

  • DH-825 Customer authorization notification (to load control service provider)

• DH-835 Load control service provider’s authorization request to customer

  • DH-835-1 Authorization request to customer – load control service provider

• DH-845 Notification by party of termination of authorization – load control service provider

  • DH-845 Notification by party of termination of authorization (load control service provider)

• DH-855 Authorization request cancellation – load control service provider

  • DH-855 Authorization request cancellation (load control service provider)

• DH-865 Request for authorization requests – load control service provider

  • DH-865-1 Request for authorization requests – load control service provider

  • DH-865-2 Return of authorization requests – load control service provider

• F15 Authorization information

• F29 Authorization information, authorization termination

• F30 Authorization request information