Overview
With this integration you will connect Alexis HR to your Tripletex account via API and can then do the following:
Scheduled or manual sync of employee data such as personal information, employment data, compensation data and more from Alexis HR to Tripletex
Sync time off data such as sickness, parental leave and vacations to Tripletex for the period that you choose. You have full control over what absences are exported for what employees and for what period
Available in: Norway
Tripletex requirements
You need to have access to the following valid credentials.
You can generate an API user key in your Tripletex account and instructions can be found here: Tripletex help center article
Set up in Simployer
The integration is activated from Settings → Integrations → Integrate with payroll system → Add Integration
In the API Integrations section, select Tripletex
Click Next to start the configuration wizard
Enter all the details needed for the connection
Settings
You can choose how the integration sync for employees is executed. The options available are as follows:
Manual sync
The data is manually synced to Tripletex by the user
This can be valuable if you have the scheduled sync turned off and want to control when data is synced to Tripletex. Either during the implementation phase or during times when an update is not wanted due to process and payroll timing
Manual syncs can be performed even when a scheduled sync is configured. This may be necessary if there have been a significant number of changes in Alexis HR after a scheduled sync has been executed
Scheduled sync
The sync runs on a schedule that you can define
Options include the day(s) of the week and the time of day for the sync to be executed
Note : Currently the sync is queued and it starts shortly after 06:00 CET.
Scope
The edit scope settings allows for more granularity on what employee will be part of the automatic or manually triggered employee export. This is useful if you know that not all of the employees should be exported to Tripletex.
The scope selection follows the standard scope selection that exists in Alexis HR.
Employee data
Overview
Employee data is synchronized from Alexis HR to Tripletex. This means that if data is updated in Tripletex on "data fields" and then the sync from Alexis HR is done the data in Tripletex will be overwritten.
When the sync is executed it will compare the data in Alexis for the "data fields" to see if there is a difference between the values for those fields in Tripletex. If there is no change, the user will not be updated. If there is a change present, the data will be updated.
Some fields are currently hardcoded, see below for more information.
Data fields
Alexis field | Tripletex field | Mapping conditions |
Work Section |
|
|
Employee.employeeNumber | Employee.code | Required |
Employee.workEmail || Employee.privateEmail | Contact.email | Uses Alexis work email if it exists. Otherwise the private email is used. |
Employee.workPhone | Employee.phoneNumberMobile |
|
Financial |
|
|
Employee.bankAccount.number | Employee.bankAccountNumber |
|
Employee.bankAccount.iban | Employee.iban |
|
Employee.bankAccount.bic | Employee.bic |
|
Personal |
|
|
Person.firstName | Employee.firstName |
|
Person.lastName | Employee.lastName |
|
Person.firstName | Contact.name | Concatenate fields from Alexis, divide with a space |
Employee.ssn | Employee.nationalIdentityNumber | If SSN IS NOT in DNumber format |
Employee.ssn | Employee.dnumber | If SSN IS in DNumber format |
Employee.Birthdate | Contact.birthday |
|
Employee.nationality | Contact.country |
|
Person.PhoneNumber | Contact.phone |
|
Person.email | Contact.email |
|
Employee.homeAddress.street | Employee.address.addressLine1 |
|
Employee.homeAddress.postalCode | Employee.address.postalCode |
|
Employee.homeAddress.city | Employee.address.city |
|
| Employee.userType | Default set to STANDARD |
Employment |
|
|
Employment.id | Employment.employmentId |
|
Employment.startDate | Employment.startDate | Required |
Employment.endDate | Employment.endDate |
|
Employment.note | Employment.employmentEndReason | “ 1 ” → EMPLOYMENT_END_WRONGLY_REPORTED “ 2 “ → EMPLOYMENT_END_EMPLOYER “ 3 “ → EMPLOYMENT_END_EMPLOYEE “ 4 “ → EMPLOYMENT_END_SYSTEM_OR_ACCOUNTANT_CHANGE “ 5 “ → EMPLOYMENT_END_INTERNAL_CHANGE “ 6 “ → EMPLOYMENT_END_EXPIRED |
Employment.latestSalary.employmentType |
| Default set to ORDINARY |
Employment.relations.type.name | Employment.latestSalary.employmentForm | If Simployer One employment type contains “permanent” → PERMANENT If Simployer One employment type contains “temporary” → TEMPORARY |
Compensation.payoutPeriod | Employment.latestSalary.renumerationType | MONTHLY → MONTHLY_WAGE HOURLY → HOURLY_WAGE Otherwise → NOT_CHOSEN |
Compensation.effectiveDate | Employment.latestSalary.date |
|
Compensation.amount | Employment.latestSalary.annualSalary | Amount * 12 if remuneration type is monthly wage. Otherwise this field is not set. |
Compensation.amount | Employment.employmentDetails.hourlyWage | If the remuneration type is set to hourly. Otherwise this field is not set. |
Employee.hireDate | Employment.dateFrom |
|
Employment.type |
|
|
Employment.rate | Employment.latestSalary.percentageOfFullTimeEquivalent |
|
Absence data
Overview
Absence data is synchronized from Alexis HR to Tripletex. This means that if data is updated in Tripletex on "data fields" and then the sync from Alexis HR is done the data in Tripletex will be overwritten.
When the sync is executed, it will compare the data in Alexis for the "data fields" to see if there is a difference between the values for those fields in Tripletex. If there is no change, the user will not be updated. If there is a change present, the data will be updated.
Some fields are currently hardcoded, see below for more information.
Key information
If the leave type code in Simployer One is set to one of the following:
FURLOUGH
PARENTAL_BENEFITS
MILITARY_SERVICE
OTHER_NOT_STATUTORILY_REQUIRED
OTHER_STATUTORILY_REQUIRED
EDUCATIONAL_NOT_STATUTORILY_REQUIRED
EDUCATIONAL_STATUTORILY_REQUIRED
The leave will be exported to Tripletex as a leave of absence. Otherwise the leave will be exported as a timesheet entry for an activity that needs to be defined in Tripletex. You then need to ensure that the leave type code in Simployer One matches exactly with the Tripletex activity number.
Data fields
Alexis field | Tripletex field | Mapping conditions |
leave.id | leaveOfAbsence.importedLeaveOfAbsenceId |
|
leave.startDate | leaveOfAbsence.startDate |
|
leave.endDate | leaveOfAbsence.endDate |
|
| leaveOfAbsence.percentage | Default set to 100% - graded leave of absence coming soon! |
leave.id | leaveOfAbsence.importedLeaveOfAbsenceId |
|
leave.relations.type.kind | leaveOfAbsence.type | If leave type code is set to one of the following in Simployer One: FURLOUGH PARENTAL_BENEFITS MILITARY_SERVICE OTHER_NOT_STATUTORILY_REQUIRED OTHER_STATUTORILY_REQUIRED EDUCATIONAL_NOT_STATUTORILY_REQUIRED EDUCATIONAL_STATUTORILY_REQUIRED |
Timesheet entry fields
Alexis absence code | Xledger absence code | Comment |
leave.relations.type.kind | entry.activity.number |
|
leave.workingDays.days[].date | entry.date |
|
| hours | Default set to 7.5 |