Finch's Relius integration ensures that employer census and payroll data is available for each payroll. Please follow these steps to ensure the integration is set up correctly:
Steps
Step 1: IP Address Allowlisting: Connecting your Relius instance with the Finch SFTP server
Step 2: Employer and Plan Setup: Ensuring correct setup for historical employers and their plans
Step 3: DER Setup: Configuring DER to reflect Finch file schema
Step 4: DVC Rules: Creating Data Validation Center rules for monitoring and validation checks
Step 5: STP Task Groups: Setting up tasks to fetch files from the SFTP, deposit them into an ASP folder, and process payroll data
General Requirements
Importing a payroll file via automation requires the setting up of a Global Data Entry Routine (DER). You will need a Finch-specific Data Entry Routine for the files delivered by Finch, since Finch sends the data in the same format regardless of the payroll provider.
Global Data Entry Routine Requirements
Minimum requirements:
- Plan Id
- Payroll Frequency
- Pay End Date
Recommended additions:
- Payroll Sequence Number
Note that there can only be one pay schedule per frequency. For example, there should only be one semi-monthly frequency and one weekly frequency.
The sources and payroll elements for all plans on Finch must be consistent.
For example, if all plans do not have the User Payroll element 1 set to Roth and that payroll element assigned to the Roth source, the import will not work correctly for all plans. See Step 2: Global DER for more information.
Recommendations
- Set standards for new plan implementation related to the Employer User Payroll elements and Source assignment. Direct the plan onboarding resources to set up all plans using the same User Payroll Elements.
- Run an analysis to pull the Employer user Payroll Labels and Source payroll elements out of Relius for review (for all plans on the Finch integration). See Step 3 Employer and Plan Setup for more information.
- Modifications during the plan year are not recommended. If required, it is recommended that the change be done at or near the beginning of a plan year.
- If you have to modify a plan that is currently using user defined payroll element 2 for ROTH to use payroll element 1, it cannot be done without certain risks:
- Reversal and re-posting of prior transactions
- The compensation form in the Census will not match the allocated amounts.
- Recommendation: Create new User Defined Payroll fields going forward.
- If you have to modify a plan that is currently using user defined payroll element 2 for ROTH to use payroll element 1, it cannot be done without certain risks:
- Set up a Plan level Extended Data field named: PRProvider to hold the payroll vendor for each plan. This will allow you to easily report on the plans using payroll integration.
- Setup a folder: PR_Integration
- Folder under PR_Integration for each vendor
- Under each Vendor add an ARCHIVE folder
- DO NOT use spaces in the directory name.