SAP - Electronic Bank Statement
SAP - Electronic Bank Statement
Last one entry will be posted automatically once actual payment made to Vendor.
SWIFT MT940 - File Format
61 – Transaction 1 (Value and booking date, Curr, amount, BTC ( bus. trans code ), client and bank).
USD 10
61 – Transaction 2 (Value and booking date, Curr, amount, SWIFT code, client and bank) – USD 10
Statement format
20:20190702
20190702 – YYYYMMDD
25:100000222
:28C:100/1
60F:C190207INR1000.
61:1902070207C20000.00 NTRF123456789//977813662
61 – Transaction tag
0207 – Entry date (Optional) System will consider this as Doc. Date.
C – Credit ba. ( Receive from cus ) l, D- Debit bal ( Vendor payment or bank charges ), RC – Reversal of
Credit, RD – Reversal of Debit,
NTRF – Transaction code , First code must be N, S or F. NCHK – Check payment, NCHG – bank charges.
If customer paid amount to us, then customer will give the invoice details here and we can pass the
entry accordingly.
Algorithm
Bank outgoing payment Clearing b/w vendor debit and actual payment made.
No need to any customization in SAP for this clearing, it is all already pre-defined in SAP.
000 – No interpretation
Interpretation algorithms are used to identify open items that you wish to clear after receiving a bank
statement. To do that, they use data which is on the bank statement to compare them with the open items
in the system. In most cases, the interpretation algorithms analyze and interpret data from the note to
payee of the bank statement items. Here you can see a list of some interpretation algorithms and an
explanation to how they function.
Once actual payment made, how system will identify and clear the next one below entry.
System will match the Check no. which available in payment doc. no. and table PAYR and same check
no. will be available in bank statement also then system will the match both the check no. and pass the
below clearing doc. No.
Outgoing payment clearing A/C Dr.
Main Bank A/C
Assignment no. will be available in the below entry in SAP and will be reflected in Table of PAYR.
Vendor A/C Dr
Outgoing payment clearing A/C
same Assignment no. will be available in bank statement also then system will the match both the
Assignment no and pass the below clearing doc. No.
020- Document no. (Tech no. BELNR) and 021 – Reference Doc no. (Tech no. XBLNR).
Customer will mention the doc. no. and inv. Ref. no. in the note while making payment to us then same
will be reflected in 86 – additional information on the BS and based on this system will pick this and clear
the entry.
Note – We have to update the a above no. ranges during custom
000 – No interpretation
1. Create GL accounts
Go to FS00 and create the GL codes for the below
As we don’t have any Fiori access so we can’t create the bank account.
We have to create the account no. along with Account ID and assign the bank GL code.
Create Account symbol – OT83
Click on New entries and create the account symbol against below GL codes.
Click on new entries and update the posting rules and text for the below and save.
Note – System will check the open item in customer related table and pick the same and pass the below
clearing entry.
Customer A/C 50 8 15
Create Transaction type Select MT940 and click on Assign external transaction.
Click on new entry and update the below details
Once we have done the above config. Then we will receive the Bank statement from bank in MT940 file
format (India and EUR ), BI240 (US).
Update the below details and select the BRS file which is going to upload.
We will get the list of files, delete the file and upload this correct format.
Create one more test file as per below
Upload the same through FF_5 -- > Click on batch input and F8
On Account posting
Here actual doc. no. 2016104 but it was wrongly updated as 2016103 in the BRS
Go to SE16N and update the table of FEBEP – We will get the uploaded information here.
We will create the new text file to upload the check payment.
Mention the correct doc. no. is 301303 and click on process open item.
Simulate and post
Go to FF_6