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

SAP Community Definition Group – SAP to ISO 20022 CGI Mapping

Purpose

Develop mappings of CGI guidelines to SAP internal Data Fields

All 6 CGI message templates

Methodology

Teleconferences and F2F meetings for actual mapping

SAP StreamWork for collaboration and sharing

Deliverables

SAP Implementation Notes - Supporting user documentation with explanations, amplifications, and guidance

Conventions:

Mapping Between SAP Internal Data Fields and the Common Global Implementation (CGI) Template - Customer Credit Transfer Initiation

pain.001.001.03 of 14 October 2010

The mappings in this document are a deliverable of the SAP Community Definition Group - SAP to ISO 20022 CGI Mapping

•Scope

Using CGI message templates, SAP FPay Tables, SAP CCTS Conformant Global Data Types, other SAP tables as appropriate

Excel Spreadsheet (e.g. this document) map between ISO 20022 Transaction elements as identified in CGI message template and the SAP internal data fields), DMEE/PMW XML Format, PI XML Schema.

Potential Incorporation into SAP product of selected transactions – to include new SAP data fields and Global Data Types (In conjunction with the SAP Implementation Note)

All CGI Conventions for Columns A through O are preserved

Color Coding for Columns P&Q in Mapping SpreadsheetColor Code Explanation

Data Tag is Tag Only to identify a parent element with one or more child elements.Data Tag not used

Special Terms

Atom

Exit

Type 1Note to payee

Type 2Short entry for note to payee, internal

Type 3short entry for note to payee, external

ContributorsSAP SWIFT

HSBC B2 - TDI

Citi JPMC UK Payments

Nordea Wells Fargo

Danske Bank RBS FIT-EDV

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.

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.

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.

Deutsche Bank

Bank of America Merrill Lynch

Danish Bankers Association

SAP Community Definition Group – SAP to ISO 20022 CGI Mapping

Purpose

Develop mappings of CGI guidelines to SAP internal Data Fields

All 6 CGI message templates

Methodology

Teleconferences and F2F meetings for actual mapping

SAP StreamWork for collaboration and sharing

Deliverables

SAP Implementation Notes - Supporting user documentation with explanations, amplifications, and guidance

Mapping Between SAP Internal Data Fields and the Common Global Implementation (CGI) Template - Customer Credit Transfer Initiation

pain.001.001.03 of 14 October 2010

The mappings in this document are a deliverable of the SAP Community Definition Group - SAP to ISO 20022 CGI Mapping

•Scope

Using CGI message templates, SAP FPay Tables, SAP CCTS Conformant Global Data Types, other SAP tables as

Excel Spreadsheet (e.g. this document) map between ISO 20022 Transaction elements as identified in CGI message template and the SAP internal data fields), DMEE/PMW XML Format, PI XML Schema.

Potential Incorporation into SAP product of selected transactions – to include new SAP data fields and Global Data Types (In conjunction with the SAP Implementation Note)

Color Coding for Columns P&Q in Mapping SpreadsheetExplanation

Data Tag is Tag Only to identify a parent element with one or more child elements.Data Tag not used

Special Terms

Note to payee

Short entry for note to payee, internal

short entry for note to payee, external

The Mapping between the CGI Element and SAP Element is agreed to and validated

The Mapping as stated is partial support for the CGI Element and has been validated

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.

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

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.

COMMON GLOBAL IMPLEMENTATION (CGI)Customer Credit Transfer Initiation pain.001.001.03As of October 14, 2010

banks can commonly accept as ONE of their implementations

by the participating banks

services and capabilities but can also offer this common implementation where desirable or requested by an appropriate customer)

on the format that can be commonly used)

domestic clearing and settlement systems from this map)

COMMON GLOBAL IMPLEMENTATION GUIDELINES

~Any of the data tags included in this guide will be accepted by any bank supporting the CGI. The bank will either use the tag for processing or ignore it.

All Content on This Sheet is taken directly from the CGI Template without change to ensure users of the mapping understand the proper context and content

}Driven by customer demand for multibank coordination of implementations}Global corporate, multi-banked, multi-payment type, multi-country implementations (mixed payables)}Is intended specifically for global, multi-country, multi-bank and multi-instrument implementations that the participating

}Focuses on the general message structure and then successful creation of individual transactions that can be executed

}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)}Serve as the sole map accepted by participating banks (e.g. – participating banks will still be able to offer their value added

}Replace domestic banking convention “in-country” or bank servicing capabilities (e.g. – these are different than agreeing

}Serve as an interbank map (e.g. – participating banks will be able to create proper instructions and file formats for

~The required elements in the CGI will be accepted by all CGI supporting banks. They define a standard set of data with agreed country/payment instrument qualifications.~Any data populated in a schema-defined optional field that is not required by an individual bank will be ignored and not stop processing of the message. This rule includes elements that are designated "Not Used" by the CGI. Bilateral documentation should specify where an "R" field will be ignored by a specific bank.

~Where individual clients do not maintain a CGI-Required or Conditional element in their systems, they should consult with their bank(s) on the minimum of data elements required for that type of transaction. This could result in the need to add those data elements into the client's systems.

~The following general attributes are assigned in the CGI and should be read in conjunction with the country/payment instrument rules produced for the CGI. If a country/payment instrument has not been addressed, the banks engaged by the client will work to try and agree on a common addition to the CGI 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 associated with a batch process 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

ATTRIBUTESCODES TERM DEFINITIONS

R Required

C Conditional

BD Bilaterally Determined

XOR eXclusive Or

NU Not Used Not Used by CGI

REFERENCES TO ISO DOCUMENTATION

[0..x] Optional

[1..1] Mandatory Mandatory to schema for subcomponent Root Tag of messageLevel Component Tag; no data contentComponent Tag; no data contentData Tag not used

CONTRIBUTORS

BBVA Nordea

RBS CargillBNP Paribas Santander Oracle

Standard element for CGI; Required either by schema or CGI

Standard element for CGI; Dependent upon a certain condition.

Standard element for CGI. Contents are bilaterally determined between client and bank

Standard element for CGI. Contents are XOR either by the schema or CGI usage.

Optional to schema for subcomponent; may repeat

CRG (Ikea, Wuerth, Fiat Group, Yara, Utsit)

Bank of America Merrill Lynch

Citibank SEB GE

Deutsche Bank Danish Bankers AssociationHSBC SWIFTJPMC 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.

-Tag length is dependent upon country clearing requirements and is not quoted in this document.

-This document addresses where the data is placed. It does not define the requirements for when the data must be present or the values to be contained.-The CGI allows for inclusion of SEPA transactions based on CGI parameters which may be broader than SEPA guidelines.

-If a bank requires a local instrument code to indicate that an URGP transaction is cross border, the value of 'IN' is utilized in Local Instrument.

Standard Chartered Bank

-Standard XML version declaration must explicitly specify that XML v1.0 is being used. The <Document> tag should specify the appropriate namespace. 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-instance">

-The branch code of an agent should be explicitely stated I the <BrnchId> component versus being combined with Clearing System Member ID when it is required.

-Information captured under <RegulatoryReporting> or <Tax> is used explicitily for the applicable function and not to be reported to beneficiary as part of the payment.-The CGI country rules template represents the minimum requirements for each payment method within each country in order for the payment to be processed. It does not indicate that all banks will use or require this minimum data. The core minimum requirement should be viewed in conjunction with the 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 code value in the External Code List in <Cd> or local market practice codes or text in <Prtry>.

banks can commonly accept as ONE of their implementations

services and capabilities but can also offer this common implementation where desirable or requested by an

domestic clearing and settlement systems from this map)

~Any of the data tags included in this guide will be accepted by any bank supporting the CGI. The bank will either use the tag for processing or ignore it.

All Content on This Sheet is taken directly from the CGI Template without change to ensure users of the mapping understand the proper context and content

Driven by customer demand for multibank coordination of implementationsGlobal corporate, multi-banked, multi-payment type, multi-country implementations (mixed payables)Is intended specifically for global, multi-country, multi-bank and multi-instrument implementations that the participating

Focuses on the general message structure and then successful creation of individual transactions that can be executed

Can be published and has endorsement from appropriate communities

The common global implementation is not intended to:Focus on purely domestic or single instrument files (e.g. – banks will still offer these)Serve as the sole map accepted by participating banks (e.g. – participating banks will still be able to offer their value added

Replace domestic banking convention “in-country” or bank servicing capabilities (e.g. – these are different than agreeing

Serve as an interbank map (e.g. – participating banks will be able to create proper instructions and file formats for

~The required elements in the CGI will be accepted by all CGI supporting banks. They define a standard set of data with agreed country/payment instrument ~Any data populated in a schema-defined optional field that is not required by an individual bank will be ignored and not stop processing of the message. This rule includes elements that are designated "Not Used" by the CGI. Bilateral documentation should specify where an "R" field will be ignored by a specific

~Where individual clients do not maintain a CGI-Required or Conditional element in their systems, they should consult with their bank(s) on the minimum of data elements required for that type of transaction. This could result in the need to add those data elements into the client's systems.

~The following general attributes are assigned in the CGI and should be read in conjunction with the country/payment instrument rules produced for the CGI. If a country/payment instrument has not been addressed, the banks engaged by the client will work to try and agree on a common addition to the CGI

General usage is equivalent to low value or non-urgent transactions. Typically associated with a batch process

General usage is equivalent to high value or urgent transactions with high priority

EXPLANATION

Select one or the other field, but not both

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.

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.

-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.

-Tag length is dependent upon country clearing requirements and is not quoted in this document.

-This document addresses where the data is placed. It does not define the requirements for when the data must be present or the values to be contained.-The CGI allows for inclusion of SEPA transactions based on CGI parameters which may be broader than SEPA guidelines.

-If a bank requires a local instrument code to indicate that an URGP transaction is cross border, the value of 'IN' is utilized in Local Instrument.

-Standard XML version declaration must explicitly specify that XML v1.0 is being used. The <Document> tag should specify the appropriate namespace.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

-The branch code of an agent should be explicitely stated I the <BrnchId> component versus being combined with Clearing System Member ID when it is

-Information captured under <RegulatoryReporting> or <Tax> is used explicitily for the applicable function and not to be reported to beneficiary as part of the

-The CGI country rules template represents the minimum requirements for each payment method within each country in order for the payment to be processed. It does not indicate that all banks will use or require this minimum data. The core minimum requirement should be viewed in conjunction with the

- The population of <Cd> or <Prtry> under <CtgyPurp> or <Purp> is depdendent upon the originator's usage of ISO 20022 code value in the External Code

Page 12 of 24

Customer Credit Transfer Initiation V3 pain.001.001.03ISO Published: April 2009Common Industry Agreement: As of October 14, 2010

V3 Implementation Guide SAP Source and Field SAP Technical Comments General Comments

Or Message Item Tag Name Mult. Type RULES Source Structure Source Field

- R R R R Tag Only

GroupHeader GroupHeader <GrpHdr> + 01 [1..1] R R R R Tag Only MessageIdentification MessageIdentification <MsgId> ++ 01.01 [1..1] Text R R R R FPAYHX RENUM XVORL CreationDateTime CreationDateTime <CreDtTm> ++ 01.02 [1..1] R R R R SYSTEM DATLO & TIMLO Atoms Use UTC with offset for all date/time

Authorisation Authorisation <Authstn> ++ 01.03 [0..2] BD BD BD Tag Only Code Code <Cd> +++ 01.03.01 [1..1] Code BD BD BD

Proprietary Proprietary <Prtry> +++ 01.03.02 [1..1] Text BD BD BD

NumberOfTransactions <NbOfTxs> ++ 01.04 [1..1] Text R R R R #AGGR <CdtTrfTxInf> number of occurences SRTF2

ControlSum ControlSum <CtrlSum> ++ 01.05 [0..1] BD BD BD R #AGGR <InstdAmt> summation (total)

InitiatingParty InitiatingParty <InitgPty> ++ 01.06 [1..1] R R R R Tag Only Name Name <Nm> +++ 01.06.01 BD BD BD FPAYHX NAMEZ Name of the sender of the message. Typically the company name

Identification Identification <Id> +++ 01.06.03 R R R R Tag Only {Or OrganisationIdentification <OrgId> ++++ 01.06.03.01 R R R R Tag Only

BICOrBEI BICOrBEI <BICOrBEI> +++++ 01.06.03.01.01 BD BD BD O #EXIT ZREGI

Other Other <Othr> +++++ 01.06.03.01.02 BD BD BD Tag Only

Identification Identification <Id> ++++++ 01.06.03.01.02.01 R R R R FPAYHX DTKID(T012D) ZORT2 SchemeName SchemeName <SchmeNm> ++++++ 01.06.03.01.02.02 BD BD BD Tag Only Code Code <Cd> +++++++ 01.06.03.01.02.02.01 R R R #EXIT

2.0 PaymentInformation <PmtInf> + 02 [1..n] R R R R Tag Only 2.1 <PmtInfId> ++ 02.01 [1..1] Text R R R R #EXIT DMEE_EXIT_SEPA_21 .INCLUDE

2.2 PaymentMethod <PmtMtd> ++ 02.02 [1..1] Code R - TRF R - TRF R - CHK R - TRF #CONST DOC1T

2.3 BatchBooking <BtchBookg> ++ 02.03 [0..1] BD BD BD SO

2.4 NumberOfTransactions <NbOfTxs> ++ 02.04 [0..1] Text BD BD BD Aggregation Note that this is within the batch, not the message.

2.5 ControlSum <CtrlSum> ++ 02.05 [0..1] BD BD BD Aggregation Note that this is within the batch, not the message.

PaymentTypeInformation <PmtTpInf> ++ 02.06 [0..1] R R R R Tag Only

2.7 InstructionPriority <InstrPrty> +++ 02.06.01 [0..1] Code BD BD NU FPAYHX DTURG RWSKT

2.8 ServiceLevel <SvcLvl> +++ 02.06.02 [0..1] R R NU R Tag Only

2.9 {Or Code <Cd> ++++ 02.06.02.01 [1..1] Code XOR XOR NU R - SEPA Conditional. See CGI Note in Column O.

ISO Index No.

Message Item (Non-Indented)

StructuralSequence

Structural Sequence Number

ACH - Domestic & Int'l

Wires - Domestic & Int'l

Cheques/Drafts

SEPACustomer to Bank ONLY

Customer Credit Transfer Initiation

<CstmrCdtTrfInitn>

1.0 1.1 1.2

DateTime

1.3 1.4 {Or Customer Customization

RequiredThis 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.

1.5 Or} Customer Customization Required

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.

1.6 NumberOfTransactions

Total number of transactions in the entire message.

1.7 Quantity

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.

Summation is made after each item in SAP system and then populated from that aggregation rather than a source field.

1.8 9.1.0 [0..1] Text O (70 char

only)Can be used for SEPA, but not required. See Appendix B.

9.1.12 [0..1] 9.1.13 OrganisationIdentificat

ion [1..1]

9.1.14 [0..1] Identifier

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.

9.1.15 [0..n] R (1 occur only)

9.1.16 [1..1] Text 9.1.17 [0..1] 9.1.18 [1..1] Code Database Table T001 and corresponding field

source PAVAL is used in the Function Module to determine the value which is presented in the Cd element. See attached information for the usage of BICorBEI element.

Qualifies the ID above. Customer Customization needed if this field is to be populated.

PaymentInformation PaymentInformationIdentification

PaymentInformationIdentification

calls small function model where SAP collects the number

PaymentMethod CONDITIONAL -TRF or CHK

TRF would be default for any electronic transfer. CHK for check.

BatchBooking Indicator

Customer Customization Required

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."

NumberOfTransactions

Total number of transactions within a Payment Information batch.

ControlSum Quantity

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.

2.6 PaymentTypeInformation

Required at either Payment or Transaction Level, but should not be present at both levels. Recommnded usage is at Payment level.

InstructionPriority Based on whether priority processing vs. normal processing is offered by the bank.

Map to the two code values in the schema - codes if marked as DTURG=HIGH, otherwise =NORM

ServiceLevel If an instrument or country is not listed on Appendix A, agreement will be bilateral until included on the list.

Constant value in SAP system. SAP will only support at the payment level for SEPA, otherwise will be at transaction level.

Code If <Cd> is populated, <Prtry> should not be populated. A code from the external code list should be used.

Filled with value SEPA if this is SEPA payment

SAP will only support at the payment level for SEPA, otherwise will be at transaction level.

A B C D E F G H I J K L M N O P Q R

1

23

4

5

6

78

9

10

11

12

13

14

15

16

28

29

30

31

3233

34

98

99

100

101

102

103

104

105

106

107

Page 13 of 24



Or Message Item Tag Name Mult. Type RULES Source Structure Source FieldISO Index No.


StructuralSequence




Cheques/Drafts


2.10 Or} Proprietary <Prtry> ++++ 02.06.02.02 [1..1] Text XOR XOR NU Conditional. See CGI Note in Column O.

2.11 LocalInstrument <LclInstrm> +++ 02.06.03 [0..1] C C C O Tag Only

2.12 {Or Code <Cd> ++++ 02.06.03.01 [1..1] Code XOR XOR NU Value List

2.13 Or} Proprietary <Prtry> ++++ 02.06.03.02 [1..1] Text XOR XOR

2.14 CategoryPurpose <CtgyPurp> +++ 02.06.04 [0..1] C C NU O Tag Only

2.15 {Or Code <Cd> ++++ 02.06.04.01 [1..1] Code XOR XOR NU O Use Instruction Keys Conditional. See CGI Note in Column O.

2.16 Or} Proprietary <Prtry> ++++ 02.06.04.02 [1..1] Text XOR XOR NU C

2.17 RequestedExecutionDate <ReqdExctnDt> ++ 02.07 [1..1] R R R R FPAYH or FPM_CGI CRVAL

2.19 Debtor <Dbtr> ++ 02.09 [1..1] R R R R Tag Only 9.1.0 Name <Nm> +++ 02.09.01 [0..1] Text R R R R FPAYHX NAMEZ PAYGR 9.1.1 PostalAddress <PstlAdr> +++ 02.09.02 [0..1] R R R R SAP Supports Structured. Tag Only

9.1.2 AddressType <AdrTp> ++++ 02.09.02.01 [0..1] Code NU NU NU Not Used WEFAE 9.1.3 Department <Dept> ++++ 02.09.02.02 [0..1] Text BD BD BD See recommendation above. Not currently supported WEAMX 9.1.4 SubDepartment <SubDept> ++++ 02.09.02.03 [0..1] Text BD BD BD See recommendation above. Not currently supported WEFMX 9.1.5 StreetName <StrtNm> ++++ 02.09.02.04 [0..1] Text BD BD BD See recommendation above. FPAYHX REF01 Read Out from central address management WEFRS 9.1.6 BuildingNumber <BldgNb> ++++ 02.09.02.05 [0..1] Text BD BD BD See recommendation above. FPAYHX REF01(60) Read Out from central address management .INCLUDE 9.1.7 PostCode <PstCd> ++++ 02.09.02.06 [0..1] Text BD BD BD FPAYHX REF01(80) Read Out from central address management RZAWE

9.1.8 TownName <TwnNm> ++++ 02.09.02.07 [0..1] Text BD BD BD See recommendation above. FPAYHX ORT1Z UZAWE 9.1.9 CountrySubDivision <CtrySubDvsn> ++++ 02.09.02.08 [0..1] Text BD BD BD Country dependent FPAYHX REF01(90) Read Out from central address management AVISG 9.1.10 Country <Ctry> ++++ 02.09.02.09 [0..1] Code R R R R See recommendation above. FPAYHX LAND1 INTRACOMP 9.1.11 AddressLine <AdrLine> ++++ 02.09.02.10 [0..7] Text BD BD BD 2 lines See recommendation above. FPAYHX AUST1-2 FORMZ 9.1.12 Identification <Id> +++ 02.09.03 [0..1] C C C Tag Only

9.1.13 {Or <OrgId> ++++ 02.09.03.01 [1..1] R R R R Tag Only

Proprietary If <Prtry> is populated, <Cd> should not be populated. The condition is based on the need to use a proprietary code not on the external code list per bilateral agreement.


LocalInstrument If an instrument or country is not listed on Appendix A, agreement will be bilateral until included on the list.

Code ONCL = overnight clearingSDCL = same day clearing

If <Cd> is populated, <Prtry> should not be populated. A code from the external code list should be used.

Combination Support and User Customization

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

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.

Proprietary C - Check Issuance (CII)

If <Prtry> is populated, <Cd> should not be populated. The condition is based on the need to use a proprietary code not on the external code list per bilateral agreement.


Conditional. See CGI Note in Column O. If customer wants to use this element for check issuance there is a CGI code for that.

CategoryPurpose Conditional based on country payment instrument. If <CtgyPurp> is used, one of <Cd> or <Prtry> must be used.



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.

RequestedExecutionDate

DateTime

AUSFD or DUEDATE_CGI

Atoms. If the user don´t specify a Date the executaion date will be set as default.

Debtor Name PostalAddress 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)

NOTE: PO Box should only appear in Address Line.

AddressType Department SubDepartment StreetName BuildingNumber PostCode See recommendation above.

Country dependent

TownName CountrySubDivision Country AddressLine Identification O - XOR

Only 1 allowed

Conditional on country payment instrument.

OrganisationIdentification



1

23

4

5

108

109

110

111

112

113

114

115

117118

119

120121122123124

125

126127128129

130

131

Page 14 of 24





StructuralSequence




Cheques/Drafts


9.1.14 BICOrBEI <BICOrBEI> +++++ 02.09.03.01.01 [0..1] C C C O Customer Customization Required

9.1.15 Other <Othr> +++++ 02.09.03.01.02 [0..n] C C C O Tag Only 9.1.16 Identification <Id> ++++++ 02.09.03.01.02.01 [1..1] Text R R R R #EXIT This is required in some countries (See CGI Appendix B).

9.1.17 SchemeName <SchmeNm> ++++++ 02.09.03.01.02.02 [0..1] BD BD BD O Tag Only 9.1.18 {{Or Code <Cd> +++++++ 02.09.03.01.02.02.01 [1..1] Code XOR XOR XOR O #EXIT

9.1.19 Or}} Proprietary <Prtry> +++++++ 02.09.03.01.02.02.02 [1..1] Text XOR XOR XOR O ID_CODE

9.1.20 Issuer <Issr> ++++++ 02.09.03.01.02.03 [0..1] Text NU NU NU O #EXIT Only used if Other (line 134) is populated and only for SEPA.

9.1.33 CountryOfResidence <CtryOfRes> +++ 02.09.04 [0..1] Code C C C FPAYHX LAND1 This is the Country Code of the physical location of the party. 9.1.34 ContactDetails <CtctDtls> +++ 02.09.05 [0..1] BD BD BD Tag Only 9.1.35 NamePrefix <NmPrfx> ++++ 02.09.05.01 [0..1] Code BD BD BD FPAYH SALUT ORIG_REC_NAME1

9.1.36 Name <Nm> ++++ 02.09.05.02 [0..1] Text BD BD BD FPAYH NAMP1 ORIG_REC_NAME2 9.1.37 PhoneNumber <PhneNb> ++++ 02.09.05.03 [0..1] Text BD BD BD FPAYH TELF1 ORIG_IBAN 9.1.38 MobileNumber <MobNb> ++++ 02.09.05.04 [0..1] Text BD BD BD FPAYH TELF2 ORIG_BIC 9.1.39 FaxNumber <FaxNb> ++++ 02.09.05.05 [0..1] Text BD BD BD FPAYH TELFX SND_DEBTOR_ID 9.1.40 EmailAddress <EmailAdr> ++++ 02.09.05.06 [0..1] Text BD BD BD FPAYH INTAD 9.1.41 Other <Othr> ++++ 02.09.05.07 [0..1] Text BD BD BD Not Currently Supported 2.20 DebtorAccount <DbtrAcct> ++ 02.10 [1..1] R R R R Tag Only 1.1.0 Identification <Id> +++ 02.10.01 [1..1] R R R R Tag Only

1.1.1 {Or IBAN <IBAN> ++++ 02.10.01.01 [1..1] XOR XOR XOR R-XOR FPAYHX UIBAN

1.1.2 Or} Other <Othr> ++++ 02.10.01.02 [1..1] XOR XOR XOR R-XOR Tag Only 1.1.3 Identification <Id> +++++ 02.10.01.02.01 [1..1] Text R R R R FPAYHX UBKNT 1.1.4 SchemeName <SchmeNm> +++++ 02.10.01.02.02 [0..1] BD BD BD Tag Only 1.1.5 {{Or Code <Cd> ++++++ 02.10.01.02.02.01 [1..1] Code BD BD BD 20022 External Code List - 3 codes. BBAN, CUID, UPIC.

1.1.6 Or}} Proprietary <Prtry> ++++++ 02.10.01.02.02.02 [1..1] Text BD BD BD

1.1.7 Issuer <Issr> +++++ 02.10.01.02.03 [0..1] Text BD BD BD SchemeAgencyName Generally not used

1.1.8 Type <Tp> +++ 02.10.02 [0..1] C C C O Tag Only

1.1.9 {Or Code <Cd> ++++ 02.10.02.01 [1..1] Code XOR XOR XOR C FPAYHX UBKON

1.1.10 Or} Proprietary <Prtry> ++++ 02.10.02.02 [1..1] Text XOR XOR XOR

1.1.11 Currency <Ccy> +++ 02.10.03 [0..1] Code R R R R FPAYHX UBWAE Currency the account is maintained in - See ISO 4217 1.1.12 Name <Nm> +++ 02.10.04 [0..1] Text NU NU NU O Not Currently Supported 2.21 DebtorAgent <DbtrAgt> ++ 02.11 [1..1] R R R R Tag Only

BICOrBEI Identifier


Other Identification 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.

SchemeName Code If <Cd> is populated, <Prtry>

should not be populated. A code from the external code list should be used.

Database Table T001 and corresponding field source PAVAL is used in the Function Module to determine the value which is presented in the Cd element. See attached information for the usage of BICorBEI element.

Codes are enumerated in external code list. This identifies the type of identifier.



Issuer Database Table T001 and corresponding field source PAVAL is used in the Function Module to determine the Institution which is presented in the Cd element. See attached information for the usage of BICorBEI element.

CountryOfResidence ContactDetails NamePrefix See Implementation Note 1665873 for user

requirements to maintain this element.

Name PhoneNumber MobileNumber FaxNumber EmailAddress Other DebtorAccount Identification Either <IBAN> or <Othr> must

be populated. IBAN

Identifier

Other Identification SchemeName Code Customer Customization

Required Proprietary Customer Customization

RequiredGenerally not used. If user requires then a customer customization will be required.

Issuer Customer Customization Required

Type Country-Dependent. See Appendix B.

Code If <Cd> is populated, <Prtry> should not be populated. A code from the list in the schema should be used.

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.

Proprietary If <Prtry> is populated, <Cd> should not be populated. The condition is based on the need to use a proprietary code not on the schema code list per bilateral agreement.


SAP to ensure it provides guidance to customers on how to customize this field.

Currency Name DebtorAgent


1

23

4

5

132

133

134

135

136

137

138

151152

153

154155156157158159160

161

162

163164165

166

167

168

169

170

171

172173174

Page 15 of 24





StructuralSequence




Cheques/Drafts


6.1.0 <FinInstnId> +++ 02.11.01 [1..1] R R R R Tag Only

6.1.1 BIC <BIC> ++++ 02.11.01.01 [0..1] C C C R FPAYHX USWIF

6.1.2 <ClrSysMmbId> ++++ 02.11.01.02 [0..1] C C C Tag Only

6.1.3 <ClrSysId> +++++ 02.11.01.02.01 [0..1] BD BD BD Tag Only

6.1.4 {Or Code <Cd> ++++++ 02.11.01.02.01.01 [1..1] Code XOR XOR XOR C

6.1.5 Or} Proprietary <Prtry> ++++++ 02.11.01.02.01.02 [1..1] Text XOR XOR XOR

6.1.6 MemberIdentification <MmbId> +++++ 02.11.01.02.02 [1..1] Text R R R FPAYHX UBNKL

6.1.8 PostalAddress <PstlAdr> ++++ 02.11.01.04 [0..1] R R R R Tag Only. Note CGI Note in Column O regarding ignore if provided 6.1.17 Country <Ctry> +++++ 02.11.01.04.09 [0..1] Code R R R R FPAYHX UBISO

6.1.25 BranchIdentification <BrnchId> +++ 02.11.02 [0..1] BD BD BD Tag Only

6.1.26 Identification <Id> ++++ 02.11.02.01 [0..1] Text BD BD BD O FPAYHX UBRCH 2.23 UltimateDebtor <UltmtDbtr> ++ 02.13 [0..1] C C C O Tag Only

9.1.0 Name <Nm> +++ 02.13.01 [0..1] Text R R R Not Currently Supported

9.1.1 PostalAddress <PstlAdr> +++ 02.13.02 [0..1] C C C R Tag Only

9.1.3 Department <Dept> ++++ 02.13.02.02 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.4 SubDepartment <SubDept> ++++ 02.13.02.03 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.5 StreetName <StrtNm> ++++ 02.13.02.04 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.6 BuildingNumber <BldgNb> ++++ 02.13.02.05 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.7 PostCode <PstCd> ++++ 02.13.02.06 [0..1] Text BD BD BD Not Currently Supported

9.1.8 TownName <TwnNm> ++++ 02.13.02.07 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.9 CountrySubDivision <CtrySubDvsn> ++++ 02.13.02.08 [0..1] Text BD BD BD Country dependent Not Currently Supported

9.1.10 Country <Ctry> ++++ 02.13.02.09 [0..1] Code R R R R See recommendation above. Not Currently Supported 9.1.11 AddressLine <AdrLine> ++++ 02.13.02.10 [0..7] Text BD BD BD See recommendation above. Not Currently Supported

9.1.12 Identification <Id> +++ 02.13.03 [0..1] C C C Tag Only

9.1.13 {Or <OrgId> ++++ 02.13.03.01 [1..1] R R R R Tag Only

9.1.14 BICOrBEI <BICOrBEI> +++++ 02.13.03.01.01 [0..1] C C C O Not Currently Supported 9.1.15 Other <Othr> +++++ 02.13.03.01.02 [0..n] C C C O Tag Only 9.1.16 Identification <Id> ++++++ 02.13.03.01.02.01 [1..1] Text R R R R Not Currently Supported 9.1.17 SchemeName <SchmeNm> ++++++ 02.13.03.01.02.02 [0..1] BD BD BD O Tag Only 9.1.18 {{Or Code <Cd> +++++++ 02.13.03.01.02.02.01 [1..1] Code XOR XOR XOR O Not Currently Supported

FinancialInstitutionIdentification


BIC Identifier

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

ClearingSystemMemberIdentification


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

ClearingSystemIdentification




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.



If this is required then customer will need to implement a customized solution.

MemberIdentification Should be populated if in SAP system and BIC above should also be populated.

PostalAddress Country Is used for multiple reasons, to including an indication if this is

cross border. BranchIdentification O (Region

and Bank Dependent)

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.

Identification UltimateDebtor Conditional based on business

need and payment transaction.SAP only supports UltimateDebtor at transaction level. If the customer requires this at the payment level, they must do a customization for all required elements.

Name R - max. 70 char

PostalAddress RECOMMENDATION: 1. Use only structured address.2. Use only Address Line (up to 7 lines; instrument by instrument limitations may 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.

Department SubDepartment StreetName BuildingNumber PostCode O - Ctry

DpdtSee recommendation above. Country dependent

TownName CountrySubDivision O - Ctry

Dpdt

Country AddressLine 2 lines

(# text to be discussed) Identification O - XOR Only 1 allowed




BICOrBEI Identifier Other

Identification SchemeName Code If <Cd> is populated, <Prtry>

should not be populated. A code from the external code list should be used.


1

23

4

5

175

176

177

178

179

180

181

183

192

200

201

228

229

230

232233234235

236

237

238

239

240

241

242

243244245246

247

Page 16 of 24





StructuralSequence




Cheques/Drafts


9.1.19 Or}} Proprietary <Prtry> +++++++ 02.13.03.01.02.02.02 [1..1] Text XOR XOR XOR O Not Currently Supported

9.1.20 Issuer <Issr> ++++++ 02.13.03.01.02.03 [0..1] Text NU NU NU O Not Currently Supported 9.1.21 Or} PrivateIdentification <PrvtId> ++++ 02.13.03.02 [1..1] NU NU NU O Tag only 9.1.22 DateAndPlaceOfBirth +++++ 02.13.03.02.01 [0..1] NU NU NU O Tag only

9.1.23 BirthDate <BirthDt> ++++++ 02.13.03.02.01.01 [1..1] NU NU NU R Not Currently Supported

9.1.24 ProvinceOfBirth <PrvcOfBirth> ++++++ 02.13.03.02.01.02 [0..1] Text NU NU NU O Not Currently Supported 9.1.25 CityOfBirth <CityOfBirth> ++++++ 02.13.03.02.01.03 [1..1] Text NU NU NU R Not Currently Supported 9.1.26 CountryOfBirth <CtryOfBirth> ++++++ 02.13.03.02.01.04 [1..1] Code NU NU NU R Not Currently Supported 9.1.27 Other <Othr> +++++ 02.13.03.02.02 [0..n] NU NU NU O Not Currently Supported Tag only 9.1.28 Identification <Id> ++++++ 02.13.03.02.02.01 [1..1] Text NU NU NU R Not Currently Supported 9.1.29 SchemeName <SchmeNm> ++++++ 02.13.03.02.02.02 [0..1] NU NU NU O Not Currently Supported Tag only 9.1.30 {{Or Code <Cd> +++++++ 02.13.03.02.02.02.01 [1..1] Code NU NU NU O Not Currently Supported 9.1.31 Or}} Proprietary <Prtry> +++++++ 02.13.03.02.02.02.02 [1..1] Text NU NU NU O Not Currently Supported 9.1.32 Issuer <Issr> ++++++ 02.13.03.02.02.03 [0..1] Text NU NU NU O Not Currently Supported 9.1.33 CountryOfResidence <CtryOfRes> +++ 02.13.04 [0..1] Code C C C O Conditional upon country rules Not Currently Supported This is the physical country of residence of the Ultimate Debtor. 9.1.34 ContactDetails <CtctDtls> +++ 02.13.05 [0..1] BD BD BD Tag Only 9.1.35 NamePrefix <NmPrfx> ++++ 02.13.05.01 [0..1] Code BD BD BD Not Currently Supported 9.1.36 Name <Nm> ++++ 02.13.05.02 [0..1] Text BD BD BD Not Currently Supported 9.1.37 PhoneNumber <PhneNb> ++++ 02.13.05.03 [0..1] Text BD BD BD Not Currently Supported 9.1.38 MobileNumber <MobNb> ++++ 02.13.05.04 [0..1] Text BD BD BD Not Currently Supported 9.1.39 FaxNumber <FaxNb> ++++ 02.13.05.05 [0..1] Text BD BD BD Not Currently Supported 9.1.40 EmailAddress <EmailAdr> ++++ 02.13.05.06 [0..1] Text BD BD BD Not Currently Supported 9.1.41 Other <Othr> ++++ 02.13.05.07 [0..1] Text BD BD BD Not Currently Supported 2.24 ChargeBearer <ChrgBr> ++ 02.14 [0..1] Code NU R - SLEV FPAYHX DTKVS

2.25 ChargesAccount <ChrgsAcct> ++ 02.15 [0..1] BD BD BD Tag Only 1.1.0 Identification <Id> +++ 02.15.01 [1..1] BD BD BD Tag Only 1.1.1 {Or IBAN <IBAN> ++++ 02.15.01.01 [1..1] BD BD BD SAP IMS issuing Workaround note

1.1.2 Or} Other <Othr> ++++ 02.15.01.02 [1..1] BD BD BD Tag Only 1.1.3 Identification <Id> +++++ 02.15.01.02.01 [1..1] Text BD BD BD FPAYHX DTGBK 1.1.4 SchemeName <SchmeNm> +++++ 02.15.01.02.02 [0..1] BD BD BD Tag Only 1.1.5 {{Or Code <Cd> ++++++ 02.15.01.02.02.01 [1..1] Code BD BD BD Generally not used.

1.1.6 Or}} Proprietary <Prtry> ++++++ 02.15.01.02.02.02 [1..1] Text BD BD BD Generally not used.

1.1.7 Issuer <Issr> +++++ 02.15.01.02.03 [0..1] Text BD BD BD Generally not used.

1.1.8 Type <Tp> +++ 02.15.02 [0..1] BD BD BD Tag Only 1.1.9 {Or Code <Cd> ++++ 02.15.02.01 [1..1] Code BD BD BD Generally not used.

1.1.10 Or} Proprietary <Prtry> ++++ 02.15.02.02 [1..1] Text BD BD BD Generally not used.

1.1.11 Currency <Ccy> +++ 02.15.03 [0..1] Code BD BD BD FPAYHX DTGIS 1.1.12 Name <Nm> +++ 02.15.04 [0..1] Text BD BD BD Generally not used.

2.27 <CdtTrfTxInf> ++ 02.17 [1..n] R R R R Tag Only

2.28 PaymentIdentification <PmtId> +++ 02.17.01 [1..1] R R R R Tag Only 2.29 InstructionIdentification <InstrId> ++++ 02.17.01.01 [0..1] Text BD BD BD O FPAYH DOC1T-DOC1R Needs to be unique over a certain time period per customer.

2.30 EndToEndIdentification <EndToEndId> ++++ 02.17.01.02 [1..1] Text R R R R DMEE_PAYD TEXT (2)

2.31 PaymentTypeInformation <PmtTpInf> +++ 02.17.02 [0..1] R R R R

2.32 InstructionPriority <InstrPrty> ++++ 02.17.02.01 [0..1] Code BD BD NU FPAYHX DTURG


Issuer PrivateIdentification DateAndPlaceOfBirth <DtAndPlcOfBirth

> BirthDate

DateTime

ProvinceOfBirth CityOfBirth CountryOfBirth Other Identification SchemeName Code Proprietary Issuer CountryOfResidence ContactDetails NamePrefix Name PhoneNumber MobileNumber FaxNumber EmailAddress Other ChargeBearer C - CRED,

DEBT, SHAR, SLEV

C - CRED, DEBT, SHAR

Conditional based on payment transaction. Should be used exclusively at the payment or transaction level.

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.

ChargesAccount Identification IBAN

Identifier


Other Identification SchemeName Code Customer Customization


Required Issuer Customer Customization

Required Type Code Customer Customization


Required Currency Name Customer Customization

Required CreditTransferTransactionInformation

CreditTransferTransactionInformation

PaymentIdentification InstructionIdentification

If present, Id to be returned only to ordering party in account statement reporting

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.

EndToEndIdentification

Payment Reference - goes with payment from debtor to creditor and travels through clearing system

SAP supports 10 characters as our standard out of the box. Reference &FPAYH-DOC1R+4(10)& or constant NOTPROVIDED.

MANDATORY. Needs to be unique for every transaction sent across an enterprise over a certain time - best practice suggestion is 12 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).

PaymentTypeInformation

Required at either Payment or Transaction Level, but should not be present at both levels. Recommnded usage is at Payment level.

SAP supports at transaction level for payment type.

Tag Only. Service Level and local instrument should be paired together under the payment type information.

InstructionPriority Based on whether priority processing vs. normal processing is offered by the bank.

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.


1

23

4

5

248

249250

251

252

253254255256257258259260261262263264265266267268269270

271

272273

274

275276277

278

279

280

281

282

283

284

285

326

327

328

329

330

331

Page 17 of 24





StructuralSequence




Cheques/Drafts


2.33 ServiceLevel <SvcLvl> ++++ 02.17.02.02 [0..1] R R NU R Tag Only

2.34 {Or Code <Cd> +++++ 02.17.02.02.01 [1..1] Code XOR XOR NU R - SEPA FPAYH DTURG or DTWS1

2.35 Or} Proprietary <Prtry> +++++ 02.17.02.02.02 [1..1] Text XOR XOR NU Conditional. See CGI Note in Column O.

2.36 LocalInstrument <LclInstrm> ++++ 02.17.02.03 [0..1] R R C O Tag Only

2.37 {Or Code <Cd> +++++ 02.17.02.03.01 [1..1] Code XOR XOR NU Value List

2.38 Or} Proprietary <Prtry> +++++ 02.17.02.03.02 [1..1] Text XOR XOR Conditional. See CGI Note in Column O.

2.39 CategoryPurpose <CtgyPurp> ++++ 02.17.02.04 [0..1] C C NU O Tag Only

2.40 {Or Code <Cd> +++++ 02.17.02.04.01 [1..1] Code XOR XOR NU O FPAYH DTWS1

2.41 Or} Proprietary <Prtry> +++++ 02.17.02.04.02 [1..1] Text XOR XOR NU C

2.42 Amount <Amt> +++ 02.17.03 [1..1] R R R R Tag Only 2.43 {Or InstructedAmount ++++ 02.17.03.01 [1..1] XOR XOR XOR R FPAYH RWBTR with Currency attribute FPAYHX-WAERS

2.44 Or} EquivalentAmount <EqvtAmt> ++++ 02.17.03.02 [1..1] XOR XOR XOR Tag Only 2.45 Amount +++++ 02.17.03.02.01 [1..1] R R R #EXIT DMEE_EXIT_CGI_EQVTAMT

2.46 CurrencyOfTransfer <CcyOfTrf> +++++ 02.17.03.02.02 [1..1] Code R R R #EXIT DMEE_EXIT_CGI_CCYOFTRF 2.47 ExchangeRateInformation <XchgRateInf> +++ 02.17.04 [0..1] BD BD BD Tag Only

2.48 ExchangeRate <XchgRate> ++++ 02.17.04.01 [0..1] Rate BD BD BD

2.49 RateType <RateTp> ++++ 02.17.04.02 [0..1] Code BD BD BD

2.50 ContractIdentification <CtrctId> ++++ 02.17.04.03 [0..1] Text BD BD BD

2.51 ChargeBearer <ChrgBr> +++ 02.17.05 [0..1] Code NU R - SLEV FPAYHX DTKVS

2.52 ChequeInstruction <ChqInstr> +++ 02.17.06 [0..1] NU NU R

2.53 ChequeType <ChqTp> ++++ 02.17.06.01 [0..1] Code NU NU FPAYH DTWS CGI allowed values are BCHQ, CCHQ, DRFT.

2.54 ChequeNumber <ChqNb> ++++ 02.17.06.02 [0..1] Text NU NU C FPAHX CHECK

2.55 ChequeFrom <ChqFr> ++++ 02.17.06.03 [0..1] NU NU C Tag Only

ServiceLevel If an instrument or country is not listed on Appendix A, agreement will be bilateral until included on the list.


Instruction keys needs to be maintained to be able to use the code values.



LocalInstrument If an instrument or country is not listed on Appendix A, agreement will be bilateral until included on the list.

Code ONCL = overnight clearingSDCL = same day clearing

If <Cd> is populated, <Prtry> should not be populated. A code from the external code list should be used.


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

Proprietary C - Check Issuance (CII)



CategoryPurpose Conditional based on country payment instrument. If <CtgyPurp> is used, one of <Cd> or <Prtry> must be used.


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.



Amount InstructedAmount <InstdAmt

Ccy="AAA"> Amount

EquivalentAmount Amount <Amt

Ccy="AAA"> Amount

CurrencyOfTransfer ExchangeRateInformation

ExchangeRate Customer Customization Required

RateType Customer Customization Required

ContractIdentification


ChargeBearer C - CRED, DEBT, SHAR, SLEV

C - CRED, DEBT, SHAR

Conditional based on payment transaction. Should be used exclusively at the payment or transaction level.

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.

ChequeInstruction Tag Only. Only applicable when a check or draft is asked to be generated by the bank.

ChequeType R - BCHQ, CCHQ, DRFT

Instruction Key T015W indicates Bank Check or Local Check.

ChequeNumber Required only for Customer Cheques

ChequeFrom Populated only if info different from Debtor/Ultimate Debtor; assumes Ultimate Debtor takes precedence over Debtor if populated.


1

23

4

5

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

Page 18 of 24





StructuralSequence




Cheques/Drafts


2.56 Name <Nm> +++++ 02.17.06.03.01 [1..1] Text NU NU C

2.57 Address <Adr> +++++ 02.17.06.03.02 [1..1] NU NU C Tag Only

10.1.0 AddressType <AdrTp> ++++++ 02.17.06.03.02.01 [0..1] Code NU NU NU

10.1.1 Department <Dept> ++++++ 02.17.06.03.02.02 [0..1] Text NU NU BD See recommendation above.

10.1.2 SubDepartment <SubDept> ++++++ 02.17.06.03.02.03 [0..1] Text NU NU BD See recommendation above.

10.1.3 StreetName <StrtNm> ++++++ 02.17.06.03.02.04 [0..1] Text NU NU BD See recommendation above.

10.1.4 BuildingNumber <BldgNb> ++++++ 02.17.06.03.02.05 [0..1] Text NU NU BD See recommendation above.

10.1.5 PostCode <PstCd> ++++++ 02.17.06.03.02.06 [0..1] Text NU NU BD

10.1.6 TownName <TwnNm> ++++++ 02.17.06.03.02.07 [0..1] Text NU NU BD See recommendation above.

10.1.7 CountrySubDivision <CtrySubDvsn> ++++++ 02.17.06.03.02.08 [0..1] Text NU NU BD Country dependent

10.1.8 Country <Ctry> ++++++ 02.17.06.03.02.09 [0..1] Code NU NU R See recommendation above.

10.1.9 AddressLine <AdrLine> ++++++ 02.17.06.03.02.10 [0..7] Text NU NU BD See recommendation above.

2.58 DeliveryMethod <DlvryMtd> ++++ 02.17.06.04 [0..1] NU NU C Tag Only

2.59 {Or Code <Cd> +++++ 02.17.06.04.01 [1..1] Code NU NU XOR FPAYH DTWS*

2.60 Or} Proprietary <Prtry> +++++ 02.17.06.04.02 [1..1] Text NU NU XOR

2.61 DeliverTo <DlvrTo> ++++ 02.17.06.05 [0..1] NU NU C Tag Only

2.62 Name <Nm> +++++ 02.17.06.05.01 [1..1] Text NU NU C

2.63 Address <Adr> +++++ 02.17.06.05.02 [1..1] NU NU C Tag Only

10.1.0 AddressType <AdrTp> ++++++ 02.17.06.05.02.01 [0..1] Code NU NU NU

10.1.1 Department <Dept> ++++++ 02.17.06.05.02.02 [0..1] Text NU NU BD See recommendation above.

10.1.2 SubDepartment <SubDept> ++++++ 02.17.06.05.02.03 [0..1] Text NU NU BD See recommendation above.

10.1.3 StreetName <StrtNm> ++++++ 02.17.06.05.02.04 [0..1] Text NU NU BD See recommendation above.

10.1.4 BuildingNumber <BldgNb> ++++++ 02.17.06.05.02.05 [0..1] Text NU NU BD See recommendation above.

10.1.5 PostCode <PstCd> ++++++ 02.17.06.05.02.06 [0..1] Text NU NU BD

Name Customer Customization Required

Address RECOMMENDATION: 1. Use only structured address.2. Use only Address Line (up to 7 lines; instrument by instrument limitations may 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.

AddressType Customer Customization Required

Department Customer Customization Required

SubDepartment Customer Customization Required

StreetName Customer Customization Required

BuildingNumber Customer Customization Required

PostCode See recommendation above. Country dependent


TownName Customer Customization Required

CountrySubDivision Customer Customization Required

Country Customer Customization Required

AddressLine Customer Customization Required

DeliveryMethod Populated to advise how cheque/draft is to be delivered

Code If <Cd> is populated, <Prtry> should not be populated. A code from the list in the schema should be used.

Use Instruction Keys. Can define additional instructions including code for the delivery method.



DeliverTo Populated only if info different from Creditor/Ultimate Creditor; assumes Ultimate Creditor takes precedence over Creditor if populated.

Name Customer Customization Required


AddressType Customer Customization Required

Department Customer Customization Required

SubDepartment Customer Customization Required

StreetName Customer Customization Required

BuildingNumber Customer Customization Required

PostCode See recommendation above. Country dependent



1

23

4

5

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

Page 19 of 24





StructuralSequence




Cheques/Drafts


10.1.6 TownName <TwnNm> ++++++ 02.17.06.05.02.07 [0..1] Text NU NU BD See recommendation above.

10.1.7 CountrySubDivision <CtrySubDvsn> ++++++ 02.17.06.05.02.08 [0..1] Text NU NU BD Country dependent

10.1.8 Country <Ctry> ++++++ 02.17.06.05.02.09 [0..1] Code NU NU R

10.1.9 AddressLine <AdrLine> ++++++ 02.17.06.05.02.10 [0..7] Text NU NU BD See recommendation above.

2.64 InstructionPriority <InstrPrty> ++++ 02.17.06.06 [0..1] Code NU NU BD FPAYHX DTURG 2.65 ChequeMaturityDate <ChqMtrtyDt> ++++ 02.17.06.07 [0..1] NU NU C FPAYH VALUT Value Date is the same as ChequeMaturityDate

2.66 FormsCode <FrmsCd> ++++ 02.17.06.08 [0..1] Text NU NU BD

2.67 MemoField <MemoFld> ++++ 02.17.06.09 [0..2] Text NU NU BD FPAYHX REF*

2.68 RegionalClearingZone <RgnlClrZone> ++++ 02.17.06.10 [0..1] Text NU NU BD

2.69 PrintLocation <PrtLctn> ++++ 02.17.06.11 [0..1] Text NU NU BD

2.70 UltimateDebtor <UltmtDbtr> +++ 02.17.07 [0..1] C C C O Tag Only

9.1.0 Name <Nm> ++++ 02.17.07.01 [0..1] Text R R R FPAYP BNAME

9.1.1 PostalAddress <PstlAdr> ++++ 02.17.07.02 [0..1] C C C R Tag Only

9.1.3 Department <Dept> +++++ 02.17.07.02.02 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.4 SubDepartment <SubDept> +++++ 02.17.07.02.03 [0..1] Text BD BD BD O See recommendation above. Not Currently Supported 9.1.5 StreetName <StrtNm> +++++ 02.17.07.02.04 [0..1] Text BD BD BD O See recommendation above. FPAYHX REF01 9.1.6 BuildingNumber <BldgNb> +++++ 02.17.07.02.05 [0..1] Text BD BD BD O See recommendation above. FPAYHX REF01(60) 9.1.7 PostCode <PstCd> +++++ 02.17.07.02.06 [0..1] Text BD BD BD FPAYHX REF01(80)

9.1.8 TownName <TwnNm> +++++ 02.17.07.02.07 [0..1] Text BD BD BD O See recommendation above. FPAYP BORT1 9.1.9 CountrySubDivision <CtrySubDvsn> +++++ 02.17.07.02.08 [0..1] Text BD BD BD Country dependent FPAYHX REF01(90)

9.1.10 Country <Ctry> +++++ 02.17.07.02.09 [0..1] Code R R R R See recommendation above. FPAYP BLAND 9.1.11 AddressLine <AdrLine> +++++ 02.17.07.02.10 [0..7] Text BD BD BD See recommendation above. FPAYP BSTRAS

9.1.12 Identification <Id> ++++ 02.17.07.03 [0..1] C C C Tag Only

9.1.13 {Or <OrgId> +++++ 02.17.07.03.01 [1..1] R R R R Tag Only

9.1.14 BICOrBEI <BICOrBEI> ++++++ 02.17.07.03.01.01 [0..1] C C C O Generally not used

9.1.15 Other <Othr> ++++++ 02.17.07.03.01.02 [0..n] C C C O Tag Only 9.1.16 Identification <Id> +++++++ 02.17.07.03.01.02.01 [1..1] Text R R R R

9.1.17 SchemeName <SchmeNm> +++++++ 02.17.07.03.01.02.02 [0..1] BD BD BD O Tag Only 9.1.18 {{Or Code <Cd> 02.17.07.03.01.02.02.01 [1..1] Code XOR XOR XOR O

9.1.19 Or}} Proprietary <Prtry> 02.17.07.03.01.02.02.02 [1..1] Text XOR XOR XOR O

9.1.20 Issuer <Issr> +++++++ 02.17.07.03.01.02.03 [0..1] Text NU NU NU O Not Used 9.1.21 Or} PrivateIdentification <PrvtId> +++++ 02.17.07.03.02 [1..1] NU NU NU O Tag Only 9.1.22 ++++++ 02.17.07.03.02.01 [0..1] NU NU NU O Tag Only

9.1.23 BirthDate <BirthDt> +++++++ 02.17.07.03.02.01.01 [1..1] NU NU NU R

TownName Customer Customization Required

CountrySubDivision Customer Customization Required

Country See recommendation above. Country dependent


AddressLine Customer Customization Required

InstructionPriority ChequeMaturityDate

DateTime

If the instrument has a maturity date.

FormsCode Customer Customization Required

MemoField Customer can use any Reference field not used by SAP

RegionalClearingZone


PrintLocation Customer Customization Required

UltimateDebtor Conditional based on business need and payment transaction.

Name R - max. 70 char

Condition check FPAYP-BNAME <> FPAYHX-NAMEZ. Sending company code is different than the paying company code.

PostalAddress RECOMMENDATION: 1. Use only structured address.2. Use only Address Line (up to 7 lines; instrument by instrument limitations may 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.

Department SubDepartment StreetName BuildingNumber PostCode O - Ctry

DpdtSee recommendation above. Country dependent

TownName CountrySubDivision O - Ctry

Dpdt

Country AddressLine 2 lines

(# text to be discussed) Identification O - XOR Only 1 allowed




BICOrBEI Identifier


Other Identification Customer Customization

Required SchemeName Code ++++++

++If <Cd> is populated, <Prtry> should not be populated. A code from the external code list should be used.


Proprietary ++++++++



Issuer PrivateIdentification

DateAndPlaceOfBirth

DateAndPlaceOfBirth <DtAndPlcOfBirth>

BirthDate DateTime



1

23

4

5

379

380

381

382

383

384

385

386

387

388

389

390

391

393394395396

397

398

399

400

401

402

403

404

405

406

407

408

409

410411

412

413

Page 20 of 24





StructuralSequence




Cheques/Drafts


9.1.24 ProvinceOfBirth <PrvcOfBirth> +++++++ 02.17.07.03.02.01.02 [0..1] Text NU NU NU O

9.1.25 CityOfBirth <CityOfBirth> +++++++ 02.17.07.03.02.01.03 [1..1] Text NU NU NU R

9.1.26 CountryOfBirth <CtryOfBirth> +++++++ 02.17.07.03.02.01.04 [1..1] Code NU NU NU R

9.1.27 Other <Othr> ++++++ 02.17.07.03.02.02 [0..n] NU NU NU O Tag Only 9.1.28 Identification <Id> +++++++ 02.17.07.03.02.02.01 [1..1] Text NU NU NU R

9.1.29 SchemeName <SchmeNm> +++++++ 02.17.07.03.02.02.02 [0..1] NU NU NU O Tag Only 9.1.30 {{Or Code <Cd> 02.17.07.03.02.02.02.01 [1..1] Code NU NU NU O

9.1.31 Or}} Proprietary <Prtry> 02.17.07.03.02.02.02.02 [1..1] Text NU NU NU O

9.1.32 Issuer <Issr> +++++++ 02.17.07.03.02.02.03 [0..1] Text NU NU NU O

9.1.33 CountryOfResidence <CtryOfRes> ++++ 02.17.07.04 [0..1] Code C C C O Conditional upon country rules FPAYP BLAND 9.1.34 ContactDetails <CtctDtls> ++++ 02.17.07.05 [0..1] BD BD BD Tag Only 9.1.35 NamePrefix <NmPrfx> +++++ 02.17.07.05.01 [0..1] Code BD BD BD

9.1.36 Name <Nm> +++++ 02.17.07.05.02 [0..1] Text BD BD BD

9.1.37 PhoneNumber <PhneNb> +++++ 02.17.07.05.03 [0..1] Text BD BD BD

9.1.38 MobileNumber <MobNb> +++++ 02.17.07.05.04 [0..1] Text BD BD BD

9.1.39 FaxNumber <FaxNb> +++++ 02.17.07.05.05 [0..1] Text BD BD BD

9.1.40 EmailAddress <EmailAdr> +++++ 02.17.07.05.06 [0..1] Text BD BD BD

9.1.41 Other <Othr> +++++ 02.17.07.05.07 [0..1] Text BD BD BD

2.71 IntermediaryAgent1 <IntrmyAgt1> +++ 02.17.08 [0..1] BD BD NU Tag Only

6.1.0 <FinInstnId> ++++ 02.17.08.01 [1..1] R R NU Tag Only

6.1.1 BIC <BIC> +++++ 02.17.08.01.01 [0..1] C C NU FPAYH BSWIFT1

6.1.2 <ClrSysMmbId> +++++ 02.17.08.01.02 [0..1] C C NU Tag Only

6.1.3 <ClrSysId> ++++++ 02.17.08.01.02.01 [0..1] BD BD NU Tag Only

6.1.4 {Or Code <Cd> +++++++ 02.17.08.01.02.01.01 [1..1] Code XOR XOR NU

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

6.1.6 <MmbId> ++++++ 02.17.08.01.02.02 [1..1] Text R R NU FPAYHX REF04 6.1.7 Name <Nm> +++++ 02.17.08.01.03 [0..1] Text NU NU NU Conditional upon country rules

6.1.8 PostalAddress <PstlAdr> +++++ 02.17.08.01.04 [0..1] R R NU Tag Only 6.1.17 Country <Ctry> ++++++ 02.17.08.01.04.09 [0..1] Code R R NU FPAYH BNKS1 6.1.25 BranchIdentification <BrnchId> ++++ 02.17.08.02 [0..1] BD BD NU Region and Bank Dependent) Tag Only 6.1.26 Identification <Id> +++++ 02.17.08.02.01 [0..1] Text BD BD NU Not Currently Supported### CreditorAgent <CdtrAgt> +++ 02.17.14 [0..1] R R NU R Tag Only 2.78 CreditorAgentAccount <CdtrAgtAcct> +++ 02.17.15 [0..1] C C NU Tag Only 2.79 Creditor <Cdtr> +++ 02.17.16 [0..1] R R R R Tag Only 2.80 CreditorAccount <CdtrAcct> +++ 02.17.17 [0..1] R R NU R Tag Only 1.1.0 Identification <Id> ++++ 02.17.17.01 [1..1] R R NU R Tag Only 1.1.1 {Or IBAN <IBAN> +++++ 02.17.17.01.01 [1..1] XOR XOR NU R FPAYH ZIBAN 1.1.2 Or} Other <Othr> +++++ 02.17.17.01.02 [1..1] XOR XOR NU R-XOR Tag Only 1.1.3 Identification <Id> ++++++ 02.17.17.01.02.01 [1..1] Text R R NU R FPAYHX ZBNKN_EXT 1.1.4 SchemeName <SchmeNm> ++++++ 02.17.17.01.02.02 [0..1] BD NU NU Tag Only 1.1.5 {{Or Code <Cd> +++++++ 02.17.17.01.02.02.01 [1..1] Code BD NU NU

1.1.6 Or}} Proprietary <Prtry> +++++++ 02.17.17.01.02.02.02 [1..1] Text BD NU NU

1.1.7 Issuer <Issr> ++++++ 02.17.17.01.02.03 [0..1] Text BD NU NU

ProvinceOfBirth Customer Customization Required

CityOfBirth Customer Customization Required

CountryOfBirth Customer Customization Required

Other Identification Customer Customization

Required

SchemeName Code ++++++

++Customer Customization Required




CountryOfResidence ContactDetails NamePrefix Customer Customization

Required Name Customer Customization

Required PhoneNumber Customer Customization

Required MobileNumber Customer Customization

Required FaxNumber Customer Customization

Required EmailAddress Customer Customization

Required Other Customer Customization

Required IntermediaryAgent1 Might be required for certain

types of payments if an intermediary is present. Bank requirements may vary.



BIC Identifier

Note 1625129 needs to be implemented by the customer in order to be able to use the source field









MemberIdentification

MemberIdentification The ID will be filled from the database table T045T. Name Customer Customization

Required PostalAddress Country BranchIdentification Identification CreditorAgent CreditorAgentAccount

Conditional base on country rules. Creditor

CreditorAccount Identification IBAN

Identifier Other Identification SchemeName Code Customer Customization


Required Issuer Customer Customization

Required


1

23

4

5

414

415

416

417

418

419

420

421

422

423424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441450458459594634648691692693694695696

697

698

699

Page 21 of 24





StructuralSequence




Cheques/Drafts


1.1.8 Type <Tp> ++++ 02.17.17.02 [0..1] C C NU O Country dependent Tag Only 1.1.9 {Or Code <Cd> +++++ 02.17.17.02.01 [1..1] Code XOR XOR NU C #ATOMS

1.1.10 Or} Proprietary <Prtry> +++++ 02.17.17.02.02 [1..1] Text XOR XOR NU

1.1.11 Currency <Ccy> ++++ 02.17.17.03 [0..1] Code BD BD NU R

1.1.12 Name <Nm> ++++ 02.17.17.04 [0..1] Text C C NU O FPAYH KOINH

2.81 UltimateCreditor <UltmtCdtr> +++ 02.17.18 [0..1] C C C R Tag Only

2.82 +++ 02.17.19 [0..n] NU BD NU SAP limits to 4 occurences. Tag Only

2.83 Code <Cd> ++++ 02.17.19.01 [0..1] Code NU BD NU Not Currently Supported 2.84 InstructionInformation <InstrInf> ++++ 02.17.19.02 [0..1] Text NU BD NU FPAYP SGTXT(50) 2.85 InstructionForDebtorAgent +++ 02.17.20 [0..1] Text C C C DMEE_PAYD TEXT

2.86 Purpose <Purp> +++ 02.17.21 [0..1] C C C O Tag Only

2.87 {Or Code <Cd> ++++ 02.17.21.01 [1..1] Code XOR XOR XOR FPAYP XREF3 freetext element

2.88 Or} Proprietary <Prtry> ++++ 02.17.21.02 [1..1] Text XOR XOR XOR FPAYP REF(XX)

2.89 RegulatoryReporting <RgltryRptg> +++ 02.17.22 C C C SC Tag Only

11.1.0 ++++ 02.17.22.01 [0..1] Code C C C SC Not Currently Supported

11.1.1 Authority <Authrty> ++++ 02.17.22.02 [0..1] BD BD BD Tag Only 11.1.2 Name <Nm> +++++ 02.17.22.02.01 [0..1] Text BD BD BD Not Currently Supported 11.1.3 Country <Ctry> +++++ 02.17.22.02.02 [0..1] Code BD BD BD FPAYP LANDL 11.1.4 Details <Dtls> ++++ 02.17.22.03 [0..n] C C C O Tag Only

11.1.5 Type <Tp> +++++ 02.17.22.03.01 [0..1] Text C C C O Not Currently Supported 11.1.6 Date <Dt> +++++ 02.17.22.03.02 [0..1] C C C O Not Currently Supported

11.1.7 Country <Ctry> +++++ 02.17.22.03.03 [0..1] Code C C C O Not Currently Supported 11.1.8 Code <Cd> +++++ 02.17.22.03.04 [0..1] Text C C C O Not Currently Supported 11.1.9 Amount +++++ 02.17.22.03.05 [0..1] C C C O Not Currently Supported

11.1.10 Information <Inf> +++++ 02.17.22.03.06 [0..n] Text C C C O Not Currently Supported 2.90 Tax <Tax> +++ 02.17.23 [0..1] C C C Tag Only

13.1.0 Creditor <Cdtr> ++++ 02.17.23.01 [0..1] C C C O Tag Only 13.1.1 TaxIdentification <TaxId> +++++ 02.17.23.01.01 [0..1] Text C C C O FPAYH STCD1 13.1.2 <RegnId> +++++ 02.17.23.01.02 [0..1] Text C C C O Not Currently Supported

13.1.3 TaxType <TaxTp> +++++ 02.17.23.01.03 [0..1] Text C C C O Not Currently Supported 13.1.4 Debtor <Dbtr> ++++ 02.17.23.02 [0..1] C C C O Tag Only 13.1.5 TaxIdentification <TaxId> +++++ 02.17.23.02.01 [0..1] Text C C C O FPAYHX STCEG 13.1.6 <RegnId> +++++ 02.17.23.02.02 [0..1] Text C C C O Not Currently Supported

13.1.7 TaxType <TaxTp> +++++ 02.17.23.02.03 [0..1] Text C C C O Not Currently Supported 13.1.8 Authorisation <Authstn> +++++ 02.17.23.02.04 [0..1] C C C O Tag Only 13.1.9 Title <Titl> ++++++ 02.17.23.02.04.01 [0..1] Text C C C O Not Currently Supported 13.1.10 Name <Nm> ++++++ 02.17.23.02.04.02 [0..1] Text C C C O Not Currently Supported 13.1.11 AdministrationZone <AdmstnZn> ++++ 02.17.23.03 [0..1] Text C C C O Not Currently Supported

Type Code If <Cd> is populated, <Prtry>

should not be populated. A code from the list in the schema should be used.

Source is the FPAYH-ZBKON field to map the control keys to the codelist provided in the schema.



Currency Constant = EUR for SEPA.

For SEPA must be constant - EUR. Customer customization if required for other than SEPA transaction.

Name Dependent upon Credit Agent validation

UltimateCreditor Conditional based on business need and payment transaction.

InstructionForCreditorAgent InstructionForCreditorAgent

<InstrForCdtrAgt>

Conditional based on country rules; may also be bank determined.

Code Not Currently Supported InstructionInformation

InstructionForDebtorAgent

<InstrForDbtrAgt>

Conditional based on country rules; may also be bank determined. Can be utilized to indicate signatures for checks where required by your bank. Boletto Bar Code /BRTL/+41 digit bar code

Purpose Conditional based on country rules; may also be bank determined.



See Implementation Note 1665873 on how to implement a workaround using a text field for those customers that require this field.

RegulatoryReporting [0..10]

Dependent upon jurisdiction/country

DebitCreditReportingIndicator

DebitCreditReportingIndicator

<DbtCdtRptgInd>


Authority Name Country Details Dependent upon

jurisdiction/country Type Date

DateTime

Country Code Amount <Amt

Ccy="AAA"> Amount

Information Tax C -

Depends on Country


Creditor TaxIdentification

RegistrationIdentification


TaxType Debtor TaxIdentification



TaxType Authorisation Title Name AdministrationZone


1

23

4

5

700

701

702

703

704

705

748

749750

751

752

753

754

755

756

757758759

760

761

762

763764

765

766

767

768769

770

771772773

774

775776777778779

Page 22 of 24





StructuralSequence




Cheques/Drafts


13.1.12 ReferenceNumber <RefNb> ++++ 02.17.23.04 [0..1] Text C C C O Not Currently Supported 13.1.13 Method <Mtd> ++++ 02.17.23.05 [0..1] Text C C C O Not Currently Supported 13.1.14 ++++ 02.17.23.06 [0..1] C C C O Not Currently Supported

13.1.15 TotalTaxAmount ++++ 02.17.23.07 [0..1] C C C O Not Currently Supported

13.1.16 Date <Dt> ++++ 02.17.23.08 [0..1] C C C O Not Currently Supported

13.1.17 SequenceNumber <SeqNb> ++++ 02.17.23.09 [0..1] C C C O Not Currently Supported 13.1.18 Record <Rcrd> ++++ 02.17.23.10 [0..n] C C C O Tag Only 13.1.19 Type <Tp> +++++ 02.17.23.10.01 [0..1] Text C C C O Not Currently Supported 13.1.20 Category <Ctgy> +++++ 02.17.23.10.02 [0..1] Text C C C O Not Currently Supported 13.1.21 CategoryDetails <CtgyDtls> +++++ 02.17.23.10.03 [0..1] Text C C C O Not Currently Supported 13.1.22 DebtorStatus <DbtrSts> +++++ 02.17.23.10.04 [0..1] Text C C C O Not Currently Supported 13.1.23 <CertId> +++++ 02.17.23.10.05 [0..1] Text C C C O Not Currently Supported 13.1.24 FormsCode <FrmsCd> +++++ 02.17.23.10.06 [0..1] Text C C C O Not Currently Supported 13.1.25 Period <Prd> +++++ 02.17.23.10.07 [0..1] C C C O Tag Only 13.1.26 Year <Yr> ++++++ 02.17.23.10.07.01 [0..1] C C C O Not Currently Supported

13.1.27 Type <Tp> ++++++ 02.17.23.10.07.02 [0..1] Code C C C O Not Currently Supported 13.1.28 FromToDate <FrToDt> ++++++ 02.17.23.10.07.03 [0..1] C C C O Tag Only 13.1.29 FromDate <FrDt> +++++++ 02.17.23.10.07.03.01 [1..1] C C C O Not Currently Supported

13.1.30 ToDate <ToDt> +++++++ 02.17.23.10.07.03.02 [1..1] C C C O Not Currently Supported

13.1.31 TaxAmount <TaxAmt> +++++ 02.17.23.10.08 [0..1] C C C O Tag Only 13.1.32 Rate <Rate> ++++++ 02.17.23.10.08.01 [0..1] Rate C C C O Not Currently Supported 13.1.33 ++++++ 02.17.23.10.08.02 [0..1] C C C O Not Currently Supported

13.1.34 TotalAmount ++++++ 02.17.23.10.08.03 [0..1] C C C O Not Currently Supported

13.1.35 Details <Dtls> ++++++ 02.17.23.10.08.04 [0..n] C C C O Tag Only 13.1.36 Period <Prd> +++++++ 02.17.23.10.08.04.01 [0..1] C C C O Tag Only 13.1.37 Year <Yr> 02.17.23.10.08.04.01.01 [0..1] C C C O Not Currently Supported

13.1.38 Type <Tp> 02.17.23.10.08.04.01.02 [0..1] Code C C C O Not Currently Supported

13.1.39 FromToDate <FrToDt> 02.17.23.10.08.04.01.03 [0..1] C C C O Tag Only

13.1.40 FromDate <FrDt> 02.17.23.10.08.04.01.03.01 [1..1] C C C O Not Currently Supported

13.1.41 ToDate <ToDt> 02.17.23.10.08.04.01.03.02 [1..1] C C C O Not Currently Supported

13.1.42 Amount +++++++ 02.17.23.10.08.04.02 [1..1] C C C O Not Currently Supported

13.1.43 AdditionalInformation <AddtlInf> +++++ 02.17.23.10.09 [0..1] Text C C C O Not Currently Supported 2.91 <RltdRmtInf> +++ 02.17.24 BD BD BD O SAP calls this note to payee Tag Only

2.92 RemittanceIdentification <RmtId> ++++ 02.17.24.01 [0..1] Text BD BD BD O Customer Customization

2.93 <RmtLctnMtd> ++++ 02.17.24.02 [0..1] Code BD BD BD O Customer Customization

2.94 ++++ 02.17.24.03 [0..1] Text BD BD BD O Customer Customization

2.95 ++++ 02.17.24.04 [0..1] BD BD BD O Tag Only

2.96 Name <Nm> +++++ 02.17.24.04.01 [1..1] Text R R R R Not Currently Supported

ReferenceNumber Method

TotalTaxableBaseAmount

TotalTaxableBaseAmount

<TtlTaxblBaseAmt Ccy="AAA">

Amount

TotalTaxAmount <TtlTaxAmt Ccy="AAA">

Amount

Date DateTime

SequenceNumber Quantity Record

Type Category CategoryDetails DebtorStatus

CertificateIdentification

CertificateIdentificatio FormsCode Period Year

DateTime

Type FromToDate FromDate

DateTime

ToDate DateTime

TaxAmount Rate

TaxableBaseAmount

TaxableBaseAmount <TaxblBaseAmt Ccy="AAA">

Amount

TotalAmount <TtlAmt Ccy="AAA">

Amount

Details Period Year ++++++

++ DateTime

Type ++++++++

FromToDate ++++++++

FromDate +++++++++

DateTime

ToDate +++++++++

DateTime

Amount <Amt Ccy="AAA">

Amount

AdditionalInformation RelatedRemittanceInformation

RelatedRemittanceInformation

[0..10]

RemittanceIdentification

RemittanceLocationMethod

RemittanceLocationMethod

RemittanceLocationElectronicAddress

RemittanceLocationElectronicAddress

<RmtLctnElctrncAdr>

RemittanceLocationPostalAddress

RemittanceLocationPostalAddress

<RmtLctnPstlAdr>

Name


1

23

4

5

780781

782

783

784

785786787788789790791792793

794

795796

797

798

799800

801

802

803804

805

806

807

808

809

810

811

812

813

814

815

816

817

Page 23 of 24





StructuralSequence




Cheques/Drafts


2.97 Address <Adr> +++++ 02.17.24.04.02 [1..1] R R R R Tag Only

10.1.1 Department <Dept> ++++++ 02.17.24.04.02.02 [0..1] Text BD BD BD See recommendation above. Not Currently Supported 10.1.2 SubDepartment <SubDept> ++++++ 02.17.24.04.02.03 [0..1] Text BD BD BD See recommendation above. Not Currently Supported 10.1.3 StreetName <StrtNm> ++++++ 02.17.24.04.02.04 [0..1] Text BD BD BD See recommendation above. Not Currently Supported 10.1.4 BuildingNumber <BldgNb> ++++++ 02.17.24.04.02.05 [0..1] Text BD BD BD See recommendation above. Not Currently Supported 10.1.5 PostCode <PstCd> ++++++ 02.17.24.04.02.06 [0..1] Text BD BD BD Not Currently Supported

10.1.6 TownName <TwnNm> ++++++ 02.17.24.04.02.07 [0..1] Text BD BD BD See recommendation above. Not Currently Supported 10.1.7 CountrySubDivision <CtrySubDvsn> ++++++ 02.17.24.04.02.08 [0..1] Text BD BD BD Country dependent Not Currently Supported 10.1.8 Country <Ctry> ++++++ 02.17.24.04.02.09 [0..1] Code R R R See recommendation above. Not Currently Supported 10.1.9 AddressLine <AdrLine> ++++++ 02.17.24.04.02.10 [0..7] Text BD BD BD See recommendation above. Not Currently Supported 2.98 RemittanceInformation <RmtInf> +++ 02.17.25 [0..1] BD/C BD/C BD/C Tag Only

2.99 Unstructured <Ustrd> ++++ 02.17.25.01 [0..n] Text BD/C BD/C BD/C DMEE_PAYD TEXT (3)

2.100 Structured <Strd> ++++ 02.17.25.02 [0..n] BD/C BD/C BD/C Tag Only

2.101 <RfrdDocInf> +++++ 02.17.25.02.01 [0..n] BD/C BD/C BD/C Tag Only

2.102 Type <Tp> ++++++ 02.17.25.02.01.01 [0..1] BD/C BD/C BD/C Tag Only 2.103 <CdOrPrtry> +++++++ 02.17.25.02.01.01.01 [1..1] R R R Tag Only 2.104 {Or Code <Cd> 02.17.25.02.01.01.01.01 [1..1] Code XOR XOR XOR Atom

2.105 Or} Proprietary <Prtry> 02.17.25.02.01.01.01.02 [1..1] Text XOR XOR XOR Rarely used. Customer customization if required.

2.106 Issuer <Issr> +++++++ 02.17.25.02.01.01.02 [0..1] Text BD BD BD

2.107 Number <Nb> ++++++ 02.17.25.02.01.02 [0..1] Text R R R FPAYP XBLNR 2.108 RelatedDate <RltdDt> ++++++ 02.17.25.02.01.03 [0..1] BD/C BD/C BD/C FPAYP BLDAT

2.109 <RfrdDocAmt> +++++ 02.17.25.02.02 [0..1] BD/C BD/C BD/C Tag Only

2.110 DuePayableAmount ++++++ 02.17.25.02.02.01 [0..1] BD/C BD/C BD/C FPAYP WRBTR

2.111 ++++++ 02.17.25.02.02.02 [0..1] BD/C BD/C BD/C FPAYP WSKTO

2.112 CreditNoteAmount ++++++ 02.17.25.02.02.03 [0..1] BD/C BD/C BD/C FPAYP WRBTR


Department SubDepartment StreetName BuildingNumber PostCode See recommendation above.

Country dependent

TownName CountrySubDivision Country AddressLine RemittanceInformation

O - either Ustrd or Strd

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

Unstructured R -XOR - Only 1 occurrence - limited to 140 characters

Reference &FPAYHX-EIKTO& (if nonempty) . DMEE_PAYD TEXT (1) Reference: /INV/FPAYP-XBLNR& &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.

Structured R - XOR - Only 1 occurrence - limited to 140 characters

Best practice for minimum usage: invoice number and remitted amount or credit note amount with currency

ReferredDocumentInformation

ReferredDocumentInformation

Type CodeOrProprietary

CodeOrProprietary Code ++++++

++If <Cd> is populated, <Prtry> should not be populated. A code from the list in the schema should be used.

CONSTANT CINV or CREN

Customer can use other codes from the schema by adding additional atoms through customization


If <Prtry> is populated, <Cd> should not be populated. The condition is based on the need to use a proprietary code not on the schema code list per bilateral agreement.



Number RelatedDate

DateTime

ReferredDocumentAmount

ReferredDocumentAmount

DuePayableAmount <DuePyblAmt Ccy="AAA">

Amount Amount due as stated on referred document

For the attribute of this element the Source is FPAYP, and the Source Field is WAERS

DiscountAppliedAmount

DiscountAppliedAmount

<DscntApldAmt Ccy="AAA">

Amount Discount amount applied against amount on invoice

For the attribute of this element the Source is FPAYP, and the Source Field is WAERS

CreditNoteAmount <CdtNoteAmt Ccy="AAA">

Amount Credit amount of a credit note or credit memo

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


1

23

4

5

818

820821822823

824

825826827828

829

830

831

832

833834

835

836

837

838

839

840

841

842

843

Page 24 of 24





StructuralSequence




Cheques/Drafts


2.113 TaxAmount ++++++ 02.17.25.02.02.04 [0..1] BD/C BD/C BD/C FPAYP WQSTE

2.114 ++++++ 02.17.25.02.02.05 [0..n] BD/C BD/C BD/C Tag Only

2.115 Amount +++++++ 02.17.25.02.02.05.01 [1..1] R R R

2.116 <CdtDbtInd> +++++++ 02.17.25.02.02.05.02 [0..1] Code BD/C BD/C BD/C Not Currently Supported

2.117 Reason <Rsn> +++++++ 02.17.25.02.02.05.03 [0..1] Text BD/C BD/C BD/C Not Currently Supported 2.118 <AddtlInf> +++++++ 02.17.25.02.02.05.04 [0..1] Text BD/C BD/C BD/C Not Currently Supported

2.119 RemittedAmount ++++++ 02.17.25.02.02.06 [0..1] BD/C BD/C BD/C FPAYP WNETT

2.120 <CdtrRefInf> +++++ 02.17.25.02.03 [0..1] BD BD BD O Tag Only

2.121 Type <Tp> ++++++ 02.17.25.02.03.01 [0..1] BD BD BD O Tag Only 2.122 <CdOrPrtry> +++++++ 02.17.25.02.03.01.01 [1..1] R R R O Tag Only 2.123 {Or Code <Cd> 02.17.25.02.03.01.01.01 [1..1] Code X0R X0R X0R R - SCOR Constant SCOR (SEPA Only)

2.124 Or} Proprietary <Prtry> 02.17.25.02.03.01.01.02 [1..1] Text X0R X0R X0R

2.125 Issuer <Issr> +++++++ 02.17.25.02.03.01.02 [0..1] Text BD BD BD O Constant Conditional Value ISO

2.126 Reference <Ref> ++++++ 02.17.25.02.03.02 [0..1] Text R R R O FPAYP STRFR

2.127 Invoicer <Invcr> +++++ 02.17.25.02.04 [0..1] BD BD BD O Tag Only 9.1.0 Name <Nm> ++++++ 02.17.25.02.04.01 [0..1] Text R R R O Not Currently Supported 2.129 <AddtlRmtInf> +++++ 02.17.25.02.06 [0..3] Text BD BD BD O DMEE_PAYD TEXT Type 1

TaxAmount <TaxAmt Ccy="AAA">

Amount Tax amount on referred document

For the attribute, the Source is FPAYP, and the Source Field is WAERS. SAP support is limited to withholding tax amount.

AdjustmentAmountAndReason

AdjustmentAmountAndReason

<AdjstmntAmtAndRsn>

Adjustment amount and reason applicable to referred document

Amount <Amt Ccy="AAA">

Amount Customer Customization Required

CreditDebitIndicator

CreditDebitIndicator

Reason AdditionalInformation

AdditionalInformation

RemittedAmount <RmtdAmt Ccy="AAA">

Amount Amount being paid on referred document

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

CreditorReferenceInformation

CreditorReferenceInformation

If the structure field FPPSTRFR is filled with value, then this will be printed, otherwise left out.

Type CodeOrProprietary

CodeOrProprietary Code ++++++

++If <Cd> is populated, <Prtry> should not be populated. A code from the list in the schema should be used.

Constant value "SCOR" for SEPA Payment Type. If customer wants to use this field for any other payment type, they must do a customization.


If <Prtry> is populated, <Cd> should not be populated. The condition is based on the need to use a proprietary code not on the schema code list per bilateral agreement.


Issuer Value of 'ISO' reserved for ISO 11649 international creditor's reference.

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.

Reference If Creditor Reference Information is used, Reference must be included.

Invoicer Name

AdditionalRemittanceInformation

AdditionalRemittanceInformation

Default for additional remittance info


1

23

4

5

844

845

846

847

848

849

850

851

852853

854

855

856

857

858859

944

Documents

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