SAP Partners With Banks and Customers To Speed Delivery of Corporate-To-Bank Connectivity Support (Tool)

Mapping Between SAP Internal Data Field
Implementation (CGI) Template - Custome

pain.001.001.03 of 14 Octo
The mappings in this document are a d

SAP Community Definition G
SAP to ISO 20022 CGI Ma
SAP Community Definition Group SAP to IS

Purpose
Develop mappings of CGI guidelines to SAP internal Data Fields
Scope
All 6 CGI message templates
Methodology
Using CGI message templates, SAP FPay Tables, SAP CCTS Conforma
appropriate
Teleconferences and F2F meetings for actual mapping
SAP StreamWork for collaboration and sharing
Deliverables
Excel Spreadsheet (e.g. this document) map between ISO 20022 Transa
template and the SAP internal data fields), DMEE/PMW XML Format, PI
SAP Implementation Notes - Supporting user documentation with explana
Potential Incorporation into SAP product of selected transactions to incl

Types (In conjunction with the SAP Implementation Note)
Conventions:
All CGI Conventions for Columns A through O are preserved
Color Code
Color Coding for Columns P&Q in Mapping Spreadsheet

Explanation
Data Tag is Tag Only to identify a parent element with one or more child elements.
Data Tag not used
The Mapping between the CGI Element and SAP Element is agreed to and validated
through testing
The Mapping as stated is partial support for the CGI Element and has been validated
through testing
The CGI Element is not as yet supported by the current SAP solution. This element may at
some future time be supported - depending on customer requirements. In the interim, it
should be treated the same as Customer Customization Required.
SAP has no plans to directly support this CGI Element as there does not appear to be
broad demand for its use. Individual customers who do require it in bilateral agreements
with their bank for their value added services will need to develop a custom solution.
Special Terms
A single element can have sub elements. These sub elements can either be used to create
a compound value for the parent element, or can represent possible nodes that depending
on the condition populate the parent element.
Atom
The exit function allows the user to enhance/override the default settings. For example if
there are bank specific settings allowed beyond the default settings provided for in the SAP
solution for a bilaterally defined field, the user can use this to meet that requirement.
Exit
Note to payee
Type 1
Short entry for note to payee, internal
Type 2
short entry for note to payee, external
Type 3
Contributors
SAP
Deutsche
Bank
SWIFT
Bank of America
Merrill Lynch
HSBC
B2 - TDI
Citi
JPMC
UK Payments
Danish Bankers
Association
Nordea
Wells Fargo
Danske Bank
RBS
FIT-EDV
Data Fields and the Common Global

- Customer Credit Transfer Initiation
of 14 October 2010
ument are a deliverable of the

y Definition Group 022 CGI Mapping
SAP to ISO 20022 CGI Mapping
urpose
a Fields
Scope
hodology
CTS Conformant Global Data Types, other SAP tables as
verables
O 20022 Transaction elements as identified in CGI message

XML Format, PI XML Schema.
ion with explanations, amplifications, and guidance
actions to include new SAP data fields and Global Data
ld elements.
o and validated
been validated
This element may at

s. In the interim, it
not appear to be
lateral agreements
ustom solution.
ther be used to create

nodes that depending
ngs. For example if

rovided for in the SAP
at requirement.
All Content on This Sheet is taken directly from the CGI Temp
ensure users of the mapping understand the proper con
COMMON GLOBAL IMPLEMENTATION (CGI)
Customer Credit Transfer Initiation pain.001.001.03
As of October 14, 2010
Driven by customer demand for multibank coordination of implementations
}Global
corporate, multi-banked, multi-payment type, multi-country implementations (mixed

}Is intended specifically for global, multi-country, multi-bank and multi-instrument implemen
banks can commonly accept as ONE of their implementations
}Focuses on the general message structure and then successful creation of individual tran
by the participating banks
}Can be published and has endorsement from appropriate communities
}Actively engages corporate partnership
The common global implementation is not intended to:
}Focus
on purely domestic or single instrument files (e.g. banks will still offer these)
as the sole map accepted by participating banks (e.g. participating banks will still
services and capabilities but can also offer this common implementation where desira
appropriate customer)
}Replace domestic banking convention in-country or bank servicing capabilities (e.g. th
on the format that can be commonly used)
}Serve as an interbank map (e.g. participating banks will be able to create proper instruc
domestic clearing and settlement systems from this map)
}Serve
COMMON GLOBAL IMPLEMENTATION GUIDELINES

~The required elements in the CGI will be accepted by all CGI supporting banks. They define a standard set of data with a
qualifications.
~Any data populated in a schema-defined optional field that is not required by an individual bank will be ignored and not s
rule includes elements that are designated "Not Used" by the CGI. Bilateral documentation should specify where an "R" f
~Where individual clients do not maintain a CGI-Required or Conditional element in their systems, they should consult wit
data elements required for that type of transaction. This could result in the need to add those data elements into the client
~The following general attributes are assigned in the CGI and should be read in conjunction with the country/payment inst
a country/payment instrument has not been addressed, the banks engaged by the client will work to try and agree on a co
country/payment instrument rules
-The following definition is associated with the payment types:

ACH - Domestic & International: General usage is equivalent to low value or non-urgent transactions. Typically assoc
and/or low priority transactions.
Wires - Domestic & International: General usage is equivalent to high value or urgent transactions with high priority
Cheques/Drafts: Typically, paper based transactions
~Any of the data tags included in this guide will be accepted by any bank supporting the CGI. The bank will either use the
ATTRIBUTES
CODES
TERM
DEFINITIONS
Required
Standard element for CGI; Required

either by schema or CGI
Conditional
Standard element for CGI; Dependent

upon a certain condition.
BD
XOR
NU
Standard element for CGI. Contents are

bilaterally determined between client and
Bilaterally Determined bank
eXclusive Or
Standard element for CGI. Contents are

XOR either by the schema or CGI usage.
Not Used
Not Used by CGI
REFERENCES TO ISO DOCUMENTATION

[0..x]
Optional
[1..1]
Mandatory
Optional to schema for subcomponent;

may repeat
Mandatory to schema for subcomponent
Root Tag of message
Level Component Tag; no data content
Component Tag; no data content
Data Tag not used
CONTRIBUTORS
BBVA
Nordea
CRG (Ikea, Wuerth, Fiat Group, Yara,

Utsit)
Bank of America
Merrill Lynch
RBS
Cargill
BNP Paribas
Citibank
Deutsche Bank
HSBC
JPMC
Santander
SEB
Standard Chartered
Bank
Oracle
GE
Danish Bankers Association
SWIFT
UK Payments
ASSUMPTIONS
-Truncation of data will be determined via bilateral agreement between customer and bank.
-Duplicate checking will be determined via bilateral agreement between customer and bank.
-Standard XML version declaration must explicitly specify that XML v1.0 is being used. The <Document> tag should spec
Example:
<?xml version="1.0" encoding="UTF-8" ?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http://www.w3.org/2001/XMLSchema-i
-Tag length is dependent upon country clearing requirements and is not quoted in this document.
-The branch code of an agent should be explicitely stated I the <BrnchId> component versus being combined with Clearin
required.
-This document addresses where the data is placed. It does not define the requirements for when the data must be prese
-The CGI allows for inclusion of SEPA transactions based on CGI parameters which may be broader than SEPA guideline
-Information captured under <RegulatoryReporting> or <Tax> is used explicitily for the applicable function and not to be re
payment.
-The CGI country rules template represents the minimum requirements for each payment method within each country in o
processed. It does not indicate that all banks will use or require this minimum data. The core minimum requirement should
primary concept of data overpopulation.
- The population of <Cd> or <Prtry> under <CtgyPurp> or <Purp> is depdendent upon the originator's usage of ISO 20022
in <Cd> or local market practice codes or text in <Prtry>.
-If a bank requires a local instrument code to indicate that an URGP transaction is cross border, the value of 'IN' is utilized
ectly from the CGI Template without change to

nderstand the proper context and content
dination of implementations
pe, multi-country implementations (mixed payables)

multi-bank and multi-instrument implementations that the participating
implementations
hen successful creation of individual transactions that can be executed
propriate communities
t intended to:
es (e.g. banks will still offer these)

banks (e.g. participating banks will still be able to offer their value added
his common implementation where desirable or requested by an
y or bank servicing capabilities (e.g. these are different than agreeing
anks will be able to create proper instructions and file formats for
om this map)
banks. They define a standard set of data with agreed country/payment instrument
d by an individual bank will be ignored and not stop processing of the message. This
ral documentation should specify where an "R" field will be ignored by a specific bank.
element in their systems, they should consult with their bank(s) on the minimum of
e need to add those data elements into the client's systems.
ead in conjunction with the country/payment instrument rules produced for the CGI. If
ed by the client will work to try and agree on a common addition to the CGI
alue or non-urgent transactions. Typically associated with a batch process
h value or urgent transactions with high priority
supporting the CGI. The bank will either use the tag for processing or ignore it.
EXPLANATION
This element is either mandatory in the schema or is a required by some
or all of the CGI supporting banks. An "R" field may represent a piece of
data that some of the banks do not need for processing, but have agreed
that the client may send. Bilateral documentation should specify where
an "R" field will be ignored by a specific bank.
This element needs to be present when certain conditions apply. These

fields are designated "C" with the condition specifically defined in the
"RULES' column. These conditions include:
-Presence based on a choice between elements or components
which are shown to be mandatory in the schema, such as the
choice between code and proprietary.
-Presence based on whether a data element or component exists
for that specific transaction, such as the presence of an ultimate
debtor or ultimate creditor for that transaction.
-Presence based on the requirements for a specific country and/or
payment instrument.
This is an element that an individual bank or client may require. The
need to populate it will vary. For example, some banks may require the
use of a branch identification code in countries where they have multiple
branches and execute transactions through each of their branches.
Individual bank documentation should be consulted to determine when
and how to populate a "BD" designated field.
Select one or the other field, but not both
This element is not used by the CGI. The field may be present and will be
ignored by receiving party of the message. The data fields are 'hidden'
for concise presentation of guide.
Occurrence will note whether a subcomponent is repeating and number

of occurences.
Occurrence will note whether a subcomponent is mandatory in the
schema of the component.
stomer and bank.

ustomer and bank.
s being used. The <Document> tag should specify the appropriate namespace.
mlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
uoted in this document.
component versus being combined with Clearing System Member ID when it is
e requirements for when the data must be present or the values to be contained.
ters which may be broader than SEPA guidelines.
plicitily for the applicable function and not to be reported to beneficiary as part of the
r each payment method within each country in order for the payment to be
mum data. The core minimum requirement should be viewed in conjunction with the
endent upon the originator's usage of ISO 20022 code value in the External Code List
action is cross border, the value of 'IN' is utilized in Local Instrument.
Customer Credit Transfer Initiation V3 pain.001.001.03
2
3
ISO Published: April 2009

Common Industry Agreement: As of October 14, 2010
ISO
Or
Index
No.
6
7
8
1.0
1.1
1.2
Message Item
Message Item (Non- Tag Name

Indented)
Structural Structural Sequence

Sequence Number
Customer Credit Transfer

Initiation
GroupHeader
MessageIdentification
CreationDateTime
<CstmrCdtTrfInitn >
GroupHeader
<GrpHdr>
+
MessageIdentification <MsgId>
++
CreationDateTime
<CreDtTm>
++
01
01.01
01.02
Mult.
[1..1]
[1..1]
[1..1]
Type
Text
ACH Domestic
& Int'l
Wires - Cheques/ SEPA

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
RULES
28
29
1.3
1.4
{Or
Authorisation
Code
1.5
Or}
Proprietary
Authorisation
Code
<Authstn>
<Cd>
++
+++
01.03
01.03.01
[0..2]
[1..1]
BD
BD
BD
Code
BD
BD
BD
Customer Customization
Required
Proprietary
<Prtry>
+++
01.03.02
[1..1]
Text
BD
BD
BD
Required
1.6
NumberOfTransactions
NumberOfTransactions <NbOfTxs>
++
01.04
[1..1]
Text
1.7
ControlSum
ControlSum
<CtrlSum>
++
01.05
[0..1]
Quantity
BD
BD
BD
1.8
9.1.0
InitiatingParty
Name
InitiatingParty
Name
<InitgPty>
<Nm>
++
+++
01.06
01.06.01
[1..1]
[0..1]
Text
BD
BD
BD
O (70 char
only)
+++
++++
01.06.03
01.06.03.01
[0..1]
[1..1]
+++++
01.06.03.01.01
[0..1]
BD
BD
BD
#EXIT
01.06.03.01.02
[0..n]
BD
BD
BD
R (1 occur
only)
R
FPAYHX
BD
BD
BD
9.1.12
9.1.13 {Or
9.1.14
Identification
Identification
<Id>
OrganisationIdentification OrganisationIdentificat <OrgId>
ion
BICOrBEI
BICOrBEI
<BICOrBEI>
31
9.1.15
32
33
9.1.16
9.1.17
9.1.18
SAP Technical Comments
General Comments
Source Field
RENUM
DATLO & TIMLO
XVORL
Atoms
Other
Identification
SchemeName
Code
2.0
2.1
This is not typically sent. If a customer wants to send one of the

four code values that are specified in the supporting XSD Schema,
they must implement a customization.
#AGGR
<CdtTrfTxInf>
number of occurences
#AGGR
<InstdAmt>
summation (total)
Can be used for SEPA, but not

required. See Appendix B.
FPAYHX
NAMEZ
PaymentInformation
SRTF2
Summation is made after each item in SAP system and then
populated from that aggregation rather than a source field.
Tag Only
Name of the sender of the message. Typically the company name
Tag Only
Tag Only
Database Table T001 and corresponding field
source PAVAL is used in the Function Module to
determine the Identification. See attached
information for usage of BICorBEI element.
ZREGI
Other
<Othr>
+++++
Identification
SchemeName
Code
<Id>
<SchmeNm>
<Cd>
++++++ 01.06.03.01.02.01
++++++ 01.06.03.01.02.02
+++++++ 01.06.03.01.02.02.01
[1..1]
[0..1]
[1..1]
<PmtInf>
<PmtInfId>
+
++
02
02.01
[1..n]
[1..1]
Text
#EXIT
DMEE_EXIT_SEPA_21
calls small function model where SAP collects the

number
.INCLUDE
CONDITIONAL -TRF or
CHK
TRF would be default for any electronic transfer.

CHK for check.
DOC1T
Text
Code
Tag Only
DTKID(T012D)
PaymentInformation
ZORT2
Tag Only
Qualifies the ID above. Customer Customization needed if this
field is to be populated.
determine the value which is presented in the Cd
element. See attached information for the usage
of BICorBEI element.
#EXIT
Tag Only
PaymentInformationIdentification PaymentInformationId
entification
99
2.2
PaymentMethod
PaymentMethod
<PmtMtd>
++
02.02
[1..1]
Code
R - TRF
R - TRF R - CHK
R - TRF
#CONST
2.3
BatchBooking
BatchBooking
<BtchBookg>
++
02.03
[0..1]
Indicator
BD
BD
BD
SO
Required
2.4
<NbOfTxs>
++
02.04
[0..1]
Text
BD
BD
BD
Total number of transactions

within a Payment Information
batch.
Aggregation
May or may not be supported by a particular bank. Default should

be to not convey this element unless the user requires it for a
specific transfer and would then need to be a customization. If it
is used, there is no consistency amongst the banks as to using
"true" or "false."
Note that this is within the batch, not the message.
<CtrlSum>
++
02.05
[0..1]
Quantity
BD
BD
BD
It is a client's option to include.

If included, value will be
checked. The sum is the hash
total of values in Instructed
Amount or Equivalent Amount.
Aggregation
Note that this is within the batch, not the message.
<PmtTpInf>
++
02.06
[0..1]
BD
BD
NU
NU
101
102
2.5
ControlSum
2.6
PaymentTypeInformation
ControlSum
103
104
PaymentTypeInformati
on
2.7
InstructionPriority
InstructionPriority
<InstrPrty>
+++
02.06.01
[0..1]
2.8
ServiceLevel
ServiceLevel
<SvcLvl>
+++
02.06.02
[0..1]
Code
Required at either Payment or

Transaction Level, but should
not be present at both levels.
Recommnded usage is at
Payment level.
Based on whether priority

processing vs. normal
processing is offered by the
bank.
If an instrument or country is
105
R
not listed on Appendix A,

agreement will be bilateral until
included on the list.
106
2.9
107
Use UTC with offset for all date/time
Tag Only
This is not typically sent. If a customer wants to send one of the
four code values that are specified in the supporting XSD Schema,
they must implement a customization.
34
100
Total number of transactions in

the entire message.
It is a client's option to include.
If included, value will be
checked. The sum is the hash
total of values in Instructed
Amount or Equivalent Amount.
Identifier
30
98
Tag Only
14
16
SAP Source and Field

Source Structure
FPAYHX
SYSTEM
12
15
Tag Only
11
13
DateTim
e
9
10
V3 Implementation Guide
4
5
{Or
Code
Code
<Cd>
++++
02.06.02.01
[1..1]
Code
XOR
XOR
NU
R - SEPA
If <Cd> is populated, <Prtry>

should not be populated. A
code from the external code list
should be used.
Page 13 of 25
Tag Only
FPAYHX
DTURG
Map to the two code values in the schema codes if marked as DTURG=HIGH, otherwise
=NORM
RWSKT
Constant value in SAP system. SAP will only

Tag Only
support at the payment level for SEPA, otherwise
will be at transaction level.
Filled with value SEPA SAP will only support at the payment level
if this is SEPA payment for SEPA, otherwise will be at transaction
level.
Conditional. See CGI Note in Column O.
2
3

ISO
Or
Index
No.
2.10
Or}
Message Item
Proprietary

Indented)

Sequence Number
Mult.
Type
Text
Proprietary
<Prtry>
++++
02.06.02.02
[1..1]
2.11
LocalInstrument
LocalInstrument
<LclInstrm>
+++
02.06.03
[0..1]
NU
If <Prtry> is populated, <Cd>

should not be populated. The
Required
condition is based on the need
to use a proprietary code not on
the external code list per
bilateral agreement.
Tag Only
ONCL =
overnight
clearing
SDCL =
same day
clearing

Combination Support
Value List
and User Customization
should be used.
Code
<Cd>
++++
02.06.03.01
[1..1]
Code
XOR
XOR
NU
2.13
Or}
Proprietary
Proprietary
<Prtry>
++++
02.06.03.02
[1..1]
Text
XOR
XOR
C - Check
Issuance
(CII)
CategoryPurpose
<CtgyPurp>
+++
02.06.04
[0..1]
NU
Conditional based on country

payment instrument. If
<CtgyPurp> is used, one of
<Cd> or <Prtry> must be used.
110
Source Field

Required
111
112
{Or
Code
Code
<Cd>
++++
02.06.04.01
[1..1]
Code
XOR
XOR
NU

Combination Support
Use Instruction Keys
should be used.
2.16
Or}
Proprietary
Proprietary
<Prtry>
++++
02.06.04.02
[1..1]
Text
XOR
XOR
NU

Required
<ReqdExctnDt>
++
02.07
[1..1]
113
114
RequestedExecutionD
ate
2.19
9.1.0
9.1.1
Debtor
Name
PostalAddress
Debtor
Name
PostalAddress
++
+++
+++
02.09
02.09.01
02.09.02
[1..1]
[0..1]
[0..1]
Text
Conditional. See CGI Note in Column O. ISO 20022 External Code

List. Two values for SEPA. Some countries for some payment types
is required. From US NAC HA perspective, typically only see CCD,
IAT, CTX, PPD. Also need to support Sweden, Austria, and
Denmark codes (See appendix B). ISO 20022 External Code List.
Conditional. See CGI Note in Column O. If customer wants to use
this element for check issuance there is a CGI code for that.
Will be a mix of customization and use

