ISO 20022 Message Implementation Guidelines for payment initiation
pain.001.001.03
CustomerCreditTransferInitiationV03
Version:
0.1
Date:
31/08/2015
Author:
Nordea Bank AB Lithuania branch
pain.001.001.03
Date
Page
31/08/2015
2 of 26
Table of contents
1.
Introduction .....................................................................................................................................3
2.
Nordea usage of ISO20022 XML format ..........................................................................................3
3.
Character set ....................................................................................................................................4
4.
Reference .........................................................................................................................................5
5.
Guidelines.........................................................................................................................................6
pain.001.001.03
Date
Page
31/08/2015
3 of 26
1. Introduction
This Message Implementation Guideline (MIG) were prepared on behalf of Nordea Bank AB Lithuania
branch (hereinafter “Nordea”).
The purpose of this documentation is to define how information in payment Messages should be structured
for the exchange between the Message sender and Nordea.
2. Nordea usage of ISO20022 XML format
The term “message” is used for one XML schema occurrence, which is a combination of blocks called Group
Header, Payment Information and Credit Transfer Transaction Information. One file can contain several messages. A message sent to Nordea can contain payments from several Debtors/accounts, and can also contain
several payment messages.
All elements or tags defined as “Mandatory” by ISO20022 for pain.001.001.03 are included in Nordea’s MIG.
This also includes elements or tags that are optional or conditional, depending on specific criteria, as set by
the service (or local country infrastructure).
The following is a description of used fields and columns in the MIG:
ISO
Index
Or
Structural
Sequence
pain.001.001.03 Payment Initiation
Message Item
XML Tag
Mult.
Type
Nordea
comment
E-firma
users
E-Bank
users
ISO Index No = Reference number that refers to the related description in the “ISO 20022 Message Definition
Report”
Or = Nordea will provide one or the other field, but not both
Structural Sequence = When an element contains sub-elements these are indented to the right and noted
with a plus sign (+) per level.
Message Item = Refers to the actual tag name in ISO20022 XML, which is also stated under the column XML
Tag Name. This can be a Message element (a.k.a. a “field” in a traditional sense), or a Message Component
(i.e. a group of information consisting of several elements). Each message element is stated with the element
type it comprises (stated under column Type).
XML Tag = Specific code referring to an XML element, and will be part of the XML Schema for the identification of an XML element. The “Tag Name” will be stated at the beginning of a string which is to include the
required information (i.e. <Dbtr>) and will end the string with the same “Tag Name”, starting with a slash
(i.e. </Dbtr>).
Multiplicity = Informs how many times an element can or must be used, as defined by ISO.
1..1
1..n
1..3
0..1
0..n
One occurrence (required)
One or several occurrences (value for “n” represents total number of occurrences)
Minimum one occurrence must be used and maximum 3 occurrences can be used.
Note: True value of “n” represents unlimited number of occurrences.
None or one occurrence to be used (optional)
None or several occurrences can be used (value for “n” represents total number of occurrences)
pain.001.001.03
Date
Page
31/08/2015
4 of 26
Note: True value of “n” represents unlimited number of occurrences.
Type = States the value to be transferred in the actual XML element. There are a total of seven different “Data Type” representations that can be used in a “CustomerCreditTransferInitiating”: Identifier, Code, Text,
Rate, Date Time, Amount & Indicator. See examples below:
Data Type
Identifier
Code
Text
Rate
Date Time
Amount
Indicator
Type
PartyId32
PaymentMethod3Code
Max35Text
Rate
ISODateTime
DecimalNumber
Indicator
ISO Index
1.8
2.2
2.1
2.48
1.2
2.5
2.3
Example
SALES COMPANY PARTY
TRF = Credit Transfer
AA22BB11
10.99999
2014-01-15T10:15:25
99999.99
true = Batch booking requested
Nordea comment = Informs of special rules or usage for each element. If no comments exist, then standard
usage according to ISO20022 applies.
The files sent to Nordea must be in UTF-8 format.
Further information on ISO 20022 definitions on pain.001.001.03 are provided on the ISO20022 website: Link
in the document “Payments_Maintenance_2009.pdf”, under the headline “pain – Payments initiation”.
E-Firma users = marked elements which can be saved on E-Firma database (without mandatory elements).
E-Bank users = marked elements which can be saved on E-Bank database (without mandatory elements).
3. Character set
The character set issue centres on the use of the full set characters in the message elements. Two considerations are:
 While banks and their customers must be allowed to use the character set currently in use at national level,
 Banks and their customers throughout SEPA cannot be required to support the full character set
used in SEPA countries.
Therefore:
 The ISO 20022 XML messages allow for the full range of global language requirements (UTF-8).
 Banks and their customers must be able to support the Latin character set commonly used in international communication, as follows:
abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/-?:().,'+
Space
pain.001.001.03

