Professional Documents
Culture Documents
SAP Bank Interface
SAP Bank Interface
There is not much difference between the functionality and configuration of MBS and
EBS. So that in order to understand how EBS functionality works in SAP we first start
with MBS.
Manual bank statement – It is a document sent by the bank which gives details of the transactions done by
the account holder. This statement is used in SAP to clear bank main and clearing accounts and to do
reconciliation of SAP bank accounts with banks.
Configuration of House Bank: First we have to create a House bank and its bank
accounts. Configuration steps of House Bank are given in the document of lockbox.
Within the IMG, the user needs to follow the menu path below to access the Manual
Bank Statement configuration.
Here we create a transaction and assign the same with posting rules created in next step.
Using the transaction you determine how and to which accounts the system is to post the
payment.
SPRO->Financial Accounting (New) ->Bank Accounting->Business Transaction->Payment Transaction-
>Manual Bank Statement->Define Posting Keys and Rules.
In this Customizing activity, user can make basic settings for the account statement. There are four
steps to be carried out. Brief description of these steps is:
In this step you create the account symbols that you later need for defining the posting specifications.
Before the posting rule is used, the account symbols are replaced with the relevant accounts to which
posting is to be made.
Specify G/L accounts (such as bank, cash receipt, outgoing checks) to which postings are to be made from
account statement. You assign account symbols to the G/L account numbers. These are required for the
posting rules.
Activities
1. Define an ID for each account symbol.
2. Enter a description in the text field.
In this step you define the account determination procedure for each individual account symbol.
Define postings to be triggered by possible transactions in the account statement (such as bank transfer,
Incoming Payment, Outgoing payment). In the posting specifications that you define here, use the account
symbols from step 1, not the G/L account numbers. This prevents similar posting rules being defined
several times, the only difference between them being the accounts to which postings are made.
To avoid having to define a separate account symbol for every single house bank account (with a different
G/L account in each case), the G/L account field can contain a masked output. The masking is done using +
+++++ for the main bank account. For the sub accounts all the other digits are masked except the last one.
For Bank charges the actual gl account is entered.
Note that masked entries (using +) are always based on a ten character account number. If you are using a
shorter account number (six characters, for example), the entry must be right-aligned.
Further examples how a user can assign a G/L account to each of the account symbols
created (Not configured in above screen). The G/L account may contain the entire G/L
account, a partial mapping of the G/L account, or a generic mapping of the G/L account.
SAP provides the functionality of creating a wildcard search value when using the plus
sign “+” character. See below the available means to map the G/L account to the account
symbol.
• The user may assign the G/L account to the entire G/L account.
• The user may assign the account symbol to a partial mapping of the G/L account.
(If the number is entered partially generic, SAP replaces the plus signs “+” with
the G/L account number contained in the House bank, but the non-generic portion
remains within the value. For example: mapping G/L account +++++++++1 will
replace the final with “1”)
Account symbol G/L account
US_CH DEPOSITED +++++++++1
SAP provides the functionality to make postings in foreign currencies. The user may
create a mapping that designates a specific foreign currency to be used with an account
symbol (e.g., EUR, GBP, USD, etc.).
SAP also provides the capability of creating a wildcard “+” for a specific account symbol
such that all currencies are available.
With the help of this field, you can direct the posting to a differentiate bank
subaccount instead of a standard one.Leave this field blank (or enter the mask
"+") if you do not want to use an account modification.
In this step we are creating the posting rules which we need to assign the external transaction code. Assign
posting rules to possible transactions in account statement file. A list of assignments where one external
transaction code is assigned to one posting rule is called a transaction type.
Activities
1. Define an ID for each account symbol.
2. Enter a description in the text field.
Step 4. Define posting rules.
The user needs to define each posting rule for how the transaction shall post as a journal
into the General Ledger. The user needs to provide the following information when
creating the posting rule.
• Posting rule
• Posting area
o 1 – Bank accounting
o 2 – Sub-ledger accounting
• Pkey (D) – posting key for debit posting
o 40 – debit entry
o Blank value designate G/L, customer, or vendor account posting
• DCInd (D) – special G/L indicator for debit posting to customer or vendor account
• Acct (debit) – account symbol for debit posting
• Comp (D) – account determination: indicator for compression (NOT OFTEN
USED): Indicator that the line items are to be compressed automatically before
posting.
• Pkey (C) – posting key for credit posting
o 50 – credit entry
o Blank value designate G/L, customer, or vendor account posting
• DCInd (C) – special G/L indicator for credit posting to customer or vendor
account
• Acct (credit) – account symbol for credit posting
• Comp (C) – account determination: indicator for compression (NOT OFTEN
USED): Indicator that the line items are to be compressed automatically before
posting.
• PstTy – bank statement posting type (see below for more detail)
• Doc. Type – bank statement document type
o PstTy – bank statement posting type
• OA pst key – posting key for posting on account when clearing posting fails
• Reason – reason for reversal
The bank statement posting type is required to determine how the posting rule should
post as a journal within SAP. SAP uses the value to identify if the transaction posts
directly to G/L account, posts directly to sub-ledger account, posts with clearing to G/L
account, or posts with clearing to sub-ledger account.
1. Bank Income
FF67
2. Bank Expense
Now we can also change the above con fig and post bank expense account to separate
expense GL account.
3. Customer Payment
Bank Statement
It says that debit main bank account and credit bank sub clearing account with clear
credit GL account. So it means that our bank sub clearing account should be cleared
automatically by system.
4. Similarly we can configure for vendor payments
Posted an Invoice
MultiCash format is created from the bank’s account statement data, usually in
SWIFT MT940 format. The format consists of two files in format AUSZUG.TXT
and UMSATZ.TXT. The AUSZUG.TXT contains the header information for the
bank account statement while UMSATZ.TXT contains the line item information.
This format allows the customer to import data from several account statements at
the same time.
SAP provides the means to convert the data from both file formats into a structure that
may be used for further processing of the data. Reason for the bank statement upload
functionality existing is for automatically posting the line item activity directly into the
General Ledger. The configuration steps required to post the information from the
electronic bank statement into the General Leger is shown below.
The user needs to access SAP Implementation Guide for R/3 Customizing (IMG) using
transaction SPRO.
Within the IMG, the user needs to follow the menu path below to access the Electronic
Bank Statement configuration.
The user needs to identify the Chart of Accounts that should be referenced within the
Electronic Bank Statement configuration. Then the user may click on the “Continue”
button.
In this Customizing activity, user can make basic settings for the account statement. There are seven
steps to be carried out for EBS. Out of these seven first four is already configured in MBS:
The user needs to create the transaction types and description as shown below. A
transaction type should exist for a conglomeration of banks that have similar External
Transaction Types. The External Transaction Types are the external transactions that are
sent from the bank referencing the type of activity occurring for a specific transaction.
SWIFT codes are some basic external transactions that appear within the bank statement.
Step 6: Assign External Transaction codes.
SAP requires the external transactions be created and assigned to posting rules for each
transaction type. To create the external transactions for a transaction type, the user needs
to select a specific transaction type. Then the user needs to double click within the Dialog
Structure the line “Assign external transaction types to posting rules”.
SAP provides the means to create and assign an external transaction type based upon the
transaction type, the movement of the transaction, the posting rule, and an interpretation
algorithm for posting the transaction.
Interpretation Algorithm
It uses information in note to payee field of EBS to search matching tranacations in sap.
If any open items are there in the system will post the subsequent entries based on the Algorithm.
If you select 00: No algorithm, use custom algorithm that developed through user exists.
If you select 01: Standard algorithm the system will identify the open items and post the subsequent
payments based on the Document number or Reference number.
If you select 11: System interpret contents of note to payee field as check number you sent and find correct
document number from check number. It assumes that check number is different from sap document
number. System will search based on document number or reference document number.
If you select 19: System search DME information in note to payee field to find correct document in SAP.
If you select 20: Same as 11 except: Document number the system will identify the open items and post the
subsequent payments based on the Document number only (Customer Invoice).
If you select 21: Same as 11 except: Reference document number the system will identify the open items
and post the subsequent payments based on the Reference document number only.
The user needs to assign the bank account to the Transaction type. SAP provides the
functionality to assign a bank key and bank account to a specific Transaction type. SAP
uses the specified Transaction type for processing the bank statement postings for that
bank account.
Upload of EBS input File: Below is the example of sample EBS. It is just to demonstrate brief structure of
Input file, how it uploaded in SAP and other related steps. So the configuration of EBS shown above does
not match with the configuration according to which below file is demonstrated.
Click on
To view cleared documents
After uploading Electronic Bank Statement data through Transaction Code FF_5, documents will
automatically posted into the Main Bank Account & also it clears the Sub ledgers open items as
shown below. Go to Transaction Code FBL3N.
Now, Bank Sub ledger amounts are transfer to Main Bank account
Checking of bank Statement (Transaction Code: - FF67)
Click on