DH-113 Request for customer information update – third party
Event description
A third party 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 it is responsible for the customer information in Datahub. If the customer in question only has a grid agreement in Datahub, the update request is forwarded to the DSO who last created an agreement with the customer. The DSO can then update the customer information in Datahub using its own update request (DH-112).
The third party reporting the event must have authorization to access the customer’s information at the time the update takes effect.
Parties
Third Party
Datahub
Supplier
DSO
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 customer information update (DH-111-4).
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.
Time limits
Effective time of the update | Notes/Exceptions |
|---|---|
The customer’s updated information is reported to Datahub immediately after being updated in the third party’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 |
Forwarding of the update request to the supplier/distribution system operator | 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. Otherwise Datahub checks whether the customer has a sales agreement (supplier with the rights to customer information). If it does have an agreement, Datahub forwards the information to the supplier who last created an agreement with the customer. If it does not, Datahub forwards the information to the DSO who last created a grid service agreement with the customer. |
Forwarding of the post office name | Datahub stores and forwards information on a post office located in Finland in upper case, even if the post office name is reported differently to Datahub. |
Return of information
Party | Description | Message |
|---|---|---|
Third party | Notification of successful or rejected customer information update or forwarding of information. |
Forwarding of information
Party | Description | Message |
|---|---|---|
Supplier | The update request is relayed 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. | |
DSO | If the customer has no sales agreements in Datahub, the update request is relayed to the DSO that made the most recent agreement with the customer in question. Note: The forwarded information shall not indicate where the update request came from. |
Composite processes
Party | Specification | Description | Composite process |
|---|---|---|---|
Supplier | The customer has a supplier | The customer information update request is forwarded to the supplier who most recently made an agreement with the customer. | |
DSO | The customer does not have a supplier | The customer information update request is forwarded to the DSO 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 or incompletely | 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 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 |
|
On the notification date, the customer must have a valid sales or grid agreement for some accounting point in Datahub. | EC.AGR.112 |
|
|
|
|
Please observe that the list is not complete. | ||