Skip to main content

How to Synchronize Employee Profiles from Combo to Silae*?

Automate the transfer of employee data from Combo to Silae*, avoid double entry, and ensure reliable payroll.

Updated yesterday

Step 1: Enable synchronization (paid option)

  • Go to Settings > Marketplace > HR

  • Select Silae* – Employee data synchronization

  • Click Subscribe!

  • Accept the terms and confirm your subscription

  • Fill in the Silae* API information:

    • Main key

    • Main client secret

    • Client ID

💡

  • Retrieve these from the Silae* API portal > My API accounts.
    Codes include numbers, letters, and special characters. Delivery may take several weeks.

  • If you don’t have API access, ask your payroll manager or contact Silae*.

  • Enter your establishments’ file numbers (digits only).


Step 2: Select and synchronize employees

From Settings > Marketplace > HR:

  • Select the employees to synchronize

  • Click Synchronize to Silae*

Check the statuses:

In progress

Synchronization activated

Synchronized

Data successfully sent

Not synchronized

User is not synchronised (e.g. missing employee number).

Failed

Error detected, e.g., duplicate employee ID


Which fields are automatically synchronized?

The following employee data is automatically sent to Silae*:

  • Identity: first name, birth name, preferred name

  • Legal info: gender, marital status, disability, social security number, employee ID

  • Birth: date, department

  • Contact details: address, postal code, city, landline and mobile phone, personal email

  • Banking: IBAN, BIC

  • Residence permit: number, type, validity dates


Best practices & recommendations

Problem

Solution

Different employee IDs in Combo and Silae*

Harmonize IDs to avoid duplicates

Incomplete data

Identify incomplete files in the Incomplete records tab in Combo

Synchronization monitoring

Track the synchronization status in the HR console to quickly detect errors or missing data

*Trademark owned by a third party unrelated to Snapshift/Combo.

Did this answer your question?