Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-13032

Billing regarding call - points

    Details

    • 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

      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

      Billing summary report discrepancy file Copy of BCSS life 1-18.xls attached in JIRA and discrepancy highlighted in red color

      CC: Prasanna Karlekar Gaurav Sodani Satya

        Attachments

          Activity

          Hide
          Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

          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

          Show
          Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - 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
          Hide
          prasanna Prasanna Karlekar (Inactive) added a comment - - edited

          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!

          Show
          prasanna Prasanna Karlekar (Inactive) added a comment - - edited 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!
          Hide
          dkulling Debbie Kulling added a comment -

          Can you please unmap the rate and recalculate

          Show
          dkulling Debbie Kulling added a comment - Can you please unmap the rate and recalculate
          Hide
          dkulling Debbie Kulling added a comment -

          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

          Show
          dkulling Debbie Kulling added a comment - 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
          Hide
          dkulling Debbie Kulling added a comment -

          one more thing. This rate has been mapped for years. Why didn't we have this issue before

          Show
          dkulling Debbie Kulling added a comment - one more thing. This rate has been mapped for years. Why didn't we have this issue before
          Hide
          prasanna Prasanna Karlekar (Inactive) added a comment -

          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

          Show
          prasanna Prasanna Karlekar (Inactive) added a comment - 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
          Hide
          prasanna Prasanna Karlekar (Inactive) added a comment -

          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

          Show
          prasanna Prasanna Karlekar (Inactive) added a comment - 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
          Hide
          dkulling Debbie Kulling added a comment -

          can I please get an ETA on completion

          Show
          dkulling Debbie Kulling added a comment - can I please get an ETA on completion
          Hide
          umesh.kadam Umesh Kadam (Inactive) added a comment -

          Hi Prasanna Karlekar,

          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]

          Show
          umesh.kadam Umesh Kadam (Inactive) added a comment - Hi Prasanna Karlekar , 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]
          Hide
          prasanna Prasanna Karlekar (Inactive) added a comment -

          Hi Umesh Kadam,

          Expected enrollment count is appearing on report. Please do the required on main copy.

          Thank you!

          cc: Amruta Lohiya, Jyoti Mayne

          Show
          prasanna Prasanna Karlekar (Inactive) added a comment - Hi Umesh Kadam , Expected enrollment count is appearing on report. Please do the required on main copy. Thank you! cc: Amruta Lohiya , Jyoti Mayne
          Hide
          umesh.kadam Umesh Kadam (Inactive) added a comment -

          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]

          Show
          umesh.kadam Umesh Kadam (Inactive) added a comment - 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]

            People

            Assignee:
            dkulling Debbie Kulling
            Reporter:
            parmeshwar.jumbad Parmeshwar Jumbad (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 8.5h
                8.5h