[UXPROD-2167] Value management through transactions Part 2 - Payments, Credits and limits - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: New Feature
Status: Closed (View Workflow)
Priority: P1
Resolution: Done
Affects Version/s: None
Fix Version/s: Q1 2020
Component/s: None
Labels:

Template:
Epic Link:
Managing Financial Structures
Analysis Estimate:
Small < 3 days
Front End Estimate:
Small < 3 days
Back End Estimate:
XXL < 30 days
Development Team:
Thunderjet
Calculated Total Rank:
PO Rank:
103
Rank: Chalmers (Impl Aut 2019):
R5
Rank: Chicago (MVP Sum 2020):
R1
Rank: Cornell (Full Sum 2021):
R1
Rank: Duke (Full Sum 2021):
R1
Rank: 5Colleges (Full Jul 2021):
R1
Rank: FLO (MVP Sum 2020):
R1
Rank: GBV (MVP Sum 2020):
R1
Rank: hbz (TBD):
R1
Rank: Hungary (MVP End 2020):
R1
Rank: Lehigh (MVP Summer 2020):
R1
Rank: Leipzig (Full TBD):
R1
Rank: Leipzig (ERM Aut 2019):
R1
Rank: MO State (MVP June 2020):
R2
Rank: TAMU (MVP Jan 2021):
R3
Rank: U of AL (MVP Oct 2020):
R1

Description

Note: this was split from ~~UXPROD-197~~ as work was not able to be completed in Q4. The remaining tasks will primarily account for the creation of payment and credit transactions that will often be the result of processing an invoice. These will updated the impacted budget values based on Fund distribution information on the invoice record. This also, includes the work on restricting encumbrance and spending when budgets do not have enough money allocated to cover the cost. These restriction rely on allowable encumbrance and allowable allocation settings found in each budget.

Previous description:
Problem: As users are creating orders and invoices that result in encumbrances and vouchers money needs to be move from allocated to expended in the appropriate funds.

Overview: There will be 4 types of transaction, payment, credit, allocation and transfer. These will allow users to manage money in a folio fund structure. Payments and credits will be the result of paying/processing invoices and will not be manually created by users. Allocations and transfers will be manually created by users. They will allow users to add or remove money from Funds throughout the fiscal year without need a PO or Invoice created. A list of transaction will be maintained for all budgets in each fiscal year. allowing transparency at a very granular level regarding what money is being spent on and the current state of a particular Funds budget.

TestRail: Results

Attachments

Issue Links

clones

UXPROD-196 Value management through transactions.

Closed

is cloned by

UXPROD-2295 Value management through transactions Part 3 - Fixes and committing/encumbering money for approved invoices

Closed

is defined by

MODFISTO-83 Migration script improvement to support transition of non-unique index to unique one

Closed

MODFISTO-84 Remove default values for budget.allowableEncumbrance and budget.allowableExpenditure

Closed

MODFISTO-86 Update encumbrance doesn't work as expected

Closed

MODFISTO-87 Able to apply transactions after all or nothing operation was performed

Closed

MODFISTO-88 Posting a credit hangs if not part of an invoice

Closed

MODORDERS-342 Check enough money in budgets while creating encumbrances

Closed

UIF-165 Search option “All” for ledger does not include Code

Closed

UIOR-494 Update settings permission label

Closed

is duplicated by

UIF-162 Display over encumbered and over expended values on Budget view

Closed

relates to

MODFIN-86 Restrict adjustment of budget's allowableEncumbrance and allowableExpenditures

Closed

MODFISTO-28 Transaction Calculations - Payments/Credits

Closed

MODFISTO-62 Payment restrictions

Closed

MODFISTO-63 Encumbrance restrictions

Closed

UIF-81 CRUD Payment

Closed

UIF-82 CRUD Credit

Closed

UIF-186 Ledger groups table not scrolling - showing a maximum of 10 groups

Closed

UIOR-431 Prevent encumbering with Funds that have insufficient amounts to cover distribution

Closed

UIOR-465 Error Message: No budget for this fund and fiscal year

Closed

MODFIN-71 Create transaction APIs - Payments, Credits

Closed

MODFIN-98 Ledger not displaying correct allocated total

Closed

MODFIN-106 Add fiscalYear query arg to GET /finance/ledgers API

Closed

MODFIN-113 Add invoiceId and invoiceLineId to the awaitingPayment schema

Closed

MODFISTO-61 budget/ledger unavailable shouldn't include overEncumbered amounts

Closed

MODFISTO-64 Ability to override allowableEncumbrance/allowableExpenditure

Closed

MODFISTO-80 LedgerFY records must be updated on payments/credits

Closed

MODFISTO-81 Budget expenditures must always be updated on payments/credits

Closed

MODFISTO-82 awaitingPayment should never go below 0

Closed

MODINVOICE-109 Create payment or credit when Invoice marked as 'Paid'

Closed

MODINVOICE-113 Call awaiting-payment API upon invoice approval

Closed

MODINVOICE-139 Create PUT /voucher/vouchers/<id>

Closed

UIF-148 Update Fiscal year record view to display group and related totals for that year

Closed

UIF-149 Update Fiscal year record view to display Ledger and related totals for that year

Closed

UIF-177 Update transaction view

Closed

UINV-117 Allow user to edit voucher information

Closed

UXPROD-197 View the total amounts available in Ledger and grouping of associated Funds.

Closed

UXPROD-697 Ability to facilitate ordering and invoicing in currencies other than default currency

Closed

UXPROD-783 Ability to create a negative invoice that results in one or many credit transactions

Closed

UXPROD-1144 Managing Ledgers, Funds, Budgets, Fiscals Years and tracking associated values

Closed

UXPROD-1152 CRUD invoices and resolve/process invoices

Closed

(5 is defined by , 1 is duplicated by, 30 relates to)

Activity

People

Assignee:: Dennis Bridges

Reporter:: Dennis Bridges

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 29/Nov/19 7:32 PM

Updated:: 16/Sep/20 9:16 PM

Resolved:: 18/Mar/20 3:08 PM

Value management through transactions Part 2 - Payments, Credits and limits