Company Name:- GBAPS

Configuration:-
Benefit Type :- Medical
Plan Name:- Voluntary Vision
Plan Termination Date Rule:- End of Month
Child Age :- Greater then 26 year

Scenario:-

Enroll Employee in "Voluntary Vision" plan with EE+SP+CH Tier.
Effective Date:- 01/01/2017
Termination Date:- NUll

Raised QE Effective Date:- 07/13/2017 and Terminate or Remove Child from Tier.

After child termination Enrollment in "Voluntary Vision" plan:-
Tier:- EE+SP+CH
Effective Date :- 01/01/2017
Termination Date :- 31/07/2017

Health Tier:- EE+SP
Effective Date :- 01/08/2017
Termination Date :- NUll

Now Run Eligiblity Service, After this please check enrollment rates.

Company Name:- City of Durham

Employee Name:- JO CLAYTON
Plan Name:- B. Retiree Basic Plan

Scenario:-
1. Rasied Qualifying Event "Active to Retired Status" (Effective Date:- 09/01/2017)
2. Enroll Employee in "B. Retiree Basic Plan" with Health Tier :- Employee + Domestic Partner + Domestic Partners Children (EEDPDP2+CH)

Enrollment Effective Date:- 09/01/2017
Enrollment Termination Date:- NUll

Enrollment Rates Effective Date:- 09/01/2017
Enrollment Rates Termination Date:- 06/30/2018

3. After Enrollment Change the Child Status "Domestic Partner Child" to "Natural child"

Enrollment Rates Effective Date:- 09/01/2017
Enrollment Rates Termination Date:- 06/30/2018

Enrollment Rates Effective Date:- 09/01/2017
Enrollment Rates Termination Date:- 06/30/2018

Hi Prasad Pise,

Can you please reproduce above mentioned scenarios on Production for "GBAPS" and "City of Durham" clients.

Thanks,
Avnish Y

CC-- Rakesh Roy,Amruta Lohiya,Satya,Vijay Siddha

Hi Alankar Chavan

Could you please share your updates on this?

CC: Rakesh RoyAmruta LohiyaSatyaVijay Siddha

Hello,

We tried reproducing this issue on Stage City of Durham for HSPL (mentioned in the second comment above) - System behaved in an expected way though

• an employee was enrolled in a Medical plan with Tier EE + Domestic SP + Domestic CH from 03/01/2017 (cost for this tier in associated rate was 20 monthly)
• effective from 09/01/2017, we changed Child's status as Natural Child from Child Form (cost in an associated rate for EE + Domestic SP + Natural CH is 30)

As shown in the screenshot, there were two entries in the rate changes log table, one for 03/01/2017 to 08/31/2017 (20$) & another for 09/01/2017 to 12/31/2017 (30$)

We should try this through Import end once to ensure that the system behaves in an expected manner through import too

CC - Satya Rakesh Roy Prasad Pise Vijay Siddha Amruta Lohiya Avnish Yadav

Hi Prasad Pise,

We have verified this issue import side but this issue is not from Import. Can you please verify this again.

Thanks,
Avnish Y

Hi Rashmita Dudhe,

Could you please provide update on this.

Thanks,
Avnish Y

CC-- Hrishikesh Deshpande,Prasad Pise,Rakesh Roy,Satya,Vijay Siddha

Hi Avnish Yadav,

CC:Hrishikesh Deshpande,Rakesh Roy,Satya,Jyoti Mayne

I have verified this issue but it is not getting reproduced tried below scenarios:

Company Name:- City of Durham for hspl
Employee Name:- JO CLAYTON
Plan Name:- B. Retiree Basic Plan

1]Add new employee and add there dependent
2]Raised QE event Active to Retired Status with Effective date 09/01/2017 enrolled in B. Retiree Basic Plan with Employee + Domestic Partner + Domestic Partners Children

cross verified through backend employee getting the correct rate

Enrollment Effective Date:- 09/01/2017
Enrollment Termination Date:- NUll

Enrollment Rates Effective Date:- 09/01/2017
Enrollment Rates Termination Date:- 06/30/2018

3]Change child status as "Domestic Partner Child" to "Natural child"

4]again check rate Enrollment Rates Effective Date:- 09/01/2017
Enrollment Rates Termination Date:- 06/30/2018

5]Change both of child staus as "Domestic Partner Child" to "Natural child"

6]Change child staus through import as "Domestic Partner Child" to "Natural child"

7]drop one child and check for new Election showing proper rate

8]Verfied through Eligibility Service also

above all scenarios, it showing proper rate.

Thanks,
Rashmita

Hi Rashmita Dudhe,

We have also tried all possible scenario to reproduce this issue but we are unable to reproduce this.

So we are closing this ticket. We will reopen this ticket once client face this issue again.

Thanks,
Avnish Y

CC-- Amruta Lohiya