ferV08 pacs.009.001 - Payments Canada · Message Functionality Message Functionality This Usage Guideline is based on the pacs.009.001.08 message definition. In addition, Payments

Usage Guideline

Lynx_FinancialInstitutionCreditTrans-ferV08_pacs.009.001.08

Lynx_FINAL_Phase2Messages_SR2019

This document describes a usage guideline restricting the base message MX pacs.009.001.08. You can also consult thisinformation online.

Published by Payments Canada and generated by MyStandards.

31 May 2020

https://www2.swift.com/mystandards/#/mp/mx/_Lpf7IGUsEeq2d4fdbL-V4w/version/11/_O9Z76GUsEeq2d4fdbL-V4w

https://www2.swift.com/mystandards/#/mp/mx/_Lpf7IGUsEeq2d4fdbL-V4w/version/11/_O9Z76GUsEeq2d4fdbL-V4w

http://www.swift.com/mystandards

Usage Guideline

Table of Contents

.Message Functionality ................................................................................................................................................. 3

1 Restriction summary ......................................................................................................................................... 4

2 Structure ................................................................................................................................................................. 6

3 Rules ....................................................................................................................................................................... 10

4 Message Building Blocks ............................................................................................................................. 12

5 Message Components .................................................................................................................................... 22

6 Message Datatypes ........................................................................................................................................ 240

.Legal Notices ............................................................................................................................................................... 286

2 Lynx_FinancialInstitutionCreditTransferV08_pacs.009.001.08 - Lynx_FINAL_Phase2Messages_SR2019

Message Functionality

Message Functionality

This Usage Guideline is based on the pacs.009.001.08 message definition. In addition, PaymentsCanada has defined usage of BusinessApplicationHeaderV02 as mandatory . The following section willbe dealing with the pacs.009.001.08 only.

Overview

Lynx Documentation Description:

This document outlines the specifications for the Lynx ISO 20022 Financial Institu-tion Credit Transfer (single financial institution credit transfer) message, cleared and settled via Payments Canada's Lynx system, that will be implemented in Novem-ber 2021 (Phase 2) (this date is now subject to Member review based on the SWIFT an-nouncement to delay their ISO 20022 migration till the end of November 2022). Prior to reading this Lynx ISO 20022 Message Specification, it is highly recommended to read the Lynx ISO 20022 Message Specification Companion Document that is published as alongside it since the Companion provides high-level context and an overview of the message portfolio and content.

ISO 20022 Documentation Description:

Scope:The FinancialInstitutionCreditTransfer message is sent by a debtor financial institu-tion to a creditor financial institution, directly or through other agents and/or a payment clearing and settlement system.It is used to move funds from a debtor account to a creditor, where both debtor and creditor are financial institutions.

Usage:The FinancialInstitutionCreditTransfer message is exchanged between agents and can contain one or more credit transfer instructions where debtor and creditor are both financial institutions.The FinancialInstitutionCreditTransfer message does not allow for grouping: a Credit-TransferTransactionInformation block must be present for each credit transfer trans-action.The FinancialInstitutionCreditTransfer message can be used in domestic and cross-bor-der scenarios.

Usage Guideline Description

Descriptive Text for all Messages in the Lynx Phase 2 Portfolio:

Messages to be implemented in Lynx Phase 2 in November 2021 (this date is now subject to Memberreview based on the SWIFT announcement to delay their ISO 20022 migration till the end of November2022).

Outline

The Lynx_FINAL_Phase2Messages_SR2019 / Lynx_FinancialInstitutionCreditTransferV08_pac-s.009.001.08 message is composed of 3 building blocks

a. GroupHeader

Set of characteristics shared by all individual transactions included in the message.

b. CreditTransferTransactionInformation

Set of elements providing information specific to the individual credit transfer(s).

c. SupplementaryData

Additional information that cannot be captured in the structured elements and/or any other specificblock.

31 May 2020 3

Usage Guideline

1 Restriction summaryThis Usage Guideline restricts the pacs.009.001.08 message. This also includes the BusinessApplica-tionHeaderV02.

Restriction Type See page

Removed elements 11, 12, 16, 17, 21, 30, 30, 30, 30,30, 30, 30, 30, 30, 30, 30, 30, 30,30, 31, 31, 31, 31, 31, 31, 31, 31,33, 33, 33, 34, 34, 35, 35, 35, 40,49, 49, 49, 49, 49, 49, 49, 49, 49,49, 49, 49, 49, 49, 50, 50, 50, 50,50, 50, 50, 50, 50, 50, 50, 51, 79,85, 89, 109, 133, 133, 133, 133, 133, 133,134, 134, 134, 134, 134, 134, 134, 134, 134,134, 134, 134, 134, 134, 134, 134, 134, 137,142, 143, 143, 143, 148, 149, 149, 149, 150,151, 151, 152, 154, 155, 156, 161, 161, 161,161, 165, 165, 166, 166, 166, 166, 169, 169,175, 182, 182, 182, 182, 182, 182, 182, 182,182, 182, 182, 183, 183, 183, 184, 184, 186,186, 187, 187, 187, 187, 187, 187, 187, 187,187, 189, 189, 189, 189, 189, 189, 189, 189,189, 189, 189, 189, 189, 190, 190, 190, 190,190, 190, 190, 190, 190, 190, 190, 190, 190,209, 209, 210, 210, 210, 211, 211, 211, 212,213, 214, 214, 215, 215, 216, 281, 281, 281

Make mandatory 53, 53, 53, 53, 53, 53, 53, 53, 53,53, 54, 54, 54, 54, 54, 54, 54, 54,54, 54, 54, 54, 55, 59, 68, 68, 73,74, 124, 124, 170, 172, 176, 185, 185, 185,185, 185, 185, 185, 185, 186, 186, 186, 186,186, 186, 187, 187, 187, 212

Reduce Multiplicity 18, 21, 85, 86, 108, 109, 157, 157, 157,157, 158, 158, 158, 158, 158, 176, 179, 179,179, 179, 179, 179, 179, 179, 179, 193, 193,193, 193, 193, 193, 193, 193, 193, 193, 194,194, 194, 194, 194, 194, 194, 194, 194, 194,194, 194, 194, 195, 195, 195, 205, 207

Ignore 69, 173, 217, 217, 217

Text rules 13, 13, 14, 14, 15, 16, 36, 37, 37,38, 38, 70, 70, 71, 72, 74, 75, 76,77, 78, 80, 81, 82, 84, 93, 94, 95,96, 97, 99, 100, 101, 102, 103, 104, 106,107, 171, 171, 172, 177, 206

Conditional rules 108, 108, 188, 195

Fixed values 46, 46, 51, 149, 246

Truncates n.a.


Restriction summary

Restriction Type See page

Comments 17, 31, 40, 46, 46, 46, 46, 46, 46,46, 47, 47, 47, 47, 47, 47, 47, 47,47, 48, 48, 48, 48, 48, 48, 55, 55,55, 55, 55, 56, 56, 56, 56, 56, 56,57, 57, 57, 57, 57, 57, 57, 58, 58,58, 58, 58, 60, 69, 74, 75, 86, 87,89, 124, 124, 146, 147, 159, 163, 164, 164,164, 164, 164, 164, 165, 167, 167, 168, 169,171, 172, 173, 176, 177, 177, 180, 184, 207

Annotations n.a.

Changed datatypes n.a.

Extensions n.a.

Synonyms 51, 68, 68, 74, 75, 76, 76, 80, 81,82, 83, 84, 84, 86, 170, 171, 217, 270,270, 270, 271

Other restrictions 26, 26, 27, 27, 27, 27, 27, 27, 27,28, 28, 28, 28, 28, 28, 28, 28, 29,29, 29, 29, 29, 29, 32, 93, 94, 95,95, 106, 106, 107, 110, 126, 126, 127, 127,127, 127, 127, 127, 127, 128, 128, 128, 128,128, 128, 128, 129, 129, 129, 129, 129, 129,129, 130, 130, 130, 130, 130, 130, 130, 131,131, 131, 131, 131, 131, 131, 132, 132, 132,132, 132, 132, 132, 133, 133, 137, 137, 167,168, 168, 168, 171

31 May 2020 5

Usage Guideline

2 Structure


Structure

Removed - Ignored - ! Details below - Mandatory - R[x..x] Repeatability[details]

Index Message Item <XML Tag> Or Mult. UsageGuidelines

Page

BusinessApplicationHeaderV02 <AppHdr> [1..1]

CharacterSet <CharSet> [0..1] 12

From <Fr> [1..1] ! 12

OrganisationIdentification <OrgId> {Or [1..1] ! 161

FinancialInstitutionIdentification <FIId> Or} [1..1] ! 161

To <To> [1..1] ! 13



BusinessMessageIdentifier <BizMsgIdr> [1..1] ! 14

MessageDefinitionIdentifier <MsgDefIdr> [1..1] ! 14

BusinessService <BizSvc> [0..1] ! 14

MarketPractice <MktPrctc> [0..1] ! 15

Registry <Regy> [1..1] 152

Identification <Id> [1..1] 152

CreationDate <CreDt> [1..1] ! 16

BusinessProcessingDate <BizPrcgDt> [0..1] 16

CopyDuplicate <CpyDplct> [0..1] 16

PossibleDuplicate <PssblDplct> [0..1] 16

Priority <Prty> [0..1] ! 17

Signature <Sgntr> [0..1] ! 17

Related <Rltd> [0..*] R[0..1] 17


From <Fr> [1..1] ! 36

To <To> [1..1] ! 36







31 May 2020 7

Usage Guideline


Page



FinancialInstitutionCreditTransferV08 <FICdtTrf> [1..1]

GroupHeader <GrpHdr> [1..1] ! 18

MessageIdentification <MsgId> [1..1] ! 148

CreationDateTime <CreDtTm> [1..1] 148

BatchBooking <BtchBookg> [0..1] 148

NumberOfTransactions <NbOfTxs> [1..1] ! 149

ControlSum <CtrlSum> [0..1] 149

TotalInterbankSettlementAmount <TtlIntrBkSttlmAmt> [0..1] 149

InterbankSettlementDate <IntrBkSttlmDt> [0..1] 149

SettlementInformation <SttlmInf> [1..1] 150

PaymentTypeInformation <PmtTpInf> [0..1] 150

InstructingAgent <InstgAgt> [0..1] 151

InstructedAgent <InstdAgt> [0..1] 151

CreditTransferTransactionInformation <CdtTrfTxInf> [1..*] R[1..1] 19

PaymentIdentification <PmtId> [1..1] 67


InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] ! 68

InterbankSettlementDate <IntrBkSttlmDt> [0..1] ! 68

SettlementPriority <SttlmPrty> [0..1] 68

SettlementTimeIndication <SttlmTmIndctn> [0..1] ! 68

SettlementTimeRequest <SttlmTmReq> [0..1] ! 69

PreviousInstructingAgent1 <PrvsInstgAgt1> [0..1] ! 70

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> [0..1] 70





InstructingAgent <InstgAgt> [0..1] ! 73

InstructedAgent <InstdAgt> [0..1] ! 74


Structure


Page

IntermediaryAgent1 <IntrmyAgt1> [0..1] ! 75

IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] ! 76





UltimateDebtor <UltmtDbtr> [0..1] 79

Debtor <Dbtr> [1..1] ! 79

DebtorAccount <DbtrAcct> [0..1] ! 80

DebtorAgent <DbtrAgt> [0..1] ! 81

DebtorAgentAccount <DbtrAgtAcct> [0..1] ! 81

CreditorAgent <CdtrAgt> [0..1] ! 82

CreditorAgentAccount <CdtrAgtAcct> [0..1] ! 83

Creditor <Cdtr> [1..1] ! 83

CreditorAccount <CdtrAcct> [0..1] ! 84

UltimateCreditor <UltmtCdtr> [0..1] 84

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] R[0..2] 85

InstructionForNextAgent <InstrForNxtAgt> [0..*] ! R[0..4] 85

Purpose <Purp> [0..1] ! 86

RemittanceInformation <RmtInf> [0..1] ! 86

UnderlyingCustomerCreditTransfer <UndrlygCstmrCdtTrf> [0..1] ! 87

SupplementaryData <SplmtryData> [0..*] 89


PlaceAndName <PlcAndNm> [0..1] 222

Envelope <Envlp> [1..1] 222

31 May 2020 9

Usage Guideline

3 RulesR1 RelatedPresentWhenCopyDupl

Related MUST contain the relevant BusinessMessageHeader elements of the BusinessMes-sage to which this BusinessMessage relates.

If CopyDuplicate is present, then Related MUST be present.

Error handling:

– Error severity: Warning

– Error Code: H00001

– Error Text: Element Related is missing

R5 InstructedAgentRule ✓

If GroupHeader/InstructedAgent is present, then CreditTransferTransactionInformation/In-structedAgent is not allowed.

Error handling:

– Error severity: Fatal

– Error Code: X00008

– Error Text: Invalid message content for instructed agent.

R6 InstructingAgentRule ✓

If GroupHeader/InstructingAgent is present, then CreditTransferTransactionInformation/In-structingAgent is not allowed.

Error handling:



– Error Text: Invalid message content for instructing agent.

R7 TotalInterbankSettlementAmountRule ✓

If GroupHeader/TotalInterbankSettlementAmount is present, then all occurrences of Credit-TransferTransactionInformation/InterbankSettlementAmount must have the same currency asthe currency of GroupHeader/TotalInterbankSettlementAmount.

Error handling:



– Error Text: Invalid message content for the total interbank settlement amount and individualinterbank settlement amount currencies.

R8 TotalInterbankSettlementAmountAndSumRule

If GroupHeader/TotalInterbankSettlementAmount is present, then it must equal the sum of alloccurrences of CreditTransferTransactionInformation/InterbankSettlementAmount.


Rules

Error handling:



– Error Text: Invalid message content for the total interbank settlement amount and sum of in-dividual interbank settlement amounts.

R9 GroupHeaderInterbankSettlementDateRule ✓

If GroupHeader/InterbankSettlementDate is present, then CreditTransferTransactionInforma-tion/InterbankSettlementDate is not allowed.

Error handling:



– Error Text: Invalid message content for interbank settlement date.

R10 TransactionInterbankSettlementDateRule ✓

If GroupHeader/InterbankSettlementDate is not present, then CreditTransferTransactionInfor-mation/InterbankSettlementDate must be present.

Error handling:



– Error Text: Invalid message content for interbank settlement date.

R11 PaymentTypeInformationRule ✓

If GroupHeader/PaymentTypeInformation is present, then CreditTransferTransactionInforma-tion/PaymentTypeInformation is not allowed.

Error handling:



– Error Text: Invalid message content for payment type information.

R12 SupplementaryDataRule

The SupplementaryData building block at message level must not be used to provide additionalinformation about a transaction. The SupplementaryData element at transaction level should beused for that purpose.

Error handling: Undefined

Usage Guideline restrictions for this element

– This rule(pacs.009.001.08/SupplementaryDataRule) is removed.

31 May 2020 11

Usage Guideline

4 Message Building Blocks

Note The following chapter identifies the building blocks of the Lynx_FINAL_Phase2Mes-sages_SR2019 / Lynx_FinancialInstitutionCreditTransferV08_pacs.009.001.08 messagedefinition.

4.1 Header Building Blocks

Note The following chapter identifies the building blocks of the BusinessApplicationHeaderV02definition.

4.1.1 CharacterSetXML Tag: CharSet

Presence: [0..1]

Definition: Contains the character set of the text-based elements used in the Business Message.

Datatype: "UnicodeChartsCode" on page 284

Usage Guideline details

• This element(pacs.009.001.08/.header/CharacterSet) is removed.

4.1.2 FromXML Tag: Fr

Presence: [1..1]

Definition: The sending MessagingEndpoint that has created this Business Message for the receivingMessagingEndpoint that will process this Business Message.

Note the sending MessagingEndpoint might be different from the sending address potentially containedin the transport header (as defined in the transport layer).

The Fr block contains the following elements (see datatype "Party44Choice__1" on page 160 for de-tails)



Page




• on pacs.009.001.08/.header/From


Message Building Blocks

– Lynx_CanadianAgentRule :

If the Agent identified is a Canadian Financial Institution, then at least one of the following options must be present:1. BIC 2. Clearing System Member ID AND [Name AND Postal Address]3. Name AND Postal AddressAll other sub-elements remain optional.

If using option 2 above, Clearing System Member ID/Clearing System ID/Code must be populated with CACPA and Clearing System Member ID/Member ID must be popu-lated with the Canadian Sort Code (a.k.a. Canadian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-digit number that includes a lead-ing zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

4.1.3 ToXML Tag: To

Presence: [1..1]

Definition: The MessagingEndpoint designated by the sending MessagingEndpoint to be the recipientwho will ultimately process this Business Message.

Note the receiving MessagingEndpoint might be different from the receiving address potentially con-tained in the transport header (as defined in the transport layer).

The To block contains the following elements (see datatype "Party44Choice__1" on page 160 for de-tails)



Page




• on pacs.009.001.08/.header/To



If using option 2 above, Clearing System Member ID/Clearing System ID/Code must be populated with CACPA and Clearing System Member ID/Member ID must be popu-lated with the Canadian Sort Code (a.k.a. Canadian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-digit number that includes a lead-

31 May 2020 13

Usage Guideline

ing zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

4.1.4 BusinessMessageIdentifierXML Tag: BizMsgIdr

Presence: [1..1]

Definition: Unambiguously identifies the Business Message to the MessagingEndpoint that has createdthe Business Message.

Datatype: "Max35Text" on page 275


• on pacs.009.001.08/.header/BusinessMessageIdentifier

– Lynx_BusinessMessageIdentifierRule:

The Business Message Identifier is the unique identifier of the Business Message instance that is being transported with this Business Application Header, as defined by the sending application or system. It must contain the Message Iden-tification element from the Group Header of the underlying message, where avail-able (as is typically the case with pacs, pain, and camt messages, for example). If Message Identification is not available in the underlying message, then this element must contain the unique identifier of the Business Message instance.This rule is inherited verbatim from CBPR+.

4.1.5 MessageDefinitionIdentifierXML Tag: MsgDefIdr

Presence: [1..1]

Definition: Contains the MessageIdentifier that defines the BusinessMessage.

It must contain a MessageIdentifier published on the ISO 20022 website.

example camt.001.001.03.



• on pacs.009.001.08/.header/MessageDefinitionIdentifier

– Lynx_MessageDefinitionIdentifierRule:

The Message Definition Identifier of the Business Message instance that is be-ing transported with this header. In general, it must be formatted exactly as it appears in the namespace of the Business Message instance.This rule is inherited verbatim from CBPR+.

4.1.6 BusinessService



XML Tag: BizSvc

Presence: [0..1]

Definition: Specifies the business service agreed between the two MessagingEndpoints under whichrules this Business Message is exchanged.

To be used when there is a choice of processing services or processing service levels.

Example: E&I.



• on pacs.009.001.08/.header/BusinessService

– Lynx_BusinessServiceRule:

This field may be used by SWIFT to support differentiated processing on SWIFT-administered services such as FINplus. For a description of reserved values, please refer to the Service Description for your service. To support differ-entiated processing on CBPRPlus, for example, SWIFT reserves a set of values that conform to a specific format. Examples include: swift.cbprplus.cov.01, swift.cbprplus.core.01, and swift.cbprplus.stp.01. A user-specific value may be used, but please contact your Service Administrator before doing so to ensure alignment with general practice on your service.This rule is inherited verbatim from CBPR+.

4.1.7 MarketPracticeXML Tag: MktPrctc

Presence: [0..1]

Definition: Specifies the market practice to which the message conforms. The market practices are aset of rules agreed between parties that restricts the usage of the messages in order to achieve betterSTP (Straight Through Processing) rates.

A market practice specification may also extend the underlying message specification by using exten-sions or supplementary data of this underlying message.

The MktPrctc block contains the following elements (see datatype "ImplementationSpecification1" onpage 152 for details)



Page




• on pacs.009.001.08/.header/MarketPractice

31 May 2020 15

Usage Guideline

– Lynx_MarketPracticeRule:

This element may be used by SWIFT on SWIFT-administered services. For a descrip-tion of reserved values, please refer to the Service Description for your ser-vice. Contact your Service Administrator for further clarification, if neces-sary.A user-specific value may be used, but please contact your Service Administrator before doing so to ensure alignment with general practice on your service.This rule is inherited verbatim from CBPR+.

4.1.8 CreationDateXML Tag: CreDt

Presence: [1..1]

Definition: Date and time when this Business Message (header) was created.

Datatype: "CBPR_DateTime" on page 247

4.1.9 BusinessProcessingDateXML Tag: BizPrcgDt

Presence: [0..1]

Definition: Processing date and time indicated by the sender for the receiver of the business message.This date may be different from the date and time provided in the CreationDate.

Usage: Market practice or bilateral agreement should specify how this element should be used.

Datatype: "ISODateTime" on page 269


• This element(pacs.009.001.08/.header/BusinessProcessingDate) is removed.

4.1.10 CopyDuplicateXML Tag: CpyDplct

Presence: [0..1]

Definition: Indicates whether the message is a Copy, a Duplicate or a copy of a duplicate of a previouslysent ISO 20022 Message.

Datatype: "CopyDuplicate1Code" on page 250

4.1.11 PossibleDuplicateXML Tag: PssblDplct

Presence: [0..1]

Definition: Flag indicating if the Business Message exchanged between the MessagingEndpoints ispossibly a duplicate.



If the receiving MessagingEndpoint did not receive the original, then this Business Message should beprocessed as if it were the original.

If the receiving MessagingEndpoint did receive the original, then it should perform necessary actions toavoid processing this Business Message again.

This will guarantee business idempotent behaviour.

NOTE: this is named "PossResend" in FIX - this is an application level resend not a network level re-transmission.

Datatype: "YesNoIndicator" on page 285

4.1.12 PriorityXML Tag: Prty

Presence: [0..1]

Definition: Relative indication of the processing precedence of the message over a (set of) BusinessMessages with assigned priorities.

Datatype: "BusinessMessagePriorityCode" on page 245


• on pacs.009.001.08/.header/Priority

Comment:This element is left optional for possible future use but has no validity for Lynx from a Priority point of view.

4.1.13 SignatureXML Tag: Sgntr

Presence: [0..1]

Definition: Contains the digital signature of the Business Entity authorised to sign this Business Mes-sage.


• This element(pacs.009.001.08/.header/Signature) is removed.

4.1.14 RelatedXML Tag: Rltd

Presence: [0..*]

Definition: Specifies the Business Application Header(s) of the Business Message(s) to which this Busi-ness Message relates.

31 May 2020 17

Usage Guideline

Can be used when replying to a query; can also be used when canceling or amending.

The Rltd block contains the following elements (see datatype "BusinessApplicationHeader5__1" onpage 35 for details)



Page


From <Fr> [1..1] ! 36

To <To> [1..1] ! 36










• on pacs.009.001.08/.header/Related

This element has change repeatability, the maximum occurrence has been changed to : 1

4.2 Payload Building Blocks

Note The following chapter identifies the building blocks of the Lynx_FINAL_Phase2Mes-sages_SR2019 / Lynx_FinancialInstitutionCreditTransferV08_pacs.009.001.08 payload de-finition.

4.2.1 GroupHeaderXML 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 "GroupHeader93__1" on page 147for details)



Page












4.2.2 CreditTransferTransactionInformationXML Tag: CdtTrfTxInf

Presence: [1..*]

Definition: Set of elements providing information specific to the individual credit transfer(s).

31 May 2020 19

Usage Guideline

The CdtTrfTxInf block contains the following elements (see datatype "CreditTransferTransaction36__1"on page 62 for details)



Page

































Page










• on pacs.009.001.08/CreditTransferTransactionInformation


4.2.3 SupplementaryDataXML Tag: SplmtryData

Presence: [0..*]

Definition: Additional information that cannot be captured in the structured elements and/or any otherspecific block.

The SplmtryData block contains the following elements (see datatype "SupplementaryData1" onpage 222 for details)



Page




• This element(pacs.009.001.08/SupplementaryData) is removed.

31 May 2020 21

Usage Guideline

5 Message Components

Note The following chapter identifies the message components.

5.1 AccountIdentification4ChoiceDefinition: Specifies the unique identification of an account as assigned by the account servicer.



Page

IBAN <IBAN> {Or [1..1] 22

Other <Othr> Or} [1..1] 22

Used in element(s)

"Identification" on page 42, "Identification" on page 40

5.1.1 IBANXML 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 ofthe IBAN can be found in the standard ISO 13616 "Banking and related financial services - InternationalBank Account Number (IBAN)" version 1997-10-01, or later revisions.

Datatype: "IBAN2007Identifier" on page 268

5.1.2 OtherXML 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" onpage 142 for details)



Page


SchemeName <SchmeNm> [0..1] 142

Issuer <Issr> [0..1] 143


Message Components

5.2 AccountSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification scheme.



Page

Code <Cd> {Or [1..1] 23

Proprietary <Prtry> Or} [1..1] 23

Used in element(s)

"SchemeName" on page 142

5.2.1 CodeXML 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 256

5.2.2 ProprietaryXML Tag: Prtry

Presence: [1..1]

Definition: Name of the identification scheme, in a free text form.


5.3 AddressType3ChoiceDefinition: Choice of formats for the type of address.



Page

Code <Cd> {Or [1..1] 23


Used in element(s)

"AddressType" on page 189, "AddressType" on page 181


Presence: [1..1]

Definition: Type of address expressed as a code.

31 May 2020 23

Usage Guideline

Datatype: "AddressType2Code" on page 242


Presence: [1..1]

Definition: Type of address expressed as a proprietary code.

The Prtry block contains the following elements (see datatype "GenericIdentification30" on page 144for details)



Page




5.4 BranchAndFinancialInstitutionIdentification6Definition: Unique and unambiguous identification of a financial institution or a branch of a financial in-stitution.



Page

FinancialInstitutionIdentification <FinInstnId> [1..1] 24

BranchIdentification <BrnchId> [0..1] 25

Used in element(s)

"InstructedAgent" on page 151, "InstructedReimbursementAgent" on page 214, "InstructingAgent"on page 151, "InstructingReimbursementAgent" on page 213, "ThirdReimbursementAgent" onpage 215, "UltimateCreditor" on page 84, "UltimateDebtor" on page 79

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


Message Components

The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentification18"on page 121 for details)



Page

BICFI <BICFI> [0..1] 121

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] 121

LEI <LEI> [0..1] 122

Name <Nm> [0..1] 122

PostalAddress <PstlAdr> [0..1] 122

Other <Othr> [0..1] 123

5.4.2 BranchIdentificationXML 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 institutioncomponent does not provide identification up to branch level.

The BrnchId block contains the following elements (see datatype "BranchData3" on page 33 for de-tails)



Page


LEI <LEI> [0..1] 33

Name <Nm> [0..1] 33


5.5 BranchAndFinancialInstitutionIdentification6__1Definition: Unique and unambiguous identification of a financial institution or a branch of a financial in-stitution.



Page

FinancialInstitutionIdentification <FinInstnId> [1..1] ! 26

BranchIdentification <BrnchId> [0..1] ! 29

31 May 2020 25

Usage Guideline

Used in element(s)

"Creditor" on page 83, "CreditorAgent" on page 104, "Debtor" on page 79, "DebtorAgent"on page 81, "DebtorAgent" on page 96, "FinancialInstitutionIdentification" on page 161, "In-structedAgent" on page 74, "InstructingAgent" on page 73, "IntermediaryAgent1" on page 75,"IntermediaryAgent1" on page 100, "IntermediaryAgent2" on page 76, "IntermediaryAgent2" onpage 102, "IntermediaryAgent3" on page 78, "IntermediaryAgent3" on page 103, "PreviousIn-structingAgent1" on page 70, "PreviousInstructingAgent1" on page 97, "PreviousInstructingA-gent2" on page 71, "PreviousInstructingAgent2" on page 98, "PreviousInstructingAgent3" onpage 72, "PreviousInstructingAgent3" on page 99


Presence: [1..1]


The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentifica-tion18__1" on page 124 for details)



Page

BICFI <BICFI> [0..1] ! 124


LEI <LEI> [0..1] 125

Name <Nm> [0..1] ! 125

PostalAddress <PstlAdr> [0..1] ! 125

Other <Othr> [0..1] 133


• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation

– Lynx_NameAndPostalAddressAgentRule:

Name and Address must always be present together.This rule is inherited verbatim from CBPR+ but they do not apply it to the From/To (Agent) components in the BAH. For Lynx, this rule is applied across all Agent components.

• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification




Message Components

• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification



• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion



• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation


Name and Address must always be present together.This rule is inherited verbatim from CBPR+.

• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation



• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification



• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification

– LynxNameAndPostalAddressAgentRule:


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification



• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification

31 May 2020 27

Usage Guideline









• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification









• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent/FinancialInstitutionIdentification



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification




Message Components

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification









• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification










Presence: [0..1]



31 May 2020 29

Usage Guideline




Page


LEI <LEI> [0..1] 33

Name <Nm> [0..1] 33



• This element(pacs.009.001.08/.header/From/FinancialInstitutionIdentification/BranchIdentifi-cation) is removed.

• This element(pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/BranchI-dentification) is removed.

• This element(pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/BranchI-dentification) is removed.

• This element(pacs.009.001.08/.header/To/FinancialInstitutionIdentification/BranchIdentifica-tion) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Debtor/BranchIdentifica-tion) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/BranchI-dentification) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/BranchI-dentification) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructingA-gent/BranchIdentification) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryA-gent1/BranchIdentification) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingA-gent1/BranchIdentification) is removed.



