HSBC
HSBC
HSBC_pain.001.001.03_LowValuePayment_-
United Arab Emirates
HSBC_pain.001.001.03_LowValuePayment_MiddleEast
This document describes a usage guideline restricting the base message MX pain.001.001.03. You can also consult this
information online.
16 February 2022
Usage Guideline
Table of Contents
2 Structure ................................................................................................................................................................. 5
Message Functionality
Overview
The UAEFTS Bulk Transfers module allows the electronic exchange of bulk payment
file instructions between banks, including salaries, supplier payments and bonus-
es. It also enables payments to be made without the need to raise physical support-
ing vouchers or documents such as cheques, bank drafts, etc. It is an interbank funds
transfer system that facilitates payments and collections via the exchange of bulk
payment transactions between banks.
Whilst the local bank clearing codes are used for ACH payments (where service level
code NURG is used), HSBC currently maintains a table of CBIDs (Clearing Bank Identi-
fication Codes) which are aligned to the local bank clearing codes. Each commercial
bank is identified in the HSBC back office system with a unique 8 characters.
Outline
The HSBC_pain.001.001.03_LowValuePayment_MiddleEast / HSBC_pain.001.001.03_LowValuePay-
ment_United Arab Emirates message is composed of 2 building blocks
a. GroupHeader
Set of characteristics shared by all individual transactions included in the message.
b. PaymentInformation
Set of characteristics that applies to the debit side of the payment transactions included in the cred-
it transfer initiation.
16 February 2022 3
Usage Guideline
1 Restriction summary
This Usage Guideline restricts the pain.001.001.03 message.
Removed elements 9, 11, 12, 36, 36, 37, 37, 38, 111,
111, 135, 167
Make mandatory 38, 39, 40, 42, 54, 56, 57, 73, 74,
77, 78, 80, 93, 99, 99, 99, 99, 105,
112
Truncates n.a.
Comments 10, 43, 54, 58, 73, 80, 81, 85, 87,
109, 113
Annotations n.a.
Extensions n.a.
Synonyms n.a.
2 Structure
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 5
Usage Guideline
3.1 GroupHeader
XML Tag: GrpHdr
Presence: [1..1]
Definition: Set of characteristics shared by all individual transactions included in the message.
The GrpHdr block contains the following elements (see datatype "GroupHeader32" on page 64 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
3.2 PaymentInformation
XML Tag: PmtInf
Presence: [1..*]
Definition: Set of characteristics that applies to the debit side of the payment transactions included in
the credit transfer initiation.
The PmtInf block contains the following elements (see datatype "PaymentInstructionInformation3__1"
on page 81 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 7
Usage Guideline
4 Message Components
Note The following chapter identifies the message components.
4.1 AccountIdentification4Choice
Definition: Specifies the unique identification of an account as assigned by the account servicer.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all AccountIdentification4Choice blocks have this element removed and/or ig-
nored. Please refer to the page number next to the element for further details on which elements have
been removed and/or ignored.
.
Used in element(s)
"Identification" on page 17
4.1.1 IBAN
XML Tag: IBAN
Presence: [1..1]
Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institu-
tions to uniquely identify the account of a customer. Further specifications of the format and content of
the IBAN can be found in the standard ISO 13616 "Banking and related financial services - International
Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Datatype: "IBAN2007Identifier" on page 159
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Identification/IBAN) will be ignored by the Receiver.
4.1.2 Other
XML Tag: Othr
Presence: [1..1]
Definition: Unique identification of an account, as assigned by the account servicer, using an identifica-
tion scheme.
The Othr block contains the following elements (see datatype "GenericAccountIdentification1" on
page 58 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Othr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAccount/Identification/Other) is removed.
4.2 AccountSchemeName1Choice
Definition: Sets of elements to identify a name of the identification scheme.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"SchemeName" on page 59
4.2.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: "ExternalAccountIdentification1Code" on page 152
4.2.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
16 February 2022 9
Usage Guideline
4.3 AmountType3Choice__1
Definition: Specifies the amount of money to be moved between the debtor and creditor, before deduc-
tion of charges, expressed in the currency as ordered by the initiating party.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Amount" on page 33
4.3.1 InstructedAmount
XML Tag: InstdAmt
Presence: [1..1]
Definition: 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.
Datatype: "ActiveOrHistoricCurrencyAndAmount_11_characters" on page 131
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Amount/In-
structedAmount
Type changed to: ActiveOrHistoricCurrencyAndAmount_11_characters on page 130
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Amount/In-
structedAmount
Comment:
Only AED currency is allowed
4.3.2 EquivalentAmount
XML Tag: EqvtAmt
Presence: [1..1]
Definition: 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.
The EqvtAmt block contains the following elements (see datatype "EquivalentAmount2" on page 49
for details)
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Amount/EquivalentAmount) is removed.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Amount/EquivalentAmount) will be ignored by the Receiver.
4.4 Authorisation1Choice
Definition: Provides the details on the user identification or any user key that allows to check if the initi-
ating party is allowed to issue the transaction.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Authorisation" on page 64
4.4.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Specifies the authorisation, in a coded form.
Datatype: "Authorisation1Code" on page 134
4.4.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Specifies the authorisation, in a free text form.
Datatype: "Max128Text" on page 161
16 February 2022 11
Usage Guideline
4.5 BranchAndFinancialInstitutionIdentification4
Definition: Set of elements used to uniquely and unambiguously identify a financial institution or a
branch of a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ChargesAccountAgent" on page 90, "DebtorAgent" on page 88, "ForwardingAgent" on
page 66, "IntermediaryAgent1" on page 35, "IntermediaryAgent2" on page 36, "IntermediaryA-
gent3" on page 37
4.5.1 FinancialInstitutionIdentification
XML Tag: FinInstnId
Presence: [1..1]
Definition: Unique and unambiguous identification of a financial institution, as assigned under an inter-
nationally recognised or proprietary identification scheme.
The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentification7"
on page 52 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all FinInstnId blocks have this element removed and/or ignored. Please refer to
the page number next to the element for further details on which elements have been removed and/or
ignored.
.
4.5.2 BranchIdentification
XML Tag: BrnchId
Presence: [0..1]
Definition: Identifies a specific branch of a financial institution.
Usage: This component should be used in case the identification information in the financial institution
component does not provide identification up to branch level.
The BrnchId block contains the following elements (see datatype "BranchData2" on page 15 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all BrnchId blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent1/BranchIdentification) will be ignored by the Receiver.
4.6 BranchAndFinancialInstitutionIdentification4__1
Definition: Set of elements used to uniquely and unambiguously identify a financial institution or a
branch of a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"CreditorAgent" on page 38
4.6.1 FinancialInstitutionIdentification
16 February 2022 13
Usage Guideline
, >> Note as not all FinInstnId blocks have this element removed and/or ignored. Please refer to
the page number next to the element for further details on which elements have been removed and/or
ignored.
.
4.6.2 BranchIdentification
XML Tag: BrnchId
Presence: [0..1]
Definition: Identifies a specific branch of a financial institution.
Usage: This component should be used in case the identification information in the financial institution
component does not provide identification up to branch level.
The BrnchId block contains the following elements (see datatype "BranchData2" on page 15 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all BrnchId blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
4.7 BranchData2
Definition: Information that locates and identifies a specific branch of a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all BranchData2 blocks have this element removed and/or ignored. Please refer
to the page number next to the element for further details on which elements have been removed and/
or ignored.
.
Used in element(s)
"BranchIdentification" on page 13, "BranchIdentification" on page 14
4.7.1 Identification
XML Tag: Id
Presence: [0..1]
Definition: Unique and unambiguous identification of a branch of a financial institution.
Datatype: "Max35Text" on page 164
4.7.2 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which an agent is known and which is usually used to identify that agent.
Datatype: "Max140Text" on page 162
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgent/BranchIdentification/Name) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAgent/BranchIdentification/Name)
will be ignored by the Receiver.
4.7.3 PostalAddress
XML Tag: PstlAdr
Presence: [0..1]
16 February 2022 15
Usage Guideline
Definition: Information that locates and identifies a specific address, as defined by postal services.
The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 96 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgent/BranchIdentification/PostalAddress) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAgent/BranchIdentification/Postal-
Address) will be ignored by the Receiver.
4.8 CashAccount16
Definition: Set of elements used to identify an account.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ChargesAccount" on page 90, "CreditorAccount" on page 39, "CreditorAgentAccount" on
page 39, "DebtorAccount" on page 87, "DebtorAgentAccount" on page 88, "IntermediaryAgen-
t1Account" on page 35, "IntermediaryAgent2Account" on page 36, "IntermediaryAgent3Account"
on page 38
4.8.1 Identification
XML Tag: Id
Presence: [1..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
The Id block contains the following elements (see datatype "AccountIdentification4Choice" on
page 8 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Id blocks have this element removed and/or ignored. Please refer to the page
number next to the element for further details on which elements have been removed and/or ignored.
.
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorAc-
count/Identification
16 February 2022 17
Usage Guideline
– HSBC_Identification:
4.8.2 Type
XML Tag: Tp
Presence: [0..1]
Definition: Specifies the nature, or use of the account.
The Tp block contains the following elements (see datatype "CashAccountType2" on page 19 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Tp blocks have this element removed and/or ignored. Please refer to the page
number next to the element for further details on which elements have been removed and/or ignored.
.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Type) will be ignored by the Receiver.
4.8.3 Currency
XML Tag: Ccy
Presence: [0..1]
Definition: Identification of the currency in which the account is held.
Usage: Currency should only be used in case one and the same account number covers several cur-
rencies
and the initiating party needs to identify which currency needs to be used for settlement on the account.
Datatype: "ActiveOrHistoricCurrencyCode" on page 132
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAccount/Currency) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Currency) will be ignored by the Receiver.
4.8.4 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.
Usage: The account name is different from the account owner name. The account name is used in cer-
tain user communities to provide a means of identifying the account, in addition to the account owner's
identity and the account number.
Datatype: "Max70Text" on page 165
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Name) will be ignored by the Receiver.
4.9 CashAccountType2
Definition: Nature or use of the account.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all CashAccountType2 blocks have this element removed and/or ignored.
Please refer to the page number next to the element for further details on which elements have been re-
moved and/or ignored.
.
Used in element(s)
"Type" on page 18
4.9.1 Code
XML Tag: Cd
Presence: [1..1]
16 February 2022 19
Usage Guideline
4.9.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAccount/Type/xor/Proprietary) will be ignored by the Receiver.
4.10 CategoryPurpose1Choice
Definition: 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 pay-
ment. It is likely to trigger special processing by any of the agents involved in the payment chain.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"CategoryPurpose" on page 94
4.10.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: "ExternalCategoryPurpose1Code" on page 152
4.10.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: "Max35Text" on page 164
4.11 Cheque6
Definition: Set of characteristics related to a cheque instruction, such as cheque type or cheque num-
ber.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Rules
R8 ChequeMaturityDateRule ✓
If ChequeMaturityDate is present, then ChequeType must be present and equal to DRFT or EL-
DR.
Error handling:
Used in element(s)
"ChequeInstruction" on page 34
16 February 2022 21
Usage Guideline
4.11.1 ChequeType
XML Tag: ChqTp
Presence: [0..1]
Definition: Specifies the type of cheque to be issued.
Datatype: "ChequeType2Code" on page 145
4.11.2 ChequeNumber
XML Tag: ChqNb
Presence: [0..1]
Definition: Unique and unambiguous identifier for a cheque as assigned by the agent.
Datatype: "Max35Text" on page 164
4.11.3 ChequeFrom
XML Tag: ChqFr
Presence: [0..1]
Definition: Identifies the party that ordered the issuance of the cheque.
The ChqFr block contains the following elements (see datatype "NameAndAddress10" on page 68
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.11.4 DeliveryMethod
XML Tag: DlvryMtd
Presence: [0..1]
Definition: Specifies the delivery method of the cheque by the debtor's agent.
The DlvryMtd block contains the following elements (see datatype "ChequeDeliveryMethod1Choice" on
page 24 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.11.5 DeliverTo
XML Tag: DlvrTo
Presence: [0..1]
Definition: Party to whom the debtor's agent needs to send the cheque.
The DlvrTo block contains the following elements (see datatype "NameAndAddress10" on page 68
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.11.6 InstructionPriority
XML Tag: InstrPrty
Presence: [0..1]
Definition: Urgency or order of importance that the originator would like the recipient of the payment in-
struction to apply to the processing of the payment instruction.
Datatype: "Priority2Code" on page 168
4.11.7 ChequeMaturityDate
XML Tag: ChqMtrtyDt
Presence: [0..1]
Definition: Date when the draft becomes payable and the debtor's account is debited.
Datatype: "ISODate" on page 159
4.11.8 FormsCode
XML Tag: FrmsCd
Presence: [0..1]
Definition: Identifies, in a coded form, the cheque layout, company logo and digitised signature to be
used to print the cheque, as agreed between the initiating party and the debtor's agent.
Datatype: "Max35Text" on page 164
16 February 2022 23
Usage Guideline
4.11.9 MemoField
XML Tag: MemoFld
Presence: [0..2]
Definition: Information that needs to be printed on a cheque, used by the payer to add miscellaneous in-
formation.
Datatype: "Max35Text" on page 164
4.11.10 RegionalClearingZone
XML Tag: RgnlClrZone
Presence: [0..1]
Definition: Regional area in which the cheque can be cleared, when a country has no nation-wide
cheque clearing organisation.
Datatype: "Max35Text" on page 164
4.11.11 PrintLocation
XML Tag: PrtLctn
Presence: [0..1]
Definition: Specifies the print location of the cheque.
Datatype: "Max35Text" on page 164
4.12 ChequeDeliveryMethod1Choice
Definition: Set of characteristics related to a cheque instruction, such as cheque type or cheque num-
ber.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"DeliveryMethod" on page 22
4.12.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Specifies the delivery method of the cheque by the debtor's agent.
Datatype: "ChequeDelivery1Code" on page 143
4.12.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Specifies a proprietary delivery method of the cheque by the debtor's agent.
Datatype: "Max35Text" on page 164
4.13 ClearingSystemIdentification2Choice
Definition: Choice of a clearing system identifier.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ClearingSystemIdentification" on page 26, "ClearingSystemIdentification" on page 27
4.13.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Identification of a clearing system, in a coded form as published in an external list.
Datatype: "ExternalClearingSystemIdentification1Code" on page 153
4.13.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Identification code for a clearing system, that has not yet been identified in the list of clearing
systems.
Datatype: "Max35Text" on page 164
4.14 ClearingSystemMemberIdentification2
Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a member
of the clearing system.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 25
Usage Guideline
, >> Note as not all ClearingSystemMemberIdentification2 blocks have this element removed
and/or ignored. Please refer to the page number next to the element for further details on which ele-
ments have been removed and/or ignored.
.
Used in element(s)
"ClearingSystemMemberIdentification" on page 52
4.14.1 ClearingSystemIdentification
XML Tag: ClrSysId
Presence: [0..1]
Definition: Specification of a pre-agreed offering between clearing agents or the channel through which
the payment instruction is processed.
The ClrSysId block contains the following elements (see datatype "ClearingSystemIdentifica-
tion2Choice" on page 25 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/IntermediaryAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-
tion/ClearingSystemIdentification) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAgent/FinancialInstitutionIdentifica-
tion/ClearingSystemMemberIdentification/ClearingSystemIdentification) will be ignored by the
Receiver.
4.14.2 MemberIdentification
XML Tag: MmbId
Presence: [1..1]
Definition: Identification of a member of a clearing system.
Datatype: "Max35Text" on page 164
4.15 ClearingSystemMemberIdentification2__1
Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a member
of the clearing system.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all ClearingSystemMemberIdentification2__1 blocks have this element re-
moved and/or ignored. Please refer to the page number next to the element for further details on which
elements have been removed and/or ignored.
.
Used in element(s)
"ClearingSystemMemberIdentification" on page 56
4.15.1 ClearingSystemIdentification
XML Tag: ClrSysId
Presence: [0..1]
Definition: Specification of a pre-agreed offering between clearing agents or the channel through which
the payment instruction is processed.
The ClrSysId block contains the following elements (see datatype "ClearingSystemIdentifica-
tion2Choice" on page 25 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-
tion/ClearingSystemIdentification) will be ignored by the Receiver.
4.15.2 MemberIdentification
XML Tag: MmbId
Presence: [1..1]
16 February 2022 27
Usage Guideline
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/MemberIdentifica-
tion
Type changed to: Max9NumericText on page 165
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/MemberIdentifica-
tion
– HSBC_MemberIdentification:
4.16 ContactDetails2
Definition: Communication device number or electronic address used for communication.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ContactDetails" on page 75, "ContactDetails" on page 79
4.16.1 NamePrefix
XML Tag: NmPrfx
Presence: [0..1]
Definition: Specifies the terms used to formally address a person.
Datatype: "NamePrefix1Code" on page 165
4.16.2 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which a party is known and which is usually used to identify that party.
Datatype: "Max140Text" on page 162
4.16.3 PhoneNumber
XML Tag: PhneNb
Presence: [0..1]
Definition: Collection of information that identifies a phone number, as defined by telecom services.
Datatype: "PhoneNumber" on page 168
4.16.4 MobileNumber
XML Tag: MobNb
Presence: [0..1]
Definition: Collection of information that identifies a mobile phone number, as defined by telecom ser-
vices.
Datatype: "PhoneNumber" on page 168
4.16.5 FaxNumber
XML Tag: FaxNb
Presence: [0..1]
Definition: Collection of information that identifies a FAX number, as defined by telecom services.
Datatype: "PhoneNumber" on page 168
4.16.6 EmailAddress
XML Tag: EmailAdr
Presence: [0..1]
Definition: Address for electronic mail (e-mail).
Datatype: "Max2048Text" on page 163
4.16.7 Other
XML Tag: Othr
Presence: [0..1]
Definition: Contact details in another form.
Datatype: "Max35Text" on page 164
4.17 CreditTransferTransactionInformation10__1
16 February 2022 29
Usage Guideline
Definition: Set of elements used to provide information specific to the individual transaction(s) included
in the message.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Rules
R20 IntermediaryAgent2Rule ✓
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.
Error handling:
R21 IntermediaryAgent3Rule ✓
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.
Error handling:
R22 InstructionForCreditorAgentRule ✓
If InstructionForCreditorAgent/Code contains CHQB, then CreditorAccount is not allowed.
Error handling:
– Error Text: Invalid message content for instruction for creditor agent PayCreditorByCheque
R23 IntermediaryAgent1AccountRule ✓
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.
Error handling:
R24 IntermediaryAgent2AccountRule ✓
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be present.
Error handling:
R25 IntermediaryAgent3AccountRule ✓
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be present.
Error handling:
16 February 2022 31
Usage Guideline
Guidelines
1. UltimateCreditorGuideline
UltimateCreditor may only be present if different from Creditor.
2. UltimateDebtorGuideline
UltimateDebtor may only be present if different from Debtor.
Used in element(s)
"CreditTransferTransactionInformation" on page 91
4.17.1 PaymentIdentification
XML Tag: PmtId
Presence: [1..1]
Definition: Set of elements used to reference a payment instruction.
The PmtId block contains the following elements (see datatype "PaymentIdentification1__1" on
page 80 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.2 PaymentTypeInformation
XML Tag: PmtTpInf
Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.
The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation19" on
page 92 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.3 Amount
XML Tag: Amt
Presence: [1..1]
Definition: 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.
The Amt block contains the following elements (see datatype "AmountType3Choice__1" on page 10
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Amt blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
4.17.4 ExchangeRateInformation
XML Tag: XchgRateInf
Presence: [0..1]
Definition: Set of elements used to provide details on the currency exchange rate and contract.
The XchgRateInf block contains the following elements (see datatype "ExchangeRateInformation1" on
page 50 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 33
Usage Guideline
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ex-
changeRateInformation) will be ignored by the Receiver.
4.17.5 ChargeBearer
XML Tag: ChrgBr
Presence: [0..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the pay-
ment transaction.
Datatype: "ChargeBearerType1Code" on page 142
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/ChargeBearer) will be ignored by the Receiver.
4.17.6 ChequeInstruction
XML Tag: ChqInstr
Presence: [0..1]
Definition: Set of elements needed to issue a cheque.
The ChqInstr block contains the following elements (see datatype "Cheque6" on page 21 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/ChequeInstruction) will be ignored by the Receiver.
4.17.7 UltimateDebtor
XML Tag: UltmtDbtr
Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
The UltmtDbtr block contains the following elements (see datatype "PartyIdentification32" on
page 72 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.8 IntermediaryAgent1
XML Tag: IntrmyAgt1
Presence: [0..1]
Definition: Agent between the debtor's agent and the creditor's agent.
Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent be-
tween the DebtorAgent and the IntermediaryAgent2.
The IntrmyAgt1 block contains the following elements (see datatype "BranchAndFinancialInstitutionI-
dentification4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.9 IntermediaryAgent1Account
XML Tag: IntrmyAgt1Acct
16 February 2022 35
Usage Guideline
Presence: [0..1]
Definition: Unambiguous identification of the account of the intermediary agent 1 at its servicing agent in
the payment chain.
The IntrmyAgt1Acct block contains the following elements (see datatype "CashAccount16" on
page 17 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent1Account) is removed.
4.17.10 IntermediaryAgent2
XML Tag: IntrmyAgt2
Presence: [0..1]
Definition: Agent between the debtor's agent and the creditor's agent.
Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent
between the IntermediaryAgent1 and the IntermediaryAgent3.
The IntrmyAgt2 block contains the following elements (see datatype "BranchAndFinancialInstitutionI-
dentification4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent2) is removed.
4.17.11 IntermediaryAgent2Account
36 HSBC_pain.001.001.03_LowValuePayment_United Arab Emirates - HSBC_pain.001.001.03_LowValuePaymen-
t_MiddleEast
Message Components
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent2Account) is removed.
4.17.12 IntermediaryAgent3
XML Tag: IntrmyAgt3
Presence: [0..1]
Definition: Agent between the debtor's agent and the creditor's agent.
Usage: If IntermediaryAgent3 is present, then it identifies the agent between the IntermediaryAgent 2
and the CreditorAgent.
The IntrmyAgt3 block contains the following elements (see datatype "BranchAndFinancialInstitutionI-
dentification4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent3) is removed.
16 February 2022 37
Usage Guideline
4.17.13 IntermediaryAgent3Account
XML Tag: IntrmyAgt3Acct
Presence: [0..1]
Definition: Unambiguous identification of the account of the intermediary agent 3 at its servicing agent in
the payment chain.
The IntrmyAgt3Acct block contains the following elements (see datatype "CashAccount16" on
page 17 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent3Account) is removed.
4.17.14 CreditorAgent
XML Tag: CdtrAgt
Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
The CdtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-
fication4__1" on page 13 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorAgent
This element is now mandatory, the minimum occurrence has been changed to : 1
4.17.15 CreditorAgentAccount
XML Tag: CdtrAgtAcct
Presence: [0..1]
Definition: 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.
The CdtrAgtAcct block contains the following elements (see datatype "CashAccount16" on page 17
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.16 Creditor
XML Tag: Cdtr
Presence: [0..1]
Definition: Party to which an amount of money is due.
The Cdtr block contains the following elements (see datatype "PartyIdentification32__1" on page 76
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor
This element is now mandatory, the minimum occurrence has been changed to : 1
4.17.17 CreditorAccount
16 February 2022 39
Usage Guideline
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorAc-
count
This element is now mandatory, the minimum occurrence has been changed to : 1
4.17.18 UltimateCreditor
XML Tag: UltmtCdtr
Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
The UltmtCdtr block contains the following elements (see datatype "PartyIdentification32" on
page 72 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ulti-
mateCreditor) will be ignored by the Receiver.
4.17.19 InstructionForCreditorAgent
XML Tag: InstrForCdtrAgt
Presence: [0..*]
Definition: Further information related to the processing of the payment instruction, provided by the initi-
ating party, and intended for the creditor agent.
The InstrForCdtrAgt block contains the following elements (see datatype "InstructionForCreditorA-
gent1" on page 66 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
structionForCreditorAgent) will be ignored by the Receiver.
4.17.20 InstructionForDebtorAgent
XML Tag: InstrForDbtrAgt
Presence: [0..1]
Definition: Further information related to the processing of the payment instruction, that may need to be
acted upon by the debtor agent, depending on agreement between debtor and the debtor agent.
Datatype: "Max140Text" on page 162
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
structionForDebtorAgent) will be ignored by the Receiver.
4.17.21 Purpose
XML Tag: Purp
Presence: [0..1]
Definition: Underlying reason for the payment transaction.
16 February 2022 41
Usage Guideline
Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) credi-
tor 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.
The Purp block contains the following elements (see datatype "Purpose2Choice" on page 100 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.17.22 RegulatoryReporting
XML Tag: RgltryRptg
Presence: [0..10]
Definition: Information needed due to regulatory and statutory requirements.
The RgltryRptg block contains the following elements (see datatype "RegulatoryReporting3__1" on
page 104 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RegulatoryRe-
porting
This element is now mandatory, the minimum occurrence has been changed to : 1
4.17.23 Tax
XML Tag: Tax
Presence: [0..1]
Definition: Set of elements used to provide details on the tax.
The Tax block contains the following elements (see datatype "TaxInformation3" on page 118 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax)
will be ignored by the Receiver.
4.17.24 RelatedRemittanceInformation
XML Tag: RltdRmtInf
Presence: [0..10]
Definition: Set of elements used to provide information related to the handling of the remittance informa-
tion by any of the agents in the transaction processing chain.
The RltdRmtInf block contains the following elements (see datatype "RemittanceLocation2" on
page 108 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RelatedRemit-
tanceInformation
Comment:
16 February 2022 43
Usage Guideline
4.17.25 RemittanceInformation
XML Tag: RmtInf
Presence: [0..1]
Definition: Information supplied to enable the matching of an entry with the items that the transfer is in-
tended to settle, such as commercial invoices in an accounts' receivable system.
The RmtInf block contains the following elements (see datatype "RemittanceInformation5" on
page 107 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.18 CreditorReferenceInformation2
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"CreditorReferenceInformation" on page 114
4.18.1 Type
XML Tag: Tp
Presence: [0..1]
Definition: Specifies the type of creditor reference.
The Tp block contains the following elements (see datatype "CreditorReferenceType2" on page 46
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.18.2 Reference
XML Tag: Ref
Presence: [0..1]
Definition: Unique reference, as assigned by the creditor, to unambiguously refer to the payment trans-
action.
Usage: If available, the initiating party should provide this reference in the structured remittance infor-
mation, 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 a payment remit identification, and on-
ly one identifier can be passed through the end-to-end chain, the creditor's reference or payment remit-
tance identification should be quoted in the end-to-end transaction identification.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/CreditorReferenceInformation/Reference) will be ignored by
the Receiver.
4.19 CreditorReferenceType1Choice
Definition: Specifies the type of document referred by the creditor.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"CodeOrProprietary" on page 46
4.19.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Type of creditor reference, in a coded form.
16 February 2022 45
Usage Guideline
4.19.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Creditor reference type, in a proprietary form.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/CreditorReferenceInformation/Type/CodeOrProprietary/Pro-
prietary) will be ignored by the Receiver.
4.20 CreditorReferenceType2
Definition: Specifies the type of creditor reference.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Type" on page 44
4.20.1 CodeOrProprietary
XML Tag: CdOrPrtry
Presence: [1..1]
Definition: Coded or proprietary format creditor reference type.
The CdOrPrtry block contains the following elements (see datatype "CreditorReferenceType1Choice"
on page 45 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.20.2 Issuer
46 HSBC_pain.001.001.03_LowValuePayment_United Arab Emirates - HSBC_pain.001.001.03_LowValuePaymen-
t_MiddleEast
Message Components
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/CreditorReferenceInformation/Type/Issuer) will be ignored by
the Receiver.
4.21 DateAndPlaceOfBirth
Definition: Date and place of birth of a person.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"DateAndPlaceOfBirth" on page 94
4.21.1 BirthDate
XML Tag: BirthDt
Presence: [1..1]
Definition: Date on which a person is born.
Datatype: "ISODate" on page 159
4.21.2 ProvinceOfBirth
XML Tag: PrvcOfBirth
Presence: [0..1]
Definition: Province where a person was born.
Datatype: "Max35Text" on page 164
4.21.3 CityOfBirth
XML Tag: CityOfBirth
16 February 2022 47
Usage Guideline
Presence: [1..1]
Definition: City where a person was born.
Datatype: "Max35Text" on page 164
4.21.4 CountryOfBirth
XML Tag: CtryOfBirth
Presence: [1..1]
Definition: Country where a person was born.
Datatype: "CountryCode" on page 147
4.22 DatePeriodDetails
Definition: Range of time defined by a start date and an end date.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"FromToDate" on page 125
4.22.1 FromDate
XML Tag: FrDt
Presence: [1..1]
Definition: Start date of the range.
Datatype: "ISODate" on page 159
4.22.2 ToDate
XML Tag: ToDt
Presence: [1..1]
Definition: End date of the range.
Datatype: "ISODate" on page 159
4.23 DocumentAdjustment1
Definition: Set of elements used to provide information on the amount and reason of the document ad-
justment.
Used in element(s)
"AdjustmentAmountAndReason" on page 107
4.23.1 Amount
XML Tag: Amt
Presence: [1..1]
Definition: Amount of money of the document adjustment.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.23.2 CreditDebitIndicator
XML Tag: CdtDbtInd
Presence: [0..1]
Definition: Specifies whether the adjustment must be subtracted or added to the total amount.
Datatype: "CreditDebitCode" on page 147
4.23.3 Reason
XML Tag: Rsn
Presence: [0..1]
Definition: Specifies the reason for the adjustment.
Datatype: "Max4Text" on page 164
4.23.4 AdditionalInformation
XML Tag: AddtlInf
Presence: [0..1]
Definition: Provides further details on the document adjustment.
Datatype: "Max140Text" on page 162
4.24 EquivalentAmount2
16 February 2022 49
Usage Guideline
Definition: 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.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"EquivalentAmount" on page 10
4.24.1 Amount
XML Tag: Amt
Presence: [1..1]
Definition: Amount of money to be moved between debtor and creditor, before deduction of charges,
expressed in the currency of the debtor's account, and to be moved in a different currency.
Usage: The first agent will convert the equivalent amount into the amount to be moved.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.24.2 CurrencyOfTransfer
XML Tag: CcyOfTrf
Presence: [1..1]
Definition: Specifies the currency of the to be transferred amount, which is different from the currency of
the debtor's account.
Datatype: "ActiveOrHistoricCurrencyCode" on page 132
4.25 ExchangeRateInformation1
Definition: Further detailed information on the exchange rate that has been used in the payment trans-
action.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ExchangeRateInformation" on page 33
4.25.1 ExchangeRate
XML Tag: XchgRate
Presence: [0..1]
Definition: The factor used for conversion of an amount from one currency to another. This reflects the
price at which one currency was bought with another currency.
Datatype: "BaseOneRate" on page 136
4.25.2 RateType
XML Tag: RateTp
Presence: [0..1]
Definition: Specifies the type used to complete the currency exchange.
Datatype: "ExchangeRateType1Code" on page 151
4.25.3 ContractIdentification
XML Tag: CtrctId
Presence: [0..1]
Definition: Unique and unambiguous reference to the foreign exchange contract agreed between the ini-
tiating party/creditor and the debtor agent.
Datatype: "Max35Text" on page 164
4.26 FinancialIdentificationSchemeName1Choice
Definition: Sets of elements to identify a name of the organisation identification scheme.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"SchemeName" on page 60
4.26.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
16 February 2022 51
Usage Guideline
4.26.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 164
4.27 FinancialInstitutionIdentification7
Definition: Set of elements used to identify a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all FinancialInstitutionIdentification7 blocks have this element removed and/or
ignored. Please refer to the page number next to the element for further details on which elements have
been removed and/or ignored.
.
Used in element(s)
"FinancialInstitutionIdentification" on page 12
4.27.1 BIC
XML Tag: BIC
Presence: [0..1]
Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as described
in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
Datatype: "BICIdentifier" on page 136
4.27.2 ClearingSystemMemberIdentification
XML Tag: ClrSysMmbId
Presence: [0..1]
Definition: Information used to identify a member within a clearing system.
The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-
fication2" on page 25 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all ClrSysMmbId blocks have this element removed and/or ignored. Please refer
to the page number next to the element for further details on which elements have been removed and/
or ignored.
.
4.27.3 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which an agent is known and which is usually used to identify that agent.
Datatype: "Max140Text" on page 162
4.27.4 PostalAddress
XML Tag: PstlAdr
Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.
The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 96 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 53
Usage Guideline
, >> Note as not all PstlAdr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• on pain.001.001.03/PaymentInformation/DebtorAgent/FinancialInstitutionIdentification/Postal-
Address
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/IntermediaryA-
gent1/FinancialInstitutionIdentification/PostalAddress
Comment:
Structured Address recommended
4.27.5 Other
XML Tag: Othr
Presence: [0..1]
Definition: Unique identification of an agent, as assigned by an institution, using an identification
scheme.
The Othr block contains the following elements (see datatype "GenericFinancialIdentification1" on
page 60 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent1/FinancialInstitutionIdentification/Other) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAgent/FinancialInstitutionIdentifica-
tion/Other) will be ignored by the Receiver.
4.28 FinancialInstitutionIdentification7__1
Definition: Set of elements used to identify a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all FinancialInstitutionIdentification7__1 blocks have this element removed
and/or ignored. Please refer to the page number next to the element for further details on which ele-
ments have been removed and/or ignored.
.
Used in element(s)
"FinancialInstitutionIdentification" on page 13
4.28.1 BIC
XML Tag: BIC
Presence: [0..1]
16 February 2022 55
Usage Guideline
Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as described
in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
Datatype: "BICIdentifier" on page 136
4.28.2 ClearingSystemMemberIdentification
XML Tag: ClrSysMmbId
Presence: [0..1]
Definition: Information used to identify a member within a clearing system.
The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-
fication2__1" on page 27 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all ClrSysMmbId blocks have this element removed and/or ignored. Please refer
to the page number next to the element for further details on which elements have been removed and/
or ignored.
.
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification
This element is now mandatory, the minimum occurrence has been changed to : 1
4.28.3 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which an agent is known and which is usually used to identify that agent.
Datatype: "Max140Text" on page 162
4.28.4 PostalAddress
XML Tag: PstlAdr
Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.
The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 96 for
details)
, >> Note as not all PstlAdr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/PostalAddress
16 February 2022 57
Usage Guideline
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/PostalAddress
Comment: (empty)
4.28.5 Other
XML Tag: Othr
Presence: [0..1]
Definition: Unique identification of an agent, as assigned by an institution, using an identification
scheme.
The Othr block contains the following elements (see datatype "GenericFinancialIdentification1" on
page 60 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgent/FinancialInstitutionIdentification/Other) will be ignored by the Receiver.
4.29 GenericAccountIdentification1
Definition: Information related to a generic account identification.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all GenericAccountIdentification1 blocks have this element removed and/or ig-
nored. Please refer to the page number next to the element for further details on which elements have
been removed and/or ignored.
.
Used in element(s)
"Other" on page 8
4.29.1 Identification
XML Tag: Id
Presence: [1..1]
Definition: Identification assigned by an institution.
Datatype: "Max34Text" on page 163
• on pain.001.001.03/PaymentInformation/DebtorAccount/Identification/Other/Identification
– HSBC_Identification:
4.29.2 SchemeName
XML Tag: SchmeNm
Presence: [0..1]
Definition: Name of the identification scheme.
The SchmeNm block contains the following elements (see datatype "AccountSchemeName1Choice"
on page 9 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAccount/Identification/Other/SchemeName) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Identification/Other/SchemeName) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAccount/Identification/Oth-
er/SchemeName) will be ignored by the Receiver.
4.29.3 Issuer
XML Tag: Issr
16 February 2022 59
Usage Guideline
Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAccount/Identification/Other/Issuer) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgentAccount/Identification/Other/Issuer) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/DebtorAccount/Identification/Other/Issuer)
will be ignored by the Receiver.
4.30 GenericFinancialIdentification1
Definition: Information related to an identification of a financial institution.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Other" on page 54, "Other" on page 58
4.30.1 Identification
XML Tag: Id
Presence: [1..1]
Definition: Unique and unambiguous identification of a person.
Datatype: "Max35Text" on page 164
4.30.2 SchemeName
XML Tag: SchmeNm
Presence: [0..1]
Definition: Name of the identification scheme.
The SchmeNm block contains the following elements (see datatype "FinancialIdentificationScheme-
Name1Choice" on page 51 for details)
4.30.3 Issuer
XML Tag: Issr
Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 164
4.31 GenericOrganisationIdentification1
Definition: Information related to an identification of an organisation.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all GenericOrganisationIdentification1 blocks have this element removed and/
or ignored. Please refer to the page number next to the element for further details on which elements
have been removed and/or ignored.
.
Used in element(s)
"Other" on page 70
4.31.1 Identification
XML Tag: Id
Presence: [1..1]
Definition: Identification assigned by an institution.
Datatype: "Max35Text" on page 164
4.31.2 SchemeName
XML Tag: SchmeNm
Presence: [0..1]
16 February 2022 61
Usage Guideline
• This element(pain.001.001.03/GroupHeader/InitiatingParty/Identification/OrganisationIdentifi-
cation/Other/SchemeName) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/Identification/OrganisationIdentification/Other/SchemeName) will be ignored by
the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ul-
timateDebtor/Identification/OrganisationIdentification/Other/SchemeName) will be ignored by
the Receiver.
• This element(pain.001.001.03/PaymentInformation/Debtor/Identification/OrganisationIdentifi-
cation/Other/SchemeName) will be ignored by the Receiver.
4.31.3 Issuer
XML Tag: Issr
Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/GroupHeader/InitiatingParty/Identification/OrganisationIdentifi-
cation/Other/Issuer) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/Identification/OrganisationIdentification/Other/Issuer) will be ignored by the Re-
ceiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ul-
timateDebtor/Identification/OrganisationIdentification/Other/Issuer) will be ignored by the Re-
ceiver.
• This element(pain.001.001.03/PaymentInformation/Debtor/Identification/OrganisationIdentifi-
cation/Other/Issuer) will be ignored by the Receiver.
4.32 GenericPersonIdentification1
Definition: Information related to an identification of a person.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Other" on page 95
4.32.1 Identification
XML Tag: Id
Presence: [1..1]
Definition: Unique and unambiguous identification of a person.
Datatype: "Max35Text" on page 164
4.32.2 SchemeName
XML Tag: SchmeNm
Presence: [0..1]
Definition: Name of the identification scheme.
The SchmeNm block contains the following elements (see datatype "PersonIdentificationScheme-
Name1Choice" on page 95 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.32.3 Issuer
XML Tag: Issr
Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 164
16 February 2022 63
Usage Guideline
4.33 GroupHeader32
Definition: Set of characteristics shared by all individual transactions included in the message.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"GroupHeader" on page 6
4.33.1 MessageIdentification
XML Tag: MsgId
Presence: [1..1]
Definition: Point to point reference, as assigned by the instructing party, and sent to the next party in the
chain to unambiguously identify the message.
Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party
for a pre-agreed period.
Datatype: "Max35Text" on page 164
4.33.2 CreationDateTime
XML Tag: CreDtTm
Presence: [1..1]
Definition: Date and time at which the message was created.
Datatype: "ISODateTime" on page 160
4.33.3 Authorisation
XML Tag: Authstn
Presence: [0..2]
Definition: User identification or any user key to be used to check whether the initiating party is allowed
to initiate transactions from the account specified in the message.
Usage: The content is not of a technical nature, but reflects the organisational structure at the initiating
side.
The authorisation element can typically be used in relay scenarios, payment initiations, payment returns
or payment reversals that are initiated on behalf of a party different from the initiating party.
The Authstn block contains the following elements (see datatype "Authorisation1Choice" on
page 11 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/GroupHeader/Authorisation
This element has change repeatability, the maximum occurrence has been changed to : 1
4.33.4 NumberOfTransactions
XML Tag: NbOfTxs
Presence: [1..1]
Definition: Number of individual transactions contained in the message.
Datatype: "Max15NumericText" on page 162
4.33.5 ControlSum
XML Tag: CtrlSum
Presence: [0..1]
Definition: Total of all individual amounts included in the message, irrespective of currencies.
Datatype: "DecimalNumber" on page 148
4.33.6 InitiatingParty
XML Tag: InitgPty
Presence: [1..1]
Definition: Party that initiates the payment.
Usage: This can either be the debtor or the party that initiates the credit transfer on behalf of the debtor.
The InitgPty block contains the following elements (see datatype "PartyIdentification32" on page 72
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 65
Usage Guideline
4.33.7 ForwardingAgent
XML Tag: FwdgAgt
Presence: [0..1]
Definition: Financial institution that receives the instruction from the initiating party and forwards it to the
next agent in the payment chain for execution.
The FwdgAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIden-
tification4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.34 InstructionForCreditorAgent1
Definition: Further information related to the processing of the payment instruction that may need to be
acted upon by the creditor's agent. The instruction may relate to a level of service, or may be an instruc-
tion that has to be executed by the creditor's agent, or may be information required by the creditor's
agent.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"InstructionForCreditorAgent" on page 41
4.34.1 Code
XML Tag: Cd
Presence: [0..1]
Definition: Coded information related to the processing of the payment instruction, provided by the initi-
ating party, and intended for the creditor's agent.
Datatype: "Instruction3Code" on page 160
4.34.2 InstructionInformation
XML Tag: InstrInf
Presence: [0..1]
Definition: Further information complementing the coded instruction or instruction to the creditor's agent
that is bilaterally agreed or specific to a user community.
Datatype: "Max140Text" on page 162
4.35 LocalInstrument2Choice
Definition: Set of elements that further identifies the type of local instruments being requested by the ini-
tiating party.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"LocalInstrument" on page 93
4.35.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Specifies the local instrument, as published in an external local instrument code list.
Datatype: "ExternalLocalInstrument1Code" on page 155
4.35.2 Proprietary
XML Tag: Prtry
16 February 2022 67
Usage Guideline
Presence: [1..1]
Definition: Specifies the local instrument, as a proprietary code.
Datatype: "Max35Text" on page 164
4.36 NameAndAddress10
Definition: Information that locates and identifies a party.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ChequeFrom" on page 22, "DeliverTo" on page 23, "RemittanceLocationPostalAddress" on
page 109
4.36.1 Name
XML Tag: Nm
Presence: [1..1]
Definition: Name by which a party is known and is usually used to identify that party.
Datatype: "Max140Text" on page 162
4.36.2 Address
XML Tag: Adr
Presence: [1..1]
Definition: Postal address of a party.
The Adr block contains the following elements (see datatype "PostalAddress6" on page 96 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Adr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
4.37 OrganisationIdentification4
Definition: Unique and unambiguous way to identify an organisation.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 69
Usage Guideline
Used in element(s)
"OrganisationIdentification" on page 71
4.37.1 BICOrBEI
XML Tag: BICOrBEI
Presence: [0..1]
Definition: Code allocated to a financial institution or non financial institution by the ISO 9362 Registra-
tion Authority as described in ISO 9362 "Banking - Banking telecommunication messages - Business
identifier code (BIC)".
Datatype: "AnyBICIdentifier" on page 134
4.37.2 Other
XML Tag: Othr
Presence: [0..*]
Definition: Unique identification of an organisation, as assigned by an institution, using an identification
scheme.
The Othr block contains the following elements (see datatype "GenericOrganisationIdentification1" on
page 61 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Othr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• on pain.001.001.03/GroupHeader/InitiatingParty/Identification/OrganisationIdentification/Other
This element has change repeatability, the maximum occurrence has been changed to : 1
4.38 OrganisationIdentificationSchemeName1Choice
Definition: Sets of elements to identify a name of the organisation identification scheme.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"SchemeName" on page 61
4.38.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: "ExternalOrganisationIdentification1Code" on page 156
4.38.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 164
4.39 Party6Choice
Definition: Nature or use of the account.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Party6Choice blocks have this element removed and/or ignored. Please refer
to the page number next to the element for further details on which elements have been removed and/
or ignored.
.
Used in element(s)
"Identification" on page 75, "Identification" on page 78
4.39.1 OrganisationIdentification
XML Tag: OrgId
Presence: [1..1]
16 February 2022 71
Usage Guideline
4.39.2 PrivateIdentification
XML Tag: PrvtId
Presence: [1..1]
Definition: Unique and unambiguous identification of a person, for example a passport.
The PrvtId block contains the following elements (see datatype "PersonIdentification5" on page 94
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/GroupHeader/InitiatingParty/Identification/PrivateIdentification)
will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/Identification/PrivateIdentification) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ulti-
mateDebtor/Identification/PrivateIdentification) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/Debtor/Identification/PrivateIdentification)
will be ignored by the Receiver.
4.40 PartyIdentification32
Definition: Set of elements used to identify a person or an organisation.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all PartyIdentification32 blocks have this element removed and/or ignored.
Please refer to the page number next to the element for further details on which elements have been re-
moved and/or ignored.
.
Used in element(s)
"Debtor" on page 87, "InitiatingParty" on page 65, "Invoicee" on page 115, "Invoicer" on
page 115, "UltimateCreditor" on page 40, "UltimateDebtor" on page 89, "UltimateDebtor" on
page 35
4.40.1 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which a party is known and which is usually used to identify that party.
Datatype: "Max140Text" on page 162
• on pain.001.001.03/PaymentInformation/Debtor/Name
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/Debtor/Name
Comment:
Debtor Name is limited to 35 characters
4.40.2 PostalAddress
XML Tag: PstlAdr
Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.
The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 96 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 73
Usage Guideline
, >> Note as not all PstlAdr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• on pain.001.001.03/PaymentInformation/Debtor/PostalAddress
This element is now mandatory, the minimum occurrence has been changed to : 1
4.40.3 Identification
XML Tag: Id
Presence: [0..1]
Definition: Unique and unambiguous identification of a party.
The Id block contains the following elements (see datatype "Party6Choice" on page 71 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Id blocks have this element removed and/or ignored. Please refer to the page
number next to the element for further details on which elements have been removed and/or ignored.
.
4.40.4 CountryOfResidence
XML Tag: CtryOfRes
Presence: [0..1]
Definition: Country in which a person resides (the place of a person's home). In the case of a company,
it is the country from which the affairs of that company are directed.
Datatype: "CountryCode" on page 147
4.40.5 ContactDetails
XML Tag: CtctDtls
Presence: [0..1]
Definition: Set of elements used to indicate how to contact the party.
The CtctDtls block contains the following elements (see datatype "ContactDetails2" on page 28 for
details)
16 February 2022 75
Usage Guideline
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ulti-
mateDebtor/ContactDetails) will be ignored by the Receiver.
4.41 PartyIdentification32__1
Definition: Set of elements used to identify a person or an organisation.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Creditor" on page 39
4.41.1 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name by which a party is known and which is usually used to identify that party.
Datatype: "Max35Text" on page 164
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor/Name
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor/Name
Type changed to: Max35Text on page 164
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor/Name
– HSBC_Name:
4.41.2 PostalAddress
XML Tag: PstlAdr
Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.
The PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 96 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 77
Usage Guideline
, >> Note as not all PstlAdr blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor/Posta-
lAddress
This element is now mandatory, the minimum occurrence has been changed to : 1
4.41.3 Identification
XML Tag: Id
Presence: [0..1]
Definition: Unique and unambiguous identification of a party.
The Id block contains the following elements (see datatype "Party6Choice" on page 71 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Id blocks have this element removed and/or ignored. Please refer to the page
number next to the element for further details on which elements have been removed and/or ignored.
.
4.41.4 CountryOfResidence
XML Tag: CtryOfRes
Presence: [0..1]
Definition: Country in which a person resides (the place of a person's home). In the case of a company,
it is the country from which the affairs of that company are directed.
Datatype: "CountryCode" on page 147
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/CountryOfResidence) will be ignored by the Receiver.
4.41.5 ContactDetails
XML Tag: CtctDtls
Presence: [0..1]
Definition: Set of elements used to indicate how to contact the party.
The CtctDtls block contains the following elements (see datatype "ContactDetails2" on page 28 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 79
Usage Guideline
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/ContactDetails) will be ignored by the Receiver.
4.42 PaymentIdentification1__1
Definition: Set of elements used to provide further means of referencing a payment transaction.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"PaymentIdentification" on page 32
4.42.1 InstructionIdentification
XML Tag: InstrId
Presence: [0..1]
Definition: Unique identification as assigned by an instructing party for an instructed party to unambigu-
ously identify the instruction.
Usage: The instruction identification is a point to point reference that can be used between the instruct-
ing party and the instructed party to refer to the individual instruction. It can be included in several mes-
sages related to the instruction.
Datatype: "Max12Text" on page 161
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentIdenti-
fication/InstructionIdentification
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentIdenti-
fication/InstructionIdentification
Type changed to: Max12Text on page 161
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentIdenti-
fication/InstructionIdentification
Comment:
The same Instruction Identification must not be reused within a 3 month period
(Max. 12 Chars)
4.42.2 EndToEndIdentification
XML Tag: EndToEndId
Presence: [1..1]
Definition: Unique identification assigned by the initiating party to unambiguously identify the transac-
tion. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the trans-
action. It can be included in several messages related to the transaction.
Datatype: "Max16Text" on page 162
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentIdenti-
fication/EndToEndIdentification
Type changed to: Max16Text on page 162
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentIdenti-
fication/EndToEndIdentification
Comment:
Unique transaction reference
4.43 PaymentInstructionInformation3__1
Definition: Set of characteristics that apply to the debit side of the payment transactions included in the
credit transfer initiation.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 81
Usage Guideline
Rules
R9 PaymentTypeInformationRule ✓
If PaymentTypeInformation is present, then CreditTransferTransactionInformation/Payment-
TypeInformation is not allowed.
Error handling:
R10 ChequeInstructionRule ✓
If PaymentMethod is different from CHK, then CreditTransferTransactionInformation/ChequeIn-
struction is not allowed.
Error handling:
R11 ChargesAccountRule ✓
If ChargesAccountAgent is present, then ChargesAccount must be present.
Error handling:
R12 ChargesAccountAgentRule
If ChargesAccountAgent is present, then it must contain a branch of the DebtorAgent. It must
not contain a completely different agent.
Error handling: Undefined
R13 ChargeBearerRule ✓
R14 UltimateDebtorRule ✓
If UltimateDebtor is present, then CreditTransferTransactionInformation/UltimateDebtor is not
allowed.
R15 ChequeAndCreditorAccountRule ✓
If PaymentMethod is CHK, then CreditTransferTransactionInformation/CreditorAccount is not
allowed.
Error handling:
R16 ChequeDeliveryAndCreditorAgentRule ✓
If PaymentMethod is CHK and CreditTransferTransactionInformation/ChequeInstruction/Deliv-
eryMethod/Code is present and is equal to MLFA, CRFA, RGFA or PUFA, then CreditTransfer-
TransactionInformation/CreditorAgent must be present.
Error handling:
– Error Text: Invalid message content for cheque payment with creditor agent.
R17 ChequeDeliveryAndNoCreditorAgentRule ✓
16 February 2022 83
Usage Guideline
– Error Text: Invalid message content for cheque payment without creditor agent.
R18 NonChequePaymentMethodRule
If PaymentMethod is different from CHK and CreditTransferTransactionInformation/Creditor is
not present, then CreditTransferTransactionInformation/CreditorAccount must be present.
Error handling:
– Error Text: Invalid message content for non cheque payment method.
R19 ChequeNoDeliveryAndNoCreditorAgentRule ✓
If PaymentMethod is CHK and CreditTransferTransactionInformation/ChequeInstruction/Deliv-
eryMethod is not present, then CreditTransferTransactionInformation/CreditorAgent is not al-
lowed.
Error handling:
– Error Text: Invalid message content for cheque payment without delivery method.
Guidelines
1. UltimateDebtorGuideline
UltimateDebtor may only be present if different from Debtor.
2. ChequeInstructionDeliverToDebtorGuideline
If CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod is present and if Cred-
itTransferTransactionInformation/ChequeInstruction/DeliveryMethod/Code is CRDB, MLDB, PUDB
or RGDB, then CreditTransferTransactionInformation/ChequeInstruction/DeliverTo may only be
present if different from Debtor.
3. ChequeInstructionDeliverToCreditorGuideline
If PaymentInformation/CreditTransferTransactionInformation/ChequeInstruction/DeliveryMethod
is present and is CRCD, MLCD, PUCD or RGCD, then CreditTransferTransactionInforma-
tion/ChequeInstruction/DeliverTo may only be present if different from CreditTransferTransactionIn-
formation/Creditor.
4. ChequeInstructionDeliverToCreditorAgentGuideline
5. ChequeFromGuideline
CreditTransferTransactionInformation/ChequeInstruction/ChequeFrom may only be present if dif-
ferent from CreditTransferTransactionInformation/UltimateDebtor or Debtor.
Used in element(s)
"PaymentInformation" on page 6
4.43.1 PaymentInformationIdentification
XML Tag: PmtInfId
Presence: [1..1]
Definition: Unique identification, as assigned by a sending party, to unambiguously identify the payment
information group within the message.
Datatype: "Max24Text" on page 163
• on pain.001.001.03/PaymentInformation/PaymentInformationIdentification
Type changed to: Max24Text on page 163
• on pain.001.001.03/PaymentInformation/PaymentInformationIdentification
– HSBC_PaymentInformationIdentification:
• on pain.001.001.03/PaymentInformation/PaymentInformationIdentification
Comment:
Payment Information Identification is limited to 12 characters
4.43.2 PaymentMethod
XML Tag: PmtMtd
Presence: [1..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod3Code" on page 167
4.43.3 BatchBooking
XML Tag: BtchBookg
Presence: [0..1]
Definition: 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.
16 February 2022 85
Usage Guideline
Usage: Batch booking is used to request and not order a possible batch booking.
Datatype: "BatchBookingIndicator" on page 137
4.43.4 NumberOfTransactions
XML Tag: NbOfTxs
Presence: [0..1]
Definition: Number of individual transactions contained in the paymnet information group.
Datatype: "Max15NumericText" on page 162
4.43.5 ControlSum
XML Tag: CtrlSum
Presence: [0..1]
Definition: Total of all individual amounts included in the group, irrespective of currencies.
Datatype: "DecimalNumber" on page 148
4.43.6 PaymentTypeInformation
XML Tag: PmtTpInf
Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.
The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation19" on
page 92 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.43.7 RequestedExecutionDate
XML Tag: ReqdExctnDt
Presence: [1..1]
Definition: 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. If payment by cheque, the date
when the cheque must be generated by the bank.
• on pain.001.001.03/PaymentInformation/RequestedExecutionDate
Comment:
Day on which the payment should be initiated
4.43.8 PoolingAdjustmentDate
XML Tag: PoolgAdjstmntDt
Presence: [0..1]
Definition: Date used for the correction of the value date of a cash pool movement that has been posted
with a different value date.
Datatype: "ISODate" on page 159
4.43.9 Debtor
XML Tag: Dbtr
Presence: [1..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
The Dbtr block contains the following elements (see datatype "PartyIdentification32" on page 72 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.43.10 DebtorAccount
XML Tag: DbtrAcct
Presence: [1..1]
16 February 2022 87
Usage Guideline
Definition: Unambiguous identification of the account of the debtor to which a debit entry will be made
as a result of the transaction.
The DbtrAcct block contains the following elements (see datatype "CashAccount16" on page 17 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.43.11 DebtorAgent
XML Tag: DbtrAgt
Presence: [1..1]
Definition: Financial institution servicing an account for the debtor.
The DbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-
fication4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/DebtorAgent
– HSBC_DebtorAgent:
4.43.12 DebtorAgentAccount
XML Tag: DbtrAgtAcct
Presence: [0..1]
Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in the
payment chain.
The DbtrAgtAcct block contains the following elements (see datatype "CashAccount16" on page 17
for details)
4.43.13 UltimateDebtor
XML Tag: UltmtDbtr
Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
The UltmtDbtr block contains the following elements (see datatype "PartyIdentification32" on
page 72 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all UltmtDbtr blocks have this element removed and/or ignored. Please refer to
the page number next to the element for further details on which elements have been removed and/or
ignored.
.
4.43.14 ChargeBearer
XML Tag: ChrgBr
Presence: [0..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the pay-
ment transaction.
16 February 2022 89
Usage Guideline
4.43.15 ChargesAccount
XML Tag: ChrgsAcct
Presence: [0..1]
Definition: Account used to process charges associated with a transaction.
Usage: Charges account should be used when charges have to be booked to an account different from
the account identified in debtor's account.
The ChrgsAcct block contains the following elements (see datatype "CashAccount16" on page 17
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.43.16 ChargesAccountAgent
XML Tag: ChrgsAcctAgt
Presence: [0..1]
Definition: Agent that services a charges account.
Usage: Charges account agent should only be used when the charges account agent is different from
the debtor agent.
The ChrgsAcctAgt block contains the following elements (see datatype "BranchAndFinancialInstitu-
tionIdentification4" on page 12 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.43.17 CreditTransferTransactionInformation
XML Tag: CdtTrfTxInf
Presence: [1..*]
Definition: Set of elements used to provide information on the individual transaction(s) included in the
message.
The CdtTrfTxInf block contains the following elements (see datatype "CreditTransferTransactionInfor-
mation10__1" on page 29 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 91
Usage Guideline
4.44 PaymentTypeInformation19
Definition: Set of elements used to provide further details of the type of payment.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"PaymentTypeInformation" on page 86, "PaymentTypeInformation" on page 32
4.44.1 InstructionPriority
XML Tag: InstrPrty
Presence: [0..1]
Definition: Indicator of the urgency or order of importance that the instructing party would like the in-
structed party to apply to the processing of the instruction.
Datatype: "Priority2Code" on page 168
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Pay-
mentTypeInformation/InstructionPriority) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/PaymentTypeInformation/InstructionPriori-
ty) will be ignored by the Receiver.
4.44.2 ServiceLevel
XML Tag: SvcLvl
Presence: [0..1]
Definition: Agreement under which or rules under which the transaction should be processed.
The SvcLvl block contains the following elements (see datatype "ServiceLevel8Choice" on page 110
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/PaymentTypeInformation/ServiceLevel
This element is now mandatory, the minimum occurrence has been changed to : 1
4.44.3 LocalInstrument
XML Tag: LclInstrm
Presence: [0..1]
Definition: User community specific instrument.
Usage: This element is used to specify a local instrument, local clearing option and/or further qualify the
service or service level.
The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice" on
page 67 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
16 February 2022 93
Usage Guideline
4.44.4 CategoryPurpose
XML Tag: CtgyPurp
Presence: [0..1]
Definition: 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 pay-
ment. It is likely to trigger special processing by any of the agents involved in the payment chain.
The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice" on
page 20 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.45 PersonIdentification5
Definition: Unique and unambiguous way to identify a person.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"PrivateIdentification" on page 72
4.45.1 DateAndPlaceOfBirth
XML Tag: DtAndPlcOfBirth
Presence: [0..1]
Definition: Date and place of birth of a person.
The DtAndPlcOfBirth block contains the following elements (see datatype "DateAndPlaceOfBirth" on
page 47 for details)
4.45.2 Other
XML Tag: Othr
Presence: [0..*]
Definition: Unique identification of a person, as assigned by an institution, using an identification
scheme.
The Othr block contains the following elements (see datatype "GenericPersonIdentification1" on
page 63 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.46 PersonIdentificationSchemeName1Choice
Definition: Sets of elements to identify a name of the identification scheme.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"SchemeName" on page 63
4.46.1 Code
XML Tag: Cd
16 February 2022 95
Usage Guideline
Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: "ExternalPersonIdentification1Code" on page 156
4.46.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 164
4.47 PostalAddress6
Definition: Information that locates and identifies a specific address, as defined by postal services.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all PostalAddress6 blocks have this element removed and/or ignored. Please
refer to the page number next to the element for further details on which elements have been removed
and/or ignored.
.
Used in element(s)
"Address" on page 68, "PostalAddress" on page 15, "PostalAddress" on page 73, "PostalAd-
dress" on page 53, "PostalAddress" on page 56, "PostalAddress" on page 77
4.47.1 AddressType
XML Tag: AdrTp
Presence: [0..1]
Definition: Identifies the nature of the postal address.
Datatype: "AddressType2Code" on page 133
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/Creditor/PostalAddress/AddressType) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInforma-
tion/CreditorAgent/FinancialInstitutionIdentification/PostalAddress/AddressType) will be ig-
nored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/In-
termediaryAgent1/FinancialInstitutionIdentification/PostalAddress/AddressType) will be ig-
nored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
latedRemittanceInformation/RemittanceLocationPostalAddress/Address/AddressType) will be
ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Ulti-
mateDebtor/PostalAddress/AddressType) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/UltimateDebtor/PostalAddress/Ad-
dressType) will be ignored by the Receiver.
16 February 2022 97
Usage Guideline
4.47.2 Department
XML Tag: Dept
Presence: [0..1]
Definition: Identification of a division of a large organisation or building.
Datatype: "Max70Text" on page 165
• This element(pain.001.001.03/PaymentInformation/UltimateDebtor/PostalAddress/Department)
will be ignored by the Receiver.
4.47.3 SubDepartment
XML Tag: SubDept
Presence: [0..1]
Definition: Identification of a sub-division of a large organisation or building.
Datatype: "Max70Text" on page 165
• This element(pain.001.001.03/PaymentInformation/UltimateDebtor/PostalAddress/SubDepart-
ment) will be ignored by the Receiver.
4.47.4 StreetName
XML Tag: StrtNm
Presence: [0..1]
Definition: Name of a street or thoroughfare.
Datatype: "Max70Text" on page 165
4.47.5 BuildingNumber
XML Tag: BldgNb
Presence: [0..1]
Definition: Number that identifies the position of a building on a street.
Datatype: "Max16Text" on page 162
4.47.6 PostCode
XML Tag: PstCd
Presence: [0..1]
Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address to
assist the sorting of mail.
4.47.7 TownName
XML Tag: TwnNm
Presence: [0..1]
Definition: Name of a built-up area, with defined boundaries, and a local government.
Datatype: "Max35Text" on page 164
4.47.8 CountrySubDivision
XML Tag: CtrySubDvsn
Presence: [0..1]
Definition: Identifies a subdivision of a country such as state, region, county.
Datatype: "Max35Text" on page 164
4.47.9 Country
XML Tag: Ctry
Presence: [0..1]
Definition: Nation with its own government.
Datatype: "CountryCode" on page 147
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Creditor/Posta-
lAddress/Country
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/CreditorA-
gent/FinancialInstitutionIdentification/PostalAddress/Country
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/Debtor/PostalAddress/Country
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/DebtorAgent/FinancialInstitutionIdentification/Postal-
Address/Country
This element is now mandatory, the minimum occurrence has been changed to : 1
4.47.10 AddressLine
XML Tag: AdrLine
Presence: [0..7]
Definition: Information that locates and identifies a specific address, as defined by postal services, pre-
sented in free format text.
16 February 2022 99
Usage Guideline
4.48 Purpose2Choice
Definition: Specifies the underlying reason for the payment transaction.
Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) credi-
tor 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.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Purpose" on page 41
4.48.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Underlying reason for the payment transaction, as published in an external purpose code list.
Datatype: "ExternalPurpose1Code" on page 157
4.48.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Purpose, in a proprietary form.
Datatype: "Max35Text" on page 164
4.49 ReferredDocumentInformation3
Definition: Set of elements used to identify the documents referred to in the remittance information.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ReferredDocumentInformation" on page 114
4.49.1 Type
XML Tag: Tp
Presence: [0..1]
Definition: Specifies the type of referred document.
The Tp block contains the following elements (see datatype "ReferredDocumentType2" on page 102
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.49.2 Number
XML Tag: Nb
Presence: [0..1]
Definition: Unique and unambiguous identification of the referred document.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentInformation/Number) will be ignored by the
Receiver.
4.49.3 RelatedDate
XML Tag: RltdDt
Presence: [0..1]
Definition: Date associated with the referred document.
Datatype: "ISODate" on page 159
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentInformation/RelatedDate) will be ignored
by the Receiver.
4.50 ReferredDocumentType1Choice
Definition: Specifies the type of the document referred in the remittance information.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"CodeOrProprietary" on page 103
4.50.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Document type in a coded form.
Datatype: "DocumentType5Code" on page 149
4.50.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Proprietary identification of the type of the remittance document.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentInformation/Type/CodeOrProprietary/Pro-
prietary) will be ignored by the Receiver.
4.51 ReferredDocumentType2
Definition: Specifies the type of the document referred in the remittance information.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Type" on page 101
4.51.1 CodeOrProprietary
XML Tag: CdOrPrtry
Presence: [1..1]
Definition: Provides the type details of the referred document.
The CdOrPrtry block contains the following elements (see datatype "ReferredDocumentType1Choice"
on page 102 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.51.2 Issuer
XML Tag: Issr
Presence: [0..1]
Definition: Identification of the issuer of the reference document type.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentInformation/Type/Issuer) will be ignored by
the Receiver.
4.52 RegulatoryAuthority2
Definition: Entity requiring the regulatory reporting information.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Authority" on page 104
4.52.1 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name of the entity requiring the regulatory reporting information.
Datatype: "Max140Text" on page 162
4.52.2 Country
XML Tag: Ctry
Presence: [0..1]
Definition: Country of the entity that requires the regulatory reporting information.
Datatype: "CountryCode" on page 147
4.53 RegulatoryReporting3__1
Definition: Information needed due to regulatory and/or statutory requirements.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"RegulatoryReporting" on page 42
4.53.1 DebitCreditReportingIndicator
XML Tag: DbtCdtRptgInd
Presence: [0..1]
Definition: Identifies whether the regulatory reporting information applies to the debit side, to the credit
side or to both debit and credit sides of the transaction.
Datatype: "RegulatoryReportingType1Code" on page 169
4.53.2 Authority
XML Tag: Authrty
Presence: [0..1]
Definition: Entity requiring the regulatory reporting information.
The Authrty block contains the following elements (see datatype "RegulatoryAuthority2" on page 103
for details)
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Reg-
ulatoryReporting/Authority) will be ignored by the Receiver.
4.53.3 Details
XML Tag: Dtls
Presence: [0..*]
Definition: Set of elements used to provide details on the regulatory reporting information.
The Dtls block contains the following elements (see datatype "StructuredRegulatoryReporting3__1" on
page 111 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RegulatoryRe-
porting/Details
This element is now mandatory, the minimum occurrence has been changed to : 1
4.54 RemittanceAmount1
Definition: Nature of the amount and currency on a document referred to in the remittance section, typ-
ically either the original amount due/payable or the amount actually remitted for the referenced docu-
ment.
Used in element(s)
"ReferredDocumentAmount" on page 114
4.54.1 DuePayableAmount
XML Tag: DuePyblAmt
Presence: [0..1]
Definition: Amount specified is the exact amount due and payable to the creditor.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.54.2 DiscountAppliedAmount
XML Tag: DscntApldAmt
Presence: [0..1]
Definition: Amount of money that results from the application of an agreed discount to the amount due
and payable to the creditor.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.54.3 CreditNoteAmount
XML Tag: CdtNoteAmt
Presence: [0..1]
Definition: Amount specified for the referred document is the amount of a credit note.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.54.4 TaxAmount
XML Tag: TaxAmt
Presence: [0..1]
Definition: Quantity of cash resulting from the calculation of the tax.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentAmount/TaxAmount) will be ignored by the
Receiver.
4.54.5 AdjustmentAmountAndReason
XML Tag: AdjstmntAmtAndRsn
Presence: [0..*]
Definition: Set of elements used to provide information on the amount and reason of the document ad-
justment.
The AdjstmntAmtAndRsn block contains the following elements (see datatype "DocumentAdjust-
ment1" on page 48 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/ReferredDocumentAmount/AdjustmentAmountAndReason)
will be ignored by the Receiver.
4.54.6 RemittedAmount
XML Tag: RmtdAmt
Presence: [0..1]
Definition: Amount of money remitted for the referred document.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.55 RemittanceInformation5
Definition: 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.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"RemittanceInformation" on page 44
4.55.1 Unstructured
XML Tag: Ustrd
Presence: [0..*]
Definition: 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 un-
structured form.
Datatype: "Max140Text" on page 162
4.55.2 Structured
XML Tag: Strd
Presence: [0..*]
Definition: 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.
The Strd block contains the following elements (see datatype "StructuredRemittanceInformation7" on
page 113 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.56 RemittanceLocation2
Definition: Set of elements used to provide information on the remittance advice.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"RelatedRemittanceInformation" on page 43
4.56.1 RemittanceIdentification
XML Tag: RmtId
Presence: [0..1]
Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the remit-
tance information sent separately from the payment instruction, such as a remittance advice.
Datatype: "Max35Text" on page 164
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RelatedRemit-
tanceInformation/RemittanceIdentification
Comment:
Refer to Advising Appendix
4.56.2 RemittanceLocationMethod
XML Tag: RmtLctnMtd
Presence: [0..1]
Definition: Method used to deliver the remittance advice information.
Datatype: "RemittanceLocationMethod2Code" on page 170
4.56.3 RemittanceLocationElectronicAddress
XML Tag: RmtLctnElctrncAdr
Presence: [0..1]
Definition: Electronic address to which an agent is to send the remittance information.
Datatype: "Max2048Text" on page 163
4.56.4 RemittanceLocationPostalAddress
XML Tag: RmtLctnPstlAdr
Presence: [0..1]
4.57 ServiceLevel8Choice
Definition: Specifies the service level of the transaction.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"ServiceLevel" on page 93
4.57.1 Code
XML Tag: Cd
Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as published in an ex-
ternal service level code list.
Datatype: "ExternalServiceLevel1Code" on page 158
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/PaymentType-
Information/ServiceLevel/Code
Single value: NURG
• on pain.001.001.03/PaymentInformation/PaymentTypeInformation/ServiceLevel/Code
Single value: NURG
4.57.2 Proprietary
XML Tag: Prtry
Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Pay-
mentTypeInformation/ServiceLevel/Proprietary) is removed.
• This element(pain.001.001.03/PaymentInformation/PaymentTypeInformation/ServiceLevel/Pro-
prietary) is removed.
4.58 StructuredRegulatoryReporting3__1
Definition: Information needed due to regulatory and statutory requirements.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Details" on page 105
4.58.1 Type
XML Tag: Tp
Presence: [0..1]
Definition: Specifies the type of the information supplied in the regulatory reporting details.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Reg-
ulatoryReporting/Details/Type) will be ignored by the Receiver.
4.58.2 Date
XML Tag: Dt
Presence: [0..1]
Definition: Date related to the specified type of regulatory reporting details.
Datatype: "ISODate" on page 159
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Reg-
ulatoryReporting/Details/Date) will be ignored by the Receiver.
4.58.3 Country
XML Tag: Ctry
Presence: [0..1]
Definition: Country related to the specified type of regulatory reporting details.
Datatype: "CountryCode" on page 147
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Reg-
ulatoryReporting/Details/Country) will be ignored by the Receiver.
4.58.4 Code
XML Tag: Cd
Presence: [0..1]
Definition: Specifies the nature, purpose, and reason for the transaction to be reported for regulatory
and statutory requirements in a coded form.
Datatype: "Max3Text" on page 164
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RegulatoryRe-
porting/Details/Code
This element is now mandatory, the minimum occurrence has been changed to : 1
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RegulatoryRe-
porting/Details/Code
• on pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/RegulatoryRe-
porting/Details/Code
Comment:
3 digits payment purpose code is required. Please contact your Client Integration
or Client Service manager for the updated UAE purpose of payment code list.
4.58.5 Amount
XML Tag: Amt
Presence: [0..1]
Definition: Amount of money to be reported for regulatory and statutory requirements.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Reg-
ulatoryReporting/Details/Amount) will be ignored by the Receiver.
4.58.6 Information
XML Tag: Inf
Presence: [0..*]
Definition: Additional details that cater for specific domestic regulatory requirements.
Datatype: "Max35Text" on page 164
4.59 StructuredRemittanceInformation7
Definition: 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.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Structured" on page 108
4.59.1 ReferredDocumentInformation
XML Tag: RfrdDocInf
Presence: [0..*]
Definition: Set of elements used to identify the documents referred to in the remittance information.
The RfrdDocInf block contains the following elements (see datatype "ReferredDocumentInformation3"
on page 100 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.59.2 ReferredDocumentAmount
XML Tag: RfrdDocAmt
Presence: [0..1]
Definition: Set of elements used to provide details on the amounts of the referred document.
The RfrdDocAmt block contains the following elements (see datatype "RemittanceAmount1" on
page 105 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.59.3 CreditorReferenceInformation
XML Tag: CdtrRefInf
Presence: [0..1]
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.
The CdtrRefInf block contains the following elements (see datatype "CreditorReferenceInformation2"
on page 44 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.59.4 Invoicer
XML Tag: Invcr
Presence: [0..1]
Definition: Identification of the organisation issuing the invoice, when it is different from the creditor or
ultimate creditor.
The Invcr block contains the following elements (see datatype "PartyIdentification32" on page 72 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/Invoicer) will be ignored by the Receiver.
4.59.5 Invoicee
XML Tag: Invcee
Presence: [0..1]
Definition: Identification of the party to whom an invoice is issued, when it is different from the debtor or
ultimate debtor.
The Invcee block contains the following elements (see datatype "PartyIdentification32" on page 72
for details)
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/Invoicee) will be ignored by the Receiver.
4.59.6 AdditionalRemittanceInformation
XML Tag: AddtlRmtInf
Presence: [0..3]
Definition: Additional information, in free text form, to complement the structured remittance information.
Datatype: "Max140Text" on page 162
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Re-
mittanceInformation/Structured/AdditionalRemittanceInformation) will be ignored by the Re-
ceiver.
4.60 TaxAmount1
Definition: Set of elements used to provide information on the tax amount(s) of tax record.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"TaxAmount" on page 128
4.60.1 Rate
XML Tag: Rate
Presence: [0..1]
Definition: Rate used to calculate the tax.
Datatype: "PercentageRate" on page 168
4.60.2 TaxableBaseAmount
XML Tag: TaxblBaseAmt
Presence: [0..1]
Definition: Amount of money on which the tax is based.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.60.3 TotalAmount
XML Tag: TtlAmt
Presence: [0..1]
Definition: Total amount that is the result of the calculation of the tax for the record.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/TaxAmount/TotalAmount) will be ignored by the Receiver.
4.60.4 Details
XML Tag: Dtls
Presence: [0..*]
Definition: Set of elements used to provide details on the tax period and amount.
The Dtls block contains the following elements (see datatype "TaxRecordDetails1" on page 128 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.61 TaxAuthorisation1
Definition: Details of the authorised tax paying party.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Authorisation" on page 124
4.61.1 Title
XML Tag: Titl
Presence: [0..1]
Definition: Title or position of debtor or the debtor's authorised representative.
Datatype: "Max35Text" on page 164
4.61.2 Name
XML Tag: Nm
Presence: [0..1]
Definition: Name of the debtor or the debtor's authorised representative.
Datatype: "Max140Text" on page 162
4.62 TaxInformation3
Definition: Details about tax paid, or to be paid, to the government in accordance with the law, including
pre-defined parameters such as thresholds and type of account.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Tax" on page 42
4.62.1 Creditor
XML Tag: Cdtr
Presence: [0..1]
Definition: Party on the credit side of the transaction to which the tax applies.
The Cdtr block contains the following elements (see datatype "TaxParty1" on page 121 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.62.2 Debtor
XML Tag: Dbtr
Presence: [0..1]
Definition: Set of elements used to identify the party on the debit side of the transaction to which the tax
applies.
The Dbtr block contains the following elements (see datatype "TaxParty2" on page 122 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.62.3 AdministrationZone
XML Tag: AdmstnZn
Presence: [0..1]
Definition: Territorial part of a country to which the tax payment is related.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
AdministrationZone) will be ignored by the Receiver.
4.62.4 ReferenceNumber
XML Tag: RefNb
Presence: [0..1]
Definition: Tax reference information that is specific to a taxing agency.
Datatype: "Max140Text" on page 162
4.62.5 Method
XML Tag: Mtd
Presence: [0..1]
Definition: Method used to indicate the underlying business or how the tax is paid.
Datatype: "Max35Text" on page 164
4.62.6 TotalTaxableBaseAmount
XML Tag: TtlTaxblBaseAmt
Presence: [0..1]
Definition: Total amount of money on which the tax is based.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.62.7 TotalTaxAmount
XML Tag: TtlTaxAmt
Presence: [0..1]
Definition: Total amount of money as result of the calculation of the tax.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
4.62.8 Date
XML Tag: Dt
Presence: [0..1]
4.62.9 SequenceNumber
XML Tag: SeqNb
Presence: [0..1]
Definition: Sequential number of the tax report.
Datatype: "Number" on page 166
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
SequenceNumber) will be ignored by the Receiver.
4.62.10 Record
XML Tag: Rcrd
Presence: [0..*]
Definition: Record of tax details.
The Rcrd block contains the following elements (see datatype "TaxRecord1" on page 125 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.63 TaxParty1
Definition: Details about the entity involved in the tax paid or to be paid.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Creditor" on page 119
4.63.1 TaxIdentification
XML Tag: TaxId
Presence: [0..1]
Definition: Tax identification number of the creditor.
Datatype: "Max35Text" on page 164
4.63.2 RegistrationIdentification
XML Tag: RegnId
Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Creditor/RegistrationIdentification) will be ignored by the Receiver.
4.63.3 TaxType
XML Tag: TaxTp
Presence: [0..1]
Definition: Type of tax payer.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Creditor/TaxType) will be ignored by the Receiver.
4.64 TaxParty2
Definition: Details about the entity involved in the tax paid or to be paid.
Used in element(s)
"Debtor" on page 119
4.64.1 TaxIdentification
XML Tag: TaxId
Presence: [0..1]
Definition: Tax identification number of the debtor.
Datatype: "Max35Text" on page 164
4.64.2 RegistrationIdentification
XML Tag: RegnId
Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Debtor/RegistrationIdentification) will be ignored by the Receiver.
4.64.3 TaxType
XML Tag: TaxTp
Presence: [0..1]
Definition: Type of tax payer.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Debtor/TaxType) will be ignored by the Receiver.
4.64.4 Authorisation
XML Tag: Authstn
Presence: [0..1]
Definition: Details of the authorised tax paying party.
The Authstn block contains the following elements (see datatype "TaxAuthorisation1" on page 118
for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.65 TaxPeriod1
Definition: Period of time details related to the tax payment.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all TaxPeriod1 blocks have this element removed and/or ignored. Please refer to
the page number next to the element for further details on which elements have been removed and/or
ignored.
.
Used in element(s)
"Period" on page 129, "Period" on page 127
4.65.1 Year
XML Tag: Yr
Presence: [0..1]
Definition: Year related to the tax payment.
Datatype: "ISODate" on page 159
4.65.2 Type
XML Tag: Tp
Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: "TaxRecordPeriod1Code" on page 172
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/Period/Type) will be ignored by the Receiver.
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/TaxAmount/Details/Period/Type) will be ignored by the Receiver.
4.65.3 FromToDate
XML Tag: FrToDt
Presence: [0..1]
Definition: Range of time between a start date and an end date for which the tax report is provided.
The FrToDt block contains the following elements (see datatype "DatePeriodDetails" on page 48 for
details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/TaxAmount/Details/Period/FromToDate) will be ignored by the Receiver.
4.66 TaxRecord1
Definition: Set of elements used to define the tax record.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Record" on page 121
4.66.1 Type
XML Tag: Tp
Presence: [0..1]
Definition: High level code to identify the type of tax details.
Datatype: "Max35Text" on page 164
4.66.2 Category
XML Tag: Ctgy
Presence: [0..1]
Definition: Specifies the tax code as published by the tax authority.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/Category) will be ignored by the Receiver.
4.66.3 CategoryDetails
XML Tag: CtgyDtls
Presence: [0..1]
Definition: Provides further details of the category tax code.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/CategoryDetails) will be ignored by the Receiver.
4.66.4 DebtorStatus
XML Tag: DbtrSts
Presence: [0..1]
Definition: Code provided by local authority to identify the status of the party that has drawn up the set-
tlement document.
Datatype: "Max35Text" on page 164
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/DebtorStatus) will be ignored by the Receiver.
4.66.5 CertificateIdentification
XML Tag: CertId
Presence: [0..1]
Definition: Identification number of the tax report as assigned by the taxing authority.
Datatype: "Max35Text" on page 164
4.66.6 FormsCode
XML Tag: FrmsCd
Presence: [0..1]
Definition: Identifies, in a coded form, on which template the tax report is to be provided.
Datatype: "Max35Text" on page 164
4.66.7 Period
XML Tag: Prd
Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
The Prd block contains the following elements (see datatype "TaxPeriod1" on page 124 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.66.8 TaxAmount
XML Tag: TaxAmt
Presence: [0..1]
Definition: Set of elements used to provide information on the amount of the tax record.
The TaxAmt block contains the following elements (see datatype "TaxAmount1" on page 116 for de-
tails)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
4.66.9 AdditionalInformation
XML Tag: AddtlInf
Presence: [0..1]
Definition: Further details of the tax record.
Datatype: "Max140Text" on page 162
4.67 TaxRecordDetails1
Definition: Provides information on the individual tax amount(s) per period of the tax record.
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
Used in element(s)
"Details" on page 117
4.67.1 Period
XML Tag: Prd
Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
The Prd block contains the following elements (see datatype "TaxPeriod1" on page 124 for details)
Removed - Partial Removed - Ignored - Partial Ignored - ! Details below -
Mandatory - R[x..x] Repeatability[details]
, >> Note as not all Prd blocks have this element removed and/or ignored. Please refer to the
page number next to the element for further details on which elements have been removed and/or ig-
nored.
.
4.67.2 Amount
XML Tag: Amt
Presence: [1..1]
Definition: Underlying tax amount related to the specified period.
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 130
• This element(pain.001.001.03/PaymentInformation/CreditTransferTransactionInformation/Tax/
Record/TaxAmount/Details/Amount) will be ignored by the Receiver.
5 Message Datatypes
Note The following chapter identifies the datatypes that are used in the message.
5.1 ActiveOrHistoricCurrencyAndAmount
Definition: A number of monetary units specified in an active or a historic currency where the unit of cur-
rency is explicit and compliant with ISO 4217.
Type: Amount
This data type must be used with the following XML Attributes:
Format
fractionDigits 5
minInclusive 0
totalDigits 18
Rules
R7 CurrencyAmount ✓
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
Used in element(s)
"Amount" on page 49, "Amount" on page 129, "Amount" on page 50, "Amount" on page 113, "Credit-
NoteAmount" on page 106, "DiscountAppliedAmount" on page 106, "DuePayableAmount" on page 106,
"RemittedAmount" on page 107, "TaxAmount" on page 106, "TaxableBaseAmount" on page 117, "Tota-
lAmount" on page 117, "TotalTaxAmount" on page 120, "TotalTaxableBaseAmount" on page 120
5.2 ActiveOrHistoricCurrencyAnd-
Amount_11_characters
Definition: A number of monetary units specified in an active or a historic currency where the unit of cur-
rency is explicit and compliant with ISO 4217.
This datatype has been created by the Publisher of this Usage Guideline.
Type: Amount
This data type must be used with the following XML Attributes:
Format
minInclusive 0
totalDigits 11
Rules
R1 CurrencyAmount ✓
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
5.3 ActiveOrHistoricCurrencyAnd-
Amount_11_characters
Definition: A number of monetary units specified in an active or a historic currency where the unit of cur-
rency is explicit and compliant with ISO 4217.
Type: Amount
This data type must be used with the following XML Attributes:
• on pain.001.001.03/PaymentIn-
formation/CreditTransferTrans-
actionInformation/Amount/In-
structedAmount/Currency
Single value: AED
Format
minInclusive 0
totalDigits 11
Rules
R26 CurrencyAmount ✓
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.
Used in element(s)
"InstructedAmount" on page 10
5.4 ActiveOrHistoricCurrencyCode
Definition: A code allocated to a currency by a Maintenance Agency under an international identification
scheme, as described in the latest edition of the international standard ISO 4217 "Codes for the repre-
sentation of currencies and funds".
Type: CodeSet
Format
pattern [A-Z]{3,3}
Rules
R2 ActiveOrHistoricCurrency ✓
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) con-
tiguous letters, and may be or not be withdrawn on the day the message containing the Curren-
cy is exchanged.
Error handling:
Used in element(s)
"Currency" on page 18, "CurrencyOfTransfer" on page 50
Used in attribute(s)
"ActiveOrHistoricCurrencyAndAmount_11_characters" on page 130, "ActiveOrHistoricCurrencyAn-
dAmount" on page 130, "ActiveOrHistoricCurrencyAndAmount_11_characters" on page 131
Restricts
"ParentCurrencyCode" on page 166
5.5 AddressType2Code
Definition: Specifies the type of address.
Type: CodeSet
Used in element(s)
"AddressType" on page 97
Restricts
"AddressTypeCode" on page 133
5.6 AddressTypeCode
Definition: Specifies the type of address.
Type: CodeSet
Is restricted by
"AddressType2Code" on page 133
5.7 AmountDirectionCode
Definition: Specifies if an operation is an increase or a decrease or the result of a reversal operation.
Type: CodeSet
Is restricted by
"CreditDebitCode" on page 147
5.8 AnyBICIdentifier
Definition: Code allocated to a financial or non-financial institution by the ISO 9362 Registration Author-
ity, as described in ISO 9362 "Banking - Banking telecommunication messages - Business identifier
code (BIC)".
Type: IdentifierSet
Format
pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}
Rules
R5 AnyBIC ✓
Only a valid Business identifier code is allowed. Business identifier codes for financial or non-
financial institutions are registered by the ISO 9362 Registration Authority in the BIC directory,
and consists of eight (8) or eleven (11) contiguous characters.
Error handling:
Used in element(s)
"BICOrBEI" on page 70
5.9 Authorisation1Code
134 HSBC_pain.001.001.03_LowValuePayment_United Arab Emirates - HSBC_pain.001.001.03_LowValuePaymen-
t_MiddleEast
Message Datatypes
Definition: Specifies the level of approval depending on a number of factors, including payment type,
threshold amount or local country or operations practice.
Type: CodeSet
• This code(pain.001.001.03/Group-
Header/Authorisation/Code/In-
structionLevelAuthorisation) is re-
moved.
Used in element(s)
"Code" on page 11
Restricts
"AuthorisationCode" on page 135
5.10 AuthorisationCode
Definition: Specifies the level of approval depending on a number of factors, including payment type,
threshold amount or local country or operations practice.
Type: CodeSet
Is restricted by
"Authorisation1Code" on page 134
5.11 BICIdentifier
Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as described
in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
Type: IdentifierSet
Format
pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}
Rules
R6 BIC ✓
Valid BICs for financial institutions are registered by the ISO 9362 Registration Authority in the
BIC directory, and consist of eight (8) or eleven (11) contiguous characters.
Error handling:
Used in element(s)
"BIC" on page 52, "BIC" on page 55
5.12 BaseOneRate
Definition: Rate expressed as a decimal, for example, 0.7 is 7/10 and 70%.
Type: Rate
Format
fractionDigits 10
totalDigits 11
Used in element(s)
"ExchangeRate" on page 51
5.13 BatchBookingIndicator
Definition: Identifies whether the sending party requests a single debit or credit entry per individual
transaction or a batch entry for the sum of the amounts of all transactions.
Type: Indicator
Meaning When True: Identifies that a batch entry for the sum of the amounts of all transactions in the
batch or message is requested.
Meaning When False: Identifies that a single entry for each of the transactions in the batch or message
is requested.
Used in element(s)
"BatchBooking" on page 85
5.14 CashAccountType4Code
Definition: Specifies the nature, or use, of the cash account.
Type: CodeSet
• This code(pain.001.001.03/Pay-
mentInformation/CreditTransfer-
TransactionInformation/Credi-
torAccount/Type/xor/Code/Cash-
Payment) will be ignored by the
Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/CashPayment) will be ig-
nored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Charges) will be ignored
by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/CashIncome)
will be ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/CashIncome) will be ig-
nored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/Commission)
will be ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Commission) will be ig-
nored by the Receiver.
• This code(pain.001.001.03/Pay-
mentInformation/CreditTransfer-
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/MarginalLending) will be
ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/MoneyMar-
ket) will be ignored by the Receiv-
er.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/MoneyMarket) will be ig-
nored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/NonResiden-
tExternal) will be ignored by the
Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/NonResidentExternal)
will be ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Overdraft) will be ignored
by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/Settlement)
will be ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Settlement) will be ig-
nored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/Salary) will
be ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Salary) will be ignored by
the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/CreditorAc-
count/Type/xor/Code/Tax) will be
ignored by the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/Tax) will be ignored by
the Receiver.
• This code(pain.001.001.03/Paymen-
tInformation/DebtorAccount/Type/
xor/Code/CashTrading) will be ig-
nored by the Receiver.
Used in element(s)
"Code" on page 19
Restricts
"CashAccountTypeCode" on page 141
5.15 CashAccountTypeCode
Definition: Specifies the nature, or use, of the cash account.
Type: CodeSet
Is restricted by
"CashAccountType4Code" on page 137
5.16 ChargeBearerType1Code
Definition: Specifies which party(ies) will pay charges due for processing of the instruction.
Type: CodeSet
Used in element(s)
"ChargeBearer" on page 89, "ChargeBearer" on page 34
Restricts
"ChargeBearerTypeCode" on page 143
5.17 ChargeBearerTypeCode
Definition: Specifies which party(ies) will pay charges due for processing of the instruction.
Type: CodeSet
Is restricted by
"ChargeBearerType1Code" on page 142
5.18 ChequeDelivery1Code
Definition: Specifies the method to be used in delivering a cheque to a party.
Type: CodeSet
Used in element(s)
"Code" on page 24
Restricts
"ChequeDeliveryCode" on page 144
5.19 ChequeDeliveryCode
Definition: Specifies the method to be used in delivering a cheque to a party.
Type: CodeSet
Is restricted by
"ChequeDelivery1Code" on page 143
5.20 ChequeType2Code
Definition: Specifies the type of cheque.
Type: CodeSet
Used in element(s)
"ChequeType" on page 22
Restricts
"ChequeTypeCode" on page 146
5.21 ChequeTypeCode
Definition: Specifies the type of cheque.
Type: CodeSet
Is restricted by
"ChequeType2Code" on page 145
5.22 CountryCode
Definition: Code to identify a country, a dependency, or another area of particular geopolitical interest,
on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
Type: CodeSet
Format
pattern [A-Z]{2,2}
Rules
R3 Country ✓
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).
Error handling:
Used in element(s)
"Country" on page 99, "Country" on page 104, "Country" on page 112, "CountryOfBirth" on page 48,
"CountryOfResidence" on page 75, "CountryOfResidence" on page 79
5.23 CreditDebitCode
Definition: Specifies if an operation is an increase or a decrease.
Type: CodeSet
Used in element(s)
"CreditDebitIndicator" on page 49
Restricts
"AmountDirectionCode" on page 134
5.24 DecimalNumber
Definition: Number of objects represented as a decimal number, for example 0.75 or 45.6.
Type: Quantity
Format
fractionDigits 17
totalDigits 18
Used in element(s)
"ControlSum" on page 65, "ControlSum" on page 86
5.25 DocumentType3Code
Definition: Specifies a type of financial or commercial document.
Type: CodeSet
Used in element(s)
"Code" on page 45
Restricts
"DocumentTypeCode" on page 150
5.26 DocumentType5Code
Definition: Specifies a type of financial or commercial document.
Type: CodeSet
Used in element(s)
"Code" on page 102
Restricts
"DocumentTypeCode" on page 150
5.27 DocumentTypeCode
Definition: Specifies a type of financial or commercial document.
Type: CodeSet
Is restricted by
"DocumentType3Code" on page 148, "DocumentType5Code" on page 149
5.28 ExchangeRateType1Code
Definition: Specifies a type of financial or commercial document.
Type: CodeSet
Used in element(s)
"RateType" on page 51
Restricts
"ExchangeRateTypeCode" on page 151
5.29 ExchangeRateTypeCode
Definition: Code used to define the type of the currency exchange.
Type: CodeSet
Is restricted by
"ExchangeRateType1Code" on page 151
5.30 ExternalAccountIdentification1Code
Definition: Specifies the external account identification scheme name code in the format of character
string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 9
Restricts
"ExternalAccountIdentificationCode" on page 152
5.31 ExternalAccountIdentificationCode
Definition: Specifies the external account identification scheme name code in the format of character
string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalAccountIdentification1Code" on page 152
5.32 ExternalCategoryPurpose1Code
Definition: Specifies the category purpose, as published in an external category purpose code list.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 20
Restricts
"ExternalCategoryPurposeCode" on page 153
5.33 ExternalCategoryPurposeCode
Definition: Specifies the category purpose, as published in an external category purpose code list.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalCategoryPurpose1Code" on page 152
5.34 ExternalClearingSystemIdentification1Code
Definition: Specifies the clearing system identification code, as published in an external clearing system
identification code list.
Format
maxLength 5
minLength 1
Used in element(s)
"Code" on page 25
Restricts
"ExternalClearingSystemIdentificationCode" on page 154
5.35 ExternalClearingSystemIdentificationCode
Definition: Specifies the clearing system identification code, as published in an external clearing system
identification code list.
Format
maxLength 5
minLength 1
Is restricted by
"ExternalClearingSystemIdentification1Code" on page 153
5.36 ExternalFinancialInstitutionIdentification1Code
Definition: Specifies the external financial institution identification scheme name code in the format of
character string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 51
Restricts
"ExternalFinancialInstitutionIdentificationCode" on page 154
5.37 ExternalFinancialInstitutionIdentificationCode
Definition: Specifies the external financial institution identification scheme name code in the format of
character string with a maximum length of 4 characters.
Type: CodeSet
Format
maxLength 4
minLength 1
Is restricted by
"ExternalFinancialInstitutionIdentification1Code" on page 154
5.38 ExternalLocalInstrument1Code
Definition: Specifies the external local instrument code in the format of character string with a maximum
length of 35 characters.
Format
maxLength 35
minLength 1
Used in element(s)
"Code" on page 67
Restricts
"ExternalLocalInstrumentCode" on page 155
5.39 ExternalLocalInstrumentCode
Definition: Specifies the external local instrument code in the format of character string with a maximum
length of 35 characters.
Format
maxLength 35
minLength 1
Is restricted by
"ExternalLocalInstrument1Code" on page 155
5.40 ExternalOrganisationIdentification1Code
Definition: Specifies the external organisation identification scheme name code in the format of charac-
ter string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 71
Restricts
"ExternalOrganisationIdentificationCode" on page 156
5.41 ExternalOrganisationIdentificationCode
Definition: Specifies the external organisation identification scheme name code in the format of charac-
ter string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalOrganisationIdentification1Code" on page 156
5.42 ExternalPersonIdentification1Code
Definition: Specifies the external person identification scheme name code in the format of character
string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 95
Restricts
"ExternalPersonIdentificationCode" on page 157
5.43 ExternalPersonIdentificationCode
Definition: Specifies the external person identification scheme name code in the format of character
string with a maximum length of 4 characters.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalPersonIdentification1Code" on page 156
5.44 ExternalPurpose1Code
Definition: Specifies the external purpose code in the format of character string with a maximum length
of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 100
Restricts
"ExternalPurposeCode" on page 158
5.45 ExternalPurposeCode
Definition: Specifies the external purpose code in the format of character string with a maximum length
of 4 characters.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalPurpose1Code" on page 157
5.46 ExternalServiceLevel1Code
Definition: Specifies the external service level code in the format of character string with a maximum
length of 4 characters.
Format
maxLength 4
minLength 1
Used in element(s)
"Code" on page 110
Restricts
"ExternalServiceLevelCode" on page 158
5.47 ExternalServiceLevelCode
Definition: Specifies the nature, or use, of the amount in the format of character string with a maximum
length of 4 characters.
Format
maxLength 4
minLength 1
Is restricted by
"ExternalServiceLevel1Code" on page 158
5.48 IBAN2007Identifier
Definition: The International Bank Account Number is a code used internationally by financial institu-
tions to uniquely identify the account of a customer at a financial institution as described in the 2007
edition of the ISO 13616 standard "Banking and related financial services - International Bank Account
Number (IBAN)" and replaced by the more recent edition of the standard.
Type: IdentifierSet
Format
pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}
Rules
R4 IBAN ✓
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.
Error handling:
Used in element(s)
"IBAN" on page 8
5.49 ISODate
Definition: A particular point in the progression of time in a calendar year expressed in the YYYY-MM-
DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3C
Recommendation 28 October 2004" which is aligned with ISO 8601.
Type: Date
Used in element(s)
"BirthDate" on page 47, "ChequeMaturityDate" on page 23, "Date" on page 120, "Date" on page 112,
"FromDate" on page 48, "PoolingAdjustmentDate" on page 87, "RelatedDate" on page 101, "Request-
edExecutionDate" on page 86, "ToDate" on page 48, "Year" on page 124
5.50 ISODateTime
Definition: A particular point in the progression of time defined by a mandatory date and a mandatory
time component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ), local time with
UTC offset format (YYYY-MM-DDThh:mm:ss.sss+/-hh:mm), or local time format (YYYY-MM-DDThh:m-
m:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second Edition - W3C
Recommendation 28 October 2004" which is aligned with ISO 8601.
Decimal fractions of seconds may be included. In this case, the involved parties shall agree on the max-
imum number of digits that are allowed.
Type: DateTime
Used in element(s)
"CreationDateTime" on page 64
5.51 Instruction3Code
Definition: Specifies further instructions concerning the processing of a payment instruction, provided by
the sending clearing agent to the next agent(s).
Type: CodeSet
Used in element(s)
"Code" on page 67
Restricts
"InstructionCode" on page 161
5.52 InstructionCode
Definition: Specifies further instructions concerning the processing of a payment instruction.
Type: CodeSet
Is restricted by
"Instruction3Code" on page 160
5.53 Max128Text
Definition: Specifies a character string with a maximum length of 128 characters.
Type: Text
Format
maxLength 128
minLength 1
Used in element(s)
"Proprietary" on page 11
5.54 Max12Text
16 February 2022 161
Usage Guideline
Format
maxLength 12
minLength 1
Used in element(s)
"InstructionIdentification" on page 80
5.55 Max140Text
Definition: Specifies a character string with a maximum length of 140 characters.
Type: Text
Format
maxLength 140
minLength 1
Used in element(s)
"AdditionalInformation" on page 49, "AdditionalInformation" on page 128, "AdditionalRemittanceInfor-
mation" on page 116, "InstructionForDebtorAgent" on page 41, "InstructionInformation" on page 67,
"Name" on page 15, "Name" on page 29, "Name" on page 73, "Name" on page 53, "Name" on page 68,
"Name" on page 118, "Name" on page 104, "Name" on page 56, "ReferenceNumber" on page 120,
"Unstructured" on page 108
5.56 Max15NumericText
Definition: Specifies a numeric string with a maximum length of 15 digits.
Type: Text
Format
pattern [0-9]{1,15}
Used in element(s)
"NumberOfTransactions" on page 65, "NumberOfTransactions" on page 86
5.57 Max16Text
Definition: Specifies a character string with a maximum length of 16 characters.
Type: Text
Format
maxLength 16
minLength 1
Used in element(s)
"BuildingNumber" on page 98, "EndToEndIdentification" on page 81, "PostCode" on page 98
5.58 Max2048Text
Definition: Specifies a character string with a maximum length of 2048 characters.
Type: Text
Format
maxLength 2048
minLength 1
Used in element(s)
"EmailAddress" on page 29, "RemittanceLocationElectronicAddress" on page 109
5.59 Max24Text
Definition:
This datatype has been created by the Publisher of this Usage Guideline.
Type: Text
Format
maxLength 24
minLength 1
Used in element(s)
"PaymentInformationIdentification" on page 85
5.60 Max34Text
Definition: Specifies a character string with a maximum length of 34 characters.
Type: Text
Format
maxLength 34
minLength 1
Used in element(s)
"Identification" on page 59
5.61 Max35Text
Definition: Specifies a character string with a maximum length of 35 characters.
Type: Text
Format
maxLength 35
minLength 1
Used in element(s)
"AdministrationZone" on page 120, "Category" on page 126, "CategoryDetails" on page 126, "Certifi-
cateIdentification" on page 127, "ChequeNumber" on page 22, "CityOfBirth" on page 47, "ContractIden-
tification" on page 51, "CountrySubDivision" on page 99, "DebtorStatus" on page 127, "FormsCode"
on page 127, "FormsCode" on page 23, "Identification" on page 60, "Identification" on page 15, "Iden-
tification" on page 61, "Identification" on page 63, "Information" on page 113, "Issuer" on page 61, "Is-
suer" on page 59, "Issuer" on page 62, "Issuer" on page 63, "Issuer" on page 103, "Issuer" on page 46,
"MemberIdentification" on page 26, "MemoField" on page 24, "MessageIdentification" on page 64,
"Method" on page 120, "Name" on page 77, "Number" on page 101, "Other" on page 29, "PrintLoca-
tion" on page 24, "Proprietary" on page 25, "Proprietary" on page 52, "Proprietary" on page 9, "Propri-
etary" on page 20, "Proprietary" on page 71, "Proprietary" on page 96, "Proprietary" on page 100, "Pro-
prietary" on page 102, "Proprietary" on page 46, "Proprietary" on page 25, "Proprietary" on page 111,
"Proprietary" on page 67, "Proprietary" on page 21, "ProvinceOfBirth" on page 47, "Reference" on
page 45, "RegionalClearingZone" on page 24, "RegistrationIdentification" on page 122, "RegistrationI-
dentification" on page 123, "RemittanceIdentification" on page 109, "TaxIdentification" on page 122,
"TaxIdentification" on page 123, "TaxType" on page 122, "TaxType" on page 123, "Title" on page 118,
"TownName" on page 99, "Type" on page 126, "Type" on page 111
5.62 Max3Text
Definition: Specifies a character string with a maximum length of 3 characters.
Type: Text
Format
maxLength 3
minLength 1
Used in element(s)
"Code" on page 112
5.63 Max4Text
Definition: Specifies a character string with a maximum length of 4 characters.
Type: Text
Format
maxLength 4
minLength 1
Used in element(s)
"Reason" on page 49
5.64 Max70Text
Definition: Specifies a character string with a maximum length of 70characters.
Type: Text
Format
maxLength 70
minLength 1
Used in element(s)
"AddressLine" on page 99, "Department" on page 98, "Name" on page 19, "StreetName" on page 98,
"SubDepartment" on page 98
5.65 Max9NumericText
Definition: Specifies a numeric string with a maximum length of 9 digits.
Type: Text
Format
pattern [0-9]{1,9}
Used in element(s)
"MemberIdentification" on page 27
5.66 NamePrefix1Code
Definition: Specifies the terms used to formally address a person.
Type: CodeSet
Used in element(s)
"NamePrefix" on page 28
Restricts
"NamePrefixCode" on page 166
5.67 NamePrefixCode
Definition: Specifies the terms used to formally address a person.
Type: CodeSet
Is restricted by
"NamePrefix1Code" on page 165
5.68 Number
Definition: Number of objects represented as an integer.
Type: Quantity
Format
fractionDigits 0
totalDigits 18
Used in element(s)
"SequenceNumber" on page 121
5.69 ParentCurrencyCode
Definition: Code allocated to a currency, by a maintenance agency, under an international identification
scheme as described in the latest edition of the international standard ISO 4217 "Codes for the repre-
sentation of currencies and funds". Valid currency codes are registered with the ISO 4217 Maintenance
Agency, and consist of three contiguous letters.
Type: CodeSet
Format
pattern [A-Z]{3,3}
Is restricted by
"ActiveOrHistoricCurrencyCode" on page 132
5.70 PaymentMethod3Code
Definition: Specifies the transfer method that will be used to transfer an amount of money.
Type: CodeSet
• This code(pain.001.001.03/Pay-
mentInformation/Payment-
Method/Cheque) is removed.
Used in element(s)
"PaymentMethod" on page 85
Restricts
"PaymentMethodCode" on page 167
5.71 PaymentMethodCode
Definition: Specifies the transfer method that will be used to transfer the cash.
Type: CodeSet
Is restricted by
"PaymentMethod3Code" on page 167
5.72 PercentageRate
Definition: Rate expressed as a percentage, that is, in hundredths, for example, 0.7 is 7/10 of a percent,
and 7.0 is 7%.
Type: Rate
Format
fractionDigits 10
totalDigits 11
Used in element(s)
"Rate" on page 117
5.73 PhoneNumber
Definition: The collection of information which identifies a specific phone or FAX number as defined by
telecom services.
It consists of a "+" followed by the country code (from 1 to 3 characters) then a "-" and finally, any com-
bination of numbers, "(", ")", "+" and "-" (up to 30 characters).
Type: Text
Format
pattern \+[0-9]{1,3}-[0-9()+\-]{1,30}
Used in element(s)
"FaxNumber" on page 29, "MobileNumber" on page 29, "PhoneNumber" on page 29
5.74 Priority2Code
Definition: Specifies the priority level of an event.
Type: CodeSet
Used in element(s)
"InstructionPriority" on page 92, "InstructionPriority" on page 23
Restricts
"PriorityCode" on page 169
5.75 PriorityCode
Definition: Specifies the priority level of an event.
Type: CodeSet
Is restricted by
"Priority2Code" on page 168
5.76 RegulatoryReportingType1Code
Definition: Identifies whether the regulatory reporting information applies to the debit side, to the credit
side or to both debit and credit sides of the transaction.
Type: CodeSet
Used in element(s)
"DebitCreditReportingIndicator" on page 104
Restricts
"RegulatoryReportingTypeCode" on page 169
5.77 RegulatoryReportingTypeCode
Definition: Identifies whether the regulatory reporting information applies to the debit side, to the credit
side or to both debit and credit sides of the transaction.
Type: CodeSet
Is restricted by
"RegulatoryReportingType1Code" on page 169
5.78 RemittanceLocationMethod2Code
Definition: Specifies the method used to deliver the remittance advice information.
Type: CodeSet
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/RelatedRemit-
tanceInformation/RemittanceLo-
cationMethod/ElectronicDataInter-
change) will be ignored by the Re-
ceiver.
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/RelatedRemit-
tanceInformation/RemittanceLoca-
• This code(pain.001.001.03/Paymen-
tInformation/CreditTransferTrans-
actionInformation/RelatedRemit-
tanceInformation/RemittanceLoca-
tionMethod/UniformResourceIden-
tifier) will be ignored by the Receiv-
er.
Used in element(s)
"RemittanceLocationMethod" on page 109
Restricts
"RemittanceLocationMethodCode" on page 171
5.79 RemittanceLocationMethodCode
Definition: Specifies the method used to deliver the remittance advice information.
Type: CodeSet
Is restricted by
"RemittanceLocationMethod2Code" on page 170
5.80 TaxRecordPeriod1Code
Definition: Specifies the period related to the tax payment.
Type: CodeSet
Used in element(s)
"Type" on page 124
Restricts
"TaxRecordPeriodCode" on page 173
5.81 TaxRecordPeriodCode
Definition: Specifies the period related to the tax payment.
Type: CodeSet
Is restricted by
"TaxRecordPeriod1Code" on page 172
Legal Notices
Copyright
SWIFT © 2022. All rights reserved.
This material is a component of MyStandards, the SWIFT collaborative Web application used to man-
age standards definitions and industry usage. It can only be used and distributed in accordance with
MyStandards Terms of Use.
Unless otherwise agreed in writing with SWIFT SCRL, you have no right to:
- authorise external end users to use this component for other purposes than their internal use.
- remove, alter, cover, obfuscate or cancel from view any copyright or other proprietary rights notices
appearing in this physical medium.
- re-sell or authorise another party e.g. software and service providers, to re-sell this component.
Confidentiality
This publication may contain SWIFT or third-party confidential information. Only disclose it outside your
organisation in accordance with MyStandards Terms of Use and your related license rights.
This component is provided 'AS IS'. SWIFT does not give and excludes any express or implied war-
ranties with respect to this component such as but not limited to any guarantee as to its quality, supply
or availability.
Any and all rights, including title, ownership rights, copyright, trademark, patents, and any other intellec-
tual property rights of whatever nature in this component will remain the exclusive property of SWIFT or
its licensors.