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.‘Create TMRS Interface File’ Highlights ‘Create TMRS Interface File’ may be found through the menu bar: The form may also be accessed through the command window with ‘UPTMRS2’. ‘Create TMRS Interface File’ Usage and Examples Report Parameters Entity Mandatory, LOV available Limits the process to the entity specified. Payroll Mandatory, LOV available Only one payroll may be selected per execution of this function. Pay Run Number Optional, LOV available 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 Only those reports of the format “TMRS Contributions” will display. Choose from the report formats created. The format “HL$TMRS2” has been provided as a sample, but should be copied, and the copy edited, by the client before running this report. The report definition selected will determine the format of the output file (if any), as well as the columnar content of the report. Interface Directory Mandatory, text Must be a directory on the 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, LOV available If the file already exists should the current information overwrite it or append to it? Exception Level Mandatory, LOV available A ‘trace’ report of exception messages may be produced to assist in the testing phase. If necessary, choose from 0 – 9 (highest) level of trace. Please note that this is a voluminous report and will cause very slow performance.
