LA Optional Retirement Plan (ORP) Report
Overview
The Optional Retirement Plan (ORP) is a defined contribution plan and an alternative retirement plan for eligible employees who may make an irrevocable election to participate in the ORP rather than the Teachers’ Retirement System of Louisiana (TRSL). Three carriers manage ORP accounts. They are ING Life Insurance and Annuity Company, Teachers Insurance and Annuity Association-College Retirement Equity Fund (TIAA-CREF), and the Variable Annuity Life Insurance Company (VALIC). The monthly Optional Retirement Plan (ORP) Input File includes salaries paid, employee contributions, employer contributions, and the carrier code.
The ‘TRSL Optional Retirement Plan Input File’ option of the Regulatory Reporting application allows you to create a Teacher Retirement System of Louisiana Optional Retirement Plan (ORP) Input File.
Report Frequency
Monthly, within 10 calendar days after the end of the month covered by the report.
Selection Criteria
All active employees with an employee deduction or employer contribution amount during the report month will be eligible for the report. Employees must have a payroll status (hr_pe_mstr.stat) of ‘A’. Employees with a termination date (hr_pe_mstr.py_emp_sep_dt) before the start of the report month will not be selected for the report.
BusinessPLUS Setup
Set up a pay base to track Earnings Subject to Retirement. This pay base will be used to report the employee’s salary.
Set up deduction codes for the Optional Retirement Plan with CDH and Pay Base XTD's activated. A CDH number must be set up for tax sheltered ORP and another code for unsheltered ORP.
Assign the appropriate deduction code to each employee that participates in ORP. Note that an employee may only have one active ORP deduction in any given calendar month.
Enter the carrier code in special code 1 on the deduction assignment. Valid codes are 01 for AETNA, 02 for TIAA-CREF, or 03 for VALIC.Set up a CDH number for tracking the regular ORP employer contribution. Assign this code to the appropriate employees.
Set up CDH numbers to track ORP members who have returned to work after retiring. These employees are not reported on this report.
Set up CDH numbers to track ORP members who are participating in Deferred Retirement Option Plan (DROP). These employees are not reported on this report.
Prior to generating the TRSL ORP report, run payroll and all other check maintenance utility tasks in the BusinessPLUS application. If it is necessary to run check maintenance after the report has been run, it may be necessary to handle the changes manually within the TRSL software.
Setup
Before a report can be generated, the reporting interface must be accessed and the necessary data setup completed. This configuration information is used by the Load and Submission processes.
For detailed information about the report screens/tabs, see the ‘Overview of Regulatory Reporting’ document. This document explains the items in common for all reports.
The following options need to be configured under ‘Setup’ menu: Site Profile, Parish Codes, Retirement Codes, and Additional Setup.
Site Profile
Click Site Profile to define the entities and their details. At least one Site Profile record is required. All of the Louisiana regulatory reports utilize this same table so data will rarely need to be changed once it has been entered.
To add details about a ‘Site’, enter data in the fields as described below.
Field | Description |
---|---|
Entity* | ID of the Entity/Employer. The Entity ID should be valid entry as defined in BusinessPLUS. Once saved, the value cannot be changed. |
Employer Name* | Name of the employer for whom the Entity ID is defined. |
Employer Address* | First line of the employer’s address. |
Employer Address(2) | Second line of the employer’s address. |
Employer City* | City in which the employer is located. |
Employer State* | State in which the employer is located. Click for the list of states. |
Employer Zip Code* | Numeric zip code of the employer’s location. This field accepts only five numeric characters and does not accept if all the five characters are zeroes. |
Employer Zip Code Extension | Numeric zip code extension of the employer’s location. This field accepts only numeric characters of 4 digits or less. |
Employer Parish Code* | Numeric parish code assigned to the site. |
Columns marked with * are required fields.
Parish Codes
Click the Parish Codes link to view or update the list of parish codes. The codes are loaded when the software is installed.
Additional Setup
Click Setup to define the entity’s additional details. This information is used by the Load Process.
To add details about an entity, enter data in the fields as described below.
Field | Description |
Entity* | Enter Entity ID defined in ‘Site Profile’ screen. |
Retirement Pay Base * | Enter the 4-digit pay base code which stores ‘Earnings Subject to Retirement’. |
Columns marked with * are required fields. All Pay Base values should fall in the range of 6000 – 6042.
Retirement Codes
Each employee’s participation in the Optional Retirement Plan is identified by a non-zero month to date employee deduction and employer contribution amount for the report month. Click Retirement Codes to define the BusinessPLUS CDH numbers for ORP deductions and contributions. Enter only the CDH codes that are to be included on this report.
To add Retirement Codes for each entity, enter data in the fields as described below.
Field | Description |
---|---|
Entity* | Select an Entity ID. Example: ROOT |
CDH Number* | The CDH number configured in BusinessPLUS for ORP. Example: 2420 |
CDH Long Description* | Description of the CDH |
System Code* | 6 – Optional Retirement Plan |
Columns marked with * are required fields.
System Code will always be 6 for ORP.
CDH Number will be 1000-1999 for employer contributions and 2000-2999 for employee deductions.
Instance
Click Report Instance to configure the report instances for each report to be created. Report instances need to be configured for the extract process.
Enter data in the fields as described below.
Field | Description |
Name* | User defined name of the report instance. |
Year* | Year for which submission will happen. Once the instance is created and saved, the Year value cannot be changed. |
Month* | Month for which submission will happen. Once the instance is created and saved, the Month value cannot be changed. |
Columns marked with * are required fields.
Load
Click on Load to extract and load the ORP employee records from BusinessPLUS into the maintenance table.
See the Submission File Layout for the source of the reported data.
To load data for an instance of a report, enter data in the fields as described below.
Field / Button | Description |
---|---|
Report Instance* | Click for the list of report instances. Select the desired report instance. |
Notes | Enter a note related to report instance or load that is to be performed. |
Entity ID | Click to select a specific Entity ID for which the load will be performed. Select ‘ALL’ to extract records of all entities. |
Employee ID(s) | If specific IDs are to be refreshed or reported on, enter on this line, separated by commas. |
Purge Existing Data | If all the existing data for the selected ‘Report Instance’ that is already in the maintenance table, needs to be deleted so that all new data will load, this check box should be marked. This action would also remove new maintenance records added previously using the maintenance screen. |
Load Button | Click to load maintenance records into maintenance table. |
Note: Columns marked with * are required fields.
After clicking ‘Load’ the following window appears, to indicate that the ‘Load Process’ has begun. Click on the ‘OK’ button to proceed further.
The selected report instance details appear as described below.
Field | Description |
---|---|
Report Definition Details | Details of the selected Report Instance. |
Last Load for the Selected Report Definition | The date (Last Load) and user (Created By) who performed the last load and any note entered for the selected ‘Report Instance’. If the report is loaded for the first time for the selected ‘Report Instance’, this information is blank. |
Maintenance
Click the Maintenance tab to view Load Process results including generated errors. Data manipulation is allowed on the extracted employee data.
The following actions are available:
· Data Changes (to data extracted from the report instance into the maintenance table)
· Adding Records
· Deleting records
Select Report or Specific Records
Field | Description |
---|---|
Report Instance | Click the down arrow to select a specific instance. |
Filter by Criteria | Filter the maintenance records based on Employee ID or Employee Last Name. Clear fields to view all the results. |
Total Record Count | Indicates the total number of maintenance records in the grid. |
Possible Error & Warning Messages
The grid at the bottom of the Maintenance page displays error messages logged during the load extract/submission package execution. The submission errors include invalid/missing mandatory field values. These values can be corrected by selecting the record from the error log grid and clicking on the ‘Filter Selected Record’ checkbox although the long-term data fix would need to occur in BusinessPLUS or the report setup type screens. On clicking this option, only the invalid record is filtered in the maintenance grid, which can then be corrected and saved. On click of ‘View All Records’, all the maintenance records are displayed on the maintenance grid.
Error Log Viewer is the list of possible error/warning messages displayed on the ‘Error Log’ section in the ‘Maintenance’ window and how to resolve the errors. The Error/Warning Messages are described below.
Error / Warning Message | Resolution |
---|---|
Employer Parish Code is not configured for the following entity - ROOT. Employees belonging to this entity will not be extracted | Enter the Employer Parish Code for the entity in the Site Profile Screen. |
xxxxx has actual earnings of zero | Confirm that this employee is a member of ORP and did not have earnings subject to retirement in the report month. |
xxxxx has employee contributions of zero | Confirm that this employee did not contribute to ORP during the report month. |
xxxxx has employer contribution of zero | Confirm that the employer did not contribute to ORP for this employee during the report month. |
xxxxx has blank carrier code | In BusinessPLUS on the ORP employee deduction, enter the carrier code in special code 1. |
xxxxx has an invalid carrier code | The carrier code must be 01, 02 or 03. In BusinessPLUS on the ORP employee deduction, enter the appropriate carrier code. |
xxxxx has no active deduction assignment for code xxxx | In BusinessPLUS Review and update the status and dates on the employee’s ORP deduction assignment. Without an active deduction assignment, the load cannot determine the carrier code. Enter the carrier code on the ORP record within Regulatory Reporting. |
xxxxx has more than 1 cdh mapping to the retire codes | An employee should not have multiple retirement deductions at the same time. Review the deduction and contribution assignments for ORP for this employee in BusinessPLUS. Make any appropriate changes. Verify that the employee contribution and employer contribution amounts are correct on the ORP record. |
The report instances dropdown list is loaded only with report instances for which ‘load’ has happened. Inserting and deleting records are not allowed if there are unsaved changes in the grid. If there are unsaved changes in the grid, sorting and filtering of the grid are disabled. If there are unsaved changes in the grid, a prompt to save the existing changes will be shown, if trying to navigate to another screen.
Submission
After confirming the maintenance data, click Submission to create the file to be submitted to the reporting agency.
To create a report file for submission, data is entered in the fields as described below.
Field / Button | Description |
---|---|
Report Instance* | Click for the list of report instances. Choose the report instance which is to be submitted. |
Notes | Any notes applicable to the submission job. |
Entity* | Click for the list of entities. The specific entity for submission is required. If the maintenance records for all the entities are to be submitted then ‘ALL’ should be selected. |
Filename* | System generated or user defined filename for the submission file. The filename should always end with the ‘.txt’ extension. The filename cannot contain these characters ‘\:/*?”<>|’ Note: The path where the file is saved is already configured in the application and should not be entered here. In some reports the report name is auto-generated and hence the text filename cannot be changes for such reports. Example: 2009_Quarter2.txt |
Report Instance Details | Details for the selected ‘Report Instance’. |
Last Submission for the Selected Report Definition | The date (Last Submission) and user (Created By) who performed the last submission and the note that was entered for submitting the selected ‘Report Instance’. The first time the Submission Process is run for the selected ‘Report Instance’, this information is blank. |
Double Arrow Button | Regenerate the filename. |
Generate Report Button | Create report file with data from maintenance table. |
View Report Button | View the submission file report. |
Columns marked with * are required fields. The user must enter data in these fields to proceed. Only if the ‘Load’ is performed on the report instance, the report instance will appear in the ‘Report Instance’ dropdown list. If the mandatory fields are empty or have an invalid value, an error is logged which can be corrected from the ‘Maintenance’ screen.
Submission File Layout
The following table shows the field numbers, field names, and source within BusinessPLUS.
Position | Field | Type | Size | Source Table | Source Column | Description / Business Logic |
---|---|---|---|---|---|---|
1 | System Code* | N | 1 | la_retire_codes | system_code | Retirement system plan. 6 - Optional Retirement Plan |
2-10 | Social Security Number* | N | 9 | hr_empmstr | ssn | Employee’s Social Security Number |
11-14 | Employer ID* | N | 4 | rr_site_profile | emplr_county | The value is determined based on the Parish Code in the Site Profile for the entity associated with the report instance. |
15-22 | End-of-Month Date* | N | 8 | rr_run_def_mstr | month, year | The last day of the month and year for which this report applies. Comes from the report instance. Example: 03312011 for March of 2011 |
23-24 | Carrier Code* | N | 2 | pyd_cdh_dtl | pyd_spec_cd01 | Carrier employee selected for the retirement plan. Two leftmost characters in special code 1 of the employee deduction assignment for ORP. 01-AETNA 02-TIAA-CREF 03-VALIC |
25-32 | Salary* | N | 8 | pyx_xtd_dtl | pyx_mtd01 … pyx_mtd12 | Employee monthly salary amount is taken from the employee accumulator pyx_xtd_dtl.pyx_mtd## (where ## is the report month) for the Retirement Pay Base, identified on the Setup Screen. |
33-40 | Employer Contribution* | N | 8 | pyx_xtd_dtl | pyx_mtd01 … pyx_mtd12 | Employer contribution is taken from the employee accumulator pyx_xtd_dtl.pyx_mtd## (where ## is the report month) for any CDH Numbers listed on the Retirement Codes screen in the range of 1000-1999. |
41-48 | Employee Contribution* | N | 8 | pyx_xtd_dtl | pyx_mtd01 … pyx_mtd12 | Employee contribution is taken from the employee accumulator pyx_xtd_dtl.pyx_mtd## (where ## is the report month) for any CDH Numbers listed on the Retirement Codes screen in the range of 2000-2999. |
49-74 | Name | A/N | 26 | hr_empmstr | lname fname mname | Captures the first 26 characters of last name, first name and middle name. |
75-80 | Filler | A/N | 6 |
|
| Blank |
Columns marked with * are required fields.
Data Types
A/N - Alpha Numeric, left justified, and blank.
N - Numeric, right justified, zero, unsigned without decimal point, cents, and dollars.
Record Length
80 bytes/characters plus one character for carriage return and one character for line feed.
File Name
Is in the format ORPnnnn_mmyyyy.txt where
nnnn is the Employer Parish Code
mm is the Reporting Month
yyyy is the Reporting Year
Before submitting the file to TRSL, it must be encrypted. The file name for the encrypted file is in the format ORPnnnn_mmyyyy.pgp.
TRSL requires a test file to be submitted prior to submitting an actual report. The file name for the test file must be ORPnnnn_TEST.pgp.
Submission Report
The submission file report can be obtained by clicking ‘Generate Report’ Button or View Report button on the ‘Submission’ page.
About
The About screen displays system level information about the report such as the version, report name and database details.