Professional Documents
Culture Documents
Electronic Bank Statement - CAMT 054 Format
Electronic Bank Statement - CAMT 054 Format
054 format
Most of the articles on EBS talk about step by step configuration guide. They talk about
concepts & end to end process very rarely. I hope we all agree that step by step
configuration guide is quite easy to follow, but the main challenge is to understand the
concept. If we understand the concept, it becomes easier for us to implement the
process in live systems. In this blog, I have tried to explain how the EBS process works
in SAP. At least I found it hard to implement when I started working on EBS in my
project. I wish my blog makes EBS process easy to my SAP colleagues across the
globe.
What is EBS?
Electronic Bank Statement is provided to the account holders in standard formats, e.g.
CAMT, MT940, BAI2 etc. As a part of Payment Transaction processing, EBS can be
imported and posted in SAP for reconciliation.
SAP has already provided a transformation for this file format. So, SAP program can
automatically transform the file content and load it in SAP tables. But yes, for that we
need to complete basic EBS settings. If you want to review how the file will look like
after transformation, follow the below steps.
Step 1:
Execute the following node in SPRO and check if the transformation exists for CAMT
054. It should be there.
Step 2:
Go to transaction STRANS and enter the transformation
FIEB_CAMT054_V2_TO_FEB
There are mainly 4 tables that holds EBS information – FEBKO, FEBEP, FEBRE &
FEBCL
2. After importing the bank data from the XML, the program first transforms the bank
data into SAP format (XSLT transformation)
3. Based on the Bank account in the file, program finds out the transaction types, in our
case it is 19CMT054
4. Program then interprets the bank data based on External Transaction types in the
bank statement and interpretation algorithm set up in the configuration.
External transaction types are used in bank statement to notify what kind of transaction
it is. It is a common identifier between the bank and the target system. In SAP, we will
have to configure all possible external transaction types for the bank statement format,
in our case it is CAMT 054. Some example transaction types are <54>353 used for
withdrawal, <54>664 used for deposits.
Interpretation Algorithm:
Interpretation algorithm defines how the note to payee information from the bank
statement will be interpreted. Refer to the below link for more details.
https://help.sap.com/saphelp_46c/helpdata/en/43/0bd56743de11d1896f0000e8322d00/
content.htm?no_cache=...
You can use standard interpretation algorithm or create your own. Refer to the SAP
note: 2032814 for the instruction on how to create Z interpretation algorithm.
5. Based on the Posting rules (Z022 & Z023) defined for each bank transaction type the
bank items are matched with the company data.
Posting rules:
Posting rules will decide what to do with the incoming EBS transaction. Posting rules
are assigned with the External transaction types. Choose + or – depending on whether
the transaction increases (+) (deposit) or decreases (-) (withdrawal) the bank account
balance.
6. There are 2 posting areas that we can post to while EBS processing in SAP.
In our example, we have used only posting area 1. That means only 1 accounting
posting will happen in Bank Accounting for each external transaction type. Refer to
accounting entry 3 & 6 below. Please note that SWISHMAIN & SWISHCLEARING are
just account symbols. The GLs have already been assigned with the account symbols.
If we choose Posting Area 2, another account posting will happen, that will clear the sub
ledger directly. Refer to entry 2 & 5 below. This configuration will look like below.
Posting type must be chosen correctly. The following posting types are available and
needs to be assigned with the Posting rules.
Posting type 8 - Clear cred.subl.acct has been used for sub ledger clearing.
If both Posting Area 1 and 2 is chosen, 2 postings will happen for each external
transaction type. First one will clear the Bank Accounting and the second one will clear
the sub ledger.
1. Vendor Invoice
Dr GR/IR Account
2. Payment to Vendor
Accounts Receivables –
4. Customer Invoice
Cr Revenue Account
6. Post EBS
External Transaction type can be seen in the BTC - Business Transaction Code column.
Here BTC is <54>. Payment notes can be interpreted by Interpretation Algorithm.
Bank Statements can be reprinted using FF_6.
KUKEY is the statement ID found on the top right of the bank statements
FEBEP - Electronic Bank Statement Line Items
External Transaction Keys are stored in VGEXT field. In our case, VGEXT = <54>-353
& <54>-664
FEBCL holds the clearing information related to the processed EBS. In our case, we are
using Assignment number (ZUONR) for clearing. The field SELVON is populated from
the Payment Notes column in the bank statement. This table information can be
customized using Z interpretation algorithm.
FEBRE - Reference record for electronic bank statement line item
Data in the VWEZW field will match with the Payment Notes information in the Bank
Statement.
Run the report RFEBKA96 with Application as 0001 & bank statement IDs. In our case,
it is 150 & 153.
Customizations in EBS upload:
SAP PI/PO or any middleware can get the CAMT 054 files from bank SFTP
folder and upload in designated folder in AL11. The folder can be configured in
SPRO.
3 logical paths to be configured for the Inbound files, Processed and Errored
files.
Above logical paths to be set up in the Define Import Parameter step