Montana Pers Report
SunGard Bi-Tech Notes
PERS Report/File for the State of Montana
August 28, 2000 Version 1.1
The process for producing the PERS report and file for the state of Montana is available via mask PYRERRMTPR.
Before running the process, the common code PYFG/PY781C must be set up. Following is a sample screen shot of this common code:
Q''2BI-TECH Vanilla Organization Copyright1''W
1((2Software C O M M O N C O D E S M A S T E R (C) 20001((2
) )
) Code Category: PYFG Code Value: PY781MT Ledger: @@ )
) )
) Short Description: EBUG )
) Medium Description: )
) Long Description: )
) )
) )
) Q;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;W )
) : ASSOCIATED VALUES, CODES & DESCRIPTIONS : )
) 199999999999999999939999999999999999399999999999999999999999999999999992 )
) : Numeric Values ) Codes ) Descriptions : )
) 199999999999999999909999999999999999099999999999999999999999999999999992 )
) : ) 12345678 ) <Organization ID : )
) : 1.00000 ) ) <PERS Paybase : )
) : 2.00000 ) ) <PERS hourbase : )
) : 1.00000 ) ) <Use Emp Ded Spec Code # : )
) : ) ) : )
) A;;;;;;;;;;;;;;;;;;4;;;;;;;;;;;;;;;;4;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;S )
) )
A92 f4 for HELP E Find Category: , Value: , Ledger: 19S
The following table describes the required values:
Field | Short Description | Usage |
Short Description | Debug Mode Control | Setting this field to “DEBUG” will turn on debug mode which, among other things, displays the output record contents on the tailsheet |
Associated Code (1) | Organization ID | This becomes the Organization ID included on the record type 1 of the PERS file. The ID consists of eight characters consisting of:
|
Associated Value (2) | PERS Paybase | Must be a value between 1 and 42 |
Associated Value (3) | PERS Hourbase | Must be a value between 1 and 42 |
Associated Value (4) | Special Code Number | A number between 1 and 4 indicating which Special Code of an employees deduction definition for additional PERS deductions to use to determine the Service Purchase Type. |
Before running the process, a number of deductions and contributions must be set up. Miscellaneous Code (1) of these CDH definitions determine the type of PERS processing performed by the process. Following are the possible values of Miscellaneous Code (1) for PERS CDHs:
· PERS Regular deduction and contribution.
· PRSB Buy-back deduction and contribution
· PRSF PERS fee deduction
· PRSP PERS penalty deduction
For sake of discussion, PERS CDHs will be referred to by their Miscellaneous Code (1) value. For example, a PRSB contribution is a CDH with PRSB in Miscellaneous Code (1).
Additional PERS employee contributions are indicated by the use of a Service Purchase Code in one of the Special Codes in the employee’s assigned deductions. The file format supports up to 5 of these additional employee contributions. The values of the Service Purchase Codes are:
Code | Service Purchase Type | Code | Service Purchase Type |
025 | Refund | 045 | Industrial Accident |
026 | Military | 046 | Retro Coordination |
040 | 1-for-5 | 047 | Refund Coordination |
041 | Retro | 048 | Active Account Coordination |
042 | Other Public Service | 049 | TRD on Account Coordination |
043 | Elected Official | 050 | TRD Refund Coordination |
044 | Legislator |
|
|
An example of how to use these codes is to set up five PERS deductions and call them something like PERSADDL1, PERSADDL2, etc. If an employee is to have an additional deduction because they are an elected official, one might assign the PERSADDL1 PERS deduction code to the employee and set the appropriate Special Code to 044. The particular Special Code to use is determined by the common code for the process.
Note that all PERS related CDHs need start and stop dates so the process can determine the start/stop dates for PERS participation which is reported in the resultant file.
When the process runs, the user will input the month/year to be reported. The process will include all periods with a check date within this month for the report.
The resultant file is named PERSyymm where yymm if the year/month being reported.
The following table includes all file and report fields developed from the data and indicates which data is included in each field:
Field | Report/ Rec Type |
Description |
Earnings | Report | All earnings that affect the PERS paybase |
Contrib | Report | PERS deductions + PRSB deductions + PRSF deductions + PRSP deductions – Service Purchase PERS deductions |
Hours | Report | All hours that affect the PERS hourbase |
Add’l Contrib | Report | All PERS deductions with a special code that matches one of the valid Service Purchase Codes |
Term | Report | “Y” if the final PERS deduction assignment ends in the reporting month, otherwise “N” |
Type | Report | “P” if type code is “REG” on the Employee Definition screen, otherwise “T” |
TOTAL EARNINGS REPORTED | 1 | All earnings that affect the PERS paybase |
TOTAL HOURS REPORTED | 1 | All hours that affect the PERS hourbase |
TOTAL MEMBER CONTRIBUTIONS REPORTED | 1 | PERS deductions |
TOTAL MEMBER BUYBACK CONTRIBUTIONS REPORTED | 1 | PRSB deductions |
TOTAL EMPLOYER CONTRIBUTIONS REPORTED | 1 | PERS, PRSB, PRSF and PRSP contributions |
TOTAL MEMBERSHIP FEE REPORTED | 1 | PRSF deductions |
TOTAL PENALTY REPORTED | 1 | PRSP deductions |
HOURS | 2 | Hours the affect the PERS hourbase |
TERMINATION INDICATOR |
| “Y” if the final PERS deduction assignment ends in the reporting month, otherwise “N” |
PART TIME INDICATOR | 2 | “Y” if the value of Miscellaneous Value (4) of the Employee Definition screen is 1.00, otherwise “N” |
SEASONAL INDICATOR | 2 | “P” if type code is “REG” on the Employee Definition screen, otherwise “T” |
EARNINGS FOR PERIOD | 3 | All earnings affecting the PERS paybase |
MEMBER CONTRIBUTION | 3 | PERS deductions + PRSB deductions + PRSF deductions + PRSP deductions – Service Purchase PERS deductions |
SERVICE PURCHASES | 3 | Codes and amounts of all Service Purchase PERS deductions |