Hi Yashau MacShate,

Please find below details:

We have take off term date of EE Brittany Vesely.

Also, we have analyze the history of EE Brittany Vesely elections.
Initially election are 01/01/2018- Null
But after Scheduled Import term date was set to 01/01/2018 - 1/10/2018
Please find screenshot

We are not able to find EE Matt Snyder Could you please tell us exact name ?

Thanks,
Shailendra Honrao

Cc:Jyoti Mayne, Rohan J Khandave, Jaideep Vinchurkar, Suraj Sokasane

Hello,
What was happening was the HSA was showing a future term date, so I went to the plan and removed the term date, waived and save then re-enrolled the member, then put the term date back to get it to work. see example below in yellow. The example in red has been corrected also but Jenni Fernandes said that both plans should have a term date but the date can not show on future enrollments. The EE's records have been corrected by me but for future enrollments we do not want this to show.

Matt Snyder is Mathew Snyder and his record has been corrected. Please correct the plan.
Yashau

CC: Vinayak Kulkarni
Jennifer Johnson

Per the client, there are 15 more employees who need the term date taken off their HSA plan.

Jared Filo
Brad Zemke
Jordan Osborne
Charles Miswald
Cristobal Paez Santana
Brian Mitten
Lucas Sevcik
Kim Troyk
Rick Ohde
Steven Pentony
Cynthia Kolbach
Zachary Lutz
Joseph Grinwald
Jenny Hostos Garro
Paul Rogers

Hi Yashau MacShate,

We have taken off Termination Date for below employee's:

We have checked in system, termination date is not set to below mentioned employee.
1. Mathew Snyder

2. Joseph Grinwald

We scanned all employee's for this issue. We found only five below employee and correction is done for them.

We are working on finding root cause why termination date is set to HSA Plan. we will update you once analysis gets complete.

Thanks,
Vinanti

CC : Jyoti Mayne, Umesh Kadam, Rohan J Khandave

Hi Yashau MacShate,

We are working on analysis for this issue. We will update you once it gets completed.

Thanks,
Vinanti

CC : Rohan J Khandave, Jyoti Mayne, Umesh Kadam, Prashant Samal

Hi Yashau MacShate,

We are working on analysis for this issue. We will provide update for this on monday (12 Feb) IST.

Thanks,
Vinanti

CC :Jyoti Mayne, Umesh Kadam, Rohan J Khandave

Hi Yashau MacShate,

Concern : Termination Date is getting to set HSA Plan with QE Enrollment mode(Effective date : 01/01/2018 ).
Cause :
Below are customization details:
A. Company infomation page:
Fiscal Year Start Date : 1 JAN
Fiscal Year End Date : 31 DEC
Apply rule on class wise is yes.
OE Start date : 1/1/2018
OE End Date : 12/31/2018

B. Class Wise OE,
Eligible for : New Hire Employee
OE Start date : 1/1/2018
OE End Date : 12/31/2018

C. HSA Plan:
Effective date : 01/01/2018
Termination date : 12/31/2018

We have checked code,
before setting Termination date to election below condition is getting checked,
(Employee is between OE Start date and Fiscal Year end date and Plan termination date is equal to Current Fiscal Year End Date)
then set termination date to election as Plan termination date.
OE Start date are refer from Company Info Page.
This is implemented under WT-3301.

Due to this termination date is getting set to election .

Correction:
Work Around : 1. Remove termination date from plan or set 12/31/2019 as termination date.

Thanks,
Vinanti

CC : Rohan J Khandave, Jyoti Mayne, Umesh Kadam

Hi Dev -

I have a question -

After Open Enrollment, there are some clients that need to have a New Hire enroll in both the 2017 and 2018 elections. We normally create a class-wise OE that is only open for New Hires (based on extra eligibility). This allows for them to enroll in annual benefits for 2017 and 2018.

Based on what you've explained above, I'm worried that we will have this issue with clients that have open enrollments coming up. I agree we need to have the check to term the elections automatically but is there a way to avoid the scenario above OR is there a better way to do the above scenario?

Jenni

I need to add to my comment -

I understand it for some BUT I looked at Jared Filo.

This employee was not a new hire. He enrolled in the plan in 2017 (11/10/2017) - We then loaded on the demographics page on 1/11/2018. When this was loaded, it caused the HSA plan to term. Can you please help explain? Based on the explanation about the OE, I'm not sure why this was termed. Please help update on this one please.

Jenni

Hi Jennifer Johnson,

Please find below updates.

#1 I'm worried that we will have this issue with clients that have open enrollments coming up. I agree we need to have the check to term the elections automatically but is there a way to avoid the scenario above OR is there a better way to do the above scenario?

Comment: Mentioned issue is only for class wise OE.
It will not occur for normal or mid year OE, because enrollment for next year (2019) is done in current year (2018) year itself.

Let us go through with example:

OE Start Date: 11/01/2018
OE End Date : 11/15/2018

Current Fiscal Year Star Day : 01/01/2018
Current Fiscal Year End Day : 12/31/2018

OE Effective Date : 01/01/2019 (Jan 1 Next Year)

Plan Name : HSA_2019
Plan Effective date : 1/1/2019
Plan Termination Date: 12/31/2019

In this case plan termination is not equal to Current Fiscal Year End Date, so termination date will not set at a time of enrollment.

Workaround:
1. Right now, to avoid this we need provide code fix to not consider this termination logic when class wise OE is On.
2. Remove termination date of HSA Plan
3. Set termination date to 12/31/2019

Please confirm shall we need to go ahead with code fix and will require development approval.

Note: With plan wise fiscal year betterment task, setting up termination date implementation for class wise OE will get cover.

#2 Jared Filo HSA plan termination analysis

Comment: He was enrolled in '2018 Health Savings Account' plan on 11/20/2017 with Effective Date '1/1/2018'.
But on 1/11/2018 date time, his demographics data was changed. PFA screen shot.


Due to this data change, he was ineligible for '2018 Health Savings Account' Plan. Hence system termed with '01/31/2018' termination date.

Again 'Cindy Wibbing' added enrollment in '2018 Health Savings Account- Wellness' on 1/11/2018 date time with Effective date '01/01/2018'. Hence his election in '2018 Health Savings Account' plan was terminated as never effective.
Due to above mentioned logic of class wise OE, termination date was set to HSA plan at a time of enrollment.

We have already remove termination date for mentioned EE.

Thanks,
Vinanti

CC :Jyoti Mayne, Umesh Kadam, Rohan J Khandave

Jackie Sivigny Jennifer Leugers Debbie Kulling Jennifer Reed

Here is another one I would like to discuss if possible.

Jenni

Satya Can we discuss this one?

Based on my discussion with Jenni, I believe the termination date should never be put automatically at enrollment time. It should be done by a service. This is what WT-3301 was about. Not sure why the additional condition of comparing Fiscal Year end with Plan termination date was added. This condition needs to be removed.

Hi Jenni,

In scope of this support ticket, correct has been done for mentioned employees. Please let us know if we should go ahead with code changes for scenario mentioned by development.

It will be good to create a separate ticket for that. Thanks

Regards,
Satya Prakash

Cc: Prashant Samal Rohan J Khandave Jyoti Mayne Rakesh Roy Jennifer Reed Abhay Patil

Hi Jennifer Johnson,

During today's scanning, we found following employees had termination date of 12/31/2018 was set to HSA elections. We have removed the termination date for following EEs.

Cc: Rohan J Khandave