Texas Municipal Retirement System - TMRS #
The following statements are taken from the Texas Municipal Retirement System's web site:
"Each TMRS participating city has its own retirement plan within the general frame work of the Texas Municipal Retirement System Act. Provisions may vary from city to city, depending upon the options selected by the individual municipality.
TMRS or ‘Texas Municipal Retirement System’ is a qualified retirement plan under Section 401 of the Internal Revenue Code."
TMRS Setup #
To execute the required monthly report the only set up required is a few pay elements and the Interface Format form (IDIF).The benefit plan may be set up with the standard benefit components documented in Benefits Administration.
Pay Elements - IPPE #
Two pay elements must be defined in order to run the UPTMRS2 update:TMRS GROSS
TMRS CONTRIBUTION
Interface Format - IDIF #
If not already defined in the Interface Formats Definition (IDIF) form, load the standard interface file format using the starter_idif_hl$tmrs2.sql script.Modify the standard TMRS2 file to bank requirements using the IDIF function. Rename the code from HL$TMRS2 to a user-defined code.
| Rec | Field | Start | Position | Ending Position | Name | Variable Number | Notes |
|---|---|---|---|---|---|---|---|
| 1 | 1 | 1 | 3 | Filler | |||
| 1 | 2 | 4 | 8 | City Number | Enter in Constant | ||
| 1 | 3 | 9 | 17 | SSN | Employee SSN | Identity Government ID | |
| 1 | 4 | 18 | 25 | Current Month Earnings | Employee Earnings | Element on UPTMRS2 | |
| 1 | 5 | 26 | 32 | Current Month Deduction | Employee Contribution | Element on UPTMRS2 | |
| 1 | 6 | 33 | 47 | Filler | |||
| 1 | 7 | 48 | 80 | Member Name | Member Name | Identity Name |
Create TMRS Interface File - UPTMRS2 Update#
These are the report parameters for the monthly required report.Report Parameters & Filters#
| Report Parameters | |
|---|---|
| Entity | Mandatory, LOV available This field limits the process to the entity specified. |
| TMRS Gross Element | Mandatory, LOV available |
| TMRS Contribution Element | Mandatory, LOV available |
| Reporting Period | Mandatory, Text YYYYMM The ‘Reporting Period’ date will be used to determine which 'month' the report falls into. |
| Interface Code | Mandatory,LOV available This field lets you identify the interface code associated with the report. |
| Interface Directory | Mandatory, Text This field must indicate a directory on the data base server for which the current user (as signed onto the client’s network) has write capability. For example the entry ‘C:\TEMP’ accesses the ‘TEMP’ directory on the server, not the local directory for the computer terminal being used. |
| File Name | Mandatory, Text Enter the name of the file that will be created in the Interface Directory specified. |
| Write or Append | Mandatory, Write or Append lexicon available If the file already exists, this field lets you indicate if the current information overwritten or appended? |
| Exception Level | Optional, Exception Level lexicon available A ‘trace’ report of exception messages may be produced to assist in the testing phase. This field defines the exception level (report messages) required. |
| Report Filters | |
|---|---|
| People List | Optional, LOV Available This field is used to limit the report to the people lists indicated. |
| Person | Optional, LOV Available This field is used to limit the report to the persons indicated. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation