Setting up the Electronic Bank Statement Q1: Does Electronic Bank Statement show transactions at customer or bank point

of view? + means debit from bank point of view, but credit from client point of view. How can I distinguish incoming and outgoing payments? A: Bank statement in format SWIFT MT940 shows transactions from the bank point of view. It means D is companys outgoing payment and C is incoming payment. SAP automatically understands direction of money movement and transforms them from D/C into +/-. Anyway, test run of real bank statement is the best indicator if settings are correct or not. Q2: I got full documentation for the statement in format SWIFT MT940. It has huge list of possible transactions. Do I need to configure all of them in Electronic Bank Statement? How can I do it? A: It worth asking your colleagues (like treasury and accountants) which of those transactions do actually exist in statements. Sure, not all of them will be in use. The same people will also tell you how to post each transaction in General Ledge. Then we set up these transactions as external transactions and group them into internal transaction codes where possible. Q3: Transaction code in SWIFT MT940 statement is very high-level. For example, TRF (NTRF) can be incoming or outgoing payment. Dont even mention smaller details. You cant say more using the field 61. And it is field 61 which maps to posting rule. Some banks like Credit Suisse can give more details in tructured field 86. 86. But system recognizes the transaction type using the field 61. How can I ask it to look into field 86??

A: Transaction FF.5 has choice of variants for upload: with field 86 structured and unstructured. Of course, you have to configure transaction types as they are in field 86 if you use structured statement. As for NTRF transaction type for incoming and outgoing payments, they can be split by direction of money movement. If bank uses NTRF, say, for outgoing payments and bank commissions, you cannot do much here, unfortunately. You have to do it manually. Or try to use search strings to replace the transaction type. Q4: How can I split domestic and international payments if they go under the same transaction type in bank statement?

A : As a rule, all the payments use the same transaction type in the bank statement. It does not matter if the payment is domestic or international. That is why you cannot distinguish them in the statement. It is different in Russia, where all domestic payments are in roubles and international payments are in foreign currency, except for loans and deposits. Things are easier in this case. Q5: Is it good idea to use special document type for the bank statement postings? Or document type SA is good enough?

A: It is very good idea to use special document type. Of course, document type SA will suite the first posting area. But I would recommend to use document types KZ/DZ for the second posting area, or even introduce special document type for bank statement. Q6: Our chart of accounts has account number with less that 10 symbols. How should I specify mask for the account symbol in bank statement configuration? Should it be left justified or right justified? ++++++++++ ++++++++ ++++++++

A: SAP always adds zeros on the left of numeric account number up to 10 characters. That is why you have to put the mask for all 10 characters. http://help.sap.com/saphelp_erp60_sp/helpdata/en/43/0bd49743de11d1896f0000e8322d00/ frameset.htm This help document has an example where account has 6 characters, but mask has 10 pluses. Q7: When I configure the bank statement, I can put + for the currency. Do I need to create separate GL accounts for each currency?

A: If you need to create different masks for different currencies, then put each currency separately. Usually bank account is single-currency. That is why + is enough. http://help.sap.com/saphelp_erp60_sp/helpdata/en/43/0bd4a443de11d1896f0000e8322d00/ frameset.htm Q8: What is Interpretation Algorithm? A: Interpretation algorithm is a link between data in bank statement and data in SAP system. For example, interpretation algorithm can find paid items using payment order number or cheque number. You can see list and details of the most available algorithms in SAP Note 114713. Q9: I put posting type = 8 (open item clearing) in the posting rule of the EBS. There are no open items in the system when I run a test. And I cannot post a payment now. What should I do if I get a down payment from customer? Which other posting type should I use for the subledger? It is unclear what to do with subledger postings. Even if I put customer number in the manual bank statement, posting only goes to General Leder. A: Posting rule can have posting type without clearing. I.e. just a customer posting. Try to use it. Or you can leave incoming payments unposted in the bank statement. Leave this task to treasury/accountants. Of course, it depends on the number of payments like this. Q10: When I try to post to subledger, Payment advice is created. What should I do with it? What is Payment Advice?

A: If I correctly understand, Payment Advice is created for Cash Management. There is no use of it unless you implement Cash management. You can switch Payment Advices in the parameters of manual bank statement entry. Transaction FF67, Settings Specifications. If it does not help, have a look at SAP Note 452579 (older SAP versions - 162571). Q11: How can I delete bank statement?

