Hi Niteen Surwase,

Please find the attached text file for the EE details facing this issue.

12053.txt

Request you to please look for other EEs facing this issue.
Thank you,
-------------------------------------------------------------------------------
CC: Mandar Kulkarni, Satya, Sheetal Bodhale

FYA

Cc: Samir Amruta Lohiya Swapnil Pandhare

Hi darryn.carter,

Please refer our inline comments:-

Regarding point 1.
A. Can you confirm why the New Hire window was opened for the below list of employees.
[Dev]:- EDS Team will provide root cause this issue.

B. I need to have the NH elections removed and entered as OE elections effective 01/01/2018.
[Dev]:- We have moved elections from NH to OE elections effective 01/01/2018 for all impacted employees.
C. Confirm if other employees are affected
[Dev]:- We have scanned whole company and found other impacted employees. Please refer attached excel sheet for more details. Please note that we have also corrected data of these employees.

2. The below employees deductions for the STD grandfathered plan did not appear on the payroll file. The STD grandfathered plan was terminated effective 12/31/2017. However, the deductions should have continued through the last pay period of the year.
[Dev]:- Vinayak Kulkarni,Rajendra Pawar can you please provide update on this.

Thanks,
Avnish Y

CC-- Swapnil Pandhare,Amruta Lohiya,Satya,Samir

Hi darryn.carter

Analysis:
We found below settings on CVHP New/Rehire Rules tab.
#Company Info --> tab New/Rehire Rule --> Select Rule
Ignore New Hire Period During Open Enrollment is No, So NH allowed during OE
Ignore Open Enrollment During New Hire is No, So OE allowed during NH

If both Open Enrollment and New Hire Enrollment Modes are active at the same time :
I. Partner/Broker Login and If we update Demographics, then it'll consider Open Enrollment mode.

II. Employee Login and If we update Demographics through-
1. Benadmin >> Demographics, then it'll consider Online Enrollment mode.
2. Benadmin >> Change New Hire Elections(work-flow) >> Demographics, then it'll consider New Hire Enrollment mode.
3. New Hire Enrollment Work-flow >> Demographics, then it'll also consider New Hire Enrollment mode.

Modes : New Hire and Open Enrollment
EmpID : 1075606 | DOE - 06/30/2017
Comment : XStandard New Hire/Rehire rule (190 Window Period) satisfies from Employment Date 06/30/2017 until 01/06/2018.
So, system have considered New Hire Enrollment mode during OE until 01/06/2018.

EmpID : 1075623 | DOE - 07/20/2017
Comment : XStandard New Hire/Rehire and other rules (190 or 120 Window Period) satisfies from Employment Date 07/20/2017 until 01/06/2018 (varies according to NewHire Rule).
So, system have considered New Hire Enrollment mode during OE until 01/06/2018.

Mode : Open Enrollment
EmpID : 106866
Comment : All employees works fine with Open Enrollment

Modes : NH & OE mode untill 10/07/2017 and currently Open Enrollment
EmpID : 1075449 | DOE - 05/01/2017
Mode : Open Enrollment
Comment : New Hire Enrollment was until 10/07/2017 by considering XStandard New Hire/Rehire rule (190 Window Period) from DOE: '05/01/2017'.
So, system have considered New Hire Enrollment mode during OE until 10/07/2017.

So, above employees getting right modes according to above mentioned scenarios. Same scenarios happens with all other employees.

Thanks,
Niteen S.
----------------------------------------------------------------------------------------------------
Cc: Swapnil Pandhare Satya Sheetal Bodhale

Hi darryn.carter,

Please find below details for point #2.

Concern : The below employees deductions for the STD grandfathered plan did not appear on the payroll file. The STD grandfathered plan was terminated effective 12/31/2017.

Cause: We have checked given employees(010131,104952,105408) and these employees enrolled into Previous Short Term Disability -52 Weeks (coverage amount listed is your weekly benefit) STD plan were enrollment was roll out on 10/19/2017 export file properly. On 10/31/2017 given employees STD enrollments termination date was changed 12/31/2017 to 10/31/2017 through scheduled import.

