Hi Debbie -

It looks like with the bridge between WT and Securian is something I cannot see to know exactly what is being sent to them. This will need to go to Dev - I will change the ticket so you don't have to re-write

I did review the record and it looks like the salary was updated but DID NOT change the actual coverage amount. The employee is enrolled in 312k BUT it doesnt seem to follow the rule. With the salary change not effecting the election, the effective date stayed the same (2/6/16). Because I am not sure what is sent to the carrier (I dont see a file feed that I can pull) - If we can get a full report from the carrier, than we can do an audit for you but without knowing what they have in their system I am unable to do an audit.

Amruta Lohiya Can you look into part of this for me?

We had a load of salaries effective 1/1/17 (loaded on 11/17/2017) - during the load the salaries changed but DID NOT change the coverage amounts. At the time, the rule was set to Next Fiscal Year - Should we have loaded with a 2016 date? Example employee is Tijana Milenkovic -

Samir - Are you able to pull a report that shows what was sent to the carrier? I will do an audit once I get a file from the carrier.

Thanks all!!

There are a few individual issues so I will keep looking as well but any help would be GREAT!

Jenni

cc: Vijay Siddha, Satya

Hi Jennifer Johnson,

CC: Satya

We did analysis of this issue.
System was configured correct for Next Fiscal Year for plan Supplemental Life.
Salary loaded with correct effective date 1/1/2017 and within OE period, but during salary load for some of the employee coverage are not changed as per changed salary.
We are working on this issue with help of Import Team.

Jaideep Vinchurkar: Could you please look into above issue? Please let me know if you need more information on salary chages.

Before data correction we need to confirm below

Employee salary loaded on 10/17/2016 instead of 11/17/2016
Next fiscal year setting done for only one plan 'Supplemental life'
So please find attached sheet for affected employee for only Supplemental Life plan.
AffectedEmployee_List.xls
After your confirmation about this data, we will do data correction.

Thanks,
Neelam

Hi Sachin Hingole,

Please get this tested ASAP, By EOD this has to be assign back to AE for their inputs

Environment: Production
Company: UND for Hspl

The issue of coverage not getting changed after importing salaries is checked on production. The issue exits, we have tested for around 15 employees.

Steps:
OE Date set: 01/11/2017 to 1/16/2017
Effective Date: 01/17/2017
Import Done with Template: Salary_Change_Ongoing

The Salary change is updated but coverage remained unchanged. This is verified through View History Confirmation Statement.

So, assigning to Jaideep Vinchurkar for above mentioned issue.

CC: Sachin Hingole

Thanks

Hi Jennifer Johnson,

We have created a bug WT-7839 to track the issue fix. Please address queries of Neelam Yangal so that we can go ahead with corrections and assign this ticket to Neelam Yangal.
For report, please create separate JIRA.

Jennifer Johnson As I do not yet understand Fiscal Year settings, I defer to you for a fix on this. I need to report on this asap and the fix needs to be corrected asap as it's effecting coverage and payroll.

Hi Jennifer Johnson,

CC: Satya

Before this data correction, we need to verify current state of the data.

Employee salary loaded on 10/17/2016 instead of 11/17/2016
Next fiscal year setting done for only one plan 'Supplemental life'
So please find attached sheet for affected employee for only Supplemental Life plan.
AffectedEmployee_List.xls
Please let us know after your confirmation about this data, we will do data correction.

Thanks,
Neelam

This is urgent. Jennifer JohnsonMichael Chand I need to see if we can get this taken care of by Friday at the latest.

Jennifer Johnson Please update us for anything needed from our side.

Jennifer Johnson Jenni, please advise.

Please note that the list that was attached above includes only one of the individuals asked about. I still need responses on all the others brought up int he ticket. This is urgent.

Please advise on this asap

Hi Deborah Mascot,

Due to other higher priority task, couldn't work on this today. We will give you update on this by 1/30 IST.

Cc: Satya

Note that this has been upgraded to beyond urgent. The client is needing resolution asap.

Hi Deborah Mascot,

Please find below 3C's:

Concern: Salary loaded with correct effective date 1/1/2017 and within OE period, but during salary load for some of the employee coverage are not changed as per changed salary

Cause: We have scanned all plans and found that only one plan named Supplemental Life is having fiscal year customization set. As there is issue WT-7839 in import with salary load that's why their coverages were not updated properly.

