Person import fields

Employee number

Employee_number

The employee number. This is used to identify person in the import file if the Username is not imported: if a person is found from Nepton with the imported employee number then the import row updates information of that person.

Yes

Yes

First name

First_name

First name of the person

Yes

No

Last name

Last_name

Last name of the person

Yes

No

Username

Username

The login name used for person identification in the login page. Can also be used in Single Sign-On for identifying the person. If the username field is provided in the import, an existing Person in Nepton is identified by it - Username cannot be changed in Person import.

Yes

No

User account enabled

User_account_enabled

Is persons account active. Default to Yes (supports inputs 0,1, Y, N, Yes, No, Kyllä, Ei). This field is not case sensitive.

Yes

No

Personal identity code

Personal_identity_code

Finnish personal identity code

Yes

Yes

Email

Email

Email address

Yes

Yes

Web page

Web_page

Website/Homepage of the Person (eg. supplier homepage for a subcontractor)

Yes

Yes

Street address

Street_address

Street address

Yes

Yes

Postcode

Postcode

Postal code

Yes

Yes

Town/city

City

Yes

Yes

Phone number

Phone_number

Phone number

Yes

Yes

IBAN

IBAN

IBAN bank account number

Yes

Yes

BIC

BIC

Bank identifier code (BIC)

Yes

Yes

RFID tag identifier

RFID_tag_identifier

RFID tag code. Used in identifying for a worktime terminal.

Yes

Yes

Pin code

Pin_code

Pin code. Used in identifying for a worktime terminal.

Yes

Yes

Password

Password

Plain text password for person. We do not recommend importing passwords to the platform, in which case a password is automatically generated. Every person can set their own password with the Forgot password function.

Yes

No

Role

Role

Person role. Accepts the following values

• Employee
• Administrator
• Salary Management
• Supervisor
• Unit Manager
• HR Management

Yes

No

Worktime roles

Worktime_roles

Worktime roles. Enter either the role name or id
If applying multiple roles separate each with the pipe "|" character. The given values will replace existing worktime roles.
With the RESET keyword you can ensure deleting all the existing worktime roles even if IgnoreEmptyValues setting was used (e.g. via the web service)

No

Yes

Job title

Job_title

Job title

Yes

Yes

Work area

Work_area

Working area

Yes

Yes

Weekly hours MIN

Weekly_hours_MIN

Weekly hours minimum value. This field also supports decimal value. Use comma ',' as decimal separator e.g. 15,5. Presented in the work shift planning for the planner.

Yes

Yes

Weekly hours MAX

Weekly_hours_MAX

Weekly hours maximum value. This field also supports decimal value. Use comma ',' as decimal separator e.g. 35,5. Presented in the work shift planning for the planner.

Yes

Yes

Employment start date

Employment_start_date

Work contract start date (DD.MM.YYYY)

No

Yes

Employment end date

Employment_end_date

Work contract end date (DD.MM.YYYY). For an ongoing work contract without end date specified the field should be imported as empty.

No

Yes

Trial period end date

Trial_period_end_date

Trial period ends date (DD.MM.YYYY)

Yes

Yes

Units

Units

Unit(s). Enter either the unit name or code.

If applying multiple units separate each with the pipe "|" character.

The given values will replace existing unit memberships for the person.
With the RESET keyword you can ensure removing all existing unit memberships for the person even if IgnoreEmptyValues setting was used (e.g. via the web service).

No

Yes

Default project

Default_project

Default Project for the person

No

Yes

Default cost group

Default_cost_group

Cost group for the person

Yes

Yes

Primary supervisor

Primary_supervisor

Primary supervisor's employee number. Empty value or RESET keyword will remove the primary supervisor.

No

Yes

Secondary supervisors

Secondary_supervisors

Pipe (|) separated list of secondary supervisor employee numbers. If the RESET keyword is included, the listed supervisors will replace all the existing secondary supervisors for the person.

No

Yes

Integration ids fields:

Aastra
Aboa
DL Software
Elisa Ring
Emce
Fivaldi
Hogia
IFS
Kieku
Lessor-5
Liksa
Mepco
Oscar
Personec F
Personec W
ProCountor
Scala
Sedab
Sonet
Tikon
Visma

Integration ids fields:

Aastra
Aboa
DL_Software
Elisa_Ring
Emce
Fivaldi
Hogia
IFS
Kieku
Lessor-5
Liksa
Mepco
Oscar
Personec_F
Personec_W
ProCountor
Scala
Sedab
Sonet
Tikon
Visma

External system id for the person. There is an IntegrationId field for each supported integration listed.

The field value accepts a string.

Yes

Yes

Balance

Balance

Inserts a balance accrual reset value in minutes to the current day. This field accepts integer value.

No

No

Additional administrative information

Additional_administrative_information

Additional Information (free text field)

Yes

Yes

Next of kin

Next_of_kin

Next of Kin (free text field for next of kin names)

Yes

Yes

Next of kin phone number

Next_of_kin_phone_number

Next of Kin Phone number (validated as phone number or empty)

Yes

Yes

Additional information for reports

Additional_information_for_reports

Additional Report Information (free text field. Information is shown in various reports)

Yes

Yes

Reason for ending employment

Reason_for_ending_employment

Reason for working contract end (free text field)

Yes

Yes

Hourly wage

Hourly_wage

Working contract hourly wage (numeric string which allows decimal values, but cannot start with zero. Use comma ',' as decimal separator e.g. 20 or 25,5)

Yes

Yes

Tax number

Tax_number

Finnish Tax number (must be exactly 12 numeric characters long, or empty)

Yes

Yes

Person group

Person_group

Persons person group code. Use either this field or "Person group code path in hierarchy" and "Person group name path in hierarchy"

No

Yes

Person group name path in hierarchy

Person_group_name_path_in_hierarchy

A pipe separated list of persongroup names representing the persongroup structure the person is part of. Both "Person group code path in hierarchy" and "Person group name path in hierarchy" are needed if one is transferred. Hierarchy is created and updated automatically.
Value is person group complete name hierarchy pipe separated.

E.g. 'Office|Sales' will import person group 'Office' with a subgroup 'Sales'. Imported person will be part of person group 'Sales'.

No

No

Person group code path in hierarchy

Person_group_code_path_in_hierarchy

A pipe separated list of persongroup codes representing the persongroup structure the person is part of.  Both "Person group code path in hierarchy" and "Person group name path in hierarchy" are needed if one is transferred. Hierarchy is created and updated automatically. Value is person group complete code hierarcy pipe separated.

E.g. '10|20' with the example provided above will import code '10' for person group 'Office' and '20' for person group 'Sales'.

No

Yes

Worktime setting group

Worktime_setting_group

Person setting group code.  Entering ‘RESET’, ‘NOLLA’, or nothing (no text), will remove the person from all settings groups from the beginning of the day until infinity

Yes

Yes

Work time percentage

Work_time_percentage

Work time percentage for person, which is used to calculate work day and work week length. If percentage changes, the new percentage will be in effect from current day onwards. The decimal format is with comma, example ’80,00’.

Yes

No

Service usage language

Service_usage_language

Persons language. The value in this field should be English name of a language. Currently supported are Finnish, English, Swedish, Danish, Polish and Estonian.

Yes

No

Visma cost centre

Visma_cost_centre

Visma cost center

Yes

No

Valid from date

Valid_from_date

Can be used to set the validity start of the information set on the row. Format to be used is (DD.MM.YYYY).

Please see the article about importing validities here.

Yes

Yes