Please find below snap.

All above STD enrollments are terminated but they are not rolled out on the file because of we mapped CVHP Payroll Indicator and Send Records Without Zero Cost Indicator together on sub template. Combination of these two indicators have some code logic issues, due to this given employees STD enrollments are not roll out on 11/02/2017 export.

Correction: We have corrected code logic to send terminated records in case of CVHP Payroll Indicator and Send Records Without Zero Cost indicators are mapped on template.

Impacted Areas: Row wise export.

Please let us know if you need more details.

CC-Vinayak Kulkarni,Satya

Thanks,
Ganesh

We should convert this to a BUG and take up the code fix post development approval

Assigning it back to Development team

Regards
Gaurav

Hey Ganesh Sadawarte

Where we able to correct the elections for the affected employee? We need to get the elections corrected al least until the bug fix. How long do we expect the fix to take?

Samir
Satya

Hi Aniruddha Dev,

Please check point #2 fix on LB.

Thanks,
Ganesh

Hi darryn.carter, lisa davison

The Employees were eligible for the plan when elections were loaded (in 2015). After that, the eligibility was changed for plan multiple times. System checks if employee is eligible for plan only when data is changed or on his/ her birthday through eligibility service.
We checked the history, sometimes when the data was changed, the eligible rule was set to plan. So election was not terminated.

On 10/31/2017, the rule was set to plan where employee was ineligible and demographics data and effective date was changed through Scheduled Import. In backend routine, import checked if employee is eligible and terminated the election as he/she was not.
There were only 3 such employees which are already mentioned above and no more.

Hi Swapnil Eksambekar,

Please test this on LB and let me know in case of any queries.

CC:Hrishikesh Deshpande

Thanks & Regards,
Aniruddha Dev

Verified this fix for Point #2 on LB with below scenarios

1) Backdated Election Termination
2) Current Date Election termination
3) Future date election termination
4) Dead enrollment for previous Election

All above scenarios worked fine with and without mapping CVHP Payroll Indicator and Send Records Without Zero Cost Indicator together on sub template

Working as expected on LB . Ready for stage

All

Looks like we are having the same issue. Please check into these records and correct. We also need to verify there are no other employees affected. This needs to be corrected ASAP!!!

Mary Jane Isip Evangelista
·         Effective 7/1/17 to current
·         As of 9/1/17, single to EE + SPOUSE coverage
·         Per file, coverage level is reflecting single, start date is changing from 9/1/17 to 7/1/17 and coverage terms as of 9/1/17
 
Nadege Blum-Smith
·         Effective 9/1/17 to current
·         As of 11/1/17, single to FAMILY coverage
·         Per file, coverage level is reflecting single, start date is changing from 11/1/17 to 9/1/17 and coverage terms 11/1/17
 
Mayra Gallardo Santan (I believe full name was too long for the field)
·         Effective 10/1/17 to current
·         As of 12/1/17, medical plan is changing to the EPO plan
·         Per file, start date is changing from 12/1/17 to 9/1/17 and coverage terms 11/1/17
 
Laura Massie Ippolito
·         Effective 7/1/17 to current
·         As of 9/1/17, EE + SPOUSE to single coverage
·         Per file, coverage tier changing from single to EE + SPOUSE, start date changing from 9/1/17 to 7/1/17 and coverage terms 9/1/17
 
Michael Veloz
·         Effective 9/1/17 to current
·         As of 11/1/17, medical plan is changing to the EPO plan
·         Per file, start date is changing from 11/1/17 to 9/1/17 and coverage terms 11/1/17

Ilene Dominguez's spouse, Matthew Gebur, is terming?
 
Per file, coverage tier is changing from EE + SPOUSE to single coverage as of 11/1/17, however, there is not term date for her spouse.
 

Samir
Satya
Amruta Lohiya

Hi lisa davison,
We have checked given employees and also scanned for other employees, We found that data was incorrect where new election got termed as never effective.
We have corrected and verified those record on HSPL which were incorrect and also done the correction on main company.

Due to this we have posted file manually after verification.

Please let us know if you required more details on this.

CC-Ganesh Sadawarte, Vinayak Kulkarni

WI have another looks like her elections was terminated Jinsol Park. SA terminated elections on 11/04/2017. What caused this termination and now I'm unable to reinstate her benefits back to 07/01/2017

Hi lisa davison,

Currently there are two elections:
7/1/17 - 8/31/17 and 9/1/17 - 12/31/17 with EE+SP tier in 'Delta PPO Buy Up Plan'.

We will make this into single election 7/1 to 12/31/17 with EE+SP tier from back end.

Cc: Amruta Lohiya

All,
'It doesn't seem as if we are correcting the problem. Again the carrier/ client is reporting additional effective date issues. We need to do a through analysis of the system to determine the root cause, correct all who is effective and ensure this doesn't continue. Also, I never received a root cause for previous reported issues.

Joshua Ian Soto
• Per file, effective 10/1/17
• Per DOH (6/19/17) and waiting period, effective 8/1/17

Marco Antonio Escobar
• Per file, effective 11/1/17
• Per DOH (7/24/17) and waiting period, effective 9/1/17

Nicholas James Rios
• Per file, effective 12/1/17
• Per DOH (8/21/17) and waiting period, effective 10/1/17

Amruta Lohiya
Samir
Satya

Please take on this on priority

MORE EMPLOYEE AFFECTED

ERNESTO ALONSO 20171001 COBRA beginning 10/1/17
JESSICA MARIE VELASQUEZ 20170901 Waived 2017 coverage
MA CARMEN BALIWAG 20170901 Waived 2017coverage, effective 1/1/18
CINTHIA MARTINEZ VELADOR 20171001 Waived 2017coverage, effective 1/1/18
MARIA NANCY DIAZ 20170901 Waived 2017coverage, effective 1/1/18
CINDY MARIE BUSTOS 20170801 Waived 2017coverage, effective 1/1/18
JOHN JONAS LUNA 20170801 Waived 2017coverage, effective 1/1/18
CHRISTOPHER ADAM DENIS 20171101 Waived 2017coverage, effective 1/1/18
DARLENE LIVINGSTON 20171001 Waived 2017coverage, effective 1/1/18

Hi lisa davison

Can we get consolidated list of employees with SSN in mail?

Amruta,

This is what the client provided. You should be able to look up the socials as I would have to. In addition, we need to check for these mentioned employees and any other employees that may be affected.

lisa davison

We are in progress to correct record and will complete today midnight.

I just need to confirm one thing with you:

Consider following employee,
Employee - NADEGE S. BLUM-SMITH enrolled in "VSP Vision" from 9/1/2017 with EE tier. Then due to issue he got new hire mode and he covered family from 11/1/2017. But client want this effective from 1/1/2018.
9/1/2017 - 12/31/2017 (EE tier)
From 1/1/2018 (EE+Family tier)

Is this correct?

CC: Samir,Bharti Satpute

More reported by the client today.

Amit Thorve I feel like we need to get someone else to assist with getting this issue resolved. I have reported this issue multiple times during OE and each time was told the problem was corrected and the system was checked to ensure no others was affected. I don't think that has been the case.

Here are all the incorrect employee records from this payroll file. Most are OE elections going live which should be effective 1/1/18.

004656 – STD
006639
006905
007421
008762
009194 – Vol life should not be pending
010119
010131 – STD
103318
104952
105408
106822
1074164
1074167
1074891
1075077
1075110
1075238
1075251
1075258
1075314
1075341
1075445
1075446
1075449
1075455
1075456
1075458
1075464
1075472
1075475
1075478
1075481
1075489
1075490
1075492
1075496
1075501
1075521
1075522
1075533
1075539
1075559
1075564
1075572
1075578
1075587
1075588
1075594
1075606
1075607
1075617
1075623
1075626
1075629
1075638
1075652
1075653
1075657
1075659
105853 – Current Vol life increase from $8.49 to $15 for the same coverage amount