Date
Page
31/08/2015
5 of 26
References, identifications and identifiers must respect the following: o Content is restricted to the
Latin character set as defined above
o Content must not start or end with a ‘/’
o Content must not contain ‘//’s
However, there may be bilateral or multilateral agreements to support one or more sets of characters beyond the Latin character set referred to above.
4. Reference
No.
Document name
1
SEPA Credit Transfer
Scheme Customer – to –
Bank Implementation Guidelines
2
LITAS – ESIS duomenų
formato konversijos į ISO
20022 standarto pranešimų
formatus gairės
ISO 20022 XML standarto
pranešimų naudojimo
taisyklės, 2015 m
3
Version
8.0
1.1
2.4
Link
http://www.europeanpaymentscouncil.eu/index.cfm/
knowledge-bank/epc-documents/sepa-credittransfer-scheme-customer-to-bank-implementationguidelines-version-8/epc132-08-c2b-ctig-v80approvedpdf/
http://sepa.lt/n23444/konversijos_i_iso_20022_gaire
s_v.1.1.pdf
http://sepa.lt/n23444/darbo_su_formatu_taisykles_v
.2.4.pdf
Date
Page
pain.001.001.03
31/08/2015
6 of 26
5. Guidelines
ISO
Index
Structural
Sequence
Or
1.0
+
1.1
++
1.2
pain.001.001.03 Payment Initiation
Message Item
Customer Credit Transfer Initiation
GroupHeader
XML Tag
Mult.
Type
<CstmrCdtTrfInitn>
Nordea comment
Message root, identifying
message type
Set of characteristics shared
by all individual transactions
included in the message
Note! Group header block
will be ignored by Nordea
Point to point reference, as
assigned by the instructing
party, and sent to the next
party in the chain to unambiguously identify the message.
Date and time at which the
message was created.
<GrpHdr>
[1..1]
GroupHeader32
MessageIdentification
<MsgId>
[1..1]
Max35Text
++
CreationDateTime
<CreDtTm>
[1..1]
ISODateTime
1.6
++
NumberOfTransactions
<NbOfTxs>
[1..1]
Max15NumText
Number of individual transactions contained in the
message.
1.7
++
ControlSum
<CtrlSum>
[0..1]
DecimalNumber
Total of all individual
amounts included in the
message, irrespective of
currencies.
1.8
++
InitiatingParty
<InitgPty>
[1..1]
PartyIdentification32
Party that initiates the payment.
9.1.0
+++
Name
<Nm>
[0..1]
Max70Text
Name by which a party is
known and which is usually
used to identify that party.
9.1.12
+++
Identification
<Id>
[0..1]
Party6Choice
Unique and unambiguous
identification of a party.
e-Firma
users
E-Bank
users
Date
Page
pain.001.001.03
9.1.13
{Or
++++
9.1.14
{{Or
+++++
9.1.15
Or}}
+++++
OrganisationIdentification
<OrgId>
[1..1]
Organisation
Identification4
Unique and unambiguous
identification of a party.
BICOrBEI
<BICOrBEI>
[0..1]
AnyBICIdentifier
Code allocated to organisations
Other
<Othr>
[0..1]
GenericOrganisation
Identification1
9.1.16
++++++
Identification
<Id>
[1..1]
Max35Text
9.1.17
++++++
SchemeName
<SchmeNm>
[0..1]
OrganisationIdentification
SchemeName1Choice
Name of the identification
scheme.
9.1.18
+++++++
<Cd>
[1..1]
ExternalOrganisation
Identification1Code
Valid codes:
CUST = Payer‘s code
TXID = Tax payer‘s code
COID = Company code
<PrvtId>
[1..1]
<DtAndPlcOfBirth>
[0..1]
9.1.21
Or}
++++
9.1.22
{{Or
+++++
Code
PrivateIdentification
DateAndPlaceOfBirth
9.1.23
++++++
BirthDate
<BirthDt>
[1..1]
DateTime
9.1.24
++++++
ProvinceOfBirth
<PrvcOfBirth>
[0..1]
Text
9.1.25
++++++
CityOfBirth
<CityOfBirth>
[1..1]
Text
9.1.26
++++++
CountryOfBirth
<CtryOfBirth>
[1..1]
Code
<Othr>
[0..n]
9.1.27
Or}}
+++++
Other
9.1.28
++++++
Identification
<Id>
[1..1]
9.1.29
++++++
SchemeName
<SchmeNm>
[0..1]
9.1.30
+++++++
<Cd>
[1..1]
Code
Text
Code
Identifiers according ISO
20022 code list:
NIDN – National Identity
Number, CUST – Customer
Identification Number,
DRLC – Driver’s License
Number, SOSE – Social Security Number, CCPT – Passport Number,
EMPL – Employee Identification Number,
31/08/2015
7 of 26
Date
Page
pain.001.001.03
2.0
+
2.1
++
2.2
2.3
++
++
PaymentInformation
PaymentInformationIdentification
PaymentMethod
BatchBooking
<PmtInf>
[1..n]
PaymentInstructionInformation3
<PmtInfId>
[1..1]
Max35Text
<PmtMtd>
<BtchBookg>
[1..1]
[0..1]
Payment
Method3Code
Indicator
31/08/2015
8 of 26
TXID – Tax Identification
Number, ARNU – Alien Registration Number.
Set of characteristics that
applies to the debit side of
the payment transactions
included in the credit transfer initiation.
Unique identification, as
assigned by a sending party,
to unambiguously identify
the payment information
group within the message.
Note! This field will be ignored by Nordea Bank.
Valid codes:
TRF = Credit Transfer
Note! This field will be ignored by Nordea Bank.
Identifies whether a single
entry per individual transaction or a batch entry for the
sum of the amounts of all
transactions within the
group of a message is requested.
Usage: Batch booking is used
to request and not order a
possible batch booking.
Valid codes:
false = Single booking requested
true = Batch booking requested
2.6
++
2.8
+++
PaymentTypeInformation
ServiceLevel
<PmtTpInf>
[0..1]
PaymentType
Information19
<SvcLvl>
[0..1]
ServiceLevel8Choice
Note! This block will be ignored by Nordea Bank.
Set of elements used to
further specify the type of
transaction.
Agreement/rule under which
the transaction should be
processed.
+
+
+
+
Date
Page
pain.001.001.03
2.9
++++
Code
<Cd>
[1..1]
External
ServiceLevel1Code
Specifies a pre-agreed service or level of service between the parties, as published in an external service
level code list.
+
Valid codes for SEPA payment:
SEPA = Single Euro Payments
Area (See note below)
Valid codes for international
payment:
NURG = Non-urgent Payment
SDVA = Same Day Value (See
note below)
URGP = Urgent Payment
INTC = Intercompany payment type
Nordea uses NURG as default value.
2.14
2.15
+++
++++
CategoryPurpose
Code
<CtgyPurp>
<Cd>
[0..1]
[1..1]
CategoryPurpose1Choice
External
CategoryPurpose1Code
Note: SEPA will be treated
by Nordea as NURG.
Note: SDVA is not used by
Nordea and payment will be
treated as Intercompany
payment.
Specifies the high-level purpose of the instruction based
on a set of predefined categories.
Payment type INTC can alternatively be specified for
each credit level.
Only for Sepa
Valid codes are:
INTC = Intra company payment
TREA = Treasury payment
SALA = Salary payment
TAXS = Tax payment
More category purpose
+
+
31/08/2015
9 of 26
+
Date
Page
pain.001.001.03
31/08/2015
10 of 26
codes are here:
http://www.iso20022.org/ex
ternal_code_list.page
Only for Sepa
2.17
++
RequestedExecutionDate
<ReqdExctnDt>
[1..1]
ISODate
2.19
++
Debtor
<Dbtr>
[1..1]
PartyIdentification32
9.1.0
+++
Name
<Nm>
[0..1]
Max70Text
9.1.1
+++
PostalAddress
<PstlAdr>
[0..1]
9.1.10
++++
Country
<Ctry>
[0..1]
CountryCode
9.1.11
++++
AddressLine
<AdrLine>
[0..7]
Text70Text
9.1.12
+++
<Id>
[0..1]
Party6Choice
<OrgId>
[1..1]
OrganisationIdentification4
9.1.13
{Or
++++
Identification
OrganisationIdentification
Date at which the initiating
party requests the clearing
agent to process the payment.
Usage: This is the date on
which the debtor's account is
to be debited.
Note! Back value date will be
changed to current date.
Maximum allowed forward
value date is 2 months
ahead.
The party from whose account the amount of payment is to be debited.
Name by which a party is
known and which is usually
used to identify that party.
Note! This field will be ignored by Nordea bank.
Information that locates and
identifies a specific address,
as defined by postal services.
Note! This field will be ignored by Nordea Bank.
Country code, set in ISO
3166
+
+
+
+
+
+
Information that locates and
identifies a specific address,
as defined by postal services,
presented in free format
text.
Unique and unambiguous
identification of either a
party or specific agreement
with Nordea.
+
+
+
+
+
+
+
Date
Page
pain.001.001.03
9.1.14
{{Or
+++++
BICOrBEI
<BICOrBEI>
[0..1]
Identifier
9.1.15
Or}}
+++++
Other
<Othr>
[0..n]
GenericOrganisationIdentification1
Note! This field will be ignored by Nordea Bank.
Identification either assigned
by official authorities or
between Nordea and the
customer.
31/08/2015
11 of 26
+
+
9.1.16
++++++
Identification
<Id>
[1..1]
Max35Text
+
+
9.1.17
++++++
SchemeName
<SchmeNm>
[0..1]
OrganisationIdentification
SchemeName1Choice
+
+
9.1.18
+++++++
<Cd>
[1..1]
External
OrganisationIdentification1Code
+
+
<PrvtId>
[1..1]
<DtAndPlcOfBirth>
[0..1]
9.1.21
Or}
9.1.22
{{Or
++++
+++++
Code
PrivateIdentification
DateAndPlaceOfBirth
9.1.23
++++++
BirthDate
<BirthDt>
[1..1]
DateTime
9.1.24
++++++
ProvinceOfBirth
<PrvcOfBirth>
[0..1]
Text
9.1.25
++++++
CityOfBirth
<CityOfBirth>
[1..1]
Text
9.1.26
++++++
CountryOfBirth
<CtryOfBirth>
[1..1]
Code
<Othr>
[0..n]
9.1.27
Or}}
+++++
Other
9.1.28
++++++
Identification
<Id>
[1..1]
9.1.29
++++++
SchemeName
<SchmeNm>
[0..1]
9.1.30
+++++++
<Cd>
[1..1]
Code
Valid codes:
CUST = Payer‘s code
TXID = Tax payer‘s code
COID = Company code
Note! This block will be
ignored by Nordea Bank.
Text
Code
Identifiers according ISO
20022 code list:
NIDN – National Identity
Number, CUST – Customer
Identification Number,
DRLC – Driver’s License
Number, SOSE – Social Security Number, CCPT – Passport Number,
Date
Page
pain.001.001.03
2.20
++
1.1.0
+++
1.1.1
{Or
DebtorAccount
Identification
IBAN
++++
1.1.11
+++
2.21
++
6.1.0
+++
6.1.1
++++
2.23
++
Currency
DebtorAgent
tion
FinancialInstitutionIdentifica-
BIC
UltimateDebtor
<DbtrAcct>
[1..1]
CashAccount32
<Id>
[1..1]
AccountIdentification4Choice
<IBAN>
[1..1]
IBAN2007Identifier
<Ccy>
[0..1]
ActiveOrHistoricCurrencyCode
<DbtrAgt>
[1..1]
BranchAndFin.Inst.Id4
<FinInstnId>
[1..1]
FinancialInstitution
Identification7
<BIC>
[0..1]
BICIdentifier
<UltmtDbtr>
[0..1]
PartyId32
EMPL – Employee Identification Number,
TXID – Tax Identification
Number, ARNU – Alien Registration Number.
Unambiguous identification
of the account of the debtor
to which a debit entry will be
made as a result of the
transaction.
Unique and unambiguous
identification for the account
between the account owner
and the account servicer.
IBAN can be used for all
countries
Note: IBAN must be used for
SEPA payments.
Note! This field will be ignored by Nordea Bank.
Note! This block will be
ignored by Nordea Bank.
Unique and unambiguous
identification of a financial
institution, as assigned under
an internationally recognised
or proprietary identification
scheme.
Code allocated to a financial
institution
Only for Sepa
31/08/2015
12 of 26
+
+
+
+
+
+
+
+
+
+
+
+
Date
Page
pain.001.001.03
9.1.0
+++
Name
<Nm>
[0..1]
9.1.12
+++
Identification
<Id>
[0..1]
<OrgId>
[1..1]
OrganisationIdentification
9.1.13
{Or
++++
9.1.14
{{Or
+++++
BICOrBEI
<BICOrBEI>
[0..1]
9.1.15
Or}}
+++++
Other
<Othr>
[0..n]
Max70Text
Identifier
Name by which a party is
known and which is usually
used to identify that party.
Only for Sepa
+
+
Unique and unambiguous
identification of a party.
Only for Sepa
Only for Sepa
+
+
+
+
Only for Sepa
+
+
Only for Sepa
+
+
Only for Sepa
+
+
+
+
+
+
Only for Sepa
9.1.16
++++++
Identification
<Id>
[1..1]
9.1.17
++++++
SchemeName
<SchmeNm>
[0..1]
9.1.18
+++++++
<Cd>
[1..1]
<PrvtId>
[1..1]
Valid codes:
CUST = Payer‘s code
TXID = Tax payer‘s code
COID = Company code
Only for Sepa
Only for Sepa
<DtAndPlcOfBirth>
[0..1]
Only for Sepa
+
9.1.21
Or}
9.1.22
{{Or
++++
+++++
Code
PrivateIdentification
DateAndPlaceOfBirth
Text
Code
31/08/2015
13 of 26
9.1.23
++++++
BirthDate
<BirthDt>
[1..1]
DateTime
Only for Sepa
+
9.1.24
++++++
ProvinceOfBirth
<PrvcOfBirth>
[0..1]
Text
Only for Sepa
+
9.1.25
++++++
CityOfBirth
<CityOfBirth>
[1..1]
Text
Only for Sepa
+
9.1.26
++++++
CountryOfBirth
<CtryOfBirth>
[1..1]
Code
Only for Sepa
+
<Othr>
[0..n]
Only for Sepa
+
+
Only for Sepa
+
+
Only for Sepa
+
+
Identifiers according ISO
20022 code list:
NIDN – National Identity
Number,
CUST – Customer Identification Number,
DRLC – Driver’s License
Number,
SOSE – Social Security Num-
+
+
9.1.27
Or}}
+++++
Other
9.1.28
++++++
Identification
<Id>
[1..1]
9.1.29
++++++
SchemeName
<SchmeNm>
[0..1]
<Cd>
[1..1]
9.1.30
{{Or
+++++++
Code
Text
Code
Date
Page
pain.001.001.03
2.24
++
ChargeBearer
<ChrgBr>
[0..1]
ChargeBearerType1Code
ber,
CCPT – Passport Number,
EMPL – Employee Identification Number,
TXID – Tax Identification
Number,
ARNU – Alien Registration
Number.
Only for Sepa
Specifies which party/parties
will bear the charges associated with the processing of
the payment transaction.
Valid codes:
DEBT = Borne By Debtor
(OUR)
CRED = Borne By Creditor
(BEN)
SHAR = Shared (SHR)
SLEV = Following Service
Level (SHR)
Use:
For International (Crossborder/Cross-currency)
payments: DEBT, SHAR,
CRED or SLEV
2.25
++
1.1.0
+++
1.1.1
++++
1.1.11
+++
ChargesAccount
Identification
IBAN
Currency
Note: Only code SLEV must
be used for SEPA payments,
i.e. other codes will be ignored.
Charges account should be
used when charges have to
be booked to an account
different from the account
identified in debtor's account.
Note! This block will be ignored by Nordea Bank.
<ChrgsAcct>
[0..1]
<Id>
[1..1]
<IBAN>
[1..1]
Identifier
<Ccy>
[0..1]
Code
+
31/08/2015
14 of 26
+
Date
Page
pain.001.001.03
2.27
++
2.28
+++
2.29
++++
2.30
++++
2.31
+++
2.33
++++
2.34
+++++
2.39
++++
CreditTransferTransactionInformation
<CdtTrfTxInf>
[1..n]
CreditTransferTransaction
Information10
<PmtId>
[1..1]
InstructionIdentification
<InstrId>
[0..1]
PaymentIdentification1
Max35Text
EndToEndIdentification
<EndToEndId>
[1..1]
Max35Text
<PmtTpInf>
[0..1]
PaymentTypeInformation19
<SvcLvl>
[0..1]
ServiceLevel8Choice
<Cd>
[1..1]
External
ServiceLevel1Code
<CtgyPurp>
[0..1]
CategoryPurpose1Choice
PaymentIdentification
PaymentTypeInformation
ServiceLevel
Code
CategoryPurpose
Set of elements used to
provide information on the
individual transaction(s)
included in the message.
Unique identification as
assigned by an instructing
party for an instructed party
to unambiguously identify
the instruction.
Unique identification assigned by the initiating party
to unambiguously identify
the transaction. This identification is passed on, unchanged, throughout the
entire end-to-end chain.
If present transaction level
will take precedence.
Only for Sepa
Agreement under which or
rules under which the transaction should be processed.
Only for Sepa
Specifies a pre-agreed service or level of service between the parties, as published in an external service
level code list.
Valid codes:
SEPA
Only for Sepa
Specifies the high level purpose of the instruction based
on a set of pre-defined categories.
Usage: This is used by the
initiating party to provide
information concerning the
processing of the payment. It
is likely to trigger special
31/08/2015
15 of 26
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Date
Page
pain.001.001.03
2.40
+++++
2.42
+++
Code
Amount
<Cd>
[1..1]
External
CategoryPurpose1Code
<Amt>
[1..1]
AmountType3Choice
ActiveOrHistoric
CurrencyAndAmount
2.43
{Or
++++
InstructedAmount
<InstdAmt Ccy="AAA">
[1..1]
2.44
Or}
++++
EquivalentAmount
<EqvtAmt>
[1..1]
2.45
+++++
Amount
<Amt Ccy="AAA">
[1..1]
2.46
+++++
CurrencyOfTransfer
<CcyOfTrf>
[1..1]
2.47
+++
<XchgRateInf>
[0..1]
ExchangeRateInformation
Code
processing by any of the
agents involved in the payment chain.
Only for Sepa
Valid codes are:
INTC = Intra company payment
TREA = Treasury payment
SALA = Salary payment
TAXS = Tax payment
Only for Sepa
The currency code for the
credit currency must be
stated.
Amount of money to be
moved between the debtor
and creditor, before deduction of charges, expressed in
the currency as ordered by
the initiating party.
Amount of money to be
moved between the debtor
and creditor, expressed in
the currency of the debtor's
account, and the currency in
which the amount is to be
moved.
Note! This field will be ignored by Nordea Bank.
Specifies the amount to be
debited from the Debtor
account
Note! This field will be ignored by Nordea Bank.
Currency in which the
amount is to be transferred
by Nordea
Note! This field will be ignored by Nordea Bank.
Set of elements used to
provide details on the currency exchange rate and
contract.
31/08/2015
16 of 26
+
+
+
+
+
Date
Page
pain.001.001.03
31/08/2015
17 of 26
Note! This field will be ignored by Nordea Bank.
2.48
++++
2.51
+++
2.71
+++
6.1.0
++++
6.1.1
+++++
6.1.2
+++++
6.1.3
++++++
6.1.4
{Or
+++++++
ExchangeRate
ChargeBearer
IntermediaryAgent1
FinancialInstitutionIdentifi-
<XchgRate>
[0..1]
Rate
<ChrgBr>
[0..1]
ChargeBearerType1Code
<IntrmyAgt1>
[0..1]
BranchAndFin.Inst.Id4
<FinInstnId>
[1..1]
<BIC>
[0..1]
FinancialInstitutionIdentification
BICIdentifier
<ClrSysMmbId>
[0..1]
<ClrSysId>
[0..1]
<Cd>
[1..1]
Code
<MmbId>
[1..1]
Text
Text
cation
BIC
ClearingSystemMemberIdentification
ClearingSystemIdentification
Code
MemberIdentification
6.1.6
++++++
6.1.7
+++++
Name
<Nm>
[0..1]
6.1.8
+++++
PostalAddress
<PstlAdr>
[0..1]
6.1.19
++++++
Country
<Ctry>
[0..1]
Code
6.1.18
++++++
AddressLine
<AdrLine>
[0..7]
Text
2.72
+++
++++
<IntrmyAgt1Acct>
[0..1]
<Id>
[1..1]
1.1.0
IntermediaryAgent1Account
Identification
1.1.1
{Or
+++++
IBAN
<IBAN>
[1..1]
1.1.2
Or}
+++++
Other
<Othr>
[1..1]
1.1.3
++++++
Identification
<Id>
[1..1]
1.1.4
++++++
SchemeName
<SchmeNm>
[0..1]
Identifier
Text
Specifies which party/parties
will bear the charges associated with the processing of
the payment transaction.
Note! This field will be ignored by Nordea Bank.
Agent between the debtor's
agent and the creditor's
agent.
Note! This block will be ignored by Nordea Bank.
BIC or Member identification
is required
+
+
Date
Page
pain.001.001.03
1.1.5
{{Or
2.77
+++
6.1.0
++++
6.1.1
+++++
6.1.2
+++++
6.1.3
++++++
6.1.4
{Or
Code
+++++++
+++++++
CreditorAgent
FinancialInstitutionIdentifi-
<Cd>
[1..1]
Code
<CdtrAgt>
[0..1]
BranchAndFinancial
InstitutionIdentification4
<FinInstnId>
[1..1]
FinancialInstitution
Identification7
<BIC>
[0..1]
BICIdentifier
<ClrSysMmbId>
[0..1]
<ClrSysId>
[0..1]
ClearingSystemMemberIdentification2
ClearingSystem
Identification2Choice
<Cd>
[1..1]
cation
BIC
ClearingSystemMemberIdentification
ClearingSystemIdentification
Code
ExternalClearingSystem
Identification1Code
Financial institution servicing
an account for the creditor.
BIC, ClearingSystemMemberId or Name is required
Only for Internationals
31/08/2015
18 of 26
+
+
+
+
+
+
+
+
Valid codes:
AUBSB = Australian Bank
State Branch Code (BSB)
CACPA = Canadian Payments
Association Payment Routing
Number
CNAPS = Chinese CNAPS
identifier
HKNCC = Hong Kong Bank
Code
INFSC = Indian Financial
System Code
JPZGN = Japan Zengin Clearing Code
NZNCC = New Zealand National Clearing Code
RUCBC = Russian Central
Bank Identification Code
SESBA = Swedish Bankers
Association
SGIBG = IBG Sort Code in
Singapore
TWNCC = Taiwanese Financial Institution Code
USABA = United States Routing Number (Fedwire, NACHA)
USPID = CHIPS Participant
Identifier
ZANCC = South African National Clearing Code
+
Date
Page
pain.001.001.03
All codes list:
http://www.iso20022.org/ex
ternal_code_list.page
Only for Internationals
6.1.6
++++++
6.1.7
+++++
6.1.8
+++++
6.1.19
++++++
6.1.18
++++++
2.78
+++
++++
1.1.0
1.1.1
{Or
+++++
MemberIdentification
<MmbId>
[1..1]
Max35Text
Name
<Nm>
[0..1]
Max140Text
PostalAddress
<PstlAdr>
[0..1]
PostalAddress6
Country
<Ctry>
[0..1]
Code
AddressLine
<AdrLine>
[0..7]
Text
<CdtrAgtAcct>
[0..1]
CreditorAgentAccount
Identification
IBAN
<Id>
[1..1]
<IBAN>
[1..1]
Note! This field will be ignored by Nordea Bank.
Name by which a party is
known and which is usually
used to identify that party.
Only for Internationals
Only for Internationals
Valid country codes:
https://www.iso.org/obp/ui/
#search/code/
Only for Internationals
Only for Internationals
Unambiguous identification
of the account of the creditor agent at its servicing
agent to which a credit entry
will be made as a result of
the payment transaction.
Note! This field will be ignored by Nordea Bank.
Only for Internationals
Identifier
Only for Internationals
+
+
+
+
31/08/2015
19 of 26
Date
Page
pain.001.001.03
1.1.2
Or}
Other
+++++
<Othr>
[1..1]
<Id>
[1..1]
Text
Creditor
<Cdtr>
[0..1]
PartyIdentification32
+
+
+
+
Identification
Only for Internationals
1.1.3
++++++
2.79
+++
9.1.0
++++
Name
<Nm>
[0..1]
Max70Text
9.1.1
++++
PostalAddress
<PstlAdr>
[0..1]
PostalAddress6
9.1.10
+++++
Country
<Ctry>
[0..1]
CountryCode
9.1.11
+++++
AddressLine
<AdrLine>
[0..7]
Max70Text
9.1.12
++++
<Id>
[0..1]
Party6Choice
<OrgId>
[1..1]
OrganisationIdentification4
9.1.13
{Or
+++++
31/08/2015
20 of 26
Identification
OrganisationIdentification
9.1.14
{{Or
++++++
BICOrBEI
<BICOrBEI>
[0..1]
Identifier
9.1.15
Or}}
++++++
Other
<Othr>
[0..n]
GenericOrganisa-
Only for Internationals
Information that locates and
identifies a specific address,
as defined by postal services.
Valid country codes:
https://www.iso.org/obp/ui/
#search/code/
Unstructured address information can only be used for
International (crossborder/cross-currency) payments. Only 2 occurrences of
35 characters per occurrence
can be used.
Only for international payments
Unique and unambiguous
identification of a party.
Unique and unambiguous
way to identify an organisation.
Note! This field will be ignored by Nordea Bank.
+
+
+
+
+
+
+
+
+
Date
Page
pain.001.001.03
31/08/2015
21 of 26
tionIdentification1
9.1.16
+++++++
Identification
<Id>
[1..1]
Max35Text
+
+
9.1.17
+++++++
SchemeName
<SchmeNm>
[0..1]
OrganisationIdentification
SchemeName1Choice
ExternalOrganisation
Identification1Code
+
+
+
+
+
+
9.1.18
{{Or
9.1.19
9.1.21
Or}}
Or}
9.1.22
{{Or
++++++++
Code
<Cd>
[1..1]
++++++++
Proprietary
<Prtry>
[1..1]
Text
PrivateIdentification
<PrvtId>
[1..1]
PersonIdentification5
<DtAndPlcOfBirth>
[0..1]
+++++
++++++
DateAndPlaceOfBirth
Valid codes:
CUST = Payer‘s code
TXID = Tax payer‘s code
COID = Company code
Note! This field will be ignored by Nordea Bank.
Note! This block will be ignored by Nordea Bank.
9.1.23
+++++++
BirthDate
<BirthDt>
[1..1]
DateTime
9.1.24
+++++++
ProvinceOfBirth
<PrvcOfBirth>
[0..1]
Text
9.1.25
+++++++
CityOfBirth
<CityOfBirth>
[1..1]
Text
9.1.26
+++++++
CountryOfBirth
<CtryOfBirth>
[1..1]
Code
<Othr>
[0..n]
GenericPersonIdentification1
Max35Text
+
+
+
+
PersonIdentification
SchemeName1Choice
ExternalPerson
Identification1Code
+
+
+
+
9.1.27
Or}}
++++++
Other
9.1.28
+++++++
Identification
<Id>
[1..1]
9.1.29
+++++++
SchemeName
<SchmeNm>
[0..1]
9.1.30
{{Or
++++++++
Code
<Cd>
[1..1]
9.1.31
Or}}
++++++++
Proprietary
<Prtry>
[1..1]
Text
Identifiers according ISO
20022 code list:
NIDN – National Identity
Number, CUST – Customer
Identification Number,
DRLC – Driver’s License
Number, SOSE – Social Security Number, CCPT – Passport Number,
EMPL – Employee Identification Number,
TXID – Tax Identification
Number, ARNU – Alien Registration Number.
Note! This field will be ignored by Nordea Bank.
Date
Page
pain.001.001.03
2.80
+++
1.1.0
++++
CreditorAccount
Identification
<CdtrAcct>
[1..1]
<Id>
[1..1]
1.1.1
{Or
+++++
IBAN
<IBAN>
[1..1]
1.1.2
Or}
+++++
Other
<Othr>
[1..1]
CashAccount16
Identifier
31/08/2015
22 of 26
+
+
+
+
All SEPA payments must
have an IBAN number.
+
+
Only for Internationals
+
+
Only for Internationals
+
+
+
+
+
+
+
+
Unambiguous identification
of the account of the creditor to which a credit entry
will be posted as a result of
the payment transaction.
1.1.3
++++++
Identification
<Id>
[1..1]
1.1.4
++++++
SchemeName
<SchmeNm>
[0..1]
1.1.5
+++++++
<Cd>
[1..1]
Code
1.1.11
++++
<Ccy>
[0..1]
Code
2.81
+++
<UltmtCdtr>
[0..1]
PartyId32
9.1.0
++++
Name
<Nm>
[0..1]
Max70Text
9.1.12
++++
Identification
<Id>
[0..1]
Only for Internationals
Valid code:
BBAN
Note! This field will be ignored by Nordea Bank.
Ultimate party to which an
amount of money is due.
Only for Sepa
Name by which a party is
known and which is usually
used to identify that party.
Only for Sepa
Only for Sepa
<OrgId>
[1..1]
Only for Sepa
+
+
Note! This field will be ignored by Nordea Bank.
Only for Sepa
+
+
Only for Sepa
+
+
Only for Sepa
+
+
Valid codes:
CUST = Payer‘s code
TXID = Tax payer‘s code
COID = Company code
+
+
Code
Currency
UltimateCreditor
OrganisationIdentifica-
9.1.13
{Or
+++++
9.1.14
{{Or
++++++
BICOrBEI
<BICOrBEI>
[0..1]
9.1.15
Or}}
++++++
Other
<Othr>
[0..n]
tion
9.1.16
+++++++
Identification
<Id>
[1..1]
9.1.17
+++++++
SchemeName
<SchmeNm>
[0..1]
<Cd>
[1..1]
9.1.18
{{Or
++++++++
Code
Max34Text
Only for Internationals
Identifier
Max35Text
Code
Date
Page
pain.001.001.03
31/08/2015
23 of 26
Only for Sepa
9.1.19
Or}}
++++++++
9.1.21
Or}
+++++
9.1.22
{{Or
++++++
Proprietary
<Prtry>
[1..1]
PrivateIdentification
<PrvtId>
[1..1]
<DtAndPlcOfBirth>
[0..1]
Text
Only for Sepa
+
+
9.1.23
+++++++
BirthDate
<BirthDt>
[1..1]
DateTime
Can be used for all countries
Only for Sepa
Note! This block will be ignored by Nordea Bank.
Only for Sepa
9.1.24
+++++++
ProvinceOfBirth
<PrvcOfBirth>
[0..1]
Text
Only for Sepa
+
9.1.25
+++++++
CityOfBirth
<CityOfBirth>
[1..1]
Text
Only for Sepa
+
9.1.26
+++++++
CountryOfBirth
<CtryOfBirth>
[1..1]
Code
Only for Sepa
+
<Othr>
[0..n]
Only for Sepa
+
+
Only for Sepa
+
+
Only for Sepa
+
+
Identifiers according ISO
20022 code list:
NIDN – National Identity
Number,
CUST – Customer Identification Number,
DRLC – Driver’s License
Number,
SOSE – Social Security Number,
CCPT – Passport Number,
EMPL – Employee Identification Number,
TXID – Tax Identification
Number,
ARNU – Alien Registration
Number.
Only for Sepa
Note! This field will be ignored by Nordea Bank.
Note! This field will be ignored by Nordea Bank.
Only for Internationals
+
+
9.1.27
Or}}
DateAndPlaceOfBirth
Other
++++++
9.1.28
+++++++
Identification
<Id>
[1..1]
9.1.29
+++++++
SchemeName
<SchmeNm>
[0..1]
9.1.30
{{Or
9.1.31
Or}}
Max35Text
++++++++
Code
<Cd>
[1..1]
Code
++++++++
Proprietary
<Prtry>
[1..1]
Text
<InstrForCdtrAgt>
[0..n]
<Cd>
[0..1]
2.82
+++
2.83
++++
InstructionForCreditorAgent
Code
Code
+
Date
Page
pain.001.001.03
2.86
+++
2.87
++++
2.98
+++
2.99
{Or
++++
Purpose
<Purp>
[0..1]
Code
<Cd>
[1..1]
<RmtInf>
[0..1]
RemittanceInformation
Unstructured
<Ustrd>
[0..n]
Code
Max140Text
31/08/2015
24 of 26
Underlying reason for the
payment transaction.
Usage: Purpose is used by
the end-customers, that is
initiating party, (ultimate)
debtor, (ultimate) creditor to
provide information concerning the nature of the
payment. Purpose is a content element, which is not
used for processing by any of
the agents involved in the
payment chain.
Only for Sepa
Only for Sepa
+
Information supplied to
enable the matching of an
entry with the items that the
transfer is intended to settle,
such as commercial invoices
in an accounts' receivable
system.
+
+
+
+
Note: Either unstructured or
structured remittance information is allowed. Can’t be
both fields provided.
Information supplied to
enable the matching/reconciliation of an entry
with the items that the payment is intended to settle,
such as commercial invoices
in an accounts' receivable
system, in an unstructured
form.
For example: Details of payment
+
Date
Page
pain.001.001.03
2.100
Or}
Structured
++++
2.120
+++++
2.121
++++++
2.122
+++++++
mation
CreditorReferenceInfor-
Type
CodeOrProprietary
<Strd>
[0..n]
<CdtrRefInf>
[0..1]
<Tp>
[0..1]
<CdOrPrtry>
[1..1]
StructuredRemittanceInformation7
2.123
{Or
++++++++
Code
<Cd>
[1..1]
Code
2.124
Or}
++++++++
Proprietary
<Prtry>
[1..1]
Text
Information supplied to
enable the matching/ reconciliation of an entry with the
items that the payment is
intended to settle, such as
commercial invoices in an
accounts' receivable system,
in a structured form.
For example: Tax code
Reference information provided by the creditor to
allow the identification of
the underlying documents.
Specifies the type of creditor
reference.
Only for Sepa
Coded or proprietary format
creditor reference type.
Only for Sepa
Valid code:
SCOR = Structured Communication Reference
Note! This field will be ignored by Nordea Bank.
Note! This field will be ignored by Nordea Bank.
31/08/2015
25 of 26
+
+
+
+
Date
Page
pain.001.001.03
2.126
++++++
Reference
<Ref>
[0..1]
Max35Text
Unique reference, as assigned by the creditor, to
unambiguously refer to the
payment transaction.
Usage: If available, the initiating party should provide
this reference in the structured remittance information, to enable reconciliation by the creditor upon
receipt of the amount of
money. If the business context requires the use of a
creditor reference or payment remit identification,
and only one identifier can
be passed through the endto-end chain, the creditor's
reference or payment remittance identification should
be quoted in the end-to-end
transaction identification.
+
31/08/2015
26 of 26
+