Message Components


• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAgent/BranchIdentification) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/IntermediaryAgent1/BranchIdentification) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/PreviousInstructingAgent1/BranchIdentification) is removed.



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent/BranchIdentification

Comment:CBPR+: Only allowed when Creditor Agent is located in Japan to identify the ac-count that must be credited. The information can be disregarded by other agents in the chain and no network validation will be conducted.

5.6 BranchAndFinancialInstitutionIdentification6__2Definition: Unique and unambiguous identification of a financial institution or a branch of a financial in-stitution.



Page



Used in element(s)

"CreditorAgent" on page 82


Presence: [1..1]


31 May 2020 31

Usage Guideline

The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentifica-tion18__2" on page 134 for details)



Page



LEI <LEI> [0..1] 135

Name <Nm> [0..1] 136


Other <Othr> [0..1] 137


• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification




Presence: [0..1]






Page


LEI <LEI> [0..1] 33

Name <Nm> [0..1] 33



Message Components


• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification) is removed.

5.7 BranchData3Definition: Information that locates and identifies a specific branch of a financial institution.



Page


LEI <LEI> [0..1] 33

Name <Nm> [0..1] 33


Used in element(s)

"BranchIdentification" on page 29, "BranchIdentification" on page 32, "BranchIdentification" onpage 25

5.7.1 IdentificationXML Tag: Id

Presence: [0..1]

Definition: Unique and unambiguous identification of a branch of a financial institution.


5.7.2 LEIXML Tag: LEI

Presence: [0..1]

Definition: Legal entity identification for the branch of the financial institution.

Datatype: "LEIIdentifier" on page 273


• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification/LEI) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/BranchIdentification/LEI) is removed.

5.7.3 Name

31 May 2020 33

Usage Guideline

XML Tag: Nm

Presence: [0..1]

Definition: Name by which an agent is known and which is usually used to identify that agent.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification/Name) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/BranchIdentification/Name) is removed.

5.7.4 PostalAddressXML 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 "PostalAddress24" on page 180 fordetails)



Page

AddressType <AdrTp> [0..1] 181

Department <Dept> [0..1] 182

SubDepartment <SubDept> [0..1] 182

StreetName <StrtNm> [0..1] 183

BuildingNumber <BldgNb> [0..1] 183

BuildingName <BldgNm> [0..1] 183

Floor <Flr> [0..1] 183

PostBox <PstBx> [0..1] 184

Room <Room> [0..1] 184

PostCode <PstCd> [0..1] 184

TownName <TwnNm> [0..1] 184

TownLocationName <TwnLctnNm> [0..1] 185

DistrictName <DstrctNm> [0..1] 185

CountrySubDivision <CtrySubDvsn> [0..1] 186

Country <Ctry> [0..1] 186

AddressLine <AdrLine> [0..7] ! 187


Message Components


• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification/PostalAddress) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/BranchIdentification/PostalAddress) is removed.

5.8 BusinessApplicationHeader5__1Definition: Specifies the Business Application Header of the Business Message.

Can be used when replying to a query; can also be used when canceling or amending.



Page


From <Fr> [1..1] ! 36

To <To> [1..1] ! 36









Used in element(s)

"Related" on page 17

5.8.1 CharacterSetXML Tag: CharSet

Presence: [0..1]

Definition: Contains the character set of the text-based elements used in the Business Message.

Datatype: "UnicodeChartsCode" on page 284


• This element(pacs.009.001.08/.header/Related/CharacterSet) is removed.

31 May 2020 35

Usage Guideline

5.8.2 FromXML Tag: Fr

Presence: [1..1]

Definition: The sending MessagingEndpoint that has created this Business Message for the receivingMessagingEndpoint that will process this Business Message.

Note the sending MessagingEndpoint might be different from the sending address potentially containedin the transport header (as defined in the transport layer).

The Fr block contains the following elements (see datatype "Party44Choice__1" on page 160 for de-tails)



Page




• on pacs.009.001.08/.header/Related/From




5.8.3 ToXML Tag: To

Presence: [1..1]

Definition: The MessagingEndpoint designated by the sending MessagingEndpoint to be the recipientwho will ultimately process this Business Message.

Note the receiving MessagingEndpoint might be different from the receiving address potentially con-tained in the transport header (as defined in the transport layer).


Message Components

The To block contains the following elements (see datatype "Party44Choice__1" on page 160 for de-tails)



Page




• on pacs.009.001.08/.header/Related/To




5.8.4 BusinessMessageIdentifierXML Tag: BizMsgIdr

Presence: [1..1]

Definition: Unambiguously identifies the Business Message to the MessagingEndpoint that has createdthe Business Message.



• on pacs.009.001.08/.header/Related/BusinessMessageIdentifier

– Lynx_BusinessMessageIdentifier:

The Business Message Identifier is the unique identifier of the Business Message instance that is being transported with this Business Application Header, as defined by the sending application or system. It must contain the Message Iden-tification element from the Group Header of the underlying message, where avail-able (as is typically the case with pacs, pain, and camt messages, for example). If Message Identification is not available in the underlying message, then this element must contain the unique identifier of the Business Message instance.This rule is inherited verbatim from CBPR+.

31 May 2020 37

Usage Guideline

5.8.5 MessageDefinitionIdentifierXML Tag: MsgDefIdr

Presence: [1..1]

Definition: Contains the MessageIdentifier that defines the BusinessMessage.

It must contain a MessageIdentifier published on the ISO 20022 website.

example camt.001.001.03.



• on pacs.009.001.08/.header/Related/MessageDefinitionIdentifier

– Lynx_MessageDefinitionIdentifierRule:

The Message Definition Identifier of the Business Message instance that is be-ing transported with this header. In general, it must be formatted exactly as it appears in the namespace of the Business Message instance.This rule is inherited verbatim from CBPR+.

5.8.6 BusinessServiceXML Tag: BizSvc

Presence: [0..1]

Definition: Specifies the business service agreed between the two MessagingEndpoints under whichrules this Business Message is exchanged.

To be used when there is a choice of processing services or processing service levels.

Example: E&I.



• on pacs.009.001.08/.header/Related/BusinessService

– Lynx_BusinessServiceRule:

This field may be used by SWIFT to support differentiated processing on SWIFT-administered services such as FINplus. For a description of reserved values, please refer to the Service Description for your service. To support differ-entiated processing on CBPRPlus, for example, SWIFT reserves a set of values that conform to a specific format. Examples include: swift.cbprplus.cov.01, swift.cbprplus.core.01, and swift.cbprplus.stp.01. A user-specific value may be used, but please contact your Service Administrator before doing so to ensure alignment with general practice on your service.This rule is inherited verbatim from CBPR+.


Message Components

5.8.7 CreationDateXML Tag: CreDt

Presence: [1..1]

Definition: Date and time when this Business Message (header) was created.

Note Times must be normalized, using the "Z" annotation.


5.8.8 CopyDuplicateXML Tag: CpyDplct

Presence: [0..1]

Definition: Indicates whether the message is a Copy, a Duplicate or a copy of a duplicate of a previouslysent ISO 20022 Message.

Datatype: "CopyDuplicate1Code" on page 250

5.8.9 PossibleDuplicateXML Tag: PssblDplct

Presence: [0..1]

Definition: Flag indicating if the Business Message exchanged between the MessagingEndpoints ispossibly a duplicate.

If the receiving MessagingEndpoint did not receive the original, then this Business Message should beprocessed as if it were the original.

If the receiving MessagingEndpoint did receive the original, then it should perform necessary actions toavoid processing this Business Message again.

This will guarantee business idempotent behaviour.

NOTE: this is named "PossResend" in FIX - this is an application level resend not a network level re-transmission.

Datatype: "YesNoIndicator" on page 285

5.8.10 PriorityXML Tag: Prty

Presence: [0..1]

Definition: Relative indication of the processing precedence of the message over a (set of) BusinessMessages with assigned priorities.

Datatype: "BusinessMessagePriorityCode" on page 245

31 May 2020 39

Usage Guideline


• on pacs.009.001.08/.header/Related/Priority

Comment:This element is left optional for possible future use but has no validity for Lynx from a Priority point of view.

5.8.11 SignatureXML Tag: Sgntr

Presence: [0..1]

Definition: Contains the digital signature of the Business Entity authorised to sign this Business Mes-sage.


• This element(pacs.009.001.08/.header/Related/Signature) is removed.

5.9 CashAccount38Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 41

Currency <Ccy> [0..1] 41

Name <Nm> [0..1] 41

Proxy <Prxy> [0..1] 42

Used in element(s)

"InstructedReimbursementAgentAccount" on page 214, "InstructingReimbursementAgentAccount" onpage 213, "SettlementAccount" on page 212, "ThirdReimbursementAgentAccount" on page 215


Presence: [1..1]

Definition: Unique and unambiguous identification for the account between the account owner and theaccount servicer.


Message Components

The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 22 for details)



Page



5.9.2 TypeXML Tag: Tp

Presence: [0..1]

Definition: Specifies the nature, or use of the account.

The Tp block contains the following elements (see datatype "CashAccountType2Choice" on page 44for details)



Page

Code <Cd> {Or [1..1] 44


5.9.3 CurrencyXML 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 242

5.9.4 NameXML Tag: Nm

Presence: [0..1]

Definition: Name of the account, as assigned by the account servicing institution, in agreement with theaccount 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'sidentity and the account number.


31 May 2020 41

Usage Guideline

5.9.5 ProxyXML Tag: Prxy

Presence: [0..1]

Definition: Specifies an alternate assumed name for the identification of the account.

The Prxy block contains the following elements (see datatype "ProxyAccountIdentification1" onpage 195 for details)



Page

Type <Tp> [0..1] 195


5.10 CashAccount38__1Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


Used in element(s)

"CreditorAccount" on page 84, "CreditorAccount" on page 106, "CreditorAgentAccount" onpage 83, "CreditorAgentAccount" on page 105, "DebtorAccount" on page 80, "DebtorAccount"on page 95, "DebtorAgentAccount" on page 81, "DebtorAgentAccount" on page 96, "Interme-diaryAgent1Account" on page 76, "IntermediaryAgent1Account" on page 101, "IntermediaryAgen-t2Account" on page 77, "IntermediaryAgent2Account" on page 102, "IntermediaryAgent3Account"on page 79, "IntermediaryAgent3Account" on page 104, "PreviousInstructingAgent1Account" onpage 70, "PreviousInstructingAgent1Account" on page 98, "PreviousInstructingAgent2Account"on page 71, "PreviousInstructingAgent2Account" on page 99, "PreviousInstructingAgent3Ac-count" on page 73, "PreviousInstructingAgent3Account" on page 100


Presence: [1..1]

Definition: Unique and unambiguous identification for the account between the account owner and theaccount servicer.


Message Components

The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 22 for details)



Page




Presence: [0..1]

Definition: Specifies the nature, or use of the account.

The Tp block contains the following elements (see datatype "CashAccountType2Choice" on page 44for details)



Page

Code <Cd> {Or [1..1] 44


5.10.3 CurrencyXML 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 242


Presence: [0..1]

Definition: Name of the account, as assigned by the account servicing institution, in agreement with theaccount 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'sidentity and the account number.


31 May 2020 43

Usage Guideline

5.10.5 ProxyXML Tag: Prxy

Presence: [0..1]

Definition: Specifies an alternate assumed name for the identification of the account.

The Prxy block contains the following elements (see datatype "ProxyAccountIdentification1__1" onpage 196 for details)



Page

Type <Tp> [0..1] 196

Identification <Id> [1..1] ! 196

5.11 CashAccountType2ChoiceDefinition: Nature or use of the account.



Page

Code <Cd> {Or [1..1] 44


Used in element(s)

"Type" on page 43, "Type" on page 41


Presence: [1..1]

Definition: Account type, in a coded form.

Datatype: "ExternalCashAccountType1Code" on page 257


Presence: [1..1]

Definition: Nature or use of the account in a proprietary form.


5.12 CategoryPurpose1ChoiceDefinition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.


Message Components

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.



Page

Code <Cd> {Or [1..1] 45


Used in element(s)

"CategoryPurpose" on page 177, "CategoryPurpose" on page 174


Presence: [1..1]

Definition: Category purpose, as published in an external category purpose code list.

Datatype: "ExternalCategoryPurpose1Code" on page 258


Presence: [1..1]

Definition: Category purpose, in a proprietary form.


5.13 ClearingSystemIdentification2ChoiceDefinition: Choice of a clearing system identifier.



Page

Code <Cd> {Or [1..1] ! 45


Used in element(s)

"ClearingSystemIdentification" on page 52, "ClearingSystemIdentification" on page 59, "Clear-ingSystemIdentification" on page 52


Presence: [1..1]

Definition: Identification of a clearing system, in a coded form as published in an external list.

31 May 2020 45

Usage Guideline

Datatype: "ExternalClearingSystemIdentification1Code" on page 259


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code

Single value: CACPA

• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code

Single value: CACPA

• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code

Comment:If identifying a Canadian Financial Institution, then CACPA is the code that must be populated in this element.

• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code



Message Components

• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code






• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Code






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCredit-Transfer/CreditorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/ClearingSystemIdentification/Code


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/Clear-ingSystemIdentification/Code

31 May 2020 47

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/ClearingSystemIdentification/Code






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdenti-fication/ClearingSystemIdentification/Code







Presence: [1..1]

Definition: Identification code for a clearing system, that has not yet been identified in the list of clearingsystems.



Message Components


• This element(pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Propri-etary) is removed.

• This element(pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Propri-etary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Propri-etary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Propri-etary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialIn-stitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Pro-prietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/Fi-nancialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifi-cation/Proprietary) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingA-gent1/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemI-dentification/Proprietary) is removed.

31 May 2020 49

Usage Guideline



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdenti-fication/ClearingSystemIdentification/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentifi-cation/ClearingSystemIdentification/Proprietary) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/IntermediaryAgent1/FinancialInstitutionIdentification/ClearingSystemMemberI-dentification/ClearingSystemIdentification/Proprietary) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/PreviousInstructingAgent1/FinancialInstitutionIdentification/ClearingSystem-MemberIdentification/ClearingSystemIdentification/Proprietary) is removed.



5.14 ClearingSystemIdentification3ChoiceDefinition: Specifies the clearing system identification.



Page

