Uploaded image for project: 'mod-invoice'
  1. mod-invoice
  2. MODINVOICE-487

Encumbrance amount updated incorrectly after cancelling related invoice

    XMLWordPrintable

Details

    • ACQ Sprint 171
    • 2
    • Thunderjet
    • Poppy (R2 2023)
    • TBD

    Description

      Overview:

      Encumbrance amount updated incorrectly after cancelling related invoice

      Preconditions:

      1. Active fund having budget with $100 allocation and Allowable encumbrance = 110%
      2. Open order with initial encumbrance $110 exists
      3. An invoice related to open order (Release encumbrance is NOT active) exists
      4. A user with the following permissions is logged in:
      • Finance: View fund and budget
      • Invoice: Approve invoices
      • Invoice: Can view and edit Invoices and Invoice lines
      • Invoice: Cancel invoices
      • Invoice: Pay invoices

      Steps to Reproduce:

      1. Edit invoice line for invoice from Preconditions #3 => change "Sub-total" field value to "10" => Click "Save & close" button
      2. Approve and pay edited invoice
      3. Check that "Current encumbrance" amount in invoice line has "100" value
      4. Cancel paid invoice
      5. Click invoice line record  "Current encumbrance" link in "Fund distribution" accordion

      Expected Results:

      "Current encumbrance" link in "Fund distribution" accordion has "110" value (equal to "Initial encumbrance")
      Actual Results:

       "Current encumbrance" link in "Fund distribution" accordion has "100" value
      Additional Information:
      Does not reproduce when "Release encumbrance" checkbox in invoice line is Active

      Scenario 1 - Invoice is approved (Pending payment transactions exist)

      Invoice amount = 10 (Pending payment)

      Before cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 15
      Current encumbrance = 85

      After cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 0
      Expended = 15
      Current encumbrance = 95

      Scenario 2 - Invoice is Paid (Payment transactions exist)

      Invoice amount = 15 (Payment)

      Before cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 15
      Current encumbrance = 85

      After cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 0
      Current encumbrance = 100

      Scenario 3 - Invoice is Paid (Credit transactions exist) Note: we found an issue with this scenario. Expended having a min value of 0 could result in canceled credit invoices over stating the expended value. If before the credit it was 0 after the credit it technically should be negative and when canceled back to 0 but this is not happening. To resolve without causing rollover issues we will need to address with new functionality.

      Invoice amount = -15 (Credit)

      Before cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 0
      Current encumbrance = 115

      After cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 0
      Current encumbrance = 100

      Scenario 4 - 2 Invoices are Paid (Credit transactions exist)

      Invoice amount = 15 (Payment)
      Invoice amount = -15 (Credit)

      Before cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 0
      Current encumbrance = 115

      After cancellation

      Encumbrance values:
      Initial encumbrance = 110
      Awaiting payment = 10
      Expended = 15
      Current encumbrance = 100

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                jreimers Joe Reimers
                Nina Chistova Nina Chistova
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases