SAP Bank Accounting in S/4HANA: House Banks, Statements, and Fiori Apps

Book: Financial Accounting in SAP S/4HANA Finance Simplified: Questions & Answers by Narayanan Veeriah | ISBN 978-93-65898-675

Chapter 18 is a full chapter on bank accounting (questions 561 through 579). Not a sub-ledger like AR or AP. FI-BL is a sub-application for bank master data, payment processing, and reconciling what your bank says happened with what SAP recorded.

What bank accounting handles

Bank accounting covers:

• Bank directory and master data
• House banks and partner bank details
• Bank chains for international payments
• Check and bill of exchange management
• Electronic and manual bank statements
• Lockbox processing (US)
• Cash journal
• Orbian payment system
• Country-specific payment media and forms

Everything from Chapter 16’s payment program lands here on the bank side. House bank setup, statement import, reconciliation.

Bank directory and house banks

The bank directory (table BNKA) stores all bank master data: your house banks and business partner banks. Create via FI01, during customer/vendor master maintenance, or import:

• Country-specific: BAUP from central banking ASCII files
• International: BIC2 from BIC Database Plus

Display with S_P99_41000166.

House banks need a 5-character ID, country key, and bank key (domestic bank number or SWIFT for foreign). Multiple accounts per house bank (Chek1, Pybl1) each link to a G/L account with house bank ID and account ID embedded in the master.

Partner bank details live on the Payment Transactions tab in business partner general data. Country + bank key links to bank directory. Payment program and forms pull address and routing info from here.

SWIFT vs IBAN

SWIFT (8 or 11 characters) identifies the bank branch for international routing. Example: DABADKKKXXX for Danske Bank Copenhagen. Does not include beneficiary account number.

IBAN (up to 34 characters) identifies the specific account. Format: country code (DK) + check digits (06) + BBAN (bank code + account number). Denmark example: DK0630003996056694. Used in Europe and most of the world. US and Canada recognize IBAN for inbound transfers but do not issue them domestically.

Rule of thumb from the book: SWIFT finds the branch. IBAN finds the exact account.

Check rules and bank chains

Country-specific check rules (OY17) validate bank number, bank key, and account number formats. Length, numeric vs alphanumeric, gap tolerance, and special checks (postal account in Germany, Belgian account algorithms, etc.).

Bank chains (multi-stage payment methods) route payments through up to three intermediary banks. General bank chains (FIBB) work without partner-specific bank details. Scenario-based optimization picks the best chain from house bank, recipient bank, currency, and payment method. Only applies to payment methods configured for bank chain processing.

Manual and electronic bank statements

Manual bank statement (FF67): enter line items, then post. Two postings per line item possible: bank account posting and sub-ledger posting with clearing. Customizing via OT84 (posting keys/rules), OT52 (business transactions), OT43 (variants).

Electronic bank statement (EBS): import files in SWIFT MT940, MultiCash, BAI, or other formats. Post-process unmatched items with FEBA_BANK_STATEMENT. Six global customizing steps via OT83: account symbols, assign accounts, posting rule keys, posting rules, transaction types, assign bank accounts to transaction types.

EBS supports automatic and manual post-processing, payment advice integration, and memo record transfer from cash management.

Lockbox, cash journal, and Orbian

Lockbox (US only): customers mail checks to a PO box your bank collects daily. Bank sends electronic statements. Post to lockbox clearing account, apply to AR open items. Residual amounts post via FLB1.

Cash journal (FBCJ): single-screen petty cash management. Opening/closing balances, receipts, payments calculated automatically. Multiple journals per company code, one per currency typically. Different currencies need different G/L accounts. Post to G/L, customer, or vendor accounts.

Orbian Payment System: alternative to traditional bank transfers. Uses Orbian Credit (OC) and Primary Orbian Credit (PMC). Buyers pay with target-duration credit (e.g. 90 days). Suppliers convert OC to cash early at discount or hold for future use. Unlocks supply chain locked cash.

Fiori apps for bank accounting

Notable apps from the chapter:

• Approve Bank Payments v2: review, approve, reject, defer payment batches
• Bank Account Change Requests: two-person verification for bank account changes
• Bank Statement Monitor: 14-day overview, missing pages, balance mismatches
• Make Bank Transfers: inter-account transfers with payment requests
• Manage Banks / In-House Bank Accounts: master data, mass create via upload
• Import Bank Directories: compare and merge bank master updates (SAP GUI via Fiori launchpad)
• Manage In-House Bank Limits: lower limit alerts at account or group level

My read on this chapter

Bank accounting often gets treated as an afterthought in implementations. This chapter makes clear it is not optional. Payment program output (Chapter 16) and bank statement input (Chapter 18) are two halves of the same cash management story. Get house banks, EBS posting rules, and check rules right early. Fixing reconciliation after go-live is painful.

Previous: AR/AP Advanced Part 2 | Next: Asset Accounting Part 1