This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

RPWRS Report #

Once set up is complete the report should be run and the file created and verified. Annual Transaction Report (ET-2533) The Annual Transaction Report should include service, earnings and employee paid contributions for all participating employees of the employer who have not been reported during the calendar year. Included should be those on leave of absence at year-end and any employees not on formal leave but for whom no earnings were paid during the year. Filings are to be completed by January 20 or January 31 depends on type of employer (see section 706 of WRS publication ET-1127). All active (not terminated) employees that have an official enrollment record at year end will be selected. Employee Transaction Report (ET-2533) The employer must notify the WRS when a participating employee terminates employment retirement coverage by reporting him/her on an Employee Transaction Report. This report serves as a mechanism for reporting other types of employee transactions when: An employee changes category due to change in job duties. A previously submitted employee transaction requires correction. Late reported earnings or salary changes must be reported. An employee takes a leave due to medical reasons. The reporting of terminated employees and other types of employee transactions should occur within one week after final reportable earnings have been paid. For state agencies on Central Payroll, employee transactions will be transmitted via the bi-weekly payroll tape. Corrections must be made through Central Payroll rather than sending paper forms to ETF. All employees who have been terminated, or have employment category changes during a user-specified date range will be selected for reporting. ‘RPWRS’ Highlights ‘RPWRS’ may be found through the menu bar: The form may also be accessed through the command window with ‘RPWRS’. ‘RPWRS’ Usage and Examples Report Parameters Entity Mandatory, LOV available Limits the process to the entity specified. Report Type Mandatory, LOV available Annual or EE Transaction Report Report Date Mandatory, Date, and LOV available The ‘Report Date' is the date printed in the file. Action Begin Date Mandatory, Date, LOV available Action End Date Mandatory, Date, LOV available The ‘Action' date range will be used to determine which pay components within the element to report on. People List Code Mandatory, Multiple selection, LOV available, <ALL> A people list may be used to indicate specific employee transaction to be processed. Person Code Mandatory, Multiple selection, LOV available, <ALL> The person code(s) of specific employee(s) to be processed. Department Mandatory, Multiple selection and LOV available Org Level Type Mandatory, LOV available Org Level Mandatory, Multiple selection and LOV available Authorization Mandatory, Multiple selection and LOV available Unit Mandatory, Multiple selection and LOV available Group Mandatory, Multiple selection and LOV available Payroll Mandatory, Multiple selection and LOV available Status Mandatory, Multiple selection and LOV available

Mandatory means that the field must have something in it. <ALL> is fine. Fiscal Hours Element Mandatory, LOV available Fiscal Earnings Element Mandatory, LOV available Calendar Hours Elem Mandatory, LOV available Calendar Earn Elem Mandatory, LOV available BAC Element Mandatory, LOV available EERC Element Mandatory, LOV available EE Add Amt Fix Elem Mandatory, LOV available EE Add Amt Vary Elem Mandatory, LOV available Fixed Tax Defer Elem Mandatory, LOV available Vary Tax Defer Elem Mandatory, LOV available ER added Fix Elem Mandatory, LOV available ER added Vary Element Mandatory, LOV available See WRS Set up - Pay Elements Interface Code Mandatory, LOV available Only those reports of the format “Wisconsin Retirement” will display. Choose from the report formats created. The format “HL$WRS” 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. 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? Output Header/Trailer Mandatory, LOV available If the file is to contain a header and trailer record then indicate <Yes>. Trial Mandatory, LOV available The report may be run in trial mode (Yes) or update mode (No) 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.