MINNESOTA PERA REPORT#


SET UP REQUIREMENTS#

1. Setup new User Fields - IMUF#

One new user field is needed to set up in the BEND table(P2K_ENROLLMENT_DETAILS) to translate and populate the PERA demographic record type (Type 42) for new employees where applicable.

The PERA_EXLCUDE_CODE user field should be set up to populate the exclusion code field (Positions 101-103)

2. Setup new User Defined Lexicons - IMLN#

Three new User Defined Lexicons must be set up to specify the:
  • PERA employment status
  • PERA position class
  • PERA position code

PERA Employment Status#

Lexicon Name: PERA_EMPLOY_STATUS Cross reference the EASD Change Reason with the PERA Employment status. Enter the PERA reportable Change Reason codes only in the SAVED VALUE column and enter the corresponding PERA status in the DISPLAYED VALUE column. A PERA_SWITCH/SW row must exist in order to report those employees who switch PERA plans.

Any Change Codes that are not entered in this table are assumed to be not reportable to PERA.

PERA Position Class#

Lexicon Name: PERA_POSITION_CLASS This lexicon is used to cross reference the Group Code with the PERA Position Class Code. Enter the Group Code under the SAVED VALUE column and enter the corresponding Position Class Code under the DISPLAYED VALUE column.

PERA Position Code#

Lexicon Name: PERA_POSITION_CODE This lexicon is used to cross reference the reportable JOB CODES with the PERA Position Code. Only the Job Codes that have equivalent PERA positions are required to be entered in this table. Any Job Codes not listed in this table will automatically be translated to the OTHER PERA Position Code. Enter the Job Code under the SAVED VALUE column and enter the PERA Position Code under the DISPLAYED VALUE column.

3. Setup new Plan Type - IBPT#

Plan Type Name: MNPERA (No exceptions) Define the MN Public Employee Retirement Administration System benefit plan type.

4. Setup new Plan - IBPN#

Plan Name: MNPERA Define the MN_PERA Plans. Users can define the Plan Code and the Plan Name, but the various PERA assigned Plan IDs must be entered as a COVERAGE within this Plan. The PERA Plan ID must be entered as the first 2 characters in the Policy Number of the COVERAGE table.

5. Setup PERA Benefit Components - IBPN#

Components section for the MN PERA Benefit Plans. Regular Date Components also applied where necessary.

Pay Component NameSourceDescription
B2010Regular Pensionable Earnings (Pay Type 01)Pay Element/Pay PCTotal employee earnings for the reporting period that are deemed pensionable. It must be stored in a Pay PC that the report program can access.
B2012Regular Employer Contribution AmountPay Element or system calculatedRegular ER Contribution. The system will calculate this amount using the ER rate.
B2014Regular Employee Deduction AmountPay Element or system calculated Regular Deduction Amount for the Pay Period based on the regular pay period salary. The system will calculate this amount using the EE rate.
B2016Additional ER Contribution on Regular EarningsPay ElementAdditional ER Contribution Amount
B2020Earning Adjustment (Pay Type 02, A)Pay ElementPensionable Salary Adjustment
B2022ER Deduction AdjustmentPay Element or system generatedER Contribution Amount that is based on the Salary Adjustment
B2024EE Contribution AdjustmentPay Element or system generatedDeduction Amount based on the Earning Adjustment
B2026Additional ER Contribution on Adjustment PaysPay ElementAdditional ER Contribution Amount
B2040Grievance Earning (Pay Type 04)Pay Element/Pay PCTotal grievance earnings for the reporting period that are deemed reportable
B2042 Grievance Employer Contribution AmountPay Element or system calculatedGrievance ER contribution amount. The system will calculate this amount using the ER rate.
B2044Greivance Employee DeductionPay Element or system calculatedEE Deduction Amount for the Pay Period based on the Grievance Pay. The system will calculate this amount using the EE rate.
B2046Additional ER amount on grievance paysPay Element or system generatedAdditional ER amount on Grievance Pay
B2050Retroactive Earning (Pay Type 05)Pay ElementPensionable Retroactive Salary
B2052Retroactive ER ContributionPay Element or system generatedER Contribution amount that is based on the Retroactive Salary
B2054 Retroactive EE DeductionPay Element or system generatedEE Deduction amount based on the Retroactive Earning
B2060Omitted Earnings (Pay Type 06)Pay ElementOmitted Pays
B2062Omitted ER ContributionPay Element or system generatedER Contribution Amount that is based on the Omitted pays
B2064Omitted EE Deduction (Pay TYpe 06)Pay ElementOmitted EE Deduction Amount
B2066Additional ER Amount on Omitted PayPay Element or system generatedAdditional ER amount on Omitted pay
B2070Lump Sum Comp Pay OutPay ElementTotal Lump Sum Payout
B2072ER Contribution on Lump Sum PayoutPay Element or system generatedER Contribution on Lump Sum Payout
B2074 EE Deduction on Lump Sum PayoutPay Element or system generatedEE Deduction on Lump Sum Payout
B2076Additional ER Amount on Lump Sum PayoutPay Element or system generatedAdditional ER amount on Lump Sum Payout
B0290Member HoursPay ComponentUse for Definition only. It must have an Hours PC associated to it for reporting pruposes.