instruction keys. SAP will provide support in
instruction keys (instrution key configuration
(V_T015V) for most common codes as identified
in the mapping discussions. The implementation
guidence explains how the customer can
customize the instruction key.
Conditional. See CGI Note in Column O. Customization by User.
CGI will be creating a dynamic code list for additional proprietary
codes. However, this might be quite dynamic so users will need to
use Proprietary as an interim.
FPAYH or FPM_CGI
AUSFD or
DUEDATE_CGI
FPAYHX
NAMEZ
DateTim
e
<Dbtr>
<Nm>
<PstlAdr>
SAP will use Payment supplement to

preconfigure those values that were defined by
the CGI representatives as most used. The
customer will be able to customize for additional
values that might be required. The preconfigured
values are:
TRF;IN;ONCL;SDCL;CCD;CTX;IAT;PPD
Tag Only
2.15
RequestedExecutionDate
General Comments
XOR
Code
2.17
XOR
{Or
115
RULES
2.12
CategoryPurpose

Source Structure

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
109
2.14
ACH Domestic
& Int'l
108
117
118
4
5
Atoms. If the user dont specify a Date the

executaion date will be set as default.
CRVAL
Tag Only
RECOMMENDATION IN ORDER
OF PREFERENCE:
1. Use only structured address.
2. When using combination of
both structured address and
Address Line, must use
structured tags for post code (if
applicable), city, country
subdivision (if applicable), and
country and only 2 lines of
Address Line (to include street
address).
3. Use only Address Line (up to
7 lines; instrument by
instrument limitations may
apply)
119
PAYGR
SAP Supports Structured.
Tag Only
NOTE: PO Box should only

appear in Address Line.
120
121
122
123
124
125
126
127
128
129
130
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.8
9.1.9
9.1.10
9.1.11
9.1.12
9.1.13 {Or
131
AddressType
Department
SubDepartment
StreetName
BuildingNumber
PostCode
TownName
CountrySubDivision
Country
AddressLine
Identification
AddressType
Department
SubDepartment
StreetName
BuildingNumber
PostCode
<AdrTp>
<Dept>
<SubDept>
<StrtNm>
<BldgNb>
<PstCd>
++++
++++
++++
++++
++++
++++
02.09.02.01
02.09.02.02
02.09.02.03
02.09.02.04
02.09.02.05
02.09.02.06
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Code
Text
Text
Text
Text
Text
NU
NU
NU
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
TownName
CountrySubDivision
Country
AddressLine
Identification
<TwnNm>
<CtrySubDvsn>
<Ctry>
<AdrLine>
<Id>
++++
++++
++++
++++
+++
02.09.02.07
02.09.02.08
02.09.02.09
02.09.02.10
02.09.03
[0..1]
[0..1]
[0..1]
[0..7]
[0..1]
Text
Text
Code
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
2 lines
<OrgId>
++++
02.09.03.01
[1..1]
O - XOR
Only 1
allowed
R
OrganisationIdentification
WEFAE
WEAMX
WEFMX
WEFRS
.INCLUDE
RZAWE
Not Used
See recommendation above.

Country dependent
Country dependent
Conditional on country payment
instrument.
OrganisationIdentificat
ion
Page 14 of 25
Not currently supported

Not currently supported
FPAYHX
REF01
FPAYHX
REF01(60)
FPAYHX
REF01(80)
FPAYHX
FPAYHX
FPAYHX
FPAYHX
ORT1Z
REF01(90)
LAND1
AUST1-2
Read Out from central address management

UZAWE
AVISG
INTRACO
FORMZ
Tag Only
Tag Only
2
3

132
133
4
5
ISO
Or
Index
No.
Message Item
9.1.14
BICOrBEI

Indented)
BICOrBEI
<BICOrBEI>

Sequence Number
+++++
02.09.03.01.01
Mult.
Type
[0..1]
ACH Domestic
& Int'l

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
RULES
Other
Identification
Other
Identification
<Othr>
<Id>
+++++
++++++
SchemeName
Code
<SchmeNm>
<Cd>
Proprietary
02.09.03.01.02
02.09.03.01.02.01

Source Structure
General Comments
Source Field
Required
Identifier
9.1.15
9.1.16
Customer Customization Required
[0..n]
[1..1]
Text
++++++ 02.09.03.01.02.02
+++++++ 02.09.03.01.02.02.01
[0..1]
[1..1]
BD
BD
BD
Code
XOR
XOR
XOR

#EXIT
should be used.
<Prtry>
+++++++ 02.09.03.01.02.02.02
[1..1]
Text
XOR
XOR
XOR

Required
Issuer
<Issr>
++++++
02.09.03.01.02.03
[0..1]
Text
NU
NU
NU
CountryOfResidence
ContactDetails
NamePrefix
<CtryOfRes>
<CtctDtls>
<NmPrfx>
+++
+++
++++
02.09.04
02.09.05
02.09.05.01
[0..1]
[0..1]
[0..1]
Code
FPAYHX
LAND1
BD
BD
BD
Code
BD
BD
BD
FPAYH
SALUT
Name
PhoneNumber
MobileNumber
FaxNumber
EmailAddress
Other
DebtorAccount
Identification
<Nm>
<PhneNb>
<MobNb>
<FaxNb>
<EmailAdr>
<Othr>
<DbtrAcct>
<Id>
++++
++++
++++
++++
++++
++++
++
+++
02.09.05.02
02.09.05.03
02.09.05.04
02.09.05.05
02.09.05.06
02.09.05.07
02.10
02.10.01
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[1..1]
[1..1]
Text
Text
Text
Text
Text
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
NAMP1
TELF1
TELF2
TELFX
INTAD
BD
BD
BD
FPAYH
FPAYH
FPAYH
FPAYH
FPAYH
Not Currently Supported
IBAN
<IBAN>
++++
02.10.01.01
[1..1]
XOR
XOR
XOR
R-XOR
XOR
XOR
XOR
R-XOR
BD
BD
BD
Code
BD
BD
BD

determine the Identification. See attached
information for usage of BICorBEI element.
#EXIT
Tag Only
This is required in some countries (See CGI Appendix B).
134
135
9.1.17
9.1.18 {{Or
SchemeName
Code
9.1.19 Or}}
Proprietary
136
137
9.1.20
Issuer
9.1.33
9.1.34
9.1.35
CountryOfResidence
ContactDetails
NamePrefix
Tag Only
Codes are enumerated in external code list. This identifies the
type of identifier.
determine the value which is presented in the Cd
element. See attached information for the usage
of BICorBEI element.
ID_CODE
#EXIT

determine the Institution which is presented in
the Cd element. See attached information for
the usage of BICorBEI element.
138
151
152
Only used if Other (line 134) is populated and only for SEPA.
This is the Country Code of the physical location of the party.

Tag Only
See Implementation Note 1665873 for user
requirements to maintain this element.
ORIG_RE
153
154
155
156
157
158
159
160
161
9.1.36
9.1.37
9.1.38
9.1.39
9.1.40
9.1.41
2.20
1.1.0
1.1.1
Name
PhoneNumber
MobileNumber
FaxNumber
EmailAddress
Other
DebtorAccount
Identification
{Or
IBAN
ORIG_RE
ORIG_IBA
ORIG_BIC
SND_DEB
Tag Only
Tag Only
Either <IBAN> or <Othr> must

be populated.
FPAYHX
UIBAN
FPAYHX
UBKNT
Identifier
162
163
164
165
166
167
168
169
1.1.2
1.1.3
1.1.4
1.1.5
Or}
1.1.6
Or}}
{{Or
Other
Identification
SchemeName
Code
Proprietary
1.1.7
Issuer
1.1.8
1.1.9
<Othr>
<Id>
<SchmeNm>
<Cd>
++++
+++++
+++++
++++++
02.10.01.02
02.10.01.02.01
02.10.01.02.02
02.10.01.02.02.01
[1..1]
[1..1]
[0..1]
[1..1]
Proprietary
<Prtry>
++++++
02.10.01.02.02.02
[1..1]
Text
BD
BD
BD
Issuer
<Issr>
+++++
02.10.01.02.03
[0..1]
Text
BD
BD
BD
Text
Type
<Tp>
+++
02.10.02
[0..1]
Code
<Cd>
++++
02.10.02.01
[1..1]
Code
XOR
XOR
XOR
Proprietary
Proprietary
<Prtry>
++++
02.10.02.02
[1..1]
Text
XOR
XOR
XOR
Currency
Name
DebtorAgent
<Ccy>
<Nm>
<DbtrAgt>
+++
+++
++
02.10.03
02.10.04
02.11
[0..1]
[0..1]
[1..1]
Code
Text
NU
NU
NU
170
1.1.10 Or}
1.1.11
1.1.12
2.21
Currency
Name
DebtorAgent
Tag Only
20022 External Code List - 3 codes. BBAN, CUID, UPIC.
Country-Dependent. See
Appendix B.
FPAYHX
code from the list in the schema
should be used.
Generally not used. If user requires then a customer customization

will be required.
SchemeAgencyName Generally not used
Tag Only
UBKON

Required
the schema code list per
171
172
173
174
Tag Only
Required
Required
Required
Code
Type
{Or
Other
Identification
SchemeName
Code
FPAYHX
UBWAE
Control Key. (note - Control Key also carries

check digit in some countries. ) SAP will map to
4 digit codes CACC, CASH, SVGS only. If the
customer wants to use any of the other current
13 codes, it will require customer customization,
and SAP will provide guidance.
SAP to ensure it provides guidance to customers
on how to customize this field.
Currency the account is maintained in - See ISO 4217

Tag Only
Page 15 of 25
2
3

ISO
Or
Index
No.
6.1.0
175
6.1.1
Message Item

Indented)
FinancialInstitutionIdentification
FinancialInstitutionIde
ntification
BIC
BIC

Sequence Number
Mult.
6.1.2
Type
ACH Domestic
& Int'l

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
<FinInstnId>
+++
02.11.01
[1..1]
<BIC>
++++
02.11.01.01
[0..1]
<ClrSysMmbId>
++++
02.11.01.02
[0..1]
<ClrSysId>
+++++
02.11.01.02.01
[0..1]
BD
BD
BD
176
6.1.3
ClearingSystemIdentification
178
Code
<Cd>
++++++
02.11.01.02.01.01
[1..1]
Code
XOR
XOR
XOR
6.1.5
Or}
Proprietary
Proprietary
<Prtry>
++++++
02.11.01.02.01.02
[1..1]
Text
XOR
XOR
XOR
MemberIdentification <MmbId>
+++++
02.11.01.02.02
[1..1]
Text
PostalAddress
Country
<PstlAdr>
<Ctry>
++++
+++++
02.11.01.04
02.11.01.04.09
[0..1]
[0..1]
BranchIdentification
<BrnchId>
+++
02.11.02
[0..1]
BD
BD
BD
O (Region
and Bank
Dependent)
Identification
UltimateDebtor
<Id>
<UltmtDbtr>
++++
++
02.11.02.01
02.13
[0..1]
[0..1]
Text
BD
BD
BD
Text
R - max. 70
char
R
180
192
MemberIdentification
6.1.25
Code
200
201
6.1.26
2.23
Identification
UltimateDebtor
9.1.0
Name
Name
<Nm>
+++
02.13.01
[0..1]
9.1.1
PostalAddress
PostalAddress
<PstlAdr>
+++
02.13.02
[0..1]
230
232
233
234
235
236
237
238
239
240
241
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
Department
SubDepartment
StreetName
BuildingNumber
PostCode
Department
SubDepartment
StreetName
BuildingNumber
PostCode
<Dept>
<SubDept>
<StrtNm>
<BldgNb>
<PstCd>
++++
++++
++++
++++
++++
02.13.02.02
02.13.02.03
02.13.02.04
02.13.02.05
02.13.02.06
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Text
Text
Text
Text
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
O - Ctry
Dpdt
9.1.8
9.1.9
TownName
CountrySubDivision
TownName
CountrySubDivision
<TwnNm>
<CtrySubDvsn>
++++
++++
02.13.02.07
02.13.02.08
[0..1]
[0..1]
Text
Text
BD
BD
BD
BD
BD
BD
9.1.10
9.1.11
Country
AddressLine
Country
AddressLine
<Ctry>
<AdrLine>
++++
++++
02.13.02.09
02.13.02.10
[0..1]
[0..7]
Code
Text
O - Ctry
Dpdt
R
BD
BD
BD
Identification
<Id>
+++
02.13.03
[0..1]
<OrgId>
++++
02.13.03.01
[1..1]
2 lines
(# text to
be
discussed)
O
- XOR
Only 1
allowed
R
<BICOrBEI>
<Othr>
<Id>
<SchmeNm>
<Cd>
+++++
02.13.03.01.01
+++++
02.13.03.01.02
++++++ 02.13.03.01.02.01
++++++ 02.13.03.01.02.02
+++++++ 02.13.03.01.02.02.01
[0..1]
[0..n] Identifier
[1..1] Text
[0..1]
[1..1] Code
BD
BD
BD
XOR
XOR
XOR
9.1.12
9.1.13 {Or
Identification
247
General Comments
USWIF
Tag Only

Required
should be used.
External Code List. 5 character code depends upon the country

that has applied for registration of their clearing system. Not all
countries are listed, and some countries have multiple codes
representing their different systems. If this is required, the
customer will need to implement a customized solution.

Required
If this is required then customer will need to implement a

customized solution.
FPAYHX
UBNKL
FPAYHX
UBISO
FPAYHX
UBRCH
Instrument and Bank

Dependent. The branch code
should be explicitely stated here
versus being combined with
Clearing System Member ID
where it is required by a bank.
Should be populated if in SAP system and BIC

above should also be populated.
Tag Only. Note CGI Note in Column O regarding ignore if provided
Is used for multiple reasons, to including an indication if this is
cross border.
Tag Only
SAP only supports UltimateDebtor at transaction Tag Only

level. If the customer requires this at the
payment level, they must do a customization for
all required elements.
RECOMMENDATION:
apply)
3. If using both structured
address and Address Line, must
use post code (if applicable,
city, country subdivision (if
applicable), and country and
only 2 lines of Address Line.
4. PO Box should appear in
unstructured address.
See recommendation
See recommendation
See recommendation
See recommendation
See recommendation
Country dependent
See recommendation
Country dependent
Tag Only
above.
above.
above.
above.
above.
Not
Not
Not
Not
Not
Currently
Currently
Currently
Currently
Currently
Supported
Supported
Supported
Supported
Supported
above.




instrument.
Tag Only
Tag Only
ion
242
243
244
245
246
FPAYHX
Conditional based on business

need and payment transaction.
228
229
Source Field
Tag Only
Code
PostalAddress
Country
ClearingSystemIdentifi
cation
{Or
6.1.8
6.1.17
Source Structure
Multiple Ids may be present if

available in originating application.
One identification is required.
6.1.4
6.1.6
RULES
Multiple Ids may be present if

available in originating application.
One identification is required.
Identifier
179
183
Tag Only
ClearingSystemMemberIdentificat ClearingSystemMemb
ion
erIdentification
177
181
4
5
9.1.14
9.1.15
9.1.16
9.1.17
9.1.18 {{Or
BICOrBEI
Other
Identification
SchemeName
Code
BICOrBEI
Other
Identification
SchemeName
Code

Tag Only
Tag Only
should be used.
Page 16 of 25
2
3

ISO
Or
Index
No.
Message Item
9.1.19 Or}}
Proprietary

Indented)
Proprietary
<Prtry>

Sequence Number
Mult.
Type
+++++++ 02.13.03.01.02.02.02
[1..1]
251
9.1.20
9.1.21 Or}
9.1.22
9.1.23
Issuer
PrivateIdentification
DateAndPlaceOfBirth
BirthDate
Issuer
<Issr>
PrivateIdentification <PrvtId>
DateAndPlaceOfBirth <DtAndPlcOfBirth
>
BirthDate
<BirthDt>
++++++
++++
+++++
02.13.03.01.02.03
02.13.03.02
02.13.03.02.01
[0..1]
[1..1]
[0..1]
++++++
02.13.03.02.01.01
[1..1]
RULES
Text
XOR
XOR
XOR