Hi Priya Dhamande,

We have done with correction, can you please verify same at your end and let us know in case of issue/concern.

Thanks,
Avnish Y

CC-- Hrishikesh Deshpande,Rakesh Roy,Amruta Lohiya,Samir

Hi Avnish Yadav,

As discussed, need to make correction for waive employee as well.

Hrishikesh Deshpande Rakesh Roy] Amruta Lohiya

Thanks

Hi lisa davison,

We have corrected enrollments of given employees. Please refer attached employee for the same. CVHP_Employee_list.xls

During our correction we have also found waived benefit data inserted in New Hire Mode. We are in-process to correct the data of these waived benefit. We will update you ASAP.

Thanks,
Avnish Y

CC--Amruta Lohiya,Samir

Hello All,

We need to check the system thoroughly and get everything corrected today as we are expected to export their test Open Enrollment payroll file tomorrow 11/21.

Hi lisa davison,

The correction for Waived benefit type under New Hire mode is implemented and verified on CVHP - Production.
Now, after correction the benefit is waived with correct effective date. Please find the list attached with jira.

The incorrect Effective date was due to incorrect customization on New Hire Rule. Screen capture attached with highlight.

This issue of incorrect date will come up again today, if New Hire Rule eligible Employee logs the system for OE.

Please let us know for any inputs required.

Thanks

Hrishikesh Deshpande Amruta Lohiya Avnish Yadav Rakesh Roy Gaurav Sodani

I have made the corrections to the new hire rules. however, we still seem to have some records that requires correction.

Laura Massie Ippolitp - please verify coverage tier. Currently in the system with EE + SP coverage as of 7/1/17 to current. Per file, she is changing to single coverage as of 9/1 – Single coverage begins 1/1/18

Nadege Blum Smith - please verify coverage tier. Currently in the system with FAMILY coverage as of 11/1/17 to current. Per file, member has single coveage – Currently in single coverage, family coverage begins 1/1/18

Michael Veloz - please verify his medical plan. Currently in the system with EPO plan. Per file, medical plan is changing to the PPO plan as of 11/1 – PPO effective 1/1/18

Amruta Lohiya
Samir
Satya

Hi lisa davison

We will look into this tomorrow and keep you updated on this.

Avnish Yadav could you please check above comments and do the correction and let me know any help needed.

Thanks,
Ganesh

We need to get this resolved prior to their OE file going out tomorrow 10/30. This needs to be resolved today!!!

Amit Thorve
Samir
Satya
Amruta Lohiya

I just manually corrected the below records. these are all recent hires from earlier this year but none of which who previously enrolled until OE for an 1/1/18 effective date. Can we checked the system to ensure no one l=else was effective? given NH windows during OE

REYNALDO CASTRO 20171001 Coverage begins 1/1/18
MARGARITA FLORES 20170901 Coverage begins 1/1/18
FERMIN COLDIVAR 20171201 Coverage begins 1/1/18
MAGGIE CARDENAS 20171201 Coverage begins 1/1/18

Prashant Samal and Jaideep Vinchurkar Can you please check this on priority? If required call lisa.

Avnish Yadav Lisa has already corrected the 4 employees mentioned above.

We need to find if there any other employees affected by the same and need to correct their data.

Avnish Yadav Call me today ASAP (11/30 IST)

CC-Amruta Lohiya

Hi Amit Thorve,

As discussed on call about Test Payroll FIle 2014 terminations rolling out on file. As per initial analysis there is issue in code. For time being we will block those terms. We will provide you details on this as soon as possible.

About Today's CVHP Payroll file, we will let you know ASAP.

With kind regards,
Rajendra Pawar
--------------------------------------------------
Vinayak Kulkarni Ganesh Sadawarte

