Introduction

In many countries today, bank statement data can be retrieved from

banks electronically. There are many SWIFT format dialects which
differ from the standard SWIFT. The SAP System does not support
these dialects.

With the FI-SBS Interface, SAP describes a special format for SWIFT
MT940. This format must be generated by the partner banks.

This document presents SAP’s format recommendation for SWIFT

MT940.

To become certified in the FI-SBS interface, partners must support

the generation of a file directly from their banking system in the
format described in this document.

The file must be set up in sentence format with each line ending
with a carriage return.

Field 20: Transaction Reference Number

SWIFT Classification: mandatory

SWIFT Format: max. 1 line, 16AN

SAP Classification: optional

SAP Format: not used

Example:

:20:34567546DEM

Field 21: Related Reference

SWIFT Classification: optional

SWIFT Format: max. 1 line, 16AN

SAP Classification: optional

SAP Format: not used

 Example:

:21:Rel. RefNo. 1997

Field 25: Account identification

SWIFT Classification: mandatory

SWIFT Format: max.1 line, 35AN

SAP Classification: mandatory

SAP Format: max. 1 line

SAP Recommended Layout for Field 25:

Field name Length Data Type Description

opt.
Min. Max.
Bank_ID 0 15 X AN Unique bank identifier,
delivery strongly recommended
Delimiter 0 1 X `/` Delimiter, must be `/`,
mandatory, if Bank_ID is delivered
Account_ID 1 24 AN Unique account identifier

Comments on Subfields:

Bank_ID: Must be a unique bank identifier either nationwide

(case 1) or worldwide (case 2).

Recommended values: Use either national bank

identifier if possible (case 1) or a SWIFT BIC bank
identifier.

Note: SWIFT BIC bank identifier can be used as

Bank_ID in case 1 as well.

Account_ID: Must be a unique account identifier of the account with

the bank, specified by Bank_ID.
 Example:

Case 1:

:25:60070080/1709111

Case 2:

:25:XXFCDEKL/1709111

Field 28: Statement Number / Sequence Number

SWIFT Classification: mandatory

SWIFT Format: 5N[/2N] or 5N[/3N]

SAP Classification: mandatory

SAP Format: max 1 line

SAP Recommended Layout for Field 28:

Field name Length Data Type Description

opt.
Min. Max.
Statement number 1 5 N Statement number
Delimiter 0 1 X `/` Delimiter,
must be `/`,
mandatory if sequence number is delivered
Sequence number 1 arb. X AN Not used

Comments on Subfields:

Statement number: Leading zeros can be omitted.

Example:

:28:00189/01
Field 60x: Beginning Balance (x = F or M)

SWIFT Classification: mandatory

SWIFT Format: max 1 line, 25AN

SWIFT Option: 60F (first) or 60M (intermediate)

SAP Classification: mandatory

SAP Format: max 1 line

SAP Recommended Layout for Field 60F:

Field name Length Data Type Description

opt.
Min. Max.
Sign 1 1 AN Beginning balance: credit (C) or debit (D)
indicator
Date 6 6 N Not used
Currency 3 3 AN Currency code (ISO)
Amount 1 15 N Beginning balance: amount

Comments on Subfields:

Sign: 'C' always indicates a credit balance and 'D' always

indicates a debit balance.
A minus (-) sign is not required for a debit balance in the
amount field.

Date: Date of beginning balance is not used.

Currency: ISO currency code mandatory.

Amount: The decimal point is a comma (,) and should always be

present.
A minus (-) sign can be used for a debit balance, but is
not necessary
(see Sign field).
The number of decimal places should be consistent with
the currency.
 Comments on Intermediate Bank Statements

(Tag :60M:):

No other bank statements can be placed between the first

statement containing tags :60F: and :62M: and the last statement
containing tags :60M: and :62F: within one sequence in a file, except
for intermediate statements of the same sequence that contain only
intermediate balances with tags :60M: and :62M: and identical
contents in fields :25: and :28:.

Example:

:60F:C970110ESP45,

Field 61: Statement Line

SWIFT Classification: optional

SWIFT Format: 1. Line: 66AN,

2. Line: 34 AN

SAP Classification: optional

SAP Format: max 1 line, 65AN

