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

WT -> BCC Invoice Enhancement -> Same month billing and adjustment | Positive Negative Costs Sequence | Duplicate entries

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Module:
      BenAdmin - Report
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 27

      Description

      Plan- Vision
      Rate - mapped rate has billed Rate (16)

      • enrollment exists from 09/01/2016 to 12/31/2016
      • fetched invoices for Sept Oct Nov 2016 - worked expected [showed billed rate costs ie, 16 in all months billing data]
      • changed billed rate value from 16 to 20
      • fetched invoice for Dec 2016 & below are the issues -
      1. though the invoice is for Dec 2016 : adjustments are also shown for the same month ie, Dec 2016 [this is not dependent on the Billing Period Policies flag on general plan design - checked]
      2. the positive and negative adjustments shown for the same month should be in same order. We can keep it as Positive first and then the Negative ones
      3. In case of enrollments in multiple plans within a benefit type - as discussed with Prasanna we are showing the only latest enrollments. Here system shown the duplicate records

      CC - Deepali Tidke Venkatesh PujariRakesh Roy Hrishikesh Deshpande

        Attachments

        1. #21.xlsx
          324 kB
        2. 7257 change rquest .doc
          42 kB
        3. Duplicate Entries.png
          Duplicate Entries.png
          141 kB
        4. Pos Neg Alternate.png
          Pos Neg Alternate.png
          138 kB
        5. Same Month Adjustment.png
          Same Month Adjustment.png
          89 kB

          Issue Links

            Activity

            Transition Time In Source Status Execution Times
            Prasanna Karlekar (Inactive) made transition -
            Open New Request
            10d 1h 37m 1
            Jyoti Agrawal (Inactive) made transition -
            New Request Pending for Approval
            107d 17h 52m 1
            Jyoti Agrawal (Inactive) made transition -
            Pending for Approval Approved for Development
            4s 1
            Jyoti Agrawal (Inactive) made transition -
            Approved for Development In Development
            3s 1
            Venkatesh Pujari (Inactive) made transition -
            In Development In LB Testing
            4d 5h 34m 1
            Venkatesh Pujari (Inactive) made transition -
            In LB Testing Pending for Stage Approval
            3d 35m 1
            Venkatesh Pujari (Inactive) made transition -
            Pending for Stage Approval Approved for Stage
            1d 21h 20m 1
            Venkatesh Pujari (Inactive) made transition -
            Approved for Stage Stage Testing
            2s 1
            Venkatesh Pujari (Inactive) made transition -
            Stage Testing Pending for Production Approval
            21h 43m 1
            Venkatesh Pujari (Inactive) made transition -
            Pending for Production Approval Approved for production
            5d 1h 50m 1
            Venkatesh Pujari (Inactive) made transition -
            Approved for production In Production Testing
            2s 1
            Venkatesh Pujari (Inactive) made transition -
            In Production Testing Production Complete
            2h 33m 1
            Venkatesh Pujari (Inactive) made transition -
            Production Complete Closed
            3s 1

              People

              Assignee:
              venkatesh.pujari Venkatesh Pujari (Inactive)
              Reporter:
              alankar.chavan Alankar Chavan (Inactive)
              Developer:
              Jyoti Agrawal (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 6h Original Estimate - 6h
                  6h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 32.25h
                  32.25h