Hi Debbie Kulling,

We are waiting for internal response on this issue, will update you tomorrow.
Thank You,

-------------------------------------------------------------------------

CC: Mandar Kulkarni, Vijay Siddha, Jaideep Vinchurkar

Hi Jyoti Mayne,

We checked this issue on production and stage.

• For HSA plan there is a field in 'Cost and Coverage' tab to select Employer prorate level.
• In this field after selecting 'No Employer Contribution After Specific Cut Off Date', there is no place to enter the cut off date.

Please refer the screen shot below for stage.

We discussed this issue with Jaideep and Amruta, they suggested that the field for specific date selection should appear after selecting 'No Employer Contribution After Specific Cut Off Date' option.

Request you to please look into this.
Thank you,
--------------------------------------------------------------------------------------------------------------

CC: Mandar Kulkarni, Vijay Siddha, Jaideep Vinchurkar, Amruta Lohiya

I really need an update on this.

Hi,

Can we please have an update?

Hi Debbie Kulling,

Currently No employer contribution after specific cutoff date flag is not implemented in system. It is just exposed on cost and coverage screen for flexible spending plans.

For this, we need to add one field to store cut off date on cost and coverage screen.

Could you please confirm the functionality of this flag for employer coverage so that we can analyzed this request further.

Cc: Satya, Kira Hamilton

If the customization is set to "no employer contribution after specific cut of date" a date field needs to be present.

Example: If they date is set to Aug 1 and enrollments with an effective date after Aug 1st should not receive the employer contribution.

Please let me know if this is something that is going to be able to be done quickly. The group that needs this is going live in about 3 weeks. If it is not going to be able to be done in that timeframe. Please suggest a work around.

Hi Debbie Kulling,

We have below queries regarding this implementation.

1. Do we need to consider this change on export side on file?

2. On Enroll now screen, following needs to implemented:

• Text box will be added on cost and coverage screen for storing cut off date value.
• On enroll now screen, we will compare election effective date with the cut off date and accordingly display employer Contribution.

Fox example: If cut off date is 8/1/2017,

• If today's date is less than cut off date
• If today's date is exact cut off date
• If today's date is greater than cut off date

In all these 3 scenarios, following will be the output.

Cc: Satya, Ganesh Sadawarte

If the cutoff date is 8/1 any elections effective 8/1 or greater would not receive the ER contribution. You second scenario is incorrect.

I don't understand what you are asking "Do we need to consider this change on export side on file?"

Hi Debbie Kulling,

Ok. We will implement on Enroll Now Screen as per your above comment. But we will complete this task in 2nd week of June on Enrollment side.

One query: Do we need to hide Employer Contribution after cut off date on 'View Enrollment Summary' and 'Confirmation Statement Page' also?

Regarding export change Ganesh Sadawarte will give explanation.

Cc: Satya, Vinayak Kulkarni

No I do not hide the ER contribution. It should just show as zero

We need to have a call about this. I think that we need to change the way the proration works. There needs to be a rule for proration (Monthly, Per Pay Period, Quarterly) and then a separate rule for cut off date.

I am available at 8am CST tomorrow (5/26).

Hi Debbie Kulling,

We will call you on Monday(5/29) at your 8 am CST. Is this fine?

Cc: Satya, Ganesh Sadawarte, Vinayak Kulkarni

We are on Holiday on Monday. Can we do 7:30 am CST on Tuesday. Please send invite

Hi Debbie Kulling,

We have sent you invite of meeting 7:30 am CST Tuesday.

Cc:Satya

are we have in a call this morning?

Hi Debbie Kulling,

Yes, we are in call. Please join us.

For HSA, We need to add one more option of Semi-Annually with facility to choose cutoff date for each option.

Currently there are 4 options available for Employer Proration:
1. Monthly
2. Quarterly
3. Pay Period
4. No Employer Contribution after specific cutoff date

User should be able to use either or combination like Monthly + cutoff date or only cutoff date.

If cut off date is say 8/1/2017, for new election only we need to implment following:
1. Elections made on 8/1/17 or greater would receive $0 employer contribution.
2. Election made before cut off date will receive full employer contribution.

Note: This is generic change for HSA employer contribution.

We will share mock up and scenario document with you Debbie Kulling once we take this for analysis.
This is expected to complete by 1st of August.

Cc: Debbie Kulling,Satya,Amruta Lohiya,Vijay Siddha,Vinayak Kulkarni,Ganesh Sadawarte,Rakesh Roy

I need an update on completion. We are now in the second week of June?

Can I please get an update on this

Hello Debbie Kulling,

In current sprint we are working on bugs. We will take this task in next sprint 7/3 to 7/14 for analysis and will share updates.

Cc: Satya, Jaideep Vinchurkar

Is there an ETA on completing this?

Hello Debbie Kulling,

We have taken this task for Sprint 7/3 - 7/14. We will share ETA on 7/3.

