Decoding: creating a user data import file

 

Before you get started

Your import files should always be in the format of a CSV file with comma-separated values.

To identify the right employee, the first column of your file must be the shared identifier between your tool and Lucca. The identifier is either:

  • The login details
  • The "Establishment" + "payroll number" pair (always unique for each establishment)
  • Email

Creating a user: mandatory fields

If default values are configured, mandatory fields can be left empty, or the columns in these fields may not be included in the file.

Data code

Description

Default value

Possible values

login

Employee identifier

Oui

 

firstName

First name

Non

 

last name

Last name

Non

 

mail

Professional email

Non

 

legalEntity

Establishment

Oui

 

dtContractStart

Contract start date

Non

MM/DD/YYYY

department

Department/Service

Oui

List of departments created or imported (general settings cog wheel - Departments)

manager

Line manager N+1

Non

If an employee has no manager or approver, then indicate manager = the employee themselves.

rolePrincipal

Primary role

Oui

List of roles configured in General settings - Roles

culture

Lucca's display language

Oui

fr-FR; de-DE; en-US; en-GB; es-ES; nl-BE; it-IT

habilitedRoles

Secondary role(s)

Non

This is not a mandatory field.

To match them by import, you must create as many columns as secondary roles required:

habilitedRoles_0 / habilitedRoles_1 / habilitedRoles_2, etc.

employeenumber

Employee number

Non

Lucca can automate the creation of the payroll number.

It can be created asynchronously with employee creation. 

This field is mandatory only if you have subscribed to Timmi Absences.

 

Fields for Timmi Absences (leave and absence management) and Timmi Timesheet (time and activity management) modules

Data code

Description

Default value

Possible values

profile_ Timmi Absences

Accrual profiles

Oui

List of profiles created in regulations

dtBirth (optional)

Date of birth

Non

MM/DD/YYYY

calendar 

Calendar of public holidays applicable to the employee

Oui

Calendar list (configure - calendars)

Occupation category

Occupation category (depending on your settings)

Oui

The settings module is in the cog wheel. 

Timmi Absences customized approver

Second paid leave approver

Non

Depends on your customized Timmi Absences approval circuit

userWorkCycles

Work cycles (cycle settings)

Non

List of work cycles (general setting: cog wheel)

userWorkCycles.start (optional)

Start date of work cycle

Non

MM/DD/YYYY

userWorkCycles.end (optional)

End date of work cycle

Non

MM/DD/YYYY

If end date is empty

dtSeniority (optional)

Seniority date if different from contract start date

Non

MM/DD/YYYY

 

dtContractEnd (optional)

Contract end date

Non

MM/DD/YYYY

 

Fields for the Cleemy Expenses module (Expense management)

Data code

Description

Default value

Possible values

iban

Mandatory (if paid via Cleemy Expenses)

Non

 

bic

Mandatory (if paid via Cleemy Expenses)

Non

 

profile_ Cleemy Expenses

Reimbursement profile

Oui

Profiles created via Settings - Expense policies

personalAccount (to be entered in the accounts if required)

Employee's auxiliary account (credit auxiliary account)

Non

 

frenchCarTaxHorsePower 

(optional)

Tax category of employee's car

Non

Format: Numeric (e.g. for 6 CVs enter 6)

frenchMotorcyclesTaxHorsePower

(optional)

Tax category of employee's motorcycle

Non

Format: Numeric (e.g. for 6 CVs enter 6)

axisValues(x) (optional)

x being the id of the analytical section indicated in the administration of analytical sections

Value of an analytical section of the employee's analytical axis x.

Non

List of analytical sections

 

Fields for the Pagga Payslip module (digitization of pay slips)

Log code

Description

Default value

Possible values

personalEmail (optional)

Personal email address for connection to the Pagga Payslip website paie.ilucca.net

Non

 

 

Field for Poplee - HR File 

The HR file is made up of two types of data:

  • Core data (data in the above tables), which cannot be modified
  • and Extended data, which you can add and customize. For more details, please refer to the HR file help page The different types of data in the HR file

Importing this data will follow the same model as a user import, with the Login in the first column.

Each data item in your database is characterized by a unique code, which you can easily find in the employee data reports

 

 

User synchronization via SFTP/FTPS

User synchronization from third-party software to Lucca can be automated to ensure that information is regularly updated.

To do this, you can synchronize your user files via a SFTP/FTPS (File Transfer Protocol).

The file sent over the Lucca SFTP/FTPS must be a flat file in CSV format (comma separated list).

Lucca lets you define default values (Employees Default values) for each establishment or department.

mceclip0.png

These values will be assigned by default to each new entrant if you do not enter a value in the file. 

The file can be uploaded either to an SFTP/FTPS server provided by Lucca or on the client's server. Synchronization takes place once a day at a time defined in the settings.

 

 

 

Page content

Was this article helpful?
2 out of 3 found this helpful