The Benefits Auto Enrollment Job analyzes all employee records with each run, even those records where there are no changes as per the eligibility rule.
This approach slows down jobs, affecting the performance with respect to time. Occasionally, it also makes the job fail due to memory consumption issues if the volume to be processed is too high for some customers based on their setup and number of employees.
To improve performance, two new jobs have been introduced to replace the Benefits Auto Enrollmentjob.
1. Create or Update Benefit Enrollments for Benefit Master Data Changes
Run this job:
- To create initial enrollments for a benefit in each period
- To handle automatic enrollment updates caused due to any changes to benefits master data. For example, changes to eligibility rule, rate chart, benefit schedule, and so on.
2. Create or Update Benefit Enrollments for Employee Master Data Changes
Schedule this job:
- To trigger updates to enrollment records due to any change in employee master data , such as Job information, Personal information, Compensation Information, which will have an impact on eligibility of benefit.
- To trigger updates to insurance enrollment contributions due to change in employee age which will have an impact on insurance rates
- To update or create enrollments due to change in eligibility
For more details, refer to the blog.
Migrating from Benefit Auto Enrollment Job to New Tracker-Based Jobs
We recommend that you start using the new jobs instead of the Benefit Auto Enrollment jobs. Refer to the above blogs for more details.
Customers who are already using the ‘Benefit Auto Enrolment’ job
Please follow the below steps if you are using Benefits Auto Enrollment job and plan to shift to the new tracker-based jobs.
1. Set up the configurations mentioned for both the jobs
Please refer to the above-mentioned blogs for more details on the configurations.
2. Set up and run the job ‘Create or Update Benefit Enrollments for Benefit Master Data Changes’ with the Job Run Context / Evaluation Scenario as ‘Determine Next Job Run Date for Enrollments’
This is a one-time job run, it is not necessary to schedule it.
Following are some examples which will explain why this step is required.
Example 1: An organization provides a ‘Company car’ benefit to employees, but employees will be eligible for this benefit only after they complete 5 years of service with the company.
Employee John Smith joins the organization on March 1, 2020. When he