FI / FICOadvanced

FICO Bank Accounting Part 3: Electronic Bank Statement and Reconciliation

Key takeaway

Automate bank reconciliation: statement formats (MT940, CAMT. 053), transaction types, account symbols and posting rules, interpretation algorithms for clearing, post-processing of unmatched items, and daily reconciliation between bank and GL.

Explanation

📌 KEY POINTS
✅ Account symbols map to GL accounts (main, clearing); posting rules define the postings for each business case.
✅ Transaction types map bank-specific external codes to posting rules and interpretation algorithms.
✅ Postings run in two areas: GL (bank accounting) and sub-ledger (customer/supplier clearing).
✅ Unmatched lines are post-processed; the aim is a daily, fully reconciled bank position.
⚠️ Unknown external codes default to nothing — new bank codes must be mapped or lines fail.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured banks. Now statements.

━━━━━━━━━━━━━━━━━━━━
▶ 1. FORMATS

MT940, CAMT.053 and others; import.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ACCOUNT SYMBOLS AND POSTING RULES

Symbols → GL; rules → posting keys and areas.

━━━━━━━━━━━━━━━━━━━━
▶ 3. TRANSACTION TYPES

External codes → posting rule + algorithm.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MATCHING

Algorithms find document or reference numbers; search strings refine.

━━━━━━━━━━━━━━━━━━━━
▶ 5. RECONCILIATION

Post-process unmatched; review clearing accounts; monitor per bank.

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

Map external codes to posting rules.
Import a statement and review results.
Post-process exceptions.

✅ CHECKPOINT: main bank GL equals statement closing balance.

Code example

ABAP Code

===== CONFIG MAP (SPRO > FI > Bank Accounting > Business Transactions > Payment Transactions > Electronic Bank Statement) =====Create account symbols (e.g. BANK → 113100, OUTGOING → 113101)Create keys for posting rules (e.g. Z001 outgoing payment)Define posting rules (area 1 GL, area 2 sub-ledger)Create transaction type → assign external transaction codes → posting rule + algorithmAssign bank accounts to transaction types ===== RUN =====FF_5 import | FEBAN post-processing | Fiori: Bank Statement Monitor

Real project scenario

A company switched a bank to CAMT.053 format and suddenly many lines failed. The new external transaction codes were not mapped. Adding them to the transaction type and monitoring failures per bank solved it.

Common mistakes

Unmapped external codes.
Weak algorithms.
Duplicate imports.
Late post-processing.
No per-bank monitoring.

Best practices

Map codes per bank.
Tune algorithms.
Guard against duplicates.
Post-process daily.
Monitor match rates.

Interview angle

Questions: "How is EBS configured?", "What are account symbols and posting rules?", "How do you reconcile banks daily?"
Strong answer: formats, symbols/rules, transaction types, algorithms, reconciliation.

Practice this lesson

Quick check

1. Lockbox processing in SAP FI is primarily used to support which business scenario?

2. During Electronic Bank Statement (EBS) processing, which configuration element carries the bank's own proprietary transaction code as delivered in the statement file, and must be mapped to SAP posting logic?

3. After a bank switched to CAMT.053, many statement lines fail. What is the likely fix?

Interview questions

1. Many electronic bank statement lines don't post or don't clear. How do you troubleshoot EBS?

Answer it in your own words first, then compare.

2. A production issue is reported in Bank Accounting. What would you check first, and how would you troubleshoot it systematically?