UXPROD-4166 - Getting issue details... STATUS
Problem(s):
Certain accounts payable systems require that orders with encumbrances or similar expected costs must exist prior to allowing payment processing. Some of these systems require at least one calendar day separation between creation of the order and processing the payment. Libraries need to output orders with encumbrances to these AP systems prior to submitting invoices.
Requirements and Use Cases:
| Requirement | Status | Use Cases |
|---|---|---|
| (SAMPLE) Library must specify which open order encumbrance(s) to output | PENDING | When a user creates a new order with an encumbrance, the system needs to know to send the order with encumbrance to the AP system without creating duplicates. When a user creates a new order, all match points must match in order to ensure uniqueness because it is not uncommon for a vendor to have multiple open orders for identical dollar amounts. Current scripts only collect same-day approvals. |
| Disencumbrances due to cancellation or similar with no associated invoice should be output when they occur | DONE | Librarian places an order, encumbering a set amount of money. That order is then cancelled and the fund disencumbered for that amount. The cancellation and disencumbrance needs communicated to the AP system. |
| When an order is created and approved, order information including vendor, funding and banking information must be transmitted to the AP system | IN REFINEMENT | |
| When changes to vendor occur, vendor gets updated in AP system (UXPROD-4164) | IN REFINEMENT | |
| FOLIO allows scripts to come in and get data with minimal user intervention on the FOLIO side | ||
| When a credit is received, library must determine if credit is valid (based on FY) and if so associated with appropriate FY | ||
| When a refund check is issued, applied as credit to existing budget to be assigned (new feature needed for refund handling) | ||
| POL added to existing PO needs to be output as individual order in AP | ||
Questions:
| Question | Status | Conclusion | Comments |
|---|---|---|---|
| Do we need to output encumbrance values or estimated prices? | OPEN | ||
| What format does the output need to be in? | IN PROGRESS | semi-structured text. Can we do JSON? Sample output to come. | |
| What is the relationship, if any, with the need to output organization info? | CLOSED | Tight integration | |
| Is this export process handled via scheduled job, manual export order or API call from the AP system? | CLOSED | Report generated and pushed through pl1/python script for conversion to AP format via automated script on automated or on-demand basis | |
| If a file is to be output, is it output to local or output to sftp? | CLOSED | SFTP; local download from logs | |
| External account number associated with fund code? Does it need to be associated with specific bank account numbers? | OPEN | ||
| What additional info needs to be included in the output? | OPEN | UUID as primary match point? PO numbers are changeable (though some should not be) and they need something fixed, unchangeable and searchable within FOLIO | |
| Where is the match point between FOLIO and the AP system for a given order? | OPEN | Existing vendor, ledger, fund (AP level), order number. Firm orders must have precise vendor match, approval plans, subscriptions allow for misc. For firm orders, invoice must be within a specified window of estimated price or invoice will be rejected. | If required fields do not match, AP system will reject |