Connecting Sympa
Prepare the Sympa interfaces, authorise the connection in Evenpay and validate the first import.
Written By Karl
Last updated 17 days ago
Connect Sympa to Evenpay to bring in employee, organisation, compensation and performance data. The connection runs through Kombo, Evenpay's integration partner. Sympa needs more preparation than most HR systems: your Sympa administrator configures the API interfaces first, and Evenpay completes the mapping and checks the data with you before regular syncing starts.
Who does what:
Your HR or data owner confirms the scope, what each field means, and the sample results.
Your Sympa administrator configures the interfaces, access and credentials.
The Evenpay administrator (the person with the Evenpay invitation) authorises the connection.
Evenpay agrees the endpoint names and mapping, configures Kombo, and validates the import with you.
1. Agree the scope and arrange access
Before starting, request the current Evenpay Integration Pre-Check from your Evenpay contact or Evenpay support. Do not put API keys or passwords in the form.
Complete the Evenpay Integration Pre-Check with your HR or data owner and your Sympa administrator, including the standard and additional interfaces in its sections 3.2 and 3.3. Agree these with your Evenpay contact:
The countries, legal entities and employee groups to include, and how former employees are handled.
The fields you need and their source tables: employee details, organisation, salary, benefits, grade, job category and performance.
The history to import, its start date and the sync frequency. Include salary effective dates where you need history.
Anything that must be left out, any IT or security requirements, and any internal approvals needed before connecting.
Then ask your Sympa administrator or Sympa support to set up access that follows the Sympa Generic API specification, and to provide an API key and API secret. Sympa uses the API key as the username and the API secret as the password.
Keep the credentials safe: enter them only in the connection window in Evenpay. Never send them by email or chat, or put them in the pre-check form.
2. Configure the Sympa interfaces
Your Sympa administrator follows the Generic API specification for the interface structure and field aliases. Kombo reads one endpoint per standard data type. Use one shared prefix for all interfaces, and the same stable Employee_number in every employee-related interface. Agree the complete list of endpoints with Evenpay before building them.
When your data is in separate tables
If countries or employee groups use separate source tables, choose one table to fill each standard interface, such as GenericCompensation, and expose the others as additional interfaces (see step 3). Agree the approach with Evenpay before building. You can authorise the connection before the mapping is finished.
3. Add interfaces for additional tables
Adding the prefix to a table name isn't enough: each additional table needs its own API interface.
Create one interface per agreed source table, with the agreed field structure. Put the qualifier after the data type, for example GenericCompensationInternational, GenericBenefitsSE or GenericPerformanceRatings.
Use the same prefix as the standard interfaces. A different prefix can make the sync fail. Include the same Employee_number in every employee-related record.
Expose all agreed history, with Valid_from and, where available, Valid_until. For performance ratings, include an identifier for the rating scale.
Make sure the API key and secret can read both the standard and the additional interfaces.
List the endpoint names, source tables and field meanings in sections 3.2 and 3.3 of the pre-check.
Kombo creates standard salary history only from the standard Compensation endpoint, and only for employees who also have an Employment record. Additional endpoints don't create these records automatically. You don't need to combine tables in Sympa: Evenpay imports this data through the agreed mapping.
4. Authorise the connection in Evenpay
Accept your invitation to Evenpay and sign in with the account that will set up the integration.
Go to Settings β People & data β Integrations.
Find Sympa and select Connect.
In the connection window, enter the Sympa API username (the API key) and password (the API secret), then select Set up integration. Kombo's guide Sympa: How do I link my account? covers this step.
Tell your Evenpay contact when the connection is complete. If it fails, share the error message and the step where it happened, without the credentials.
History, grade and performance
Salary history: expose the historical entries with Valid_from and, where available, Valid_until. Kombo uses Valid_from as the effective date.
Grade and job category: include them on the compensation entries where they're stored. Evenpay maps fields from both standard and additional tables.
Performance: expose ratings through an agreed additional endpoint, such as GenericPerformanceRatings, with Employee_number, the rating, the rating scale identifier, and the review period or date where available.
Evenpay then completes the agreed field mappings, including the settings for additional interfaces, and checks the results with you. Nothing is imported until the mapping is finished and an import profile is enabled; regular use starts after validation.
5. Validate and start syncing
Review the first import with your Evenpay contact before using the data for analysis. Check a representative employee from each country, employee group and source table:
Coverage and identity: the expected employees and countries are there, employee numbers match, and there are no duplicates. Gender is filled in, because pay equity analysis needs it.
Employment and organisation: employing company, country, department, manager, job title, grade, category and working hours are correct.
Compensation: amounts, currencies and monthly or hourly pay basis match Sympa. Benefits use the agreed units and period and aren't counted twice.
History: earlier salary entries, effective dates and end dates are correct. Include an employee with a salary change and, where relevant, someone who moved between countries or source tables.
Performance: ratings match Sympa, with the right scale for each employee group.
Evenpay confirms when the mapping is ready and agrees the ongoing sync schedule with you.
Good to know
When you add countries, tables or fields later, tell your Evenpay contact so the mapping can be updated and a full sync run.
If the connection fails, ask your Sympa administrator to check the credentials and API access.
If a country, table or field is missing, check the shared prefix, Employee_number and field setup with your Evenpay contact.
Data showing up as a custom field doesn't by itself mean it has reached the intended Evenpay field. Check it during validation.
See also Managing a connection, Undoing an integration sync and Placing employees in entities.
Related articles
Was this helpful?
More in HR system connections
Connecting HiBobConnecting WorkdayConnecting DeelConnecting RemoteStill need help? Ask the team