FI Electronic Bank Statement - Weeblythefico.weebly.com/.../4/9/7/14970654/fi_electronic_bank_statement.pdf · FI Electronic Bank Statement SAP AG Typographic Conventions iv May 1997

SAP® AG ì Neurottstr. 16 ì D-69190 Walldorf

FI Electronic Bank Statement

Release 3 .1®

FI Electronic Bank Statement SAP AG

Copyright

ii May 1997

Copyright

Copyright 1997 SAP AG. All rights reserved.

No part of this documentation may be reproduced or transmitted in any form or for anypurpose without the express permission of SAP AG.

SAP AG further does not warrant the accuracy or completeness of the information, text,graphics, links or other items contained within these materials. SAP AG shall not beliable for any special, indirect, incidental, or consequential damages, including withoutlimitation, lost revenues or lost profits, which may result from the use of these materials.The information in this documentation is subject to change without notice and does notrepresent a commitment on the part of SAP AG in the future.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft®, WINDOWS, NT® ,EXCEL and SQL-Server® are registered trademarksof Microsoft Corporation.

IBM®, OS/2, DB2/6000®, AIX®, OS/400®, AS/400® are a registered trademark ofIBM Corporation.

OSF/Motif is a registered trademark of Open Software Foundation.

ORACLE is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX-OnLine for SAP is a registered trademark of Informix SoftwareIncorporated.

UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.

ADABAS is a registered trademark of Software AG

SAP, R/2®, R/3®, RIVA®, ABAP/4, SAPoffice, SAPmail, SAPaccess®, SAP-EDI, SAP ArchiveLink, SAP EarlyWatch®, SAP Business Workflow, R/3 Retail®are registered trademarks of SAP AG

All rights reserved.

SAP AG FI Electronic Bank Statement

Contents

May 1997 iii

Contents

Chapter 1: Electronic Bank Statement..................................................................... 1–1Electronic Bank Statement .....................................................................................1–3Electronic Bank Statement: Configuration .............................................................. 1–3Core Terms and Their Significance for Configuration ............................................. 1–4External Transaction .............................................................................................. 1–4Posting Rules......................................................................................................... 1–4Transaction Type ................................................................................................... 1–5Posting Specifications and Account Determination................................................. 1–5Account Symbols And Account Allocation .............................................................. 1–8Assigning G/L Accounts to Account Symbols ......................................................... 1–8Account Allocation for Business Transactions in Foreign Currency......................... 1–9Account Allocation Using Function Enhancement: Account Modification .............. 1–10Recommended Sequence of Configuration Tasks................................................ 1–10Creating Transaction Types.................................................................................. 1–11Allocating Banks .................................................................................................. 1–11Creating Keys For Posting Rules.......................................................................... 1–11Allocating External Transactions .......................................................................... 1–12Defining Posting Rules......................................................................................... 1–12How Does The Automatic Posting Function Work?............................................... 1–13Information in the Electronic Bank Statement ....................................................... 1–13Using the Electronic Bank Statement for Postings and Clearing ........................... 1–14Electronic Bank Statement: Usage ....................................................................... 1–15Importing Data ..................................................................................................... 1–15Interpreting the Note to Payee Fields ................................................................... 1–16Output Data ......................................................................................................... 1–18Executing the Program......................................................................................... 1–18Displaying the Overview....................................................................................... 1–22Postprocessing Bank Statements......................................................................... 1–23Postprocessing Bank Statements Using the Transaction...................................... 1–24Postprocessing Bank Statements with Batch Input Sessions................................ 1–25Conversion Programs........................................................................................... 1–26Functional Enhancements For The Electronic Bank Statement ............................ 1–26Formats For The Electronic Bank Statement ........................................................ 1–27


Typographic Conventions

iv May 1997


This type style represents

Interface Text words or characters that appear on the screen. Thisincludes system messages, field names, screen titles,pushbuttons, menu names, and menu options.

Document Title cross-references to other documentation

User Entry exact user entry. These are words and characters thatyou enter exactly as they appear in the documentation.

<Variable User Entry> variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

NAME names of elements in the R/3 System. These includereport names, program names, transaction codes, tablenames, ABAP/4 language elements, file names, anddirectories.

KEY keys on your keyboard. These include function keys(for example, F2) and the ENTER key, among others.

This icon helps you identify

Note a note. Notes contain important information likespecial considerations or exceptions.

Example an example. Examples help clarify concepts orprocedures.

Cautiona caution. Cautions help you avoid errors such as thosethat could lead to data loss.



May 1997 v

SAP AG Electronic Bank Statement

Overview

May 1997 1–1

Chapter 1: Electronic Bank Statement

Overview

The following topics explain the processing steps of the electronic bank statement, suchas how data is imported, entered, processed, posted, and displayed. You can also findimportant information on the note to payee fields, how to start the program, and how toconfigure it.

Contents

Electronic Bank Statement....................................................................................... 1–3

Electronic Bank Statement: Configuration.............................................................. 1–3

Core Terms and Their Significance for Configuration ........................................... 1–4

External Transaction................................................................................................. 1–4

Posting Rules............................................................................................................ 1–4

Transaction Type ...................................................................................................... 1–5

Posting Specifications and Account Determination ............................................... 1–5

Account Symbols And Account Allocation ............................................................. 1–8

Assigning G/L Accounts to Account Symbols........................................................ 1–8

Account Allocation for Business Transactions in Foreign Currency .................... 1–9

Account Allocation Using Function Enhancement: Account Modification ......... 1–10

Recommended Sequence of Configuration Tasks ............................................... 1–10

Creating Transaction Types ................................................................................... 1–11

Allocating Banks..................................................................................................... 1–11

Creating Keys For Posting Rules........................................................................... 1–11

Allocating External Transactions........................................................................... 1–12

Defining Posting Rules........................................................................................... 1–12

How Does The Automatic Posting Function Work? ............................................. 1–13

Information in the Electronic Bank Statement ...................................................... 1–13

Using the Electronic Bank Statement for Postings and Clearing ........................ 1–14

Electronic Bank Statement: Usage ........................................................................ 1–15

Importing Data ........................................................................................................ 1–15

Interpreting the Note to Payee Fields .................................................................... 1–16

Output Data ............................................................................................................. 1–18

Executing the Program........................................................................................... 1–18

Electronic Bank Statement SAP AG

Electronic Bank Statement

1–2 May 1997

Displaying the Overview......................................................................................... 1–22

Postprocessing Bank Statements.......................................................................... 1–23

