ftwilliam.com - Census Data Transfer

One of the largest conveniences to emerge from PensionPro's partnership with ftwilliam.com is the ability to transmit a Plan's collected census data to ftwilliam.com for compliance testing with a single click. PensionPro users can send the census and receive the results via email, bypassing the necessity of signing in to ftwilliam.com for testing needs.

 

Requires Add-On: Automate Compliance

Compatible Tiers: Team, Business

 

Article Contents

 

 


 

Overview of ftwilliam.com Census Transfer

 

The census transfer functionality works alongside PlanSponsorLink to simplify the process of collecting census data from the Plan Sponsor and entering it into ftwilliam.com. Rather than exporting the collected participant data from PensionPro and then importing it into ftwilliam.com, PensionPro can transfer it directly. Once transferred, compliance testing will be performed automatically.

 

Before this functionality can be used, an integration to ftwilliam.com must be established, and Plan records in PensionPro must be linked to corresponding plans in ftwilliam.com. For more information, refer to the following articles:

 

 


 

Sending Census Data to ftwilliam.com

 

After the Plan Sponsor completes Data Collection and the census information has been verified, it can be sent to ftwilliam.com via the following steps:

 

  1. Navigate to the Data Collection in PensionPro and open the Employees view.
  2. At the top-right of the grid, select Moremore_options.png > Send & Run Tests in ftwilliam.com.

 

PensionPro will transmit all census information to ftwilliam.com, including any relevant principals and family members. A timestamp will be added above the Employees grid to indicate the last time this action was performed. The user will receive two emails: the first confirming that the census data has been queued for transfer, and the second once the data has been successfully sent to ftwilliam.com.

 

Warning: Family relationship values other than Child, Parent, Grandparent, or Spouse may default to Child in FTW. We are currently investingating this behavior; please review these items in FTW if needed.

 

Once the census data is sent, ftwilliam.com will perform all applicable compliance testing (per the FTW Compliance page). Additionally, ftwilliam.com will send the results of the compliance testing via email.

 

The option to send the census to FTW is unavailable for me. Why?


The following conditions must be met before the census can be transferred to ftwilliam.com:

  • The Plan must be linked to FTW.
  • The year end must exist for the Plan within FTW.
  • All Data Collection steps must be complete.
  • The Project cannot be aborted (Business tier).

 


 

Appendix: Table of Census Field Mapping

 

The following charts show how PensionPro items are mapped to corresponding FTW items when the "Send & Run Tests" option is used and what validation rules are in place.

 

PensionPro FTW Field Data Rules
Last Name LastName Text (Alphanumeric)
First Name FirstName Text (Alphanumeric)
SSN SSN Format: 123-45-6789 or 123456789
Date of Birth BirthDate Date (MM/DD/YYYY)
Original Date of Hire EmploymentHireDate1 Date (MM/DD/YYYY)
Gender Gender Accepted values: Male, Female
Date of Rehire EmploymentHireDate2 Date (MM/DD/YYYY)
Company Division DivisionCode Text (Alphanumeric)
Hours Service_EligibilityHours Integer
Gross Compensation Compensation_Statutory Decimal (2 places)
Box 3 Compensation HPICompensation Decimal (2 places)
PreTax Deferral Contribution_ElectiveDeferral Decimal (2 places)
Roth Salary Deferral Contribution_Roth Decimal (2 places)
Employer Match Contribution_Matching Decimal (2 places)
Employer Contribution Contribution_NonElective Decimal (2 places)
Other Contribution Contribution_OtherPlanAveBen Decimal (2 places)
Address 1 Address Text (Alphanumeric)
Address 2 Address2 Text (Alphanumeric)
City City Text (Alphanumeric)
State State Text (Alphanumeric)
Zip Code Zip Text (#####)
Middle Initial MiddleName Text (Alphanumeric)
Employment Status EmploymentStatus1 Accepted values: Hire, Terminate, No Change
Date of Separation EmploymentTermDate1 Date (MM/DD/YYYY)
Date of Death EmploymentTermDate1,
RMDDeathDate
Date (MM/DD/YYYY)
Date of Retirement EmploymentTermDate1 Date (MM/DD/YYYY)
Separation Reason TermReason1

Accepted values: Termination, Death, Disability, Retirement, LOA-Paid, LOA-Unpaid, LOA-FMLA, LOA-Military, N/A. Other values will be mapped as Termination.

If Date of Death, Date of Retirement, or Date of Termination is present and Separation Reason is blank, it will be set to an appropriate value.

Work Email EmailAddress Text (#####@###.###)
After-Tax Employee Contribution Contribution_AfterTax Decimal (2 places)
Compensation from Entry Date Compensation_Statutory_FromEntry Decimal (2 places)
Safe Harbor Match Contributions Contribution_SafeHarborMatching Decimal (2 places)
Safe Harbor Non-Elective Contributions Contribution_SafeHarborNE Decimal (2 places)
User Defined Number 1 Census_UDFNumber1 Decimal (2 places)
User Defined Number 2 Census_UDFNumber2 Decimal (2 places)
User Defined Number 3 Census_UDFNumber3 Decimal (2 places)
User Defined Number 4 Census_UDFNumber4 Decimal (2 places)
User Defined Number 5 Census_UDFNumber5 Decimal (2 places)
User Defined Text 1 Census_UDFText1 Text (Alphanumeric)
User Defined Text 2 Census_UDFText2 Text (Alphanumeric)
User Defined Text 3 Census_UDFText3 Text (Alphanumeric)
These FTW fields are mapped one-to-one from the employee census

 

PensionPro FTW Field Data Rules
If the employee matches a Principal entry, whether they are an Officer Officer Values: Yes, No
If the employee matches a Principal entry, their Ownership Percentage PercentageOwnership Decimal (2 places)
If the employee matches a Family entry, a letter code indicating who they are related to (thus "grouping" all related individuals) FamilyGroup Values: None, A, B, C, D, E, F, G, H, I, J, K, L, M, N
If the employee matches a Family entry, their Relationship to the Principal FamilyGroupRelation Accepted values: Spouse, Child, Parent, Grandparent, N/A
These FTW fields are mapped based on census entries as well as data from the Principal and Family steps