Tripletex – Absence
Description
We offer the possibility to establish an integration based on absences registered in Simployer.
Leave and absence types (such as unpaid leave) are transferred once they have started. Sick leave is transferred once it is confirmed in Simployer. Vacation is exported day by day starting from the start date.
Prerequisites
The absence integration requires that the Tripletex person integration is already established.
The Time module in Tripletex must be in use.
Absence codes must be harmonized between Simployer and Tripletex.
Technical Description
We need the following:
EmployeeToken from Tripletex
The customer must generate an EmployeeToken toward Simployer (Tripletex must assist with this)
Service User Setup
A service user is created in Simployer for queries against the customer database.
The user is hidden by Simployer AS to ensure it does not appear in reports and cannot log in.
The integration job is set up in Simployer’s Azure middleware, using Logic Apps and Azure Functions.
Fields Transferred
| Simployer | Tripletex | Description |
|---|---|---|
| Absence type | Activity code | Type of absence |
| From date | Date (per day) | Absence is sent per day |
| To date | Date (per day) | Absence is sent per day |
| Comment | Comment | Any note or description |
Format
REST API
Frequency
Daily / Scheduled
Any work beyond standard setup will be billed based on time spent at 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