Datahub operator correction processes

The main rule in Datahub is that the information stored in Datahub always comes from the market parties. However, there are situations where the parties are unable to update their data using normal processes and need support from the market operator. In this case, the operator, using its admin rights to the system, carries out the necessary process, either on behalf of the market party or customer.

Corrections to agreement processes

Concerning agreement processes, the retroactive agreement notifications documentation states that if sales agreement of several different suppliers are valid at the accounting point between the start date of the retroactively reported sales agreement and the time of the notification, the parties cannot agree on a retroactive agreement by themselves. In this case, the market operator will then investigate the situation and proceed with the needed corrections. Depending on the situation, the market operator cancels the pertinent agreements and notifies about the termination of the remaining agreement, if necessary. No notifications will be sent to the market parties about agreement cancellations made by the operator from Datahub. If the market operator terminates the sales agreement under this repair chain, a notification will be sent to that supplier in accordance with the DH-331 process.

Agreement terminations will never be reported retroactively in accordance with the normal process, except when the DSO removes meters. If a market party needs to correct an agreement so it ends retroactively, the party notifies the market operator, who can make this retroactive termination (for example, if an end customer goes bankrupt). Retroactive endings can be made for both sales and grid agreements. Notifications of retroactive agreement endings by the market operator are normally sent to the other market parties and to the party whose agreement has been ended by the operator.

In addition to corrections to agreement information, corrections to balance data are the most frequent type. When investigating corrections, the market operator also confirms the status of the balance information with the market parties and makes the necessary corrections to the balance information on the basis of the information thus received. There will be no notifications of the corrections to the balance information made by the market operator.

The market operator will also handle customer disputes which the DSO has notified it of. Disputing an agreement is described in this section: The customer disputes a sales agreement. If the market operator delivers the customer dispute, Datahub will send a notification to the supplier of the disputed agreement with the reason code AR05 – Agreement dispute by market operator.

Datahub’s initial data was imported by data migration. All rules for information stored using ordinary Datahub processes cannot be used for information originating from the data migration. An example of this is agreement cancellations. Cancellation processes have many rules regarding previous agreements. For agreements imported using data migration, no prior information exists in Datahub, meaning that agreements from data migration cannot be cancelled using normal cancellation processes. If the market parties need to cancel an agreement originating from the data migration, they need to notify the market operator, who will then process the cancellation in Datahub. If there is a need to restore a previous agreement that does not exist in Datahub, the market operator will ask the previous supplier to report this agreement to Datahub.

Corrections to customer information

For customer information, parties have the rights to maintain all other information except the customer ID. If the customer ID needs to be corrected, the market party notifies the market operator. The market operator will make the necessary corrections to Datahub, and all parties entitled to this particular customer’s information will be notified. The market operator can also correct customer data retroactively upon request when errors are corrected (data protection issues). No notification will be sent to the parties regarding retroactive corrections of customer data.

Market parties may change a customer identifier of the type ‘party’s own identification’ to ‘personal identification code’ or ‘business ID’ with the customer information update process. When the customer’s personal identification code or business ID already exists in Datahub, Datahub rejects the change request. The market party must then inform the market operator, who can merge a customer identified by the party’s own identification with the existing customer information using personal identification code or business id. The agreement information of the customer with the party’s own identification is then linked to the customer already existing in Datahub with personal identification code or business ID.

Concerning residential customers, the rule is that the residential customer manages their own authorizations through the Datahub customer portal. If for some reason a residential customer is unable to terminate an authorization they have made in the customer portal, the customer may ask the market operator to terminate the authorization on their behalf. This authorization is always terminated on behalf of the party who has the authorization from the customer. A notification of the authorization termination is sent to the party whose authorization was terminated.