PEPData - Knowledge Repository
English
English
  • The Application
    • Transaction Register
      • Transaction risk categorization
    • Customer Register
      • Customer import
      • Risk categorization of individual persons/organizations
  • API
    • Overview
    • Validations
    • Registers
    • Search
    • Adverse Media
    • Beneficial Owners
    • Users
    • PEPData list integration
    • Examples of use
Powered by GitBook
On this page
  • Details of files to import
  • General Details
  • Organizations file
  • Individual persons file
  • File of relationships between individual persons and organizations

Was this helpful?

  1. The Application
  2. Customer Register

Customer import

The new customer import allows you to easily and quickly upload your customers to the platform, automatically creating a registration for each customer.

To do so, please divide the information to be imported into 3 different files:

  • Organizations

    • File with your organizational customers

  • Individual persons

    • File with the members of the administration and beneficial owners

  • Relationships between individual persons and organizations

    • File that maps the relationships between the organizations and individuals mentioned above

    • This must be the last file to be imported, only being accepted if the remaining two have already been inserted

After creating these 3 files, you can import them using the "Import Records" button on the "Customer Register" page.

Details of files to import

General Details

  • The first line must contain the name of the columns that represent the information to be imported

  • The separation of columns should be done by semicolon (;), to .txt and .csv files

  • Extension: .txt, .csv or xlsx

  • Limited to 700,000 rows per import

Organizations file

  • Must contain one organization per line

  • Accepted properties (mandatory in bold):

Fields
Notes

id_custom

Customer identifier used by your organization. It has to be unique.

name

brand_name

Brand name.

vat_number

responsible_email

Email of the user who will be responsible for the customer's questionnaire. Must be a user entered in your organization.

invited_email

Email of the person to be invited to complete the questionnaire. Note: the invitation will have to be sent manually after insertion.

corporate_object

foundation_date

Should follow one of the following formats:

  • dd-mm-yyyy

  • dd/mm/yyyy

  • yyyy-mm-dd

  • yyyy/mm/dd

nace_codes

NACE codes. Separated by semicolons if there are multiples.

country_constitution

operations_countries

Separated by semicolons if there are multiples.

is_identified

0, in case there is no identification.

country_address

address_postal_code

address

address_door

address_district

address_city

has_branch_offices

1 or 0, whether there are branches or not, respectively.

adverse_media

Adverse media types, in the format [old/new][serious/light][allegations/accusations/convictions]. Separated by a comma if there are multiples. Example: old_serious_allegations, new_light_convictions

Example file

Individual persons file

  • Must contain one individual person per line

  • Accepted properties (mandatory in bold):

Fields
Notes

id_custom

Customer identifier used by your organization. It has to be unique.

name

vat_number

If you do not have the VAT identification number of the individual person, you can generate a unique identifier, which must have a letter as the first character. Ex: ID659

responsible_email

Email of the user who will be responsible for the customer's questionnaire. Must be a user entered in your organization.

invited_email

User email to invite. The invitation will have to be sent manually after insertion.

email

Email of the individual person.

birth_date

Should follow one of the following formats:

  • dd-mm-yyyy

  • dd/mm/yyyy

  • yyyy-mm-dd

  • yyyy/mm/dd

nationalities

Separated by semicolons if there are multiples.

country_birth

address_type

Accepted values: residence, fiscal_residence and headquarters.

country_address

is_identified

0, in case there is no identification.

address_postal_code

address

address_door

address_district

address_city

adverse_media

Adverse media types, in the format [old/new][serious/light][allegations/accusations/convictions]. Separated by a comma if there are multiple. Example: old_serious_allegations, new_light_convictions

Example file

File of relationships between individual persons and organizations

  • Must contain one relation per line

  • Accepted properties (mandatory in bold):

Fields
Notes

organization_vat_number

VAT identification number of the organization to insert the relationships. This organization must already exist in the system.

vat_number

VAT identification number of the relationship to be inserted. This individual person/organization must already exist in the system.

position_in_organization

It can have free text (e.g. "Chairman", "Manager", etc.), "owner", in case the relationship is as a shareholder or holder of voting rights, or "beneficial_owner" if it is a beneficial owner. If the vat_number belongs to an organization, this field must have the value "owner".

capital_percentage

It can only be filled in if the value of the position_in_organization field is "owner" or "beneficial_owner". E.g.: 19,96

voting_rights_percentage

It can only be filled in if the value of the position_in_organization field is "owner" or "beneficial_owner". E.g.: 19,96

Example file

PreviousCustomer RegisterNextRisk categorization of individual persons/organizations

Last updated 7 months ago

Was this helpful?

413B
organizations.csv
516B
individuals.csv
189B
relationships.csv