Hi Amit Thorve,

We have deployed this jira on stage Today,

Stage Company name : CVHP Temp Copy for Export

Now template _Payroll Export exporting all valid terms records on file, But we found anther one issue that for below employee's, Termination date is getting exporting on file on field termination date appended twice.

e.g.
1075244 CHANDA DUONG
1075602 CHRISTINA CRUZ

exporting like 12/31/201712/31/2017 instaed of 12/31/2017.

This is an code issue and we are analyzing the same.

With kind regards,
Rajendra Pawar
---------------------------------------------
Samir Vinayak Kulkarni Ganesh Sadawarte Hrishikesh Deshpande Swapnil Eksambekar

Hi Amit Thorve,

Yesterday, we got on below issue on stage while testing Payroll file.

Two records were coming over file like
2 0000000XXXXXXDENT-PRM 9.34 03/01/2017 12/31/201712/31/2017
2 0000000XXXXXXHLTHPOST 0.00 09/01/2017 10/31/201710/31/2017

But it should be like
2 0000000XXXXXXDENT-PRM 9.34 03/01/2017 12/31/2017
2 0000000XXXXXXHLTHPOST 0.00 09/01/2017 10/31/2017

We observed in code that, there are special code written for CVHP indicator for last field, and for this last field there are some calculation related to cost fields. This is causing above issue.

I will discuss with Vinayak Kulkarni, Ganesh Sadawarte and Rohan J Khandave about this.

But for time being this can be handled by customization. just map one dummy field before indicators with field length 0.

Please let us know if any queries on this.

With kind regards,
Rajendra Pawar

All,

On the regular scheduled payroll file exported yesterday 11/30 there were more record found that had a change in their benefit effective date. These were previous NH employees that either elected benefits or did not and was given a new NH effective date when going through the OE tunnel to elect benefits for 01/01/2018. I have provided another list of affected employees that exported on the file to the client yesterday.

001020 – STD
006905 – Dental
006968 – STD
007421 – HCSA
008762- STD
008855 - STD
008758 – Vol Life
010131 - STD
010802 - STD
103318- STD
104426 – STD
104945 – Vol Life
104952 - STD
105029 – STD
105062 – STD
105664 - STD
105846 – STD
106822- HCSA
106866 – Spouse Coverage should be active
107154- Coverage should not begin until 1/1/18
1073115 – Vol Life
1074037 – Vol Life
1074891
1075201
1075230
1075251
1075258
1075314
1075341
1075437
1075440
1075445
1075446
1075449
1075456
1075458
1075478
1075481
1075489
1075490
1075501
1075521
1075522
1075526
1075533
1075543
1075559
1075564
1075571
1075572
1075578
1075594
1075595
1075602
1075606
1075607
1075617
1075626
1075629
1075644
1075652
1075653
1075659
1075674
1075681
1075683
1075710
1075720
1075722

Amit Thorve - I really need help auditing our system using activity dates 1/30 - 11/20 to determine if election effective dates was terminated and re-enrolled by SA. This would be the fourth time the client has brought this to our attention and each time we were told the system was checked and all effected employee records was corrected. The client is very frustrated to say the least at this point.

Nathaniel Cornejo-Walker
Samir
Satya
Amruta Lohiya

lisa davison As per my discussion with Avnish Yadav who was working on data cleanup, he was going to correct the entire data before OE file run.

Amruta Lohiya Can you please look into this on priority?

CC-Samir, Satya

Hi lisa davison,

We have found there were _Payroll Export and Test Payroll FIle two company level template was exported on 11/30/2017 and also saw _Payroll Export template is exported with Send Data File To Carrier with 'Yes' flag but as we checked above records for mention code are not exported on _Payroll Export. Please find snap of exported records on _Payroll Export template for employee 006905 and 006968 as sample.

The Test Payroll FIle template exported above records effective(1/1/2018) because of on template settings page has Current Year Election flag to 'NO'.Due to this it exported 1/1/18 effective records on file. Please find below snap of template setting customization.

