Reference General Setup
Before configuring this integration, please complete the Simployer HRM Integration – General Setup Guide. This guide covers the initial steps for setting up integrations in Simployer and ensures that you have configured the necessary base settings for successful data sync
Overview
This article covers all specifics for the Tripletex standard integration.
The integration enables scheduled and manual synchronization of employee and employment data between Simployer One and Tripletex. Note that some data types, like absences, follow separate export flows.
Available in: Norway
Requirments & API Credentials
Tripletex Requirments
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
Simployer Requirements
The employee must have a valid employment registered in Simployer One; only then can employee and employment data be exported to Tripletex.
Business Rules
Employee numbers must match between Simployer One and Tripletex for the integration to work correctly. Assign unique and accurate employee numbers in both systems.
Employee email is prioritized as work email; if unavailable, the private email is used. This field is not updated after initial sync.
Updating of fields (such as phone number, bank details, personal information) only occurs when new values are added or changed in Simployer One.
Some fields are immutable or only updated under certain conditions (for example, birthdate cannot be changed after a-melding submission in Tripletex).
The SSN is only updated in Tripletex if there is no current value; if a DNumber is used, it will be synced if provided.
Certain personal identification fields (e.g., international ID) are currently unsupported—reach out to Support if you need these features.
Address fields are not updated in Tripletex after initial creation, so any changes to home address must be managed manually in Tripletex.
The following section details the field mapping between Simployer and Tripletex for employee data, including creation, updates, and limitations for each mapped field.
Employee data
Overview
The integration matches employees using their employee number. If the employee number in Simployer One matches an existing employee in Tripletex, the integration will update the details of that employee in Tripletex. If not, a new employee record will be created.
When the integration runs, employments are created in Tripletex for any employees who do not already exist in Tripletex. If an employee is already registered in Tripletex prior to integration setup, the integration will add new employment details to their current active employment in Tripletex.
An employment in Simployer One is required to enable export of both employee and employment data to Tripletex.
Below are the fields populated when creating an employment in Tripletex, as well as the fields that are updated when the employee is offboarded in Simployer One:
Work Section
SimployerOne | Tripletex field | Mapping conditions | Additional Info |
Employee.employeeNumber | Employee.employeeNumber |
| The employee number is used to match employees between Simployer One and Tripletex. It is thus not updated. And it is important that the employee number is assigned correctly in the systems for the integration to work. |
Employee.workEmail || Employee.privateEmail | Employee.email | Uses Simployer One work email if it exists. Otherwise the private email is used. | Not updated |
Employee.workPhone | Employee.phoneNumberMobile |
| Updated if given new value in SimployerOne |
Financial
SimployerOne | Tripletex field | Mapping conditions | Additional Info |
Employee.bankAccount.number | Employee.bankAccountNumber |
| Updated if given new value in SimployerOne |
Employee.bankAccount.iban | Employee.iban |
| Updated if given new value in SimployerOne. This field is required if the Bank country is other than Norway. |
Employee.bankAccount.bic | Employee.bic |
| Updated if given new value in SimployerOne. This field is required if the Bank country is other than Norway. |
Personal
SimployerOne | Tripletex field | Mapping conditions | Additional Info |
Employee.firstName | Employee.firstName |
| Updated if changed |
Employee.lastName | Employee.lastName |
| Updated if changed |
Employee.birthDate | Employee.dateOfBirth |
| Field is required. Can be updated, but not after a-melding has been submitted for the employee in Tripletex. |
Employee.ssn | Employee.nationalIdentityNumber | If ssn is NOT of DNumber format | Only updated if it does not have a value in Tripletex. |
Employee.ssn | Employee.dnumber | If ssn IS of DNumber format | Updated if given new value |
| Employee.internationalId.number |
|
|
Employee.homeAddress.street | Employee.address.addressLine1 |
| Not updated |
Employee.homeAddress.postalCode | Employee.address.postalCode |
| Not updated |
Employee.homeAddress.city | Employee.address.city |
| Not updated |
Is not fetched - set to default | Employee.userType |
| Set to default STANDARD. Not updated |
Employee.internationalId is not supported currently. Reach out to CS if this is something you need.
SimployerOne | Tripletex field | Mapping conditions | Additional Info |
Employment.id | Employment.employmentId |
| The id of the first employment for the employee in Simployer One |
Employment.startDate | Employment.startDate |
| We use the first employment of the employee to create an employment in Tripletex. Only if there is no employment registered in tripletex for said employee. |
Employee.endDate | Employment.endDate |
| When employee is offboarded in Simployer One. We set the employment end date in Tripletex to the employee end date from Simployer One. |
See additional comment | Employment.employmentEndReason | EMPLOYMENT_END_EMPLOYEE | When the employee is offboarded in SimployerOne, and we end the employment in Tripletex. We use the hardcoded value "EMPLOYMENT_END_EMPLOYEE" as the end reason. If the customer wants to change the reason, they have to do it manually in Tripletex. |
Employment details data mapping
Employment details get created on the main/active employment in Tripletex, whenever a new employment is created on the employee in Simployer One, or when a new compensation is added.
If a new employment is created in Simployer One, we combine the employment data with the latest compensation that exists for the employee.
And vice versa, if a new compensation gets added in Simployer One, we combine the compensation data with the latest employment that exists for the employee.
Simployer One field | Tripletex field | Mapping conditions | Additional Info |
Is not fetched - set to default | employmentDetail.employmentType |
| Set to ORDINARY by default |
Employment.relations.type.name | employmentDetail.employmentForm | If Simployer One employment type name contains "permanent" → PERMANENT If Simployer One employment type name contains "temporary" → TEMPORARY |
|
Compensation.payoutPeriod | employmentDetail.remunerationType | ANNUAL → MONTHLY_WAGE MONTHLY → MONTHLY_WAGE HOURLY → HOURLY_WAGE Otherwise → NOT_CHOSEN | Allowed values are: [ MONTHLY_WAGE, HOURLY_WAGE, COMMISION_PERCENTAGE, FEE, NOT_CHOSEN, PIECEWORK_WAGE ] |
Employment.rate | employmentDetail.percentageOfFullTimeEquivalent |
|
|
Compensation.amount | employmentDetail.annualSalary | If Compensation.payoutPeriod is ANNUAL, then this field is set to Compensation.amount. If Compensation.payoutPeriod is MONTHLY, then this field is set to Compensation.amount * 12. Otherwise this field is not set. |
|
Compensation.amount | employmentDetail.hourlyWage | if the Compensation.payoutPeriod is set to HOURLY. Otherwise this field is not set. |
|
Employment.note | employmentDetail.occupationCode.code | If there is a 7 digit code in the notes field of the employment in Simployer One. And if the code matches one of the occupation codes in the Tripletex API, it will be set on the employment detail. |
|