HRIS Reporting Requirements – Higher Education –
Chapter 2 – Reporting Personnel and Payroll Data
Data Entry Guidelines
Entering Effective Dates
The EFF-DT
, EFF-START-DT
or EFF-END-DT
field must be the date the transaction became or will become effective.
Example:
On 12/10/2008, Jane’s supervisor approved Jane’s promotion for 01/01/2009. Jane was informed of the promotion 12/15/2008. The payroll clerk key-entered the promotion transaction into the agency’s system on 12/17/2008, and the agency’s programmer produced an HRIS personnel maintenance tape on 01/05/2009. The effective date reported to HRIS for the promotion transaction must be the date the promotion was effective, which was 01/01/2009.
Entering Job/Appointment
Job/Appointment Numbers
The job/appointment number (JOB/APPT-NO) is a unique number assigned to each job/appointment of an employee and enables HRIS to identify the different appointments for an employee. Every employee must have at least one job/appointment number.
The same number can be used only one time per employee during a fiscal year unless the employee is terminated and rehired during the same fiscal year or a job/appointment is reversed.
In either case, the same job/appointment number may be used twice during the same fiscal year because the edits are reset after each of these situations. For employees who hold multiple jobs/appointments, the payroll information must be allocated to each individual job/appointment and may not be combined into one job.
Institutions must report all payroll transactions for casual and task employees. Use job/appointment number 000 and Pay-Trans-Type TP (task payment) for the following entitlement codes:
TSK – Task Payment
SSP – Student Status Payments (College Work Study/Student Status only)
HLY – Hourly (Temporary Hourly only)
OTP – Overtime Pay
Setting up New Jobs/Appointments
Use reason codes 900–932 to set up all job appointments.
You must use reason codes 900–932 on record ID 67 to submit all new jobs/appointments or reappointments that begin the following fiscal year.
Example:
John Doe was hired on 09/01/2008 as the Dean of Business and as a professor for an Accounting I class. During the spring semester, Doe was also hired to teach the Accounting III summer session classes. This scenario would require three separate HRIS transactions, which would be performed as follows:
Action
- Establish Doe’s job/appointment as the Dean of Business using the following reason codes and dates:
- Reason code 010 (record ID 27)
- Effective date of 09/01/2008
- Reason code 900 (record ID 67), effective date of 09/01/2008
- Job/appointment end date of 08/31/2009
- Job/appointment number 001
- Establish Doe’s second job/appointment as an Accounting I professor using the following reason codes and dates:
- Reason code 900 (record ID 67)
- Effective date of 09/01/2008
- Job/appointment end date of 05/31/2009
- Job/appointment number 002
- Establish Doe’s third job/appointment as an Accounting III professor using the following reason codes and dates:
- Reason code 900 (record ID 67)
- Effective date of 06/01/2009
- Job/appointment end date of 08/31/2009
- Job/appointment number 003
In this scenario, all job records end on or before 08/31/2009. But, if Doe is reappointed for FY 2010 to the same job/appointments held in FY 2009, three separate HRIS transactions are again required. John Doe, however, is no longer a new employee. Instead of using reason code 010 (record ID 27), you must use reason code 900–932 (record ID 67) for his job reappointment.
Entering Payroll Sign Fields
The ACT-GROSS-PAID-SIGN
and the PAY-AMT-SIGN
on the Payment Information Record (Record ID 83) and the ENT-ACTUAL-AMT-SIGN
on the Payment Entitlement Information Record (Record ID 85) must be entered as + for positive or – for negative. If left blank, the fields will default to +.
The PAY-AMT-SIGN
on the Payment Information Record (Record ID 83) must be entered as Z when reporting 0 (zero) in the PAY AM
field. If left blank, the field will default to +, and the record will not process.
The DED-ACTUAL-AMT-SIGN
on the Payment Deduction Information Record (Record ID 87) must be entered as + for positive or – for negative. If left blank, the field will default to +. The DED-ACTUAL-AMT-SIGN
applies to the entire record.
Determining Employee Types
Employee types are based on the total number of hours an employee has worked in all jobs/appointments at one higher education agency or institution. Employee types and corresponding codes were defined so that employee benefits audited by HRIS can be monitored. The employee types are defined as follows:
Employee Type | Code | Definition | ||||||
---|---|---|---|---|---|---|---|---|
Regular Full-Time | RF | An employee scheduled to work 40 hours/week for at least 4 1/2 months. | ||||||
Regular Part-Time | RP | An employee scheduled to work less than 40 hours/ week for at least 4 1/2 months. | ||||||
Temporary Full-Time | TF |
|
||||||
Temporary Part-Time | TP |
|
If an employee type code changes as a result of a change in position, the code(s) must be updated on the Employee Descriptive Information Record (Record ID 27).
Processing Reappointment and Salary Action/Position Status Change Transactions
Salary action and position status change transactions (see Appendix A – “Reason Codes and Records”) may be processed using the employee’s current applicable job/appointment number or a new job/appointment number.
If the current job/appointment number is used to process a salary action or position status change transaction, the appropriate reason code and effective date must be submitted.
Example:
Jane Doe is assigned job/appointment 001 effective 09/01/2008 with a job/appointment end date of 08/31/2009. Doe is awarded a promotion effective 04/01/2009. The agency submits a transaction for job/appointment 001 with an effective date of 04/01/2009 and uses reason code 920.
If a new job/appointment number is assigned to an employee for a salary action or position status change transaction, the previous job/appointment number must be updated to reflect the appropriate job/appointment end date and reason code.
Example:
John Doe is assigned job/appointment 001 effective 09/01/2008 with a job/appointment end date of 08/31/2009. Doe is awarded a promotion effective 11/01/2008. The agency determines that a new job/appointment number should be assigned due to the promotion. A job/appointment end date of 10/31/2008 is submitted for job/appointment 001 with reason code 038. A new job/appointment number of 002 is assigned and submitted with an effective date of 11/01/2008. The job/appointment end date is 08/31/2009 and the reason code is 920.
Important: Your HRIS interface program must be set up to automatically send a reason code 038 transaction to modify the job/appointment end date. If the correct action is not taken, the HRIS database will reflect more active jobs than actually exist.
All salary actions with reason codes 923–932, excluding 926, must be reported with the actual amount of the monthly increase or decrease within the SALARY-ADJUSTMENT-AMT
field.
All actions with reason codes 920–922 and 926 may or may not involve a change in the salary rate. Therefore, if a change in the salary rate occurs, report the appropriate value in the SALARY-ADJUSTMENT-AMT
field. If a change does not occur, do not report a value in the SALARY-ADJUSTMENT-AMT
field.
Erasing Field Values
To erase a field value on a record in the HRIS database, follow these steps:
Action
- Enter the key fields of the record that contains the fields you want to erase.
- Enter + at the far-left side of the fields you want to erase.
- Submit the record to HRIS.
Example:
You submitted an Employee Descriptive Information Record (Record ID 27) with a P.O. box number in theMAILING-ADDR-2
field. Later you learn that the employee no longer has a P.O. box number. To erase the old P.O. box number, you must:
Action
- Enter the key fields of the 27 record for the employee.
- Enter + in the left-most side of the MAILING-ADDR-2 field.
- Submit the record to HRIS.
Note: You do not need to re-enter the data for the other fields.
Reversing Transactions (Reason Codes)
Reversing transactions² is possible on the Employee Job/Appt Information Record (Record ID 67) and the Employee Descriptive Information Record (Record ID 27). Reversing a transaction is possible only after HRIS has processed the transaction. The following reason codes can be reversed:
018 | Institutional across-the-board lump-sum payment |
---|---|
043 | Leave without pay |
044 | Faculty development leave |
051–069 | Employee terminations |
900–932 | Salary action codes |
²Reversing a transaction restores the record to its previous state except for the JOB/APPT END DATE
field on reason codes 900–932 This date can be reset using reason code 038.
Two situations may require you to reverse a transaction:
A | A record is submitted with incorrect information, such as an incorrect effective date on LWOP Status Change (Reason Code 043). |
---|---|
B | A record is submitted for a retirement transaction (Reason Code 068) and the employee decides not to retire. |
In either of these situations, a reversal record must be submitted to correct the original record.
When creating a reversal record, be sure to enter the same reason code and the same effective date as on the original record being reversed.
To reverse and correct situation A:
Action
- Enter Y in the
REVERSAL-IND
field of the Employee Job/Appt Information Record (Record ID 67) you wish to reverse. This creates a reversal record. - Access a new 67 record and enter the corrected transaction.
- Submit both records (the reversal record and the new record) to HRIS.
To reverse situation B:
Action
- Enter Y in the
REVERSAL-IND
field of the original Employee Descriptive Information Record (Record ID 27). - Resubmit the record to HRIS. This reversal returns the employee to an active status.
Note: When reversing a termination:
- if termination date is greater than job/appointment end date, upon reversal, job/appointment end date stays the same as set originally when job gets restored.
- if termination date is less than job/appointment end date, upon reversal, job/appointment end date returns to either 5/31 or 8/31 depending on if the contract basis was 9 or 12.