Code <Cd> {Or [1..1] ! 51



Message Components

Used in element(s)

"ClearingSystem" on page 212


Presence: [1..1]

Definition: Infrastructure through which the payment instruction is processed, as published in an exter-nal clearing system identification code list.

Datatype: "ExternalCashClearingSystem1Code" on page 258


• on pacs.009.001.08/GroupHeader/SettlementInformation/ClearingSystem/Code

Single value: LYX

• on pacs.009.001.08/GroupHeader/SettlementInformation/ClearingSystem/Code

Synonym (MT 205 - field 103 Header - code CAD): Clearing System Identifier


Presence: [1..1]

Definition: Clearing system identification in a proprietary form.



• This element(pacs.009.001.08/GroupHeader/SettlementInformation/ClearingSystem/Propri-etary) is removed.

5.15 ClearingSystemMemberIdentification2Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a memberof the clearing system.



Page

ClearingSystemIdentification <ClrSysId> [0..1] 52

MemberIdentification <MmbId> [1..1] 52

Used in element(s)

"ClearingSystemMemberIdentification" on page 121

31 May 2020 51

Usage Guideline

5.15.1 ClearingSystemIdentificationXML Tag: ClrSysId

Presence: [0..1]

Definition: Specification of a pre-agreed offering between clearing agents or the channel through whichthe payment instruction is processed.

The ClrSysId block contains the following elements (see datatype "ClearingSystemIdentifica-tion2Choice" on page 45 for details)



Page

Code <Cd> {Or [1..1] 45


5.15.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.


5.16 ClearingSystemMemberIdentification2__1Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a memberof the clearing system.



Page


MemberIdentification <MmbId> [1..1] ! 55

Used in element(s)



Presence: [0..1]



Message Components




Page

Code <Cd> {Or [1..1] ! 45



• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification

This element is now mandatory, the minimum occurrence has been changed to : 1

• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification


31 May 2020 53

Usage Guideline





• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCredit-Transfer/CreditorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/ClearingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/Clear-ingSystemIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/ClearingSystemIdentification






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdenti-fication/ClearingSystemIdentification




Message Components





Presence: [1..1]


Datatype: "CBPR__RestrictedFINXMax28Text" on page 248


• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/MemberIdentification

Comment:If identifying a Canadian Financial Institution, Member Identification must be populated with the Canadian Sort Code (a.k.a. Canadian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-digit number that includes a leading zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/MemberIdentification


• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/MemberIdentification


• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/ClearingSystemMemberIdentification/MemberIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/MemberIdentification

31 May 2020 55

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/ClearingSystemMemberIdentification/MemberIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/MemberIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/MemberIdentification

Comment:Member Identification must be populated with the Canadian Sort Code (a.k.a. Cana-dian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-dig-it number that includes a leading zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/MemberIdentification

Comment:Member Identification must be populated with the Canadian Sort Code (a.k.a. Cana-dian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-dig-it number that includes a leading zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/MemberIdentification





Message Components



• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/MemberIdentification






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCredit-Transfer/CreditorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/MemberIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/Mem-berIdentification


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdentifica-tion/MemberIdentification

31 May 2020 57

Usage Guideline






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification/ClearingSystemMemberIdenti-fication/MemberIdentification







Message Components

5.17 ClearingSystemMemberIdentification2__2Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a memberof the clearing system.



Page



Used in element(s)



Presence: [0..1]





Page

Code <Cd> {Or [1..1] ! 45



• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/ClearingSystemIdentification



Presence: [1..1]


Datatype: "CBPR_RestrictedFINXMax28Text" on page 247

31 May 2020 59

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/MemberIdentification


5.18 Contact4Definition: Specifies the details of the contact person.



Page

NamePrefix <NmPrfx> [0..1] 60

Name <Nm> [0..1] 60

PhoneNumber <PhneNb> [0..1] 61

MobileNumber <MobNb> [0..1] 61

FaxNumber <FaxNb> [0..1] 61

EmailAddress <EmailAdr> [0..1] 61

EmailPurpose <EmailPurp> [0..1] 61

JobTitle <JobTitl> [0..1] 61

Responsibility <Rspnsblty> [0..1] 62


Other <Othr> [0..*] 62

PreferredMethod <PrefrdMtd> [0..1] 62

Used in element(s)

"ContactDetails" on page 169, "ContactDetails" on page 165

5.18.1 NamePrefixXML Tag: NmPrfx

Presence: [0..1]

Definition: Specifies the terms used to formally address a person.

Datatype: "NamePrefix2Code" on page 277

5.18.2 Name


Message Components

XML Tag: Nm

Presence: [0..1]

Definition: Name by which a party is known and which is usually used to identify that party.


5.18.3 PhoneNumberXML Tag: PhneNb

Presence: [0..1]

Definition: Collection of information that identifies a phone number, as defined by telecom services.

Datatype: "PhoneNumber" on page 278

5.18.4 MobileNumberXML Tag: MobNb

Presence: [0..1]

Definition: Collection of information that identifies a mobile phone number, as defined by telecom ser-vices.


5.18.5 FaxNumberXML Tag: FaxNb

Presence: [0..1]

Definition: Collection of information that identifies a FAX number, as defined by telecom services.


5.18.6 EmailAddressXML Tag: EmailAdr

Presence: [0..1]

Definition: Address for electronic mail (e-mail).


5.18.7 EmailPurposeXML Tag: EmailPurp

Presence: [0..1]

Definition: Purpose for which an email address may be used.


5.18.8 JobTitleXML Tag: JobTitl

31 May 2020 61

Usage Guideline

Presence: [0..1]

Definition: Title of the function.


5.18.9 ResponsibilityXML Tag: Rspnsblty

Presence: [0..1]

Definition: Role of a person in an organisation.


5.18.10 DepartmentXML Tag: Dept

Presence: [0..1]

Definition: Identification of a division of a large organisation or building.



Presence: [0..*]

Definition: Contact details in another form.

The Othr block contains the following elements (see datatype "OtherContact1" on page 159 for de-tails)



Page

ChannelType <ChanlTp> [1..1] 159


5.18.12 PreferredMethodXML Tag: PrefrdMtd

Presence: [0..1]

Definition: Preferred method used to reach the contact.

Datatype: "PreferredContactMethod1Code" on page 279

5.19 CreditTransferTransaction36__1Definition: Provide further details specific to the individual transaction(s) included in the message.


Message Components



Page































31 May 2020 63

Usage Guideline


Page








Rules

R16 IntermediaryAgent2Rule ✓

If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.

Error handling:



– Error Text: Invalid message content for intermediary agent 2.



Error handling:





If IntermediaryAgent1 is present, then CreditorAgent must be present.

Error handling:




R19 IntermediaryAgent1AccountRule ✓

If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.

Error handling:


Message Components



– Error Text: Invalid message content for intermediary agent 1 account.



Error handling:






Error handling:




R22 DebtorAgentAccountRule ✓

If DebtorAgentAccount is present, then DebtorAgent must be present.

Error handling:



– Error Text: Invalid message content for debtor agent account.

R23 CreditorAgentAccountRule ✓

If CreditorAgentAccount is present, then CreditorAgent must be present.

Error handling:



– Error Text: Invalid message content for creditor agent account.

R24 PreviousInstructingAgent1AccountRule ✓

If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must bepresent.

Error handling:

31 May 2020 65

Usage Guideline



– Error Text: Invalid message content for previous instructing agent account.



Error handling:






Error handling:




R27 PreviousInstructionAgent2Rule ✓

If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.

Error handling:






Error handling:




Guidelines

1. UltimateDebtorGuideline

UltimateDebtor may only be present if different from Debtor.

2. UltimateCreditorGuideline

UltimateCreditor may only be present if different from Creditor.


Message Components

3. PreviousInstructingAgent1Guideline

It is recommended that, when present, PreviousInstructingAgent1 is the closest to the DebtorAgentin the payment chain.

Used in element(s)

"CreditTransferTransactionInformation" on page 19

5.19.1 PaymentIdentificationXML Tag: PmtId

Presence: [1..1]

Definition: Set of elements used to reference a payment instruction.

The PmtId block contains the following elements (see datatype "PaymentIdentification7__1" onpage 170 for details)



Page

InstructionIdentification <InstrId> [0..1] ! 170

EndToEndIdentification <EndToEndId> [1..1] ! 171

TransactionIdentification <TxId> [0..1] 172

UETR <UETR> [0..1] ! 172

ClearingSystemReference <ClrSysRef> [0..1] ! 172

5.19.2 PaymentTypeInformationXML 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 "PaymentTypeInformation28__1" onpage 175 for details)



Page

InstructionPriority <InstrPrty> [0..1] 175

ClearingChannel <ClrChanl> [0..1] ! 175

ServiceLevel <SvcLvl> [0..*] ! R[0..3] 175

LocalInstrument <LclInstrm> [0..1] ! 176

CategoryPurpose <CtgyPurp> [0..1] ! 177

31 May 2020 67

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInformation


5.19.3 InterbankSettlementAmountXML Tag: IntrBkSttlmAmt

Presence: [1..1]

Definition: Amount of money moved between the instructing agent and the instructed agent.

Datatype: "CBPR_Amount_2decimals" on page 246


• on pacs.009.001.08/CreditTransferTransactionInformation/InterbankSettlementAmount

Synonym (MT 205 - field 32A - subfield 2+3): Currency, Amount

5.19.4 InterbankSettlementDateXML Tag: IntrBkSttlmDt

Presence: [0..1]

Definition: Date on which the amount of money ceases to be available to the agent that owes it andwhen the amount of money becomes available to the agent to which it is due.

Datatype: "ISODate" on page 269


• on pacs.009.001.08/CreditTransferTransactionInformation/InterbankSettlementDate


• on pacs.009.001.08/CreditTransferTransactionInformation/InterbankSettlementDate

Synonym (MT 205 - field 32A - subfield 1): Value Date

5.19.5 SettlementPriorityXML Tag: SttlmPrty

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

Datatype: "Priority3Code" on page 280

5.19.6 SettlementTimeIndicationXML Tag: SttlmTmIndctn


Message Components

Presence: [0..1]

Definition: Provides information on the occurred settlement time(s) of the payment transaction.

The SttlmTmIndctn block contains the following elements (see datatype "SettlementDateTimeIndica-tion1" on page 208 for details)



Page

DebitDateTime <DbtDtTm> [0..1] 208

CreditDateTime <CdtDtTm> [0..1] 208


• This element(pacs.009.001.08/CreditTransferTransactionInformation/SettlementTimeIndica-tion) will be ignored by the Receiver.

• on pacs.009.001.08/CreditTransferTransactionInformation/SettlementTimeIndication

Comment:This element has no relevance for Lynx settlement purposes and is ignored. We are leaving it optional here because CBPR+ leaves it optional and it may be populated by a non-Canadian FI sending a payment instruction into Canada.

5.19.7 SettlementTimeRequestXML Tag: SttlmTmReq

Presence: [0..1]

Definition: Provides information on the requested settlement time(s) of the payment instruction.

The SttlmTmReq block contains the following elements (see datatype "SettlementTimeRequest2__1"on page 216 for details)



Page

CLSTime <CLSTm> [0..1] ! 216

TillTime <TillTm> [0..1] 217

FromTime <FrTm> [0..1] 217

RejectTime <RjctTm> [0..1] 217


• on pacs.009.001.08/CreditTransferTransactionInformation/SettlementTimeRequest

31 May 2020 69

Usage Guideline

– Lynx_SettlementTimeRequestFromTimeRule:

If present, the From Time (FrTm) option will be used to indicate the time from which the payment will be considered for settlement in Lynx. All other options, if present, will be ignored from a Lynx processing point of view.

5.19.8 PreviousInstructingAgent1XML Tag: PrvsInstgAgt1

Presence: [0..1]

Definition: Agent immediately prior to the instructing agent.

The PrvsInstgAgt1 block contains the following elements (see datatype "BranchAndFinancialInstitu-tionIdentification6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1




5.19.9 PreviousInstructingAgent1AccountXML Tag: PrvsInstgAgt1Acct

Presence: [0..1]

Definition: Unambiguous identification of the account of the previous instructing agent at its servicingagent in the payment chain.


Message Components

The PrvsInstgAgt1Acct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]





Page









31 May 2020 71

Usage Guideline

Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]





Page









Message Components


Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.19.14 InstructingAgentXML Tag: InstgAgt

Presence: [0..1]

Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).

The InstgAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent



31 May 2020 73

Usage Guideline





Synonym (MT 205 - Header): Sender


Comment:For Lynx, the Instructing Agent is synonymous with the Direct Settlement Partici-pant of the Debtor.

5.19.15 InstructedAgentXML Tag: InstdAgt

Presence: [0..1]

Definition: Agent that is instructed by the previous party in the chain to carry out the (set of) instruc-tion(s).

The InstdAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent




Message Components





Synonym (MT205 - Header): Receiver


Comment:For Lynx, the Instructed Agent is synonymous with the Direct Settlement Partici-pant of the Creditor.

5.19.16 IntermediaryAgent1XML 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-dentification6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1

31 May 2020 75

Usage Guideline





Synonym (MT 205 - field 56a): Intermediary

5.19.17 IntermediaryAgent1AccountXML Tag: IntrmyAgt1Acct

Presence: [0..1]

Definition: Unambiguous identification of the account of the intermediary agent 1 at its servicing agent inthe payment chain.

The IntrmyAgt1Acct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1Account

Synonym (MT 205 - field 56a - subfield 1): Intermediary Institution - Account


Presence: [0..1]



Message Components

Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agentbetween the IntermediaryAgent1 and the IntermediaryAgent3.




Page









Presence: [0..1]


31 May 2020 77

Usage Guideline




Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]


Usage: If IntermediaryAgent3 is present, then it identifies the agent between the IntermediaryAgent 2and the CreditorAgent.




Page









Message Components


Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.19.22 UltimateDebtorXML Tag: UltmtDbtr

Presence: [0..1]

Definition: Ultimate financial institution that owes an amount of money to the (ultimate) institutional cred-itor.

The UltmtDbtr block contains the following elements (see datatype "BranchAndFinancialInstitutionIden-tification6" on page 24 for details)



Page




• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateDebtor) is re-moved.

5.19.23 DebtorXML Tag: Dbtr

Presence: [1..1]

Definition: Financial institution that owes an amount of money to the (ultimate) financial institutionalcreditor.

31 May 2020 79

Usage Guideline

The Dbtr block contains the following elements (see datatype "BranchAndFinancialInstitutionIdentifica-tion6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor




• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor

Synonym (MT 205 - field 52a): Ordering Institution

5.19.24 DebtorAccountXML Tag: DbtrAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the debtor to which a debit entry will be madeas a result of the transaction.

The DbtrAcct block contains the following elements (see datatype "CashAccount38__1" on page 42for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAccount

Synonym (MT 205 - field 52a - subfield 1): Ordering Institution - Account

5.19.25 DebtorAgentXML Tag: DbtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the debtor.

The DbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent




5.19.26 DebtorAgentAccountXML Tag: DbtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in thepayment chain.

31 May 2020 81

Usage Guideline

The DbtrAgtAcct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.19.27 CreditorAgentXML Tag: CdtrAgt

Presence: [0..1]

Definition: Financial institution servicing an account for the creditor.

The CdtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__2" on page 31 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent




• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent

Synonym (MT 205 - field 57a): Account With Institution


Message Components

5.19.28 CreditorAgentAccountXML Tag: CdtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor agent at its servicing agent to whicha credit entry will be made as a result of the payment transaction.

The CdtrAgtAcct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgentAccount

Synonym (MT 205 - field 57a - subfield 1): Account With Institution - Account

5.19.29 CreditorXML Tag: Cdtr

Presence: [1..1]

Definition: Financial institution that receives an amount of money from the financial institutional debtor.

The Cdtr block contains the following elements (see datatype "BranchAndFinancialInstitutionIdentifica-tion6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor

31 May 2020 83

Usage Guideline




• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor

Synonym (MT 205 - field 58a): Beneficiary Institution

5.19.30 CreditorAccountXML Tag: CdtrAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor to which a credit entry will be post-ed as a result of the payment transaction.

The CdtrAcct block contains the following elements (see datatype "CashAccount38__1" on page 42for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAccount

Synonym (MT 205 - field 58a - subfield 1): Beneficiary Institution - Account

5.19.31 UltimateCreditorXML Tag: UltmtCdtr

Presence: [0..1]

Definition: Ultimate financial institution to which an amount of money is due.


Message Components

The UltmtCdtr block contains the following elements (see datatype "BranchAndFinancialInstitutionIden-tification6" on page 24 for details)



Page




• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor) is re-moved.

5.19.32 InstructionForCreditorAgentXML 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-gent2" on page 153 for details)



Page

Code <Cd> [0..1] 154

InstructionInformation <InstrInf> [0..1] 154


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructionForCreditorAgent


5.19.33 InstructionForNextAgentXML Tag: InstrForNxtAgt

Presence: [0..*]

Definition: Further information related to the processing of the payment instruction that may need to beacted upon by the next agent.

Usage: The next agent may not be the creditor agent.

The instruction can relate to a level of service, can be an instruction that has to be executed by theagent, or can be information required by the next agent.

31 May 2020 85

Usage Guideline

The InstrForNxtAgt block contains the following elements (see datatype "InstructionForNextAgent1" onpage 154 for details)



Page

Code <Cd> [0..1] 154

InstructionInformation <InstrInf> [0..1] ! 155


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructionForNextAgent


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructionForNextAgent

Synonym (MT 205 - field 72): Sender To Receiver Information

5.19.34 PurposeXML Tag: Purp

Presence: [0..1]

Definition: 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 isnot 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 197 for de-tails)



Page

Code <Cd> {Or [1..1] 198



• on pacs.009.001.08/CreditTransferTransactionInformation/Purpose

Comment:Code is the preferred option.

5.19.35 RemittanceInformationXML Tag: RmtInf

Presence: [0..1]


Message Components

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 "RemittanceInformation2" onpage 206 for details)



Page

Unstructured <Ustrd> [0..*] ! R[0..1] 207


• on pacs.009.001.08/CreditTransferTransactionInformation/RemittanceInformation

Comment:In the case of a COV scenario, pacs.008 remittance information will be available in the Underlying Transaction Information.

5.19.36 UnderlyingCustomerCreditTransferXML Tag: UndrlygCstmrCdtTrf

Presence: [0..1]

Definition: Provides information on the underlying customer credit transfer for which cover is provided.

31 May 2020 87

Usage Guideline

The UndrlygCstmrCdtTrf block contains the following elements (see datatype "CreditTransferTransac-tion37__1" on page 89 for details)



Page

UltimateDebtor <UltmtDbtr> [0..1] ! 93

InitiatingParty <InitgPty> [0..1] ! 93





















UltimateCreditor <UltmtCdtr> [0..1] ! 106

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] ! R[0..2] 107


Tax <Tax> [0..1] ! 109


InstructedAmount <InstdAmt> [0..1] 110


Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTransfer

Comment:This component will only be present in a pacs.009 if the payment is a COVER pay-ment for a pacs.008.

5.19.37 SupplementaryDataXML Tag: SplmtryData

Presence: [0..*]

Definition: Additional information that cannot be captured in the structured elements and/or any otherspecific block.

The SplmtryData block contains the following elements (see datatype "SupplementaryData1" onpage 222 for details)



Page




• This element(pacs.009.001.08/CreditTransferTransactionInformation/SupplementaryData) isremoved.

5.20 CreditTransferTransaction37__1Definition: Provides further details specific to the individual transaction(s) included in the message.

31 May 2020 89

Usage Guideline



Page

UltimateDebtor <UltmtDbtr> [0..1] ! 93

InitiatingParty <InitgPty> [0..1] ! 93





















UltimateCreditor <UltmtCdtr> [0..1] ! 106

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] ! R[0..2] 107


Tax <Tax> [0..1] ! 109


InstructedAmount <InstdAmt> [0..1] 110

Rules



Message Components


Error handling:






Error handling:






Error handling:






Error handling:






Error handling:






Error handling:

31 May 2020 91

Usage Guideline






Error handling:






Error handling:






Error handling:






Error handling:




Guidelines

1. UltimateDebtorGuideline

UltimateDebtor may only be present if different from Debtor.

2. UltimateCreditorGuideline

UltimateCreditor may only be present if different from Creditor.


Message Components

3. PreviousInstructingAgent1Guideline

It is recommended that, when present, PreviousInstructingAgent1 is the closest to the DebtorAgentin the payment chain.

Used in element(s)

"UnderlyingCustomerCreditTransfer" on page 87


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 "PartyIdentification135" onpage 162 for details)



Page

Name <Nm> [0..1] 162



CountryOfResidence <CtryOfRes> [0..1] ! 164

ContactDetails <CtctDtls> [0..1] 165


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor

– Lynx_CanadianParty(UltimateDebtor)Rule :

For a Canadian Ultimate Debtor, one of the following options should be present:1. Name AND Postal Address2. [Name AND Postal Address] AND [Identification (Org or Private)]

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor

– Lynx_NameAndPostalAddressPartyRule:

If Postal Address is present, Name is mandatory.This rule is inherited verbatim from CBPR+.

5.20.2 InitiatingPartyXML Tag: InitgPty

Presence: [0..1]

Definition: Party that initiates the payment.

31 May 2020 93

Usage Guideline

Usage: This can be either the debtor or a party that initiates the credit transfer on behalf of the debtor.

The InitgPty block contains the following elements (see datatype "PartyIdentification135" onpage 162 for details)



Page

Name <Nm> [0..1] 162






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty

– Lynx_CanadianParty(InitiatingParty)Rule :

For a Canadian Initiating Party, both Name AND Postal Address should be present.

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty




Presence: [1..1]

Definition: Party that owes an amount of money to the (ultimate) creditor.


Message Components

The Dbtr block contains the following elements (see datatype "PartyIdentification135__1" onpage 166 for details)



Page

Name <Nm> [0..1] 166




ContactDetails <CtctDtls> [0..1] ! 169


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor

– Lynx_CanadianParty(Debtor)Rule :

For a Canadian Debtor, one of the following options should be present:1. Identification/Org ID/Any BIC AND [Debtor Account OR Identification/Org ID/Other]2. [Name AND Postal Address] AND [Debtor Account or Identification (Org or Pri-vate)]


– Lynx_DebtorNameMandatoryIfRule:

For Debtor, if AnyBIC is absent, Name is mandatory.This rule is inherited verbatim from CBPR+.




5.20.4 DebtorAccountXML Tag: DbtrAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the debtor to which a debit entry will be madeas a result of the transaction.

31 May 2020 95

Usage Guideline

The DbtrAcct block contains the following elements (see datatype "CashAccount38__1" on page 42for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.20.5 DebtorAgentXML Tag: DbtrAgt

Presence: [1..1]

Definition: Financial institution servicing an account for the debtor.

The DbtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__1" on page 25 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent




5.20.6 DebtorAgentAccount


Message Components

XML Tag: DbtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in thepayment chain.

The DbtrAgtAcct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]





Page




• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1



If using option 2 above, Clearing System Member ID/Clearing System ID/Code must be populated with CACPA and Clearing System Member ID/Member ID must be popu-lated with the Canadian Sort Code (a.k.a. Canadian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-digit number that includes a lead-

31 May 2020 97

Usage Guideline

ing zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.


Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]





Page






Message Components





Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]





Page



31 May 2020 99

Usage Guideline







Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]


Usage: If more than one intermediary agent is present, then IntermediaryAgent1 identifies the agent be-tween the DebtorAgent and the IntermediaryAgent2.


Message Components




Page




• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1





Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


31 May 2020 101

Usage Guideline


Presence: [0..1]


Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agentbetween the IntermediaryAgent1 and the IntermediaryAgent3.




Page









Presence: [0..1]



Message Components




Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [0..1]


Usage: If IntermediaryAgent3 is present, then it identifies the agent between the IntermediaryAgent 2and the CreditorAgent.




Page








31 May 2020 103

Usage Guideline


Presence: [0..1]





Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.20.19 CreditorAgentXML Tag: CdtrAgt

Presence: [1..1]

Definition: Financial institution servicing an account for the creditor.

The CdtrAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6__1" on page 25 for details)



Page


BranchIdentification <BrnchId> [0..1] ! 29


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent



If using option 2 above, Clearing System Member ID/Clearing System ID/Code must be populated with CACPA and Clearing System Member ID/Member ID must be popu-


Message Components

lated with the Canadian Sort Code (a.k.a. Canadian Clearing (CC) Code) of the Canadian Financial Institution. This is a 9-digit number that includes a lead-ing zero as the first character, followed by the 3-digit Institution Number, followed by the 5-digit Transit/Branch Routing Number. Example: 012345678.

5.20.20 CreditorAgentAccountXML Tag: CdtrAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor agent at its servicing agent to whicha credit entry will be made as a result of the payment transaction.

The CdtrAgtAcct block contains the following elements (see datatype "CashAccount38__1" onpage 42 for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43



Presence: [1..1]

Definition: Party to which an amount of money is due.

The Cdtr block contains the following elements (see datatype "PartyIdentification135__1" onpage 166 for details)



Page

Name <Nm> [0..1] 166






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor

31 May 2020 105

Usage Guideline

– Lynx_CanadianParty(Creditor)Rule :

For a Canadian Creditor, one of the following options should be present:1. Identification/Org ID/Any BIC AND [Creditor Account OR Identification/Org ID/Other]2. [Name AND Postal Address] AND [Creditor Account or Identification (Org or Private)]


– Lynx_CreditorNameMandatoryIfRule:

For Creditor, if AnyBIC is absent, Name is mandatory.This rule is inherited verbatim from CBPR+.




5.20.22 CreditorAccountXML Tag: CdtrAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the creditor to which a credit entry will be post-ed as a result of the payment transaction.

The CdtrAcct block contains the following elements (see datatype "CashAccount38__1" on page 42for details)



Page


Type <Tp> [0..1] 43


Name <Nm> [0..1] 43


5.20.23 UltimateCreditorXML Tag: UltmtCdtr

Presence: [0..1]

Definition: Ultimate party to which an amount of money is due.


Message Components

The UltmtCdtr block contains the following elements (see datatype "PartyIdentification135" onpage 162 for details)



Page

Name <Nm> [0..1] 162






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor

– Lynx_CanadianParty(UltimateCreditor)Rule :

For a Canadian Ultimate Creditor, both Name AND Postal Address should be present.

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor



5.20.24 InstructionForCreditorAgentXML 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 153 for details)



Page

Code <Cd> [0..1] 153


31 May 2020 107

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InstructionForCreditorAgent



– Lynx_Instruction for Creditor Agent1 Rule:

If CHQB is present, HOLD is not allowed. Otherwise, HOLD is optional.This rule is inherited verbatim from CBPR+.

If CHQB is present

Then HOLD is not allowed

Else HOLD is optional


– Lynx_Instruction for Creditor Agent2 Rule:

If CHQB is present, HOLD is not allowed. Otherwise, HOLD is optional.This rule is inherited verbatim from CBPR+.

If PHOB is present

Then TELB is not allowed

Else TELB is optional

5.20.25 InstructionForNextAgentXML Tag: InstrForNxtAgt

Presence: [0..*]

Definition: Further information related to the processing of the payment instruction that may need to beacted upon by the next agent.

The InstrForNxtAgt block contains the following elements (see datatype "InstructionForNextAgent1" onpage 154 for details)



Page

Code <Cd> [0..1] 154



Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InstructionForNextAgent


5.20.26 TaxXML Tag: Tax

Presence: [0..1]

Definition: Provides details on the tax.

The Tax block contains the following elements (see datatype "TaxInformation8" on page 229 for de-tails)



Page

Creditor <Cdtr> [0..1] 230

Debtor <Dbtr> [0..1] 230

AdministrationZone <AdmstnZone> [0..1] 231

ReferenceNumber <RefNb> [0..1] 231

Method <Mtd> [0..1] 231

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] 231

TotalTaxAmount <TtlTaxAmt> [0..1] 231

Date <Dt> [0..1] 232

SequenceNumber <SeqNb> [0..1] 232

Record <Rcrd> [0..*] 232


• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/Tax) is removed.

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

31 May 2020 109

Usage Guideline

The RmtInf block contains the following elements (see datatype "RemittanceInformation16" onpage 205 for details)



Page

Unstructured <Ustrd> [0..*] R[0..1] 205

Structured <Strd> [0..*] ! 206


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation

– Lynx_Unstructured_Structured_MutuallyExclusiveRule:

For Remittance Information, Unstructured and Structured are mutually exclusive.This rule is inherited verbatim from CBPR+.

5.20.28 InstructedAmountXML Tag: InstdAmt

Presence: [0..1]

Definition: Amount of money to be moved between the debtor and creditor, before deduction ofcharges, expressed in the currency as ordered by the initiating party.

Usage: This amount has to be transported unchanged through the transaction chain.

Datatype: "CBPR_Amount" on page 245

5.21 CreditorReferenceInformation2Definition: Reference information provided by the creditor to allow the identification of the underlyingdocuments.



Page

Type <Tp> [0..1] 110

Reference <Ref> [0..1] 111

Used in element(s)

"CreditorReferenceInformation" on page 219


Presence: [0..1]


Message Components

Definition: Specifies the type of creditor reference.

The Tp block contains the following elements (see datatype "CreditorReferenceType2" on page 112for details)



Page

CodeOrProprietary <CdOrPrtry> [1..1] 112


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


5.22 CreditorReferenceType1ChoiceDefinition: Specifies the type of document referred by the creditor.



Page

Code <Cd> {Or [1..1] 111


Used in element(s)

"CodeOrProprietary" on page 112


Presence: [1..1]

Definition: Type of creditor reference, in a coded form.

Datatype: "DocumentType3Code" on page 253

5.22.2 Proprietary

31 May 2020 111

Usage Guideline

XML Tag: Prtry

Presence: [1..1]

Definition: Creditor reference type, in a proprietary form.


5.23 CreditorReferenceType2Definition: Specifies the type of creditor reference.



Page



Used in element(s)

"Type" on page 110

5.23.1 CodeOrProprietaryXML 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 111 for details)



Page