Postprocessing Bank Statements Using the Transaction.................................... 1–24

Postprocessing Bank Statements with Batch Input Sessions............................. 1–25

Conversion Programs............................................................................................. 1–26

Functional Enhancements For The Electronic Bank Statement .......................... 1–26

Formats For The Electronic Bank Statement ........................................................ 1–27


Electronic Bank Statement

May 1997 1–3

Electronic Bank StatementIn many countries today, bank statement data can be electronically retrieved from banks.In Germany, this information is accessed using the bank communication standard (BCS)of the banks. To transmit data from bank to customer, a transfer program (for example,MultiCash) that recognizes BCS is necessary. For example, MultiCash retrieves thedesired data (for example, bank statements) from the banks and generates two files fromthe bank data for further processing:

– UMSATZ.TXT– AUSZUG.TXT

The AUSZUG.TXT file contains the header information on the bank statement. TheUMSATZ.TXT file contains the line items. These files can be imported into the SAPSystem where they are then automatically processed. To do this, you run the programthat imports the files generated by MultiCash into the SAP System or, more specific, intothe bank data memory.

During conversion, data in these files is supplied with SAP-specific information, such asthe chart of accounts and company code, for further processing. After the importtransaction is completed, the data in the bank data memory is analyzed. The system triesto identify the individual business transactions and filter out the information necessaryfor posting, for example document numbers, from the note to payee fields on the bankstatement (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 SAPSystem. The SAP System offers comfortable tools to subsequently process line items thatare not posted.

Note

Problems 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. In these situations, youwill have to use the postprocessing function to post the items.

Electronic Bank Statement: ConfigurationBy making configuration settings, you ensure that all business transactions of which yourbank informs you via the electronic bank statement are posted correctly in the system.

The following topics contain the information you require to be able to configure theelectronic statement.

You access the configuration functions for the electronic bank statement via the “Cashmanagement” node in the Implementation Guide.


Core Terms and Their Significance for Configuration

1–4 May 1997

For more information on the steps involved, refer to the online documentation for thisnode and the steps for making specifications for the electronic bank statement in theIMG.

Core Terms and Their Significance for ConfigurationThe following topics explain the terms that you will encounter and need to understandwhen configuring the electronic bank statement.

External TransactionExternal transactions (also known as business transaction codes) are bank-specific codesfor business transactions, each of which involves a different type of payment. Theexternal transaction code is issued by banks in the electronic bank statement. The SAPsystem requires this code in order to identify the business transaction. It converts thebank-defined codes into its own system-internal transaction codes ( known as postingrules), which in turn trigger certain specific posting transactions in the system.

Examples 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 transfer

For more information on these, refer to Posting Rules.

Posting RulesThe external transactions must be allocated to a posting rule as part of the configurationof the electronic bank statement. The system uses the posting rules to determine whichbank or sub-ledger accounts to post the transactions to.

Each posting rule is represented in the system by a system-set code, such as 0001 fordebit memos.

Why do you require an internal code that is related to the posting rule in order toconfigure the electronic bank statement? Why is each posting rule not directly linked toan external transaction?

Banks have many different transactions, several of which may require just a singleposting in your accounts.

Example:

• 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 memo


Transaction Type

May 1997 1–5

These three external transactions all require the same posting in your accounts. Theymust therefore all be allocated to the same posting rule (for example, 001 for debitmemos). This posting rules tells the system how to post a debit memo. Using internalcodes (posting rules) instead of those defined by the banks when configuring theelectronic bank statement therefore has the advantage that you only need to determinehow a transaction (for example, debit memo) is posted once and not three times (as inthe example above).

For more information, refer to Posting Specifications and Account Determination.

Transaction TypeYou define transaction types in order to group together banks with the same externaltransaction codes (for example, all banks of the same type).

The advantage of this grouping is that you do not have to allocate the external transactioncodes of the banks (business transaction codes) to internal SAP posting rules for everyindividual bank but rather can make this allocation just once per transaction type.

After defining transaction types you must allocate each of your house banks to atransaction type.

Posting Specifications and Account DeterminationWhen you define a posting rule, you must specify how each business transaction that istransmitted to you by electronic account statement (for example, bank transfer) is postedin your system.

When you do this you can specify two sets of posting specifications for each posting rule,one for G/L account postings (or bank-related postings) and one for sub-ledger postings.

Depending on whether this posting rules only requires a posting to a G/L account (orbank account) or also requires a sub-ledger posting, you specify posting specifications foreither one or both of these postings.

Example

For the “check credit memo” transaction you only require posting specifications forthe G/L accounts, since the customer entry is cleared when the check is deposited.However, for a “transfer” transaction, you require posting specifications for both theG/L accounts and the sub-ledger accounts, in order to be able to clear the customerentry.

You enter account symbols rather than the actual account names in postingspecifications. You can define these account symbols to meet your requirements.

Example

For account 113100 you could define an account symbol BANK.

For information on account symbols, refer to Account Symbols And Account Allocation.


Posting Specifications and Account Determination

1–6 May 1997

Posting specifications consist of a posting key and account symbol (and their attendantspecifications) for one or two line items (debit and credit postings). The system uses theaccount symbol to determine the G/L account to which to make the posting.

Examples: Posting Specifications

Examples: Posting Specifications

Example 1: Posting Check Deposits

Example 2: Posting Transfer Debit Memos

Example 3: Posting Charges

Example 1: Posting Check Deposits

Posting rule Posting area Document type Posting key Account symbol

0003 1 SA 40 INCOMING_CHECK

50 CLEAR_CHECK

0003 2 DZ 40 CLEAR_CHECK

no entry no entry

When making these specifications, you should note that you are not permitted to enteraccount symbols for sub-ledger accounts, since these are determined either by thestandard interpretation algorithm for finding clearing information or by functionalenhancements.

You start by specifying a posting type for each set of posting specifications.

You can choose from the following posting types:

Key Meaning

1 Post to G/L account

2 Debit posting to sub-ledger account

3 Credit posting to sub-ledger account

4 Clear debit entry from G/L account

5 Clear credit entry from G/L account

7 Clear debit entry from sub-ledger account

8 Clear credit entry from sub-ledger account

In example 1 the posting in posting area 1 would have posting type 1 (Post to G/Laccount) and the posting in posting area 2 would have posting type 8 (Clear credit entryfrom sub-ledger account).



May 1997 1–7

Example 2: Posting Transfer Debit Memos


0006 1 SA 40 TRANSFER

50 BANK




Key Meaning








In example 2 you would allocate posting type 4 (Clear debit entry from G/L account).

Example 3: Posting Charges


0009 1 SA 40 OTHERS

50 BANK




Key Meaning


Account Symbols And Account Allocation

1–8 May 1997








In example 3 you would allocate posting type 1 (Post to G/L account).

Account Symbols And Account AllocationThe account symbol is defined by the user when configuring the electronic bankstatement. It specifies which G/L account is posted to. You create the prerequisites forthis when creating your house banks. Here you maintain the bank details and theaccounts that you have at your house bank. You must create a G/L account in yoursystem for each of these accounts. In the master record of each of these G/L accounts youenter a currency key. The currency key must be the same as the currency in which yourun the respective account at your house bank.

Maintain your house banks in the G/L Accounting Implementation Guide via the stepDefine house banks.

Caution

When specifying bank account data in the house bank table on your accounts at yourhouse bank, you must create a G/L account for each account. If you fail to do this, thesystem cannot make any postings when it receives the electronic bank statement.

How does the G/L account you specified when maintaining your house bank accountsreceive the correct posting when you specify a certain account symbol? This is effectedby the system replacing the account symbol with the appropriate account at the time ofposting.

The following topics describe the options available for allocating G/L accounts toaccount symbols.

Assigning G/L Accounts to Account Symbols

Account Allocation Using Function Enhancement: Account Modification

Account Allocation for Business Transactions in Foreign Currency

Assigning G/L Accounts to Account SymbolsYou can assign the G/L account to the account number in the following ways:

• You can enter it in full:

Account symbol G/L account


Account Allocation for Business Transactions in Foreign Currency

May 1997 1–9

BANK 0000113100

• You can enter the account number generically, i.e. by entering a series of “+” signs:


BANK ++++++++++

If you enter the number generically, the system replaces these plus signs with the G/Laccount number you maintained for your house bank (for example, 0000113100).

• You can enter the part of the account number and complete the field with “+” signs:


BANK ++++++++02

In this case too the system replaces these plus signs with the G/L account number youmaintained for your house bank, but the non-generic part of your entry remains in thefield. Again, taking the example of account 0000113100 (as defined in the house bankmaster), the two end digits of the number are replaced by “02”. This entry would triggera posting to account 0000113102.

Note

Note that, when making generic entries (i.e. using “+” signs), the system expects a10-character entry for an account. If you are using account numbers shorter than 10characters, you must make your entries right-justified.

You can test the postings that your entries will trigger by selecting Goto → Selectsimulation from the maintenance screen for the posting specifications.

Account Allocation for Business Transactions in Foreign CurrencyYou can also make postings in foreign currencies to foreign currency accounts. Forexample, you want to post foreign currency cash receipts (for example, DEM, GBP) to adifferent account from that to which you post cash receipts in local currency (forexample, USD). You achieve this by making the following entries in the accountdetermination configuration settings:

Account symbol Currency G/L account

CASH_RECEIPT (1) + ++++++++01

CASH_RECEIPT(2) GBP ++++++++02

CASH_RECEIPT(3) DEM ++++++++03

If the electronic bank statement contains an amount in GBP, the system takes the secondentry from the table (2) in order to determine the account for posting. For amounts inDEM it takes the third entry (3). For amounts in local currency or currencies for whichno separate account has been defined, the system takes the first entry (1).


Account Allocation Using Function Enhancement: Account Modification

1–10 May 1997

Account Allocation Using Function Enhancement: AccountModification

Another way of modifying the determination of accounts for postings in the SAP systemis the Account modification function (field FEBEP-KFMOD). Entries in the “Accountmodification” column are user-defined. They are required by the functional enhancement(user exit) for your company-specific posting transactions, such as ‘breakdown ofaccount transactions by processing clerk’ or ‘selection by delivery note number’ etc.

Example:

An insurance company has defined the account symbol CASH_RECEIPT for cashreceipts from its policy holders. To make the postings easier to analyze, the accountingdepartment wants to post the cash receipts to different accounts according to the type ofinsurance involved. The insurance type is therefore denoted by the first three digits of theinsurance number. The policy holders pay their premiums using pre-printed transferforms containing the insurance number. This enables the company to set the accountmodification as the first three digits of the insurance number (by means of a functionalenhancement). The G/L account for the insurance company’s house bank is 113100. Thisleads to the following entries for the account determination:

Account symbol Account modif.. Currency G/L account

CASH_RECEIPT + + ++++++++01

CASH_RECEIPT 200 + ++++++++02

CASH_RECEIPT 300 + ++++++++03

If you have programmed your functional enhancement accordingly and then receive acash receipt for insurance number 200.1234.3456.11, field FEBEP-KFMOD is set to‘200’ (FEBEP-KFMOD = ‘200’) in the functional enhancement (user exit). This triggersa posting to account 113102. If the system cannot find an insurance number at the time ofthe cash receipt, this field remains empty and account 113100 receives the posting.

Recommended Sequence of Configuration TasksYou should carry out the configuration of the electronic account statement in thefollowing order:

1. Define transaction types.

You should group together all banks that use the same external transaction code forcertain business transactions under the same transaction type.

2. Allocate banks to each transaction type via the bank key and bank account number(1).

3. Create posting rules. The system needs these to find the posting specifications (2).

4. Allocate the external transactions to the posting rules (3).

5. Define posting rules and/or posting specifications (4).


Creating Transaction Types

May 1997 1–11

MT940 051 + 1000MT940 051 - 2000

: 1000

MT940 052 + 1000. . .

Bank key Bank act Trans.type

100 200 30 548333 MT940100 200 30 888333 MT940300 500 00 6097612 MT940622 512 50 + MT940. . .

Post.rule Text

1000 Credit memo2000 Debit memo

. . .

1 2

43

Posting rules

Postings

Allocate banks

Allocate transactions

Posting rule

Posting specifications

Account determination

Tran.type Ext.tran. +/- Post.rule

Creating Transaction TypesYou define transaction types via the “Cash Management” node in the ImplementationGuide. Go to this node and then select the step “Maintain transaction types”. For moreinformation on this topic, read the documentation in for the “Cash Management” node inthe Implementation Guide.

Refer also to:

Transaction Type

Allocating BanksYou allocate each of your house banks to a transaction type via the “Cash Management”node in the Implementation Guide. Banks are identified by specifying bank keys andexternal account numbers.

To do this, select the step “Allocate banks to transaction types”.

For more information on the procedure, refer to the “Cash Management” node in theImplementation Guide.

Creating Keys For Posting RulesYou create posting rules vie the “Cash Management” node in the Implementation Guide.Posting rules are represented in the system by a non-bank-specific code (for example,0001 for debit memos).

To do this, select the step Create keys for posting rules.


Also refer to:


Allocating External Transactions

1–12 May 1997

Posting Rules

Allocating External TransactionsVia the “Cash Management” node in the Implementation Guide you allocate the externalbank-defined transaction codes to system-internal posting rules for each transaction type.To do so, select the step Allocate external transactions.

Note the following when allocating the transaction codes:

• +/- sign

You can further differentiate between external transactions by setting “+” or “-” signsfor them. If the external transaction code has a “+” sign in front of it, it is a cashreceipt; likewise, a “-” sign represents a cash disbursement.

• the interpretation algorithm

In addition to specifying posting rules, you must also specify which interpretationalgorithm should be used. The interpretation algorithm determines whether (and withwhich algorithms) the system should search the note to payee lines of the electronicbank statement for clearing information.

For more information on this, read Interpreting the Note to Payee Fields.


See also:

Posting Rules

Defining Posting RulesYou define posting rules via the “Cash Management” node in the Implementation Guide.To do so, select the step Define posting rules for electronic bank statement.

In this step you carry out the following activities:

• You create the account symbols for the required posting transactions.

• You define the account determination rules for each of the account symbols.

• You create posting specifications for postings to G/L or bank accounts (posting area1) and sub-ledger postings (posting area 2) for those of the posting transactions youchoose.


See also:



How Does The Automatic Posting Function Work?

May 1997 1–13

How Does The Automatic Posting Function Work?The following section describes the process involved in the automatic posting of the datafrom the electronic bank statement in the SAP system.

You will find it helpful to have first read the configuration topics before reading thissection.

Information in the Electronic Bank Statement

Using the Electronic Bank Statement for Postings and Clearing

Information in the Electronic Bank Statement

The table below illustrates the structure of the electronic bank statement and theinformation it contains:

CNo.

0001

0002

Val.dt.

0003

0004

0005

0006

Posting text BTC

070

004

0XX

001

051

051

Note to payee

-

17100075

1350000023

30,000.00

-3,300.00

207,000.00

- 600.00

10,700.00

1,000,000,000.00

33,900.00

1,000,277,700.00

0.000.00

Example: bank statement

Bank: XXX Account no: 179097789 Short key: 00000687Acct holder: YYY Account ID: CURR Statement no.: 00051Bank no.: 66010076 Currency: USD Statement date: 09/24/1996House bank: ZZZ

Pst.dt. Amount

09/24

09/24

09/24

09/24

09/24

09/25

09/24

09/24

09/24

09/24

09/24

09/24

Doc.

Invoice

Check 1500045

Invoice from07/03/1996Inv.no.131000067Bk.no.: 66010075Act: 279099756

Invoice from06/15/1996

CHECKDEPOSIT

CREDITMEMO

Opening balance:

Closing balance:

Debit total:Credit total:

The electronic bank statement contains the following information:


Using the Electronic Bank Statement for Postings and Clearing

1–14 May 1997

• General information on the house bank (bank number and account number, accountcurrency, statement number and statement date)

• List of individual business transactions that took place on the account (line items)

Using the Electronic Bank Statement for Postings and ClearingAfter importing the electronic bank statement, the SAP system searches through it for theinformation that it requires for the automatic part of the processing.

For example: Your customer pays an open invoice by bank transfer to your house bankaccount (item no. 5 in the example from Information in the Electronic Bank Statement ).

You have configured the electronic statement in such a way that this transaction triggersthe following two-level posting transaction in your system:

1. The cash receipt is posted to a clearing account, for example, a cash receipt account(bank posting)

2. The customer is determined and the item cleared from this account (sub-ledgerposting)

For this the system requires the following information from the statement:

a. The business transaction (for example, transfer by credit memo) must be identified.Then the system must apply a rule in order to determine how that businesstransaction is posted in the system (account determination).

b. Clearing information must be found (for example, document number), in order thatthe customer open items can be cleared.

How does the system then identify the business transaction and find the relevant accountusing the posting rule?

To do this, the system applies the following search sequence:

1. It determines the transaction type in the configuration table on the basis of the bankkey (in our example 66010076) and the bank account (in our example 179097789).

2. It determines the posting rule key in the configuration table on the basis of thetransaction type and the external transaction code / bank’s business transaction code(BTC), (in our example 051).

3. It determines the posting specifications and the account determination rules that youdefined in the configuration of the electronic bank statement, on the basis of theposting rule key.

How is the customer open item now cleared? Which information is required for theclearing transaction?

The system finds the necessary information for this in the note to payee lines in thestatement (in our example the reference number 131000067). Using the documentnumber or the reference document number, the system finds and clears the document.The document number or the reference document number are found by means of“interpretation algorithms”. Even if the document number was not included in thestatement, there are several ways to clear the document. For information on this, refer toInterpreting the Note to Payee Fields.


Electronic Bank Statement: Usage

May 1997 1–15

If the system is able to find all the information it requires in the electronic statement, thedata is posted in the system. Normally these postings should be made error-free.However, there are many cases that require manual post-processing - see PostprocessingBank Statements.

Electronic Bank Statement: UsageThe following sections describe electronic bank statement entry. Processing is always inthree steps.

1. Each bank statement format is imported into the bank date memory.

2. Data is interpreted by filtering out the clearing information from the unstructureddata. This clearing information is stored in the database for payment advices.

3. Batch input sessions are then created, or the bank statements are posted directly.

To ensure statements are posted properly, certain requirements must be fulfilled.

• An internal transaction key must be defined for all posting transactions. Thistransaction key represents the business transactions relevant to bank statement entryand controls the procedure for posting to G/L and subledger accounts.

• External transactions must be defined for those keys (business transaction code, textkey, posting text) that may be used differently by each bank.

• External transactions must be allocated to an internal transaction so that the systemcan post them.

If the program encounters an "unknown" external business transaction code whenimporting data, it terminates after the entire bank statement is imported and outputs alist of the missing entries.

You must then maintain the missing entries and restart the program.

The above requirements for the posting procedure are fulfilled within systemconfiguration. For more information on this subject, refer to Electronic Bank Statement:Configuration.

For more information, refer to:

Importing DataBefore importing bank statements into the SAP System, you must first receive them fromthe banks.

Normally, you receive the statement files via banking communication software (BCS),which calls the bank and retrieves the files via data transfer. Banks in almost allcountries sell these PC programs and provide training for them.

Data transfer with banks usually occurs on a contractual basis.

Note

Contact your banking representative for more information on electronic banking.


Interpreting the Note to Payee Fields

1–16 May 1997

Data transfer in Germany is normally carried out with Multicash Software. Almost everycredit institute has its own name for data transfer software.

The import procedure can only be run when the bank statement files are accessible onyour file system or PC drive.

Release 3.0 supports over 16 international formats for the electronic bank statement.Before importing files, SAP’s standard program converts some of the bank statementfiles to Multicash format.

If SWIFT-Mt940 should be processed, SAP recommends converting it to Multicashformat (AUSZUG.TXT and UMSATZ.TXT) via Multicash Software. You should onlydirectly import the SWIFT format when Multicash Software is not available in thecountries where you are transferring statement data.

MultiCash format is recommended because it is standard for all banks.

For the SWIFT format, there are dialects which differ from the standard SWIFT. TheSAP System does not support these dialects.

Note

For more information on the format you require see the respective programdocumentation.

See:

Interpreting the Note to Payee FieldsThe note to payee fields in the electronic bank statement contain information relevant toclearing open items.

For example, the following information is supplied for each line item:

• Document number

• Reference document number

• Check number

The interpretation algorithm allows you to search for your own incoming and outgoingpayments in the bank statement, based on information supplied by your customers and/oryour house bank and entered in the note to payee lines in the bank statement.

Caution

The information in the note to payee lines must already be available in the R/3System. If it is not, the system cannot find any clearing information. That is, you canonly find a document number in the system if the information on it is supplied byyour customer and/or bank in exactly the same form and with exactly the samenumber of characters as are used in the R/3 System for that document. Thisstipulation also applies to leading zeroes.

The interpretation algorithm determines how the system is to interpret the information inthe note to payee lines.


Interpreting the Note to Payee Fields

May 1997 1–17

Note to payee info Interpretation alg. Interpretation

1001101 011 “1001101” is interpreted as thecheck number and not as adocument number; the algorithmuses the check number to find thedocument number in the SAPSystem

1001101 012 “1001101” is interpreted as thecheck number and the documentnumber; in this case, the checknumber is the same as thedocument number in the SAPSystem

In all line items, the system first uses the accounting transaction code or the externaltransaction to check whether and with what algorithms it should try to obtain clearinginformation.

The following algorithms are available.

• 000 (No interpretation)

You use this key if you do not want to use the standard algorithms delivered by SAP.Instead, the system calls up the algorithms you defined yourself, in conjunction withthe functional enhancements (user exits).

• 001 (Standard algorithm)

Algorithm 001 interprets the values in the note to payee fields of the electronic bankstatement as either documents numbers or reference document numbers. In theprocess, it checks whether the values are in the document/reference documentnumber ranges you entered when importing the bank statement. If they are, it thentries to find the items to be cleared in the R/3 System.

Caution

Note that you must prescribe the possible intervals for documents/referencedocuments using the values “BELNR number range” and “XBLNR number range” inthe selection screen for importing the electronic bank statement.

If the reference document was stored with leading zeroes in the R/3 System, thedocument can only be found if the value in the bank statement includes the leadingzeroes. If, for example, you enter 00100 - 00200 as the interval in the bank statementimport selection screen, the system does not find the value if the reference documentnumber is simply 100.

• 011 (Outgoing check: check number not same as document number)

Algorithm 011 is used in the case of payments by check where the bank usesprenumbered checks. Your house bank supplies the check number in the bankstatement. The algorithm uses the check number to find the appropriate documentnumber.


Output Data

1–18 May 1997

• 012 (Outgoing check: check number same as document number)

Algorithm 012 is used in the case of payments by check if the check print isconducted using forms which are not numbered. The SAP document number is thenprinted on the check as the check number. Your house bank confirms this checknumber on the bank statement.

You must specify the number range for the number range search here too.

• 013 (Outgoing check: check number either same or not same as documentnumber)

Algorithm 13 interprets the check number in the note to payee lines per eitheralgorithm 11 or per algorithm 12.

• 019 (Reference number DME administration)

You use algorithm 019 in the payment run. All the items for a payment mediumgenerated using the payment program are summarized by means of a DME (datamedium exchange) reference number. Your house bank confirms the overall total forthe line items with the DME reference number. The algorithm finds the DMEreference number in the note to payee lines in the bank statement. The referencenumber is used to find and clear all the line items in the system.

• 020 (Document number search)

Algorithm 020 functions in the same way as algorithm 011, except that it interpretsthe contents of the note to payee fields only as a document number.

• 021 (Reference document number search)

Algorithm 020 functions in the same way as algorithm 011, except that it interpretsthe contents of the note to payee fields only as a reference document number.

You stipulate the interpretation algorithm as part of customizing work on the electronicbank statement. Go to the Cash Management implementation guide and choose BusinessTransactions → Electronic bank statement → Allocate external transactions to postingrules. See also Allocating External Transactions

Output DataOutput data is controlled using various parameters. The following options are available:

• Execute as background job

• Print bank statement

• Print posting log

• Print statistics

• Test run

Executing the ProgramUse program RFEBKA00 to import files containing bank statement data.

To run the program, proceed as follows.

1. Choose Input → Elect. bank statemnt → Import.


Executing the Program

May 1997 1–19

2. On the next screen, access the country-specific program you need for importing thedata.

You reach the initial screen.

3. Enter the information necessary for the activated fields in the entry areas.

For more detailed information on the most important fields in the entry areas, doubleclick on one of the areas listed here:– File Specifications

– Posting Parameters

– Cash Management

– Algorithms

– Output Controls

4. To execute the program, select Program → Execute.

File Specifications

Import dataSelect this option. Set this indicator to import the bank statement from the file system toSAP bank data storage.

Caution

If you start the import program without setting this indicator, the system will try toprocess all the bank statements already in bank data storage. For this reason, makesure that bank data storage contains only actual data and no test data.

Elect. bank statement formatHere you specify the format in which the bank statements are to be imported. Normally,you will specify the format M(ulticash) or S(wift MT 940).

Statement fileEnter the path and the name of the file containing the statement data. When importingfrom a PC (hard drive or disk drive), you must also specify the drive (for example, A:).

Line item fileEnter the path and the name of the file containing the line item data.

Note

This field can only be filled when you are using the MultiCash format. This field isunnecessary for all other formats.

PC uploadSelect this option if you are using a PC and want to import the file from the disk drive orhard drive.

Caution

Note that this option is not possible if you have selected the option Execute asBatchjob (see: Output Controls ).



1–20 May 1997

Posting Parameters

Post immediatelySelect this option to have the program post the data immediately (call transaction). To beable to use the postprocessing transaction for the electronic bank statement, you have toselect this option. See Postprocessing Bank Statements.

Generate batch inputTo generate batch input sessions, select this option. See Batch Input for moreinformation on batch input processing.

Do not postIf you select this option, no postings are generated. The data is loaded into bank datastorage and held there. The posting log lists which postings would have been placed inthe batch input sessions during a production run. You can use this option, for example,for test purposes.

Assign value dateIf you select this option, the system uses the value date during posting.

Note

Make sure that the value date field on the bank posting line items is ready for input(see the field status groups).

Batch Input

When processing bank statements, you can have the system post the lines items to theG/L and subledger accounts simultaneously. To do this, the system creates two batchinput sessions:

– bank-related accounting– subledger accounting

Both sessions can be created in one run. Another option is to have the system generateand process only the session for bank postings first. By doing this, you can have up-to-date G/L account balances accessible in Cash Management as earlier as possible. Youthen create the session for the subledger postings at a later time.

Note

Once a transaction is placed in a session, it is considered to be posted.

You can set the following options for batch input processing:

• Only bank accts: Only post data for bank-related accounting.

• Session names: Rule for naming the sessions.This option is ignored if you select the option Post immediately. The sessions can benamed using the house bank ID and account ID. This applies to the bank postingsession and the subledger posting session. The first character in the name of thesubledger posting session is a “/”, which differentiates that session.



May 1997 1–21

Cash Management

If you are posting directly (online), the cash management data is posted automaticallywhen the documents are generated. If you are generating batch input sessions, however,and do not process these on time, you can integrate the data from the bank statementsinto cash management by generating cash management payment advice notes.

Cash mgmt payment advice notesSelect this option if you want the system to create a payment advice in cash managementfor each line item in the bank statement. This option is useful if there are so manypostings to be made in bank-related accounting that the system cannot post the bankstatements by the time you need to carry out your cash planning.

Note

You can select this option only if you post the electronic bank statement using batchinput.

Since postings in Financial Accounting have an effect on planning data, the batch inputsessions can then only be processed after you have completed your cash planning. Cashmanagement payment advices generated by the program are archived with the firsttransaction in the session for bank-related accounting. This option cannot be used if youselect “Post immediately”.

Planning typeThe planning type is an entry criterion for:

• The planning level under which the memo record is updated,

• The archiving category in which the memo record is stored during archiving,

• Determining whether the memo record should expire automatically because of anexpiration date, or whether it remains valid until archiving,

• The number range under which memo records are managed, and

• Determining which fields are to be displayed and ready for input when you create orchange memo records.

SummarizationIf you select this option, the system does not create a payment advice for each bankstatement item. Instead, it summarizes the bank statement items by value date and thenplaces the payment advices resulting from the summarized records into the session.

Algorithms

Number intervalHere you enter the intervals in which the values of your document numbers and/orreference document numbers are found. Values that are not within these intervals areignored by the program and therefore cannot be used as information to clear open items.

The reference number must have the same form and length as the number in the R/3System. This includes any leading zeroes.

Example


Displaying the Overview

1–22 May 1997

You send your customer a bank transfer form numbered 00101. The customer,however, tells the bank only the 101 and the bank enters this number in the bankstatement. The system cannot then find the number because it is not the same.

BundlingYou can use this field to determine whether and how bank statement items should begrouped into bundles. If you have the program post the bank statements immediately(call transaction), you can select the items of a bank statement in the postprocessingfunction by bundle. If you generate batch input sessions, you can generate an separatesession for each bundle.

With bundle type 1 (bundle per accounting clerk), the system enters the accounting clerkID from the customer master record into the field. If the customer cannot be uniquelyidentified using the bank details, the field remains blank.

With bundle type 2, the system creates a bundle per n items. A maximum of 99 bundlescan be created. If you enter 100 as the number of items, the first 100 items are put inbundle 1, the next 100 items in bundle 2, and so on. If you enter 1 as the number ofitems, items 1 to 99 are put in bundles 1 to 99. Item 100 is then placed in bundle 1 and soon.

Output Controls

You can control the output of data using the following options:

Execute as background job

Print bank statement

Print posting log

Print statistics

List separationSelect this option if you want the posting log and posting statistics printed separately.

Note

However, you can only use this option if you have selected background job. Theinformation is then printed separately according to the entries in the list separationtable with domain “LSEPW_EB”. In this table, you can maintain the parameters forprinting the posting log with value “1”, and can maintain the parameters for printingthe statistics with value “2”.

Displaying the OverviewYou can display the bank statements found in bank data memory at any time. To selectthe bank statements for displaying, you can enter the following information:

– Company code

– House bank ID

– Bank account ID

– Statement number


Postprocessing Bank Statements

May 1997 1–23

– Statement date

– External transaction code

– Posting rule

– Bundle number

– Amount

The ID is information that is not transmitted with the bank statement. Each bankstatement is assigned a unique number in the SAP System. This is referred to as the ID.

The ID is internally assigned by the SAP System

To display the overview, proceed as follows:

1. Select Input → Elect. bank statemnt → Display.

2. On the next screen, access the country-specific program.

3. Enter your selection parameters on the next screen.

4. Select Program → Execute.

Postprocessing Bank StatementsYou have the following options for postprocessing electronic bank statements. Youchoose these in the bank account import selection screen.

1. Post immediately (call transaction).

2. Generate batch input session.

The type of processing you choose at this point determines what type of postprocessingyou can use for the electronic bank statement.

If you selected the Post immediately parameter when importing the bank statement, youcan use the postprocessing transaction to modify and then post line items that the systemhas not automatically posted.

The advantage of this option is that each document number, posted because of theelectronic bank statement, is saved in bank data storage. It is then possible to determinethe status of a posting.

This is not possible in batch input processing because the statement data is not posteduntil the sessions are processed. Only then can you obtain information on whether or nota posting was made successfully.

As a rule, the sessions are first processed in the background. The result is recorded in thebatch input log. Transactions not updated remain in the session as defective records.

The sessions are then postprocessed online. You can change or delete defective data oradd any that was missing. Postprocessing is complete when there are no more defectiverecords in a session.

Since the system assumes that the postings in a session will eventually be madesuccessfully, it indicates that the line items of the bank statement are “postedsuccessfully”.


Postprocessing Bank Statements Using the Transaction

1–24 May 1997

The status in bank data storage is set to “Completed” as soon as the transaction is storedin a session.

Additional advantages include the options available in the postprocessing transaction.You can change the postings rules later or edit the payment advices (not to be confusedwith the cash management payment advices).

The table illustrates the options available.

Posting Parameter Postprocessing Where is data stored if noposting is made?

Post immediately Use transaction FEBA (path Input → Elect.bankstatemnt→ Import)

Payment advice database

Generate batch input Process defective sessionsonline

Records in the defectivebatch input session

Caution

The type of postprocessing depends on the posting parameter chosen. This meansthat it is not possible to use the postprocessing transaction to edit a batch inputsession which may be defective.

Postprocessing Bank Statements Using the Transaction

Postprocessing Bank Statements with Batch Input Sessions

Postprocessing Bank Statements Using the TransactionThe postprocessing transaction is carried out as follows.

1. Select a posting area (bank accounts or subledger accounts).

2. Then select the line items for postprocessing.

3. For each line item, you can change or delete clearing information when you comparethe note to payee lines with the clearing information that the interpretation algorithm,or user exit, stored in the payment advice.

After making your changes, you can rerun the posting process. The system thenautomatically creates the posting data. You can choose whether to display all the screensor none of them, or only to display screens in the event of an error.

To postprocess bank statements, proceed as follows:

1. Choose Input → Elect. bank statemnt → Postprocess.

The system displays the screen Postprocess Electronic Bank Statmt.

2. Enter the information necessary for the activated fields in the entry areas.

For more detailed information on the most important fields in the entry areas, doubleclick on one of the areas listed here:– Bank Statement

– Posting Parameters


Postprocessing Bank Statements with Batch Input Sessions

May 1997 1–25

3. Choose Goto → Statement overview, and the system displays the bank statements forpostprocessing.

Bank Statement

Bundle numberBank statement line items that belong together can be combined into a bundle by usingthis field. This is only important if the field GRPNR was filled using bundling when thebank statement was imported or was filled using the user exit.

The following fields are self-explanatory:– Company code– House bank– Account ID– Statement number– Statement date

Posting Parameters

Posting areaHere you specify whether G/L postings or subledger postings are displayed.

Posting methodHere you specify which screens are displayed. Normally, the postprocessing transactionis used to manually post items that were not posted automatically. Therefore, you shouldselect the setting “Display incorrect screens”.

Postprocessing Bank Statements with Batch Input SessionsIf you want to use batch input to postprocess a bank statement, proceed as follows:

1. Use the electronic bank statement import program to generate the batch input session.Choose Import → Elect.bank statmnt → Import.

At the same time, you can update the line items to the G/L and subsidiary ledgeraccounts. The system generates two batch input sessions for this purpose; one for thebank account posting and one for the subsidiary ledger posting.

You can create both sessions in one run. Alternatively, you can create and post thebank posting session first. If you do, the current G/L account balances are availablein Cash Management at the earliest possible moment. You generate the session forsubsidiary ledger postings at a later stage.

2. Process the sessions in the background.

The system makes the appropriate postings. Data from defective postings arerecorded in a session.

3. If there are any defective postings, process the defective session online.

4. Post the defective postings using the usual posting transactions.


Conversion Programs

1–26 May 1997

Conversion ProgramsThe following programs convert bank statements to MultiCash format.

Program RFEBBE00 converts the Belgium bank statement format, CODA, to MultiCashformat.

Program RFECFI00 converts Finnish bank statements specifying reference paymentsfrom customers or bank collections to MultiCash format.

Program RFEBDK00 converts Danish bank statements to MultiCash format. Thefollowing services are supported:

– UDDATA giro bank– 0602 Pengeinstituttenes Betalingssystemer(PBS)

Program RFEBNO00 converts Norwegian bank statements to MultiCash format. TheOCR giro format from Betalings Sentral (BBS) and the OCR format from a giro accountare supported.

Program RFEBSE00 converts Swedish bank statements to MultiCash format. Thefollowing formats are supported:

– Bank giro OCR– Bank giro LM (Automatisk avprickning)– Bank giro Autogiro– Postal giro OCR– Postal giro TIPS (Total Integrated Payment System)– Postal giro Autogiro

The programs import a CODA file that is stored on a PC (hard drive, disk) or in a filesystem, and create two MultiCash files.

1. Statement file

This file contains data about the statements (statement number, old balance, newbalance, currency, bank account number).

2. Line item file

This file contains the individual transactions from the statements.

Note

To import the MultiCash files that are created, use the standard program,RFEBKA00. For more information see the documentation for this program.

Functional Enhancements For The Electronic Bank StatementFunctional enhancement FEB0001 allows you to change the way the statement isprocessed.

The exact procedure is described in the documentation for the enhancement components.You can find this documentation within the enhancement definitions. You define


Formats For The Electronic Bank Statement

May 1997 1–27

enhancements via the ABAP/4 Development Workbench. Here select the path Utilities→ Enhancements → Definition. Then enter the name of the enhancement (hereFEB0001), select “Components” and then select the Display button. From the componentdisplay screen select the path Edit → Documentation.

Formats For The Electronic Bank StatementThe following section contains an overview of the formats that are supported for theelectronic bank statement in Germany. However, this overview is relevant for allcountries where the bank software package MultiCash is available or the MultiCashformat is supported.

The following Formats are supported:

• MultiCash format

This format is generated from the SWIFT MT940 formats using BCS software(Banking Communication Standard) and is recommended by SAP for use with itselectronic bank statement.

It is a format that is standard for all banks and can be easily controlled by means of aspreadsheet program or a word processing program. It consists of two files with theformats AUSZUG.TXT and UMSATZ.TXT. AUSZUG.TXT contains the headerinformation from the statement and UMSATZ.TXT contains the item information.This format allows you to import data from several electronic statements at the sametime, even from different banks.

BCS software is usually MultiCash software. This is often used by banks under adifferent name (Cotel - Commerzbank, Dretec - Dresdner Bank, ELKO - Sparkassen,...). If the BCS program is from the Deutsche Bank, you must install the program‘db-direct’.

• Swift MT940

Banks usually provide statementsin the SWIFT MT940 format (with or withoutstructured field 86).

SAP recommends that you do not import these files directly into the SAP system,since this format is not provided as standard by many banks. You are thereforeadvised to convert these formats into the MultiCash format using the BCS software(see MultiCash format).

SWIFT MT940 should only be used in cases where it is not possible to use theMultiCash format.

• DTAUS format

The main advantage of the electronic bank statement is that it ensures that all thebusiness transactions contained in the statement are posted in your system.

The DTAUS format only contains a single business transaction (for example, cashreceipt) per file and therefore only represents a fraction of the items processed in anaccount. Using the DTAUS format usually entails more than one files being importedinto the system and even some business transactions (that are not supported by thisformat) being posted manually.



1–28 May 1997

What is more, the header record of DTAUS files does not contain any reference tothe statement the items originated from (such as statement date or number). Thismeans that the import program cannot carry out the usual checks, such as thosewhich prevent the same items being imported multiple times or which check thecompleteness of the imported data.

The DTAUS format originated in the mainframe era and has certain disadvantages;the individual data records, for example, are not separated with the special characterdenoting a ‘new line’ (Carriage-Return Line-Feed <CR><LF> ), and this renders thesearch for errors extremely difficult in cases where the bank has transmitted defectivefiles. Such problems occur relatively often in Germany, where the ‘Umlaut’ character(ö, ü or ü) is frequently converted into a special character during the conversion fromASCII to EBCDIC code and back again, and thus not transmitted as a text character.

Another disadvantage of DTAUS files is that if just a single byte is missing from thefile, this renders the whole file unreadable, since every subsequent data record isdisplaced by one byte.

For the above reasons SAP does not recommend the use of the DTAUS format forposting bank statement data in the system, unless of course there are unavoidablereasons for doing so.

• BAZ format

The BAZ format is a special format used only by German post office banks. Thesame problems as with the DTAUS format apply here.

• MAOBE

The MAOBE format is chiefly used for importing data on cashed checks.

As this format will be no longer be supported by banks in future and, as of Release2.1, cashed check data can be posted using the electronic bank statement, programRFSHRU00 (which posts cashed check data) will no longer be maintained by SAPafter Release 3.0.

The electronic bank statement enables you to post all the financial transactions onany of your house bank accounts. It therefore provides far more comprehensivefunctionality in this area than program RFSHRU00, which only posted data oncashed checks.

• SAP.TXT or SAPKURZ.TXT

SAP.TXT and SAPKURZ.TXT exist for historical reasons. They were originallycreated in response to certain restrictions within the R/2 system, which have sincebeen removed. Today their use is not recommended by SAP even in the R/2 system.For this reason the formats for SAP.TXT and SAPKURZ.TXT will not be deliveredin the next version of MultiCash software (the Release after 1.24).

The R/3 system does not support these formats, since they do not contain all thenecessary fields from a bank statement (out of those available). SAP recommendsthat you use the MultiCash standard post-processing files AUSZUG.TXT andUMSATZ.TXT with their fixed record format.

These files have the following advantages:a) AUSZUG.TXT and UMSATZ.TXT have become the standard file types used for

