This page (revision-9) was last changed on 26-Nov-2021 10:22 by Lilia Urtan

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 26-Nov-2021 10:22 9 KB Lilia Urtan to previous
8 26-Nov-2021 10:22 8 KB Lilia Urtan to previous | to last
7 26-Nov-2021 10:22 8 KB JMyers to previous | to last
6 26-Nov-2021 10:22 8 KB JEscott to previous | to last
5 26-Nov-2021 10:22 8 KB JEscott to previous | to last
4 26-Nov-2021 10:22 8 KB JMyers to previous | to last
3 26-Nov-2021 10:22 8 KB JMyers to previous | to last
2 26-Nov-2021 10:22 8 KB JMyers to previous | to last
1 26-Nov-2021 10:22 8 KB JMyers to last

Page References

Incoming links Outgoing links
IEEI
IEEI

Version management

Difference between version and

At line 1 changed one line
!!!Employment Records
[{TableOfContents }]
!!!Maintain Employment Records
At line 5 changed one line
An employee must have at least one employment record which is created automatically by either the Establish Personal Profiles (IEHR) or Quick Hire (IEQH) form. When an employee is terminated, the employment record is considered closed. If they are rehired in the same type of relationship, a new employment record is created with a different hire date.
An employee must have at least one employment record which is created automatically by either the Establish Personal Profiles ([IEHR]) or Quick Hire ([IEQH]) form. When an employee is terminated, the employment record is considered closed. If they are rehired in the same type of relationship, a new employment record is created with a different hire date.
At line 18 removed one line
!!Heading 2 title‘Define Employment Record’ Usage and Examples
At line 23 changed 2 lines
;[Employment Type|EMPLOYMENT_TYPE]:Describes the type of relationship which the employee has with the organization.
When an employee is hired, their employment type will be inherited from the group, but you may override the data through the [IEHR] form. This employment type will be displayed on the id line of all of the employee-related forms. This field is derived from the Employment Type entered on the Group [(IDGR)] record. It may be overridden on IEHR at the point of hire, but may not be changed at any other point, after the record is saved. Employment_Type is derived from the IEHR form and cannot be changed directly on this screen.
;[Employment Type|EMPLOYMENT_TYPE]:Describes the type of relationship which the employee has with the organization. When an employee is hired, their employment type will be inherited from the group, but you may override the data through the [IEHR] form. This employment type will be displayed on the id line of all of the employee-related forms. This field is derived from the Employment Type entered on the Group ([IDGR]) record. It may be overridden on IEHR at the point of hire, but may not be changed at any other point, after the record is saved. Employment_Type is derived from the [IEHR] form and cannot be changed directly on this screen.
At line 39 changed 2 lines
;[Original Hire Date|ORIGINAL_HIRE_DATE]:The earliest date an employee ever worked for this or any related organization. An employee may have more than one period of employment with the organization if they are terminated and rehired, or if they are laid off and later recalled. An employee may become an employee through their organization being acquired, merged or taken over, or they may have some previous service with an organization, which becomes affiliated with their current employer. In this case, their original hire date may be earlier than the hire date that is being used for their current employment agreement.
Original_Hire_Date is a mandatory date you must manually enter or use the calendar (F9) for any date changes that may occur.
;[Original Hire Date|ORIGINAL_HIRE_DATE]:The earliest date an employee ever worked for this or any related organization. An employee may have more than one period of employment with the organization if they are terminated and rehired, or if they are laid off and later recalled. An employee may become an employee through their organization being acquired, merged or taken over, or they may have some previous service with an organization, which becomes affiliated with their current employer. In this case, their original hire date may be earlier than the hire date that is being used for their current employment agreement. Original_Hire_Date is a mandatory date you must manually enter or use the calendar (F9) for any date changes that may occur.
At line 44 changed 2 lines
;[First Work Date|FIRST_WORK_DATE]:The date an employee first performs duties and/or attends the work place for the current period of employment. First work date will automatically be set at the time an employee's first pay is closed. The date will be set to the later of the Hire Date or first day of the first pay period. This field may be over-ridden after the pay has been closed.
First_Work_Date is an optional date which may be system derived. You may manually enter or use the calendar (F9) for any date changes that may occur.
;[First Work Date|FIRST_WORK_DATE]:The date an employee first performs duties and/or attends the work place for the current period of employment. First work date will automatically be set at the time an employee's first pay is closed. The date will be set to the later of the Hire Date or first day of the first pay period. This field may be over-ridden after the pay has been closed. First_Work_Date is an optional date which may be system derived. You may manually enter or use the calendar (F9) for any date changes that may occur.
At line 47 changed one line
;[Last Work Date|LAST_DAY_WORKED]:The date an employee last performs duties and/or attends the work place for the current period of employment. Last work date will automatically be set at the time an employee's pay is closed. The date will be set to the earlier of the last pay transaction date or the pay period end date. This field Last_Day_Worked is an optional date which may be system derived. You may manually enter or use the calendar (F9) for any date changes that may occur.
;[Last Work Date|LAST_WORK_DATE]:The date an employee last performs duties and/or attends the work place for the current period of employment. Last work date will automatically be set at the time an employee's pay is closed. The date will be set to the earlier of the last pay transaction date or the pay period end date. This field Last_Day_Worked is an optional date which may be system derived. You may manually enter or use the calendar (F9) for any date changes that may occur.
At line 49 changed one line
;[Income Guarantee|]:This field shows the percentage of disposable income that is guaranteed to an employee.
;[Income Guarantee|INCOME_GUARANTEE]:This field shows the percentage of disposable income that is guaranteed to an employee. Income_Guarantee is a 5-character optional alphanumeric field.
At line 48 added 4 lines
;[ACA Stability Date|]:-A date will be added to ACA Stability Date field on IEEI only when the ACA Category in IBACA is using the Look Back method. \\ - The ACA Stability Date is derived by UBACA and inserted into this field. \\ - It is the start date of the Stability Period which will extend forward for the number of months indicated in IBACA. \\ - During this period UBACA will not recalculate hours worked or a wage rate to determine if the employee is FT or PT or whether the medical coverage is Affordable. \\ - The employees ACA status is fixed as of this date and will extend to the end of the Stability Period when a new measurement period will determine the next stability date and ACA status. \\ - During a new employees UBACA processing, there will be no stability date entered until the last month of the Look Back period has been reached. \\ - Newly hired and terminated employees will have to be reviewed and modified as needed in IBACAE once UBACA is ran for all employees for all months of the reporting year
;[Override User Profile|]:If this field is populated, on login to SelfService it will override the user profile defined on IEID. In order for the override user profile function to work properly, the IEMSS-Employment Selection function has to be enabled (rights can be granted via IMER).  Once the SelfService user authenticates, they are able to switch between employments and the user profile tied to that employment should come into effect.
At line 52 changed 2 lines
;[Rehire Status|REHIRE_STATUS]:This field indicates whether a terminated or laid off employee would be rehired or recalled.
Rehire_Status is an optional fixed lexicon [(X_REHIRE_STATUS)] you may use to look up the value.
;[Rehire Status|REHIRE_STATUS]:This field indicates whether a terminated or laid off employee would be rehired or recalled. Rehire_Status is an optional fixed lexicon [(X_REHIRE_STATUS)] you may use to look up the value.
At line 66 added 5 lines
----
![Notes|Edit:Internal.IEEI]
[{InsertPage page='Internal.IEEI' default='Click to create a new notes page'}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by Lilia UrtanTop