Skip to content 
SAP Electronic Bank Statement BAI2 Configuration Checklist
Electronic Bank Statement setup connects bank files, cash posting, clearing, exception handling, and reconciliation. A BAI2 file can import successfully and still fail during posting if transaction codes, posting rules, account symbols, or search strings are incomplete.
Use this checklist before configuration review, user testing, and go-live.
Before You Start
- Collect the bank’s BAI2 implementation guide and sample statement file.
- Confirm company code, house bank, account ID, bank key, account number, currency, and GL assignment.
- List bank transaction codes for deposits, wires, ACH, checks, fees, interest, and transfers.
- Define which transactions should post automatically and which should remain for review.
- Confirm import method, file naming, statement date, and statement number rules.
Core Configuration Checklist
House Bank And Account Mapping
- House bank and account ID match the bank statement account.
- Bank account is assigned to the correct company code and GL account.
- Inactive or test accounts are not included in production processing.
- Opening and closing balances can be reconciled after import.
External Transaction Codes
- Every BAI2 transaction code has a mapped posting rule or documented manual process.
- Debit and credit versions are reviewed separately when the bank uses different meanings.
- Bank fee, interest, wire, ACH, check, and transfer codes are tested with realistic examples.
Posting Rules And Account Symbols
- Posting rules create the expected debit and credit accounting entries.
- Account symbols point to the correct main bank, clearing, fee, interest, and suspense accounts.
- Subledger clearing is used only where references are reliable enough for automatic matching.
- Each posting rule has a matching test case and expected accounting result.
Search Strings And Clearing Logic
- Invoice numbers, customer references, check numbers, payment document numbers, ACH traces, and wire references are reviewed.
- Search strings are used where important data appears in bank memo text.
- Special characters, long memo text, and missing references are tested.
Testing Checklist
- Import one clean BAI2 file.
- Import a file with multiple accounts, if applicable.
- Post incoming payments, outgoing payments, bank fees, interest, and transfers.
- Confirm open-item clearing where expected.
- Confirm unmatched items remain available for exception handling.
- Confirm duplicate statement prevention.
- Validate GL postings against expected accounting.
Common Issues
| Issue | What To Check |
|---|---|
| File imports but does not post | External transaction code mapping and posting rule assignment |
| Wrong GL account posts | Account symbol and company-code account determination |
| Open items do not clear | Interpretation algorithm, search strings, memo text, and references |
| Bank fees post incorrectly | BAI2 fee code and assigned posting rule |
Go-Live Controls
- Bank account list is approved.
- All expected transaction codes are mapped or documented.
- Finance approves the accounting entries.
- Exception ownership is clear.
- First production import is monitored by finance and SAP support.
Frequently Asked Questions
Is BAI2 the only Electronic Bank Statement format?
No. BAI2 is common in the United States, but companies may also use MT940, CAMT, or bank-specific formats. The same review logic applies.
Why does EBS import but not clear open items?
SAP usually needs a reliable reference in the bank file. Review memo text, invoice references, check numbers, payment document numbers, and search strings.
Learn The Full Configuration
For a hands-on walkthrough of Electronic Bank Statement configuration, posting rules, search strings, and testing, see the AUMTECH course:
SAP Electronic Bank Statements
Related resources:
