[UXPROD-1145] Interact with external financial or eProcurement systems to process payments and credit Created: 19/Jan/18 Updated: 09/Mar/22 |
|
| Status: | In Progress |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Epic | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ACQDRAFT, acquisitions, finances, post-v1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Name: | External Financial System Integration |
| Analysis Estimate: | Large < 10 days |
| Analysis Estimator: | Dennis Bridges |
| Development Team: | Thunderjet |
| Start date (migrated): | |
| End date: | |
| Epic Color: | ghx-label-8 |
| Description |
|
may be single systems at the university or state level, or additional systems at the national level (e.g. the Nordics). Some libraries may also choose to track financials in an eProcurement system rather than their ILS.� may be single systems at the university or state level, or additional systems at the national level (e.g. the Nordics). Some libraries may also choose to track financials in an eProcurement system rather than their ILS. At minimum available as PDF but electronic is preferred. Notes: Critical! Tight integration via API cuold happen later. Need to determine which are the top 3 systems and focus on those. FMID: ID519 Info from Ann Crowley and Sharon Beltaine August 2019: For Cornell, Ann Crowley notes that currently invoices approved, and we use the Voyager Reporter client to create a voucher for each invoice. The financial information from the voucher is how we create the electronic feed for DFA. Cornell will modify its existing Voyager-to-DFA integration to work with FOLIO instead of using this solution. This comment is about the financial aspects of this integration only. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 28/May/18 ] |
|
Dennis Bridges - Looks like these should be "new features", not epics, as we want the estimates at the feature level. Epics are, with a few exceptions, the line items from the v1 roadmap. We shouldn't really be adding epics without speaking with Hkaplanian. |
| Comment by Dennis Bridges [ 28/May/18 ] |
|
Sure thing, I'm not actually creating any Epics just linking the features to what exists already. My thinking is I can approach Harry and discuss the need for new Epics if there are features that don't fit well under the existing ones. I'm not sure who created this one, but I may have linked issues to it. |
| Comment by Tod Olson [ 06/Jun/18 ] |
|
Rather than target specific systems, you may want to think in terms of integration hooks. FOLIO could provide a way to move invoice/voucher requests from FOLIO to an external system (API, export file, whatever) and a way for the external system to return data (check number for a paid invoice or whatever) in a fairly generic format. If the right hooks are in place, then the implementing can handle the rest of integration and share those solutions. |