This article describes how to configure a client for the Standard 401k to BPAS 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 BPAS moov to your account by following these steps.
Once the Standard 401k to BPAS moov has been added to your account, access the moovs section on the left side menu and click on the Standard 401k to BPAS moov.
The Standard 401k to BPAS 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.
In the moov configuration section, click the Add button to add a new client to send retirement data to BPAS.
Client/Entity - either select an existing client or click the + sign to create a new client.
Status - the status field is important when configuring a new integration with BPAS as it provides the correct file name used to send to BPAS while in their testing phase. This field should be set to 'Testing' until the testing phase has been completed.
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
For more information on the BPAS file specifications detamoov uses to transform the Standard 401k extract file, including the position of each field, please visit the Standard 401k to BPAS help page.
If you are a UKG Ready user and an employee was not paid in the current pay period, a field override is needed to provide the Pay Date. detamoov has provided custom fields that take the existing dates from the source file and allow you to apply them to the missing fields.
To provide the override custom fields, locate the Action - Transform step, click the Field Overrides panel, and click the Add button. Then select the appropriate field from the Output Field dropdown, change the Override Type to Custom Field, and then select the Custom field from the dropdown menu as shown below:
BPAS requires that the Plan ID be included in the file and used in the file name sent to them. If you do not store the Plan ID in payroll then you will need to add a Field Override for the BPAS Plan Number field.
To add a Field Override, locate the Action - Transform step, expand the Field Overrides panel and click the Add button. Then select the appropriate Output field, set the Override Type to Text and enter the Override Value.
BPAS plans require contribution source code and amount mapping that is plan specific and located in the plan specifications provided by BPAS. An example of the plan specification can be seen below:
NOTE: these are example plan specifics. Your plan specifics may differ from what is show here.
In the example plan above we will need to create Transformation Overrides for the Source Code fields as well as the Amount fields that correspond to them.
To create a Transformation Override, locate the Action - Transform step, expand the Transformation Overrides panel and click the Add button.
Step 1
The first Source Code in the example plan above is Source Code "A". This corresponds to the Contribution Source Code 1 in the Transformation Overrides fields list. Select this field and click Add Override.
On the New Transformation Override page, click the 'Add Rule' button and then select the 'Default Value' transformation rule from the dropdown and enter in 'A' in the Default Value field.
Click the OK button to apply the transformation rule to the field.
Step 2
Create a transformation override for the Contribution Source X Amount per Pay Period field that corresponds to the Source Code. This can be found in the plan specifications under the Contribution Source Code field.
Using the example plan specifics above, this would be Employee Pre-Tax and would map to the Contribution Source 1 (Name) Amount per Pay Period field. Select this field from the dropdown and click Add Override.
Because this field is associated with the Employee Pre-Tax contribution, click on the Input Fields dropdown and select "Current Payroll Employee PreTax Contribution" and click "Add Rule".
In the Transformation Rule dropdown, select the 'Round Number - Forced Decimals' rule and then enter the number 2 into the Decimals field and click the Add Rule button.
In the Transformation Rule dropdown, select the 'Input Field Empty' rule. Enter the value 0.00 into the True field and toggle the Input passthrough option to enabled. Then click the Add Rule button.
In the Transformation Rule dropdown, select the 'Padding Left' rule and enter the value 0 into the Fill Character field and then click the OK button.
If the BPAS plan specifications have more Source Code and Contribution Amount values, repeat Steps 1 and 2 above for each one.
BPAS file names are plan specific and are in the following format:
Test files: TEST__FTP__[Plan specific value]__TEXT_[BPAS Plan number].txt
Production files: FTP__[Plan specific value]__TEXT_[BPAS Plan number].txt
This format and the Plan specific value can be found in the plan documentation provided by BPAS. To ensure the file name is correct, you will need to provide a file name override.
To add a file name override, locate the Action -Name File step and toggle the 'Use default parameters' off.
In BOTH the Production and Test naming rule sections replace the Text [Plan Specific] with the plan specific value received from BPAS.
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.
