Tripletex - Absence Data Import to Simployer One

Modified on Wed, 10 Jun at 2:44 PM

Tripletex Absence Import - Setup & Specifics

Please read the general guide first. This article only covers what is specific to Tripletex. The import flow, the preview categories (Importable / Already imported / Conflicts / Orphaned / Unmapped), the full-day rules, and the import limits are the same for all source systems and are described in Absence Import from Time & Payroll Systems.

Organisations that track absences via Tripletex timesheets can import leave entries into Simployer One's Time Off module. Tripletex remains the master system for absence management: employees request and report their absences in Tripletex, and the import brings the data into Simployer One.

Quick facts

What is read	Timesheet entries from Tripletex's timesheet module.
How codes are mapped	The Simployer leave type code is entered in the Number field of the Tripletex activity. Configured in both systems (see below).
Daily hours	Read from the hours on the timesheet entry. 7.5 hours or more = full-day absence; less = partial-day absence.
Grouping	Consecutive days with the same leave code are grouped into a single absence period.
Export counterpart	The outbound direction (Simployer One to Tripletex) is a separate process. See Tripletex Standard Integration - Absence Data (Export).

Map Absence Codes

Both systems need matching leave type codes so the import knows which Tripletex timesheet entry corresponds to which Simployer One absence type. This mapping must be configured on both sides: the same code is entered as the Number on the Tripletex activity and as the Leave type code in Simployer One.

In Simployer One

1	Open Time Off settings Navigate to Settings > Time off settings.

2	Add the Leave type code For each absence type that should be imported from Tripletex, add the corresponding Leave type code. This code must match the value configured in Tripletex (see below).

In Tripletex

1	Open Timesheet settings Navigate to Time sheet > Settings.

Add Simployer codes via the Number field

Open the Internal activities section. For each activity that represents an absence (vacation, sick leave, etc.), enter the matching Simployer leave type code in the Number field, and make sure the activity's Absence checkbox is enabled. Activities that represent working time should be left without a Simployer code in Number; they will be ignored during import.

Tip: Only map leave-type entries (vacation, sick leave, etc.). Leave working time, overtime, and other non-absence timesheet entries unmapped. This ensures only actual absences are imported into Simployer One.

Tripletex-Specific Behavior

Only timesheet entries with a Simployer code in the Number field appear in the preview. Activities without a code in the Number field (e.g. working time) are skipped silently. Entries that do have a code but no matching Simployer One absence type appear in the preview under Unmapped leaves types and require a code mapping before they can be imported (see Map Absence Codes above).

The typical workflow is to run the import once per month, after the previous month's timesheets are finalized in Tripletex.

Tripletex Integration

→ Absence Import from Time & Payroll Systems (General Guide)

→ Simployer HRM Integration - General Setup Guide

→ Tripletex Integration - Employee Data

→ Tripletex Standard Integration - Absence Data (Export)