Before starting
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 ID between your tool and Lucca. The ID is either:
- The login details
- The "Establishment" + "payroll number" pair (always unique for each establishment)
- The 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 ID |
Yes |
|
|
firstName |
First name |
No |
|
|
lastName |
Last name |
No |
|
|
|
Professional email |
No |
|
|
legalEntity |
Establishment |
Yes |
|
|
dtContractStart |
Contract start date |
No |
MM/DD/YYYY |
|
department |
Department/Service |
Yes |
List of departments created or imported (general settings cog wheel -> Departments) |
|
manager |
Line manager N+1 |
No |
If an employee has no manager or approver, then indicate manager = the employee themselves. |
|
Primary role |
Primary Role |
Yes |
List of roles configured in General settings -> Roles |
|
culture |
Lucca's display language |
Yes |
fr-FR; de-DE; en-US; en-GB; es-ES; nl-BE; it-IT |
|
habilitedRoles |
Secondary role(s) |
No |
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 .... |
|
employeenumber |
Payroll number |
No |
Lucca can automate the creation of the payroll number. It can be created asynchronously with employee creation. This field is only mandatory 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 |
Yes |
List of profiles created in regulations |
|
dtBirth (optional) |
Date of birth |
No |
MM/DD/YYYY |
|
calendar |
Calendar of public holidays applicable to the employee |
Yes |
Calendar list (configure -> calendars) |
|
occupation category |
Occupation category (depending on your settings) |
Yes |
The settings module is in the cog wheel. |
|
Timmi Absences customized approver |
Second paid leave approver |
No |
Depends on your customized Timmi Absences approval workflow |
|
userWorkCycles |
Work cycles (cycle settings) |
No |
List of work cycles (general settings: cog wheel) |
|
userWorkCycles.start (optional) |
Start date of work cycle |
No |
MM/DD/YYYY |
|
userWorkCycles.end (optional) |
End date of work cycle |
No |
MM/DD/YYYY If end date is empty |
|
dtSeniority (optional) |
Seniority date if different from contract start date |
No |
MM/DD/YYYY
|
|
dtContractEnd (optional) |
Contract end date |
No |
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) |
No |
|
|
bic |
Mandatory (if paid via Cleemy Expenses) |
No |
|
|
profile_ Cleemy Expenses |
Reimbursement profile |
Yes |
Profiles created via Settings -> Expense policies |
|
personalAccount (to be completed by accounting if necessary) |
Employee's auxiliary account (credit auxiliary account) |
No |
|
|
frenchCarTaxHorsePower (optional) |
Tax category of employee's car |
No |
Format: Numeric (e.g. for 6 CVs enter 6) |
|
frenchMotorcyclesTaxHorsePower (optional) |
Tax category of employee's motorcycle |
No |
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 section x. |
No |
List of analytical sections |
Fields for the Pagga Payslip module (digitization of pay slips)
|
Code |
Description |
Default value |
Possible values |
|
personalEmail (optional) |
Personal email address for connection to the Pagga Payslip website paie.ilucca.net |
No |
Field for Poplee - HR File
The HR file is made up of two types of data:
- Core data (data in the above dashboards), which cannot be modified
- and Extended data which is data you can add and customize; for more details, see the help sheet The Various 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 an SFTP/FTPS server (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.
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.