0% found this document useful (0 votes)
298 views38 pages

SAP - Electronic Bank Statement

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
298 views38 pages

SAP - Electronic Bank Statement

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 38

SAP – Electronic Bank statement - We have to upload the EBRS into SAP system then based on this

entry SAP will pass the entry as per below:

Outgoing payment clearing A/C Dr

Main Bank A/C


Note -- The main bank account balance should always be equal to your bank account balance.

Last one entry will be posted automatically once actual payment made to Vendor.
SWIFT MT940 - File Format

Field 20 is for statement date.

Field 25 is the account number. ( HB )

28C – Statement no.

60F – Opening Balance -Equal to main bank account - 100 USD

61 – Transaction 1 (Value and booking date, Curr, amount, BTC ( bus. trans code ), client and bank).
USD 10

86 – Transaction 1 addition details (Transaction code, Code description, from/to, other)

61 – Transaction 2 (Value and booking date, Curr, amount, SWIFT code, client and bank) – USD 10

86 – Transaction 2 details (Transaction code, Code description, from/to, other)

62F – Closing Balance – 80 USD

Statement format

20:20190702

20 : Identifier tag for statement

20190702 – YYYYMMDD

25:100000222

25: Account identifier tag

100000222 – Bank Account no.

:28C:100/1

28C – Statement No. tag

100/1 – 100 is statement no. 1 is additional no.

Opening balance format

60F:C190207INR1000.

60F – Identifier tag for Opening balance


C – Credit (Inflow). D – Debit (Outflow).

190207 – YYMMDD – Date of op. balance

INR – Curr. code

1000 – Op. bal. amt

61:1902070207C20000.00 NTRF123456789//977813662

61 – Transaction tag

190207 – YYMMDD -Posting date

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,

20000 – Transaction amount with comma decimal

NTRF – Transaction code , First code must be N, S or F. NCHK – Check payment, NCHG – bank charges.

123456789 – Client ref. no. Cheque no. or payment ref .no.

//977813662 – bank reference no.

:86: CUST-301303RTGS12345678 – Additional information about above one transaction

Note—For 61 and 86., Put together one transaction will be passed.

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.

011 – Check clearing.

015 – Assignment no.

020- Document no.

021 – Reference Doc no.

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.

011 - Check payment clearing


Once APP payment made to vendor then we will pass the below entry for check payment too
Vendor A/C Dr
Outgoing payment clearing A/C
End-user will go to FCH5 and create the manual check and it will reflect in PAYR Table

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

015 – Assignment no.

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.

Outgoing payment clearing A/C Dr.


Main Bank A/C

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

GL code GL Name Open item Mgt. B/S/ P&L


1 HDFC Bank A/C No B/S
4 BRS-Out GL Yes B/S
5 BRS-IN GL Yes B/S
2005 Bank charges A/C No P/L
2. BRS Out
BRS In
Bank charges
2. Create House Bank

Go to FI12 and create the HB

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

Go to OT83  Select the CoA

Click on New entries and create the account symbol against below GL codes.

GL code GL Name Account symbol

1 HDFC Bank A/C Z100


4 BRS-Out GL Z200
5 BRS-IN GL Z300
2005 Bank charges A/C Z400

Click on Assign accounts to account symbol

Assign the GL code against account symbol.


Create the Keys for posting rules which are the entries hitting main bank A/C.
Posting rules Description
Z100 Customer A/C Cr to HDFC Main A/C
Z200 Clear outgoing bank A/C Dr to HDFC Main A/C
Z400 Bank Charges A/C Dr to HDFC Main A/C

Click on new entries and update the posting rules and text for the below and save.

Click on define posting rules and click on new entries

Note – System will check the open item in customer related table and pick the same and pass the below
clearing entry.

Z100 - Customer receipt

A/C symbol PK P. Type on. Acc

Main Bank A/C – Z100 Dr 40 -- --

Customer A/C 50 8 15

Update the above one into posting rules and save


Z200 - Customer receipt

A/C symbol PK P. Type on. Acc

Main Bank A/C – Z100 Cr 50 4 --

Outgoing bank clearing A/C – Z200 40 -- --

Update the above one into posting rules and save.


Z400 - Customer receipt

A/C symbol PK P. Type on. Acc

Main Bank A/C – Z100 Cr 50 4 --

Bank charges A/C – Z400 40 -- --

Create Transaction type  Select MT940 and click on Assign external transaction.
Click on new entry and update the below details

Ex. Tr +/- sign Posting value Interpretation Algorithm

NTRF + Z100 021 – Ref. Doc. no.

NTRF - Z200 020 – Doc. No.

NCHG - Z400 00- No Interpretation

Go to assign bank account to transaction

Click on new entry

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).

Prepare the MT940 test file in the below format


Go to FF_5 to upload the BRS

Update the below details and select the BRS file which is going to upload.

Save as variant and F8 to execute


Getting this error RFEKA400: Error when converting date

Go to SE38 to delete the file

Update the below prog. RFEBKA96 and F8

Update the 0001 and execute it

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

Go to SM35 and post through batch process.


 Select the uploaded file  Click on process  select the display error and process.

On Account posting

Prepare a file with doc. no. mismatch

Here actual doc. no. 2016104 but it was wrongly updated as 2016103 in the BRS

Upload the same file in FF_5.


We can see one more entry has been created. However, no clearing happened here since doc. no.
mismatch b/s BRS and clearing doc.

Go to SE16N and update the table of FEBEP – We will get the uploaded information here.

Update the below details and F8


We got the on account posting details

Go to Tcode FEBAN and update the below details and F8.


We will get all the details which are the details uploaded by us

Green – Posted and clearing successfully.

Yellow – Posted but not cleared

For check payment

Go to OT83 and change the Algorithm for check payment

Create the check lot


Go to F110 and below option

Update the below details

Provide the below details to create the check


We have to make the check payment in F110 or F-53 then go to FCH5

Update the below details


Update the below details and save.
Go to SE16N and update PAYR and check the details of check payment

We will create the new text file to upload the check payment.

Upload the file in FF_5


We have successfully posted the check transaction

Post processing testing – FEBAN

Prepare the upload file


Go to FF_5 and upload the same file

This file was not posted so go to FEBAN

Update the below details and check


We can see the below details

Green – Posted and clearing successfully

Yellow - Posted and but not cleared

Red – Not even posted

Click on red and Other display


Select the not posted item and click on post
Actual doc. no. is 301303 but wrongly mentioned as 90000151 so system did not post the same.

Mention the correct doc. no. is 301303 and click on process open item.
Simulate and post

Error msg no. changes as green


How to check the uploaded document

Go to FF_6

Update the below details and F8

We will get the uploaded doc. details over here

You might also like