Think of this section as the checklist for your data. 7 easy points to keep in mind when preparing data for Person data upload. The rest is "nice-to-know".
1. The table must be in standard CSV format and use UTF-8 encoding.
The first row of the file must be a header row with the column names, followed by one or more rows of the actual data. You can prepare the CSV with a spreadsheet editor, text editor, or export it from your internal system if it supports exporting CSV.
2. All entries in the document must correspond to the same data type
This means the entire document has data for type "Person", i.e. it is a Person table.
3. All data fields (ie column names) must be in snake_case or camelCase.
Choose either snake_case or camelCase and stick with it for all data fields.
An example of snake_case across all data fields:
4. Make sure fields “id” and “type” are present for every entity/row
id - unique person number (for example, the customer number in your system).
NB! Allowed character are alphanumerics `a-zA-Z0-9` (case sensitive), hyphens `-`, underscores `_`, colons `:`, dots `.`
type - must be INDIVIDUAL or LEGAL or UNDEFINED.
NB! Make sure these are written in capital letters.
5. Each row must correspond to one entity
As visible from the example above, one row corresponds to one Person.
6. If you want to add the following data, name the data fields exactly as stated below
Data fields (column names) can be in snake_case or camelCase, as long as the 3rd point on the checklist is followed. Below examples are in snake_case:
first_name
last_name
dob - date of birth (must be in ISO 8601! eg 2001-01-28)
company_name
industry
email
phone_number
street_address
city
💡 You can also set the address info up using JSON, look at the simple values table below. The relevant field should be called addresses.
country
onboarding_date
id_document
id_country
gender
business_reg_number
expected_monthly_turnover
shareholders
☝ NB! If this list doesn't work with your data structure, let us know, and we can advise further.
7. All other data fields
The rest of the data fields are up to you. We recommend choosing data fields that
you need for investigating persons/creating rules. For example, if you want to make rules that take into account customer’s gender or business activity, make sure you add the relevant fields.
correspond to data your company actually collects. Don’t add fields that you don’t have data for.
NB! Any dates and times you want to add must be in ISO 8601 format (yyyy-MM-dd’T’HH:mm:ss’Z’). If you wish to send digits after seconds, then Salv supprts up to 6 digits after seconds. (yyyy-MM-dd’T’HH:mm:ss.xxxxxx’Z’)
Example data
If you'd like to see some example data sets you can find them here (input from our Fakebank dataset).
Data upload type PERSON RELATION (Complex or Nested data)
What is it? - Data upload type “Person relation” is meant for uploading complex data for an already existing PERSON, for example, to add
List of companies (and attributes pertaining to those companies) owned by customer
List of loan agreements associated with customer
List of shareholders or representatives associated with customer (i.e. a company)
any other data, that you want to connect with a specific customer that may have additional attributes connected to it.
PERSON RELATION data fields can be uploaded in either camelCase or snake_case.
Types of complex data
Complex structures table
The following data-fields are obligatory:
person_id - must match the "id"-field in the PERSON table
person_relation_type - category name (such as loans, companies, associates)
id - unique number, relates to person relation type.
All other data fields are up to you. However, if you are adding additional fields, you must follow our naming rules, outlined in point no. 6, e.g. date of birth has to be named as dob, first name should be sent as first_name, and so on.
❗ All entries in the table must belong to the same person relation type.
Simple values table
The following data-fields are obligatory:
person_id - must match the "id"-field in the PERSON table
person_relation_type - category name (such as shareholders, companies, associates)
person_relation_data - Data pertaining to the category stated above
No other data fields are allowed for a simple values table.
For example:
📌 PersonRelationData - list entries (like in the above example) should be separated by a semi-colon (;).
❗️ To have complex data displayed properly, you need to set up schemas. You can read more about it here.