Tripletex integration - Employee Data

Endret Wed, 10 Jun ved 2:58 PM

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


Requirements & Business Rules: 

Tripletex Requirements:

You need to have access to the following valid credentials.


Simployer Requirements:

  • The employee must have a valid employment registered in Simployer One; only then can employee and employment data be exported to Tripletex.

  • It is recommended to add the occupational code during the import of the master data to Simployer One.


Business Rules/Constraints:

  • Identity & Matching Requirements:

    • Employee numbers must match between Simployer One and Tripletex for the integration to work correctly. Assign unique and accurate employee numbers in both systems. If not, a new employee record will be created.

    • Employees start date must match between Simployer and in Tripletex

    • Compensation effective date must match in both Simployer and Tripletex. 

  • Field Update Behavior:

    • 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).

  • SSN: 

    • National Identity Number is synced only when it is empty in Tripletex, i.e existing values in Tripletex are not overwritten. However, if a DNumber is used, it will be synced regardless.

    • Certain personal identification fields (e.g., international ID) are currently unsupported. Reach out to Support if you need these features. 

  • Bank account: 
    • The country field on the bank account in Simployer is mandatory, without it the system assumes a Norwegian bank. For Norwegian banks, only the account number is used. 
    • For non-Norwegian banks, IBAN and BIC are required and the country must be set; otherwise the bank details will not sync correctly
  • Employment Detail: 
    • An employment record in Simployer One is required to export employee and employment data. For new employees, a new employment is created in Tripletex; for employees already in Tripletex before the integration was set up, new employment details are added to their existing active employment.
    • New backdated employment details are synced to Tripletex as long as the effective date is within the past year. 
    • Employment details already synced and dated before the current month cannot be modified by the integration; those corrections must be made manually in Tripletex
  • Division: 
    • Make sure the division in your Tripletex account that should be used for new employments are still active i.e. they have either no end date or an end date in the future. The integration skips division whose end date has already passed.
  • Departments: 
    • All departments used in Simployer One must already exist in Tripletex with exactly matching names before the sync runs. The integration does not create missing departments.


The following section details the field mapping between Simployer and Tripletex for employee data, including creation, updates, and limitations for each mapped field.


Work:


Simployer One 

Tripletex field

Mapping conditions

Additional Info

Employee Number

Employee Number

 

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.

Work Email || Private Email

Email

Uses Simployer One work email if it exists. Otherwise the private email is used.

Not updated

Work Phone

Phone Number Mobile

 

Updated if given new value in SimployerOne

Financial: 


Simployer One

Tripletex field

Mapping conditions

Additional Info

Bank Account Number

Bank Account Number

 

Updated if given new value in SimployerOne

Country

Required to determine if bank account details are Norwegian or not.

IBAN

IBAN

 

Updated if given new value in SimployerOne. This field is required if the Bank country is other than Norway.

BIC

BIC

 

Updated if given new value in SimployerOne. This field is required if the Bank country is other than Norway.


Personal:


Simployer One

Tripletex field

Mapping conditions

Additional Info

First Name

First Name

 

Updated if changed

Last Name

Last Name

 

Updated if changed

Birth Date

Date Of Birth

 

Field is required. Can be updated, but not after a-melding has been submitted for the employee in Tripletex.

Social Security Number

National Identity Number

If SSN is NOT of DNumber format

Only updated if it does not have a value in Tripletex.

Social Security Number

DNumber

If SSN is of DNumber format

Updated if given new value

International ID is not supported currently. Reach out to CS if this is something you need.


Home Address:


Simployer One

Tripletex field

Mapping conditions

Additional Info

Street Name

Address Line 1

 


Zip Code

Postal Code

 


City

City

 


Is not fetched - set to default

User Type

 

Set to default STANDARD. Not updated


Employment:


SimployerOne

Tripletex field

Mapping conditions

Additional Info

Start Date

Start Date

 

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.

End Date

End Date

 

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 End Reason

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

Employment Type

 

Set to ORDINARY by default

Employment Type

Employment Form

If Simployer One employment type name contains "permanent" → PERMANENT  If Simployer One employment type name contains "temporary" → TEMPORARY

 

Employment Rate


Percentage Of FullTime Equivalent




Compensation 

Payout Period

Remuneration Type

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 ]

Compensation Amount

Annual Salary

If Compensation payout Period is ANNUAL, then this field is set to Compensation.amount.  If Compensation payout Period is MONTHLY, then this field is set to Compensation.amount * 12.  Otherwise this field is not set.

For norweigan customers,we recommend that you use annual or hourly as the payout period. 

Compensation Amount

Hourly Wage

if the Compensation payout Period is set to HOURLY. Otherwise this field is not set.

 

Employment Note

Occupation 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.

 

To set up the absence data follow article Tripletex integration - absence data.


Var denne artikkelen nyttig?

Så bra!

Takk for din tilbakemelding

Beklager at vi ikke kunne være mer til hjelp

Takk for din tilbakemelding

Fortell oss hvordan vi kan forbedre denne artikkelen.

Velg minst én av grunnene
CAPTCHA-verifisering er obligatorisk.

Tilbakemeldingen er sendt inn

Vi setter pris på tilbakemeldingen din og vil prøve å rette på artikkelen