Description
We offer the option to establish an integration where person data is created and updated in Tripletex, based on data from Simployer HRM.
All newly created persons will be registered as standard users in Tripletex. With this integration in place, employees can maintain their personal data in Simployer, and that information will be transferred automatically to Tripletex.
During data transfer, the system checks Tripletex: if the employee number already exists, the person's data will be updated. If not, a new person will be created in Tripletex with personal and some job-related data.
Required Fields for Transfer to Tripletex
Employee number
National ID number or D-number
Department, if departmental accounting is used in Tripletex
Fields that are filled out and transferred must comply with regulations (e.g. bank account number, national ID number, D-number, etc.).
Technical Description
We need the following:
EmployeeToken from Tripletex
The customer must generate an EmployeeToken toward Simployer (Tripletex support may assist with this)
Service user creation
A service user is created in Simployer for use in API queries against the customer database.
This user is hidden by Simployer AS to exclude them from reports and login access.
The integration job is set up in Simployer’s Azure middleware, using Logic Apps and Azure Functions.
Fields Transferred
| Simployer | Tripletex | Comment |
|---|---|---|
| First name | FirstName | New/Update |
| Last name | LastName | New/Update |
| Employee number | EmployeeNumber | New |
| Date of birth | DateOfBirth | New/Update |
| New only, Tripletex does not support updates | ||
| Mobile number | PhoneNumberMobile | New/Update |
| Work phone number | PhoneNumberWork | New/Update |
| Bank account | BankAccountNumber | New/Update |
| National ID number | NationalIdentityNumber | New/Update |
| Employee category | EmployeeCategory | New |
| Department number | Department/Division | New/Update |
| Address line 1 | AddressLine1 | New/Update |
| Address line 2 | AddressLine2 | New/Update |
| Postal code | PostalCode | New/Update |
| City | City | New/Update |
| Start date | StartDate | New |
| End date | EndDate | New |
Format
REST API
Frequency
Daily / Scheduled
All work beyond the standard setup will be billed based on time spent, according to the applicable hourly rate.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article