Organizations (Vendor) management functionality that FOLIO needs to stay competitive (UXPROD-3441)

[UXPROD-4170] Organizations - Store banking information for a given organization Created: 05/Apr/23  Updated: 05/Feb/24

Status: In Review
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Organizations (Vendor) management functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 1
Labels: LC-priority1, SolutionArchitecture, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File no-permissions.png     PNG File screenshot-1.png     PNG File screenshot-2.png    
Issue links:
Defines
is defined by UIORGS-418 Suppress banking error message for un... Closed
is defined by MODORG-54 BE - Banking information fields edit ... Closed
is defined by MODORG-60 Support searching by bankAccountNumber Closed
is defined by MODORGSTOR-148 BE - Implement CRUD for Banking Accou... Closed
is defined by MODORGSTOR-155 BE - Implement CRUD for Organization ... Closed
is defined by UIORGS-388 Permissions for Banking information Closed
is defined by UIORGS-389 Create banking information accordion ... Closed
is defined by UIORGS-390 Banking information fields Closed
is defined by UIORGS-391 Settings for banking information Closed
is defined by UIORGS-392 Search organization on bank account n... Closed
is defined by UIPFO-47 Search organization on bank account n... Closed
Release: Quesnelia (R1 2024)
Epic Link: Organizations (Vendor) management functionality that FOLIO needs to stay competitive
Analysis Estimate: Medium < 5 days
Analysis Estimator: Khalilah Gambrell
Front End Estimate: Medium < 5 days
Front End Estimator: Mikita Siadykh
Front-End Confidence factor: 80%
Back End Estimate: XL < 15 days
Back End Estimator: Serhii_Nosko
Back-End Confidence factor: 80%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: Certain libraries need to store organization-specific banking and account information in the organization record, independent of the normal account information stored in an organization record. This banking information is sensitive and requires its own permissions in order to view. These permissions may be assigned to external systems via API in some instances.

In scope

  • Create a Banking info accordion associated with an Organization record
  • Create required banking fields
  • Create permissions for viewing, creating, editing and deleting banking information
  • Create protections preventing banking information from being included in organizations-related reports, except specific reports run by authorized persons.
  • Suppress the banking accordion from view to unauthorized users
  • Create or modify record history functionality associated with banking information, visible only to authorized users
  • Mask account numbers and other restricted information
  • Allow authorized users to view masked information
  • Allow banking information to be output to authorized external systems

Out of scope

Use case(s)

A library uses FOLIO as its primary data store for bank account information for many of its vendors. The library needs to include this bank account information in certain vouchers and with other accounts payable activity.

Banking info should include fields for Bank name, bank account number, transit/routing number, bank address, account type and notes

Proposed solution/stories

Links to additional info

https://folio-org.atlassian.net/wiki/x/uxVU

Questions


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