Code <Cd> {Or [1..1] 111


5.23.2 IssuerXML Tag: Issr

Presence: [0..1]

Definition: Entity that assigns the credit reference type.


5.24 DateAndPlaceOfBirth1Definition: Date and place of birth of a person.


Message Components



Page

BirthDate <BirthDt> [1..1] 113

ProvinceOfBirth <PrvcOfBirth> [0..1] 113

CityOfBirth <CityOfBirth> [1..1] 113

CountryOfBirth <CtryOfBirth> [1..1] 113

Used in element(s)

"DateAndPlaceOfBirth" on page 178

5.24.1 BirthDateXML Tag: BirthDt

Presence: [1..1]

Definition: Date on which a person is born.


5.24.2 ProvinceOfBirthXML Tag: PrvcOfBirth

Presence: [0..1]

Definition: Province where a person was born.


5.24.3 CityOfBirthXML Tag: CityOfBirth

Presence: [1..1]

Definition: City where a person was born.


5.24.4 CountryOfBirthXML Tag: CtryOfBirth

Presence: [1..1]

Definition: Country where a person was born.

Datatype: "CountryCode" on page 251

5.25 DatePeriod2Definition: Range of time defined by a start date and an end date.

31 May 2020 113

Usage Guideline



Page

FromDate <FrDt> [1..1] 114

ToDate <ToDt> [1..1] 114

Used in element(s)

"FromToDate" on page 235

5.25.1 FromDateXML Tag: FrDt

Presence: [1..1]

Definition: Start date of the range.


5.25.2 ToDateXML Tag: ToDt

Presence: [1..1]

Definition: End date of the range.


5.26 DiscountAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 114

Amount <Amt> [1..1] 115

Used in element(s)

"DiscountAppliedAmount" on page 201, "DiscountAppliedAmount" on page 204


Presence: [0..1]

Definition: Specifies the type of the amount.


Message Components

The Tp block contains the following elements (see datatype "DiscountAmountType1Choice" onpage 115 for details)



Page

Code <Cd> {Or [1..1] 115


5.26.2 AmountXML Tag: Amt

Presence: [1..1]

Definition: Amount of money, which has been typed.

Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 241

5.27 DiscountAmountType1ChoiceDefinition: Specifies the amount type.



Page

Code <Cd> {Or [1..1] 115


Used in element(s)

"Type" on page 114


Presence: [1..1]

Definition: Specifies the amount type, in a coded form.

Datatype: "ExternalDiscountAmountType1Code" on page 260


Presence: [1..1]

Definition: Specifies the amount type, in a free-text form.


5.28 DocumentAdjustment1

31 May 2020 115

Usage Guideline

Definition: Set of elements used to provide information on the amount and reason of the document ad-justment.



Page

Amount <Amt> [1..1] 116

CreditDebitIndicator <CdtDbtInd> [0..1] 116

Reason <Rsn> [0..1] 116

AdditionalInformation <AddtlInf> [0..1] 116

Used in element(s)

"AdjustmentAmountAndReason" on page 202, "AdjustmentAmountAndReason" on page 204


Presence: [1..1]

Definition: Amount of money of the document adjustment.


5.28.2 CreditDebitIndicatorXML Tag: CdtDbtInd

Presence: [0..1]

Definition: Specifies whether the adjustment must be subtracted or added to the total amount.

Datatype: "CreditDebitCode" on page 252

5.28.3 ReasonXML Tag: Rsn

Presence: [0..1]

Definition: Specifies the reason for the adjustment.


5.28.4 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Provides further details on the document adjustment.


5.29 DocumentLineIdentification1


Message Components

Definition: Identifies the documents referred to in the remittance information.



Page

Type <Tp> [0..1] 117

Number <Nb> [0..1] 117

RelatedDate <RltdDt> [0..1] 117

Used in element(s)

"Identification" on page 118


Presence: [0..1]

Definition: Specifies the type of referred document line identification.

The Tp block contains the following elements (see datatype "DocumentLineType1" on page 119 fordetails)



Page



5.29.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Identification of the type specified for the referred document line.


5.29.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document line.


5.30 DocumentLineInformation1Definition: Provides document line information.

31 May 2020 117

Usage Guideline



Page

Identification <Id> [1..*] 118

Description <Desc> [0..1] 118

Amount <Amt> [0..1] 118

Used in element(s)

"LineDetails" on page 199


Presence: [1..*]

Definition: Provides identification of the document line.

The Id block contains the following elements (see datatype "DocumentLineIdentification1" onpage 116 for details)



Page

Type <Tp> [0..1] 117

Number <Nb> [0..1] 117


5.30.2 DescriptionXML Tag: Desc

Presence: [0..1]

Definition: Description associated with the document line.



Presence: [0..1]

Definition: Provides details on the amounts of the document line.


Message Components

The Amt block contains the following elements (see datatype "RemittanceAmount3" on page 203 fordetails)



Page

DuePayableAmount <DuePyblAmt> [0..1] 203

DiscountAppliedAmount <DscntApldAmt> [0..*] 204

CreditNoteAmount <CdtNoteAmt> [0..1] 204

TaxAmount <TaxAmt> [0..*] 204

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 204

RemittedAmount <RmtdAmt> [0..1] 205

5.31 DocumentLineType1Definition: Specifies the type of the document line identification.



Page



Used in element(s)

"Type" on page 117


Presence: [1..1]

Definition: Provides the type details of the referred document line identification.

The CdOrPrtry block contains the following elements (see datatype "DocumentLineType1Choice" onpage 120 for details)



Page

Code <Cd> {Or [1..1] 120



31 May 2020 119

Usage Guideline

Presence: [0..1]

Definition: Identification of the issuer of the reference document line identificationtype.


5.32 DocumentLineType1ChoiceDefinition: Specifies the type of the document line identification.



Page

Code <Cd> {Or [1..1] 120


Used in element(s)



Presence: [1..1]

Definition: Line identification type in a coded form.

Datatype: "ExternalDocumentLineType1Code" on page 261


Presence: [1..1]

Definition: Proprietary identification of the type of the remittance document.


5.33 FinancialIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the organisation identification scheme.



Page

Code <Cd> {Or [1..1] 121


Used in element(s)



Message Components


Presence: [1..1]


Datatype: "ExternalFinancialInstitutionIdentification1Code" on page 261


Presence: [1..1]



5.34 FinancialInstitutionIdentification18Definition: Specifies the details to identify a financial institution.



Page



LEI <LEI> [0..1] 122

Name <Nm> [0..1] 122


Other <Othr> [0..1] 123

Used in element(s)

"FinancialInstitutionIdentification" on page 24

5.34.1 BICFIXML Tag: BICFI

Presence: [0..1]

Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as describedin ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".

Datatype: "BICFIDec2014Identifier" on page 244

5.34.2 ClearingSystemMemberIdentificationXML Tag: ClrSysMmbId

Presence: [0..1]

31 May 2020 121

Usage Guideline

Definition: Information used to identify a member within a clearing system.

The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-fication2" on page 51 for details)



Page


MemberIdentification <MmbId> [1..1] 52


Presence: [0..1]

Definition: Legal entity identifier of the financial institution.



Presence: [0..1]




Presence: [0..1]



Message Components




Page







Floor <Flr> [0..1] 183


Room <Room> [0..1] 184







AddressLine <AdrLine> [0..7] 187


Presence: [0..1]

Definition: Unique identification of an agent, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericFinancialIdentification1" onpage 143 for details)



Page




31 May 2020 123

Usage Guideline

5.35 FinancialInstitutionIdentification18__1Definition: Specifies the details to identify a financial institution.



Page

BICFI <BICFI> [0..1] ! 124


LEI <LEI> [0..1] 125

Name <Nm> [0..1] ! 125


Other <Othr> [0..1] 133

Used in element(s)



Presence: [0..1]




• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/BICFI


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/BICFI


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/BICFI

Comment:Made mandatory to include the BIC of the Lynx Participant who will be credited at Bank of Canada to settle the payment.

• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/BICFI

Comment:Made mandatory to include the BIC of the Lynx Participant who will be debited at Bank of Canada to settle the payment.


Message Components


Presence: [0..1]


The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-fication2__1" on page 52 for details)



Page




Presence: [0..1]




Presence: [0..1]




Presence: [0..1]


31 May 2020 125

Usage Guideline

The PstlAdr block contains the following elements (see datatype "PostalAddress24__1" on page 188for details)



Page







Floor <Flr> [0..1] 191


Room <Room> [0..1] 191







AddressLine <AdrLine> [0..7] ! R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] 193


• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/PostalAddress

– Lynx_StructuredVsUnstructuredRule:

If PostalAddress is used and if AddressLine is present, then all other optional elements in PostalAddress must be absent.

• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/PostalAddress

– Lynx_TownNameAndCountryRule:

If PostalAddress is used, and if AddressLine is absent, then Town Name and Coun-try must be present.

• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress


Message Components



• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress



• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/PostalAddress



• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/PostalAddress



• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/PostalAddress



• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/PostalAddress


If PostalAddress is used and if AddressLine is present, then all other optional elements in PostalAddress must be absent.This rule is inherited verbatim from CBPR+.

• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/PostalAddress

31 May 2020 127

Usage Guideline


If "PostalAddress" is used, and if AddressLine is absent, then Town Name and Country must be present.This rule is inherited verbatim from CBPR+.

• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/PostalAddress

– StructuredVsUnstructuredRule:


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/PostalAddress

– TownNameAndCountryRule:


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/PostalAddress


Message Components



• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/PostalAddress
















31 May 2020 129

Usage Guideline



• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/PostalAddress


















• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent/FinancialInstitutionIdentification/PostalAddress


Message Components



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent/FinancialInstitutionIdentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/PostalAddress



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification/PostalAddress










31 May 2020 131

Usage Guideline









• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification/PostalAddress














Message Components







Presence: [0..1]





Page





• This element(pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/Other) is removed.

• This element(pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitu-tionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitu-tionIdentification/Other) is removed.

31 May 2020 133

Usage Guideline

• This element(pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialIn-stitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/Finan-cialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/Finan-cialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/Fi-nancialInstitutionIdentification/Other) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingA-gent1/FinancialInstitutionIdentification/Other) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/FinancialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAgent/FinancialInstitutionIdentification/Other) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/IntermediaryAgent1/FinancialInstitutionIdentification/Other) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/PreviousInstructingAgent1/FinancialInstitutionIdentification/Other) is re-moved.



5.36 FinancialInstitutionIdentification18__2Definition: Specifies the details to identify a financial institution.


Message Components



Page



LEI <LEI> [0..1] 135

Name <Nm> [0..1] 136


Other <Othr> [0..1] 137

Used in element(s)



Presence: [0..1]




Presence: [0..1]


The ClrSysMmbId block contains the following elements (see datatype "ClearingSystemMemberIdenti-fication2__2" on page 59 for details)



Page




Presence: [0..1]



31 May 2020 135

Usage Guideline


Presence: [0..1]




Presence: [0..1]





Page







Floor <Flr> [0..1] 191


Room <Room> [0..1] 191







AddressLine <AdrLine> [0..7] R[0..3] 193


• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/PostalAddress


Message Components



• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/PostalAddress




Presence: [0..1]





Page





• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/Finan-cialInstitutionIdentification/Other) is removed.

5.37 Garnishment3Definition: Provides remittance information about a payment for garnishment-related purposes.

31 May 2020 137

Usage Guideline



Page

Type <Tp> [1..1] 138

Garnishee <Grnshee> [0..1] 138

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 139


Date <Dt> [0..1] 139


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 140

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 140

Used in element(s)

"GarnishmentRemittance" on page 221


Presence: [1..1]

Definition: Specifies the type of garnishment.

The Tp block contains the following elements (see datatype "GarnishmentType1" on page 140 for de-tails)



Page



5.37.2 GarnisheeXML Tag: Grnshee

Presence: [0..1]

Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to thegarnisher.


Message Components

The Grnshee block contains the following elements (see datatype "PartyIdentification135" onpage 162 for details)



Page

Name <Nm> [0..1] 162





5.37.3 GarnishmentAdministratorXML Tag: GrnshmtAdmstr

Presence: [0..1]

Definition: Party on the credit side of the transaction who administers the garnishment on behalf of theultimate beneficiary.

The GrnshmtAdmstr block contains the following elements (see datatype "PartyIdentification135" onpage 162 for details)



Page

Name <Nm> [0..1] 162





5.37.4 ReferenceNumberXML Tag: RefNb

Presence: [0..1]

Definition: Reference information that is specific to the agency receiving the garnishment.


5.37.5 DateXML Tag: Dt

Presence: [0..1]

Definition: Date of payment which garnishment was taken from.

31 May 2020 139

Usage Guideline


5.37.6 RemittedAmountXML Tag: RmtdAmt

Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.37.7 FamilyMedicalInsuranceIndicatorXML Tag: FmlyMdclInsrncInd

Presence: [0..1]

Definition: Indicates if the person to whom the garnishment applies (that is, the ultimate debtor) hasfamily medical insurance coverage available.

Datatype: "TrueFalseIndicator" on page 284

5.37.8 EmployeeTerminationIndicatorXML Tag: MplyeeTermntnInd

Presence: [0..1]

Definition: Indicates if the employment of the person to whom the garnishment applies (that is, the ulti-mate debtor) has been terminated.

Datatype: "TrueFalseIndicator" on page 284

5.38 GarnishmentType1Definition: Specifies the type of garnishment.



Page



Used in element(s)

"Type" on page 138


Presence: [1..1]

Definition: Provides the type details of the garnishment.


Message Components

The CdOrPrtry block contains the following elements (see datatype "GarnishmentType1Choice" onpage 141 for details)



Page

Code <Cd> {Or [1..1] 141



Presence: [0..1]

Definition: Identification of the issuer of the garnishment type.


5.39 GarnishmentType1ChoiceDefinition: Specifies the type of garnishment.



Page

Code <Cd> {Or [1..1] 141


Used in element(s)



Presence: [1..1]

Definition: Garnishment type in a coded form.

Would suggest this to be an External Code List to contain:

GNCS Garnishment from a third party payer for Child Support

GNDP Garnishment from a Direct Payer for Child Support

GTPP Garnishment from a third party payer to taxing agency.

Datatype: "ExternalGarnishmentType1Code" on page 262


31 May 2020 141

Usage Guideline

Presence: [1..1]

Definition: Proprietary identification of the type of garnishment.


5.40 GenericAccountIdentification1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 22


Presence: [1..1]

Definition: Identification assigned by an institution.


5.40.2 SchemeNameXML Tag: SchmeNm

Presence: [0..1]

Definition: Name of the identification scheme.

The SchmeNm block contains the following elements (see datatype "AccountSchemeName1Choice"on page 23 for details)



Page

Code <Cd> {Or [1..1] 23



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAccount/Identification/Other/SchemeName) is removed.


Message Components

• This element(pacs.009.001.08/GroupHeader/SettlementInformation/SettlementAccount/Identi-fication/Other/SchemeName) is removed.


Presence: [0..1]

Definition: Entity that assigns the identification.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAccount/Identification/Other/Issuer) is removed.

• This element(pacs.009.001.08/GroupHeader/SettlementInformation/SettlementAccount/Identi-fication/Other/Issuer) is removed.

5.41 GenericFinancialIdentification1Definition: Information related to an identification of a financial institution.



Page




Used in element(s)

"Other" on page 133, "Other" on page 137, "Other" on page 123


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Presence: [0..1]


31 May 2020 143

Usage Guideline

The SchmeNm block contains the following elements (see datatype "FinancialIdentificationScheme-Name1Choice" on page 120 for details)



Page

Code <Cd> {Or [1..1] 121



Presence: [0..1]



5.42 GenericIdentification30Definition: Information related to an identification, for example, party identification or account identifica-tion.



Page




Used in element(s)

"Proprietary" on page 24


Presence: [1..1]

Definition: Proprietary information, often a code, issued by the data source scheme issuer.

Datatype: "Exact4AlphaNumericText" on page 256


Presence: [1..1]




Message Components


Presence: [0..1]

Definition: Short textual description of the scheme.


5.43 GenericOrganisationIdentification1Definition: Information related to an identification of an organisation.



Page


SchemeName <SchmeNm> [0..1] ! 145


Used in element(s)

"Other" on page 157


Presence: [1..1]

Definition: Identification assigned by an institution.



Presence: [0..1]


The SchmeNm block contains the following elements (see datatype "OrganisationIdentifica-tionSchemeName1Choice" on page 158 for details)



Page

Code <Cd> {Or [1..1] 158

Proprietary <Prtry> Or} [1..1] ! 158

31 May 2020 145

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/OrganisationIdentification/Other/SchemeName

Comment:CBPR+ makes this mandatory (Code only) because of translation from 50F in the MT message.


Presence: [0..1]



5.44 GenericPersonIdentification1Definition: Information related to an identification of a person.



Page




Used in element(s)

"Other" on page 178


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Presence: [0..1]



Message Components

The SchmeNm block contains the following elements (see datatype "PersonIdentificationScheme-Name1Choice" on page 179 for details)



Page

Code <Cd> {Or [1..1] 180



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/PrivateIdentification/Other/SchemeName

Comment:CBPR+ makes this mandatory (Code only) because of translation from 50F in the MT message.


Presence: [0..1]



5.45 GroupHeader93__1Definition: Set of characteristics shared by all individual transactions included in the message.



Page












31 May 2020 147

Usage Guideline

Rules

R13 TotalInterbankSettlementAmountAndDateRule ✓

If TotalInterbankSettlementAmount is present, then InterbankSettlementDate must be present.

Error handling:



– Error Text: Invalid message content for group header interbank settlement date.


– This rule(pacs.009.001.08/GroupHeader/TotalInterbankSettlementAmountAnd-DateRule) is removed.

Used in element(s)

"GroupHeader" on page 18

5.45.1 MessageIdentificationXML Tag: MsgId

Presence: [1..1]

Definition: Point to point reference, as assigned by the instructing party, and sent to the next party in thechain to unambiguously identify the message.

Usage: The instructing party has to make sure that MessageIdentification is unique per instructed partyfor a pre-agreed period.


5.45.2 CreationDateTimeXML Tag: CreDtTm

Presence: [1..1]

Definition: Date and time at which the message was created.


5.45.3 BatchBookingXML Tag: BtchBookg

Presence: [0..1]

Definition: Identifies whether a single entry per individual transaction or a batch entry for the sum of theamounts of all transactions within the group of a message is requested.

Usage: Batch booking is used to request and not order a possible batch booking.

Datatype: "BatchBookingIndicator" on page 245


Message Components


• This element(pacs.009.001.08/GroupHeader/BatchBooking) is removed.

5.45.4 NumberOfTransactionsXML Tag: NbOfTxs

Presence: [1..1]

Definition: Number of individual transactions contained in the message.

Datatype: "Max15NumericText" on page 274


• on pacs.009.001.08/GroupHeader/NumberOfTransactions

Single value: 1

5.45.5 ControlSumXML Tag: CtrlSum

Presence: [0..1]

Definition: Total of all individual amounts included in the message, irrespective of currencies.

Datatype: "DecimalNumber" on page 252


• This element(pacs.009.001.08/GroupHeader/ControlSum) is removed.

5.45.6 TotalInterbankSettlementAmountXML Tag: TtlIntrBkSttlmAmt

Presence: [0..1]

Definition: Total amount of money moved between the instructing agent and the instructed agent.

Datatype: "ActiveCurrencyAndAmount" on page 240


• This element(pacs.009.001.08/GroupHeader/TotalInterbankSettlementAmount) is removed.

5.45.7 InterbankSettlementDateXML Tag: IntrBkSttlmDt

Presence: [0..1]

31 May 2020 149

Usage Guideline

Definition: Date on which the amount of money ceases to be available to the agent that owes it andwhen the amount of money becomes available to the agent to which it is due.



• This element(pacs.009.001.08/GroupHeader/InterbankSettlementDate) is removed.

5.45.8 SettlementInformationXML Tag: SttlmInf

Presence: [1..1]

Definition: Specifies the details on how the settlement of the transaction(s) between the instructingagent and the instructed agent is completed.

The SttlmInf block contains the following elements (see datatype "SettlementInstruction7" onpage 208 for details)



Page

SettlementMethod <SttlmMtd> [1..1] ! 211

SettlementAccount <SttlmAcct> [0..1] ! 212

ClearingSystem <ClrSys> [0..1] ! 212

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] 213

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] 213

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] 214

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] 214

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] 215

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] 215

5.45.9 PaymentTypeInformationXML Tag: PmtTpInf

Presence: [0..1]

Definition: Set of elements used to further specify the type of transaction.


Message Components

The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation28" onpage 173 for details)



Page


ClearingChannel <ClrChanl> [0..1] 173

ServiceLevel <SvcLvl> [0..*] 173

LocalInstrument <LclInstrm> [0..1] 174

CategoryPurpose <CtgyPurp> [0..1] 174


• This element(pacs.009.001.08/GroupHeader/PaymentTypeInformation) is removed.

5.45.10 InstructingAgentXML Tag: InstgAgt

Presence: [0..1]

Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).

The InstgAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6" on page 24 for details)



Page




• This element(pacs.009.001.08/GroupHeader/InstructingAgent) is removed.

5.45.11 InstructedAgentXML Tag: InstdAgt

Presence: [0..1]

Definition: Agent that is instructed by the previous party in the chain to carry out the (set of) instruc-tion(s).

31 May 2020 151

Usage Guideline

The InstdAgt block contains the following elements (see datatype "BranchAndFinancialInstitutionIdenti-fication6" on page 24 for details)



Page




• This element(pacs.009.001.08/GroupHeader/InstructedAgent) is removed.

5.46 ImplementationSpecification1Definition: Identifies the implementation specification to which the ISO 20022 message conforms.



Page



Used in element(s)

"MarketPractice" on page 15

5.46.1 RegistryXML Tag: Regy

Presence: [1..1]

Definition: Name of the implementation specification registry in which the implementation specificationof the ISO 20022 message is maintained.

For example, "MyStandards".



Presence: [1..1]

Definition: Identifier which unambiguously identifies, within the implementation specification registry,the implementation specification to which the ISO 20022 message is compliant. This can be done via aURN. It can also contain a version number or date.

For instance, "2018-01-01 - Version 2" or "urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66".


Message Components


5.47 InstructionForCreditorAgent1Definition: Further information related to the processing of the payment instruction that may need to beacted 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'sagent.



Page

Code <Cd> [0..1] 153


Used in element(s)

"InstructionForCreditorAgent" on page 107


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 270

5.47.2 InstructionInformationXML Tag: InstrInf

Presence: [0..1]

Definition: Further information complementing the coded instruction or instruction to the creditor's agentthat is bilaterally agreed or specific to a user community.


5.48 InstructionForCreditorAgent2Definition: Further information related to the processing of the payment instruction that may need to beacted 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'sagent.



Page

Code <Cd> [0..1] 154


31 May 2020 153

Usage Guideline

Used in element(s)

"InstructionForCreditorAgent" on page 85


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.



Presence: [0..1]

Definition: Further information complementing the coded instruction or instruction to the creditor's agentthat is bilaterally agreed or specific to a user community.


5.49 InstructionForNextAgent1Definition: Further information related to the processing of the payment instruction that may need to beacted upon by an other agent. The instruction may relate to a level of service, or may be an instructionthat has to be executed by the creditor's agent, or may be information required by the other agent.



Page

Code <Cd> [0..1] 154


Used in element(s)

"InstructionForNextAgent" on page 85, "InstructionForNextAgent" on page 108


Presence: [0..1]

Definition: Coded information related to the processing of the payment instruction, provided by the initi-ating party, and intended for the next agent in the payment chain.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructionForNextA-gent/Code) is removed.


Message Components

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/InstructionForNextAgent/Code) is removed.


Presence: [0..1]

Definition: Further information complementing the coded instruction or instruction to the next agent thatis bilaterally agreed or specific to a user community.


5.50 LocalInstrument2ChoiceDefinition: Set of elements that further identifies the type of local instruments being requested by the ini-tiating party.



Page

Code <Cd> {Or [1..1] 155


Used in element(s)

"LocalInstrument" on page 174


Presence: [1..1]

Definition: Specifies the local instrument, as published in an external local instrument code list.

Datatype: "ExternalLocalInstrument1Code" on page 263


Presence: [1..1]

Definition: Specifies the local instrument, as a proprietary code.


5.51 LocalInstrument2Choice__1Definition: Set of elements that further identifies the type of local instruments being requested by the ini-tiating party.

31 May 2020 155

Usage Guideline



Page

Code <Cd> {Or [1..1] ! 156


Used in element(s)

"LocalInstrument" on page 176


Presence: [1..1]

Definition: Specifies the local instrument, as published in an external local instrument code list.

Datatype: "ExternalLocalInstrument1Code" on page 263


• This element(pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInforma-tion/LocalInstrument/Code) is removed.


Presence: [1..1]

Definition: Specifies the local instrument, as a proprietary code.


5.52 OrganisationIdentification29Definition: Unique and unambiguous way to identify an organisation.



Page

AnyBIC <AnyBIC> [0..1] 156

LEI <LEI> [0..1] 157

Other <Othr> [0..*] R[0..2] R[0..2] R[0..2] R[0..2] R[0..2] R[0..2] R[0..2] R[0..2] R[0..2] 157

Used in element(s)

"OrganisationIdentification" on page 160

5.52.1 AnyBIC


Message Components

XML Tag: AnyBIC

Presence: [0..1]

Definition: Business identification code of the organisation.

Datatype: "AnyBICDec2014Identifier" on page 244


Presence: [0..1]

Definition: Legal entity identification as an alternate identification for a party.



Presence: [0..*]

Definition: Unique identification of an organisation, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericOrganisationIdentification1" onpage 145 for details)



Page





• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/Identification/Or-ganisationIdentification/Other


31 May 2020 157

Usage Guideline

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAdministra-tor/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicee/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicer/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor/Identification/OrganisationIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/Identification/OrganisationIdentification/Other


5.53 OrganisationIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the organisation identification scheme.



Page

Code <Cd> {Or [1..1] 158


Used in element(s)



Presence: [1..1]


Datatype: "ExternalOrganisationIdentification1Code" on page 264


Presence: [1..1]



Message Components



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/OrganisationIdentification/Other/SchemeName/Proprietary

Comment:CBPR+ removes this

5.54 OtherContact1Definition: Communication device number or electronic address used for communication.



Page

ChannelType <ChanlTp> [1..1] 159


Used in element(s)

"Other" on page 62

5.54.1 ChannelTypeXML Tag: ChanlTp

Presence: [1..1]

Definition: Method used to contact the financial institution's contact for the specific tax region.



Presence: [0..1]

Definition: Communication value such as phone number or email address.


5.55 Party38ChoiceDefinition: Nature or use of the account.

31 May 2020 159

Usage Guideline



Page

OrganisationIdentification <OrgId> {Or [1..1] 160

PrivateIdentification <PrvtId> Or} [1..1] 160

Used in element(s)

"Identification" on page 168, "Identification" on page 163

5.55.1 OrganisationIdentificationXML Tag: OrgId

Presence: [1..1]

Definition: Unique and unambiguous way to identify an organisation.

The OrgId block contains the following elements (see datatype "OrganisationIdentification29" onpage 156 for details)



Page

AnyBIC <AnyBIC> [0..1] 156

LEI <LEI> [0..1] 157


5.55.2 PrivateIdentificationXML 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 "PersonIdentification13" on page 177for details)



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 178


5.56 Party44Choice__1Definition: Identification of a person, an organisation or a financial institution.


Message Components



Page



Used in element(s)

"From" on page 12, "From" on page 36, "To" on page 13, "To" on page 36

5.56.1 OrganisationIdentificationXML Tag: OrgId

Presence: [1..1]

Definition: Identification of a person or an organisation.

The OrgId block contains the following elements (see datatype "PartyIdentification135" on page 162for details)



Page

Name <Nm> [0..1] 162



CountryOfResidence <CtryOfRes> [0..1] 164



• This element(pacs.009.001.08/.header/From/OrganisationIdentification) is removed.

• This element(pacs.009.001.08/.header/Related/From/OrganisationIdentification) is removed.

• This element(pacs.009.001.08/.header/Related/To/OrganisationIdentification) is removed.

• This element(pacs.009.001.08/.header/To/OrganisationIdentification) is removed.

5.56.2 FinancialInstitutionIdentificationXML Tag: FIId

Presence: [1..1]

Definition: Identification of a financial institution.

31 May 2020 161

Usage Guideline

The FIId block contains the following elements (see datatype "BranchAndFinancialInstitutionIdentifica-tion6__1" on page 25 for details)



Page



5.57 PartyIdentification135Definition: Specifies the identification of a person or an organisation.



Page

Name <Nm> [0..1] 162





Used in element(s)

"Garnishee" on page 138, "GarnishmentAdministrator" on page 139, "InitiatingParty" on page 93,"Invoicee" on page 220, "Invoicer" on page 219, "OrganisationIdentification" on page 161, "Ulti-mateCreditor" on page 106, "UltimateDebtor" on page 93


Presence: [0..1]




Presence: [0..1]



Message Components




Page







Floor <Flr> [0..1] 183


Room <Room> [0..1] 184

PostCode <PstCd> [0..1] ! 184






AddressLine <AdrLine> [0..7] 187


Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

The Id block contains the following elements (see datatype "Party38Choice" on page 159 for details)



Page




• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/Identification

31 May 2020 163

Usage Guideline

Comment:For a Canadian Ultimate Debtor, it is recommended to include one Identification (either Org Id or Private ID).

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



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty/CountryOfResidence

Comment:Country of Residence (where the party physically lives) should be used only if different from PostalAdress/Country (country linked to the owner of the account used for contact purposes).

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/CountryOfResi-dence


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAdministra-tor/CountryOfResidence


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicee/CountryOfResidence


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicer/CountryOfResidence


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor/CountryOfResidence


Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/CountryOfResidence


5.57.5 ContactDetailsXML 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 "Contact4" on page 60 for details)



Page


Name <Nm> [0..1] 60












• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/InitiatingParty/ContactDetails) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/Con-tactDetails) is removed.

31 May 2020 165

Usage Guideline

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAd-ministrator/ContactDetails) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/Invoicer/ContactDetails) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateCreditor/ContactDetails) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateDebtor/ContactDetails) is removed.

5.58 PartyIdentification135__1Definition: Specifies the identification of a person or an organisation.



Page

Name <Nm> [0..1] 166




ContactDetails <CtctDtls> [0..1] ! 169

Used in element(s)

"Creditor" on page 105, "Debtor" on page 94


Presence: [0..1]




Presence: [0..1]



Message Components




Page







Floor <Flr> [0..1] 191


Room <Room> [0..1] 191







AddressLine <AdrLine> [0..7] R[0..3] R[0..3] 193


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor/PostalAddress

Comment:Structured Postal Address is recommended.

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/PostalAddress

Comment:Structured Postal Address is recommended.




31 May 2020 167

Usage Guideline











Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

The Id block contains the following elements (see datatype "Party38Choice" on page 159 for details)



Page



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



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor/CountryOfResidence


Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/CountryOfResidence


5.58.5 ContactDetailsXML 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 "Contact4" on page 60 for details)



Page


Name <Nm> [0..1] 60












• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/Creditor/ContactDetails) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/Debtor/ContactDetails) is removed.

31 May 2020 169

Usage Guideline

5.59 PaymentIdentification7__1Definition: Provides further means of referencing a payment transaction.



Page

InstructionIdentification <InstrId> [0..1] ! 170

EndToEndIdentification <EndToEndId> [1..1] ! 171

TransactionIdentification <TxId> [0..1] 172

UETR <UETR> [0..1] ! 172

ClearingSystemReference <ClrSysRef> [0..1] ! 172

Rules

R31 TransactionIdentificationPresenceRule

TransactionIdentification or UETR must be present. Both may be present

Error handling:



– Error Text: No transaction identification is present

Used in element(s)

"PaymentIdentification" on page 67

5.59.1 InstructionIdentificationXML Tag: InstrId

Presence: [0..1]

Definition: Unique identification, as assigned by an instructing party for an instructed party, to unam-biguously 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.



• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentification/InstructionI-dentification




Message Components

Synonym (MT 205 - field 20): Transaction Reference Number


Comment:Restricted to 16 characters for now to align with CBPR+. Restriction to be re-vis-ited after the SWIFT migration coexistence period ends.


– Lynx_InstructionIdentificationRule:

This field must not start or end with a slash '/' and must not contain two con-secutive slashes '//'.This rule is inherited verbatim from CBPR+.

5.59.2 EndToEndIdentificationXML Tag: EndToEndId

Presence: [1..1]

Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the trans-action. 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.

Usage: In case there are technical limitations to pass on multiple references, the end-to-end identifica-tion must be passed on throughout the entire end-to-end chain.



• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentification/EndToEndI-dentification

– Lynx_E2E_CORERule:

In the pacs.009 CORE, the E2E identification is provided by the Debtor (Agent).This rule is inherited verbatim from CBPR+.


– Lynx_E2E_COVRule:

In the pacs.009 COV, the E2E identification should transport the instruction identification of the underlying pacs.008.This rule is inherited verbatim from CBPR+.


Synonym (MT 205 - field 21): Related Reference

31 May 2020 171

Usage Guideline


Comment:In the pacs.009 CORE, the E2E identification is provided by the Debtor (Agent).In the pacs.009 COV, the E2E identification should transport the Instruction Iden-tification of the underlying pacs.008.

5.59.3 TransactionIdentificationXML Tag: TxId

Presence: [0..1]

Definition: Unique identification, as assigned by the first instructing agent, to unambiguously identify thetransaction that is passed on, unchanged, throughout the entire interbank chain.

Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating tothe transaction on the interbank level.

Usage: The instructing agent has to make sure that the transaction identification is unique for a pre-agreed period.


5.59.4 UETRXML Tag: UETR

Presence: [0..1]

Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.

Datatype: "UUIDv4Identifier" on page 284


• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentification/UETR


• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentification/UETR

– Lynx_UETR_COVRule:

In the pacs.009 COV, the UETR should transport the UETR of the underlying pacs.008.This rule is inherited verbatim from CBPR+.

5.59.5 ClearingSystemReferenceXML Tag: ClrSysRef

Presence: [0..1]

Definition: Unique reference, as assigned by a clearing system, to unambiguously identify the instruc-tion.



Message Components


• This element(pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentifica-tion/ClearingSystemReference) will be ignored by the Receiver.

• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentIdentification/ClearingSys-temReference

Comment:This element should not be populated by any Lynx Participants and should only be passed on if it was populated by a non-Canadian agent on an incoming pacs.009. It is not a reference assigned by Lynx. Therefore, from a Lynx perspective, it is ignored.

5.60 PaymentTypeInformation28Definition: Provides further details of the type of payment.



Page


ClearingChannel <ClrChanl> [0..1] 173

ServiceLevel <SvcLvl> [0..*] 173

LocalInstrument <LclInstrm> [0..1] 174

CategoryPurpose <CtgyPurp> [0..1] 174

Used in element(s)

"PaymentTypeInformation" on page 150

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


5.60.2 ClearingChannelXML Tag: ClrChanl

Presence: [0..1]

Definition: Specifies the clearing channel to be used to process the payment instruction.

Datatype: "ClearingChannel2Code" on page 249

5.60.3 ServiceLevel

31 May 2020 173

Usage Guideline

XML Tag: SvcLvl

Presence: [0..*]

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 207for details)



Page

Code <Cd> {Or [1..1] 207


5.60.4 LocalInstrumentXML 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 theservice or service level.

The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice" onpage 155 for details)



Page

Code <Cd> {Or [1..1] 155


5.60.5 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.


The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice" onpage 44 for details)



Page

Code <Cd> {Or [1..1] 45



Message Components

5.61 PaymentTypeInformation28__1Definition: Provides further details of the type of payment.



Page


ClearingChannel <ClrChanl> [0..1] ! 175

ServiceLevel <SvcLvl> [0..*] ! R[0..3] 175

LocalInstrument <LclInstrm> [0..1] ! 176

CategoryPurpose <CtgyPurp> [0..1] ! 177

Used in element(s)

"PaymentTypeInformation" on page 67

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


5.61.2 ClearingChannelXML Tag: ClrChanl

Presence: [0..1]

Definition: Specifies the clearing channel to be used to process the payment instruction.

Datatype: "ClearingChannel2Code" on page 249


• This element(pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInforma-tion/ClearingChannel) is removed.

5.61.3 ServiceLevelXML Tag: SvcLvl

Presence: [0..*]

Definition: Agreement under which or rules under which the transaction should be processed.

31 May 2020 175

Usage Guideline

The SvcLvl block contains the following elements (see datatype "ServiceLevel8Choice" on page 207for details)



Page

Code <Cd> {Or [1..1] 207



• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Ser-viceLevel


• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Ser-viceLevel

Comment:Must contain at least 1 GPI code.

5.61.4 LocalInstrumentXML 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 theservice or service level.

The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice__1" onpage 155 for details)



Page

Code <Cd> {Or [1..1] ! 156



• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/LocalIn-strument




Message Components

– Lynx_LocalInstrumentRule:

Local Instrument is to be used to indicate the settlement mechanism and settle-ment priority information as defined by Lynx. This is an alphanumeric element (numbers or letters). The first character represents the settlement mechanism and the next 2 characters, if present, represent the settlement priority for the Liquidity Savings Mechanism (LSM). Acceptable values are: - 1 (definition = Urgent Payment Mechanism - UPM, default priority) - 2 (definition = LSM, default priority) - 201 (definition = LSM, priority 1) - 203 (definition = LSM, priority 3) - 205 (definition = LSM, priority 5) - R (definition = Reserved Collateral Mechanism - RCM, default priori-ty)


Comment: (empty)

5.61.5 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.


The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice" onpage 44 for details)



Page

Code <Cd> {Or [1..1] 45



• on pacs.009.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Category-Purpose

Comment:Code is the preferred option.

5.62 PersonIdentification13Definition: Unique and unambiguous way to identify a person.

31 May 2020 177

Usage Guideline



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 178


Used in element(s)

"PrivateIdentification" on page 160

5.62.1 DateAndPlaceOfBirthXML Tag: DtAndPlcOfBirth

Presence: [0..1]

Definition: Date and place of birth of a person.

The DtAndPlcOfBirth block contains the following elements (see datatype "DateAndPlaceOfBirth1" onpage 112 for details)



Page

BirthDate <BirthDt> [1..1] 113

ProvinceOfBirth <PrvcOfBirth> [0..1] 113

CityOfBirth <CityOfBirth> [1..1] 113

CountryOfBirth <CtryOfBirth> [1..1] 113


Presence: [0..*]

Definition: Unique identification of a person, as assigned by an institution, using an identificationscheme.

The Othr block contains the following elements (see datatype "GenericPersonIdentification1" onpage 146 for details)



Page





Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/Identification/Pri-vateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAdministra-tor/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicee/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicer/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor/Identification/PrivateIdentification/Other


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/Identification/PrivateIdentification/Other


5.63 PersonIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification scheme.



Page

Code <Cd> {Or [1..1] 180


31 May 2020 179

Usage Guideline

Used in element(s)



Presence: [1..1]


Datatype: "ExternalPersonIdentification1Code" on page 264


Presence: [1..1]




• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/Identification/PrivateIdentification/Other/SchemeName/Proprietary

Comment:CBPR+ removes this

5.64 PostalAddress24Definition: Information that locates and identifies a specific address, as defined by postal services.


Message Components



Page







Floor <Flr> [0..1] 183


Room <Room> [0..1] 184

PostCode <PstCd> [0..1] ! 184






AddressLine <AdrLine> [0..7] ! 187

Used in element(s)

"PostalAddress" on page 122, "PostalAddress" on page 34, "PostalAddress" on page 162

5.64.1 AddressTypeXML Tag: AdrTp

Presence: [0..1]

Definition: Identifies the nature of the postal address.

The AdrTp block contains the following elements (see datatype "AddressType3Choice" on page 23for details)



Page

Code <Cd> {Or [1..1] 23


31 May 2020 181

Usage Guideline


• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateDebtor/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/InitiatingParty/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/Postal-Address/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAd-ministrator/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/Invoicee/PostalAddress/AddressType) is re-moved.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/Invoicer/PostalAddress/AddressType) is re-moved.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateCreditor/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateDebtor/PostalAddress/AddressType) is removed.


Presence: [0..1]




• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/Department) is removed.

5.64.3 SubDepartmentXML Tag: SubDept

Presence: [0..1]


Message Components

Definition: Identification of a sub-division of a large organisation or building.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/SubDepartment) is removed.

5.64.4 StreetNameXML Tag: StrtNm

Presence: [0..1]

Definition: Name of a street or thoroughfare.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/StreetName) is removed.

5.64.5 BuildingNumberXML Tag: BldgNb

Presence: [0..1]

Definition: Number that identifies the position of a building on a street.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/BuildingNumber) is removed.

5.64.6 BuildingNameXML Tag: BldgNm

Presence: [0..1]

Definition: Name of the building or house.


5.64.7 FloorXML Tag: Flr

Presence: [0..1]

Definition: Floor or storey within a building.

31 May 2020 183

Usage Guideline


5.64.8 PostBoxXML Tag: PstBx

Presence: [0..1]

Definition: Numbered box in a post office, assigned to a person or organisation, where letters are keptuntil called for.


5.64.9 RoomXML Tag: Room

Presence: [0..1]

Definition: Building room number.


5.64.10 PostCodeXML Tag: PstCd

Presence: [0..1]

Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address toassist the sorting of mail.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/PostCode) is removed.

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/PostalAddress/PostCode

Comment:It is recommended to add Post Code if available.

5.64.11 TownNameXML Tag: TwnNm

Presence: [0..1]

Definition: Name of a built-up area, with defined boundaries, and a local government.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/TownName) is removed.


Message Components

• on pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor/FinancialInstitu-tionIdentification/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UltimateDebtor/FinancialInstitu-tionIdentification/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCredit-Transfer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/PostalAd-dress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAdministra-tor/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicee/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicer/PostalAddress/TownName


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/PostalAddress/TownName


5.64.12 TownLocationNameXML Tag: TwnLctnNm

Presence: [0..1]

Definition: Specific location name within the town.


5.64.13 DistrictNameXML Tag: DstrctNm

Presence: [0..1]

Definition: Identifies a subdivision within a country sub-division.


31 May 2020 185

Usage Guideline

5.64.14 CountrySubDivisionXML Tag: CtrySubDvsn

Presence: [0..1]

Definition: Identifies a subdivision of a country such as state, region, county.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/CountrySubDivision) is removed.

5.64.15 CountryXML Tag: Ctry

Presence: [0..1]

Definition: Nation with its own government.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifi-cation/PostalAddress/Country) is removed.

• on pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor/FinancialInstitu-tionIdentification/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UltimateDebtor/FinancialInstitu-tionIdentification/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/InitiatingParty/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCredit-Transfer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/PostalAd-dress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAdministra-tor/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicee/PostalAddress/Country



Message Components

• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured/Invoicer/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateCreditor/PostalAddress/Country


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/UltimateDebtor/PostalAddress/Country


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



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateCreditor/Finan-cialInstitutionIdentification/PostalAddress/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UltimateDebtor/Finan-cialInstitutionIdentification/PostalAddress/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/InitiatingParty/PostalAddress/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/Garnishee/Postal-Address/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/GarnishmentRemittance/GarnishmentAd-ministrator/PostalAddress/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/Invoicee/PostalAddress/AddressLine) is re-moved.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/RemittanceInformation/Structured/Invoicer/PostalAddress/AddressLine) is re-moved.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateCreditor/PostalAddress/AddressLine) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/UltimateDebtor/PostalAddress/AddressLine) is removed.

31 May 2020 187

Usage Guideline

• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/BranchIdentifica-tion/PostalAddress/AddressLine

– NameAndAddressRestriction:

The rule restricts the total length of Name and Address information to a maximum of 4 lines of 35 characters in line with MT NameAndAddress format

If Name is longer than 35

Then AddressLine must not occur more than 2 times

Else AddressLine (3rd occurrence) will be ignored

5.65 PostalAddress24__1Definition: Information that locates and identifies a specific address, as defined by postal services.



Page







Floor <Flr> [0..1] 191


Room <Room> [0..1] 191







AddressLine <AdrLine> [0..7] ! R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] R[0..3] 193

Used in element(s)

"PostalAddress" on page 125, "PostalAddress" on page 136, "PostalAddress" on page 166


Message Components

5.65.1 AddressTypeXML Tag: AdrTp

Presence: [0..1]

Definition: Identifies the nature of the postal address.

The AdrTp block contains the following elements (see datatype "AddressType3Choice" on page 23for details)



Page

Code <Cd> {Or [1..1] 23



• This element(pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialIn-stitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/Fi-nancialInstitutionIdentification/PostalAddress/AddressType) is removed.



31 May 2020 189

Usage Guideline

• This element(pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingA-gent1/FinancialInstitutionIdentification/PostalAddress/AddressType) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/Creditor/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/CreditorAgent/FinancialInstitutionIdentification/PostalAddress/AddressType)is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/Debtor/PostalAddress/AddressType) is removed.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/DebtorAgent/FinancialInstitutionIdentification/PostalAddress/AddressType) isremoved.

• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/IntermediaryAgent1/FinancialInstitutionIdentification/PostalAddress/Ad-dressType) is removed.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomer-CreditTransfer/PreviousInstructingAgent1/FinancialInstitutionIdentification/PostalAd-dress/AddressType) is removed.




Presence: [0..1]



5.65.3 SubDepartment


Message Components

XML Tag: SubDept

Presence: [0..1]

Definition: Identification of a sub-division of a large organisation or building.


5.65.4 StreetNameXML Tag: StrtNm

Presence: [0..1]

Definition: Name of a street or thoroughfare.


5.65.5 BuildingNumberXML Tag: BldgNb

Presence: [0..1]

Definition: Number that identifies the position of a building on a street.


5.65.6 BuildingNameXML Tag: BldgNm

Presence: [0..1]

Definition: Name of the building or house.


5.65.7 FloorXML Tag: Flr

Presence: [0..1]

Definition: Floor or storey within a building.


5.65.8 PostBoxXML Tag: PstBx

Presence: [0..1]

Definition: Numbered box in a post office, assigned to a person or organisation, where letters are keptuntil called for.


5.65.9 RoomXML Tag: Room

31 May 2020 191

Usage Guideline

Presence: [0..1]

Definition: Building room number.


5.65.10 PostCodeXML Tag: PstCd

Presence: [0..1]

Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address toassist the sorting of mail.


5.65.11 TownNameXML Tag: TwnNm

Presence: [0..1]

Definition: Name of a built-up area, with defined boundaries, and a local government.


5.65.12 TownLocationNameXML Tag: TwnLctnNm

Presence: [0..1]

Definition: Specific location name within the town.


5.65.13 DistrictNameXML Tag: DstrctNm

Presence: [0..1]

Definition: Identifies a subdivision within a country sub-division.


5.65.14 CountrySubDivisionXML Tag: CtrySubDvsn

Presence: [0..1]

Definition: Identifies a subdivision of a country such as state, region, county.


5.65.15 CountryXML Tag: Ctry

Presence: [0..1]


Message Components

Definition: Nation with its own government.


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



• on pacs.009.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/PostalAddress/AddressLine


• on pacs.009.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress/AddressLine


• on pacs.009.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/PostalAddress/AddressLine


• on pacs.009.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitutionIdentifica-tion/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/Creditor/FinancialInstitutionIdentifi-cation/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/Debtor/FinancialInstitutionIdentifi-cation/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/PostalAddress/AddressLine

31 May 2020 193

Usage Guideline


• on pacs.009.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/PostalAddress/AddressLine






• on pacs.009.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/PostalAddress/AddressLine






• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Creditor/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/CreditorAgent/FinancialInstitutionIdentification/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/Debtor/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/DebtorAgent/FinancialInstitutionIdentification/PostalAddress/AddressLine


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/IntermediaryAgent1/FinancialInstitutionIdentification/PostalAddress/AddressLine






Message Components


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/PreviousInstructingAgent1/FinancialInstitutionIdentification/PostalAddress/AddressLine







– HVP_NameAndAddressRule:

The rule restricts the total length of Name and Address information to a maximum of 4 lines of 35 characters in line with MT NameAndAddress format

If Name is longer than 35

Then AddressLine must not occur more than 2 times

Else AddressLine can occur up to 3 times.

5.66 ProxyAccountIdentification1Definition: Information related to a proxy identification of the account.



Page

Type <Tp> [0..1] 195


Used in element(s)

"Proxy" on page 42


Presence: [0..1]

Definition: Type of the proxy identification.

31 May 2020 195

Usage Guideline

The Tp block contains the following elements (see datatype "ProxyAccountType1Choice" onpage 197 for details)



Page