bank statements (all banks use the same format).



May 1997 1–29

b) Format enhancements such as the addition of new fields do not require anymodifications on the part of the SAP user.

c) They carry more information than SAP.TXT and SAPKURZ.TXT (for example,business transaction code, payer’s bank data etc.)


Index

May 1997 Index-1

Index

Aaccount allocation, 1–4, 1–8account determination, 1–4, 1–5, 1–8, 1–9, 1–10account modification, 1–4, 1–10, 1–26account symbol, 1–4, 1–5, 1–8, 1–9algorithm, 1–16

BBank, 1–3, 1–5bank, 1–8, 1–11, 1–27bank account, 1–8bank accounting, 1–5bank data memory, 1–3, 1–22bank software, 1–27bank statement, 1–18bank statement, 1–13, 1–15bank statement transmission, electronic

importing data, 1–15Banking Communication Standard, 1–3Batch input, 1–25batch input processing, 1–23Batch input sessions, 1–23BCS, 1–3BTC, 1–4business transaction, 1–4business transaction code, 1–4

CClear, 1–14concepts, 1–3, 1–4, 1–5, 1–8, 1–9, 1–10, 1–13, 1–14, 1–15, 1–26, 1–27configuration, 1–4, 1–6configuration, 1–3, 1–4, 1–5, 1–10conversion program, 1–26create, 1–11Currency, 1–9customizing, 1–3, 1–4, 1–5, 1–6, 1–8, 1–10, 1–11,1–12

