DH-116 Customer merging

1 Event description
2 Parties
3 Time limits
4 Event processing in Datahub
5 Information storage
6 Return of information
7 Forwarding of information
8 Significant errors and consequences
9 Event cancellation
10 Validation rules

Customer merge

Event description

A customer merge process is initiated when a market party tries to update the customer ID from type “Party’s own identification (AA04)” to “Personal ID (AA03)” or “Business ID (AA01)” and the update is rejected because the reported identification already exists in Datahub. The market party then requests the Datahub operator to update the customer ID (= merge customers). This request is not made in Datahub. The requesting party (supplier or DSO) must have a valid sales or grid agreement with the customer either at the requested update time or later, or (only the supplier) an agreement that ended no more than six weeks earlier.

Parties

Datahub
Supplier
DSO

Time limits

Effective time of the update	Notes/Exceptions

Effective time of the update	Notes/Exceptions
The merge is done from the start date of the customer, using the party’s own identification.

Event processing in Datahub

Step	Description
Transferring/copying agreements to the customer	All agreements of the customer with customer identification type Party’s own identification are transferred/copied to the customer with customer identification type Personal identity number/Business ID.
Deactivating the customer	The customer with customer identification type Party’s own identification is deactivated after the merge.

Information storage

Origin of information	Information stored
Information processed by Datahub	Transferred agreements and deactivated customer.

Return of information

Party	Description	Message

Party	Description	Message
Datahub	Notification of a successful or rejected customer merge to the Datahub operator.	-

Forwarding of information

Party	Specification	Description	Message

Party	Specification	Description	Message
Supplier		The notification of the update is sent to suppliers who, at the time of the notification, have a valid sales agreement, a future-dated sales agreement, or a sales agreement that ended no more than six weeks ago with the merged customer (identified by the party’s own identifier).	DH-116-3
DSO		The notification of the update is sent to DSOs who, at the time of the notification, have a valid or future-dated network agreement with the merged customer (identified by the party’s own identifier).	DH-116-2

Significant errors and consequences

Error	Consequence

Error	Consequence
Customer merge is done for wrong customers.	-

Event cancellation

This process cannot be cancelled.

Validation rules

Please see Datahub Validation Rules for a more thorough list.

Rule	Error code	Note

Rule	Error code	Note
The updated customer is recorded in Datahub and is either residential or business customer type.
If a residential customer whose identifier is a party’s own identifier (AA04) is confidential (non-disclosure) and a customer with a personal identification code is not, the process is interrupted.

Please observe that the list is not complete.