Code <Cd> {Or [1..1] 197



Presence: [1..1]

Definition: Identification used to indicate the account identification under another specified name.


5.67 ProxyAccountIdentification1__1Definition: Information related to a proxy identification of the account.



Page

Type <Tp> [0..1] 196


Used in element(s)

"Proxy" on page 44


Presence: [0..1]

Definition: Type of the proxy identification.

The Tp block contains the following elements (see datatype "ProxyAccountType1Choice" onpage 197 for details)



Page

Code <Cd> {Or [1..1] 197


5.67.2 Identification


Message Components

XML Tag: Id

Presence: [1..1]

Definition: Identification used to indicate the account identification under another specified name.

Datatype: "CBPR_RestrictedFINXMax320Text_Extended" on page 248

5.68 ProxyAccountType1ChoiceDefinition: Specifies the scheme used for the identification of an account alias.



Page

Code <Cd> {Or [1..1] 197


Used in element(s)

"Type" on page 196, "Type" on page 195


Presence: [1..1]


Datatype: "ExternalProxyAccountType1Code" on page 265


Presence: [1..1]



5.69 Purpose2ChoiceDefinition: 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 isnot used for processing by any of the agents involved in the payment chain.



Page

Code <Cd> {Or [1..1] 198


31 May 2020 197

Usage Guideline

Used in element(s)

"Purpose" on page 86


Presence: [1..1]

Definition: Underlying reason for the payment transaction, as published in an external purpose code list.

Datatype: "ExternalPurpose1Code" on page 266


Presence: [1..1]

Definition: Purpose, in a proprietary form.


5.70 ReferredDocumentInformation7Definition: Set of elements used to identify the documents referred to in the remittance information.



Page

Type <Tp> [0..1] 198

Number <Nb> [0..1] 199


LineDetails <LineDtls> [0..*] 199

Used in element(s)

"ReferredDocumentInformation" on page 218


Presence: [0..1]

Definition: Specifies the type of referred document.


Message Components

The Tp block contains the following elements (see datatype "ReferredDocumentType4" on page 200for details)



Page



5.70.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Unique and unambiguous identification of the referred document.


5.70.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document.


5.70.4 LineDetailsXML Tag: LineDtls

Presence: [0..*]

Definition: Set of elements used to provide the content of the referred document line.

The LineDtls block contains the following elements (see datatype "DocumentLineInformation1" onpage 117 for details)



Page

Identification <Id> [1..*] 118

Description <Desc> [0..1] 118

Amount <Amt> [0..1] 118

5.71 ReferredDocumentType3ChoiceDefinition: Specifies the type of the document referred in the remittance information.

31 May 2020 199

Usage Guideline



Page

Code <Cd> {Or [1..1] 200


Used in element(s)



Presence: [1..1]

Definition: Document type in a coded form.

Datatype: "DocumentType6Code" on page 253


Presence: [1..1]

Definition: Proprietary identification of the type of the remittance document.


5.72 ReferredDocumentType4Definition: Specifies the type of the document referred in the remittance information.



Page



Used in element(s)

"Type" on page 198


Presence: [1..1]

Definition: Provides the type details of the referred document.


Message Components

The CdOrPrtry block contains the following elements (see datatype "ReferredDocumentType3Choice"on page 199 for details)



Page

Code <Cd> {Or [1..1] 200



Presence: [0..1]

Definition: Identification of the issuer of the reference document type.


5.73 RemittanceAmount2Definition: 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.



Page







Used in element(s)

"ReferredDocumentAmount" on page 218

5.73.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


5.73.2 DiscountAppliedAmount

31 May 2020 201

Usage Guideline

XML Tag: DscntApldAmt

Presence: [0..*]

Definition: Amount specified for the referred document is the amount of discount to be applied to theamount due and payable to the creditor.

The DscntApldAmt block contains the following elements (see datatype "DiscountAmountAndType1"on page 114 for details)



Page

Type <Tp> [0..1] 114

Amount <Amt> [1..1] 115

5.73.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount specified for the referred document is the amount of a credit note.


5.73.4 TaxAmountXML Tag: TaxAmt

Presence: [0..*]

Definition: Quantity of cash resulting from the calculation of the tax.

The TaxAmt block contains the following elements (see datatype "TaxAmountAndType1" onpage 224 for details)



Page

Type <Tp> [0..1] 224

Amount <Amt> [1..1] 224

5.73.5 AdjustmentAmountAndReasonXML Tag: AdjstmntAmtAndRsn

Presence: [0..*]

Definition: Specifies detailed information on the amount and reason of the document adjustment.


Message Components

The AdjstmntAmtAndRsn block contains the following elements (see datatype "DocumentAdjust-ment1" on page 115 for details)



Page

Amount <Amt> [1..1] 116


Reason <Rsn> [0..1] 116



Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.74 RemittanceAmount3Definition: 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.



Page







Used in element(s)

"Amount" on page 118

5.74.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


31 May 2020 203

Usage Guideline

5.74.2 DiscountAppliedAmountXML Tag: DscntApldAmt

Presence: [0..*]

Definition: Amount of discount to be applied to the amount due and payable to the creditor.

The DscntApldAmt block contains the following elements (see datatype "DiscountAmountAndType1"on page 114 for details)



Page

Type <Tp> [0..1] 114

Amount <Amt> [1..1] 115

5.74.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount of a credit note.



Presence: [0..*]

Definition: Amount of the tax.

The TaxAmt block contains the following elements (see datatype "TaxAmountAndType1" onpage 224 for details)



Page

Type <Tp> [0..1] 224

Amount <Amt> [1..1] 224

5.74.5 AdjustmentAmountAndReasonXML Tag: AdjstmntAmtAndRsn

Presence: [0..*]

Definition: Specifies detailed information on the amount and reason of the adjustment.


Message Components

The AdjstmntAmtAndRsn block contains the following elements (see datatype "DocumentAdjust-ment1" on page 115 for details)



Page

Amount <Amt> [1..1] 116


Reason <Rsn> [0..1] 116



Presence: [0..1]

Definition: Amount of money remitted.


5.75 RemittanceInformation16Definition: Information supplied to enable the matching/reconciliation of an entry with the items that thepayment is intended to settle, such as commercial invoices in an accounts' receivable system.



Page

Unstructured <Ustrd> [0..*] R[0..1] 205

Structured <Strd> [0..*] ! 206

Used in element(s)

"RemittanceInformation" on page 109

5.75.1 UnstructuredXML Tag: Ustrd

Presence: [0..*]

Definition: Information supplied to enable the matching/reconciliation of an entry with the items that thepayment is intended to settle, such as commercial invoices in an accounts' receivable system, in an un-structured form.



• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Unstructured

31 May 2020 205

Usage Guideline


5.75.2 StructuredXML Tag: Strd

Presence: [0..*]

Definition: Information supplied to enable the matching/reconciliation of an entry with the items thatthe payment is intended to settle, such as commercial invoices in an accounts' receivable system, in astructured form.

The Strd block contains the following elements (see datatype "StructuredRemittanceInformation16" onpage 217 for details)



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] 218

ReferredDocumentAmount <RfrdDocAmt> [0..1] 218

CreditorReferenceInformation <CdtrRefInf> [0..1] 219

Invoicer <Invcr> [0..1] 219

Invoicee <Invcee> [0..1] 220

TaxRemittance <TaxRmt> [0..1] 220

GarnishmentRemittance <GrnshmtRmt> [0..1] 221

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 221


• on pacs.009.001.08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTrans-fer/RemittanceInformation/Structured

– Lynx_RemittanceRules:

1. Use of Structured Remittance must be bilaterally or multilaterally agreed

2. Structured Remittance can be repeated, however the total business data for all occurrences (excluding tags) must not exceed 9,000 characters.

These rules are inherited verbatim from CBPR+.

5.76 RemittanceInformation2Definition: Information supplied to enable the matching of an entry with the items that the transfer is in-tended to settle.


Message Components



Page

Unstructured <Ustrd> [0..*] ! R[0..1] 207

Used in element(s)

"RemittanceInformation" on page 86

5.76.1 UnstructuredXML Tag: Ustrd

Presence: [0..*]

Definition: Information supplied to enable the matching of an entry with the items that the transfer is in-tended to settle, for example, commercial invoices in an accounts' receivable system in an unstructuredform.



• on pacs.009.001.08/CreditTransferTransactionInformation/RemittanceInformation/Unstruc-tured


• on pacs.009.001.08/CreditTransferTransactionInformation/RemittanceInformation/Unstruc-tured

Comment:This element may be used to communicate payments details related to the settlement of interest claims and compensation between Lynx participants.

5.77 ServiceLevel8ChoiceDefinition: Specifies the service level of the transaction.



Page

Code <Cd> {Or [1..1] 207


Used in element(s)

"ServiceLevel" on page 175, "ServiceLevel" on page 173


Presence: [1..1]

31 May 2020 207

Usage Guideline

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 267


Presence: [1..1]

Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.


5.78 SettlementDateTimeIndication1Definition: Information on the occurred settlement time(s) of the payment transaction.



Page

DebitDateTime <DbtDtTm> [0..1] 208

CreditDateTime <CdtDtTm> [0..1] 208

Used in element(s)

"SettlementTimeIndication" on page 68

5.78.1 DebitDateTimeXML Tag: DbtDtTm

Presence: [0..1]

Definition: Date and time at which a payment has been debited at the transaction administrator. In thecase of TARGET, the date and time at which the payment has been debited at the central bank, ex-pressed in Central European Time (CET).


5.78.2 CreditDateTimeXML Tag: CdtDtTm

Presence: [0..1]

Definition: Date and time at which a payment has been credited at the transaction administrator. In thecase of TARGET, the date and time at which the payment has been credited at the receiving centralbank, expressed in Central European Time (CET).


5.79 SettlementInstruction7Definition: Provides further details on the settlement of the instruction.


Message Components



Page

SettlementMethod <SttlmMtd> [1..1] ! 211

SettlementAccount <SttlmAcct> [0..1] ! 212

ClearingSystem <ClrSys> [0..1] ! 212

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] 213

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] 213

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] 214

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] 214

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] 215

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] 215

Rules

R50 ThirdReimbursementAgentRule ✓

If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and Instructe-dReimbursementAgent must both be present.

Error handling:



– Error Text: Invalid message content for third reimbursement agent.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/ThirdReim-bursementAgentRule) is removed.

R51 SettlementMethodAgentRule ✓

If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSys-tem are not allowed.

Error handling:



– Error Text: Invalid message content for settlement method INGA or INDA.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/Settlement-MethodAgentRule) is removed.

31 May 2020 209

Usage Guideline

R52 SettlementMethodCoverRule ✓

If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not al-lowed.

Error handling:



– Error Text: Invalid message content for cover settlement method with settlement accountand clearing system.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/Settlement-MethodCoverRule) is removed.

R53 SettlementMethodCoverAgentRule ✓

If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or InstructingRe-imbursementAgent must be present.

Error handling:



– Error Text: Invalid message content for cover settlement method and reimbursement agents.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/Settlement-MethodCoverAgentRule) is removed.

R54 SettlementMethodClearingRule ✓

If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)are not allowed.

Error handling:



– Error Text: Invalid message content for settlement method CLRG.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/Settlement-MethodClearingRule) is removed.

R55 InstructingReimbursementAgentAccountRule ✓

If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgentmust be present.


Message Components

Error handling:



– Error Text: Invalid message content for instructing reimbursement agent account.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/InstructingRe-imbursementAgentAccountRule) is removed.

R56 InstructedReimbursementAgentAccountRule ✓

If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgentmust be present.

Error handling:



– Error Text: Invalid message content for instructed reimbursement agent account.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/InstructedReim-bursementAgentAccountRule) is removed.

R57 ThirdReimbursementAgentAccountRule ✓

If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must bepresent.

Error handling:



– Error Text: Invalid message content for third reimbursement agent account.


– This rule(pacs.009.001.08/GroupHeader/SettlementInformation/ThirdReim-bursementAgentAccountRule) is removed.

Used in element(s)

"SettlementInformation" on page 150

5.79.1 SettlementMethodXML Tag: SttlmMtd

Presence: [1..1]

31 May 2020 211

Usage Guideline

Definition: Method used to settle the (batch of) payment instructions.

Datatype: "SettlementMethod1Code" on page 280

5.79.2 SettlementAccountXML Tag: SttlmAcct

Presence: [0..1]

Definition: A specific purpose account used to post debit and credit entries as a result of the transaction.

The SttlmAcct block contains the following elements (see datatype "CashAccount38" on page 40for details)



Page


Type <Tp> [0..1] 41


Name <Nm> [0..1] 41



• This element(pacs.009.001.08/GroupHeader/SettlementInformation/SettlementAccount) is re-moved.

5.79.3 ClearingSystemXML Tag: ClrSys

Presence: [0..1]


The ClrSys block contains the following elements (see datatype "ClearingSystemIdentification3Choice"on page 50 for details)



Page

Code <Cd> {Or [1..1] ! 51



• on pacs.009.001.08/GroupHeader/SettlementInformation/ClearingSystem


Message Components


5.79.4 InstructingReimbursementAgentXML Tag: InstgRmbrsmntAgt

Presence: [0..1]

Definition: Agent through which the instructing agent will reimburse the instructed agent.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only Instruct-ingReimbursementAgent must be used.

The InstgRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialIn-stitutionIdentification6" on page 24 for details)



Page




• This element(pacs.009.001.08/GroupHeader/SettlementInformation/InstructingReimbursemen-tAgent) is removed.

5.79.5 InstructingReimbursementAgentAccountXML Tag: InstgRmbrsmntAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the instructing reimbursement agent account atits servicing agent in the payment chain.

The InstgRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount38" onpage 40 for details)



Page


Type <Tp> [0..1] 41


Name <Nm> [0..1] 41


31 May 2020 213

Usage Guideline


• This element(pacs.009.001.08/GroupHeader/SettlementInformation/InstructingReimbursemen-tAgentAccount) is removed.

5.79.6 InstructedReimbursementAgentXML Tag: InstdRmbrsmntAgt

Presence: [0..1]

Definition: Agent at which the instructed agent will be reimbursed.

Usage: If InstructedReimbursementAgent contains a branch of the InstructedAgent, then the party in In-structedAgent will claim reimbursement from that branch/will be paid by that branch.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only Instruct-ingReimbursementAgent must be used.

The InstdRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialIn-stitutionIdentification6" on page 24 for details)



Page




• This element(pacs.009.001.08/GroupHeader/SettlementInformation/InstructedReimbursement-Agent) is removed.

5.79.7 InstructedReimbursementAgentAccountXML Tag: InstdRmbrsmntAgtAcct

Presence: [0..1]

Definition: Unambiguous identification of the account of the instructed reimbursement agent account atits servicing agent in the payment chain.


Message Components

The InstdRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount38" onpage 40 for details)



Page


Type <Tp> [0..1] 41


Name <Nm> [0..1] 41



• This element(pacs.009.001.08/GroupHeader/SettlementInformation/InstructedReimbursement-AgentAccount) is removed.

5.79.8 ThirdReimbursementAgentXML Tag: ThrdRmbrsmntAgt

Presence: [0..1]

Definition: Agent at which the instructed agent will be reimbursed.

Usage: If ThirdReimbursementAgent contains a branch of the InstructedAgent, then the party in In-structedAgent will claim reimbursement from that branch/will be paid by that branch.

The ThrdRmbrsmntAgt block contains the following elements (see datatype "BranchAndFinancialInsti-tutionIdentification6" on page 24 for details)



Page




• This element(pacs.009.001.08/GroupHeader/SettlementInformation/ThirdReimbursementA-gent) is removed.

5.79.9 ThirdReimbursementAgentAccountXML Tag: ThrdRmbrsmntAgtAcct

Presence: [0..1]

31 May 2020 215

Usage Guideline

Definition: Unambiguous identification of the account of the third reimbursement agent account at itsservicing agent in the payment chain.

The ThrdRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount38" onpage 40 for details)



Page


Type <Tp> [0..1] 41


Name <Nm> [0..1] 41



• This element(pacs.009.001.08/GroupHeader/SettlementInformation/ThirdReimbursementA-gentAccount) is removed.

5.80 SettlementTimeRequest2__1Definition: Provides information on the requested settlement time(s) of the payment instruction.



Page

CLSTime <CLSTm> [0..1] ! 216

TillTime <TillTm> [0..1] 217

FromTime <FrTm> [0..1] 217

RejectTime <RjctTm> [0..1] 217

Used in element(s)

"SettlementTimeRequest" on page 69

5.80.1 CLSTimeXML Tag: CLSTm

Presence: [0..1]

Definition: Time by which the amount of money must be credited, with confirmation, to the CLS Bank'saccount at the central bank.

Usage: Time must be expressed in Central European Time (CET).

Datatype: "CBPR_Time" on page 248


Message Components


• This element(pacs.009.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/CLSTime) will be ignored by the Receiver.

• on pacs.009.001.08/CreditTransferTransactionInformation/SettlementTimeRequest/CLSTime

Synonym (MT 205 - field 13C - CLSTIME): Time Indication

5.80.2 TillTimeXML Tag: TillTm

Presence: [0..1]

Definition: Time until when the payment may be settled.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/TillTime) will be ignored by the Receiver.

5.80.3 FromTimeXML Tag: FrTm

Presence: [0..1]

Definition: Time as from when the payment may be settled.


5.80.4 RejectTimeXML Tag: RjctTm

Presence: [0..1]

Definition: Time by when the payment must be settled to avoid rejection.



• This element(pacs.009.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/RejectTime) will be ignored by the Receiver.

5.81 StructuredRemittanceInformation16Definition: Information supplied to enable the matching/reconciliation of an entry with the items thatthe payment is intended to settle, such as commercial invoices in an accounts' receivable system, in astructured form.

31 May 2020 217

Usage Guideline



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] 218

ReferredDocumentAmount <RfrdDocAmt> [0..1] 218

CreditorReferenceInformation <CdtrRefInf> [0..1] 219

Invoicer <Invcr> [0..1] 219

Invoicee <Invcee> [0..1] 220

TaxRemittance <TaxRmt> [0..1] 220

GarnishmentRemittance <GrnshmtRmt> [0..1] 221

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 221

Used in element(s)

"Structured" on page 206

5.81.1 ReferredDocumentInformationXML Tag: RfrdDocInf

Presence: [0..*]

Definition: Provides the identification and the content of the referred document.

The RfrdDocInf block contains the following elements (see datatype "ReferredDocumentInformation7"on page 198 for details)



Page

Type <Tp> [0..1] 198

Number <Nb> [0..1] 199


LineDetails <LineDtls> [0..*] 199

5.81.2 ReferredDocumentAmountXML Tag: RfrdDocAmt

Presence: [0..1]

Definition: Provides details on the amounts of the referred document.


Message Components

The RfrdDocAmt block contains the following elements (see datatype "RemittanceAmount2" onpage 201 for details)



Page







5.81.3 CreditorReferenceInformationXML Tag: CdtrRefInf

Presence: [0..1]

Definition: Reference information provided by the creditor to allow the identification of the underlyingdocuments.

The CdtrRefInf block contains the following elements (see datatype "CreditorReferenceInformation2"on page 110 for details)



Page

Type <Tp> [0..1] 110

Reference <Ref> [0..1] 111

5.81.4 InvoicerXML Tag: Invcr

Presence: [0..1]

Definition: Identification of the organisation issuing the invoice, when it is different from the creditor orultimate creditor.

31 May 2020 219

Usage Guideline

The Invcr block contains the following elements (see datatype "PartyIdentification135" on page 162for details)



Page

Name <Nm> [0..1] 162





5.81.5 InvoiceeXML Tag: Invcee

Presence: [0..1]

Definition: Identification of the party to whom an invoice is issued, when it is different from the debtor orultimate debtor.

The Invcee block contains the following elements (see datatype "PartyIdentification135" on page 162for details)



Page

Name <Nm> [0..1] 162





5.81.6 TaxRemittanceXML Tag: TaxRmt

Presence: [0..1]

Definition: Provides remittance information about a payment made for tax-related purposes.


Message Components

The TaxRmt block contains the following elements (see datatype "TaxInformation7" on page 226 fordetails)



Page






Method <Mtd> [0..1] 228



Date <Dt> [0..1] 228



5.81.7 GarnishmentRemittanceXML Tag: GrnshmtRmt

Presence: [0..1]

Definition: Provides remittance information about a payment for garnishment-related purposes.

The GrnshmtRmt block contains the following elements (see datatype "Garnishment3" on page 137for details)



Page

Type <Tp> [1..1] 138

Garnishee <Grnshee> [0..1] 138

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 139


Date <Dt> [0..1] 139


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 140

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 140

5.81.8 AdditionalRemittanceInformation

31 May 2020 221

Usage Guideline

XML Tag: AddtlRmtInf

Presence: [0..3]

Definition: Additional information, in free text form, to complement the structured remittance information.


5.82 SupplementaryData1Definition: Additional information that can not be captured in the structured fields and/or any other spe-cific block.



Page



Rules

R47 SupplementaryDataRule

This component may not be used without the explicit approval of a SEG and submission to theRA of ISO 20022 compliant structure(s) to be used in the Envelope element.


Used in element(s)

"SupplementaryData" on page 21, "SupplementaryData" on page 89

5.82.1 PlaceAndNameXML Tag: PlcAndNm

Presence: [0..1]

Definition: Unambiguous reference to the location where the supplementary data must be inserted inthe message instance.

In the case of XML, this is expressed by a valid XPath.


5.82.2 EnvelopeXML Tag: Envlp

Presence: [1..1]

Definition: Technical element wrapping the supplementary data.

5.83 TaxAmount2Definition: Set of elements used to provide information on the tax amount(s) of tax record.


Message Components



Page

Rate <Rate> [0..1] 223

TaxableBaseAmount <TaxblBaseAmt> [0..1] 223

TotalAmount <TtlAmt> [0..1] 223

Details <Dtls> [0..*] 223

Used in element(s)

"TaxAmount" on page 237

5.83.1 RateXML Tag: Rate

Presence: [0..1]

Definition: Rate used to calculate the tax.

Datatype: "PercentageRate" on page 278

5.83.2 TaxableBaseAmountXML Tag: TaxblBaseAmt

Presence: [0..1]

Definition: Amount of money on which the tax is based.


5.83.3 TotalAmountXML Tag: TtlAmt

Presence: [0..1]

Definition: Total amount that is the result of the calculation of the tax for the record.


5.83.4 DetailsXML Tag: Dtls

Presence: [0..*]

Definition: Set of elements used to provide details on the tax period and amount.

31 May 2020 223

Usage Guideline

The Dtls block contains the following elements (see datatype "TaxRecordDetails2" on page 238 fordetails)



Page

Period <Prd> [0..1] 238

Amount <Amt> [1..1] 239

5.84 TaxAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 224

Amount <Amt> [1..1] 224

Used in element(s)

"TaxAmount" on page 202, "TaxAmount" on page 204


Presence: [0..1]

Definition: Specifies the type of the amount.

The Tp block contains the following elements (see datatype "TaxAmountType1Choice" on page 224for details)



Page

Code <Cd> {Or [1..1] 225



Presence: [1..1]

Definition: Amount of money, which has been typed.


5.85 TaxAmountType1Choice


Message Components

Definition: Specifies the amount type.



Page

Code <Cd> {Or [1..1] 225


Used in element(s)

"Type" on page 224


Presence: [1..1]

Definition: Specifies the amount type, in a coded form.

Datatype: "ExternalTaxAmountType1Code" on page 268


Presence: [1..1]

Definition: Specifies the amount type, in a free-text form.


5.86 TaxAuthorisation1Definition: Details of the authorised tax paying party.



Page

Title <Titl> [0..1] 225

Name <Nm> [0..1] 226

Used in element(s)

"Authorisation" on page 234

5.86.1 TitleXML Tag: Titl

Presence: [0..1]

Definition: Title or position of debtor or the debtor's authorised representative.


31 May 2020 225

Usage Guideline


Presence: [0..1]

Definition: Name of the debtor or the debtor's authorised representative.


5.87 TaxInformation7Definition: Details about tax paid, or to be paid, to the government in accordance with the law, includingpre-defined parameters such as thresholds and type of account.



Page






Method <Mtd> [0..1] 228



Date <Dt> [0..1] 228



Used in element(s)

"TaxRemittance" on page 220


Presence: [0..1]

Definition: Party on the credit side of the transaction to which the tax applies.


Message Components

The Cdtr block contains the following elements (see datatype "TaxParty1" on page 232 for details)



Page

TaxIdentification <TaxId> [0..1] 233

RegistrationIdentification <RegnId> [0..1] 233

TaxType <TaxTp> [0..1] 233


Presence: [0..1]

Definition: Identifies 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 233 for details)



Page




Authorisation <Authstn> [0..1] 234


Presence: [0..1]

Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to thetaxing authority.

The UltmtDbtr block contains the following elements (see datatype "TaxParty2" on page 233 for de-tails)



Page





5.87.4 AdministrationZone

31 May 2020 227

Usage Guideline

XML Tag: AdmstnZone

Presence: [0..1]

Definition: Territorial part of a country to which the tax payment is related.



Presence: [0..1]

Definition: Tax reference information that is specific to a taxing agency.


5.87.6 MethodXML Tag: Mtd

Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.87.7 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.87.8 TotalTaxAmountXML Tag: TtlTaxAmt

Presence: [0..1]

Definition: Total amount of money as result of the calculation of the tax.



Presence: [0..1]

Definition: Date by which tax is due.


5.87.10 SequenceNumberXML Tag: SeqNb

Presence: [0..1]


Message Components

Definition: Sequential number of the tax report.

Datatype: "Number" on page 277

5.87.11 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

The Rcrd block contains the following elements (see datatype "TaxRecord2" on page 235 for details)



Page

Type <Tp> [0..1] 236

Category <Ctgy> [0..1] 236

CategoryDetails <CtgyDtls> [0..1] 236

DebtorStatus <DbtrSts> [0..1] 236

CertificateIdentification <CertId> [0..1] 237

FormsCode <FrmsCd> [0..1] 237

Period <Prd> [0..1] 237

TaxAmount <TaxAmt> [0..1] 237


5.88 TaxInformation8Definition: Details about tax paid, or to be paid, to the government in accordance with the law, includingpre-defined parameters such as thresholds and type of account.

31 May 2020 229

Usage Guideline



Page





Method <Mtd> [0..1] 231



Date <Dt> [0..1] 232



Used in element(s)

"Tax" on page 109


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 232 for details)