Text
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
9.1.24
9.1.25
9.1.26
9.1.27
9.1.28
9.1.29
9.1.30 {{Or
9.1.31 Or}}
9.1.32
9.1.33
9.1.34
9.1.35
9.1.36
9.1.37
9.1.38
9.1.39
9.1.40
9.1.41
2.24
ProvinceOfBirth
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Code
Proprietary
Issuer
CountryOfResidence
ContactDetails
NamePrefix
Name
PhoneNumber
MobileNumber
FaxNumber
EmailAddress
Other
ChargeBearer
ProvinceOfBirth
CityOfBirth
CountryOfBirth
Other
Identification
SchemeName
Code
Proprietary
Issuer
CountryOfResidence
ContactDetails
NamePrefix
Name
PhoneNumber
MobileNumber
FaxNumber
EmailAddress
Other
ChargeBearer
<PrvcOfBirth>
<CityOfBirth>
<CtryOfBirth>
<Othr>
<Id>
<SchmeNm>
<Cd>
<Prtry>
<Issr>
<CtryOfRes>
<CtctDtls>
<NmPrfx>
<Nm>
<PhneNb>
<MobNb>
<FaxNb>
<EmailAdr>
<Othr>
<ChrgBr>
++++++ 02.13.03.02.01.02
++++++ 02.13.03.02.01.03
++++++ 02.13.03.02.01.04
+++++
02.13.03.02.02
++++++ 02.13.03.02.02.01
++++++ 02.13.03.02.02.02
+++++++ 02.13.03.02.02.02.01
+++++++ 02.13.03.02.02.02.02
++++++ 02.13.03.02.02.03
+++
02.13.04
+++
02.13.05
++++
02.13.05.01
++++
02.13.05.02
++++
02.13.05.03
++++
02.13.05.04
++++
02.13.05.05
++++
02.13.05.06
++++
02.13.05.07
++
02.14
[0..1]
[1..1]
[1..1]
[0..n]
[1..1]
[0..1]
[1..1]
[1..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
NU
Not
Not
Not
Not
Not
Not
Not
Not
Not
Not
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
2.25
1.1.0
1.1.1
ChargesAccount
Identification
IBAN
ChargesAccount
Identification
IBAN
<ChrgsAcct>
<Id>
<IBAN>
++
+++
++++
02.15
02.15.01
02.15.01.01
[0..1]
[1..1]
[1..1]
Other
Identification
SchemeName
Code
<Othr>
<Id>
<SchmeNm>
<Cd>
++++
+++++
+++++
++++++
02.15.01.02
02.15.01.02.01
02.15.01.02.02
02.15.01.02.02.01
[1..1]
[1..1]
[0..1]
[1..1]
Proprietary
<Prtry>
++++++
02.15.01.02.02.02
Issuer
<Issr>
+++++
Type
Code
<Tp>
<Cd>
+++
++++
Proprietary
<Prtry>
Currency
Name
Text
Text
Code
Text
Code
Text
Text
Code
Code
Text
Text
Text
Text
Text
Text
Code
274
275
276
277
278
279
280
281
282
283
284
285
{Or
Or}
{{Or
Other
Identification
SchemeName
Code
1.1.6
Or}}
Proprietary
1.1.7
1.1.8
1.1.9
Issuer
{Or
1.1.10 Or}
1.1.11
1.1.12
326
2.28
2.29
Type
Code
Proprietary
Currency
Name
CreditTransferTransactionInfo CreditTransferTransact
rmation
ionInformation
PaymentIdentification
InstructionIdentification
General Comments
Tag only
Tag only
R
R
O
R
O
O
O
O
Conditional upon country rules
R - SLEV
Conditional based on payment

transaction. Should be used
exclusively at the payment or
transaction level.
2.30
330
2.32
InstructionPriority
PaymentTypeInformati
on
InstructionPriority
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Tag only
This is the physical country of residence of the Ultimate Debtor.

Tag Only
DTKVS
SAP supports this for SEPA at the payment level

and for the other types of transactions at the
transaction level. Key Values are converted to
codes in the application logic.
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
Code
BD
BD
BD
[1..1]
Text
BD
BD
BD
02.15.01.02.03
[0..1]
Text
BD
BD
BD
02.15.02
02.15.02.01
[0..1]
[1..1]
BD
BD
BD
Code
BD
BD
BD
++++
02.15.02.02
[1..1]
Text
BD
BD
BD
<Ccy>
<Nm>
+++
+++
02.15.03
02.15.04
[0..1]
[0..1]
Code
Text
BD
BD
BD
BD
BD
BD
<CdtTrfTxInf>
++
02.17
[1..n]
+++
++++
02.17.01
02.17.01.01
[1..1]
[0..1]
Text
BD
BD
BD
If present, Id to be returned only FPAYH

to ordering party in account
statement reporting
DOC1T-DOC1R
SAP will support the standard 24 Digit SAP

system generated Document Number consisting
of company code, payment run and document
number. If customer requires something else,
then customer customization will be required.
<EndToEndId>
++++
02.17.01.02
[1..1]
Text
Payment Reference - goes with

payment from debtor to
creditor and travels through
clearing system
TEXT (2)
SAP supports 10 characters as our standard out MANDATORY. Needs to be unique for every transaction sent across
of the box. Reference &FPAYH-DOC1R+4(10)& or an enterprise over a certain time - best practice suggestion is 12
constant NOTPROVIDED.
months. Companies may have issues with other clearing systems
that limit field length to something less (e.g. 10 or 12 characters)
and need to have flexibility to customize length for local markets).
<PmtTpInf>
+++
02.17.02
[0..1]
Required at either Payment or

Transaction Level, but should
not be present at both levels.
Recommnded usage is at
Payment level.
<InstrPrty>
++++
02.17.02.01
[0..1]
BD
BD
NU
Required
Text
Code
Tag Only
Tag Only
SAP IMS issuing Workaround note

Tag Only
FPAYHX
DTGBK
Tag Only
Generally not used.
Required
Required
Required
Generally not used.

Generally not used.
Tag Only
Generally not used.
Required
Required
FPAYHX
DTGIS
Required
329
PaymentTypeInformation
Not Currently
Not Currently
Not Currently
Not Currently
Not Currently
Not Currently
Not Currently
FPAYHX
Tag only
BD
EndToEndIdentification
2.31
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
BD
PaymentIdentification <PmtId>
<InstrId>
EndToEndIdentification
Currently
Currently
Currently
Currently
Currently
Currently
Currently
Currently
Currently
Currently
NU
InstructionIdentificatio
n
328
331
Source Field
Identifier
1.1.2
1.1.3
1.1.4
1.1.5
2.27
327
Source Structure
C - CRED,
CDEBT,
CRED,
SHAR, SLEV DEBT,
SHAR
271
272
273

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
DateTim
e
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
ACH Domestic
& Int'l
248
249
250
4
5
Generally not used.
Generally not used.

Tag Only
Based on whether priority

processing vs. normal
processing is offered by the
bank.
Page 17 of 25
DMEE_PAYD
SAP supports at transaction level for payment

type.
FPAYHX
DTURG
Within the instruction key maintenance the tick

box could be set for urgent payments. If it is set
'HIGH' will be present otherwise 'NORM' if the
instruction key is maintained.
Tag Only
Needs to be unique over a certain time period per customer.
Tag Only. Service Level and local instrument should be paired

together under the payment type information.
2
3

ISO
Or
Index
No.
2.33
Message Item
ServiceLevel

Indented)

Sequence Number
Mult.
ServiceLevel
<SvcLvl>
++++
02.17.02.02
[0..1]
Type

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
RULES
NU
R - SEPA

FPAYH
should be used.
2.34
{Or
Code
Code
<Cd>
+++++
02.17.02.02.01
[1..1]
Code
XOR
XOR
NU
2.35
Or}
Proprietary
Proprietary
<Prtry>
+++++
02.17.02.02.02
[1..1]
Text
XOR
XOR
NU
LocalInstrument
<LclInstrm>
++++
02.17.02.03
[0..1]
333
LocalInstrument
<Cd>
+++++
02.17.02.03.01
[1..1]
Code
XOR
XOR
NU
2.38
Or}
Proprietary
Proprietary
<Prtry>
+++++
02.17.02.03.02
[1..1]
Text
XOR
XOR
C - Check
Issuance
(CII)
CategoryPurpose
<CtgyPurp>
++++
02.17.02.04
[0..1]
NU

payment instrument. If
<CtgyPurp> is used, one of
<Cd> or <Prtry> must be used.

Required
348
349
Code
Code
<Cd>
+++++
02.17.02.04.01
[1..1]
Code
XOR
XOR
NU

FPAYH
should be used.
2.41
Or}
Proprietary
Proprietary
<Prtry>
+++++
02.17.02.04.02
[1..1]
Text
XOR
XOR
NU

Required
2.42
2.43
Amount
InstructedAmount
Amount
InstructedAmount
+++
++++
02.17.03
02.17.03.01
[1..1]
[1..1]
Amount
XOR
XOR
XOR
EquivalentAmount
Amount
EquivalentAmount
Amount
<Amt>
<InstdAmt
Ccy="AAA">
<EqvtAmt>
<Amt
Ccy="AAA">
<CcyOfTrf>
<XchgRateInf>
{Or
++++
+++++
02.17.03.02
02.17.03.02.01
[1..1]
[1..1]
XOR
XOR
XOR
Amount
#EXIT
DMEE_EXIT_CGI_EQVTAMT
+++++
+++
02.17.03.02.02
02.17.04
[1..1]
[0..1]
Code
#EXIT
DMEE_EXIT_CGI_CCYOFTRF
BD
BD
BD
2.44
2.45
2.46
2.47
Or}
CurrencyOfTransfer
ExchangeRateInformation
CurrencyOfTransfer
352
353
354
DTWS1
Will be a mix of customization and use

