FAQ Tripletex integration

Absence and master data

Q: Changes in employee data — how does this flow through to Tripletex?

A: The integration exports employee and employment data from Simployer One to Tripletex, using the employee number to match people. When a field that is part of the mapping is given a new value or changed in Simployer One (for example phone number, bank details, name), the integration updates that field in Tripletex according to the rules and limitations described in the mapping tables. The customer decides on how the often the sync should run.

Q: Incorrect absence registered in Simployer One — how do you troubleshoot / find discrepancies?

A:  The export is manual - so at the time they chose to the export they need to make sure the absence is correct.

Do they mean that they have created absence in S1 + in Tripletex?

I would ask that, because I'm not sure how the system works if there is discrepencies; if we overwrite it or what happens..

Q: Is there a report for this?

A: There is email-notifications that is sent out around the integration with logs and discrepencies

Q: Is it HR who has to detect it?

A: Yes; Responsibility for checking and detecting discrepancies (for example wrong absence or address) is an internal process choice for the customer (often HR and/or payroll).

Q: How often is Tripletex updated?

A: The article states that the integration supports both scheduled and manual synchronization of employee and employment data. This means you can decide how often the employee-data sync should run (for example, nightly or multiple times per day), within what you have agreed and configured in your Simployer integration setup.

Troubleshooting

Q: It’s unclear by whom and how errors are discovered.

A: In practice, errors will normally be discovered either when data in Tripletex does not match Simployer (for example wrong employment dates, missing bank account) or when the integration run/logs show failed records, and then handled by the customer’s internal process (HR/payroll/system owner). Sent my email-notification (for employee data)

Q: Could this be solved by having absence codes approved by a manager/HR?

A: Whether you add a manager/HR approval step for absence is therefore an internal process decision, not something controlled by this integration

Data transfer to Tripletex

Q: How does the data flow, what data is transferred, and when does it happen?

A: The flow is one-way for these standard integrations: Simployer One sends employee and employment data to Tripletex, using employee number as the key to either update an existing person or create a new one. Data is transferred for the mapped fields in the Work, Financial, Personal and Employment sections (for example email, mobile, bank account, name, birthdate, SSN/D-number, address on creation, employment dates, employment percentage, salary and wage type) whenever the scheduled or manual sync is run and there are changes that satisfy the business rules.

Q: What about other types of data than what is described in the API docs?

A: The integration only covers the fields listed in the employee-data mapping and the separate absence-data article; the article explicitly says that some personal identification fields such as international ID are not supported, and that certain other data types like absences follow separate flows. If a field or data type is not documented as mapped, it is not transferred by the standard integration and must be handled manually or via a different/custom solution.

Other question

Q: It says that employees must have valid employments in Simployer for the integration with Tripletex to work. What does this mean, and how do we avoid users being excluded?

A: “Valid employment” means that the person has at least one employment registered in Simployer One; only then can the integration export both employee and employment data to Tripletex. To avoid exclusions, ensure every employee that should exist in Tripletex has a correctly set up employment in Simployer One (start date, active status, etc.) and that their employee number matches between the two systems.

Q: For example, employment start/end date – how does the employment integration actually work?

A: When the integration runs, Tripletex will get an employment created for any employee who does not already have an employment there; the start date comes from the first employment in Simployer One, and the employment is linked via the Simployer employment ID. When the employee is offboarded in Simployer One, the integration sets the employment end date in Tripletex to the Simployer employee end date and uses the hardcoded end reason “EMPLOYMENT_END_EMPLOYEE”, which the customer can later change manually in Tripletex if needed.

Q: Some fields must be updated manually – how do we catch any discrepancies here?

A: For fields that are not updated after initial creation (for example home address) or not supported at all (for example international ID), the article states that changes must be done manually in Tripletex. There is no automatic discrepancy detection, so the practical way to catch differences is to use Simployer as the reference, then periodically compare these fields in Tripletex (via reports or spot checks) and adjust Tripletex where needed.

Q: “Updating of fields only occurs when new values are added or changed in Simployer One.” How do you know which changes have been made?

A: The integration logic checks whether a mapped field in Simployer One has a new or changed value and, if it meets the business rules, sends that new value over; examples are mobile number, bank account, IBAN/BIC, and names. From a user perspective, you do not see a “change log”, instead, you can see the current values in Simployer versus Tripletex and, if they differ where the mapping says they should be kept in sync, you know a change has been made or needs to be re‑synced.

For the changes that have been made its showed in the report that is sent out via email.

Q: Address fields are not updated in Tripletex after initial creation. How do we know which address changes have been made?

A: The article clearly states that address fields (street, postal code, city) are not updated in Tripletex once the person is created there, so later changes to the home address in Simployer will not flow through. To discover such changes, you must either compare addresses between Simployer and Tripletex or use an internal process (for example, HR/payroll reviews address changes in Simployer and then updates Tripletex manually).

Q: The absence integration does not support partial (graded) sick leave. If an employee has graded sick leave, do they still have to enter hours manually in Tripletex, since Simployer only supports full days? Do you have experience with how other customers solve this?

A: The employee-data article only points to a separate absence-data article and does not describe graded sick leave support; the absence article states that partial sick leave is not supported in the integration and is under development. In practice, where partial sick leave is needed, customers normally handle the detailed hours directly in Tripletex (manual registration) while using Simployer for full-day registrations, but specific customer practices are not documented in this article and can vary.

Q: The absence integration currently has to be run manually. Who is responsible for this, and how often should it be run?

A: The employee-data article confirms that employee data can run on a schedule or be triggered manually and says that absence uses a separate export flow, but it does not assign responsibility or prescribe a frequency for the absence job. Typically, customers let HR/payroll or a system owner run the manual absence export at intervals that fit their payroll and time registration routines (for example daily or before payroll), but this is a process decision, not something enforced by the integration.

Q: Today there are two integrations: employee data (automatic) and absence (manual). Is that correct? Can we run employee data more frequently, and does absence have to be manual?

A: Yes, that understanding matches the documentation: there is one standard integration for employee and employment data that supports scheduled and manual sync, and a separate absence integration described in another article, which is currently manual. Employee sync can be scheduled to run as often as you configure it in Simployer, while the documentation for absence states that it is a manual export today, so it must be triggered by a user until an automated option is introduced.

Good to know
If you want to include the occupational code the recommendation is to add the occupational code during the import of master data to Simploer One.