Page





Presence: [0..1]

Definition: Party on the debit side of the transaction to which the tax applies.


Message Components

The Dbtr block contains the following elements (see datatype "TaxParty2" on page 233 for details)



Page





5.88.3 AdministrationZoneXML Tag: AdmstnZone

Presence: [0..1]

Definition: Territorial part of a country to which the tax payment is related.



Presence: [0..1]

Definition: Tax reference information that is specific to a taxing agency.


5.88.5 MethodXML Tag: Mtd

Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.88.6 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.88.7 TotalTaxAmountXML Tag: TtlTaxAmt

Presence: [0..1]

Definition: Total amount of money as result of the calculation of the tax.


31 May 2020 231

Usage Guideline


Presence: [0..1]

Definition: Date by which tax is due.


5.88.9 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 277

5.88.10 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

The Rcrd block contains the following elements (see datatype "TaxRecord2" on page 235 for details)



Page

Type <Tp> [0..1] 236






Period <Prd> [0..1] 237



5.89 TaxParty1Definition: Details about the entity involved in the tax paid or to be paid.


Message Components



Page




Used in element(s)

"Creditor" on page 226, "Creditor" on page 230

5.89.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the creditor.


5.89.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.


5.89.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


5.90 TaxParty2Definition: Details about the entity involved in the tax paid or to be paid.



Page





31 May 2020 233

Usage Guideline

Used in element(s)

"Debtor" on page 227, "Debtor" on page 230, "UltimateDebtor" on page 227

5.90.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the debtor.


5.90.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.


5.90.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


5.90.4 AuthorisationXML 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 225for details)



Page

Title <Titl> [0..1] 225

Name <Nm> [0..1] 226

5.91 TaxPeriod2Definition: Period of time details related to the tax payment.


Message Components



Page

Year <Yr> [0..1] 235

Type <Tp> [0..1] 235

FromToDate <FrToDt> [0..1] 235

Used in element(s)

"Period" on page 237, "Period" on page 238

5.91.1 YearXML Tag: Yr

Presence: [0..1]

Definition: Year related to the tax payment.



Presence: [0..1]

Definition: Identification of the period related to the tax payment.

Datatype: "TaxRecordPeriod1Code" on page 282

5.91.3 FromToDateXML 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 "DatePeriod2" on page 113 for de-tails)



Page

FromDate <FrDt> [1..1] 114

ToDate <ToDt> [1..1] 114

5.92 TaxRecord2Definition: Set of elements used to define the tax record.

31 May 2020 235

Usage Guideline



Page

Type <Tp> [0..1] 236






Period <Prd> [0..1] 237



Used in element(s)

"Record" on page 229, "Record" on page 232


Presence: [0..1]

Definition: High level code to identify the type of tax details.


5.92.2 CategoryXML Tag: Ctgy

Presence: [0..1]

Definition: Specifies the tax code as published by the tax authority.


5.92.3 CategoryDetailsXML Tag: CtgyDtls

Presence: [0..1]

Definition: Provides further details of the category tax code.


5.92.4 DebtorStatusXML Tag: DbtrSts

Presence: [0..1]


Message Components

Definition: Code provided by local authority to identify the status of the party that has drawn up the set-tlement document.


5.92.5 CertificateIdentificationXML Tag: CertId

Presence: [0..1]

Definition: Identification number of the tax report as assigned by the taxing authority.


5.92.6 FormsCodeXML Tag: FrmsCd

Presence: [0..1]

Definition: Identifies, in a coded form, on which template the tax report is to be provided.


5.92.7 PeriodXML 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 "TaxPeriod2" on page 234 for details)



Page

Year <Yr> [0..1] 235

Type <Tp> [0..1] 235



Presence: [0..1]

Definition: Set of elements used to provide information on the amount of the tax record.

31 May 2020 237

Usage Guideline

The TaxAmt block contains the following elements (see datatype "TaxAmount2" on page 222 for de-tails)



Page

Rate <Rate> [0..1] 223

TaxableBaseAmount <TaxblBaseAmt> [0..1] 223

TotalAmount <TtlAmt> [0..1] 223

Details <Dtls> [0..*] 223

5.92.9 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Further details of the tax record.


5.93 TaxRecordDetails2Definition: Provides information on the individual tax amount(s) per period of the tax record.



Page

Period <Prd> [0..1] 238

Amount <Amt> [1..1] 239

Used in element(s)

"Details" on page 223

5.93.1 PeriodXML Tag: Prd

Presence: [0..1]

Definition: Set of elements used to provide details on the period of time related to the tax payment.


Message Components

The Prd block contains the following elements (see datatype "TaxPeriod2" on page 234 for details)



Page

Year <Yr> [0..1] 235

Type <Tp> [0..1] 235



Presence: [1..1]

Definition: Underlying tax amount related to the specified period.


31 May 2020 239

Usage Guideline

6 Message Datatypes

Note The following chapter identifies the datatypes that are used in the message.

6.1 ActiveCurrencyAndAmountDefinition: A number of monetary units specified in an active currency where the unit of currency is ex-plicit and compliant with ISO 4217.

Type: Amount

This data type must be used with the following XML Attributes:

Attribute Tag Datatype

Currency Ccy "ActiveCurrencyCode" on page 240

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R14 CurrencyAmount ✓

The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

Error handling:


– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

Used in element(s)

"TotalInterbankSettlementAmount" on page 149

6.2 ActiveCurrencyCodeDefinition: A code allocated to a currency by a Maintenance Agency under an international identificationscheme as described in the latest edition of the international standard ISO 4217 "Codes for the repre-sentation of currencies and funds".

Type: Code

Format

pattern [A-Z]{3,3}


Message Datatypes

Rules

R15 ActiveCurrency ✓

The currency code must be a valid active currency code, not yet withdrawn on the day the mes-sage containing the currency is exchanged. Valid active currency codes are registered with theISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and are not yet with-drawn on the day the message containing the Currency is exchanged.

Error handling:



– Error Text: Invalid currency code

Used in attribute(s)

"ActiveCurrencyAndAmount" on page 240

Restricts

"ParentCurrencyCode" on page 278

6.3 ActiveOrHistoricCurrencyAndAmountDefinition: 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



Currency Ccy "ActiveOrHistoricCurrencyCode" on page 242

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R48 CurrencyAmount ✓


Note: The decimal separator is a dot.

Error handling:



– Error Text: Invalid currency code or too many decimal digits.

31 May 2020 241

Usage Guideline

Used in element(s)

"Amount" on page 116, "Amount" on page 115, "Amount" on page 224, "Amount" on page 239, "Cred-itNoteAmount" on page 202, "CreditNoteAmount" on page 204, "DuePayableAmount" on page 201,"DuePayableAmount" on page 203, "RemittedAmount" on page 203, "RemittedAmount" on page 205,"RemittedAmount" on page 140, "TaxableBaseAmount" on page 223, "TotalAmount" on page 223, "To-talTaxAmount" on page 228, "TotalTaxAmount" on page 231, "TotalTaxableBaseAmount" on page 228,"TotalTaxableBaseAmount" on page 231

6.4 ActiveOrHistoricCurrencyCodeDefinition: A code allocated to a currency by a Maintenance Agency under an international identificationscheme, as described in the latest edition of the international standard ISO 4217 "Codes for the repre-sentation of currencies and funds".

Type: Code

Format

pattern [A-Z]{3,3}

Rules

R34 ActiveOrHistoricCurrency ✓

The Currency Code must be registered, or have already been registered. Valid active or historiccurrency 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:



– Error Text: Invalid currency code.

Used in element(s)

"Currency" on page 43, "Currency" on page 41


"ActiveOrHistoricCurrencyAndAmount" on page 241

Restricts

"ParentCurrencyCode" on page 278

6.5 AddressType2CodeDefinition: Specifies the type of address.

Type: Code

Code Name Definition

ADDR Postal Address is the complete postal address.


Message Datatypes


BIZZ Business Address is the business address.

DLVY DeliveryTo Address is the address to which deliveryis to take place.

HOME Residential Address is the home address.

MLTO MailTo Address is the address to which mail issent.

PBOX POBox Address is a postal office (PO) box.

Used in element(s)

"Code" on page 23

Restricts

"AddressTypeCode" on page 243

6.6 AddressTypeCodeDefinition: Specifies the type of address.

Type: Code


ADDR Postal Address is the complete postal address.

BIZZ Business Address is the business address.

DLVY DeliveryTo Address is the address to which deliveryis to take place.

HOME Residential Address is the home address.

MLTO MailTo Address is the address to which mail issent.

PBOX POBox Address is a postal office (PO) box.

Is restricted by

"AddressType2Code" on page 242

6.7 AmountDirectionCodeDefinition: Specifies if an operation is an increase or a decrease or the result of a reversal operation.

Type: Code


CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

RVCD ReversalCredit Debit entry used to reverse a previouslybooked credit entry.

31 May 2020 243

Usage Guideline


RVDB ReversalDebit Credit entry used to reverse a previouslybooked debit entry.

Is restricted by

"CreditDebitCode" on page 252

6.8 AnyBICDec2014IdentifierDefinition: Code allocated to a financial or non-financial institution by the ISO 9362 Registration Authori-ty, as described in ISO 9362: 2014 - "Banking - Banking telecommunication messages - Business iden-tifier code (BIC)".

Type: IdentifierSet

Format

pattern [A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}

Rules

R49 AnyBIC ✓

Only a valid Business identifier code is allowed. Business identifier codes for financial or non-financial institutions are registered and published by the ISO 9362 Registration Authority in theISO directory of BICs, and consists of eight (8) or eleven (11) contiguous characters.

Error handling:



– Error Text: Invalid BIC.

Used in element(s)

"AnyBIC" on page 156

6.9 BICFIDec2014IdentifierDefinition: Code allocated to a financial institution by the ISO 9362 Registration Authority as describedin ISO 9362: 2014 - "Banking - Banking telecommunication messages - Business identifier code (BIC)".

Type: IdentifierSet

Format

pattern [A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}

Rules

R32 BICFI ✓


Message Datatypes

Valid BICs for financial institutions are registered and published by the ISO 9362 RegistrationAuthority in the ISO directory of BICs, and consist of eight (8) or eleven (11) contiguous charac-ters.

Error handling:



– Error Text: Invalid FI BIC.

Used in element(s)

"BICFI" on page 124, "BICFI" on page 135, "BICFI" on page 121

6.10 BatchBookingIndicatorDefinition: Identifies whether the sending party requests a single debit or credit entry per individualtransaction 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 thebatch or message is requested.

Meaning When False: Identifies that a single entry for each of the transactions in the batch or messageis requested.

Used in element(s)

"BatchBooking" on page 148

6.11 BusinessMessagePriorityCodeDefinition: Specifies the priority levels for the BusinessMessage.

The different priorities are typically user / service / implementation dependent. The semantics of the dif-ferent values for a Mesage (Set) need to be defined by the relevant user community (SEG.).

Type: Code

Rules

R3 ValidationByTable


Used in element(s)

"Priority" on page 39

6.12 CBPR_AmountDefinition:

31 May 2020 245

Usage Guideline

This datatype has been created by the Publisher of this Usage Guideline.

Type: Amount



Ccy Ccy "CurrencyCode" on page 252

Format

minInclusive 0

totalDigits 14

fractionDigits 5

Rules

R45 CurrencyAmount


Note: The decimal separator is a dot

Error handling:



– Error Text: Invalid currency code or too many decimal digits

Used in element(s)

"InstructedAmount" on page 110

6.13 CBPR_Amount_2decimalsDefinition:

Type: Amount



Ccy Ccy "CurrencyCode" on page 252

Usage Guideline restrictions for this at-tribute

• on pacs.009.001.08/CreditTransfer-TransactionInformation/InterbankSet-tlementAmount/Ccy

Single value: CAD


Message Datatypes

Format

minInclusive 0

totalDigits 14

fractionDigits 2

Rules

R29 CurrencyAmount


Note: The decimal separator is a dot

Error handling:



– Error Text: Invalid currency code or too many decimal digits

Used in element(s)

"InterbankSettlementAmount" on page 68

6.14 CBPR_DateTimeDefinition:


Type: DateTime

Format

pattern .*(\+|-)((0[0-9])|(1[0-3])):[0-5][0-9]

Used in element(s)

"CreationDate" on page 39, "CreationDateTime" on page 148

6.15 CBPR_RestrictedFINXMax28TextDefinition: Specifies a character string with a maximum length of 28 characters limited to character setX, that is, a-z A-Z / - ? : ( ) . , ' + .


Type: Text

Format

minLength 1

31 May 2020 247

Usage Guideline

maxLength 28

pattern [0-9a-zA-Z/\-\?:\.,'\+ ]{1,28}

Used in element(s)

"MemberIdentification" on page 59

6.16 CBPR_RestrictedFINXMax320Text_ExtendedDefinition: Specifies a character string with a maximum length of 35 characters limited to character setX, that is, a-z A-Z / - ? : ( ) . , ' + . !#$%&*=^_`{|}~";<>@[\]


Type: Text

Format

pattern [0-9a-zA-Z/\-\?:\.,'\+ !#$%&\*=^_`\{\|\}~";<>@\[\\\]]{1,320}

Used in element(s)


6.17 CBPR_TimeDefinition:


Type: Time

Format

pattern .*(\+|-)((0[0-9])|(1[0-3])):[0-5][0-9]

Used in element(s)

"CLSTime" on page 216, "FromTime" on page 217, "RejectTime" on page 217, "TillTime" on page 217

6.18 CBPR__RestrictedFINXMax28TextDefinition: Specifies a character string with a maximum length of 28 characters limited to character setX, that is, a-z A-Z / - ? : ( ) . , ' + .


Type: Text


Message Datatypes

Format

minLength 1

maxLength 28

pattern [0-9a-zA-Z/\-\?:\.,'\+ ]{1,28}

Used in element(s)

"MemberIdentification" on page 55

6.19 ClearingChannel2CodeDefinition: Specifies the clearing channel for the routing of the transaction, as part of the payment typeidentification.

Type: Code


BOOK BookTransfer Payment through internal book transfer.

MPNS MassPaymentNetSystem Clearing channel is a mass payment netsettlement system.

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross set-tlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net settle-ment system.

Used in element(s)

"ClearingChannel" on page 175, "ClearingChannel" on page 173

Restricts

"ClearingChannelCode" on page 249

6.20 ClearingChannelCodeDefinition: Specifies the clearing channel for the routing of the transaction, as part of the payment typeidentification.

Type: Code


BOOK BookTransfer Payment through internal book transfer.

MPNS MassPaymentNetSystem Clearing channel is a mass payment netsettlement system.

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross set-tlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net settle-ment system.

31 May 2020 249

Usage Guideline

Is restricted by

"ClearingChannel2Code" on page 249

6.21 CopyDuplicate1CodeDefinition: Specifies if this document is a copy, a duplicate, or a duplicate of a copy.

Type: Code


CODU CopyDuplicate Message is being sent as a copy to aparty other than the account owner, forinformation purposes and the messageis a duplicate of a message previouslysent.

Usage Guideline restrictions for thiscode

• on pacs.009.001.08/.head-er/CopyDuplicate/CopyDupli-cate

Unknown type of restriction [prac-tice:InternalCommentRestriction]:

• on pacs.009.001.08/.header/Re-lated/CopyDuplicate/CopyDu-plicate


COPY Copy Message is being sent as a copy to aparty other than the account owner, forinformation purposes.


• on pacs.009.001.08/.head-er/CopyDuplicate/Copy


• on pacs.009.001.08/.header/Re-lated/CopyDuplicate/Copy


DUPL Duplicate Message is for information/confirmationpurposes. It is a duplicate of a messagepreviously sent.


Message Datatypes

Used in element(s)

"CopyDuplicate" on page 39

Restricts

"CopyDuplicateCode" on page 251

6.22 CopyDuplicateCodeDefinition: Specifies if this document is a copy, a duplicate, or a duplicate of a copy.

Type: Code


CODU CopyDuplicate Message is being sent as a copy to aparty other than the account owner, forinformation purposes and the messageis a duplicate of a message previouslysent.

COPY Copy Message is being sent as a copy to aparty other than the account owner, forinformation purposes.

DUPL Duplicate Message is for information/confirmationpurposes. It is a duplicate of a messagepreviously sent.

Is restricted by

"CopyDuplicate1Code" on page 250

6.23 CountryCodeDefinition: 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: Code

Format

pattern [A-Z]{2,2}

Rules

R33 Country ✓

The code is checked against the list of country names obtained from the United Nations (ISO3166, Alpha-2 code).

Error handling:



– Error Text: Invalid Country Code.

31 May 2020 251

Usage Guideline

Used in element(s)

"Country" on page 192, "Country" on page 186, "CountryOfBirth" on page 113, "CountryOfResidence"on page 168, "CountryOfResidence" on page 164

6.24 CreditDebitCodeDefinition: Specifies if an operation is an increase or a decrease.

Type: Code


CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

Used in element(s)

"CreditDebitIndicator" on page 116

Restricts

"AmountDirectionCode" on page 243

6.25 CurrencyCodeDefinition: Code allocated to a currency, by a maintenance agency, under an international identificationscheme 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 MaintenanceAgency, and consist of three contiguous letters.

Type: Code

Format

pattern [A-Z]{3,3}

Rules


Must be a valid currency code which is registered with the ISO 4217 Maintenance Agency, andconsist of three contiguous letters.



"CBPR_Amount_2decimals" on page 246, "CBPR_Amount" on page 245

6.26 DecimalNumberDefinition: Number of objects represented as a decimal number, for example 0.75 or 45.6.

Type: Quantity


Message Datatypes

Format

totalDigits 18

fractionDigits 17

Used in element(s)

"ControlSum" on page 149

6.27 DocumentType3CodeDefinition: Specifies a type of financial or commercial document.

Type: Code


DISP DispatchAdvice Document is a dispatch advice.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-arranged foreign exchange transactionto which the payment transaction refers.

PUOR PurchaseOrder Document is a purchase order.

RADM RemittanceAdviceMessage Document is a remittance advice sentseparately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment instruc-tion to which the current payment in-struction is related, for example, in acover scenario.

SCOR StructuredCommunicationReference Document is a structured communica-tion reference provided by the creditor toidentify the referred transaction.

Used in element(s)

"Code" on page 111

Restricts

"DocumentTypeCode" on page 254

6.28 DocumentType6CodeDefinition: Specifies a type of financial or commercial document.

Type: Code


AROI AccountReceivableOpenItem Document is a payment that applies to aspecific source document.

BOLD BillOfLading Document is a shipping notice.

CINV CommercialInvoice Document is an invoice.

31 May 2020 253

Usage Guideline


CMCN CommercialContract Document is an agreement between theparties, stipulating the terms and condi-tions of the delivery of goods or services.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the finalamount settled for a commercial transac-tion.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.


DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the finalamount settled for a commercial transac-tion.

HIRI HireInvoice Document is an invoice for the hiring ofhuman resources or renting goods orequipment.

MSIN MeteredServiceInvoice Document is an invoice claiming pay-ment for the supply of metered services,for example gas or electricity supplied toa fixed meter.


SBIN SelfBilledInvoice Document is an invoice issued by thedebtor.

SOAC StatementOfAccount Document is a statement of the transac-tions posted to the debtor's account atthe supplier.

TSUT TradeServicesUtilityTransaction Document is a transaction identifier asassigned by the Trade Services Utility.

VCHR Voucher Document is an electronic payment doc-ument.

Used in element(s)

"Code" on page 200

Restricts

"DocumentTypeCode" on page 254

6.29 DocumentTypeCodeDefinition: Specifies a type of financial or commercial document.

Type: Code


AROI AccountReceivableOpenItem Document is a payment that applies to aspecific source document.

BOLD BillOfLading Document is a shipping notice.

CINV CommercialInvoice Document is an invoice.


Message Datatypes


CMCN CommercialContract Document is an agreement between theparties, stipulating the terms and condi-tions of the delivery of goods or services.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the finalamount settled for a commercial transac-tion.

CRCP CustomerReceipt When the Sale System requires the POIsystem to print the Customer receipt.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.


DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the finalamount settled for a commercial transac-tion.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-arranged foreign exchange transactionto which the payment transaction refers.

HIRI HireInvoice Document is an invoice for the hiring ofhuman resources or renting goods orequipment.

HRCP CashierReceipt When the Sale system print the Cashiercopy of the Payment receipt.

JNRL Journal When the POI or the Sale System wantsto store a message on the journal printeror electronic journal of the Sale Terminal(it is sometimes a Sale Logging/JournalPrinter).

MSIN MeteredServiceInvoice Document is an invoice claiming pay-ment for the supply of metered services,for example gas or electricity supplied toa fixed meter.


RADM RemittanceAdviceMessage Document is a remittance advice sentseparately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment instruc-tion to which the current payment in-struction is related, for example, in acover scenario.

SBIN SelfBilledInvoice Document is an invoice issued by thedebtor.

SCOR StructuredCommunicationReference Document is a structured communica-tion reference provided by the creditor toidentify the referred transaction.

SOAC StatementOfAccount Document is a statement of the transac-tions posted to the debtor's account atthe supplier.

SRCP SaleReceipt When the Sale System requires the POIsystem to print the Sale receipt.

31 May 2020 255

Usage Guideline


TSUT TradeServicesUtilityTransaction Document is a transaction identifier asassigned by the Trade Services Utility.

VCHR Voucher Document is an electronic payment doc-ument.

Is restricted by

"DocumentType3Code" on page 253, "DocumentType6Code" on page 253

6.30 Exact4AlphaNumericTextDefinition: Specifies an alphanumeric string with a length of 4 characters.

Type: Text

Format

pattern [a-zA-Z0-9]{4}

Used in element(s)


6.31 ExternalAccountIdentification1CodeDefinition: Specifies the external account identification scheme name code in the format of characterstring with a maximum length of 4 characters.

The list of valid codes is an external code list published separately.

External code sets can be downloaded from www.iso20022.org.

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 23

Restricts

"ExternalAccountIdentificationCode" on page 256

6.32 ExternalAccountIdentificationCodeDefinition: Specifies the external account identification scheme name code in the format of characterstring with a maximum length of 4 characters.


Message Datatypes



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalAccountIdentification1Code" on page 256

6.33 ExternalCashAccountType1CodeDefinition: Specifies the nature, or use, of the cash account in the format of character string with a maxi-mum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 44

Restricts

"ExternalCashAccountTypeCode" on page 257

6.34 ExternalCashAccountTypeCodeDefinition: Specifies the nature, or use, of the cash account in the format of character string with a maxi-mum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

31 May 2020 257

Usage Guideline

Is restricted by

"ExternalCashAccountType1Code" on page 257

6.35 ExternalCashClearingSystem1CodeDefinition: Specifies the cash clearing system, as published in an external cash clearing system codelist.


Type: Code

Format

minLength 1

maxLength 3

Used in element(s)

"Code" on page 51

Restricts

"ExternalCashClearingSystemCode" on page 258

6.36 ExternalCashClearingSystemCodeDefinition: Specifies the cash clearing system, as published in an external cash clearing system codelist.


Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalCashClearingSystem1Code" on page 258

6.37 ExternalCategoryPurpose1CodeDefinition: Specifies the category purpose, as published in an external category purpose code list.


Type: Code

Format

minLength 1


Message Datatypes

maxLength 4

Used in element(s)

"Code" on page 45

Restricts

"ExternalCategoryPurposeCode" on page 259

6.38 ExternalCategoryPurposeCodeDefinition: Specifies the category purpose, as published in an external category purpose code list.


Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalCategoryPurpose1Code" on page 258

6.39 ExternalClearingSystemIdentification1CodeDefinition: Specifies the clearing system identification code, as published in an external clearing systemidentification code list.


Type: Code

Format

minLength 1

maxLength 5

Used in element(s)

"Code" on page 45

Restricts

"ExternalClearingSystemIdentificationCode" on page 259

6.40 ExternalClearingSystemIdentificationCodeDefinition: Specifies the clearing system identification code, as published in an external clearing systemidentification code list.

31 May 2020 259

Usage Guideline


Type: Code

Format

minLength 1

maxLength 5

Is restricted by

"ExternalClearingSystemIdentification1Code" on page 259

6.41 ExternalDiscountAmountType1CodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 115

Restricts

"ExternalDiscountAmountTypeCode" on page 260

6.42 ExternalDiscountAmountTypeCodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4


Message Datatypes

Is restricted by

"ExternalDiscountAmountType1Code" on page 260

6.43 ExternalDocumentLineType1CodeDefinition: Specifies the document line type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 120

Restricts

"ExternalDocumentLineTypeCode" on page 261

6.44 ExternalDocumentLineTypeCodeDefinition: Specifies the document line type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalDocumentLineType1Code" on page 261

6.45 ExternalFinancialInstitutionIdentification1CodeDefinition: Specifies the external financial institution identification scheme name code in the format ofcharacter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

31 May 2020 261

Usage Guideline

Used in element(s)

"Code" on page 121

Restricts

"ExternalFinancialInstitutionIdentificationCode" on page 262

6.46 ExternalFinancialInstitutionIdentificationCodeDefinition: Specifies the external financial institution identification scheme name code in the format ofcharacter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalFinancialInstitutionIdentification1Code" on page 261

6.47 ExternalGarnishmentType1CodeDefinition: Specifies the garnishment type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 141

Restricts

"ExternalGarnishmentTypeCode" on page 262

6.48 ExternalGarnishmentTypeCodeDefinition: Specifies the garnishment type as published in an external document type code list.

Type: Code


Message Datatypes

Format

minLength 1

maxLength 4

Is restricted by

"ExternalGarnishmentType1Code" on page 262

6.49 ExternalLocalInstrument1CodeDefinition: Specifies the external local instrument code in the format of character string with a maximumlength of 35 characters.



Type: Code

Format

minLength 1

maxLength 35

Used in element(s)

"Code" on page 156, "Code" on page 155

Restricts

"ExternalLocalInstrumentCode" on page 263

6.50 ExternalLocalInstrumentCodeDefinition: Specifies the external local instrument code in the format of character string with a maximumlength of 35 characters.



Type: Code

Format

minLength 1

maxLength 35

Is restricted by

"ExternalLocalInstrument1Code" on page 263

31 May 2020 263

Usage Guideline

6.51 ExternalOrganisationIdentification1CodeDefinition: Specifies the external organisation identification scheme name code in the format of charac-ter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 158

Restricts

"ExternalOrganisationIdentificationCode" on page 264

6.52 ExternalOrganisationIdentificationCodeDefinition: Specifies the external organisation identification scheme name code in the format of charac-ter string with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalOrganisationIdentification1Code" on page 264

6.53 ExternalPersonIdentification1CodeDefinition: Specifies the external person identification scheme name code in the format of characterstring with a maximum length of 4 characters.



Type: Code


Message Datatypes

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 180

Restricts

"ExternalPersonIdentificationCode" on page 265

6.54 ExternalPersonIdentificationCodeDefinition: Specifies the external person identification scheme name code in the format of characterstring with a maximum length of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalPersonIdentification1Code" on page 264

6.55 ExternalProxyAccountType1CodeDefinition: Specifies the external proxy account type code, as published in the proxy account type exter-nal code set.


Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 197

Restricts

"ExternalProxyAccountTypeCode" on page 266

31 May 2020 265

Usage Guideline

6.56 ExternalProxyAccountTypeCodeDefinition: Specifies the external proxy account type code, as published in the proxy account type exter-nal code set.


Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalProxyAccountType1Code" on page 265

6.57 ExternalPurpose1CodeDefinition: Specifies the external purpose code in the format of character string with a maximum lengthof 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 198

Restricts

"ExternalPurposeCode" on page 266

6.58 ExternalPurposeCodeDefinition: Specifies the external purpose code in the format of character string with a maximum lengthof 4 characters.



Type: Code


Message Datatypes

Format

minLength 1

maxLength 4

Is restricted by

"ExternalPurpose1Code" on page 266

6.59 ExternalServiceLevel1CodeDefinition: Specifies the external service level code in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 207

Restricts

"ExternalServiceLevelCode" on page 267

6.60 ExternalServiceLevelCodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalServiceLevel1Code" on page 267

31 May 2020 267

Usage Guideline

6.61 ExternalTaxAmountType1CodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 225

Restricts

"ExternalTaxAmountTypeCode" on page 268

6.62 ExternalTaxAmountTypeCodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalTaxAmountType1Code" on page 268

6.63 IBAN2007IdentifierDefinition: An identifier used internationally by financial institutions to uniquely identify the account ofa customer at a financial institution, as described in the latest edition of the international standard ISO13616: 2007 - "Banking and related financial services - International Bank Account Number (IBAN)".

Type: IdentifierSet

Format

pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}


Message Datatypes

Rules

R46 IBAN ✓

A valid IBAN consists of all three of the following components: Country Code, check digits andBBAN.

Error handling:



– Error Text: Invalid IBAN format or invalid check digits.

Used in element(s)

"IBAN" on page 22

6.64 ISODateDefinition: 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 - W3CRecommendation 28 October 2004" which is aligned with ISO 8601.

Type: Date

Used in element(s)

"BirthDate" on page 113, "Date" on page 228, "Date" on page 139, "Date" on page 232, "FromDate" onpage 114, "InterbankSettlementDate" on page 149, "InterbankSettlementDate" on page 68, "Related-Date" on page 117, "RelatedDate" on page 199, "ToDate" on page 114, "Year" on page 235

6.65 ISODateTimeDefinition: A particular point in the progression of time defined by a mandatory date and a mandatorytime component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ), local time withUTC 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 - W3CRecommendation 28 October 2004" which is aligned with ISO 8601.

Note on the time format:

1) beginning / end of calendar day