6. Setup PERA Contribution Rates - IBPN#

The RATES section of the MN PERA Plan (only the EE, ER and User 1 rates are used, and are expressed as a percentage. The User 1 Rate is used to define the Additional ER contribution RATE.

PROCESSING#

  • Once the set up of the MN PERA Benefit Plan Types and Plans is complete, the Pay Elements for each Benefit Component must be established. The Plan setup will be used as the definition for processing.
  • All Employee/Employer Amounts calculated through this Plan will be reported on the File and the Report.
  • Normally, only PERA Record Types of 30, 31 AND 38 will be created.
  • When a new employee starts the PERA deduction, or there is a change of employment status, or address change, then Record Type 42 will be created under a separate demographic file.
  • A change of employment status, including new employment, is defined as the record having a Change Reason Code that is defined in the User Lexicon PERA_EMPLOY_STATUS.
  • A switch in PERA plans must occur at the end of a Pay period. Example: The old Plan will be terminated at the end of a pay period and the new Plan will be effective at the beginning of the immediately following pay period. In this case, a New record for the new Plan and a Termination record for the old Plan will be created. A switch of the plans must be identified with PERA_SWITCH as the Change Reason code.

REPORTING PROCESS#

  • The Pay Calendar and Pau Issue Date must be entered.
  • The six-character PERA employer ID must be entered. This number can be defaulted through the IMPM form.
  • The Detail File Name is 200 bytes long and contains the required 30, 31 and 38 Record Types.
  • The Enroll File Name is 400 bytes long and contains the optional 42 Enrollment Record Type.

MAGNETIC MEDIA REPORTING#

Report Header Record - Type 30
Data ElementData TypeLengthPositionValidationDescription
Transaction CodeCharacter21-230
Employer NumberNumber63-8 Unique Employer ID, assigned by PERA
Paid DateCCMMYYDD89-16RequiredPay Issue Date CCYYMMDD
Increase/DecreaseCharacter117-17RequiredUse either an + to indicate an increase or an - to indicate a decrease
Contribution TotalNumber1418-31 Two decimal positions. Net total of all Employer and Member amounts reported.
Number of Plan Summary RecordsNumber632-27 Computed


Plan Summary Record - Type 31

Data ElementData TypeLengthPositionValidationDescription
Transaction CodeCharacter21-231Person Record Type
Employer ID for the PERA systemNumber63-8RequiredEmployer Identification Number, assigned by PERA
PERA Plan IDNumber29-10 01-Basic 02-Coordinated 03-Police and Fire 11-Correctional 12-Police Consolidated 13-Fire Consolidated 14-DCP Ambulance 15-DCP Physician 16-DCP Elected Official 99-Exempt
Increase/DecreaseCharacter111-11 Use either an + to indicate an increase or an - to indicate a decrease
Plan TotalNumber1212-23 Two decimal places. Net total of employee and employer contributions for the plan
Increase/DecreaseCharacter124-24 Use either an + to indicate an increase or an - to indicate a decrease
Member TotalNumber1225-36 Two decimal places. Net total member contribution amount
Increase/DecreaseCharacter137-37 Use either an + to indicate an increase or an - to indicate a decrease
Employer TotalNumber1238-49 Two decimal places. Net total employer contribution amount
Increase/DecreaseCharacter150-50 Use either an + to indicate an increase or an - to indicate a decrease
Additional Total Number1251-62 Two decimal places. Net total employer additional contribution amount
Number of Detail RecordsNumber663-68 Number of detail records associated with the Summary record


Detail Transaction Record - Type 38

Data ElementData TypeLengthPositionValidationDescription
Record TypeCharcter21-238Record Type
Employer NumberNumber63-8RequiredAssigned by PERA
Plan IDCharacter29-10RequiredAssigned by PERA
Employee SSNCharacter911-19Required
Last NameCharacter3020-49
First NameCharacter3050-79
Middle InitialCharacter180-80
TitleCharacter481-84
Coverage Start DateCCYYMMDD885-92 Must not be greater than the Coverage End Date
Coverage End DateCCYYMMDD893-100
Pay TypeCharacter2101-102 01-Regular Pay 02-Adjustment or Lump Sum 04-Grievance Pay 05-Retroactive 06-Omitted Deduction
AdjustmentCharacter1103-103 A for Adjustment O for all other, not adjustment
Increase/DecreaseCharacter1104-104 Use - if Member amount is negative
Member AmountNumber9(8)V99105-114
Increase/DecreaseCharacter1115-115 Use - if Eligible earning is negative
PERA Eligible EarningNumber9(8)V99116-125
Increase/DecreaseCharacter1104-104 Use - if amount is negative
Employer AmountNumber9(8)V99127-136 DCP Only
Fiscal YearCCYY4137-140
ReferenceCharacter20141-160Optional
Hours WorkedNumber4161-164Optional


Demographic Data Record - Type 42

Data ElementData TypeLengthPositionValidationDescription
Record TypeCharacter21-242Record Type
Employer NumberNumber63-8RequiredAssigned by PERA
Plan IDNumber29-10 PERA Plan Code
Employee SSNNumber911-19
Employee Last NameCharacter3020-49RequiredUsed to identify member
Employee First NameCharacter3050-79
Employee Middle InitialCharacter180-80
TitleCharacter481-84
Hire DateCCYYMMDD885-92 Date when employee was first hired. Must be on or before the Eligibility Date.
Eligibility DateCCYYMMDD893-100
Exclusion CodeCharacter3101-103 UDF
Employment StatusCharacter2104-105 User Defined Lexicon
Employment Status Effective DateCCYYMMDD8106-113 For Termination/Death, report last date worked. Otherwise effective date.
Position CodeCharacter4114-117 Job Code User Lexicon
Position ClassCharacter2118-119 Group Code User Lexicon
Job TitleCharacter20120-149Optional
Last Name at BirthCharacter30150-179OptionalIf different then current name
GenderCharacter1180-180
Birth DateCCYYMMDD8181-188
Address AttentionCharacter30189-218
Address Line 1Character40219-258
Address Line 2Character40259-298
CityCharacter20299-318
StateCharacter2319-320
Zip CodeNumber5321-325
Zip + fourCharacter4326-329

Report Parameters & Filters#

Report Parameters
Plan TypeMandatory, LOV available
Plan CodeOptional, LOV available
Department CodeOptional, LOV available
Pay CategoryOptional, LOV available
Include ReversalOptional, LOV available, <YES/NO>
Reversal Pay CategoryOptional, LOV available
Pay CalendarMandatory, LOV available
Limits the process to the pay calendar specified.
Pay Issue DateMandatory, Date, LOV available
This field displays the pay issue date.
PERA Employer IDMandatory,text
Create FileOptional, LOV available, <YES/NO>
The report may be run without creating an interface file (normally for testing purposes).
Directory NameMandatory, 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.
Detail File NameMandatory, text
Enter the name of the file that will be created in the interface directory specified.
Enroll File NameMandatory, text
Enter the name of the file that will be created in the interface directory specified.
Include ExceptionOptional, LOV available, <YES/NO>
Exception LevelMandatory, 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.

Notes #

Click to create a new notes page