instruction keys. SAP will provide support in
instruction keys (instrution key configuration
(V_T015V) for most common codes as identified
in the mapping discussions. The implementation
guidence explains how the customer can
customize the instruction key.
RWBTR
with Currency attribute FPAYHX-WAERS
Tag Only
FPAYH
Tag Only
Tag Only
ExchangeRateInformat
ion
2.48
ExchangeRate
ExchangeRate
<XchgRate>
++++
02.17.04.01
[0..1]
Rate
BD
BD
BD
2.49
RateType
RateType
<RateTp>
++++
02.17.04.02
[0..1]
Code
BD
BD
BD
ContractIdentification
BD
BD
ContractIdentification <CtrctId>
++++
02.17.04.03
[0..1]
Text
BD
2.51
ChargeBearer
ChargeBearer
<ChrgBr>
+++
02.17.05
[0..1]
Code
C - CRED,
CDEBT,
CRED,
SHAR, SLEV DEBT,
SHAR
NU
2.52
ChequeInstruction
ChequeInstruction
<ChqInstr>
+++
02.17.06
[0..1]
NU
NU
2.53
ChequeType
ChequeType
<ChqTp>
++++
02.17.06.01
[0..1]
Code
NU
NU
2.54
ChequeNumber
ChequeNumber
<ChqNb>
++++
02.17.06.02
[0..1]
Text
NU
NU
R - BCHQ,
CCHQ,
DRFT
C
2.55
ChequeFrom
ChequeFrom
<ChqFr>
++++
02.17.06.03
[0..1]
NU
NU
2.50
350
351
Tag Only
{Or
346
347
SAP will use Payment supplement to

preconfigure those values that were defined by
the CGI representatives as most used. The
customer will be able to customize for additional
values that might be required. Preconfigured
values are: TRF, IN, ONCL, SDCL, CCD, CTX, IAT,
PPD
2.40
340
345
Instruction keys needs to be maintained to be

able to use the code values.

Combination Support
Value List
should be used.
Code
339
344
DTURG or DTWS1
ONCL =
overnight
clearing
SDCL =
same day
clearing
Code
338
343
Tag Only
Tag Only
337
342
General Comments
{Or
CategoryPurpose
Source Field
2.37
2.39
335
336
Source Structure

Required
334
2.36
ACH Domestic
& Int'l
332
341
4
5
R - SLEV
Conditional based on payment

transaction. Should be used
exclusively at the payment or
transaction level.
Required
Required
Required
FPAYHX
DTKVS
FPAYH
Required only for Customer
FPAHX
Cheques
Populated only if info different
from Debtor/Ultimate Debtor;
assumes Ultimate Debtor takes
precedence over Debtor if
populated.
Page 18 of 25
DTWS
For SEPA, SLEV is the only valid value and SAP

only supports at the payment level. The other
three codes are supported at this transaction
level using instruction key table.
Instruction Key T015W indicates Bank Check or

Local Check.
Tag Only. Only applicable when a check or draft is asked to be

generated by the bank.
CGI allowed values are BCHQ, CCHQ, DRFT.
CHECK
Tag Only
2
3

355
ISO
Or
Index
No.
Message Item

Indented)

Sequence Number
Mult.
Type
Text
2.56
Name
Name
<Nm>
+++++
02.17.06.03.01
[1..1]
2.57
Address
Address
<Adr>
+++++
02.17.06.03.02
[1..1]
ACH Domestic
& Int'l

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
NU
NU
NU
NU
356
357
358
359
360
361
362
363
364
365
366
367
<AdrTp>
++++++
02.17.06.03.02.01
[0..1]
Code
NU
NU
NU
<Dept>
++++++
02.17.06.03.02.02
[0..1]
Text
NU
NU
BD
10.1.2
SubDepartment
SubDepartment
<SubDept>
++++++
02.17.06.03.02.03
[0..1]
Text
NU
NU
BD
10.1.3
StreetName
StreetName
<StrtNm>
++++++
02.17.06.03.02.04
[0..1]
Text
NU
NU
BD
10.1.4
BuildingNumber
BuildingNumber
<BldgNb>
++++++
02.17.06.03.02.05
[0..1]
Text
NU
NU
BD
10.1.5
PostCode
PostCode
<PstCd>
++++++
02.17.06.03.02.06
[0..1]
Text
NU
NU
BD
10.1.6
TownName
TownName
<TwnNm>
++++++
02.17.06.03.02.07
[0..1]
Text
NU
NU
BD

Country dependent
10.1.7
CountrySubDivision
CountrySubDivision
<CtrySubDvsn>
++++++
02.17.06.03.02.08
[0..1]
Text
NU
NU
BD
Country dependent
10.1.8
Country
Country
<Ctry>
++++++
02.17.06.03.02.09
[0..1]
Code
NU
NU
10.1.9
AddressLine
AddressLine
<AdrLine>
++++++
02.17.06.03.02.10
[0..7]
Text
NU
NU
BD
DeliveryMethod
<DlvryMtd>
++++
02.17.06.04
[0..1]
NU
NU
Populated to advise how

cheque/draft is to be delivered
FPAYH
should be used.
376
377
Customization
Customization
Customization
Customization
Customization
Customization
Customization
Customization
Customization
Tag Only
Code
Code
<Cd>
+++++
02.17.06.04.01
[1..1]
Code
NU
NU
XOR
2.60
Or}
Proprietary
Proprietary
<Prtry>
+++++
02.17.06.04.02
[1..1]
Text
NU
NU
XOR

Required
DeliverTo
<DlvrTo>
++++
02.17.06.05
[0..1]
NU
NU
Populated only if info different

from Creditor/Ultimate Creditor;
assumes Ultimate Creditor takes
precedence over Creditor if
populated.
NU
NU
NU
NU
2.62
Name
Name
<Nm>
+++++
02.17.06.05.01
[1..1]
2.63
Address
Address
<Adr>
+++++
02.17.06.05.02
[1..1]
Text
General Comments
Customization
{Or
372
375
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
2.59
DeliverTo
Source Field
Tag Only
Department
2.61
Required
AddressType
DeliveryMethod
RECOMMENDATION:
apply)
Department
2.58

Source Structure
AddressType
370
374
RULES
10.1.1
369
373
10.1.0
368
371
4
5
DTWS*
Use Instruction Keys. Can define additional

instructions including code for the delivery
method.
Tag Only
Required
RECOMMENDATION:
apply)
10.1.0
AddressType
AddressType
<AdrTp>
++++++
02.17.06.05.02.01
[0..1]
Code
NU
NU
NU
10.1.1
Department
Department
<Dept>
++++++
02.17.06.05.02.02
[0..1]
Text
NU
NU
BD
10.1.2
SubDepartment
SubDepartment
<SubDept>
++++++
02.17.06.05.02.03
[0..1]
Text
NU
NU
BD
10.1.3
StreetName
StreetName
<StrtNm>
++++++
02.17.06.05.02.04
[0..1]
Text
NU
NU
BD
10.1.4
BuildingNumber
BuildingNumber
<BldgNb>
++++++
02.17.06.05.02.05
[0..1]
Text
NU
NU
BD
Page 19 of 25
Tag Only
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customization
Customization
Customization
Customization
Customization
2
3

378
379
380
381
382
383
ISO
Or
Index
No.

Indented)
Message Item

Sequence Number
Mult.
Type
386
387
388
389

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
RULES

Country dependent
PostCode
PostCode
<PstCd>
++++++
02.17.06.05.02.06
[0..1]
Text
NU
NU
BD
10.1.6
TownName
TownName
<TwnNm>
++++++
02.17.06.05.02.07
[0..1]
Text
NU
NU
BD
10.1.7
CountrySubDivision
CountrySubDivision
<CtrySubDvsn>
++++++
02.17.06.05.02.08
[0..1]
Text
NU
NU
BD
10.1.8
Country
Country
<Ctry>
++++++
02.17.06.05.02.09
[0..1]
Code
NU
NU
10.1.9
AddressLine
AddressLine
<AdrLine>
++++++
02.17.06.05.02.10
[0..7]
Text
NU
NU
BD
++++
++++
02.17.06.06
02.17.06.07
[0..1]
[0..1]
Code
NU
NU
BD
NU
NU
2.64
2.65
InstructionPriority
ChequeMaturityDate
InstructionPriority
<InstrPrty>
ChequeMaturityDate <ChqMtrtyDt>
Source Structure
Customer
Required
Customer
Required
Country dependent
Customer
Required
Customer
Country dependent
Required
Customer
Required
FPAYHX
If the instrument has a maturity FPAYH
date.
DateTim
e
2.66
FormsCode
FormsCode
<FrmsCd>
++++
02.17.06.08
[0..1]
Text
NU
NU
BD
2.67
MemoField
MemoField
<MemoFld>
++++
02.17.06.09
[0..2]
Text
NU
NU
BD
2.68
RegionalClearingZone
RegionalClearingZone <RgnlClrZone>
++++
02.17.06.10
[0..1]
Text
NU
NU
BD
2.69
PrintLocation
PrintLocation
<PrtLctn>
++++
02.17.06.11
[0..1]
Text
NU
NU
BD
2.70
UltimateDebtor
UltimateDebtor
<UltmtDbtr>
+++
02.17.07
[0..1]
R - max. 70
char
RECOMMENDATION:
apply)
See recommendation
See recommendation
See recommendation
See recommendation
See recommendation
Country dependent
See recommendation
Country dependent
9.1.0
Name
Name
<Nm>
++++
02.17.07.01
[0..1]
9.1.1
PostalAddress
PostalAddress
<PstlAdr>
++++
02.17.07.02
[0..1]
Text
ACH Domestic
& Int'l
10.1.5
384
385
4
5
398
399
400
401
402
Customization
Customization
Customization
Customization
DTURG
VALUT
Department
SubDepartment
StreetName
BuildingNumber
PostCode
<Dept>
<SubDept>
<StrtNm>
<BldgNb>
<PstCd>
+++++
+++++
+++++
+++++
+++++
02.17.07.02.02
02.17.07.02.03
02.17.07.02.04
02.17.07.02.05
02.17.07.02.06
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Text
Text
Text
Text
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
O - Ctry
Dpdt
9.1.8
9.1.9
TownName
CountrySubDivision
TownName
CountrySubDivision
<TwnNm>
<CtrySubDvsn>
+++++
+++++
02.17.07.02.07
02.17.07.02.08
[0..1]
[0..1]
Text
Text
BD
BD
BD
BD
BD
BD
9.1.10
9.1.11
Country
AddressLine
Country
AddressLine
<Ctry>
<AdrLine>
+++++
+++++
02.17.07.02.09
02.17.07.02.10
[0..1]
[0..7]
Code
Text
O - Ctry
Dpdt
R
BD
BD
BD
Identification
<Id>
++++
02.17.07.03
[0..1]
<OrgId>
+++++
02.17.07.03.01
[1..1]
2 lines
(# text to
be
discussed)
O
- XOR
Only 1
allowed
R
<BICOrBEI>
++++++
02.17.07.03.01.01
[0..1]
9.1.13 {Or
403
404
405
406
407
9.1.14
BICOrBEI
Other
Identification
9.1.17
9.1.18 {{Or
SchemeName
Code
9.1.19 Or}}
Proprietary
BNAME
BICOrBEI
412

FPAYHX
REF01
FPAYHX
REF01(60)
FPAYHX
REF01(80)
above.
FPAYP
FPAYHX
BORT1
REF01(90)
FPAYP
FPAYP
BLAND
BSTRAS

instrument.
Tag Only
Tag Only
Required
Other
Identification
<Othr>
<Id>
++++++ 02.17.07.03.01.02
+++++++ 02.17.07.03.01.02.01
[0..n]
[1..1]
Text
SchemeName
Code
<SchmeNm>
<Cd>
+++++++ 02.17.07.03.01.02.02
++++++ 02.17.07.03.01.02.02.01
++
[0..1]
[1..1]
BD
BD
BD
Code
XOR
XOR
XOR

Required
should be used.
Proprietary
<Prtry>
++++++
++
[1..1]
Text
XOR
XOR
XOR

Required
[0..1]
[1..1]
[0..1]
Text
NU
NU
NU
NU
NU
NU
NU
NU
NU
02.17.07.03.01.02.02.02
409
9.1.20
9.1.21 Or}
9.1.22
Tag Only
above.
above.
above.
above.
above.