A: Use program RFEBKA96. This program deletes bank statement itself, but not the posted documents. Thats why I would recommend using this program in test systems only; and being very careful. Q12: What else can I read about the bank statement? A: Have a look at SAP Note 549277. Q13: Where do I define interpretation algorithms? A: Interpretation algorithms are defined in program RFEBBU10.

Configuration of Electronic Bank Statement (EBS) for MT940

This article explains how to configure EBS (Electronic Bank Statement) in SAP for MT940 bank statement format. The SAP MT940 format consists of a sequence of fields defined as follows:

Define MT 940 transaction code. Following table shows MT 940 transaction codes which have been defined by bank officer and business user previously. Some more transaction code could be applied in SAP EBS configuration. It is better to include Debit / Credit identification during definition.

Define bank transactions. Before configure EBS, we have to know several of daily bank transactions. This information usually is coming from business user who take care bank reconciliation. For example: 1. 2. 3. 4. Bank Incoming Bank Outgoing Bank Charges Bank Interest

For each bank transaction should follow with which GL account for posting.

Make Global Settings for Electronic Bank Statement

IMG Financial Accounting Bank Accounting Business Transactions Payment Transactions Electronic Bank Statement Make Global Settings for Electronic Bank Statement Enter Chart of Accounts press enter Configuration steps are follow: 1. Create account symbols. Specify G/L accounts (such as bank, cash receipt, outgoing checks) to which postings are to be made from account statement. You create account symbols instead of G/L account numbers. These are required for the posting rules in step 2 Examples: Bank Account; Outgoing checks; Incoming checks; Outgoing Transfers; Incoming transfers; Bank charges etc. Enter a description in the text field

2. Assign accounts to account symbols. Double click on Assign accounts to accounts symbol and click on new entries.

We have not assigned charges accounts, because we should ascertain from the business, to which GL account the charges are to be posted. This step has to be performed again for charges. Bank charges account is hard coded because this account is commonly debited for charges debited by all house banks. 3. Create keys for posting rules. Double click on Create keys for posting rules field and click on NEW ENTRIES 1. Define an ID for each posting rule. 2. Enter a description in the text field. Update the information as follows.

Click on save 4. Define posting rules. Double click on Define posting rules and click on New Entries In this activity you create posting specifications for each posting rule. You use the posting specifications to specify how a certain business transaction (such as a check issued) is to be posted. Posting specifications consist of one or two posting records Debit and Credit

5. Create Transaction type. Double click on Create transaction type. Here we create the names and descriptions of the various transaction types we require. House banks that use identical lists of business transaction codes (external transactions) can be assigned to the same transaction type later. Click on NEW ENTRIES and enter the required transaction types Create the names and descriptions of the various transaction types you require. In the present business scenario we go for MT940 and we require creating this transaction type here.

6. Assign external transaction type to posting rules. Double click on Assign external transaction types to posting rules and click on new entries. Here we assign the external transaction type of banks to our posting rules. Bank Transaction Type (samples)

Banks generally have their own codes for various transactions. For example Mashreq bank is issuing statements with the following transaction codes

We need to have clarity from business on which transaction type should post with clearing or post only. NCHK denotes check transaction and prefixed with D for debit (out going) and C for credit (incoming). Hence we need to create two variations while mapping these transaction types to our posting rules (one for Debit and the other for Credit). From the point of view of business use, the external business transactions listed above use identical posting procedures and must therefore be assigned to the same posting rule. The same posting rules can also be used for different bank details, even if different business transaction codes are used (if different file formats are used, for example). Note: Update the algorithm for bank transaction type which needs to be posted with clearing in EBS transaction. 7. Assign Bank Accounts to Transaction types. Double click on assign bank accounts to transaction types and click on new entries. Here we assign each of the bank accounts to a transaction type. You can specify a work list of G/L accounts. This enables you to search several bank sub accounts for open items that the system could not clear during posting of the account statement when you post process the account statement.

If you select the field No Automatic Clearing, an open item remains, even if the amount of the open item agrees with that in the account statement. We assign our banks to a transaction type and, if required, to a currency class. The banks are identified by means of the bank key and the external account number.