Ddata transfer, 1–15Definieren, Posting rule, 1–12Definitions, 1–19, 1–20, 1–21, 1–22, 1–25

display, bank statement, 1–22

Eelectronic bank statement, 1–23enhancement, 1–26examples, 1–6, 1–7explanations, 1–19, 1–20, 1–21, 1–22, 1–25external transaction, 1–4, 1–12

FForeign currency, 1–9format, 1–27functional enhancement, 1–26

GG/L accoung, 1–8G/L account, 1–8generic entry, 1–8glossary, 1–19, 1–20, 1–21, 1–22, 1–25

Hhouse bank, 1–5, 1–8, 1–11

Iidentification, 1–13import, 1–3, 1–15, 1–18, 1–26incoming payment, 1–16interpretation algorithm, 1–12, 1–16, 1–26

MMulticash, 1–3, 1–15, 1–26, 1–27

NNote to payee, 1–13note to payee fields, 1–16

Ooutput data, 1–18overview, display, 1–22Overviews, 1–3


Index

Index-2 May 1997

Ppost, 1–4, 1–14, 1–23, 1–24posting, 1–4, 1–5, 1–13posting rule, 1–4, 1–5posting rule, 1–4, 1–11, 1–12, 1–26posting specification, 1–4, 1–5posting specifications, 1–6Postprocessing, 1–24, 1–25post-processing, 1–23prerequisite, 1–15Procedures, 1–11, 1–12, 1–15, 1–16, 1–18, 1–22,1–23, 1–24, 1–25Process, 1–25process flow, 1–13process flow, 1–26Processes, 1–11, 1–12, 1–15, 1–16, 1–18, 1–22, 1–23

Rreport, 1–26

Ssequence, 1–10, 1–13settings, 1–3, 1–4, 1–10sub-ledger accounting, 1–5Swift, 1–27

Ttransaction, 1–4, 1–12transaction type, 1–5transaction type, 1–4, 1–11, 1–12Transmission of electronic bank statement, 1–16,1–18, 1–22, 1–23

run report,, 1–18transmission program, 1–3

UUpdate, 1–13user exit, 1–26

FI Electronic Bank Statement - Weeblythefico.weebly.com/.../4/9/7/14970654/fi_electronic_bank_statement.pdf · FI Electronic Bank Statement SAP AG Typographic Conventions iv May 1997

Documents