Condition check FPAYP-BNAME <> FPAYHXNAMEZ. Sending company code is different than
the paying company code.
ion
408
410
411
Customer can use any Reference field not used

by SAP
Tag Only
FPAYP
Identifier
9.1.15
9.1.16
Value Date is the same as ChequeMaturityDate

Department
SubDepartment
StreetName
BuildingNumber
PostCode
Identification
General Comments
Required
Required
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.12
Customization
Required
FPAYHX
REF*
391
397
Source Field
390
393
394
395
396
Issuer
Issuer
<Issr>
+++++++ 02.17.07.03.01.02.03
PrivateIdentification <PrvtId>
PrivateIdentification
+++++
02.17.07.03.02
DateAndPlaceOfBirth DateAndPlaceOfBirth <DtAndPlcOfBirth ++++++ 02.17.07.03.02.01
>
Generally not used

Tag Only
Required
Tag Only
Not Used
Tag Only
Tag Only
Page 20 of 25
2
3

ISO
Or
Index
No.

Indented)
Message Item
9.1.23
BirthDate
BirthDate
9.1.24
ProvinceOfBirth
9.1.25
CityOfBirth
9.1.26
CountryOfBirth

Sequence Number
Mult.
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
9.1.27
9.1.28
Other
Identification
9.1.29
9.1.30 {{Or
SchemeName
Code
9.1.31 Or}}
Proprietary
9.1.32
Issuer
9.1.33
9.1.34
9.1.35
CountryOfResidence
ContactDetails
NamePrefix
Type
NU
NU
Required
Required
Required
Required
[1..1]
ProvinceOfBirth
<PrvcOfBirth>
+++++++ 02.17.07.03.02.01.02
[0..1]
Text
NU
NU
NU
CityOfBirth
<CityOfBirth>
+++++++ 02.17.07.03.02.01.03
[1..1]
Text
NU
NU
NU
CountryOfBirth
<CtryOfBirth>
+++++++ 02.17.07.03.02.01.04
[1..1]
Code
NU
NU
NU
Other
Identification
<Othr>
<Id>
++++++ 02.17.07.03.02.02
+++++++ 02.17.07.03.02.02.01
[0..n]
[1..1]
NU
NU
NU
NU
NU
NU
Text
SchemeName
Code
<SchmeNm>
<Cd>
[0..1]
[1..1]
NU
NU
NU
NU
NU
NU
Code
Proprietary
<Prtry>
[1..1]
Text
NU
NU
NU
Issuer
<Issr>
+++++++ 02.17.07.03.02.02.02
++++++ 02.17.07.03.02.02.02.01
++
++++++ 02.17.07.03.02.02.02.02
++
+++++++ 02.17.07.03.02.02.03
[0..1]
Text
NU
NU
NU
CountryOfResidence
ContactDetails
NamePrefix
<CtryOfRes>
<CtctDtls>
<NmPrfx>
++++
++++
+++++
02.17.07.04
02.17.07.05
02.17.07.05.01
[0..1]
[0..1]
[0..1]
Code
BD
BD
BD
Code
BD
BD
BD
Name
Name
<Nm>
+++++
02.17.07.05.02
[0..1]
Text
BD
BD
BD
9.1.37
PhoneNumber
PhoneNumber
<PhneNb>
+++++
02.17.07.05.03
[0..1]
Text
BD
BD
BD
9.1.38
MobileNumber
MobileNumber
<MobNb>
+++++
02.17.07.05.04
[0..1]
Text
BD
BD
BD
9.1.39
FaxNumber
FaxNumber
<FaxNb>
+++++
02.17.07.05.05
[0..1]
Text
BD
BD
BD
9.1.40
EmailAddress
EmailAddress
<EmailAdr>
+++++
02.17.07.05.06
[0..1]
Text
BD
BD
BD
9.1.41
Other
Other
<Othr>
+++++
02.17.07.05.07
[0..1]
Text
BD
BD
BD
IntermediaryAgent1
IntermediaryAgent1
<IntrmyAgt1>
+++
02.17.08
[0..1]
BD
BD
NU
++++
02.17.08.01
[1..1]
NU
FinancialInstitutionIde
ntification
<FinInstnId>
FinancialInstitutionIdentification
<BIC>
+++++
02.17.08.01.01
[0..1]
NU
<ClrSysMmbId>
+++++
02.17.08.01.02
[0..1]
NU
<ClrSysId>
++++++
02.17.08.01.02.01
[0..1]
BD
BD
NU
6.1.0
6.1.1
BIC
BIC
6.1.3
ClearingSystemIdentification
436
General Comments
Tag Only
Tag Only
Required
Required
Required
FPAYP
BLAND
Tag Only
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customer
Required
Customization
Customization
Customization
Customization
Customization
Customization
Customization
Might be required for certain

types of payments if an
intermediary is present. Bank
requirements may vary.
Tag Only
Tag Only
FPAYH
BSWIFT1
Note 1625129 needs to be implemented by the

customer in order to be able to use the source
field
Tag Only
Tag Only
ClearingSystemIdentifi
cation
6.1.4
{Or
Code
Code
<Cd>
+++++++ 02.17.08.01.02.01.01
[1..1]
Code
XOR
XOR
NU

Required
should be used.
6.1.5
Or}
Proprietary
Proprietary
<Prtry>
+++++++ 02.17.08.01.02.01.02
[1..1]
Text
XOR
XOR
NU

Required
MemberIdentification <MmbId>
Name
<Nm>
++++++
+++++
[1..1]
[0..1]
Text
Text
NU
NU
NU
NU
PostalAddress
Country
Identification
CreditorAgent
CreditorAgentAccount
Creditor
CreditorAccount
Identification
IBAN
Other
Identification
SchemeName
Code
+++++
02.17.08.01.04
++++++ 02.17.08.01.04.09
++++
02.17.08.02
+++++
02.17.08.02.01
+++
02.17.14
+++
02.17.15
+++
02.17.16
+++
02.17.17
++++
02.17.17.01
+++++
02.17.17.01.01
+++++
02.17.17.01.02
++++++ 02.17.17.01.02.01
++++++ 02.17.17.01.02.02
+++++++ 02.17.17.01.02.02.01
NU
NU
BD
BD
NU
BD
BD
NU
NU
NU
NU
NU
XOR
XOR
NU
XOR
XOR
NU
R-XOR
NU
BD
NU
NU
BD
NU
NU
437
438
440
ClearingSystemMemberIdentificat ClearingSystemMemb
ion
erIdentification
435
439
Source Field
Identifier
6.1.2
Required
432
433

Source Structure
NU
+++++++ 02.17.07.03.02.01.01
DateTim
e
RULES

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
9.1.36
2.71
434
ACH Domestic
& Int'l
<BirthDt>
413
414
4
5
6.1.6
6.1.7
441 6.1.8
450 6.1.17
458 6.1.25
459 6.1.26
594 ###
634 2.78
648 2.79
691 2.80
692 1.1.0
693 1.1.1 {Or
694 1.1.2 Or}
695 1.1.3
696 1.1.4
1.1.5 {{Or
697
MemberIdentification
Name
PostalAddress
Country
Identification
CreditorAgent
CreditorAgentAccount
Creditor
CreditorAccount
Identification
IBAN
Other
Identification
SchemeName
Code
<PstlAdr>
<Ctry>
<BrnchId>
<Id>
<CdtrAgt>
<CdtrAgtAcct>
<Cdtr>
<CdtrAcct>
<Id>
<IBAN>
<Othr>
<Id>
<SchmeNm>
<Cd>
02.17.08.01.02.02
02.17.08.01.03
[0..1]
[0..1] Code
[0..1]
[0..1] Text
[0..1]
[0..1]
[0..1]
[0..1]
[1..1]
[1..1]
[1..1] Identifier
[1..1] Text
[0..1]
[1..1] Code
FPAYHX
REF04
Required
The ID will be filled from the database table

T045T.
Tag Only
FPAYH
BNKS1
Region and Bank Dependent)
Tag Only
Tag
Tag
Tag
Tag
Tag
Conditional base on country

rules.
FPAYH
ZIBAN
FPAYHX
ZBNKN_EXT
Only
Only
Only
Only
Only
Tag Only
Tag Only
Required
Page 21 of 25
2
3

698
699
700
4
5
ISO
Or
Index
No.
1.1.6
Message Item
Mult.
Type
ACH Domestic
& Int'l

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
<Prtry>
+++++++ 02.17.17.01.02.02.02
[1..1]
Text
BD
NU
NU
Issuer
<Issr>
++++++
02.17.17.01.02.03
[0..1]
Text
BD
NU
NU
Type
Code
<Tp>
<Cd>
++++
+++++
02.17.17.02
02.17.17.02.01
[0..1]
[1..1]
NU
Code
XOR
XOR
NU
Proprietary
<Prtry>
+++++
02.17.17.02.02
[1..1]
Text
XOR
XOR
NU
Currency
Currency
<Ccy>
++++
02.17.17.03
[0..1]
Code
BD
BD
NU
Name
Name
<Nm>
++++
02.17.17.04
[0..1]
Text
NU
UltimateCreditor
<UltmtCdtr>
+++
02.17.18
[0..1]
NU
BD
NU
NU
BD
NU
NU
BD
NU
Proprietary
Issuer
{Or

Sequence Number
Proprietary
Or}}
1.1.7
1.1.8
1.1.9

Indented)
Type
Code
Proprietary
705
1.1.12
2.81
UltimateCreditor
2.82
InstructionForCreditorAgent
<InstrForCdtrAgt +++
InstructionForCreditor >
Agent
02.17.19
[0..n]
2.83
2.84
2.85
Code
InstructionInformation
InstructionForDebtorAgent
Code
<Cd>
++++
InstructionInformation <InstrInf>
++++
<InstrForDbtrAgt +++
InstructionForDebtorA >
gent
02.17.19.01
02.17.19.02
02.17.20
[0..1]
[0..1]
[0..1]
2.86
Purpose
748
749
750
Code
Text
Text
<Purp>
+++
02.17.21
[0..1]
Dependent upon Credit Agent

FPAYH
validation
rules; may also be bank
determined.

determined. Can be utilized to
indicate signatures for checks
where required by your bank.
Boletto Bar Code /BRTL/+41
digit bar code
++++
02.17.21.01
[1..1]
Code
XOR
XOR
XOR

FPAYP
should be used.
XREF3
freetext element
2.88
Or}
Proprietary
Proprietary
<Prtry>
++++
02.17.21.02
[1..1]
Text
XOR
XOR
XOR

FPAYP
REF(XX)
See Implementation Note 1665873 on how to

