Skip to main content

HRIS Integration Settings Explained

We have added a bunch of new settings helping users control how the integration behaves with their HRIS.

Written by Aubree Thomas
Updated this week

You can create these settings as you are setting up your integration or you can adjust these any time in the HRIS integration section of org details.

The following are explanations of the settings you will see as you set up your HRIS integration.

Synced Entities: If the customer used Finch's multi-entity sync, this will show each entity within their HRIS that we are pulling data from.

Sync Frequency: This determines how often SixFifty will sync with Finch. By default, Finch syncs to the HRIS system every 24 hours, so if you want the most up-to-date data, you should also set this setting to daily. That means there could be a 24-48 hour window in which data in SixFifty does not match a change you made in your HRIS, but beyond that it should always be in sync.

Automatically send portal invites when new contacts are synced: When this is turned ON, every time a new contact gets added to SixFifty they will get an email sent to them inviting them to the employee portal.

Create new contacts from inactive/terminated HRIS records: When this is turned OFF, we won’t ever create SixFifty contacts from HRIS records that are inactive/terminated. When this is turned ON, we sync all inactive HRIS records and automatically add them as inactive records in SixFifty. Most customers will want this OFF to avoid noise.

Please note: If a record was Active in your HRIS that we synced in SixFifty, and then later becomes Inactive, we will keep the record of that contact but make it Inactive in our system.

Automatically reactivate inactive contacts when they become active in the HRIS again: If this setting is turned ON and if we have records in our system that are Inactive and are synced from the HRIS, we will re-activate that person if their status is shown as Active in the HRIS. This should likely be ON unless the SixFifty Admin has inactivated a bunch of records in SixFifty that are still active in the HRIS and the SixFifty Admin does not want future syncs to reverse that. If that is the case, this setting should be turned OFF and the Admin should be informed that they will need to manually perform contact re-activations whenever they occur.

Only sync contacts with a “Work” email in the HRIS: This means if the contact does not have this field, then we will not create a record in SixFifty for that contact. We will instead give an error message in the sync log for that contact saying that work email was missing. If the Admin prefers that their employee's SixFity portal accounts be created with the HRIS work email, this setting should be turned ON to ensure we don't create a record using a personal email (in cases where there is no work email available in the HRIS sync).

Allowed Employment Types:

This lets the Admin filter which contacts should be considered for the sync based on their listed employment type in Finch. These employment types will be one of the following: Employee, Contractor, or Null. If all boxes are unchecked and no filter is applied, we will sync all of the employment types. The Admin should know that if this field field is blank in Finch and they have not selected the Null checkbox, then we will not sync the contact.

Allowed Employment Subtypes:

This lets the Admin filter which contacts are considered for the sync based on their listed employment subtype in Finch. The employment subtypes will be one of the following: Full Time, Part Time, Intern, Temp, Seasonal, Individual Contractor, or Null. If all boxes are unchecked and no filter is applied, we sync all of the employment subtypes. The Admin should know that if the field is blank in Finch and they have not selected the Null checkbox, we will not sync the contact.

Please note: if the Admin changes the configuration to restrict the sync, we will not automatically discard existing contacts that will no longer be considered in the sync. They will stay in SixFifty until the Admin inactivates or deletes them.

Did this answer your question?