Transferring Team Member data

Team Members are eligible for data transfer to PlanSource if they meet the basic data requirements. you also need to assign them to a Policy where you've selected US Benefits is active. You can assign the Policy to them directly, or to their HR Departments. Data transfer is then automatic.

Note

When you set up a new sandbox for an org where data transfers to PlanSource, remove the PlanSource configuration from the sandbox. Do this before changing team member data on the fields you've mapped to PlanSource fields in the sandbox. If you don't remove the active configuration, you risk transferring unintended changes to team member data in PlanSource. See US Advanced Benefits (PlanSource)

Tip The system can experience issues transferring a single benefit record for a team member from PlanSource to Sage People. This can happen even when all other benefits for the team member transfer successfully. The team member’s record will exist correctly in PlanSource but not in Sage People.
To resolve this, you need to check the validation rules you’ve set up in the benefit object.
For example, you can have a validation rule for a benefit object that states you must enter life insurance in increments of 10,000. But if this validation doesn’t exist in PlanSource, the record will fail. Sage People doesn’t have an error handling for this, so the benefit fails without informing you.
In this instance, you need to ensure you’ve done all validation in PlanSource or check the validation rules in PlanSource and Sage People match.