implement a workaround using a text field for
those customers that require this field.
RegulatoryReporting
<RgltryRptg>
+++
02.17.22
[0..10]
SC
02.17.22.01
[0..1]
Code
SC
BD
BD
BD
Text
Code
BD
BD
BD
BD
BD
BD
RegulatoryReporting
DebitCreditReportingIndicator
11.1.1
11.1.2
11.1.3
11.1.4
Authority
Name
Country
Details
11.1.5
11.1.6
Type
Date
<DbtCdtRptgInd ++++
DebitCreditReportingIn >
dicator
Authority
Name
Country
Details
<Authrty>
<Nm>
<Ctry>
<Dtls>
++++
+++++
+++++
++++
02.17.22.02
02.17.22.02.01
02.17.22.02.02
02.17.22.03
[0..1]
[0..1]
[0..1]
[0..n]
Type
Date
<Tp>
<Dt>
+++++
+++++
02.17.22.03.01
02.17.22.03.02
[0..1]
[0..1]
766
767
768
769
11.1.7
11.1.8
11.1.9
11.1.10
2.90
13.1.0
13.1.1
13.1.2
Country
Code
Amount
Country
Code
Amount
Information
Information
Tax
Tax
Creditor
TaxIdentification
RegistrationIdentification
770
771
772
773
Text
Dependent upon
jurisdiction/country
Dependent upon
Tag Only
Tag Only
FPAYP
LANDL
Dependent upon
Tag Only
DateTim
e
762
765
Tag Only
<Cd>
2.89
Tag Only
Not Currently Supported Not Currently

Supported
FPAYP
SGTXT(50)
DMEE_PAYD
TEXT
Code
756
763
764
Tag Only
SAP limits to 4 occurences.
Code
11.1.0
761
KOINH
{Or
754
760
For SEPA must be constant - EUR. Customer

customization if required for other than SEPA
transaction.
2.87
753
757
758
759
Tag Only

determined.
752
755
General Comments
Source is the FPAYH-ZBKON field to map the

control keys to the codelist provided in the
schema.
Constant = EUR for

SEPA.
751
Purpose

Required
703
704
Source Field
Country dependent
#ATOMS
should be used.
702
1.1.11

Source Structure
Required
Required
701
1.1.10 Or}
RULES
13.1.3
13.1.4
13.1.5
TaxType
Debtor
TaxIdentification
Creditor
TaxIdentification
<Ctry>
<Cd>
<Amt
Ccy="AAA">
<Inf>
<Tax>
+++++
+++++
+++++
02.17.22.03.03
02.17.22.03.04
02.17.22.03.05
[0..1]
[0..1]
[0..1]
Code
Text
Amount

+++++
+++
02.17.22.03.06
02.17.23
[0..n]
[0..1]
Text
<Cdtr>
<TaxId>
<RegnId>
++++
+++++
+++++
02.17.23.01
02.17.23.01.01
02.17.23.01.02
[0..1]
[0..1]
[0..1]
CDepends
on Country
O
Text
Text
FPAYH
STCD1
<TaxTp>
<Dbtr>
<TaxId>
+++++
++++
+++++
02.17.23.01.03
02.17.23.02
02.17.23.02.01
[0..1]
[0..1]
[0..1]
Text

Dependent upon
Tag Only
Tag Only
RegistrationIdentificati
on
TaxType
Debtor
TaxIdentification
Text
Tag Only
FPAYHX
Page 22 of 25
STCEG
2
3

ISO
Or
Index
No.
13.1.6
774
775
776
777
778
779
780
781
Message Item

Indented)
RegistrationIdentification
RegistrationIdentificati
on
<RegnId>
TaxType
Authorisation
Title
Name
AdministrationZone
ReferenceNumber
Method
13.1.7
13.1.8
13.1.9
13.1.10
13.1.11
13.1.12
13.1.13
13.1.14
TaxType
Authorisation
Title
Name
AdministrationZone
ReferenceNumber
Method
TotalTaxableBaseAmount
13.1.15
TotalTaxAmount
TotalTaxAmount
13.1.16
Date
Date
782
783
<TaxTp>
<Authstn>
<Titl>
<Nm>
<AdmstnZn>
<RefNb>
<Mtd>
<TtlTaxblBaseAm
TotalTaxableBaseAmou t Ccy="AAA">
nt
<TtlTaxAmt
Ccy="AAA">
<Dt>

Sequence Number
Mult.
Type
803
804
13.1.17
13.1.18
13.1.19
13.1.20
13.1.21
13.1.22
13.1.23
13.1.24
13.1.25
13.1.26
SequenceNumber
SequenceNumber
Record
Record
Type
Type
Category
Category
CategoryDetails
CategoryDetails
DebtorStatus
DebtorStatus
CertificateIdentification
CertificateIdentificatio
FormsCode
FormsCode
Period
Period
Year
Year
<SeqNb>
<Rcrd>
<Tp>
<Ctgy>
<CtgyDtls>
<DbtrSts>
<CertId>
<FrmsCd>
<Prd>
<Yr>
+++++
+++++
++++++
++++++
++++
++++
++++
++++
02.17.23.02.03
02.17.23.02.04
02.17.23.02.04.01
02.17.23.02.04.02
02.17.23.03
02.17.23.04
02.17.23.05
02.17.23.06
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Text
Text
Text
Text
Text
Text
Amount
Not
Not
Not
Not
Not
Not
++++
02.17.23.07
[0..1]
Amount
++++
02.17.23.08
[0..1]
807
13.1.27
13.1.28
13.1.29
Type
FromToDate
FromDate
Type
FromToDate
FromDate
<Tp>
<FrToDt>
<FrDt>
ToDate
ToDate
13.1.31
13.1.32
13.1.33
Supported
Supported
Supported
Supported
Supported
Supported
++++
++++
+++++
+++++
+++++
+++++
+++++
+++++
+++++
++++++
02.17.23.09
02.17.23.10
02.17.23.10.01
02.17.23.10.02
02.17.23.10.03
02.17.23.10.04
02.17.23.10.05
02.17.23.10.06
02.17.23.10.07
02.17.23.10.07.01
[0..1]
[0..n]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Quantity
Text
Text
Text
Text
Text
Text
Tag Only
Not
Not
Not
Not
Not
Not
Currently
Currently
Currently
Currently
Currently
Currently
Supported
Supported
Supported
Supported
Supported
Supported
Tag Only
++++++ 02.17.23.10.07.02
++++++ 02.17.23.10.07.03
+++++++ 02.17.23.10.07.03.01
[0..1]
[0..1]
[1..1]
Code
Tag Only
+++++++ 02.17.23.10.07.03.02
[1..1]
TaxAmount
TaxAmount
Rate
Rate
TaxableBaseAmount TaxableBaseAmount
+++++
++++++
++++++
02.17.23.10.08
02.17.23.10.08.01
02.17.23.10.08.02
[0..1]
[0..1]
[0..1]
Rate
Amount

++++++
02.17.23.10.08.03
[0..1]
Amount
++++++ 02.17.23.10.08.04
+++++++ 02.17.23.10.08.04.01
++++++ 02.17.23.10.08.04.01.01
++
[0..n]
[0..1]
[0..1]
++++++
++
++++++
++
++++++
+++
02.17.23.10.08.04.01.02
[0..1]
02.17.23.10.08.04.01.03
[0..1]
02.17.23.10.08.04.01.03.01
[1..1]
++++++
+++
02.17.23.10.08.04.01.03.02
[1..1]
13.1.34
TotalAmount
TotalAmount
13.1.35
13.1.36
13.1.37
Details
Period
Year
Details
Period
Year
<TaxAmt>
<Rate>
<TaxblBaseAmt
Ccy="AAA">
<TtlAmt
Ccy="AAA">
<Dtls>
<Prd>
<Yr>
13.1.38
Type
Type
<Tp>
13.1.39
FromToDate
FromToDate
<FrToDt>
13.1.40
FromDate
FromDate
<FrDt>
13.1.41
ToDate
ToDate
<ToDt>
13.1.42
Amount
<Amt
Ccy="AAA">
AdditionalInformation <AddtlInf>
<RltdRmtInf>
RelatedRemittanceInfo
rmation
Tag Only
Tag Only
Tag Only
DateTim
e
Code
Tag Only
DateTim
e
DateTim
e
Amount
[1..1]
+++++
+++
02.17.23.10.09
02.17.24
[0..1] Text
[0..10]
BD
BD
BD
<RmtId>
++++
02.17.24.01
[0..1]
Text
BD
BD
BD
<RmtLctnMtd>
++++
02.17.24.02
[0..1]
Code
BD
BD
BD
2.94
<RmtLctnElctrnc ++++
RemittanceLocationElectronicAddr RemittanceLocationEle Adr>
ess
ctronicAddress
02.17.24.03
[0..1]
Text
BD
BD
BD
2.95
<RmtLctnPstlAdr ++++
RemittanceLocationPostalAddress RemittanceLocationPo >
stalAddress
02.17.24.04
[0..1]
BD
BD
BD
02.17.24.04.01
[1..1]
2.92
Amount
DateTim
e
+++++++ 02.17.23.10.08.04.02
13.1.43
2.91
812
AdditionalInformation
RelatedRemittanceInformation
RemittanceIdentification
813
RemittanceIdentificati
on
2.93
RemittanceLocationMethod
814
815
816
817
General Comments
Tag Only
Currently
Currently
Currently
Currently
Currently
Currently
<ToDt>
809
811
Source Field
DateTim
e
808
810
DateTim
e
805
806

Source Structure
DateTim
e
13.1.30
802
RULES
Text
798
801

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
[0..1]
797
799
800
ACH Domestic
& Int'l
02.17.23.02.02
794
795
796
+++++
784
785
786
787
788
789
790
791
792
793
4
5
2.96
Name
SAP calls this note to payee
Tag Only
RemittanceLocationMe
thod
Name
<Nm>
+++++
Text
Tag Only
Page 23 of 25
2
3

ISO
Or
Index
No.
2.97

Indented)
Message Item
Address

Sequence Number
Mult.
Type
ACH Domestic
& Int'l

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
RULES
RECOMMENDATION:
apply)
Address
<Adr>
+++++
02.17.24.04.02
[1..1]
Department
SubDepartment
StreetName
BuildingNumber
PostCode
<Dept>
<SubDept>
<StrtNm>
<BldgNb>
<PstCd>
++++++
++++++
++++++
++++++
++++++
02.17.24.04.02.02
02.17.24.04.02.03
02.17.24.04.02.04
02.17.24.04.02.05
02.17.24.04.02.06
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
Text
Text
Text
Text
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD
TownName
CountrySubDivision
Country
AddressLine
<TwnNm>
<CtrySubDvsn>
<Ctry>
<AdrLine>
<RmtInf>
++++++
++++++
++++++
++++++
+++
02.17.24.04.02.07
02.17.24.04.02.08
02.17.24.04.02.09
02.17.24.04.02.10
02.17.25
[0..1]
[0..1]
[0..1]
[0..7]
[0..1]
Text
Text
Code
Text
BD
BD
BD
BD
BD
BD
BD
BD
BD
BD/C
BD/C
BD/C
O - either
Ustrd or
Strd
Text
BD/C
BD/C
BD/C
R -XOR Only 1
occurrence
- limited to
140
characters
R - XOR Only 1
occurrence
- limited to
140
characters
818
820
821
822
823
824
825
826
827
828
4
5
10.1.1
10.1.2
10.1.3
10.1.4
10.1.5
10.1.6
10.1.7
10.1.8
10.1.9
2.98
Department
SubDepartment
StreetName
BuildingNumber
PostCode
TownName
CountrySubDivision
Country
AddressLine
RemittanceInformation
RemittanceInformatio
n
829