Correction: Employees who need correction already shared. We need approval from your side to update coverages for attached 93 employees in sheet to proceed with the correction.

Cc: Satya

We do need this corrected, but the proper Guarantee issue rules need to be followed. Since these could impact what should have happened in the system with GI rules, we need to make certain that we are careful to follow this correctly. I've requested a listing of what went to the carrier through the SSO to them for underwriting, but if you can produce a listing that will be helpful so that this can be properly analyzed before correction is done.

Hi Deborah Mascot,

Please find below details:

For employee 'Tijana Milenkovic' currently she is having election in Supp life plan with 2/6/2016 effective date with $312000 amount which is as per her old salary of 103757.86(3x of salary)

Current Coverage details:

Her salary was changed in OE with 1/1/17 effective date to $114133.65 so her coverage has to be changed but it was not due to issue explained above. She should have new coverage of $342400 with 1/1/17 effective date.

After correction record will be:

Santosh Balid Could you please give reply about SSO query?

Cc: Satya

Hi Deborah Mascot,

Though we are doing corrections manually in backed, but this will not work for SSO.
SSO comes into picture only when enrollment process for EOI happens through application not when we do manual data corrections through backed.

So if employee wants to enroll for new coverage amount as per updated salary, then either employee should re-enroll(I don't know how feasible it is) or We should convey this issue to securian and provide new coverage details , so that they can approve as per new coverage amount.

Please let us know in case of any query related to SSO.

Regards,
Santosh

Cc: Satya, Samir, shyam sharma, Vijay Siddha, Rohan J Khandave

Hi Deborah Mascot,

Please find below details and provide us approval for data correction.

1. Currently employee 'Tijana Milenkovic' is having following data for Supp life plan:

This employee got 2/6/2016 election due to import mode with 0 salary index and due to this when his salary changed on 10/17/2016 his coverage didn't got updated.

After correction, employee's election data will be:

Note: As we are doing this correction from back end it will not get reflected on SSO. Please find above comments added by Santosh Balid.

We will scanned all employees and correct employees salary index and coverage.

2.Lawrence Dwyer (NDID: 900313791) had 10x his salary in 2016, but he was sent to Securian stating that he needed to complete an EOI in order to receive 10x his salary again in 2017. This was not a change, so it does not require an EOI.
Comment: Currently this employee is having $356000 coverage with No EOI with 1/1/17 effective date. So no need of correction

3.Keith Hostetler (NDID: 901917614) appears to have elected 4x his salary during open enrollment. He did not previously have coverage, so this would require an EOI with Securian. Based on the open enrollment upload Keith was given 3x his salary as of 1/1/17. He should not have received any coverage since he has not been approved through Securian. There are others in a similar situation as well. Is WorkTerra set up to automatically approve 3x coverage for anyone that is electing coverage for the first time during open enrollment?
Comment: This employees election is terminated as never effective by company admin 'Amber Petras'

Cc: Satya. Jaideep Vinchurkar

Hi Suraj Sokasane,

Can you please check why 'Tijana Milenkovic' got 0 salaryindex due to 8/21/2016 import and there are around 61 employees of this type.

Cc: Vijay Siddha, Satya, Jaideep Vinchurkar

Hi Rashmita Dudhe,

Can you help in reproducing the issue? I'll provide you the Imported file.

Analysis in progress.

The Enrollment for this plan was supposed to e done from Securian Service. Import currently does not support such enrollments.
We are looking into it for possible solution.

CC- Deborah Mascot, Jaideep Vinchurkar, Jyoti Mayne, Rashmita Dudhe

Note that the enrollment was not to be done by Securian. The EOI processing was all that was sent through the SSO connection with Securian. Only those elections requiring EOI were to be sent through that connection.

Hello Deborah Mascot,

Shall we proceed with data correction for the employee ''Tijana Milenkovic'' as explained in above comments in tabular format.

We will also do scanning and check whether employees coverage are as per current salary and do correction if required.

Yes, you should make the change for Tijana Milenkovic.

Hello Deborah Mascot,

We have scanned all employees and found attached UND_Supp_Life_List.xls employees whose coverage were not as per 2017 salary for Supp Life plans. We have corrected their coverages.

Please confirm and let us know if you face any issue.

Cc: Satya, Jaideep Vinchurkar, Vishal Bajad, Vijay Siddha

Deborah Mascot Please update for next action if required.