Invoicing functionality that FOLIO needs to stay competitive (UXPROD-3439)

[UXPROD-4169] Update voucher information from accounts payable system Created: 05/Apr/23  Updated: 18/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Umbrellaleaf (R2 2025)
Parent: Invoicing functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: ecs, lc-priority6, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-4396 AP system integration Draft
Potential Workaround: Joe Reimers - this process can currently be accomplished manually via library staff from within FOLIO.
Epic Link: Invoicing functionality that FOLIO needs to stay competitive
Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: Many libraries integrate with third-party accounts payable (AP) systems (such as Banner, Momentum, etc.) When these systems retrieve voucher information from the FOLIO system, particularly via API call from the AP system, they need to update voucher and other related payment information within FOLIO to reflect changes in exchange rate, status, invoice status and other related fields.

This process is currently a manual process within FOLIO, and relies on library staff outputting vouchers to AP systems rather than permitting AP systems to retrieve vouchers ready for payment.

Within a multitenant consortium, this functionality should be configurable per tenant.

In scope 

  • Update voucher information in response to an API call from an authorized external system
  • Update invoice information in response to an API call from an authorized external system
  • Prevent update of information in response to an API call from an unauthorized external system
  • Logging of relevant updates
  • Logging of errors/rejected vouchers
  • Implement necessary configuration to allow support for multiple accounts payable systems within a multitenant consortium.

Out of scope

Use case(s)

A library relies on a third-party accounts payable system for payment of invoices. This accounts payable system pulls vouchers that are ready for payment from the FOLIO system. The accounts payable system then sends the FOLIO system updates via API to indicate that the voucher has been processed, the exchange rate updated (if needed) and the invoice paid.

Proposed solution/stories

Links to additional info

Questions

Do we want to update Order/POL status as well?


Generated at Fri Feb 09 00:37:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.