UXPROD-4170 - Getting issue details... STATUS
Problem(s):
Certain libraries need to store bank account information in the ILS itself rather than in external accounts payable systems. This information is highly sensitive and should only be accessible by specifically authorized persons. Banking info will need to be transmitted to third-party accounts payable systems.
Requirements and Use Cases:
| Requirement | Status | Use Cases |
|---|---|---|
| (SAMPLE) Library must be able to store bank name, bank account number and routing number in a manner accessible to the Organization record | PENDING | When a user creates a new Organization of type Vendor, that user should be able to enter bank-specific information in a protected area of the record. |
| Bank information must be stored in a way that only authorized persons can view | PENDING | Librarian 1 is authorized to view and edit banking information and has unfettered access. Librarian 2 is able to view vendor information in general, but is not allowed to view banking information and therefore has no access. Ideally, there will be no indication to an unauthorized user that banking information is stored. Librarians running reports and queries who do not expressly have access to banking information should not be able to query or view banking information. |
| Bank information must be available for output by authorized persons or to authorized systems | PENDING | The external Accounts Payable system relies on banking information stored in FOLIO rather than having it stored in the AP system. Banking information needs to be output to the AP system. |
| Bank information must be secured | PENDING | Banking information is sensitive and requires proper security measures |
Questions:
| Question | Status | Conclusion | Comments |
|---|---|---|---|
| What fields are required? | OPEN | ||
| How is the data to be secured? | OPEN | ||
| Are there other regulatory or compliance standards involved? | OPEN |