Skip to main content

Sapling - Sequoia Benefits Integration Guide

Matt Troy
Updated

Introduction

For Kallidus customers who use the Sapling product, you can sync new hire data with your Sequoia account, saving your HR, People Operations, and Payroll manual data entry and removing the risk of errors, while providing a great new hire experience. This is done by Sapling sending new hire data to the Bswift SFTP service.

 

With the Sequoia Benefits integration, Sapling will:

  1. Create Users: When a user completes their Sapling profile, the user data will be sent to BSwift. 

  2. Update User Attributes: When a user attribute is changed in Sapling, the corresponding user profile in BSwift will automatically be updated. 

  3. Deactivate Users: When a user is offboarded in Sapling, the corresponding user in BSwift will automatically be terminated

*The data is processed overnight (1:30 am PST) and then sent via a CSV file to Sequoia shortly after.


This article covers the following topics:

How It Works

MicrosoftTeams-image.png

 

 

Setting up the Integration Step by Step

Step #1. Enable the Sequoia Benefits Integration in Sapling

  1. Navigate to the Integrations → Payroll → Sequoia

  2. Enable the Sequoia Benefits Integration

  3. Enter your Sequoia Benefits account information

    • Bswift hostname
    • Bswift username
    • Bswift password
  4. Enable Bswift auto-enroll

 

Step #2: Confirm the Integration settings

  1. Apply any Group Filters if necessary 
  2. Click Next to review your setup, then Activate

Overview

Sequoia brings the technology, guidance, and community to help HR leaders drive deep business impact through their programs.

 

Integration Fields

Kallidus is continually expanding the number of fields that sync between Sapling and Sequoia Benefits. 

Please note that some fields are required in order to sync users from Sapling to Sequoia. It is not possible to exclude or custom map any of the supported fields above, or map any additional fields at this time. 

Key Factors to be aware of

Data Syncing Management

Once the SFTP details are added to Sapling, each night Sapling creates a CSV with the required data validations at 1:30 am PST and sends this to the BSwift SFTP service. The data is saved in Sapling’s database and a confirmation email to Sapling's internal users.

  • For new hires and data changes: The data is processed overnight (1:30 am PST) and then sent via a CSV file to Sequoia shortly after.
  • For terminations: The termination information goes to Sequoia the day after the actual termination date. For example:
    • Monday 2:00 pm - Team member is terminated in Sapling with last day set to Thursday
    • Thursday 5:00 pm - Team member's terminated information sent from Sapling to Sequoia
    • Friday 1:30 am - Team member is  terminated in Sequoia

Fields Management

  • For the fields to sync correctly, the field names in Sapling and Sequoia Benefits must match.

  • For the fields to sync correctly, the field options must match between Sapling and Sequoia Benefits must match.

Profile Creation Management

Team members' profiles are sent to Sequoia Benefits once they have completed preboarding. If a team member's profile is not in the CSV file, it could be due to the following:

  • Filters configured are not applicable to the team member
  • Required fields are not completed
  • Required fields do not have an acceptable value

Sequoia Integrated Platform

We only integrate with Sequoia on BSwift (benefits), not Sequoia One (their PEO model for payroll). 

 

Filters in Sapling

Sapling supports filtering, and allows you to identify what team members you want to send to Sequoia Benefits based on the following group filters:

  • Location
  • Department
  • Employment Status

💡Looking to do more?

Related articles