Electronic Bank Statement Import and Automatic Posting Interface
Short answer: A custom interface program that reads the account movements banks deliver in different formats (MT940, CAMT.053, bank XML or an Excel export) every day, writes them into the SAP electronic bank statement tables, finds the customer, vendor or G/L account from the counterparty IBAN and text rules, and triggers the standard posting step. Unmatched movements land on the postprocessing list.
- Estimated effort
- M · 7–10 working days
- System
- ECC and S/4HANA
- Tables
- 9
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
FF_5 imports statements from defined formats such as MT940, but a bank's own XML, web service or Excel export has to be converted first. Standard search strings find patterns in the note to payee, but finding the customer or vendor from the counterparty IBAN, splitting one movement across several invoices or posting bank charges and similar fees to a separate account needs extra rules. The custom program converts all formats in one place, applies a rule table and keeps the standard posting and postprocessing (FEBAN).
Who uses it? Accounting teams doing bank reconciliation, treasury teams and SAP FI consultants managing bank integrations.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| FEBKOElectronic Bank Statement Headers | Statement header: house bank, account, statement number and date; duplicate check | Read / write | ECC + S/4 |
| FEBEPElectronic Bank Statement Line Items | Statement items: value date, amount, external and internal transaction code | Write | ECC + S/4 |
| FEBREReference Records for Electronic Bank Statement Line Items | Note to payee lines of the items | Write | ECC + S/4 |
| FEBCLClearing Data for Electronic Bank Statement Line Items | Account type, account and clearing selection found by the rule table | Write | ECC + S/4 |
| T012KHouse Bank Accounts | House bank accounts and their G/L account | Read | ECC + S/4 |
| TIBANIBAN Numbers | From the counterparty IBAN to bank account details | Read | ECC + S/4 |
| KNBKCustomer Bank Details | Customer bank accounts: finding the customer from the IBAN | Read | ECC + S/4 |
| LFBKVendor Master: Bank Details | Vendor bank accounts: finding the vendor from the IBAN | Read | ECC + S/4 |
| BSIDCustomer Open Items | Customer open items to match against incoming payments | Read | ECC + S/4 |
S/4HANA notes
- T012K: In S/4HANA reads of T012K go through the compatibility view V_T012K_BAM; bank accounts are maintained in Bank Account Management (BAM).
- BSID → I_OperationalAcctgDocItem: In S/4HANA BSID is no longer filled as a separate index table; reads work through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
BAPIs and functions used
- SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Emails the run summary to the accounting team
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_HBKID | House bank | Range / multiple | FEBKO-HBKID | No | AKB01 |
| S_HKTID | Account ID | Range / multiple | FEBKO-HKTID | No | TRY01 |
| R_SRC | Source: file folder or bank service | Radio button | — | No | Dosya klasörü |
| P_FILE | File path (for a single file) | Single value | — | No | /interface/bank/in/ |
| P_POST | Start the posting step after import | Checkbox | — | No | X |
| P_TEST | Test mode (show without writing to the tables) | Checkbox | — | No | — |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Account IBAN | By rule Mapped to the house bank account in T012K; stored in FEBKO as house bank and account ID | Yes |
| 2 | Value date | FEBEP-VALUT | Yes |
| 3 | Amount (signed) | FEBEP-KWBTR | Yes |
| 4 | Currency | By rule Compared with the account currency; the row is rejected if it differs | Yes |
| 5 | Bank transaction code | FEBEP-VGEXT | No |
| 6 | Description | FEBRE-VWEZW | No |
| 7 | Counterparty IBAN | By rule Looked up in TIBAN, KNBK and LFBK to find the customer or vendor | No |
| 8 | Counterparty name | By rule Used for name matching when no IBAN is found, and shown in the list | No |
Sample upload file
| 1 | Account IBAN * | Value date * | Amount (signed) * | Currency * | Bank transaction code | Description | Counterparty IBAN | Counterparty name |
|---|---|---|---|---|---|---|---|---|
| 2 | TR12 0006 4000 0011 2345 6789 01 | 11/16/2026 | 125,400 | TRY | NTRF | Payment of invoice 2026-004512 | TR55 0001 0009 8765 4321 0000 11 | Örnek Tekstil A.Ş. |
| 3 | TR12 0006 4000 0011 2345 6789 01 | 11/16/2026 | -86,250 | TRY | NTRF | November rent payment | TR77 0004 6000 1122 3344 5566 77 | Demo Gayrimenkul Ltd. |
| 4 | TR12 0006 4000 0011 2345 6789 01 | 11/16/2026 | -42.50 | TRY | NCHG | Transfer fee |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Statement no. | FEBKO-AZNUM |
| 2 | Item | FEBEP-ESNUM |
| 3 | Value date | FEBEP-VALUT |
| 4 | Amount | FEBEP-KWBTR |
| 5 | Counterparty | Calculated Counterparty name from the file |
| 6 | Account found | FEBCL-AGKON |
| 7 | Rule applied | Calculated IBAN, invoice reference, fixed pattern or no match |
| 8 | Accounting document | FEBEP-BELNR |
| 9 | Status | Calculated Posted and cleared, posted, left for postprocessing or error |
Sample result list
| Statement no. | Item | Value date | Amount | Counterparty | Account found | Rule applied | Accounting document | Status |
|---|---|---|---|---|---|---|---|---|
| 00317 | 1 | 11/16/2026 | 125,400 | Örnek Tekstil A.Ş. | 300145 | Invoice reference | 1400008812 | Posted and cleared |
| 00317 | 2 | 11/16/2026 | -86,250 | Demo Gayrimenkul Ltd. | 200388 | IBAN | 1500004410 | Posted |
| 00317 | 3 | 11/16/2026 | -42.50 | 780100 | Fixed pattern | 1500004411 | Posted | |
| 00317 | 4 | 11/16/2026 | 18,700 | Mavi Ev Ürünleri Ltd. | No match | Left for postprocessing |
How does the program work?
- A source is defined for each bank account (file folder, SFTP or bank web service), and a reader class converts that bank’s format into one common structure.
- The house bank and account ID are found in T012K and T012; a statement that arrives twice is rejected by checking its number and date in FEBKO.
- A rule table is applied to each movement in order: the counterparty IBAN is looked up in TIBAN, KNBK and LFBK; if nothing is found, the invoice or reference number in the text is matched against open items in BSID; patterns for bank charges, interest and taxes are routed to fixed G/L accounts.
- The header is written to FEBKO, the items to FEBEP, the note to payee lines to FEBRE and the clearing information found to FEBCL; each item gets an internal transaction code.
- If P_POST is set, the standard bank statement posting step is started; matched items are posted and open items cleared, unmatched ones stay in FEBAN for postprocessing.
- A run summary (movements received, posted and left for postprocessing, with amounts) is listed and sent by email.
Performance notes
Daily movements rarely exceed a few hundred. For BSID matching, only open items in the movement's company code and within the amount tolerance are read. The job can be scheduled several times a day.
Features
- Runs as a background job Runs automatically at planned intervals during the day.
- Test mode (check without posting)
- Line-by-line result and error log
- Send the result by email The run summary and errors are sent by email.
Authorization objects
- F_FEBB_BUKAuthorization to import and process bank statements for the company code
- F_BKPF_BUKPosting authorization for the bank statement entries
Frequently asked questions
Can it connect to the bank's web service directly?
Yes. The reader layer depends on the source; movements can be fetched from a file folder, SFTP or the bank's API. Connection and certificate settings are managed through SAP's standard communication settings.
What if one receipt pays several invoices?
If the text contains several invoice numbers, all of them are written to FEBCL as clearing selections, and the item is cleared in one posting when the total matches. If it does not match, the item is left for postprocessing.
Can it be used on S/4HANA?
Yes. The bank statement tables and postprocessing are the same on S/4HANA, and the Fiori bank statement apps show the same data.
Related reports
Unmatched Bank Statement Items on Clearing Accounts Report
A custom ALV report that lists electronic or manual bank statement items that were never posted, or were posted to a bank clearing account and are …
Daily Central Bank Exchange Rate Import Interface
A custom interface program that reads the daily exchange rates published by the central bank over the internet and writes them into the SAP rate table …
Mass Open Item Clearing Upload from Excel (Customer, Vendor, G/L)
A custom program that clears open items grouped in an Excel file on customer, vendor or G/L accounts in bulk. Each group becomes one clearing …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.