We need to analyze this change. Will provide an update on this by 30th Jan 2017.
Please confirm that this requirement is only for Invoice and not for the Providerwise export functionality.
Prasanna Karlekar (Inactive)
added a comment - Hi Debbie Kulling ,
We need to analyze this change. Will provide an update on this by 30th Jan 2017.
Please confirm that this requirement is only for Invoice and not for the Providerwise export functionality.
cc: Satya
Prasanna Karlekar (Inactive)
added a comment - Hi Debbie Kulling ,
Could not get "This functionality should be for all billing reports".
Does it implies this change should be for:
Standard Billing Report
Invoice
Enrollment Report
As all 3 can display coverage field. Please confirm.
Will need time to analyze. Will provide an update within 2-3 days after getting this confirmed.
Thank you!
The coverage or salary needs to correspond with the rate. If we are basing the coverage on an old salary because of the salary update rule then we should be exporting that salary
on LTD if the rate is based on covered salary that is what the salary that needs to be exported.
Debbie Kulling
added a comment - The coverage or salary needs to correspond with the rate. If we are basing the coverage on an old salary because of the salary update rule then we should be exporting that salary
on LTD if the rate is based on covered salary that is what the salary that needs to be exported.
Maybe we need a "covered salary" field?
This change request is not scheduled in this sprint which is ending on 7th April 2017. I also think that we might need a call to discuss this change. We will let you know accordingly.
Prasanna Karlekar (Inactive)
added a comment - Hi Debbie Kulling ,
This change request is not scheduled in this sprint which is ending on 7th April 2017. I also think that we might need a call to discuss this change. We will let you know accordingly.
Thank you!
cc: Lalit Kumar , Jyoti Agrawal , Venkatesh Pujari
Below are our findings: Child life:
For family rate scenario, we have done the changes in Standard Billing and Enrollment Report, JIRA for same is WT-8642. Billing Summary and Invoice are pending for changes.
LTD:
Covered salary scenario. For this we may need enhancement from Enrollment team to store the salary, based on which premium was calculated. This will need more analysis.
This change request will be taken after 15th June 2017 as currently we are focusing only on bug fixing.
Prasanna Karlekar (Inactive)
added a comment - - edited Hi Debbie Kulling ,
Below are our findings:
Child life:
For family rate scenario, we have done the changes in Standard Billing and Enrollment Report, JIRA for same is WT-8642 . Billing Summary and Invoice are pending for changes.
LTD:
Covered salary scenario. For this we may need enhancement from Enrollment team to store the salary, based on which premium was calculated. This will need more analysis.
This change request will be taken after 15th June 2017 as currently we are focusing only on bug fixing.
Thank you!
cc: Satya , Jyoti Agrawal
Gaurav Sodani (Inactive)
added a comment - Hi Debbie Kulling ,
Please give us time till 7/14/2017 to confirm you on the ETA
Will be splitting this task into two separate JIRA ticket
Regards
Gaurav
CC: Jyoti Mayne Prasanna Karlekar Jyoti Agrawal Satya
We have created two separate JIRA tickets as this ticket consists of two different tasks.
For, correct coverage for child life - WT-10129
For, Invoice to show covered salary - WT-10130
Jyoti Agrawal (Inactive)
added a comment - We have created two separate JIRA tickets as this ticket consists of two different tasks.
For, correct coverage for child life - WT-10129
For, Invoice to show covered salary - WT-10130
Hi Debbie Kulling,
We need to analyze this change. Will provide an update on this by 30th Jan 2017.
Please confirm that this requirement is only for Invoice and not for the Providerwise export functionality.
cc: Satya