The Finch 360 integration lets you send contribution rate changes back to the payroll provider. At a high level:

• The custom report you add to Relius Reporting generates the output file in the format Finch requires.

• You set up an STP task group to run that report automatically.

• A custom task renames the generated file to the format that Finch requires

• The STP task group uploads the renamed file to the 360 subdirectory on the same Finch-owned SFTP server used for the 180 integration.

The output is a .csv file in the following format:

Each output file contains records for a single plan. The STP job is set up to generate a separate file per plan rather than combining multiple plans into one file.

How the custom report determines the RateEffectiveDate

The custom report you add later in these directions applies this logic to determine the date that populates the “effective date” field, RateEffectiveDate:

• If you allow enrollment prior to plan entry, a participant can have a contribution effective date before they're eligible to defer.

  • If the participant hasn't met the entry requirements, the report uses the projected entry date.

• If the participant has met the entry requirements but the entry date is blank, the report uses the projected entry date. Example: if the participant met the requirements on 7/15 and entry is the first of each month, the entry date is 8/1

  • If an eligibility transaction was not posted on or after 8/1, the entry date will not be populated.

• If the plan entry date is prior to the contribution rate change effective date, the custom report uses the contribution change date

Set up a Plan Group

Set up a Plan Group and add every plan that will send contribution rate change files back to Finch. Without a Plan Group, you'd have to run the report across all plans, which can take significantly longer.

Create the Required Folders

Create the following folders:

• Payroll_360 folder under your FINCH payroll folder, containing a PROCESSED subfolder.

• BATCH folder under your Q Drive. Don't use an underscore or other special character in this folder name.

Rename the generated report files to match Finch's format

Finch requires the file name to include only a Plan ID and a date, in either order, and nothing else unique to the file. Relius generates the report file with extra information built into the name, so this task sets up a process to rename the generated file down to just what Finch requires. It uses the BATCH folder you created in task 2.

Confirm your global report output naming convention

Review the report output naming convention default settings for the Plan Group you'll use for this integration. The order of the plan id and date stamp does not matter.

• Report Writer Reports > File > Output Naming Convention

• Confirm the naming convention includes a Plan ID and a date/time stamp. Either can come first.

Create the FinchRename.bat File

This script in the .bat file strips the file name down to the required format for Finch's system:

1. Open NotePad in the ASP environment.

2. Copy the script below with two modifications

   1. Replace the placeholder ABC100 with your Relius client id.

   2. Replace the place holder FINCH with your Finch\Payroll_360 folder.

      1. e.g. FINCH -> FinchPayroll

3. Save the file to the BATCH folder you created above.

   1. File name: FinchRename.bat

   2. Don't use an underscore or other special characters in the file name.

@echo off
setlocal enabledelayedexpansion

:: Loop through all .txt files in the folder (change *.csv to match your files)

for %%F in (\\pdc1wwraradap02\ABC100\FINCH\Payroll_360\*.csv) do (
set "filename=%%~nF"
set "ext=%%~xF"
:: Remove the last 11 characters from the filename (e.g., "_144746_001")
set "newname=!filename:~0,-11!"
:: Rename the file
ren "%%F" "!newname!!ext!"
)

endlocall

Add the custom contribution changes report to the Custom node in Relius Reporting

1. Finch emails you the FINCH_360_Contr_Chgs report file (for example, FINCH_360_Contr_Chgs_v3.rpt). The version number in the file name changes as Finch updates the report, so always use the most recent file Finch sent you rather than a specific version number.

2. Copy the report file Finch emailed you to your Custom Report folder.

3. Go to Relius > Reporting > Report Writer Reports.

4. Highlight Custom.

5. Select File > New > Report.

6. Select the FINCH_360_Contr_Chgs report file.

   

7. Enter a Description for the report 

   

8. Click Add.

Add a custom task to run FinchRename.bat

This task requires the FinchRename.bat file you created above.

1. Relius main menu: STP >Task Scheduler > File > Custom Tasks

2. Click on the PLUS sign to add a custom task

   1. Short Name: Limit = 15 Characters

   2. Program Name: FULL file path to the BATCH folder: \\pdc1wwraradap02\ABC100\Batch\FinchRename.BAT

Test the custom task to rename the file

1. Create a file in NotePad with the word TEST

2. Save the file:

   1. name:  deferral_ABC123_2026-08-10_140987_001.csv

   2. file path: pdc1wwraradap02\ABC100\FINCH\Payroll_360\

      1. Reminder that ABC100 is a placeholder for your Relius Client ID.

   3. Choose the file type All Files (will make it so .csv is not counted as characters in the file name)

3. Create a new task group named:  TEST – Custom Rename.

   1. In the task scheduler, click the green + button

   2. Select add new group

4. Add the Finch File Rename task to the task group.

5. Save the task group

6. Open the Job Queue STP > Job Queue

7. Click on the PLUS sign to add a job to the Job Queue

8. Add the TEST – Custom Rename task group to the job queue

9. Check if the jobs runs as successful or errors

   1. If the job runs as “Successful”

      1. Go to the FINCH\Payroll_360 folder

      2. Verify that the file named: deferral_ABC123_2026-08-10_140987_001.csv is now deferral_ABC123_2026-08-10.csv

   2. If the job runs as “Errors”

      1. The Output will not show information related to the error.

      2. Check the Custom task to make sure that the Program name is correct

         1. Copy the Program name to NotePad to verify

      3. Check to make sure that the program name FinchRename.bat is in the BATCH folder

      4. Verify that there are no special characters in the file path or file name.

Create a copy of the FTP file transfer task group

We are using the same Finch SFTP server and credentials that are used for the 180 file delivery. You can create a new one from scratch if you have saved the public and private key files, instead of copying the existing one. These directions are to make a copy of the existing task group so that you do not have to find and upload those public and private key files.

1. Open the Relius STP task group that was set up in STEP 5, item 1 of the Finch Relius setup guide.

   1. Relius > STP > Task Scheduler:

   2. Double click on the task group: Finch - SFTP Payroll Transfer (yours may be named differently) to open the Task Group.

      

   3. Select Save As option (bottom right) - this is the command that makes a copy.

   4. In the Task group name box, enter the name for the new task group. Something such as Finch - 360 payroll deferral changes

      

   5. Click OK.

2. Add the following tasks to the NEW Task Group (created in step 1)

   1. Create Single Report

   2. File move/copy

   3. Finch File Rename (name of the customer task setup above).

      

   4. Click of the FTP file transfer task under Selected Tasks

   5. Click on "Move Down" until this task is the last task in the list:

   

3. Set the Task Parameters for the 4 selected tasks

   1. Create Single Report Parameters

      

   2. File move/copy - creates a copy of the original file in the Payroll_360\PROCESSED folder (or what you named it).

      

      

   3. Finch File Rename - custom file rename task. No parameters for this task.

   4. FTP File Transfer