Hi Prasanna Karlekar & Amruta Lohiya,

Please coordinate together to resolve this issue

Regards
Gaurav

Umesh KadamSatyaHrishikesh Deshpande

Hi Kira Hamilton,

We have verified this issue. It is caused because of fix done in WT-10187, which impacted the retro add adjustments in case of multiple self insured component scenario.

Following is the scenario:
Rate name : AmWins MediGap
Components mapped : AmWins, BCC Fee, EAP Fee, HUB Fee, EHCW Fee
Retro add cost for component AmWins was appearing and other components cost was getting excluded. To fetch proper data in case of multiple self insured components we have done script changes on all BCC companies.

Update regarding impacted invoices:
WT-10187 was deployed in Production environment on 22-Dec-2017.
We are scanning this scenario for invoices generated after 22-Dec-2017 on all BCC companies.
Will provide detailed update about scanned data by tomorrow 12-Jan-2018.

Apologies. By mistake, regenerated Feb 2018 invoice on COB instead of HSPL copy, while verifying the script change for mentioned employee.

Do let us know, if issue still persist.

Thank you!

Hi,

Per an email received 1/11/2018 from Jennifer H at BCC, I have re-ran the February invoice with all of the retirees who needed to have a rate change and the issue has been resolved.

This ticket can be closed,

Thank you,
Kira Hamilton
Debbie Kulling

Please see previous note posted.

Hi Kira Hamilton,

Have reopened this ticket as scanning for impacted invoices was not complete yesterday.

Thank you!

Hi Kira Hamilton,

We have scanned all BCC company invoices that were generated after 12/21/2017.
We found adjustment issue related to self insured components for 4 companies.

Following are the impacted invoices:

For details, please refer WT-13063_ImpactedInvoices.xlsx.

Please let us know if it is possible do delete and regenerate these invoices.
If not, then, we will manipulate data from back end, so that affected elections will have proper adjustments in next invoices.

Kindly inform.

Thank you!

Hi Prasanna Karlekar,

Per BCC: The only group's invoice that can be deleted by development is City of Walnut Creek's January invoice. Other than this group, please inform Development that they absolutely CANNOT DELETE our generated Invoices. This is NOT an option. They must make the appropriate adjustments and have those adjustments appear on the client’s next Invoice. I would also like an explanation as to how or why this occurred? Also, what has been put into place to ensure that this does not happen again in the future.

Thank you,
Kira Hamilton
Debbie Kulling

Hi Kira Hamilton,

Following are the updates for above reply from BCC:
#1. "The only group's invoice that can be deleted by development is City of Walnut Creek's January invoice."
-There are only 4 elections that were impacted for this company. We will trigger the adjustments from backend so that they appear in Feb 2018 invoice. No need to regenerate Jan 2018 invoice for City of Walnut Creek as well.

#2. "Other than this group, please inform Development that they absolutely CANNOT DELETE our generated Invoices. This is NOT an option."
-Please be informed that, we never delete any invoice (finalized / non finalized) on main company. We always do the verification on HSPL copy. If any time it does happens, then it is only by mistake and not intentionally. Hence, we will not be deleting / regenerating any of the client's invoices.

#3. "They must make the appropriate adjustments and have those adjustments appear on the client’s next Invoice."
-Yes. This will be done. You can expect the data that will trigger adjustments on Feb 2018 invoice, to be inserted in system by following date:

We need more time for COSB, as there are around 61 adjustments that needs to triggered. We need time to insert this data and verify it once at our end.

#4. I would also like an explanation as to how or why this occurred?
-This issue was there only for Health plans when a rate has more than 1 self insured component mapped. We have already mentioned in our first comment itself that, this issue is caused because of fix that we did in WT-10187. We had verified WT-10187 for Health - Billed Rate, Health - Single Self Insured Component and Non Health plan - Single Rate, Non Health plan - Multiple rates mapped. We did not verify the scenario for multiple self insured components. And this issue got reported for multiple self Insured components where only single component cost was appearing on invoice and rest of the components cost was getting excluded.

#5. Also, what has been put into place to ensure that this does not happen again in the future.
-While doing any core logic changes, in our verification check list with Health Plan - Billed Rates, Health Plan - Single Self Insured Component, Non Health Plan - Single Rate, Non Health Plan - Multiple Rates, we will also include multiple self insured component scenario.

Please note that we are not converting this JIRA to bug as we had explored this issue at our end while fixing WT-13053. Hence, the fix will be deployed on all companies with WT-13053 only.

Also, we do apologies for the incorrect Jan 2018 invoices that got generated at client end.

Do let us know, if any more details required.

Thank you!

cc: Jyoti Agrawal

Hi Kira Hamilton,

Today, we could complete the correction and verification for City of SeaTac only.
Kindly regenerate Feb 2018 invoice, to get adjustments for Dec 2017. Please note that, we have already mentioned company wise impacted election details in WT-13063_ImpactedInvoices.xlsx.

Kindly confirm and do let us know in case of issues for City of SeaTac.

Thank you!

Hi Venkatesh Pujari,

We have done data manipulation to trigger the adjustments on Feb 2018 invoice. Data manipulation is done on COSB for HSPL.
Kindly verify all the adjustments mentioned in WT-13063_ImpactedInvoices.xlsx for COSB.
Post QA verification we will do the data manipulation on main company.

Thank you!

cc: Sachin Hingole, Rakesh Roy, Gaurav Sodani

Hi Prasanna Karlekar,

I have verified impacted records randomly on HSPL copy. The adjustments seem to fine for both the Invoices. Please could you manipulate the data on Main company.

Thanks,
Venkatesh

Venkatesh Pujari -

We have done data manipulation to trigger the adjustments on Feb 2018 invoice on main copy.
Kindly verify.

Thank you!

Hi Kira Hamilton,

Following is the update from our side:

City of Walnut Creek: No manipulations done as client has regenerated Jan 2018 invoice. Thank you!
COSB : We have verified the ajustment related to incorrect health plan adjustments that appeared on Jan 2018 invoice. We have verified the records mentioned in "WT-13063_ImpactedInvoices.xlsx". Please regenarted Feb 2018 invoice to get proper adjustments.

Kindly verify the data at your end and do let us now in case of issue.

Prasanna Karlekar,Sachin Hingole

Thanks,
Venkatesh