Overview: Cornell has experienced an issue where upon approve and pay the invoice is transitioned to the paid status but NO transactions are created.

Steps to Reproduce:

1. Create 2 funds and budgets

2. Create an order

3. Create an order line with the first fund

4. Open the order

5. Create an invoice

6. Add an invoice line linked to the po line

7. Change the invoice line fund to the second fund

8. Approve the invoice - this will fail with a 400 in Juniper before HF3

9. Unopen the order

10. Remove the fund distribution from the order line

11. Add a new fund distribution with the new fund to the order line

12. Reopen the order

13. Remove the invoice line

14. Add another invoice line with the second fund

15. Approve the invoice

16. Pay the invoice

17. Check the payment transaction

18. Check the budgets

NOTE: Library had created the invoice based on POL and it would not approve (Because the invoice line referenced an encumbrance that did not exists anymore). The invoice line was deleted and added back and the invoice was successfully approved and paid. However, no transactions (Payments or credits) can be found on the budget.

Expected Results: Invoice is approved and paid successfully and necessary transactions are created against the correct budget

Actual Results:

Additional Information:

To sum up conclusions, this can happen for an invoice created before Juniper HF3, if an invoice line fund was changed to a different fund before the invoice was approved and the approval failed (see https://folio-org.atlassian.net/browse/MODINVOICE-290#icft=MODINVOICE-290). After this, mod-finance-storage is keeping a failed temporary transaction that is making any future invoice approval silently fail to create pending payments for the same invoice, even in the latest Kiwi. Only editing the mod-finance-storage database to remove the failed temporary transaction before approving the invoice would resolve the issue.

https://folio-org.atlassian.net/browse/MODFISTO-268#icft=MODFISTO-268 would resolve the latest issue of invoices staying in an unstable state after something bad happens when creating a transaction, because new summary ids would be used instead of invoice ids. Failed groups of transactions would not affect new ones.

URL:
Interested parties: