HR events allow you to associate submitted forms with one or more workflows that are triggered when a submitted form is processed. There are several template, or system, HR Events that are included in Dayforce by default. Most template HR events are also generated by the Benefits HR Event Generator background job. This section provides information on the function and typical configuration of these HR Events.
Address Changed
Created when changes are made to the employee’s primary residence information. If benefits eligibility is based on primary address, configure this event with the Address form as the triggering form, and a triggered workflow that includes the Benefits Enrollment object.
Age Changed
Created when the system date matches the affected employee’s birth date. If an employee’s age is used to qualify for benefits plans, options, or rates, this event should be configured.
Assignment Changed
Before You Begin: This event can also be created when there is a change to an employee’s primary job assignment or location as a result of an HR Import. See Events Triggered by HR Import.
Created when any of the following occur:
- A new work assignment is created or when changes are made to the employee’s work assignment by changing the primary or secondary assignment the Work > Work Assignments screen in People.
- Any field in Work > Work Assignments is edited.
When benefits eligibility is based on settings such as pay class, pay type, location, job assignment, compensation, or other employee work assignment information, configure this event with either or both of the Job Assignment Change form and the Job Assignment and Compensation Change form as the triggering form, and a triggered workflow that includes the Benefits Enrollment object.
Benefit Compensation
Created when changes are saved for an employee in the Benefits > Benefit Properties screen of the People feature. This event doesn’t require a triggering form. When the Benefit Compensation property is added or edited and the record is saved, the triggered workflow is initiated.
This event is generated upon save of the Benefit Compensation property, and not by the background job.
Dependent Added
Created when a new dependent is added. When a Dependent Qualifier or Participant Definitions are configured, configure this event with the Current Dependent Information form as the triggering form, and a triggered workflow that includes the Benefits Enrollment object.
Dependent Address Changed
Created when the primary residence of the employee’s dependent is changed in the Personal > Dependents and Beneficiaries screen of People or in the Current Dependent Information form. If benefits eligibility is based on primary address, configure this event with a triggered workflow that includes the Benefits Enrollment object.
Created when the system date (month and day) matches the dependent’s birth date (month and day). To determine a dependent’s age, Dayforce reviews all participant definitions, dependent qualifiers and the relationship types configured, and age reduction configurations before generating an event for every date on which the dependent age changed, based on those settings.
For example, you have a participant definition that checks dependent age as of the last day of the month and a dependent qualifier that checks age as of the first day of the month. If a dependent has a birthday, Dayforce will generate an HR event for that dependent on the last day of the birthday month and on the first day of the following month.
Note: The background job doesn’t create an event when a dependent reaches the minimum participant age of 0 years old.
If a dependent’s age is used to qualify for benefits plans, options, or rates, configure this event with a triggered workflow that includes the Benefits Enrollment object. When the HR event is generated, it triggers the necessary recalculations.
Dependent Disability Status Changed
Created when the disability status of the employee’s dependent is changed in the Confidential Information tab of the Personal > Dependents and Beneficiaries screen in People or on the Current Dependent Information form. If benefits eligibility is based on disability status, configure this event with a triggered workflow that includes the Benefits Enrollment object.
Dependent Ended
Created when a dependent is deleted, or a date of death is recorded. When a Dependent Qualifier or Participant Definitions are configured, configure this event with the Current Dependent Information form as the triggering form, and a triggered workflow that includes the Benefit Enrollment object.
Dependent Student Status Changed
Created when changes are made to the dependent's student status. If benefit eligibility is based on student status, configure this event with the Current Dependent Information form as the triggering form, and a triggered workflow that includes the Benefit Enrollment object.
Dependent Tobacco Usage Changed
Created when changes are made to the dependent’s tobacco use status. If benefit eligibility is based on the dependent’s tobacco usage status, configure this event with the Current Dependent Information form as the triggering form, and a triggered workflow that includes the Benefit Enrollment object.
Employee Property Changed
Created when a specified Employee Property is updated. For example, employees are qualified to enroll in a Reimbursement plan to subsidize parking expenses, after they've submitted proof of an annual parking plan.
This event is generated upon save of the Employee Property, and not by the background job.
Employee Tobacco Usage Changed
Created when changes are made to the employee’s tobacco use. If benefit eligibility is based on the employee’s tobacco usage status, configure this event with the Health & Wellness form as the triggering form, and a triggered workflow that includes the Benefit Enrollment object.
Employment Status Changed
Created when a new status record is created or when changes are made to the employee’s status in the Employment Status tab of the Employment > Employment Settings screen in People or through a status change on a workflow form. When benefit eligibility is based on status, configure this event with the Terminate an Employee, Request a Leave or Return to Work forms (or custom form if applicable) as the triggering form, and a triggered workflow that includes the Benefit Enrollment object. The event isn’t triggered if there is a New Hire event for an employee on the same day.
Job Application Status Changed
This is a system event used by Recruiting only, and isn’t applicable to Benefits.
Marital Status Change
Created when changes are made to the employee’s name and marital status information in the Personal > Confidential Information and Personal > Contact Information screens in People. When benefit eligibility is based on marital status, configure this event with the Name and Marital Status form as the triggering form, and a triggered workflow that includes the Benefit Enrollment object.
New Hire/Rehire
Before You Begin: This event can also be created when there is a rehire or new hire as a result of an HR Import. See Events Triggered by HR Import.
This HR event can only be generated by a triggering form, such as the New Hire form. This event is commonly used to open the New Hire Enrollment.
This event is generated when the triggering form is processed or by way of the Recruiting Import, and not by the background job.
Note: The Recruiting Import is included in the HR Import.
Number of Days Since Hire
This HR event is typically generated by the Benefits HR Events Generator Background job to open the New Hire Enrollment if eligibility is determined X days/months after the New Hire Date. If benefit eligibility is based on the number of days since hire, configure this event with a triggered workflow that includes the Benefit Enrollment object.
Payroll Qualification Reached
This HR event can be generated only by the Benefits HR Events Generator Background job. It’s created when the payroll earnings used as a payroll qualifier match the payroll qualifier properties (for example, the number of hours worked). If benefit eligibility is based on payroll qualifications, configure this event with a triggered workflow that includes the Benefit Enrollment object.
PPACA Override Date Changed
Generated when the employee’s PPACA override date is updated. The event reassigns PPACA calendar periods to the affected employee, when an update is made to the PPACA Override Date field in the Key Information tab of the Employment > Employment Settings screen in People.
Spouse Coverage Verification Change
This is a system event that is generated when changes are made in the Current Dependent Information form or in the Benefits > Spouse Coverage Verification screen in People, that results in a “Yes” designation. A “Yes” designation indicates that the spouse has been offered medical coverage elsewhere.
If benefit eligibility is based on whether a spouse has been offered medical coverage elsewhere, configure the event with the Current Dependent Information form in the Triggering Forms section, and a workflow that includes the Benefits Enrollment node.
Dayforce determines a spouse’s eligibility for an option based on their coverage verification status on the election effective date. For example, Medical Option A doesn’t allow for spouses to be covered if they are offered coverage elsewhere. If employee John’s election effective date for Medical Option A is January 1, 2018, Dayforce checks the coverage verification records for John’s spouse, Jane, as of January 1, 2018. If Jane doesn’t have a coverage verification status record or as long as she has one that says “No”, then she is eligible for the option. Even if Jane has a coverage verification status record of “Yes” on January 2, 2018, she will still be eligible for Medical Option A.
This event is generated when the when the designation is saved in People or the triggering form is processed, and not by the background job.
Years of Service Changed (Hire Date)
The Benefits HR Event Generator background job generates this HR event to determine the benefit eligibility when an employee’s years of service changes based on the most recent hire date. You can find the employee’s most recent hire date in the Employment > Employment Settings screen in People. This HR event is generated when the background job date (month and day) matches the employee's most recent hire date (month and day). Dayforce sets the HR event date to the background job start date or the current date. Configure this HR event with a triggered workflow that includes Benefit Eligibility.
Years of Service Changed (Original Hire Date)
The Benefits HR Event Generator background job generates this HR event to determine the benefit eligibility when an employee’s years of service changes based on the original hire date. You can find the employee’s original hire date in the Employment > Employment Settings screen in People. This HR event is generated when the background job date (month and day) matches the employee's original hire date (month and day). Dayforce sets the HR event date to the background job start date or the current date. Configure this event with a triggered workflow that includes Benefit Eligibility.
Years of Service Changed (Seniority Date)
The Benefits HR Event Generator background job generates this HR event to determine the benefit eligibility when an employee’s years of service changes based on the seniority date. You can find the employee’s seniority date in the Employment > Employment Settings screen in People. This HR event is generated when the background job date (month and day) matches the employee's seniority date (month and day). Dayforce sets the HR event date to the background job start date or the current date. Configure this event with a triggered workflow that includes Benefit Eligibility.