SAP Recommended Layout for Field 61:

Field name Length Data Type Description

opt.
Min. Max.
Value date 6 6 N Value date (YYMMDD)
Entry date 4 4 X N Not used,
if delivered, format must be MMDD.
Credit/debit mark 1 2 AN Credit/debit indicators
possible entries: `C`. `D`, `RD` or `RC`
Funds code 1 1 X AN not used
Amount 1 15 N Item amount
Transaction code 4 4 AN Transaction Type Identification Code,
first character must be `N`, `S`or `F`.
Owner’s reference 0 13 X AN Owner`s reference
Separator 2 2 X `//` Separator,
 must be present if owner`s reference is
delivered
Institution’s 0 16 X AN not used
reference

Comments on Subfields:

Value date: Format must be YYMMDD.

Entry date: Format must be MMDD (constant length) if

delivered.

Credit/debit mark: Indicates transaction type (credit or debit)

Allowed entries:
C = credit
D = debit
RC = reversal of credit (debit entry)
RD = reversal of debit (credit entry)

Funds code: Not used

Amount: Delimited on the right side by N, S or F`(-> start of

transaction code).
Decimal point is a comma (,) and should always be
present.
A minus (-) sign for a debit amount is allowed, but
not necessary
(-> credit/debit mark).
The number of decimals should be consistent with
the currency.

Transaction code: List of transaction codes must be delivered

by a bank. Also referred to as business transaction code.

