DH-113-1 Request for customer information update – third party
Message DH-113-1 is of message type F01.
Message payload includes the following information:
Information field | Level | Necessity | Field content | Note |
|---|---|---|---|---|
Payload | 1 | 1..1 |
|
|
Start of occurrence | 2 | 1..1 |
|
|
Description | 2 | 0..1 |
|
|
Basic customer information | 2 | 1..1 |
|
|
Customer identification | 3 | 1..1 |
| If a personal identity code is provided, it must comply with the format requirements for personal identity codes. If a party’s own customer identification is used, it must be provided as <notifying supplier’s identification>_<customer number> (used as specifying data in a situation in which the personal identity code is not known or business ID does not exist). |
Customer identification type | 3 | 1..1 |
| If the customer type is consumer, customer identification type must be either personal identity code or party’s own identification. If the customer type is company, customer identification type must be business ID or party’s own identification. |
Customer type | 3 | 1..1 |
|
|
Customer sub-type | 3 | 0..1 |
|
|
Information restriction | 3 | 0..1 | Yes/No |
|
Language | 3 | 0..1 |
|
|
Company name | 3 | 0..1 |
| The company's official name according to the Business Information System YTJ which can be found in the trade register. In case of an association, the registered name of the association is used. The maximum length of the company name in Datahub is 200 characters. If the name is longer, it is still written according to the official name and the name is truncated after 200 characters. |
Given name | 3 | 0..1 |
| The consumer customer name must not contain numbers. The first letter of a consumer customer’s first and middle name must be in uppercase, and the following letters in lowercase. For multi-part first and middle names, the first letter of each part must be in uppercase, and the following letters in lowercase (e.g., Hanna-Kaisa). |
Middle names | 3 | 0..1 |
| |
Family name | 3 | 0..1 |
|
|
Date of birth | 3 | 0..1 | Mandatory for a consumer customer, if no personal identity code has been provided YYYY-MM-DD |
|
Additional identification | 3 | 0..1 |
| If a business customer also needs to have a personal identity code, it is reported in the additional identification field. |
Contact information | 3 | 0..2 |
| One telephone number and one e-mail address may be specified for a customer. |
Contact information type | 4 | 0..1 |
|
|
Telephone number Email address | 4 | 0..1 |
| The reported telephone number or email address must be in the correct format (see Datahub Datastandard). The information must be the customer’s actual contact information through which the customer can be reached if necessary. Contact information should be left blank if it is not known. A phone number must start with a plus ’+’. A phone number may not contain spaces. The country code ‘+358’ may not be followed by the number zero. |
Postal address | 3 | 0..1 |
| Address information must contain the postal code and either street name and building number or PO Box. Address information may not contain both PO Box and street address information (street name, building number, stairwell identification or apartment). If any data needs to be removed from customer information, the field in question will be sent empty. |
Address specifier | 4 | 0..1 | c/o |
|
Street name | 4 | 0..1 |
|
|
Building number | 4 | 0..1 |
| When the address is in Finland, the building number field:
|
Stairwell identification | 4 | 0..1 |
| Rules for the stairwell identification field:
|
Apartment | 4 | 0..1 |
| When the address is in Finland, the apartment field:
|
Postal code | 4 | 0..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
PO Box | 4 | 0..1 |
|
|
Post office | 4 | 0..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
Country | 4 | 0..1 | ISO 31661 alpha-2 ID is used. |
|