Electronic Account Statement (FI-BL)

1 Electronic Account Statement (FI-BL) Account Statement (FI-BL) SAP AG2 April 2001 Copyright Copyright 2001 SAP AG. All rights part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software , WINDOWS , NT , EXCEL , Word , PowerPoint and SQL Server are registeredtrademarks ofMicrosoft , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 , AIX , S/390 ,AS/400 , OS/390 , and OS/400 are registered trademarks of IBM is a registered trademark of ORACLE -OnLine for SAP and Informix Dynamic ServerTM are registered trademarks ofInformix Software , X/Open , OSF/1 , and Motif are registered trademarks of the Open , DHTML, XML, XHTML are trademarks or registered trademarks of W3C , World WideWeb Consortium.

2 Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, Logo and trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies. SAP AGElectronic Account Statement (FI-BL)April 20013 IconsIconMeaningCautionExampleNoteRecomm endationSyntaxElectronic Account Statement (FI-BL) SAP AG4 April 2001 ContentsElectronic Account Statement (FI-BL).

3 6 Electronic Account Statement : Customizing .. 7 Central Terms .. 8 External Transactions .. 9 Posting Rules .. 10 Transaction 11 Posting Specifications and Account Determination .. 12 Example 1: Posting Check 13 Example 2: Posting Transfer Debit Memos .. 14 Example 3: Posting Charges .. 15 Account Symbols and Account Assignment .. 16 Assigning G/L Accounts to Account 17 Assignments for Foreign Currency 18 Account Assignment Using Function 19 Recommended Sequence of Configuration Tasks .. 20 Creating Transaction Types ..21 Assigning 22 Creating Keys for Posting Rules .. 23 Assigning External 24 Defining Posting Rules .. 25 Electronic Account Statement Implementation 26 How Does Automatic Posting Work? .. 28 Information in the Electronic Account 29 Electronic Account Statement : Posting and 30 Using the Electronic Account 31 Importing the Account 32 Interpreting the Note to Payee Fields.

4 33 String Search for Document 34 Interpretation 37 Executing the 41 File 42 Posting Parameters .. 43 Cash 44 Algorithms .. 45 Output 46 Displaying Account Statements .. 47 Postprocessing Account Statements .. 48 Postprocessing Electronic Account Statements .. 49 Account 50 Posting Parameters (Postprocessing) .. 51 Postprocessing Account Statements with Batch Input 52 Conversion 53 Functional Enhancements For The Electronic Account 54 Formats for the Electronic Account 55 SAP AGElectronic Account Statement (FI-BL)April 20015 Receiving Account Statements Using EDI .. 57 Electronic Account Statement : Glossary of Terms .. 60 Electronic Account Statement (FI-BL) SAP AGElectronic Account Statement (FI-BL)6 April 2001 Electronic Account Statement (FI-BL)In many countries today, Account Statement data can be electronically retrieved from banks.

5 InGermany, this information is accessed using the bank communication standard (BCS) of thebanks. For example, MultiCash retrieves the desired data (for example, Account statements) fromthe banks and generates two files from the bank data for further processing: file contains the header information on the Account Statement . file contains the line items. These files can be imported into the SAP R/3 Systemwhere they are then automatically processed. To do this, you run the program that imports thefiles generated by MultiCash into the system or, more specifically, into the bank data conversion, data in these files is supplied with SAP-specific information, such as the chartof accounts and company code, for further processing. After the import transaction is completed,the data in the bank data memory is analyzed.

6 The system tries to identify the individual businesstransactions and filter out the information necessary for posting, for example document numbers,from the note to payee fields on the Account Statement (interpretation of the note to payee).If the necessary information can be interpreted, the system will automatically post thetransactions (using batch input or a call transaction). All line items are usually postedautomatically. Statistics show that up to 95% of customer data can be posted automatically in the SAP R/3 System. The system offers convenient tools for further processing of line items that are may occur during the posting of incoming payments in the accountsreceivable area. Some customer invoices may not be completely cleared or banktransactions may have been made with incorrect references.

7 In these situations, youwill have to use the postprocessing function to post the following topics explain the processing steps of the Electronic Account Statement , such ashow data is imported, posted, displayed, and subject to further processing. You can also findimportant information on the note to payee fields, how to start the program, and how to configureit. Customizing for the Electronic Account Statement is also explained in more detail. SAP AGElectronic Account Statement (FI-BL) Electronic Account Statement : CustomizingApril 20017 Electronic Account Statement : CustomizingBy making configuration settings in Customizing, you ensure that all business transactions ofwhich your bank informs you using the Electronic Account Statement are posted correctly in following topics contain the information you require to configure the Electronic for the Electronic Account Statement are made in Customizing for Bank Accounting For more information on the steps involved, refer to the online documentation for this node andthe steps for making specifications for the Electronic Account Statement in the Account Statement (FI-BL) SAP AGCentral Terms8 April 2001 Central TermsThe following topics explain the terms that you need to understand when configuring theelectronic Account Statement .

8 SAP AGElectronic Account Statement (FI-BL)External TransactionsApril 20019 External TransactionsExternal transactions (also known as business transaction codes) are bank-specific codes forbusiness transactions, each of which involves a different type of payment. The external transaction code is issued by banks in the Electronic Account Statement . The SAPR/3 System requires this code in order to identify the business transaction. It converts the bank-defined codes into its own system-internal transaction codes (known as posting rules), which inturn trigger certain specific posting transactions in the of bank-defined external transactions are:- 020 Transfer order- 051 Transfer credit memo- 052 Recurring entry credit memo- 072 Bill of exchange presentation- 206 Foreign bank transferFor more information, see Posting Rules [Page 10].

9 Electronic Account Statement (FI-BL) SAP AGPosting Rules10 April 2001 Posting RulesAs part of the configuration of the Electronic Account Statement , external transactions must beassigned to a posting rule. The system uses the posting rules to determine which bank orsubledger accounts to post the transactions rules are represented in the system by a non-bank-specific code (for example, 0001 fordebit memos).Why do you require an internal code that is related to the posting rule in order to configure theelectronic Account Statement ? Why is each posting rule not directly linked to an externaltransaction?Banks have many different transactions, several of which may require just a single posting inyour : Transaction code 004 denotes a direct debit by debit memo Transaction code 005 denotes a collection authorization by debit memo Transaction code 020 denotes a transfer order by debit memoThese three external transactions all require the same posting in your accounts.

10 They musttherefore all be assigned to the same posting rule (for example, 001 for debit memos). Thisposting rules tells the system how to post a debit memo. Using internal codes (posting rules) when configuring the Electronic Account Statement has theadvantage that you only need to determine how a transaction (for example, debit memo) isposted once and not three times (as in the example above).See also Posting Specifications and Account Determination [Page 12]. SAP AGElectronic Account Statement (FI-BL)Transaction TypesApril 200111 Transaction TypesYou define transaction types in order to group together banks with the same external transactioncodes (for example, all banks of the same type). The advantage of this method is that you do not have to assign the external transaction codes ofthe banks (business transaction codes) to internal R/3 posting rules for every individual bank butrather can make this assignment just once per transaction type.