DH-112 Request for customer information update – DSO
Event description
The DSO updates customer information in its own system, which then notifies Datahub about the update request. The update request is forwarded to the supplier who has last created an agreement for the customer. The supplier will make the actual customer information update since they are responsible for the customer information in Datahub. If the customer in question only has a grid agreement in Datahub, the information is updated directly in Datahub on the basis of the DSO’s notification.
The DSO notifying the event must have an agreement with the customer that is either valid at the time the update takes effect or will become valid after the update time.
Parties
DSO
Datahub
Supplier
Third Party
Balancing service provider
Important considerations for event handling
A customer information update request must not be sent automatically based on any event forwarded to the party by Datahub, such as a notification of a new sales agreement (DH-311-2).
The update must be based on the customer’s verified need for an information update.
Updates to customer information made by a party in their own system must not trigger an update to Datahub if the update does not change the customer information maintained in Datahub.
A customer information update request must not automatically trigger another event, such the update agreement billing address (DH-322), unless the updated information also applies to the agreement.
Time limits
Effective time of the update | Notes/Exceptions |
|---|---|
The customer’s updated information is reported to Datahub immediately after being updated in the DSO’s system. |
|
The date the change takes effect may not be in the past and it can be at most 90 days in the future. | Validity periods are for whole days. |
Event processing in Datahub
Step | Description |
Comparison of stored and reported information | Datahub checks whether the information in the update request is the same as the currently valid customer information. If it is, a negative reply is returned, and no further actions are taken. If the request is a response to an update request, unchanged data is also allowed. |
Forwarding the update request to the supplier | If the request contains changed data (and is not a response to an update request), Datahub checks whether the customer has a sales agreement (i.e., a supplier with rights to the customer data). If so, Datahub does not store the reported data but forwards it to the supplier who last made an agreement with the customer for approval. If there is no supplier, Datahub updates the data directly based on the notification from the DSO. |
Termination of authorizations | If Datahub updates the customer data based on the DSO’s notification and the customer becomes private, all of the customer’s authorizations are ended. |
Information storage
Origin of information | Information stored |
Information reported by the party | Changed customer information and the date of the change if the customer only has a grid agreement. Old information is stored in Datahub. |
Datahub stores and forwards the name of a postal locality located in Finland entirely in uppercase letters, even if it is submitted in a different format by the reporting party. | |
Information processed by Datahub | Any potentially updated authorization information. |
Return of information
Forwarding of information
Party | Specification | Description | Message |
|---|---|---|---|
Supplier | Customer’s supplier | The update request is forwarded to the supplier that made the most recent agreement with the customer in question. Note: The forwarded information does not indicate where the update request came from. | |
Authorized supplier | If authorizations were terminated based on a notification from the DSO, a notification of the change in authorization is forwarded to the parties whose authorizations were ended. | ||
DSO |
| If the customer has no supplier, the updated customer data is forwarded to any other DSOs who have a valid or future agreement with the customer. | |
Third party |
| If the customer has no supplier, the updated customer information is forwarded to third parties who have authorization to access the customer’s information. | |
If authorizations were terminated based on a notification from the DSO, a notification of the change in authorization is forwarded to the parties whose authorizations were ended. | |||
Balancing service provider |
| If authorizations were terminated based on a notification from the DSO, a notification of the change in authorization is forwarded to the parties whose authorizations were ended. |
Composite processes
Party | Description | Composite process |
|---|---|---|
Supplier | The customer information update request is forwarded to the supplier who most recently made an agreement with the customer. |
Significant errors and consequences
Incorrect customer information is forwarded to all parties that are entitled to the customer information.
Maintaining the correctness of the information is the responsibility of the personal data registrar. Passing on incorrect personal data is a violation of data protection.
Error | Consequence |
|---|---|
The customer’s postal address is reported incorrectly | Possible mail (incl. invoices) is sent to the wrong address, especially if the agreement does not have a separate invoicing address. This may result in wrong collection actions or a violation of data protection. |
The customer’s contact information is reported incorrectly | It is impossible to contact the customer as the existing contact information is lost. |
The customer’s name information is reported incorrectly | Possible mail (incl. invoices) is not delivered or is delivered to a wrong recipient. |
Event cancellation
The cancellation is made with a new update message.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The distribution system operator must hold an agreement with the customer which is either valid on or after the date the notified update enters into force. | EC.AGR.306 |
|
The customer must be recorded in Datahub. | EC.CUS.113 |
|
The customer type cannot be changed. | EC.CUS.118 |
|
This event cannot be used to change a customer’s status from confidential (“non-disclosure”) to non-confidential. | EC.CUS.144 |
|
|
|
|
Please observe that the list is not complete. | ||