You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Home > moovs > How to configure a moov - Payroll to Retirement > How to configure an Alerus 3(16) moov
How to configure an Alerus 3(16) moov
print icon

 

Note: Alerus supports multiple integration types, including the standard Alerus moov and the Alerus 3(16) moov. Please verify which moov applies to your client before proceeding, and confirm that you have received the correct plan specifications from Alerus.

 

This article describes how to configure a client for the Standard 401k to Alerus 3(16) moov definition.  Each client configuration will vary based on their plan specification and will need to be configured accordingly.

 

If you have not already done so, please add the Standard 401k to Alerus 3(16) moov to your account by following these steps.

 

Once the Standard 401k to Alerus 3(16) moov has been added to your account, access the moovs section on the left side menu and click on the Standard 401k to Alerus 3(16) moov.

 

 

Notification Settings

 

The Standard 401k to Alerus 3(16) moov provides a notification for when the moov is complete.  The notification can be sent to any email address you wish and can also be configured to sent to multiple email addresses. 

 

To edit the notification step, click on the cog icon under the Action - Notify 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 notification 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.

 

Configure a client

 

In the moov configuration section, click the Add button to add a new client to send retirement data to Alerus 3(16).

 

 

Complete the ID and source

 

Client/Entity - either select an existing client or click the + sign to create a new client. 

Status - Alerus doesn't have a test filename convention or test SFTP directory while in a testing phase, so you can set this to Testing or Active if you are ready to send retirement data to Alerus.  Please contact Alerus prior to sending a test file.

Expected Frequency - the client's payroll frequency

File Name Starts With - typically the client or company code within your payroll platform.  The value entered into this field is important as the file you send to detamoov must start with this value.

File Name Contains - optional value that is included in the file name

 

 

Alerus 3(16) Plan Specifications

 

For more information on the Alerus 3(16) plan specifications detamoov uses to transform the Standard 401k extract file, please visit the Standard 401k to Alerus 3(16) help page.

 

Field Overrides

 

Division/Location/Excluded Employees

 

If your client's plan has a division/location then a field override can be used to provide this value. To add a field override for the Payroll Frequency field, locate the Action - Transform step and click the Field Overrides panel.  Then click the Add button and select '8: Division/Location/Excluded Employees' from the Output field dropdown menu. 

 

 

Payroll Frequency

 

Alerus requires that the Payroll Frequency be included in the file sent to them.

 

To add a field override for the Payroll Frequency field, locate the Action - Transform step and click the Field Overrides panel.  Then click the Add button and select '26: Payroll Frequency' from the Output field dropdown menu. 

 

The value you need to enter in the Override Value field will be the Alerus payroll frequency code that corresponds to the client's payroll frequency, here:

 

Weekly = 7

Bi-Weekly = 6

Semi-Monthly = 5  

Monthly = 4

 

 

 

Transformation Overrides

 

Employee Type

 

Alerus 3(16) format requires that the Employee Type be provider for each employee.  The following is a list of employee types and their corresponding Alerus values:

 

N/A = 0
Full time = 1
Part time = 2
Seasonal = 3
Leased = 4
Union = 5
Non-Resident Alien = 6
Student = 7
Less than Required = 8
Inactive = 9
Expatriate = A

 

To provide a transformation override to map the employee type in payroll to the Alerus value, locate the Action - Transform step, expand the Transformation Overrides panel, and click ADD.

 

 

Select field 27: Employee Type and click ADD OVERRIDE.

 

 

In the Input Field dropdown select the Reserved field where the Employee Type will be passed to detamoov and select the 'Replace/Remove exact value using a list' Transformation Rule.

 

Note: PrismHR Employee Type values are mapped to Reserved4 by default.  For other payroll platforms, map the Employee Type in payroll to a reserved field in the Standard 401k extract format.

 

 

In the Replacement Groups field, enter in a group for each of the possible Employee Types.  For example, if Full Time is coming out of payroll as 'FT', and Part Time as 'PT', enter a replace group for each.  A replacement group is the value coming out of payroll and the value to be replaced, separate by a pipe-character.  Refer to the client's payroll configuration for the exact values coming out of payroll.

 

 

Click OK once you have added the appropriate replacement groups.

 

Header/Footer Row Overrides

 

Alerus may require the ACH Account ID be provided in the footer row of the file sent to them.  To provide the ACH Account ID, locate the Action - Header/Footer Rows step and click the Row index: 1 to expand the Footer Rows.  Then, locate the row component for 'Multi ACH Account ID' and enter in the ACH Account ID in the text field.

 

 

File Name Overrides

 

Alerus also requires that the Plan Name be included in file name.  If you do not store the Plan ID in payroll then you will need to add a File Name Override for the Plan ID field. 

 

To add a file name override, locate the Action -Name File step and toggle the 'Use default parameters' off. Then on the Plan ID Custom Field, change the Naming Component Type to Text and enter in the client's plan ID in the Text field.

 


Notification step overrides

 

At the beginning of this article you configured the notification step for the moov to send a notification once the moov had completed.  You also have the ability to configure the notification step for each client configuration if you wish to add or remove email addresses per client. 


To override the notification step, locate the Action - Notify 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.

scroll to top icon