Cc: Satya

Hi Debbie Kulling

Please find attached ETA.
WT-9486 Estimates.xls

Thanks And Regards,
Rohit Shete.

CC:Jyoti Mayne

Can you please provide an ETA for completion

Hi Debbie Kulling,

It will be available on Local Environment by 7/13. After QA Approval, we will move it further and share Stage and Production due dates.

Cc: Satya, Vijay Siddha, Gaurav Sodani

Hi Debbie Kulling

We need to confirm expected result of below two scenarios:

#Scenario 1

Suppose Cut off date is 06/01/2017

Employee 1st Election 01/01/2017 - 05/31/2017 with EE coverage
2nd election 06/01/2017 - Null with EE+Family Coverage

Expected: Here for 04/01/2017 election, we will not consider cut off date functionality as it is continue election not new one. Is this correct?

#Scenario 2

Suppose Cut off date is 06/01/2017

Employee 1st Election 01/01/2017 - 01/31/2017 with EE coverage
2nd election 05/15/2017 - Null with EE+Family Coverage

Expected: Here for second election 05/015/2017, we will consider cut off functionality as it is new election. Is this correct?

Could please review above scenario and let us know about output?

Thanks,
Rashmita

Attached some scenarios.
Scenarios writing is still continue.

Hi Debbie Kulling,

We have some queries regarding few scenarios mentioned above. Can we discuss this in today's report team call?

Cc: Satya, Rashmita Dudhe, Prasanna Karlekar

You are correct in both scenarios below you are correct. I did change the date in bold because I think it was a typo

#Scenario 1

Suppose Cut off date is 06/01/2017

Employee 1st Election 01/01/2017 - 05/31/2017 with EE coverage
2nd election 06/01/2017 - Null with EE+Family Coverage

Expected: Here for *06/01/2017 *election, we will not consider cut off date functionality as it is continue election not new one. Is this correct?

#Scenario 2

Suppose Cut off date is 06/01/2017

Employee 1st Election 01/01/2017 - 01/31/2017 with EE coverage
2nd election 05/15/2017 - Null with EE+Family Coverage

Expected: Here for second election 05/015/2017, we will consider cut off functionality as it is new election. Is this correct?

Hi Debbie Kulling,

As discussed in today's call, if on plan only No Employer Contribution After Specific Cut Off Date is customized, in that case for terminated HSA election, we will calculate ER coverage as per EE payroll schedule by considering lapsed pay cycle.

Rashmita will attached detailed scenario document.

Cc: Satya, Rashmita Dudhe

Hi Debbie Kulling,

Please refer attached Scenario sheet HSA cut off for calculation of Semi-annually, Semi annually+Cut-off and Only Cut-off with expected result.

Thanks,
Rashmita

Hello Debbie Kulling,

Could you please go through attached 'HSA Cut Off.xls' once and confirmed, so that we can continue with development for related scenarios.

Cc: Satya, Gaurav Sodani, Amruta Lohiya

Hello Debbie Kulling,

Did you get chance to look at scenarios? Please confirm so that we can start development for same.

Cc: Satya, Gaurav Sodani

Yes and BCC is reviewing them. I followed up with them today and they said they will have a response on Monday

Hello Debbie Kulling,

Do we have any update on this?

They are still working on it. The scenarios have brought to light some different issues. We are trying to figure out what we are going to do. I will get back to you as soon as possible.

Hi There,

Attached are the responses to the scenarios. I think that we should have a call to discuss.

Hi Debbie Kulling,

Thank you for the verification of scenarios. We will go through all scenarios and update you about call.

Cc: Satya, Gaurav Sodani

Can I please get an update on this

Hi Debbie Kulling,,

We are done with analysis. Can we have call today at 7 am CST?

Cc: Satya, Gaurav Sodani, Rashmita Dudhe

Hi Debbie Kulling,

As discussed in 8/16 call, could you please confirm with client what ER contribution should be for attached scenario of Semi-annually also regarding One time Pro ration where to specify prorate period?

Cc: Satya, Gaurav Sodani, Rashmita Dudhe

Can we please have a call to discuss this. Tuesday at 8am CST or Wednesday at 8am CST

Hi Debbie Kulling,

Yes Debbie, can we can discuss today at 8.30 am CST?

Hi Debbie Kulling,

We will be adding following fields on cost and coverage screen. Please find below screen shot.

User is able to customized either Employer Proration or Disbursement.

We also want to discuss some scenarios with client. Can we have call tomorrow? Please share time for same.

Cc: Amruta Lohiya, Jyoti Mayne

Amruta Lohiya will be taking call for disbursement discussion with client.

Hi All,
Attaching development approval email to work on this ticket: Unable to embed resource: Re Sprint 38 Enhancement Starting from 925 and Ending on 1006.msg of type application/octet-stream
Regards
Gaurav

This ticket has been linked to Dev-2126 just to track previous requirements & linked Jira tickets.