00:00:00 = the beginning of a calendar day

24:00:00 = the end of a calendar day

2) fractions of second in time format

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

31 May 2020 269

Usage Guideline

Used in element(s)

"CreditDateTime" on page 208, "DebitDateTime" on page 208

6.66 Instruction3CodeDefinition: Specifies further instructions concerning the processing of a payment instruction, provided bythe sending clearing agent to the next agent(s).

Type: Code


CHQB PayCreditorByCheque (Ultimate) creditor must be paid bycheque.


• on pacs.009.001.08/Credit-TransferTransactionInforma-tion/UnderlyingCustomerCred-itTransfer/InstructionForCredi-torAgent/Code/PayCreditorBy-Cheque

Synonym (MT 103 - field 23E - codeCHQB): Instruction Code

HOLD HoldCashForCreditor Amount of money must be held for the(ultimate) creditor, who will call. Pay onidentification.


• on pacs.009.001.08/Credit-TransferTransactionInforma-tion/UnderlyingCustomerCred-itTransfer/InstructionForCred-itorAgent/Code/HoldCashFor-Creditor

Synonym (MT 103 - field 23E - codeHOLD): Instruction Code

PHOB PhoneBeneficiary Please advise/contact (ultimate) credi-tor/claimant by phone.


• on pacs.009.001.08/Credit-TransferTransactionInforma-tion/UnderlyingCustomerCred-itTransfer/InstructionForCredi-


Message Datatypes


torAgent/Code/PhoneBeneficia-ry

Synonym (MT 103 - field 23E - codePHOB): Instruction Code

TELB Telecom Please advise/contact (ultimate) credi-tor/claimant by the most efficient meansof telecommunication.


• on pacs.009.001.08/Credit-TransferTransactionInforma-tion/UnderlyingCustomerCred-itTransfer/InstructionForCredi-torAgent/Code/Telecom

Synonym (MT 103 - field 23E - codeTELB): Instruction Code

Used in element(s)

"Code" on page 153

Restricts

"InstructionCode" on page 272


Type: Code


PHOA PhoneNextAgent Please advise/contact next agent byphone.

TELA TelecomNextAgent Please advise/contact next agent by themost efficient means of telecommunica-tion.

Used in element(s)

"Code" on page 154

Restricts


31 May 2020 271

Usage Guideline


Type: Code




Used in element(s)

"Code" on page 154

Restricts


6.69 InstructionCodeDefinition: Specifies further instructions concerning the processing of a payment instruction.

Type: Code


CHQB PayCreditorByCheque (Ultimate) creditor must be paid bycheque.

HOLD HoldCashForCreditor Amount of money must be held for the(ultimate) creditor, who will call. Pay onidentification.

PBEN PayTheBeneficiary (Ultimate) creditor to be paid only afterverification of identity.

PHOA PhoneNextAgent Please advise/contact next agent byphone.


TELA TelecomNextAgent Please advise/contact next agent by themost efficient means of telecommunica-tion.


TFRO TimeFrom Payment instruction will be valid and el-igible for execution from the date andtime stipulated.

TTIL TimeTill Payment instruction is valid and eligiblefor execution until the date and time stip-ulated. Otherwise, the payment instruc-tion will be rejected.


Message Datatypes

Is restricted by

"Instruction3Code" on page 270, "Instruction4Code" on page 271, "Instruction5Code" onpage 272

6.70 LEIIdentifierDefinition: Legal Entity Identifier is a code allocated to a party as described in ISO 17442 "FinancialServices - Legal Entity Identifier (LEI)".

Type: IdentifierSet

Format

pattern [A-Z0-9]{18,18}[0-9]{2,2}

Used in element(s)

"LEI" on page 125, "LEI" on page 135, "LEI" on page 122, "LEI" on page 33, "LEI" on page 157

6.71 Max128TextDefinition: Specifies a character string with a maximum length of 128 characters.

Type: Text

Format

minLength 1

maxLength 128

Used in element(s)



Type: Text

Format

minLength 1

maxLength 140

Used in element(s)

"AdditionalInformation" on page 116, "AdditionalInformation" on page 238, "AdditionalRemittanceInfor-mation" on page 221, "InstructionInformation" on page 153, "InstructionInformation" on page 155, "In-structionInformation" on page 154, "Name" on page 125, "Name" on page 136, "Name" on page 166,"Name" on page 226, "Name" on page 122, "Name" on page 33, "Name" on page 162, "Name" onpage 60, "ReferenceNumber" on page 228, "ReferenceNumber" on page 139, "ReferenceNumber" onpage 231, "Unstructured" on page 207, "Unstructured" on page 205

31 May 2020 273

Usage Guideline

6.73 Max15NumericTextDefinition: 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 149


Type: Text

Format

minLength 1

maxLength 16

Used in element(s)

"BuildingNumber" on page 191, "BuildingNumber" on page 183, "InstructionIdentification" on page 170,"PostBox" on page 191, "PostBox" on page 184, "PostCode" on page 192, "PostCode" on page 184


Type: Text

Format

minLength 1

maxLength 2048

Used in element(s)

"Description" on page 118, "EmailAddress" on page 61, "Identification" on page 196, "Identification" onpage 152


Type: Text


Message Datatypes

Format

minLength 1

maxLength 34

Used in element(s)



Type: Text

Format

minLength 1

maxLength 350

Used in element(s)

"PlaceAndName" on page 222, "Registry" on page 152


Type: Text

Format

minLength 1

maxLength 35

Used in element(s)

"AddressLine" on page 193, "AdministrationZone" on page 227, "AdministrationZone" on page 231,"BuildingName" on page 191, "BuildingName" on page 183, "BusinessMessageIdentifier" on page 37,"BusinessService" on page 38, "Category" on page 236, "CategoryDetails" on page 236, "CertificateI-dentification" on page 237, "CityOfBirth" on page 113, "ClearingSystemReference" on page 172, "Coun-trySubDivision" on page 192, "CountrySubDivision" on page 186, "DebtorStatus" on page 236, "District-Name" on page 192, "DistrictName" on page 185, "EmailPurpose" on page 61, "EndToEndIdentifica-tion" on page 171, "FormsCode" on page 237, "Identification" on page 143, "Identification" on page 145,"Identification" on page 146, "Identification" on page 33, "Issuer" on page 144, "Issuer" on page 143,"Issuer" on page 146, "Issuer" on page 147, "Issuer" on page 112, "Issuer" on page 144, "Issuer" onpage 119, "Issuer" on page 141, "Issuer" on page 201, "JobTitle" on page 61, "MemberIdentification"on page 52, "MessageDefinitionIdentifier" on page 38, "MessageIdentification" on page 148, "Method"on page 228, "Method" on page 231, "Number" on page 117, "Number" on page 199, "Proprietary" onpage 51, "Proprietary" on page 48, "Proprietary" on page 121, "Proprietary" on page 23, "Proprietary"on page 44, "Proprietary" on page 158, "Proprietary" on page 180, "Proprietary" on page 198, "Propri-etary" on page 111, "Proprietary" on page 115, "Proprietary" on page 225, "Proprietary" on page 208,"Proprietary" on page 155, "Proprietary" on page 45, "Proprietary" on page 120, "Proprietary" onpage 141, "Proprietary" on page 200, "Proprietary" on page 197, "ProvinceOfBirth" on page 113, "Ref-

31 May 2020 275

Usage Guideline

erence" on page 111, "RegistrationIdentification" on page 233, "RegistrationIdentification" on page 234,"Responsibility" on page 62, "SchemeName" on page 145, "TaxIdentification" on page 233, "TaxIdentifi-cation" on page 234, "TaxType" on page 233, "TaxType" on page 234, "Title" on page 225, "TownLoca-tionName" on page 192, "TownLocationName" on page 185, "TownName" on page 192, "TownName"on page 184, "TransactionIdentification" on page 172, "Type" on page 236


Type: Text

Format

minLength 1

maxLength 3

Used in element(s)

"Proprietary" on page 156


Type: Text

Format

minLength 1

maxLength 4

Used in element(s)

"ChannelType" on page 159, "Reason" on page 116

6.81 Max70TextDefinition: Specifies a character string with a maximum length of 70characters.

Type: Text

Format

minLength 1

maxLength 70

Used in element(s)

"AddressLine" on page 187, "Department" on page 190, "Department" on page 182, "Department" onpage 62, "Floor" on page 191, "Floor" on page 183, "Name" on page 43, "Name" on page 41, "Room"on page 191, "Room" on page 184, "StreetName" on page 191, "StreetName" on page 183, "SubDe-partment" on page 190, "SubDepartment" on page 182


Message Datatypes

6.82 NamePrefix2CodeDefinition: Specifies the terms used to formally address a person.

Type: Code


DOCT Doctor Title of the person is Doctor or Dr.

MADM Madam Title of the person is Madam.

MIKS GenderNeutral Title of the person is gender neutral(Mx).

MISS Miss Title of the person is Miss.

MIST Mister Title of the person is Mister or Mr.

Used in element(s)

"NamePrefix" on page 60

Restricts

"NamePrefixCode" on page 277

6.83 NamePrefixCodeDefinition: Specifies the terms used to formally address a person.

Type: Code


DOCT Doctor Title of the person is Doctor or Dr.

MADM Madam Title of the person is Madam.

MIKS GenderNeutral Title of the person is gender neutral(Mx).

MISS Miss Title of the person is Miss.

MIST Mister Title of the person is Mister or Mr.

Is restricted by

"NamePrefix2Code" on page 277

6.84 NumberDefinition: Number of objects represented as an integer.

Type: Quantity

Format

totalDigits 18

fractionDigits 0

31 May 2020 277

Usage Guideline

Used in element(s)

"SequenceNumber" on page 228, "SequenceNumber" on page 232

6.85 ParentCurrencyCodeDefinition: Code allocated to a currency, by a maintenance agency, under an international identificationscheme 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 MaintenanceAgency, and consist of three contiguous letters.

Type: Code

Format

pattern [A-Z]{3,3}

Is restricted by

"ActiveCurrencyCode" on page 240, "ActiveOrHistoricCurrencyCode" on page 242

6.86 PercentageRateDefinition: 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

totalDigits 11

fractionDigits 10

Used in element(s)

"Rate" on page 223

6.87 PhoneNumberDefinition: The collection of information which identifies a specific phone or FAX number as defined bytelecom 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 61, "MobileNumber" on page 61, "PhoneNumber" on page 61


Message Datatypes

6.88 PreferredContactMethod1CodeDefinition: Preferred method used to reach the individual contact within an organisation.

Type: Code


CELL MobileOrCellPhone Preferred method used to reach the con-tact is per mobile or cell phone.

FAXX Fax Preferred method used to reach the con-tact is per fax.

LETT Letter Preferred method used to reach the con-tact is per letter.

MAIL Email Preferred method used to reach the con-tact is per email.

PHON Phone Preferred method used to reach the con-tact is per phone.

Used in element(s)

"PreferredMethod" on page 62

Restricts

"PreferredContactMethodCode" on page 279

6.89 PreferredContactMethodCodeDefinition: Preferred method used to reach the individual contact within an organisation.

Type: Code


CELL MobileOrCellPhone Preferred method used to reach the con-tact is per mobile or cell phone.

FAXX Fax Preferred method used to reach the con-tact is per fax.

LETT Letter Preferred method used to reach the con-tact is per letter.

MAIL Email Preferred method used to reach the con-tact is per email.

PHON Phone Preferred method used to reach the con-tact is per phone.

Is restricted by

"PreferredContactMethod1Code" on page 279

6.90 Priority2CodeDefinition: Specifies the priority level of an event.

Type: Code

31 May 2020 279

Usage Guideline


HIGH High Priority level is high.

NORM Normal Priority level is normal.

Used in element(s)

"InstructionPriority" on page 175, "InstructionPriority" on page 173

Restricts

"PriorityCode" on page 280

6.91 Priority3CodeDefinition: Specifies the priority level of an event.

Type: Code




URGT Urgent Priority level is urgent (highest prioritypossible).

Used in element(s)

"SettlementPriority" on page 68

Restricts

"PriorityCode" on page 280

6.92 PriorityCodeDefinition: Specifies the priority level of an event.

Type: Code



LOWW Low Priority level is low.


URGT Urgent Priority level is urgent (highest prioritypossible).

Is restricted by

"Priority2Code" on page 279, "Priority3Code" on page 280

6.93 SettlementMethod1Code


Message Datatypes

Definition: Specifies the method used to settle the credit transfer instruction.

Type: Code


CLRG ClearingSystem Settlement is done through a paymentclearing system.

COVE CoverMethod Settlement is done through a cover pay-ment.


• This code(pacs.009.001.08/Group-Header/SettlementInformation/Set-tlementMethod/CoverMethod) is re-moved.

INDA InstructedAgent Settlement is done by the agent instruct-ed to execute a payment instruction.


• This code(pacs.009.001.08/Group-Header/SettlementInformation/Set-tlementMethod/InstructedAgent) isremoved.

INGA InstructingAgent Settlement is done by the agent instruct-ing and forwarding the payment to thenext party in the payment chain.


• This code(pacs.009.001.08/Group-Header/SettlementInformation/Set-tlementMethod/InstructingAgent) isremoved.

Used in element(s)

"SettlementMethod" on page 211

Restricts

"SettlementMethodCode" on page 281

6.94 SettlementMethodCodeDefinition: Specifies the method used to settle the payment instruction.

31 May 2020 281

Usage Guideline

Type: Code


CLRG ClearingSystem Settlement is done through a paymentclearing system.

COVE CoverMethod Settlement is done through a cover pay-ment.

INDA InstructedAgent Settlement is done by the agent instruct-ed to execute a payment instruction.

INGA InstructingAgent Settlement is done by the agent instruct-ing and forwarding the payment to thenext party in the payment chain.

Is restricted by

"SettlementMethod1Code" on page 280

6.95 TaxRecordPeriod1CodeDefinition: Specifies the period related to the tax payment.

Type: Code


HLF1 FirstHalf Tax is related to the first half of the peri-od.

HLF2 SecondHalf Tax is related to the second half of theperiod.

MM01 FirstMonth Tax is related to the second month of theperiod.

MM02 SecondMonth Tax is related to the first month of theperiod.

MM03 ThirdMonth Tax is related to the third month of theperiod.

MM04 FourthMonth Tax is related to the fourth month of theperiod.

MM05 FifthMonth Tax is related to the fifth month of theperiod.

MM06 SixthMonth Tax is related to the sixth month of theperiod.

MM07 SeventhMonth Tax is related to the seventh month ofthe period.

MM08 EighthMonth Tax is related to the eighth month of theperiod.

MM09 NinthMonth Tax is related to the ninth month of theperiod.

MM10 TenthMonth Tax is related to the tenth month of theperiod.

MM11 EleventhMonth Tax is related to the eleventh month ofthe period.


Message Datatypes


MM12 TwelfthMonth Tax is related to the twelfth month of theperiod.

QTR1 FirstQuarter Tax is related to the first quarter of theperiod.

QTR2 SecondQuarter Tax is related to the second quarter ofthe period.

QTR3 ThirdQuarter Tax is related to the third quarter of theperiod.

QTR4 FourthQuarter Tax is related to the forth quarter of theperiod.

Used in element(s)

"Type" on page 235

Restricts

"TaxRecordPeriodCode" on page 283

6.96 TaxRecordPeriodCodeDefinition: Specifies the period related to the tax payment.

Type: Code


HLF1 FirstHalf Tax is related to the first half of the peri-od.

HLF2 SecondHalf Tax is related to the second half of theperiod.

MM01 FirstMonth Tax is related to the second month of theperiod.

MM02 SecondMonth Tax is related to the first month of theperiod.

MM03 ThirdMonth Tax is related to the third month of theperiod.

MM04 FourthMonth Tax is related to the fourth month of theperiod.

MM05 FifthMonth Tax is related to the fifth month of theperiod.

MM06 SixthMonth Tax is related to the sixth month of theperiod.

MM07 SeventhMonth Tax is related to the seventh month ofthe period.

MM08 EighthMonth Tax is related to the eighth month of theperiod.

MM09 NinthMonth Tax is related to the ninth month of theperiod.

31 May 2020 283

Usage Guideline


MM10 TenthMonth Tax is related to the tenth month of theperiod.

MM11 EleventhMonth Tax is related to the eleventh month ofthe period.

MM12 TwelfthMonth Tax is related to the twelfth month of theperiod.

QTR1 FirstQuarter Tax is related to the first quarter of theperiod.

QTR2 SecondQuarter Tax is related to the second quarter ofthe period.

QTR3 ThirdQuarter Tax is related to the third quarter of theperiod.

QTR4 FourthQuarter Tax is related to the forth quarter of theperiod.

Is restricted by

"TaxRecordPeriod1Code" on page 282

6.97 TrueFalseIndicatorDefinition: A flag indicating a True or False value.

Type: Indicator

Meaning When True: True

Meaning When False: False

Used in element(s)

"EmployeeTerminationIndicator" on page 140, "FamilyMedicalInsuranceIndicator" on page 140

6.98 UUIDv4IdentifierDefinition: Universally Unique IDentifier (UUID) version 4, as described in IETC RFC 4122 "UniversallyUnique IDentifier (UUID) URN Namespace".

Type: IdentifierSet

Format

pattern [a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}

Used in element(s)

"UETR" on page 172

6.99 UnicodeChartsCodeDefinition: codelist containing the names of the UNICODE code block name as specified on http://uni-code.org/Public/UNIDATA/Blocks.txt.


Message Datatypes

Type: Code

Rules



Used in element(s)

"CharacterSet" on page 35

6.100 YesNoIndicatorDefinition: Indicates a "Yes" or "No" type of answer for an element.

Type: Indicator

Meaning When True: Yes

Meaning When False: No

Used in element(s)

"PossibleDuplicate" on page 39

31 May 2020 285

Usage Guideline

Legal Notices

Copyright

SWIFT © 2020. 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 withMyStandards 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 noticesappearing 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 yourorganisation 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, supplyor 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 orits licensors.

Trademarks and Patents

SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:SWIFT, the SWIFT logo, 3SKey, Innotribe, Sibos, SWIFTNet, MyStandards, SWIFTReady, and Accord.Other product, service, or company names in this publication are trade names, trademarks, or regis-tered trademarks of their respective owners.


Documents

ferV08 pacs.009.001 - Payments Canada · Message Functionality Message Functionality This Usage Guideline is based on the pacs.009.001.08 message definition. In addition, Payments