Country dependent
Country dependent
Remittance information
delivered outside of the clearing
system will be conditional on
bank services. Amount of
remittance information
delivered through the clearning
system will be limited by
specific clearing system

Source Structure
Not
Not
Not
Not
Not
Currently
Currently
Currently
Currently
Currently
Supported
Supported
Supported
Supported
Supported
Not
Not
Not
Not
Currently
Currently
Currently
Currently
Supported
Supported
Supported
Supported
Unstructured
<Ustrd>
++++
02.17.25.01
[0..n]
DMEE_PAYD
2.100
Structured
Structured
<Strd>
++++
02.17.25.02
[0..n]
BD/C
BD/C
BD/C
<RfrdDocInf>
+++++
02.17.25.02.01
[0..n]
BD/C
BD/C
BD/C
Type
CodeOrProprietary
Code
<Tp>
<CdOrPrtry>
<Cd>
++++++ 02.17.25.02.01.01
+++++++ 02.17.25.02.01.01.01
++++++ 02.17.25.02.01.01.01.01
++
[0..1]
[1..1]
[1..1]
BD/C
BD/C
BD/C
Code
XOR
XOR
XOR

Atom
should be used.
Proprietary
<Prtry>
++++++
++
[1..1]
Text
XOR
XOR
XOR

Required
Issuer
<Issr>
+++++++ 02.17.25.02.01.01.02
[0..1]
Text
BD
BD
BD
Number
RelatedDate
<Nb>
<RltdDt>
++++++
++++++
02.17.25.02.01.02
02.17.25.02.01.03
[0..1]
[0..1]
Text
BD/C
BD/C
BD/C
<RfrdDocAmt>
+++++
02.17.25.02.02
[0..1]
BD/C
BD/C
BD/C
++++++
02.17.25.02.02.01
[0..1]
Amount
BD/C
BD/C
BD/C
++++++
02.17.25.02.02.02
[0..1]
Amount
BD/C
BD/C
BD/C
++++++
02.17.25.02.02.03
[0..1]
Amount
BD/C
BD/C
BD/C
TEXT (3)
830
2.101
833
834
2.102
2.103
2.104 {Or
ReferredDocumentInformation
Type
CodeOrProprietaryCode
ReferredDocumentInfo
rmation
835
2.105 Or}
Proprietary
02.17.25.02.01.01.01.02
836
837
838
2.106
2.107
2.108
Issuer
Number
RelatedDate
839
2.109
840
841
842
2.110
DuePayableAmount
2.111
2.112
843
ReferredDocumentAmount
DiscountAppliedAmount
CreditNoteAmount
ReferredDocumentAm
ount
DuePayableAmount
<DuePyblAmt
Ccy="AAA">
<DscntApldAmt
DiscountAppliedAmou Ccy="AAA">
nt
CreditNoteAmount
<CdtNoteAmt
Ccy="AAA">
General Comments
Source Field
Tag Only
Unstructured
832
Tag Only
2.99
831
Reference &FPAYHX-EIKTO& (if nonempty) .

DMEE_PAYD TEXT (1) Reference: /INV/FPAYPXBLNR& &FPAYP-BLDAT(Z)&
DMEE_PAYD TEXT (1) (once for every invoice,
up to four)
DMEE_PAYD TEXT (1) (advice instead if more
than four invoices were settled)
DMEE_PAYD TEXT (1) (plus information for
payment on behalf, if needed)
Reference information glued into one char 140
field (atoms). customers can deviate from SAP
default.
Best practice for minimum

usage: invoice number and
remitted amount or credit note
amount with currency
Tag Only
Tag Only
Tag Only
Tag Only
CONSTANT CINV or
CREN
Customer can use other codes from the schema

by adding additional atoms through
customization
Rarely used. Customer customization if required.
Required
FPAYP
XBLNR
FPAYP
BLDAT
DateTim
e
Tag Only
Amount due as stated on

FPAYP
referred document
Discount amount applied
FPAYP
against amount on invoice
Credit amount of a credit note or FPAYP
credit memo
Page 24 of 25
WRBTR
WSKTO
WRBTR
For the attribute of this element the Source is

FPAYP, and the Source Field is WAERS
For the attribute of this element the Source is
FPAYP, and the Source Field is WAERS
CONDITION WRBTR <0, populate the Credit
Note, otherwise populate the Remitted Amount.
For the attribute, the Source is FPAYP, and the
Source Field is WAERS
2
3

ISO
Or
Index
No.
2.113

Indented)
Message Item
TaxAmount
TaxAmount
2.114
AdjustmentAmountAndReason
845
847
848
849
2.115
2.116
2.117
2.118
2.119
Amount
AdditionalInformation
RemittedAmount
[0..1]
<AdjstmntAmtAn ++++++
AdjustmentAmountAn dRsn>
dReason
02.17.25.02.02.05
[0..n]
Amount
2.120
852
853
2.121
2.122
2.123 {Or
CreditorReferenceInformation
Type
CodeOrProprietaryCode
2.124 Or}
Proprietary
Type
Amount
RULES
Source Structure
Source Field
BD/C
BD/C
BD/C
Tax amount on referred

document
FPAYP
WQSTE
BD/C
BD/C
BD/C
Adjustment amount and reason

applicable to referred document
Issuer
2.126
Reference
+++++++ 02.17.25.02.02.05.02
[0..1]
Code
BD/C
BD/C
BD/C
Reason
<Rsn>
AdditionalInformation <AddtlInf>
+++++++ 02.17.25.02.02.05.03
+++++++ 02.17.25.02.02.05.04
[0..1]
[0..1]
Text
Text
BD/C
BD/C
BD/C
BD/C
BD/C
BD/C
944
AdditionalRemittanceInformation
RemittedAmount
<RmtdAmt
Ccy="AAA">
++++++
02.17.25.02.02.06
[0..1]
Amount
BD/C
BD/C
BD/C
<CdtrRefInf>
+++++
02.17.25.02.03
[0..1]
BD
BD
BD
Type
CodeOrProprietary
Code
<Tp>
<CdOrPrtry>
<Cd>
++++++ 02.17.25.02.03.01
+++++++ 02.17.25.02.03.01.01
++++++ 02.17.25.02.03.01.01.01
++
[0..1]
[1..1]
[1..1]
BD
BD
BD
Code
X0R
X0R
X0R
R - SCOR
Proprietary
<Prtry>
++++++
++
[1..1]
Text
X0R
X0R
X0R
Issuer
<Issr>
+++++++ 02.17.25.02.03.01.02
[0..1]
Text
BD
BD
BD
Value of 'ISO' reserved for ISO

11649 international creditor's
reference.
Reference
<Ref>
++++++
02.17.25.02.03.02
[0..1]
Text
If Creditor Reference Information FPAYP

is used, Reference must be
included.
Invoicer
Name
<Invcr>
<Nm>
<AddtlRmtInf>
+++++
++++++
+++++
02.17.25.02.04
02.17.25.02.04.01
02.17.25.02.06
[0..1]
[0..1]
[0..3]
BD
BD
BD
Text
Text
BD
BD
BD
AdditionalRemittanceI
nformation
General Comments
For the attribute, the Source is FPAYP, and the

Source Field is WAERS. SAP support is limited to
withholding tax amount.

Amount being paid on referred
document
FPAYP
WNETT
CONDITION WNETT <0, populate the Credit Note,

otherwise populate the Remitted Amount. For
the attribute, the Source is FPAYP, and the
Source Field is WAERS
If the structure field FPPSTRFR is filled with
value, then this will be printed, otherwise left
out.
Tag Only
Tag Only
Tag Only
Constant
should be used.
SCOR (SEPA Only)
Constant value "SCOR" for SEPA Payment Type. If

customer wants to use this field for any other
payment type, they must do a customization.
Conditional Value ISO
SAP only supports the value "ISO." If a client

wants to do anything other than the value "ISO"
they will need to do customization to over ride
the default or to use proprietary field which also
requires customization.

Required
857
Invoicer
Name
Required
856
2.127
9.1.0
2.129
Tag Only
855
2.125

Domesti Drafts
Customer
c & Int'l
to Bank
ONLY
Amount
02.17.25.02.03.01.01.02
ACH Domestic
& Int'l
[1..1]
CreditorReferenceInfor
mation
<Amt
Ccy="AAA">
<CdtDbtInd>
854
858
859
+++++++ 02.17.25.02.02.05.01
850
851
Mult.
02.17.25.02.02.04
CreditDebitIndicator
CreditDebitIndicator
Reason
<TaxAmt
Ccy="AAA">

Sequence Number
++++++
844
846
4
5
Constant
STRFR
Tag Only
Default for additional remittance DMEE_PAYD
TEXT
info
Page 25 of 25
Type 1

SAP Partners With Banks and Customers To Speed Delivery of Corporate-To-Bank Connectivity Support (Tool)

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP Partners With Banks and Customers To Speed Delivery of Corporate-To-Bank Connectivity Support (Tool)

Încărcat de

Drepturi de autor:

Formate disponibile

Mapping Between SAP Internal Data Field

Implementation (CGI) Template - Custome

The mappings in this document are a d

SAP Community Definition Group SAP to IS

All 6 CGI message templates

SAP Implementation Notes - Supporting user documentation with explana

Potential Incorporation into SAP product of selected transactions to incl

Color Coding for Columns P&Q in Mapping Spreadsheet

Short entry for note to payee, internal

short entry for note to payee, external

Data Fields and the Common Global

ument are a deliverable of the

SAP to ISO 20022 CGI Mapping

CTS Conformant Global Data Types, other SAP tables as

O 20022 Transaction elements as identified in CGI message

ion with explanations, amplifications, and guidance

actions to include new SAP data fields and Global Data

This element may at

ther be used to create

ngs. For example if

Driven by customer demand for multibank coordination of implementations

corporate, multi-banked, multi-payment type, multi-country implementations (mixed

The common global implementation is not intended to:

COMMON GLOBAL IMPLEMENTATION GUIDELINES

-The following definition is associated with the payment types:

Standard element for CGI; Required

Standard element for CGI; Dependent

Standard element for CGI. Contents are

Standard element for CGI. Contents are

Not Used by CGI

REFERENCES TO ISO DOCUMENTATION

Optional to schema for subcomponent;

CRG (Ikea, Wuerth, Fiat Group, Yara,

ectly from the CGI Template without change to

pe, multi-country implementations (mixed payables)

es (e.g. banks will still offer these)

y or bank servicing capabilities (e.g. these are different than agreeing

alue or non-urgent transactions. Typically associated with a batch process

h value or urgent transactions with high priority

This element needs to be present when certain conditions apply. These

Select one or the other field, but not both

Occurrence will note whether a subcomponent is repeating and number

stomer and bank.

action is cross border, the value of 'IN' is utilized in Local Instrument.

Customer Credit Transfer Initiation V3 pain.001.001.03

ISO Published: April 2009

Message Item (Non- Tag Name

Structural Structural Sequence

Customer Credit Transfer

Wires - Cheques/ SEPA

SAP Technical Comments

This is not typically sent. If a customer wants to send one of the

Can be used for SEPA, but not

calls small function model where SAP collects the

TRF would be default for any electronic transfer.

Total number of transactions

May or may not be supported by a particular bank. Default should

It is a client's option to include.

Note that this is within the batch, not the message.

Required at either Payment or

Based on whether priority

not listed on Appendix A,