Note: This transaction type MT940 shall be added to the bank accounts 8. Search string definition When importing an electronic bank statement, the system identifies the business transactions and uses the settings you have already made to determine how each should be recorded. In most cases, the system uses the document number entered in the note to payee lines of the bank statement to determine the appropriate clearing transaction. For example, a cash receipt clears customer open items. The information in the note to payee may be incomplete for example, the first characters in the document number may be cut off or new characters may be added. The interpretation algorithm then reaches the limits and cannot find the appropriate document numbers. This means the document cannot be cleared and you must post- process the transactions manually. In addition to the search for clearing information, you can use the the search string to fill other fields (such as the cost center or posting rule, depending on the content of the note to payee. It is the Target Field which determined which field is filled in each case. The target field in the bank data store indicates to where the result of the search is written. The target field must always be the note to payee when you are searching for clearing information (document number, reference document number. (Unlike other fields, it is not necessary to repeatedly change the note to payee field the information in it is temporarily enriched while the interpretation algorithm is running.) The explanations and examples that follow all refer to the search for clearing information (meaning that the note to payee is the target field), but they can also be applied to most other fields (such as Cost Center; see the section on Other Target Fields).

To increase the number of hits in the document number search, you can use this step to define strings for the search. The system uses this string to conduct the search before the interpretation algorithm comes into effect.

Note: Please check length of cheque number for each company code which use EBS functionality. It may different with 7 digits length as configured above. 9. Assign Search String to Interpretation Algorithm Go back and double click in the tree Note-to-payee search string Choose New entries. Enter the company code, house bank, account, interpretation algorithm, and a name for the string. If you leave all or one of the fields Company code, House bank, or Account , the system uses the specified search string to search in all company codes, house banks, and/or accounts. If you want to use the string in the document number search, select Active and Note to Payee as the target field. Enter a mapping basis if required. Select the ID indicator if required.

10. User exit This exit will remove original note to payee of bank file with TRANSACTION TYPE and CHEQUE NUMBER as new note to payee. Example: Original MT940 file recognize NONREF as note to payee value for both line :20:0000000000511286 :25:0493134965

:28C:175/1 :60F:C100608AED341400,35 :61:100103C499601,350NCHK0000431268 :61:100103D158201,000NCHK0000008760 :62F:C100608AED682800,70 After run this exit, new note to payee become NCHK0000431268 for first line and NCHK0000008760 for second line. 11. Default Cost Center for Bank Charges Maintain OKB9 per company code. //NONREF //NONREF

Step-by-Step Procedure for Customizing an Electronic Bank Reconciliation Statement To set up Electronic Bank Statements (EBS) Processing in SAP for most customers in North America. 1. Create House Bank and Account ID (FI12) 2. Setup EDI Partner Profile for FINSTA Message Type (WE20) 3. Configure Global Settings for EBS (IMG) - Create Account Symbols - Assign Accounts to Account Symbols - Create Keys for Posting Rules - Define Posting Rules - Create Transaction Types - Assign External Transaction Types to Posting Rules - Assign Bank Accounts to Transaction Types 4. Define Search String for EBS (Optional) - Search String Definition - Search String Use 5. Define Program and Variant Selection Additional information is also available in the SAP Library under: Financial Accounting > Bank Accounting (FI-BL) > Electronic Bank Statement > Electronic Account Statement Customizing.

Bank Reconciliation Statement The following are the steps for BRS: Create Bank Master Data - This can be created through T.Code FI01 or you can also create the house bank through IMG/FA/Bank accounting/Bank account 2. Define House Bank 3. Set up Bank selection payment programme- IMG/FA/ARAP/BT/AUTOIP/PM/Bank selection for payment prg. a. setup all co codes for payment transaction - Customer and vendors b.setup paying co codes for payment transactions c.setup payment method per country d.setup payment method per co code for payment transaction e.setup bank determination for payment transaction Please go for Cheque mangement using T code FCHI (IMG/FA/ARAP/BT/OP/AutoOp/PaymentMedia/CheckManagement) and for void reasons FCHV. You can create Bank Reconcilliation statement by TC FF67 (SAP/AC/Treasury/CashManagement/Incomings/ManualBankStatement) . Don't forget to keep the opening Balance as zero. Use FEBA for post process. All the steps together will lead to (FF67) Bank reconciliation statement.

http://scn.sap.com/thread/1794922

MT 940 format for EBS

This question has been Answered. Ratnam V Sep 28, 2010 1:41 PM Hello, Could any one share MT 940 format sample for doing Electronic bank statement, I have done Electronic bank reco configuration and format is not available, How is MT 940 format looks like? Thanks in advance for your help Regards, Ratnam. Helpful Answers by Srikanth Boddupalli, Henri LOISEAU, Henri LOISEAU 3469 Views Average User Rating (0 ratings) Re: MT 940 format for EBS

Ratnam V Sep 29, 2010 9:35 AM (in response to Ratnam V) Hello Experts, I have received file from bank in MT 940 format, the file is in Excel format, do we need to convert into text format before going to upload in T-code: FF_5? Can any one explain how to proceed with uploading and process for electronic bank statement. Thanks, Ratnam. o o Helpful AnswerRe: MT 940 format for EBS
Report Abuse Like (0)

Srikanth Boddupalli Sep 29, 2010 11:19 AM (in response to Ratnam V) Hello Ratnam, I am not sure whether Excel file can be uploaded but better you can go with notepad file for uploading. And if you really want to test whether your configurations are

correctly placed. YOu can do so by using program RFEBKATX it will create open items and simulataneously multi cash file format is available for you to test the same. Do not worry even if it is a multi cash format it helps you in finding whether your configuration is correct or not. Coming to upload of MT940 format. Go to FF_5 select import data button and give file format as S if it structured file otherwise I if it is unstructure. Then upload the file in the field statement file. IN the posting parameters you can select either post immediately or do not post. Also give the algorithms for identifying the open items. If you are not posting directly. Then once after upload you need to goto FEBAN transaction for doing the postings. Regards Srikanth Re: MT 940 format for EBS
Report Abuse Like (0)

Ravichandran Iyer Sep 29, 2010 1:23 PM (in response to Ratnam V) MT940 will normally be a text file with specialized indicators for each line and value. Trysearching the internet and you'll get the format specifications. You can also get the specifications from the SWIFT website. As told above, you'd use FF.5 or FF_5 to upload the statement where you'll select the indicator to identify your format (I or S). You'd use FEBA to post if you have not selected posting in FF_5 and later use F.13 to clear the Bank entries. Ravi. Re: MT 940 format for EBS
Report Abuse Like (0)

Ratnam V Oct 1, 2010 6:24 AM (in response to Ravichandran Iyer) Hi, Thanks for reply! I have receive two files from bank one is header file and having Bank account number, ID and opening balance and closing balance. Another one is having line item details (statement file), When I entered T-code: FF_5 and selected Statement file and line item file for upload.

Selected Import data check box Elect. bank Statement format : S SWIT MT940 with field 86 structured Statement file: Line Item file: (If select both files, error message is triggering like "Line item file field can only be used with MultiCash format") Please let me know which file need to be upload here because one is having 6 lines data like header data details and another is having entire transactions statement. IF select only Statement file: Error message like u201CTermination in statement no. 00256 of ac 006106027099 ; closing record 62F missingu201D papering Work station upload check box Generate Batch input radio button Assign value date check box and the output control check boxes selected are below Print Bank statement, Print posting log, Print statistics Separate list then executed. Thanks, Ratnam. Re: MT 940 format for EBS
Report Abuse Like (0)

Henri LOISEAU Oct 1, 2010 10:05 AM (in response to Ratnam V) Hi, Multicash format works with 2 files (auszug = header and umsatz = items). MT940 works with a single file. o Report Abuse o Re: MT 940 format message for Electronic Bank statement
Like (0)

Ratnam V Oct 11, 2010 7:29 AM (in response to Henri LOISEAU) Hello,

Now I am able to upload MT940 fomat statement file in the system, but Warning message is appearing while uploading like u201CAccount ICIC0000081 not in the bank data storage Message no. FB770 00510907081 INR: Statement 201000000 is

Diagnosis The previous account statement has not been imported. System Response The system permits the import regardless. Procedure You can deactivate the message for the formats Multicash and MT940: Effects on Customizing You can define when this system message is to be issued in accordance with your requirements. You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control. The application area and message number can be taken from the technical documentation.u201D Please suggest how to define message in system. Thanks, Ratnam Re: MT 940 format for EBS
Report Abuse Like (0)

Henri LOISEAU Oct 11, 2010 8:53 AM (in response to Ratnam V) Hi, I already sent this error to SAP, but the answer was I had to suppress the message. When you receive the first statement of the year (statement 1), you receive a message saying that statement 0 is missing. Obviously there is no statement 0. If you suppress the message, you will have no warning when there is a missing statement during the year (for exemple when receiving statement 54 without receiving statement 53). So suppressing warning messages is not a good solution for me. I suggested to SAP to add a test in the program for not issuing the message at statement 1, but they refused. o Report Abuse o Re: MT 940 format for EBS
Like (0)

Ratnam V Oct 11, 2010 9:37 AM (in response to Henri LOISEAU) Hello Henri, Thanks for reply! I am getting warning message "Account ICIC0000081 Statement 201000000 is not in the bank data storage" 008909017081 INR:

then I click information button above message is showing, Can we upload number of statements at a time in the single statement? or different statements need to upload? How many statements can we upload for day? Thanks, Ratnam Re: MT 940 format for EBS
Report Abuse Like (0)

Ravichandran Iyer Oct 11, 2010 12:05 PM (in response to Ratnam V) You can upload multiple statements in a single file. However, if they are of the same date, all except the last one should be marked as intermediate statements (The closing & opening balance indicators for intermediate statements). Unless you get the statements in that form, SAP will not allow multiple statements for the same account in the same file. Did you download the specifications of MT940 from the swift website? If you go through that file, you'll understand the format and a sample is also available there. In MT940, normally the header and line items are in the same file. If you received both separately, then the format might be of Multicash. Ravi. Helpful AnswerRe: MT 940 format for EBS
Report Abuse Like (0)

Henri LOISEAU Oct 11, 2010 9:59 AM (in response to Ratnam V) Hi, Usually there is only one statement per bank account for each day, but you may have several statements (with different statement numbers) for the same account ans the same date, it is not a problem. You may have several statements in the same file (with different banks, different dates, different accounts...). I think that the sequence in the file has no importance: the program sort the statements internaly (at least in Musticash format; I'm not sure for MT940). In

Multicash format, I had a small problem: when a file contains statements 99 and 100, the program sorts them alphabetically (100 before 99) and there is a warning saying 'statement 100 without 99'; but it's only a warning and the results are OK. I don't know if there is the same problem with MT940 (I switched recently from Multicash to MT940). o Report Abuse o Re: MT 940 format for EBS
Like (0)

Ratnam V Oct 11, 2010 11:00 AM (in response to Henri LOISEAU) Hello Henri, When I upload statement in to system it is not getting uploaded in the system after warning message, I ignored warning message and entered, statement summary and statement is appearing but when I see in FF67 statement over view, no data contains list Thanks in advance! for your promptly reply Thanks, Ratnam Re: MT 940 format for EBS
Report Abuse Like (0)

Henri LOISEAU Oct 11, 2010 11:07 AM (in response to Ratnam V) Hi, FF67 is for manual statements. Please see with transaction FEBA or FEBAN for electronic bank statements. o Report Abuse o Re: MT 940 format for EBS
Like (0)

Ratnam V Oct 11, 2010 12:37 PM (in response to Henri LOISEAU) Hi, I have tried to see in FEBA and FEAN, nothing is displaying below message is like "You have selected either no or several items. To select, double-click on an item at the top (list) or on the left (tree display) of the screen."

I think we can able to see uploaded statements either manual or Electronic statements in FF67. Because I have created one file with 2 entries debit and credit and uploaded in FF_5, it got uploaded and I have seen in FF67 also. But when I am uploading file which I got form bank it is not coming in FF67. Thanks, Ratnam Helpful AnswerRe: MT 940 format for EBS
Report Abuse Like (0)

Henri LOISEAU Oct 11, 2010 2:18 PM (in response to Ratnam V) Hi, you are right for FF67. I don't know why you don't see anything. Please check in table FEBKO with FEBKOEDATE = upload date. o Report Abuse o Re: MT 940 format for EBS
Like (0)

Ratnam V Oct 19, 2010 9:47 AM (in response to Henri LOISEAU) Hello Henri, Thanks for reply, I have uploaded MT940 file successfully and it is appearing in FF67 and FEBA also. Because the file which I got from bank is wrong file one record was missed. For automatic reconciliation I mapped Assignment field in the algorithm but in MT940 file assignment field is coming test instead of cheque number How can we get required field ? Thanks Ratnam Re: MT 940 format for EBS
Report Abuse Like (0)

Ratnam V Nov 25, 2010 7:13 AM (in response to Ratnam V) Thanks for reply. I can able to do EBS now. o
Report Abuse

Like (0)