First, go to Company Settings > Data Management > HR system integration > Connect.

If you’re already connected — there is nothing to do! Feel free to jump to ‘Configure your HRIS field import into Ledgy’

At a minimum Ledgy will need "View public data" to retrieve basic employee data.

Paste your Humaans API Key and click on Submit.

You need to configure the fields before initiating sync. Hit ‘Configure’ to open up the modal below. You are able to change the configuration later and at any future point.

2.1. Stakeholder identifier should be a unique identifier, and the value should exist for all employees in HRIS. In Humaans case, the identifier is “Work email”.

2.2. Stakeholder email: Choose which employee field to map to Ledgy’s primary email.

2.3. Additional fields to import allow you to optionally import any of the following fields:

2.4. Hover over the “❓ Some basic stakeholder fields” to see the default fields mapped from HRIS into Ledgy

2.5. For Humaans, it is not possible to add additional fields to Ledgy from your HRIS.

2.6. You can add "Sync if" conditions to specify which employees to sync in Ledgy.

⚠️ Note: filters are additive, meaning that stakeholders must match all conditions for a rule to apply to them. You can use ‘OR’ conditions to select multiple values for a given filter. For example: you may want to sync employees across multiple countries, and of multiple groups.

Once you have setup the configuration, you can sync stakeholders. Hit ‘sync’ to preview stakeholders that will be created or updated in Ledgy.

First, go to Company Settings > Data Management > HR system integration > Connect.

If you’re already connected — there is nothing to do! Feel free to jump to ‘Configure your HRIS field import into Ledgy’

At a minimum Ledgy will need "View public data" to retrieve basic employee data.

Paste your Humaans API Key and click on Submit.

You need to configure the fields before initiating sync. Hit ‘Configure’ to open up the modal below. You are able to change the configuration later and at any future point.

2.1. Stakeholder identifier should be a unique identifier, and the value should exist for all employees in HRIS. In Humaans case, the identifier is “Work email”.

2.2. Stakeholder email: Choose which employee field to map to Ledgy’s primary email.

2.3. Additional fields to import allow you to optionally import any of the following fields:

2.4. Hover over the “❓ Some basic stakeholder fields” to see the default fields mapped from HRIS into Ledgy

2.5. For Humaans, it is not possible to add additional fields to Ledgy from your HRIS.

2.6. You can add "Sync if" conditions to specify which employees to sync in Ledgy.

⚠️ Note: filters are additive, meaning that stakeholders must match all conditions for a rule to apply to them. You can use ‘OR’ conditions to select multiple values for a given filter. For example: you may want to sync employees across multiple countries, and of multiple groups.

2.7. Update your stakeholders:

Once you have setup the configuration, you can sync stakeholders. Hit ‘sync’ to preview stakeholders that will be created or updated in Ledgy.

By default, we now map more data from your HRIS into Ledgy, and you can select from optional fields to also map into Ledgy.

For fields that are not supported by default by your HRIS, please follow FAQ for “How do I setup HR field mappings from my HRIS into Ledgy?”, to request the field mapping via support chat. You can then map the field mapping into a Ledgy custom field.

Oh no! Possible reason:

If this issue cannot be resolved by changing the API key permission or by adding the missing field via a custom field (see FAQ for “How do I setup HR field mappings from my HRIS into Ledgy?”) - you can manually input field value in Ledgy for a Stakeholder, or via bulk excel.

In Humaans case, it is not possible to map custom fields with your Ledgy account.

Ledgy stakeholder custom fields are company-wide fields that you create in Ledgy. They exist on each stakeholder.

Ledgy requires a Stakeholder identifier to match existing stakeholders in Ledgy with employees in HRIS. If no identifiers exist in Ledgy and the names do not match 100% between your HRIS platform and Ledgy, then duplicates may be created in Ledgy in the syncing process.

If you have created your stakeholders without your HRIS platform in your Ledgy account and now wish to connect your HRIS platform, please follow the steps to ensure that the sync doesn't create duplicate stakeholders.

Update your stakeholders:

Correct mapping:

Now you can sync Ledgy with your HRIS platform, and we will not create any duplicates!

You can still use the Data Management page to manage your stakeholder’s custom fields.

When syncing Ledgy with your HRIS, terminated employees are not automatically recognised as terminated by Ledgy. Thus, if not specified otherwise, Ledgy will prompt you to create or update them.

There are different options for managing the terminated employees: