Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-5711

NF:- Invoice Management - Multiple Self Insured components giving wrong adjustments for Retro Add enrollment

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Not Verified
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
      None
    • Environment:
      Others
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Level:
      Partner
    • Module:
      BenAdmin - Report
    • Reported by:
      Harbinger
    • Company:
      All Clients/Multiple Clients
    • Item State:
      LB QA - Ready for Stage
    • Browser:
      Google Chrome

      Description

      Environment - Codemap
      Steps:-
      1] Log onto Codemap site.
      2] Search and select For QA-CHMC-Azure company.
      3] Create on Self Insured components rate with two components.
      4] Generate an invoice of Jan 2018 month
      5] Now do an enrollment from 01/01/2017 with EE tier
      6] Now generate an invoice of Feb 2018 month.
      7] Observe the Feb 2018 invoice

      Correct Billing details are being displayed on Feb 2018 Invoice but wrong adjustments are displayed for multiple self insured components.

        Attachments

          Issue Links

            Activity

            Hide
            prasanna Prasanna Karlekar (Inactive) added a comment -

            Please verify this issue, once NF-5698 is deployed as we had already fixed this issue in NF-5698.

            Thank you!

            cc: Jyoti Agrawal

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - Please verify this issue, once NF-5698 is deployed as we had already fixed this issue in NF-5698 . Thank you! cc: Jyoti Agrawal
            Hide
            prasanna Prasanna Karlekar (Inactive) added a comment -

            Hi Venkatesh Pujari,

            Following are the 3 Cs:
            Concern:
            Multiple Self Insured components giving wrong adjustments for Retro Add enrollment.

            Cause:
            This is caused because of fix done in WT-10187. While excluding duplicate retro add enrollments for same month, we were separating records based on election ID, rate ID and subrate ID. Self Insured Rates ID was not considered. Because of which, in case of multiple self insured components, only single record with any one component cost was getting considered and other component's cost records were getting excluded as they were getting marked as duplicates.

            Correction:
            Now while separating the records, we have included Self Insured Rate Id also. While checking duplicate elections this too will be one parameter for separation which will avoid exclusion of self insured component costs.

            As mentioned above, we have fixed this issue with NF-5698. Assigning the issue to you as NF-5698 is deployed.

            Thank you!

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - Hi Venkatesh Pujari , Following are the 3 Cs: Concern: Multiple Self Insured components giving wrong adjustments for Retro Add enrollment. Cause: This is caused because of fix done in WT-10187 . While excluding duplicate retro add enrollments for same month, we were separating records based on election ID, rate ID and subrate ID. Self Insured Rates ID was not considered. Because of which, in case of multiple self insured components, only single record with any one component cost was getting considered and other component's cost records were getting excluded as they were getting marked as duplicates. Correction: Now while separating the records, we have included Self Insured Rate Id also. While checking duplicate elections this too will be one parameter for separation which will avoid exclusion of self insured component costs. As mentioned above, we have fixed this issue with NF-5698 . Assigning the issue to you as NF-5698 is deployed. Thank you!
            Hide
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment -

            Tested this on Codemap. Working fine as expected. This is ready for Stage.

            Show
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment - Tested this on Codemap. Working fine as expected. This is ready for Stage.

              People

              Assignee:
              venkatesh.pujari Venkatesh Pujari (Inactive)
              Reporter:
              venkatesh.pujari Venkatesh Pujari (Inactive)
              QA:
              Venkatesh Pujari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0.5h Original Estimate - 0.5h
                  0.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h
                  2h