DH-111 Customer information update – supplier
Event description
The supplier updates the customer information in Datahub or replies to a customer information update request. As a reply to a customer information update request, current customer information can be reported too. Reporting current information means that the update request is rejected.
The supplier reporting the event must have a sales agreement with the customer that is either valid at the indicated time of the update, will become valid after the indicated update time, or has ended no more than six weeks before the update is reported to Datahub.
Parties
Supplier
Datahub
DSO
Third party
Balancing service provider
Important considerations for event handling
A customer information update must not be sent automatically based on any event forwarded to the party by Datahub (excluding customer information update requests DH-112-2 and DH-113-2), such as a customer information update message (DH-311-6) received based on a new sales agreement. An automatic update is allowed only as a response to a customer information update request from another party (DH-112-2/DH-113-2). However, a customer information update request may not be automatically rejected.
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.
The update of customer information must not automatically trigger another event, such as the update of agreement billing address (DH-321), unless the updated information also applies to the agreement.
Time limits
Effective time of the update | Notes/Exceptions |
|---|---|
The customer’s updated information is exported to Datahub immediately after being updated in the supplier’s system. |
|
The date the update 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. |
When a supplier responds to a customer data update request, the update should be reported within two working days of receiving the request. | Information about customer 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. |
Event processing in Datahub
Step | Description |
Partial update of customer data | When updating customer information, a partial update is used, where only the information entered in the event is updated. Data fields that are not included in the event retain their previous value. If information needs to be deleted from Datahub in the partial update, the data field in question is included in the event empty. For example, if only the customer’s e-mail address is reported in addition to the mandatory information in the update of the customer’s information, the only optional customer information that is updated is the e-mail address. If the customer already had, for example, a phone number, it remains unchanged. |
End of authorizations | If the customer is changed to private, all customer authorizations are ended. |
Information storage
Origin of information | Information stored |
Information reported by the party | The customer information reported by the supplier will take effect on the specified effective date. Old information is stored in Datahub. The supplier has the primary responsibility for the accuracy of customer information. |
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
Party | Description | Message |
|---|---|---|
Supplier | Notification of a successful or rejected customer information update. |
Forwarding of information
Party | Specification | Description | Message |
|---|---|---|---|
Supplier | All of the customer’s sellers | If the event contains updates to customer information, customer information is forwarded to suppliers who have a valid agreement with the customer at the time of entry into force, or whose agreement ended no more than 6 weeks earlier, or will become effective in the future. |
|
If the customer is changed to private, a notification of the change in authorization is sent to those parties whose authorizations were terminated. | |||
DSO | All of the customer’s DSOs | If the update includes changes to customer data, the information is forwarded to DSOs who have a valid or future agreement with the customer at the time of entry into force. | |
The DSO who requested the update | If the event is a reply to DSO’s update request (DH-112), it is forwarded to the DSO in question even if it does not contain any changes to customer information. | ||
Third party |
| If the update includes changes to customer information, the information is forwarded to third parties who have a valid authorization from the customer. Note: If the customer is private, the information included in the update is never forwarded to third parties. | |
If the customer is changed to private, a notification of the change in authorization is sent to the parties whose authorizations were terminated. | |||
Balancing service provider |
| If the customer is changed to private, a notification of the change in authorization is sent to the parties whose authorizations were terminated. |
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
An update is corrected with a new customer information update. If the update to be cancelled is in the future the cancellation is done with an update with the same start of occurrence. If the update to be cancelled is already valid, customer information can be corrected starting from the current date.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
A supplier must hold a sales agreement with a customer which is valid at the notified date of an update’s entry into force, enters into force after the notified update date, or has terminated no earlier than 6 weeks before the update is notified to Datahub. | EC.AGR.219 |
|
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. | ||