Introduction

Sapling can sync new hire data with your TeamSpirit account, saving your HR, People Operations, and Payroll manual data entry and removing the risk of errors, while providing a great new hire experience.

With the TeamSpirit Integration, Sapling will generate 3 CSV files each week delivered to a defined container of Azure blob:

  1. New hires in the past week (Users whose start date is in the past 7 days)

  2. Offboards in the past week (Users whose termination date is in the past 7 days)

  3. Data changes in the past week (Users with profile changes in the past 7 days)

How It Works

Setting up the Integration Step by Step

Step #1. Create or access current Storage Account in Azure

  1. Navigate to your Azure Portal → Storage Accounts

  2. Create a new storage account or choose an active storage account

  3. Navigate to Selected Storage Account → Security + Networking → Access Keys

  4. Click on Show Keys ( You should see the key appear and you will copy it)

  5. Retrieve Storage Account Name and Storage Keys

Step #2. Enable the TeamSpirit Integration in Sapling

  1. Navigate to the Integrations → Payroll → TeamsSpirit

  2. Enable the TeamSpirit Integration

  3. Enter your Storage Account Name, Storage Access Key, and Storage Container Name (This can be any name that will be used to create the container in the storage account of Azure blob)

  4. Select the date you want the CSV files to be sent to TeamSpirit

Step #3. Confirm the Integration settings

  1. Review the filters and make your selection

  2. Select on Next → Active

Overview

IRIS FMP Amity (IRIS FMP Teamspirit) is a cloud-based solution featuring advanced functionality and security. This fully integrated web-based HR and Payroll solution provides full functionality on any device via mobile responsive screens.

Integration Fields

Sapling is continually expanding the number of fields that sync between Sapling and IRIS FMP TeamSpirit.

  • Here is a full list of Sapling and IRIS FMP TeamSpirit Integration Fields.

Key Factors to be aware of

Integration Flow

  • 1-way (Sapling to TeamSpirit) payroll integration supported through a CSV file upload to a mutual SFTP site on a weekly basis that includes all new hires, all employee updates, and all offboarded users for that week.

  • First, the CSV files will be sent to the S3 server and then from the S3 server, the files will be sent to the provided container in Azure Blob.

  • CSV Files will be sent on the day configured between 8:00 to 8:30 AM according to the company timezone.

Azure Blob Management

  • These files are imported into Teamspirit from the Azure blob storage through routines inside Teamspirit itself - our job is to get the correct data to the Azure blob storage each week when this integration is active.

CSV Files Naming Convention and Delivery

The 3 files will follow the naming convention below:

  • starters_[company_id]_[company_sapling_domain]_[datetime_generated_with_no_spaces]

  • leavers_[company_id]_[company_sapling_domain]_[datetime_generated_with_no_spaces]

  • changes_[company_id]_[company_sapling_domain]_[datetime_generated_with_no_spaces]

  • The files will be delivered on a day of the week configured in the integration setup to an azure blob storage site configured in the integration setup.

CSV Files Overview

  • The “starters” file contains all employees with a start date within the past 7 days.

    • This includes rehires.

  • The “leavers” file contains all employees with a termination date within the past 7 days.

  • The “changes” file contains all employees with a data change within the past 7 days.

    • Non-effective-dated fields are included if changed in the past 7 days.

    • Effective-dated fields are included if changed in the past 7 days AND the effective date is on or prior to the date the file is generated.

  • Ultimately when this file is received, Teamspirit will take this data and overwrite the user’s profile with the new file and this will update the user’s profile in Teamspirit.

  • For fields with no effective dates, we take all the changes from the last 7 days.

  • For fields with effective dates (ie Job Details, Emp Status, etc ), we only include those changes if the effective date of those changes is in the last 7 days (not the date the change was made).

Filters in Sapling

Sapling supports filtering, and allows you to identify what users you want to keep synced based on the following:

  • Location

  • Department

  • Employment Status

💡Looking to do more?

Did this answer your question?