SAP FI Bank Accounting

You are an SAP FI (Financial Accounting) specialist configuring bank master data, electronic bank statement processing, and automated bank reconciliation in SAP ERP.

What to check first

• Run transaction OBD4 to verify your company code is properly configured with bank details
• Execute transaction FI12 to check existing bank master records and validate bank key assignments
• Review transaction FBZP to confirm electronic bank statement (EBS) configuration is active for your company code

Steps

1. Create bank master data in transaction FI12 — enter bank country key, bank key, bank name, and SWIFT/BIC code; save and note the bank ID for later reference
2. Configure bank accounts in transaction FI12 — click "Account" tab, enter GL account number (typically 1100 range), currency, and mark "House Bank" checkbox if this is your primary bank
3. Set up electronic bank statement variants in transaction FBZP — select your company code, choose statement format (MT940, OFX, or ISO20022), and assign the appropriate conversion program
4. Create a logical file path in transaction FILE — define RFC destination or local file system path where bank statements will be imported from
5. Configure bank statement processing in transaction OBA7 — link your bank master to the statement import program, set field mapping rules, and define statement line item tolerance amounts
6. Test import by uploading a sample bank statement file using transaction FF.5 (EBICS configuration) or FF_5 (file upload); verify statement appears in FF.5 with status "received"
7. Set up automatic matching rules in transaction OBA9 — define matching algorithms for open items against incoming statement lines using amount, date, reference field, and document type criteria
8. Create reconciliation profiles in transaction OBH3 — configure posting logic for automatically cleared items, configure tolerance accounts, and set posting date rules
9. Execute bank reconciliation in transaction FF.8 — select company code, bank, account, and statement date; review unmatched items and manually assign remaining differences using transaction FF.9

Code

*&---------------------------------------------------------------------*
*& Report: Bank Statement Import and Reconciliation Setup
*&---------------------------------------------------------------------*
REPORT z_bank_reconciliation_config.

DATA: lt_banks TYPE TABLE OF bnka,
      lt_accounts TYPE TABLE OF bnkc,
      ls_bank TYPE bnka,
      ls_account TYPE bnkc,
      lv_company TYPE bukrs,
      lv_bank_id TYPE bankl,
      lv_account TYPE konto,
      lv_swift TYPE swift,
      lv_result TYPE sy-subrc.

PARAMETERS: p_bukrs TYPE bukrs DEFAULT '1000',
            p_bank_key TYPE bankl,
            p_account TYPE konto.

START-OF-SELECTION.

  " Step 1: Check existing bank master records
  SELECT * FROM bnka INTO TABLE lt_banks
    WHERE land1 = 'US

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change