-
Type:
Support Activity
-
Status: Resolved
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Support Task Type:Query Resolution
-
Environment:Production
-
Reported by:Client
-
Company:ATC
-
Module:BenAdmin - Report
-
Issue Importance:Good To Have
-
Severity:Simple
As discussed in the call client requires billing details report with self insured components in column-wise format & need to verify discrepancy in Billing summary report and Enrollment report . Please check attached email for more details. Re Call on Monday Morning regarding Billing.oft
Billing summary report discrepancy file Copy of BCSS life 1-18.xls attached in JIRA and discrepancy highlighted in red color
Parmeshwar Jumbad (Inactive)
created issue -
Parmeshwar Jumbad (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Billing Details Column-wise report with self insured components | Billing regarding call - points |
Parmeshwar Jumbad (Inactive)
made changes -
| Description |
As discussed in the calll client requires billing details report with self insured components in column-wise format. Please check attached email for more details. [^Re Call on Monday Morning regarding Billing.oft] CC: [~prasanna] [~gaurav.sodani] [~satyap] |
As discussed in the call client requires billing details report with self insured components in column-wise format & need to verify discrepancy in Billing summary report and Enrollment report . Please check attached email for more details. [^Re Call on Monday Morning regarding Billing.oft] CC: [~prasanna] [~gaurav.sodani] [~satyap] |
Parmeshwar Jumbad (Inactive)
made changes -
| Attachment | Copy of BCSS life 1-18.xls [ 71466 ] |
Parmeshwar Jumbad (Inactive)
made changes -
| Description |
As discussed in the call client requires billing details report with self insured components in column-wise format & need to verify discrepancy in Billing summary report and Enrollment report . Please check attached email for more details. [^Re Call on Monday Morning regarding Billing.oft] CC: [~prasanna] [~gaurav.sodani] [~satyap] |
As discussed in the call client requires billing details report with self insured components in column-wise format & need to verify discrepancy in Billing summary report and Enrollment report . Please check attached email for more details. [^Re Call on Monday Morning regarding Billing.oft] Billing summary report discrepancy file [^Copy of BCSS life 1-18.xls] attached in JIRA and discrepancy highlighted in {color:red}red{color} color CC: [~prasanna] [~gaurav.sodani] [~satyap] |
| Remaining Estimate | 0h [ 0 ] | |
| Time Spent | 2.5h [ 9000 ] | |
| Worklog Id | 99793 [ 99793 ] |
Hi Debbie Kulling,
Have verified following discrepancies related to Billing Summary Report for Company - Barrow:
| Plan Name | Summary Report Count | Enrollment Report Count |
| Employee Optional Life | 818 | 818 |
| Employee Accident Coverage | 600 | 756 |
Count for Employee Optional Life matches.
Following is the reason for enrollment count discrepancy for Accident plan:
2 rates are mapped to this plan. 2018 - Accident - Employee and 2018 - Accident - Spouse. Summary report does not work for multiple Sub Rates. In case of multiple sub rates, as per data stored in system, sub rate that got stored first against an election is considered while processing summary. In our case for 600 elections, cost was first stored for rate 2018 - Accident - Employee. For remaining 156 elections, cost was first stored for rate 2018 - Accident - Spouse. All elections for this plan are done with coverage of Member type employee. But 2018 - Accident - Spouse rate is configured for Member type Spouse. Due to this member type discrepancy such records are getting excluded. Hence the difference in enrollment count.
Please validate, if the customization to map Spouse rate for Employee Optional Life plan is correct or not. If not then it needs to be unmapped and recalculation needs to be done. After which, discrepancy should get resolved between Enrollment and Billing Summary report
Hope this helps you.
Thank you!
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Prasanna Karlekar [ prasanna ] | Debbie Kulling [ dkulling ] |
| Resolution | System Behaviour [ 10100 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
Can you please unmap the rate and recalculate
also this need to be logged as a bug. There are times when we map two rates two one plan and when that happens the billing summary report should still work and be accurate
one more thing. This rate has been mapped for years. Why didn't we have this issue before
-
- Time Spent:
- 2.5h
-
Issue analysis
Procedure debug to find root cause
JIRA update
Email communication
| Time Spent | 2.5h [ 9000 ] | 5h [ 18000 ] |
| Worklog Id | 99850 [ 99850 ] |
| Worklog Id | 99850 [ 99850 ] |
| Resolution | System Behaviour [ 10100 ] | |
| Status | Resolved [ 5 ] | Reopen [ 4 ] |
| Assignee | Debbie Kulling [ dkulling ] | Parmeshwar Jumbad [ parmeshwar.jumbade ] |
| Comment |
[ Hi [~parmeshwar.jumbade], Could you please look in to this on priority and update? Thanks. ------------------------------------------------------- CC: [~prasanna], [~satyap], [~gaurav.sodani] ] |
| Assignee | Parmeshwar Jumbad [ parmeshwar.jumbade ] | Prasanna Karlekar [ prasanna ] |
| Status | Reopen [ 4 ] | In Progress [ 3 ] |
| Attachment | WT-7561.png [ 71574 ] |
Hi Debbie Kulling,
We have created WT-13060 for issue "Billing Summary should work when multiple rates are mapped".
Regarding mapping of Spouse rate to Employee Accident plan:
We had this same issue last year too. Reference JIRA WT-7516. But at that time we handled it via corrections. Please refer below screenshot:
Hence now it is better, if we unmap and recalculate.
Assigning this JIRA to enrollment team for unmapping and recalculation. Post enrollment team's recalculation we will verify the Billing Summary report.
Thank you!
cc: Gaurav Sodani
Hi Jyoti Mayne,
Please unmap rate 2018 - Accident - Spouse for plan Employee Accident Coverage and recalculate. Assign the JIRA back to us for verification once recalculation is complete.
Thank you!
cc: Gaurav Sodani
| Assignee | Prasanna Karlekar [ prasanna ] | Jyoti Mayne [ jyoti.mayne ] |
-
- Time Spent:
- 1h
-
Previous JIRA go through
Discussion on previous corrections done
Discussion with Enrollment team for recalculation
New JIRA creation
JIRA update
| Time Spent | 5h [ 18000 ] | 6h [ 21600 ] |
| Worklog Id | 99972 [ 99972 ] |
| Worklog Id | 99972 [ 99972 ] |
can I please get an ETA on completion
| Assignee | Jyoti Mayne [ jyoti.mayne ] | Umesh Kadam [ umesh.kadam ] |
As requested, we have un-mapped "2018 - Accident - Spouse" rate from "Employee Accident Coverage" Plan in "Barrow for HSPL" on production. Please check and confirm.
Thanks and Regards,
:: Umesh Kadam
CC : Amruta Lohiya, Rohan J Khandave, Jyoti Mayne, [~parmeshwar.jumbade]
| Assignee | Umesh Kadam [ umesh.kadam ] | Prasanna Karlekar [ prasanna ] |
Hi Umesh Kadam,
Expected enrollment count is appearing on report. Please do the required on main copy.
Thank you!
cc: Amruta Lohiya, Jyoti Mayne
| Assignee | Prasanna Karlekar [ prasanna ] | Umesh Kadam [ umesh.kadam ] |
Hi Debbie Kulling,
As requested, we have un-mapped "2018 - Accident - Spouse" rate from "Employee Accident Coverage" Plan in LIVE copy of "Barrow" on production. Please check and confirm.
Thanks and Regards,
:: Umesh Kadam
CC : Amruta Lohiya, Rohan J Khandave, Jyoti Mayne, Prasanna Karlekar, [~parmeshwar.jumbade]
| Assignee | Umesh Kadam [ umesh.kadam ] | Debbie Kulling [ dkulling ] |
| Resolution | Done [ 10000 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Time Spent | 6h [ 21600 ] | 8h [ 28800 ] |
| Worklog Id | 100409 [ 100409 ] |
-
- Time Spent:
- 2h
-
Analysis
Data correction and verification in HSPL and LIVE copy
Discussion with Parmeshwar and Prasanna
-
- Time Spent:
- 0.5h
-
Billing Summary verification
JIRA update
| Link | This issue relates to WT-13060 [ WT-13060 ] |
| Time Spent | 8h [ 28800 ] | 8.5h [ 30600 ] |
| Worklog Id | 101283 [ 101283 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
7h 50m | 1 |
|
21h 33m | 1 |
|
27m 54s | 1 |
|
4d 23h 26m | 2 |
Hi Prasanna Karlekar,[~parmeshwar.jumbade],
As per our discussion, we have checked to achieve discussed format but we can't achive this on export.
CC-Vinayak Kulkarni