Owner`s reference: If bank’s reference is also

delivered, owner’s reference is delimited on right
side by '//'. Data is also interpreted as check
number.
Maximum length: 13. Use field :86: for longer
entries.

Bank reference: Not used.

Example:

:61:970111CP301,NMSCNONREF//8380050000085146

Field 86: Information to Account Holder

SWIFT Classification: optional

SWIFT Format: max.. 6 lines , 65AN each.

SAP Classification: optional (unstructured)/mandatory

(structured)

SAP Format: n lines, 65AN each,n arbitrary (unstructured)

Max. 6 lines, 65 AN each (structured)

General considerations about the need for providing selected and

structured information in field 86 for SWIFT MT940 format:

Efficiently using R/3’s electronic banking program RFEBKA00 relies

basically on two very essential requirements:

 A file format for the delivered bank statement that enables the
transfer of electronically readable data between a customer’s
house bank and the R/3 System.

 The actual data contained in this format in order to optimize the

performance of program RFEBKA00.

Providing that the house bank supplies electronic statement data

using a structure that meets SAP’s MT940 format recommendation,
the performance of RFEBKA00 greatly depends on the data that is
actually contained in the file.

Since line 61 can contain only a certain amount of information,

additional information can be entered in field 86 for each line 61 of
a bank statement.

Data in field 86 must be structured so that the SAP R/3 System can
correctly identify and interpret it. The system can retrieve only
structured data without significant loss of performance.

The following comments describe the information that is essential

for data transfer and the processing steps that require this
information.

Then the layout of a structured field 86 that SAP has implemented

in the R/3 System is explained. It is a ready-to-use solution as long
as your bank can transfer its statements with the data required in
this format. This structure is an exact copy of the structure of
MT940 bank statements that German banks are able to deliver.

Customers can implement the user exit from program RFEBBU10 to support
any bank-specific structure for field 86. In this case, the bank must provide
a detailed layout description of field 86 and a list of all contents required in
its MT940 statements. Customers have to create their own source code for
this user exit or obtain it from their house bank.

Comments on Essential Information:

Business transaction information:

The program uses this code and the settings you make in
Customizing to find the posting rule that determines:

 if the item is posted in a one or two step process

 if individual items in one transaction are compressed before they

are posted

 the accounts to which an item is posted in each step

how the bank statement information is interpreted using

algorithms. Algorithms interpret the delivered information in a
particular way (i.e. as invoice number) in order to find the open
item to be cleared.

 whether posting and clearing are performed at the same time

 Clearing information:

To find the open item that should be cleared with the item in a bank
statement, the program has to find a link to it.

To do this, it can use:

 specific information on the open item like the document number

or invoice number

information on the account to be posted, for example, a link to the

customer who initiated this particular transaction. Once it
determines the right account, the program tries to identify the
open item by amount and then clear it.

SAP Recommendation for the Actual Data in

Field :86

1) MOST IMPORTANT: Provide ALL data STRUCTURED!

2) Provide one unique business transaction code for each

transaction offered.

3) Deliver business partner’s bank identifier and account number if

possible.

4) Deliver all notes to payee without truncation if possible

SAP Implemented Layout for Structured Field

86:

Field name Length Data Type Description

opt.
Min. Max.
Business 3 3 AN Mandatory
Transaction
Code
Delimiter 1 1 ASC Mandatory, if Business Transaction Code not
equal 999
Data 0 386 X AN Structured data

SAP Classification: mandatory

 SAP Format: max. 6 lines , 65AN each,n arbitrary

Comments on Subfields:

General: Field :86: (structured) is mandatory, if report RFEBKA00 is

used with option `S`.

Business Transaction Code: A list with their meanings is provided

by the house bank.
Unknown transactions are described
by 999.

Delimiter: Caution: Any ASCII sign at fourth position of field :

86: is interpreted as separator.
Therefore no ASCII sign can be used that is also part of
the provided data (i.e. all
letters or numbers)

Data: Data is structured as follows:

1) Data can consist of 13 fields.

2) All fields are separated by the Separator.
3) First two numbers of each field identify of the field
contents.
4) Rest of field is information contents.

Data Layout Description:

Identifier Maximum Type Data Meaning

length Opt.
00 50 AN X Posting text
10 10 AN X Primanota
20 65 AN X Note to payee 1
21 65 AN X Note to payee 2
22 65 AN X Note to payee 3
23 65 AN X Note to payee 4
24 65 AN X Note to payee 5
25 65 AN X Note to payee 6
26 65 AN X Note to payee 7
27 65 AN X Note to payee 8
30 15 AN X Bank identifier business partner
 31 18 AN X Account identifier business partner
32 55 AN X Name business partner

Example of Structured Field 86:

:86:051?00INVOICE?100799?20Invoice# 0012788888888?21invoice
date 05.12.96?22415 clutches?3060070080?311709111?32SAP AG

Field 62: Ending Balance (x = F or M)

SWIFT Classification: mandatory

SWIFT Option: 60F (first) or 60M (intermediate)

SWIFT Format: max 1 line, 25AN

SAP Classification: mandatory

SAP Format: max 1 line

SAP Recommended Layout for Field 62F

Field name Length Data Type Description

opt.
Min. Max.
Sign 1 1 AN Ending balance: Credit (C) or Debit (D) Mark
Date 6 6 N Not used
Currency 3 3 AN Currency code (ISO)
Amount 1 15 N Ending balance: amount

Comments on Subfields:

Sign: 'C' always indicates a credit balance and 'D' always

indicates a debit balance.
For debit balances no further minus (-) sign in the Amount
field is needed.
 Date: Used as date of account statement. Format
YYMMDD.

Currency: ISO-currency code mandatory.

Amount: The decimal point is a comma (,) and should always be

present. A minus (-) sign for
a debit balance is allowed, but not necessary (-> Sign
field).
The number of decimals should be in consistency with the
currency.

Comments on Intermediate Bank Statements

(Tag :62M:):

No other bank statements can be placed between the first

statement containing tags :60F: and :62M: and the last statement
containing tags :60M: and :62F: within one sequence in a file, except
for intermediate statements of the same sequence that contain only
intermediate balances with tags :60M: and :62M: and identical
contents in fields :25: and :28:.

:62F:C970110ESP301,

Other Fields

NOT USED

File Example:

:20:34567546DEM
:21:Rel. RefNo. 1997
:25:60070080/1709111
:28:00189/01
:60F:C970610DEM145,31
:61:970611C,19NMSCNONREF//8380050000085146
:86:051?00INVOICE?100799?20Invoice# 1800000240?21invoice
date 05.12.96?22415 clutches?3060070080?311709111?32SAP AG
:62F:C970611DEM145,50
:20:34567546DEM
:21:Rel. RefNo. 1997
:25:60070080/1709111
:28:00190/01
:60F:C970611DEM145,50
:86:999
:62F:C970612DEM145,50