Purpose: 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.

User story statement(s):

As a staff member who manages vendors
I want to store banking information with the organization
so that I can effectively interact with the accounts payable system

Scenarios:

Scenarios are described in the corresponding UI ticket:  

Acceptance criterias:

• new banking_information schema is created with fields described in the corresponding UI ticket:  

• new table banking_information is created with foreign field organizationId

• BankingInformationAPI is created to cover CRUD operations on this new table