Develop edge API for invoices
- Joseph Reimers
Problem
A variety of proposed features and functional enhancements related to invoice management and processing have been suggested. Developing a comprehensive edge API would simplify development of external-facing invoice functionality.
Possible scope
Allow external entities (e.g. vendors, helper apps) to create invoices based on known data (e.g. vendor, order number)
Allow external entities (e.g. bursar systems, helper apps) to retrieve voucher data on demand based on known data
Allow external entities to update certain voucher data
Allow external entities to update invoice status
Use cases and requirements
Requirement | Status | Use case |
|---|---|---|
Allow creation of an invoice in FOLIO from an external source using JSON | pending | Library vendor can transmit invoice data based on FOLIO order data to create an invoice in real-time Library uses a helper app to parse pdf and email invoices and wants to load those directly into FOLIO without manual keying |
Allow external entities to retrieve approved invoice/voucher data based on status and/or creation day. | pending | Library wants vouchers from invoices approved that day transmitted into the campus bursar system for payment. Vouchers already transmitted should be excluded. |
Allow external entities to update and reconcile voucher data such as updated exchange rates. | pending | Library needs to update actual disbursement to account for variances between library invoice and actual payment due to difference in exchange rate at the time of payment. |
Allow only trusted entities to create, read or update invoice/voucher data | pending | Campus systems tend to be susceptible to cybersecurity threats. Libraries need to be sure only authorized campus systems can retrieve vouchers and update payment status. |
Allow trusted external entities to mark an invoice as paid | pending | When a voucher has been transmitted to an external bursar system, if the voucher is accepted and the invoice paid, the bursar system should update the FOLIO invoice status to reflect that the invoice has actually been paid. |
Invoice match points should be human readable and based on data available to external systems (rather than restricted to FOLIO UUID) | pending | Bursar system needs to retrieve data or update data based on vendor invoice number Bursar app requires common vendor code for payments |
Respect Acq Units | pending | Single-tenant consortium has multiple institutions with independent bursar systems which align with acq units. Library with multiple ordering departments handle acquisitions procedures differently and requires individualized voucher processes. |
Create endpoints for IDs: | pending | Enable transmission of FOLIO UUIDs to external systems for configuration purposes |
Required match points
Field | Status | Use case |
|---|---|---|
Vendor invoice number | pending |
|
FOLIO POL number | pending |
|
Organization code | pending |
|
Vendor order number | pending |
|