Could you please check which template exported file was sent on 11/30/2017?

Please let us know if you require more details details.

CC-Amit Thorve,Samir,Satya,Vinayak Kulkarni

Thanks,
Ganesh

Hi All,
Keeping the ticket on hold, as it has not been approved for stage deployment
Regards
Gaurav

Hello Ganesh,

There was two payroll files exported on 11/30/2017. One for the current year changes and another was a test OE payroll file. The file in question is the current year file.

Thanks

Hi lisa davison,

The current year changes file ie _Payroll Export was not exported 1/1/2018 effective records. Please see my above comments where i have attach snap of employee 006905 and 006968 as example which exported on _Payroll Export. Only current year changes are exported on 11/30/2017 export file.

Please let us know if need other details

Thanks,
Ganesh

Avnish Yadav Please call me today to go over this issue. This is very urgent.
Amruta, please join the call if possible.

CC-Amruta Lohiya, Satya, Gaurav Sodani

Hi Amit Thorve,

In our previous scanned, we have considered only enrollment having Null Termination Date. Now we have scanned all active enrollments and correct the impacted employees . After our correction we observed that no active employee impacted by this issue.

Ganesh Sadawarte: Please update ticket once you fixed export issue on Production.

Thanks,
Avnish Y

CC-- Vinayak Kulkarni,Amruta Lohiya,Satya,Samir

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Verified this on LB,
12/31/201712/31/2017 is not getting export on file,
It is working as expected.

CC-Hrishikesh DeshpandeRakesh ShahaneRakesh RoyAniruddha Dev

Hi Ganesh Sadawarte,

Please look into the concern raised by Lisa

"I reported this issue early this week and haven't received a response.
The below employees are having effective date issues as well. This is related to the ticket were plans effective dates was given there new hire effective date when it should have been effective 01/01/2018. We need theses to be corrected tonight.
007421
008762
008855
010131
010802
103318
104952
105029
105062
104426
104945
105408
105664
105846
106822
1073115
1074720
1075201
1075251
1075437
1075445
1075446
1075449
1075456
1075476
1075481
1075492
1075501
1075521
1075526
1075533
1075572
1075594
1075606
1075644
1075653
1075674
1075710
1075722
"
Regards
Gaurav

Hi lisa davison,

Please find below details

1) As per discussion with enrollment team most of changes are due to salary changes not due to new hire enrollment changes. Please find below sample employee details.
007421
008762
010802
103318
104426
104952

2) We have checked and found that there are enrollment's which has effective date in 2017 but that changed due other reason than salary changes.

1075606
1075644
1075653
1075674
1075710

3) There were some employee who's enrollment does not have any change in 2017. Could you please confirm do you need effective date 01/01/2018 for this?
employee details.
008855
010131

We need call with you to discuss above point.

CC-Samir,Amruta Lohiya,Vinayak Kulkarni

Thanks,
Ganesh

Hi All,

This ticket has been approved for stage deployment on 12/21/17.

Regards
Gaurav

Verified this fix on Stage with below scenarios

1) Backdated Election Termination
2) Current Date Election termination
3) Future date election termination
4) Dead enrollment for previous Election

All above scenarios worked fine with mapping CVHP Payroll Indicator and Send Records Without Zero Cost Indicators.
Working as expected on Stage,Ready for Production.

CC-Aniruddha DevHrishikesh DeshpandeRakesh Roy

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Hi darryn.carter,

Verified this fix on Production with below scenarios
1) Backdated Election Termination -Pass
2) Current Date Election termination -Pass
3) Future date election termination -Pass
4) Dead enrollment for previous Election-Pass

All above scenarios worked fine with mapping CVHP Payroll Indicator and Send Records Without Zero Cost Indicators.
Working as expected on Production,Can you please check this at your end and close this JIRA ?
Please let us know in case of any queries or issues.

CC-Aniruddha DevHrishikesh DeshpandeRakesh RoyGaurav Sodani