Bank Accounting
FI / FICOintermediate

FICO Bank Accounting Part 2: House Bank Setup, Account Determination and Posting Integration

Key takeaway

Configure bank accounting: house banks and bank accounts (S/4HANA bank account management), GL accounts with open item management, links to the payment program and bank determination, and how incoming and outgoing postings find their clearing accounts.

Explanation

📌 KEY POINTS
✅ House banks and house bank accounts are defined per company code; in S/4HANA bank accounts are managed as master data (bank account management).

✅ Each house bank account links to a main GL account; clearing accounts are determined by payment method or posting rules.

✅ Bank GL accounts use currency, open item management (clearing accounts) and line item display.

✅ FBZP bank determination uses house banks for outgoing payments.

⚠️ Bank account master data changes need approval workflows — they are sensitive.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 explained the concept. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. HOUSE BANK

  • Bank key, house bank ID.

━━━━━━━━━━━━━━━━━━━━
▶ 2. BANK ACCOUNTS

  • Account ID, currency, IBAN, GL account (bank account management).

━━━━━━━━━━━━━━━━━━━━
▶ 3. GL ACCOUNTS

  • Main and clearing accounts; open item on clearing; field status.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PAYMENT INTEGRATION

  • Bank determination ranking; payment method → clearing account.

━━━━━━━━━━━━━━━━━━━━
▶ 5. INCOMING POSTINGS

  • Posting rules and account symbols for statements (Part 3).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Define house bank and account.
  2. Create GL accounts (main + clearing).
  3. Add to FBZP bank determination.

✅ CHECKPOINT: a test payment picks the correct bank and clearing account.

Code example

ABAP Code
===== CONFIG MAP =====House bank ............ FI12 (S/4: FI12_HBANK) | Bank accounts: Fiori "Manage Bank Accounts"GL accounts ........... FS00: 113100 main (no open item), 113101/113102 clearing (open item ✔)Payment integration ... FBZP bank determination: ranking order, bank accounts, available amountsStatement posting ..... Posting rules / account symbols (Part 3)

Real project scenario

A company added a new bank account but forgot FBZP bank determination. Payment runs kept using the old bank, which had insufficient funds. A bank-onboarding checklist (house bank, GL, FBZP, statement mapping) prevented repeats.

Common mistakes

  • No open item on clearing.
  • Missing FBZP updates.
  • No approval on bank master.
  • Inconsistent naming.
  • Forgetting statement mapping.

Best practices

  • Onboarding checklist.
  • Open item on clearing.
  • Approval workflow.
  • Naming conventions.
  • Test payments.

Interview angle

Questions: "How do you configure a house bank?", "How are clearing accounts determined?", "What is bank account management?"
Strong answer: house bank and accounts, GL design, payment integration, statement mapping, controls.

Practice this lesson

Quick check

1. In SAP's Bank Account Management (BAM) functionality, which object serves as the central master record combining bank details, account details, currency, and authorization information for one specific account?

2. Which attribute should typically be activated on a bank interim/clearing G/L account to allow open items posted from payments to be matched and cleared against incoming bank statement line items?

3. In classic House Bank configuration (pre-Bank Account Management), which combination of keys uniquely identifies a specific bank account for a company code?

Interview questions

1. How would you apply Bank Accounting in a real SAP project? Walk through the design or implementation approach.

Answer it in your own words first, then compare.

2. What are the most important design decisions, trade-offs, and best practices in Bank Accounting?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics