Benefits Enrollment nodes are the stage in the workflow at which benefits eligibility is calculated, and if the affected employee’s eligibility has changed since the last calculation, Dayforce enables an enrollment and sends notification, if applicable. If the affected employee’s eligibility hasn't changed, the workflow proceeds to the next node.
When the workflow is triggered by an HR event, eligibility is calculated using the event date associated with the HR event, and Dayforce performs the following steps, as necessary:
- Ends current elections, if the employee no longer qualifies for an existing election.
- Adjusts coverage or cost of an existing election.
- Automatically enrolls employees in auto-enroll options, if the employee is newly eligible.
- Enables enrollments.
- Updates payroll elections mapped to benefits.
- Makes appropriate Affordable Care Act (ACA) period assignments for US organizations using ACA functionality to measure hours by calendar period.
Benefits Enrollment nodes should have one or more outgoing connections, which must be from Notification or Start nodes. They must have only one outgoing connection, leading to an End node.
Note: Benefits Enrollment nodes shouldn’t be connected to a Process node, because the Benefits Enrollment node performs a process function. In some cases, including both nodes can result in an error when the process function is performed twice.
For example, new employees are onboarded using the New Hire form and no approval is required. To configure Dayforce to process new hire records and then enable an enrollment and send notification to the new employee, you can configure two separate workflows and associate them with an HR Event. The first workflow is associated with the New Hire form and processes the new employee record:
When the workflow is completed, it triggers the New Hire/Rehire HR Event, which starts the second workflow that enables an enrollment and, if configured to do so, sends notification to the appropriate recipients:
Message Subject
Click Create Expression and enter the subject line of the message Dayforce sends. Enter any text that you want to include in the subject line of the message. To include variables from the tree on the left, find the appropriate token and double-click it.
See Compose Workflow Messages.
Message Body
Click Create Expression and enter the body of the message Dayforce sends. Enter any text that you want to include in the body of the message. To include variables from the tree on the left, find the appropriate token and double-click it. You can click Cut, Copy, and Paste to update existing text, or edit the font face, size, color, and style using the text editing controls.
See Compose Workflow Messages.
Send To User
In the drop-down list, select the users to which Dayforce sends the message.
Send to Affected Employee
Select the checkbox and Dayforce sends the message to the affected employee. Clear the checkbox and Dayforce doesn’t send the message to the affected employee.
Send Only When Benefit Enrollment Is Published
Select the checkbox, and Dayforce sends a notification to employees only when they have become eligible for benefits (that is, when an enrollment has been published for them). Clear the checkbox, and Dayforce always sends a notification to employees, whether an enrollment has been published for them or not.
Send to Submitter
Select the checkbox and Dayforce sends the message to the user that submitted the request. Clear the checkbox and Dayforce doesn’t send the message to the user.
Send to Authority Type Relative to Affected Employee
In the drop-down list, select the authority types, relative to the affected employee, to which Dayforce sends the message.
Send to Role Relative to Affected Employee
In the drop-down list, select the roles, relative to the affected employee, to which Dayforce sends the message.
Send To Affected Employee’s Manager
Select the checkbox and Dayforce sends the message to the affected employee’s manager. Clear the checkbox and Dayforce doesn’t send the message to the affected employee’s manager.
Relative Level of Affected Employee’s Manager
Enter the numeric level of management to which the notification is sent, in relation to the affected employee. By default, this setting is set to 1 and the notification is sent to the affected employee’s direct manager if the Send to Affected Employee’s Manager checkbox is selected. Enter a different whole number to send the notification to that level of management. Negative numbers aren’t supported.
For example, Amanda reports to her manager, Troy, who in turn reports to his manager, Brent. Brent reports directly to the CEO, Brann. The associated workflow has the Send to Affected Employee’s Manager checkbox selected, and the Relative Level of Affected Employee’s Manager field has 2 entered. As a result, the notification is routed two levels above the affected employee, and Brent receives the notification.
Send To Authority Type Relative to Submitter
In the drop-down list, select the authority types, relative to the submitter, to which Dayforce sends the message.
Send To Role Relative to Submitter
In the drop-down list, select the roles, relative to the submitter, to which Dayforce sends the message.
Send to Submitter’s Manager
Select the checkbox and Dayforce sends the message to the submitter’s manager. Clear the checkbox and Dayforce doesn’t send the message to the submitter’s manager.
Relative Level of Submitter’s Manager
Enter the numeric level of management to which the notification is sent, in relation to the submitter. By default, this setting is set to 1 and the notification is sent to the submitter’s direct manager if the Send to Affected Employee’s Manager checkbox is selected. Enter a different whole number to send the notification to that level of management. Negative numbers aren’t supported.
For example, Amanda reports to her manager, Troy, who in turn reports to his manager, Brent. Brent reports directly to the CEO, Brann. The associated workflow has the Send to Affected Employee’s Manager checkbox selected, and the Relative Level of Affected Employee’s Manager field has 2 entered. As a result, the notification is routed two levels above the affected employee, and Brent receives the notification.