In SAP, users need to maintain a unique Bank Account Identifier for each house bank. This identifier represents the specific bank account that the company holds with the respective house bank. It encompasses essential information such as the bank account number, currency key, and various country-specific data.

In the SAP system, each bank account is uniquely identified within a company code. This structure allows for clear segregation and management of multiple bank accounts across different legal entities within an organization. For each bank account, users are required to maintain detailed information including the bank key, bank country, addresses, and other relevant data. The SAP system leverages this information to accurately identify and link to the correct bank master data, ensuring precise financial transactions and reporting.

The flowchart provided in the image illustrates the key steps of maintaining house banks and bank accounts in SAP. It involves manual preparation and approval, followed by the creation or modification of house bank and bank account IDs in the system. The process concludes with a decision on whether to use the bank account in payment runs, which may require additional configuration.

Below is a breakdown of process steps for flowchart image:

1. Manual Preparation and Approval:
   • This initial step involves completing a manual form for maintaining existing house banks/bank accounts or creating new ones.
   • For new house banks/bank accounts, new general ledger accounts (bank statement account and bank clearing accounts) are identified and created during this step.
2. Maintain House Bank ID (FI11): SAP transaction FI11 is used to create a new House Bank if required.
3. Maintain Bank Account ID (FI11 / FI12):
   • SAP transaction FI11 is used to create a new Bank Account.
   • SAP transaction FI12 is used to amend an existing Bank Account.
4. Decision: Use in Payment Run?:
   • If the new bank account is required for the Accounts Payable payment run, additional configuration is needed.
   • If not required for payment runs, no further configuration is necessary.
5. Auto Payment Run Configuration (FBZP) (if required):
   • If the bank account is to be used in payment runs, additional configuration is required for bank determination and existing payment methods.
   • This is done using SAP transaction FBZP.