Do you think this issue will be resolved today? BCC needs to send the August invoice out.

Following are the updates:
Issue 1:
Code fix will be required.
We are working on this. With verification this will be fixed by tomorrow.

Issue 2:
This is done.
Correction was required. Issue was due to incorrect data in billing table. Have scanned this company for COBRA Admin plan. Found mentioned 2 employees only.

Issue 3:
Could not understand following mentioned by client:
"The system for ADD is crediting $110,000 and re-billing at a volume of $260,000 February through current month of August"
We confirmed August 2017 invoice for employee Barton Wright. He is getting credits for coverage $110,000 and is being re billed for coverage $169,000. This new coverage is as per his life plan.
Please let us know, if this is an issue for Invoice or do we need to find the root cause for incorrect age reduction happening for plan AD&D?

Thank you!

cc: Satya, Jyoti Agrawal

Issue 3 is being caused by the incorrect age reduction. We need to find the root cause of the incorrect age reduction.

Is it possible to take a copy and then fix the age reduction from the back end this morning. Then look for the root cause. BCC needs to get this bill out today

Hi Debbie Kulling,

Will check with Jyoti M. for data correction related to Age Reduction.

Status update for Issue #1:
After fixing the issue while verifying data got few more records that should not appear on August 2017 Invoice. This is also because of data inconsistency.
We are working on same and will provide an update in an hour.

cc: Jyoti Mayne, Satya

Could not check the issue for Age Reduction with Jyoti M. as she has left the office.

Thank you!

cc: Satya, Jyoti Mayne

Hi Debbie Kulling,

We have done the code fix for Issue #1.
Following are the 3C's:
Concern:
LTD coverage is being unbilled and rebilled at a pro-rated monthly portion.

Cause:
There were no cost changes but table where system stores cost related data did not had a continuous record. The record was terminated with date 1/24/2017 and new entry with same cost was inserted with effective date 1/25/2017. In invoice code, we do not expect such scenario when record is parted without cost change.

Correction:
Code changes made to handle this scenario.
Currently, fix is only done on Production - TIBCO. Could not verify the data completely but have done verification to our best. Fix will be deployed on all companies as per patch process.

Regarding Issue #3:
I think that the changed coverage that is currently appearing on Invoice is correct as it is same as his Life plan. Also, adjustment related to this coverage change appearing in August 2017 invoice are valid.

Could you please confirm and let us know.

Thank you!

cc: Satya, Jyoti Agrawal, Venkatesh Pujari

Hi Debbie Kulling,

Today we started auditing TIBCO Invoice for August 2017. We are getting adjustment related issues as there are thousands of adjustments that are appearing on this invoice. There seems to be no issues with retro add records but we found some valid retro terms missing from the invoice.
We are investigating the same but we need some more time.
Please let us know, if we can complete this by your tomorrow morning.

Thank you!

cc: Satya, Jyoti Agrawal, Venkatesh Pujari

Hi Debbie Kulling,

Please find below details for point#3.

Concern: Barton Wright his ADD is not age reducing correctly. His age reduction should be the same as life with a volume of $169,000.00. The system for ADD is crediting $110,000 and re-billing at a volume of $260,000 February through current month of August. It looks like the system has not been doing the ADD age reductions correctly from the beginning. The system was reducing the amount to $110,000 versus $169,000

Cause: Life Plan and AD&D Plan both are having different customization:

Plan Name	Reduction Rule	Screen shot for Reduction	Update Election on Salary Change Rule
Life Plan	Apply Reduction On New Salary: Yes, Display Reduced Amount On Enroll Now For Overage?: Yes		Jan 1 Next Year
AD&D Plan	Apply Reduction On New Salary: No, Display Reduced Amount On Enroll Now For Overage?: No		Effective on date of change

• Mentioned EE age is 66. EE enrolled in 'Life Plan' with 2x of salary with 1/1/17 effective date. His salary was 130000. So coverage $260000 but as per customization he got $169000 coverage. After that, due to salary changes, he got new coverage with reduced amount with 1/1/18 date.

• Initially he enrolled in 'AD&D Plan' plan with 1/1/17 date with 2x of salary i.e. 260000 on 2016-11-03 10:18:31.947 datetime. As he is overage, next day reduction service reduced coverage to 65%, he got $169000 coverage. All these changes were done in enrollment future table. In future enrollment table, there is one issue WT-10248 that reduction details are not getting properly stored. Hence, it was reduced twice i.e 1690000*65% = 110000. On 1/1/17, that enrollment moved from intermediate to main table. After that, all enrollments changes were done in main table and there is no issue.

After salary changes, he got new coverage as per date of change rule with 1/16/2017 with $169000 coverage.

Please let us know if any action item is required from our side for this EE record?

Cc: Satya, Prasanna Karlekar, Gaurav Sodani

Hi Debbie Kulling,

We saw that BCC has finalized their August 2017 Invoice. Today we did not get much time to complete end to end audit for August Invoice. We want to audit the August 2017 invoice once at our end.
Please let us know, if we can get time till 26-July-2017 and BCC can wait till then. We know that, this is a delay. But if there is adjustment issue in any of the invoices, upcoming invoices may also not have proper adjustments.

Apologies for same. But do let us know.

Thank you!

cc:Satya, Jyoti Agrawal, Venkatesh Pujari

BCC had to post the invoice. Are you still able to correct the adjustments so they are correct on Sept invoice?

Hi Debbie Kulling,

Could not get back to this issue this week. We will be auditing the TIBCO data in coming week and will provide you list of adjustments that we feel went incorrect on Invoice. Will update you on this by Wed 2-Aug-2017 next week.

Thank you!

cc: Satya, Jyoti Agrawal, Venkatesh Pujari

Hi Debbie Kulling,

Auditing part for TIBCO is still pending. Due to on going tasks we are not able to work on this.
Will provide an update on this, once we resume back working on this.
Not committing any date, but will try to schedule and work on this in upcoming 2 sprints.

Thank you!

cc: Gaurav Sodani

Following is pending:

• Need to check if current code deployed on Production contains the fix done for this issue.
• Data Audit for generated invoices.

This will be done by 27-Oct-2017

Thank you!

cc: Gaurav Sodani

Prasanna Karlekar Gaurav Sodani Satya

Hey Prasanna, has this been done?

Hi Jennifer Reed,

Below 2 points are pending against this JIRA ticket:
1. We had done the fix for Issue #1, on the TIBCO company only, at that time, as it was required on priority to get the invoice processed. This fix is not yet deployed on any environment as end to end testing was not done at that time due to time constraint. Once testing is done at development end, patch for this ticket can be given.
-Unit testing for this will be done with WT-11691 as both require the adjustment part to be thoroughly unit tested.

2. Data audit for already generated invoices for TIBCO.
-This will be a time taking activity. This activity is to check if any incorrect data was processed by previously generated invoices.

Hope this clears your query. Also, do let us know, if any more details are required.

Thank you!

cc: Gaurav Sodani, Satya, Jyoti Agrawal

Thank you Prasanna Karlekar for the clarification

We will be covering the scenario testing for this JIRA in WT-11691. For updates please refer work log details of WT-11691.

Thank you!

Hi All, Attaching development approval email to work on this ticket: FW Development approval for 9-Nov-2017.msg

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

cc: Sachin Hingole

Hi Prasanna Karlekar,

I have tested some scenarios like retro term adjustments on LB and observed that the records displayed on Invoice are not as per expectation. Please find the below listed scenarios for which the system failed on LB :-

1] Billed Rate - Bill for entire month policy - 1 day enrollment generate invoice for December month
Actual result :- System billing the Employee for 11 months.
2] SelfInsued Rate - Bill for entire month policy - 1 day enrollment generate invoice for December month
Actual result :- System billing the Employee for 11 months.
3] Rate Plan Design Mapping is not working for Self Insured Rates

I have verified this on Stage and observed that on Stage it is working as per expectation.

REOPEN

Sachin Hingole,Prasad Patil

Thanks,
Venkatesh

Following are the 3Cs:
Concern:
One day enrollment effective and termed retrospectively, populating retro add records for months which should not be billed.

Cause:
To get the retro adds, month wise, we break the date span stored in system in subsequent months.
While doing code fix for this issue we had added a condition to populate month wise retro add records, only when the effective date is less than or equal to elections actual termination date. Instead of election effective date, monthwise start date should have been considered.
Example: On 12/18/2017, election was made with effective date as 1/1/2017. Now, user waives this election by date 1/2/2017. Hence, the election stored in system is for span 1/1/2017 to 1/1/2017, a one day election.
In this scenario, retro add records were getting populated for months from Jan 2017 - Nov 2017. Instead they should have populated for Jan 2017 only.

Correction:
We have changed the conditionn to consider monthwise start date instead of actual election effective date while populating retro add records.

Impacted Areas:
Retro add records appearing for Invoice Adjustments

Affected Files:
OES_SP_GetRetroBillingDetails_InvoiceBenefitWise

Unit tested Scenarios:
Could verify following scenarios - First Invoice

Thank you!

Hi Prasanna Karlekar,

Tested the Retro Add and Retro Term scenarios along with ADD/TERM Policies on LB on For QA Casio For Hspl company. They are working fine as expected. This is ready for Stage.

Gaurav Sodani,Sachin Hingole,Hrishikesh Deshpande,Jyoti Agrawal

Thanks,
Venkatesh

Hi All,

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

Regards
Gaurav

Hi Prasanna Karlekar,

Tested the Retro Add and Retro Term scenarios along with ADD/TERM Policies on Stage on 2018 CHMC For HSPL company. They are working fine as expected. This is ready for Production.

Sachin Hingole,Jyoti Agrawal,Hrishikesh Deshpande,Gaurav Sodani

Thanks,
Venkatesh

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Hi Prasanna Karlekar,

Tested the Retro Add and Retro Term scenarios along with ADD/TERM Policies on Production on AFI For HSPL company. They are working fine as expected.

Sachin Hingole,Hrishikesh Deshpande,Jyoti Agrawal

Thanks,
Venkatesh

Hi Debbie Kulling,

The issues have been resolved and also tested on Production. Could you please verify and close this ticket.

Thanks,
Venkatesh