This article describes how to configure the Voya Deduction Feedback Split by Location Code moov to PrismHR. This moov is intended for Voya plans where there are multiple locations within a single plan. If your client's plan does does not have multiple locations, please see How to configure the Voya Deduction Feedback to PrismHR moov.
PrismHR - Configure a Web Service/API User
Before detamoov can update deductions in PrismHR, the Allowed Methods for Retirement Providers to PrismHR Integrations (known as "360") must be added to the Web Service/API User. These methods can be found in the Configuring a Web Service/API User in PrismHR article.
To adopt the Voya Deduction Feedback Split by Location Code moov, click on the moovs option on the left and click the Add button in the upper right.
Then expand the 'Retirement - Retirement to Payroll' section, click on the 'Voya Deduction Feedback Split by Location Code' moov and click USE THIS MOOV by scrolling down to the bottom of the right sidenav.
In the moov configuration section, click the Add button to add a new client to the moov.
Client/Entity - either select an existing client or click the + sign to create a new client.
Status - Voya has a testing phase to allow you to pull a test file before receiving live feedback files. Set this field to 'Testing' during the testing phase. Once Voya instructs you that live files are ready, you will need to change this to 'Active' and then save the configuration.
Expected Frequency - the client's payroll frequency
File Name Starts With - Enter your client's Voya Plan ID into this field
File Name Contains - csv
Note: make sure that the File Name Starts with field matches as this can cause issues pulling the Voya feedback file and updating the payroll platform.
To automate the 360 integration, configure the SFTP schedule. Click the SFTP banner under the Trigger - SFTP Pull Data Trigger step and click Add.
On the New SFTP Configuration section on the right, select the SFTP Pull option from the Premier Integration menu. Then select either "Every X weeks" or "On certain days of the month", depending on how often you would like detamoov to check for new deduction files. We recommend that you check for feedback files at least twice a week. In the example below, we have set up a schedule to check for files twice a week on Tuesdays and Fridays.
Overrides for Filter Step for each Location
To properly split the Voya Deduction Feedback file by Location Code, you will need to provide filter overrides for each location. For example, if our client's Voya plan has three locations that we expect in the feedback file, then we need to set filter overrides for the first three filter steps. If there are four locations, then four filter overrides are needed, and so on.
To set a filter override, click on the Filter Overrides panel, click the ADD button.
Then select Filter 1: Location Code (Div/Sub Id) and click ADD OVERRIDE.
The default filter is set to filter out any record where the value is not 9999. You will need to replace the value 9999 with the Location Code you expect and click OK.
The above filter override will need to be repeated for each Location Code you expect in the feedback file. Any other Filter steps beyond the number of Location Codes you expect should not be changed.
Here is a table showing the step(s) that need a filter override based on the number of Location Codes expected in the feedback file:
| # of Location Codes | Filter Steps to Override |
| 1 | Step 4 |
| 2 | Step 4, 9 |
| 3 | Step 4, 9, 14 |
| 4 | Step 4, 9, 14, 19 |
| 5 | Step 4, 9, 14, 19, 24 |
| 6 | Step 4, 9, 14, 19, 24, 29 |
| 7 | Step 4, 9, 14, 19, 24, 29, 34 |
| 8 | Step 4, 9, 14, 19, 24, 29, 34, 39 |
| 9 | Step 4, 9, 14, 19, 24, 29, 34, 39, 44 |
Once you have provided a filter override for each Location Code, scroll to the bottom of the page and Click Next. Then click Save on the summary page
Configuring the Voya Deduction Feedback to PrismHR moov
Each client location will need to be separately configured for the Voya Deduction Feedback moov. To adopt this moov, click moovs on the left, click the Add button in the upper right, locate and click on the Voya Deduction Feedback to PrismHR moov. Then click ADD THIS MOOV.
The Voya Deduction Feedback to PrismHR moov provides a notification once the moov is complete with a summary of the retirement plan and loan changes that were made in PrismHR. The notification can be sent to any email address you wish and can also be configured to send to multiple email addresses.
To edit the send file step, click on the cog icon under the Action - Send File step on the left. Then toggle the "Use default parameters" off and enter in the email addresses you would like to receive the notification. If you would like to enter multiple email addresses, separate them with a comma. A Reply to email is also required in the event that a recipient of the notification replies to the email.
Note: these settings apply to any client configuration you set up for this specific moov. You also have the ability to configure the send file step for each client configuration if you wish to add or remove email addresses per client.
To save your parameters click on the Save Changes button.
In the moov configuration section, click the Add button to add a new client to the moov.
Client/Entity - either select an existing client or click the + sign to create a new client.
Status - Set to Active
Expected Frequency - the client's payroll frequency
File Name Starts With - [Location Code]-[Voya Plan ID]
File Name Contains -
When adding a new client configuration, it is important to understand the naming convention used in the Voya Deduction Feedback Split by Location Code moov. Each Location Code file is renamed using the naming convention:
[Location Code]-[Voya Plan ID].csv
To ensure that the each Location Code file is associated with the correct client configuration, the File Name Starts with and File Name Contains fields must be correct. For example, if we provided a Filter Override for Location Code 1001 and Voya Plan ID 12345, our ID and Source would look like this:
Note: make sure that the File Name Starts with field matches as this can cause issues pulling the Voya feedback file and updating PrismHR.
Click Next once you have completed the ID and source section.
When using the Voya Deduction Feedback Split by Location Code, the SFTP Pull Data Trigger step should NOT be configured. The banner under the SFTP panel should read 'Not yet configured'.
The Voya Deduction Feedback Split by Location Code moov decrypts the Voya feedback file. Since decryption is already done on the Voya Deduction Feedback Split by Location Code moov, you will need to set the 'Select skip behavior' dropdown to 'Always skip'.
The PrismHR Plan ID is required for detamoov to update changes via their API. A field override is required to provide this as the Plan ID in Voya may be different from the Plan ID in PrismHR.
The PrismHR Plan ID can be found in Benefit Plan Maintenance/Retirement Plans:
To create a field override locate step 7 Action Transform and expand the Field Overrides section.
NOTE: There are 3 separate Transform steps on the Voya Deduction Feedback to PrismHR moov. Make sure are you creating the field override on step 7 - Action Transform.
Then click the ADD button and select field 8: Plan ID and enter you the PrismHR Plan ID in the Override value field.
If detamoov receives a Loan in the feedback file, it is important to understand the relationship between the Voya Loan Number and the TPA Loan Identifier field in PrismHR.
If an employee makes a change to an existing loan in Voya, the Voya Loan Number passed in the feedback file must match the TPA Loan Identifier fields in PrismHR. If these don't match, a new loan will be created for this employee instead of an update to the existing loan.
Configure the PrismHR Retirement 360 Step
To configure the PrismHR Retirement 360 step for you client, locate the Action - PrismHR Retirement 360 step, expand the PrismHR API panel and click ADD.
On the side panel that appears, select your PrismHR Premier Integration and enter in the Client Id.
If you have a Multi-Entity Group set up for your clients, please see the Using Multi-Entity Groups article for information on how to use a Multi-Entity Group on your configuration.
Optionally, you can toggle the 'Skip Employee Retirement Plan ID Validation' switch on. This is applicable when your client has multiple retirement plans inside PrismHR and you don't want detamoov to validate the Plan ID field for each employee. If this option is toggled on, detamoov will skip the validation of the employee retirement plan ID when updating existing deferrals and loans. Since most situations require retirement plan ID validation, this option is toggled off by default.
You can also enter in one or more email addresses in the Error Messages Email. If left blank, all detamoov users on your account will receive emails if the PrismHR Retirement 360 step fails.
Click OK to complete the PrismHR Retirement 360 configuration.
At the beginning of this article you configured the send file step for the moov to send a notification once the moov had completed. You also have the ability to configure the send file step for each client configuration if you wish to add or remove email addresses per client.
To override the send file step, locate the Action - Send File step and toggle the "Use default parameters" off and enter/remove email addresses from Email Address and Reply To fields. If you would like to enter multiple email addresses, separate them with a comma.
To complete the configuration for your client, click the Next button at the bottom of the page and then the Save button on the moov summary page.
