We allow bulk changes to the Client File by uploading documents. This way you can, for example, add new parties, update product data, upload documents, create connections between parties.
Scope of this article
There are a few ways to get your data into the Client File. This article covers the new bulk update functionality in Client File.
The article does not cover:
Transferring an onboarding case to the Client File;
Building an integration with our API's;
Using the old import functionality in Client File;
Using the old bulk file upload functionality in Client File.
The new method of importing data in the Client File aims to replace the previous version of the import functionality in the future.
Steps of bulk updating data
There are a couple of steps we will be going through:
Data preparation
In this step we will collect the data from the source and will convert it into the data format, expected by the Client File.
Data validation
The Client File will now validate your file and its data. In this step you still may (or sometimes have to) make some changes to the file you want to process.
Data import
When all data has been reviewed and has passed validation, the data will be imported and will become visible in Client File.
Data preparation
The Client File requires a csv file format for imports. By using the csv template, provided by Blanco, you can be sure to use the correct column names and thereby avoid validation errors.
It is possible to download the csv template by clicking the "Download template" button.
The template may look like this when opened in an application to edit CSV files:
The first line in the CSV is always the header. Every other line in the file is either a Party, Product or Connection.
Party; Either a natural person, legal entity or natural person group (joint)
Product; The entity that holds the client contract. Every client has at least one product.
Connection; Can be used to connect a product to a party and also to create a structure of multiple parties.
You may add as much as 50.000 lines in one csv file.
Some fields are straightforward, others require some extra attention. Fields which need a bit extra attention, we will address here:
Field | Value |
entityType | PARTY, PRODUCT, CONNECTION |
partyId, productId | This is the ID from the entity in the Client File, which is required in case you want to update it. When importing a new entity, this field should be empty. You for example could use the Client or Product Overview export to get all ID's from the application. |
np_gender | M, F |
np_dateOfBirth, prd_endDate | Date format: dd/mm/yyyy |
np_countryOfBirth, np_nationality, country, taxResidenceCountries | Alpha-2 country code, according to the ISO 3166 standard |
np_insider, US_person | TRUE, FALSE |
phone | Format international notation. Example: +31612345678 |
le_legalActivities | Legal activities for a legal entity. Read more: Field: Legal activities |
prd_productName | This field can only contain product names, which are configured here: https://backend.blanco-acc.cloud/administration/settings/products |
prd_investmentObjective | RETIREMENT, INVESTMENT, SPECIFIC_GOAL, FINANCIAL_BUFFER |
prd_investmentGoal | Number field, '.' as decimal delimiter |
prd_profile | This field can only contain profiles, which are configured here: https://backend.blanco.cloud/administration/settings/products |
Field: Legal activities
Column header: le_legalActivities
The content of this column is a comma separated list of legal activities. Each legal activity consists of a classification, code and description, separated by a pipe (|).
Example: classification_1|code_1|description_1,classification_2|code_2|description_2,classification_n|code_n|description_n
The field is handled as follows:
When classification is empty, you will receive a validation error.
example:|1234|descriptive textWhen the description and code are both empty:
example:NACE||On creation this item is ignored.
On update this item triggers the removal of all existing legal activities for classification.
When classification is "NACE”, a code is provided and the description is empty
example:NACE|9200|The description is filled in automatically based on the KYC Suite NACE code table. Translations for English, Dutch and French are provided.
In any other case.
example:NACE|9200|Not gamblingA legal activity record is created according to the input. We allow input of any code and description, it will not be checked on validity. We do not support translations for legal activities that are created in this manner.
Data validation and review
When you have your csv files prepared, you may proceed to click the button "New import".
Here you can add one, or multiple csv files you would like to import, assign the import process to either yourself or a colleague (not required) and start the validation.
Check if the "Status" of the documents is "Completed", which means that the file has been uploaded successfully. Click "Start validation" to start validation of the selected csv file.
When validation has finished, you can review your data, by expanding the file and viewing the records. If there are records with validation errors, they will be shown first in the list.
In case you have made a mistake in a single field, you can update this field in the review screen, and revalidate the import.
Tip: If you have made a mistake in a single column of your csv, for all of the entities, we recommend to revisit your csv file, rather than updating the individual records in the UI, since fixing the data in the application would be relatively time consuming. (For example if a data format was incorrect, or when a phone number is not matching the international standards).
When all records have passed validation, the import button will become active, which you can click to start the actual import.
Data import
During the data import, the data gets added to the Client File. When this step is done, you can view your new data in the Client File.