ferv08 pacs.008.001 - payments canada€¦ · message functionality message functionality this...

Usage Guideline

Lynx_FIToFICustomerCreditTrans-ferV08_pacs.008.001.08

Lynx_FINAL_Phase2Messages_SR2019

This document describes a usage guideline restricting the base message MX pacs.008.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/_O9Z75GUsEeq2d4fdbL-V4w

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

http://www.swift.com/mystandards

Usage Guideline

Table of Contents

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

1 Restriction summary ......................................................................................................................................... 5

2 Structure ................................................................................................................................................................. 7

3 Rules ....................................................................................................................................................................... 12

4 Message Building Blocks ............................................................................................................................. 15

5 Message Components .................................................................................................................................... 25

6 Message Datatypes ........................................................................................................................................ 222

.Legal Notices ............................................................................................................................................................... 272

2 Lynx_FIToFICustomerCreditTransferV08_pacs.008.001.08 - Lynx_FINAL_Phase2Messages_SR2019

Message Functionality

Message Functionality

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

Overview

Lynx Documentation Description:

This document outlines the specifications for the Lynx ISO 20022 FI To FI Customer Credit Transfer (single customer credit transfer) message, cleared and settled via Payments Canada's Lynx system, that will be implemented in November 2021 (Phase 2) (this date is now subject to Member review based on the SWIFT announcement 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 FinancialInstitutionToFinancialInstitutionCustomerCreditTransfer message is sent by the debtor agent to the creditor agent, directly or through other agents and/or a payment clearing and settlement system. It is used to move funds from a debtor ac-count to a creditor.

Usage:The FIToFICustomerCreditTransfer message is exchanged between agents and can contain one or more customer credit transfer instructions.The FIToFICustomerCreditTransfer message does not allow for grouping: a CreditTrans-ferTransactionInformation block must be present for each credit transfer transaction.The FIToFICustomerCreditTransfer message can be used in different ways:- If the instructing agent and the instructed agent wish to use their direct account relationship in the currency of the transfer then the message contains both the funds for the customer transfer(s) as well as the payment details;- If the instructing agent and the instructed agent have no direct account relation-ship in the currency of the transfer, or do not wish to use their account relation-ship, then other (reimbursement) agents will be involved to cover for the customer transfer(s). The FIToFICustomerCreditTransfer contains only the payment details and the instructing agent must cover the customer transfer by sending a FinancialInsti-tutionCreditTransfer to a reimbursement agent. This payment method is called the Cov-er method;- If more than two financial institutions are involved in the payment chain and if the FIToFICustomerCreditTransfer is sent from one financial institution to the next financial institution in the payment chain, then the payment method is called the Serial method.The FIToFICustomerCreditTransfer message can be used in domestic and cross-border 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_FIToFICustomerCreditTransferV08_pac-s.008.001.08 message is composed of 3 building blocks

31 May 2020 3

Usage Guideline

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.


Restriction summary

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

Restriction Type See page

Removed elements 14, 15, 18, 20, 24, 32, 32, 32, 32,32, 32, 32, 32, 32, 32, 32, 32, 32,34, 35, 35, 36, 37, 41, 50, 50, 50,50, 50, 50, 50, 50, 50, 50, 50, 50,51, 51, 52, 53, 70, 71, 92, 94, 115,115, 115, 115, 115, 115, 115, 115, 115, 115,115, 115, 115, 115, 118, 128, 129, 130, 130,130, 131, 132, 132, 134, 136, 142, 142, 142,142, 147, 147, 147, 147, 147, 148, 148, 151,151, 157, 163, 163, 163, 163, 163, 163, 163,167, 167, 167, 167, 167, 167, 167, 169, 169,169, 169, 169, 169, 169, 169, 169, 169, 169,169, 169, 169, 169, 169, 169, 169, 190, 191,191, 191, 192, 192, 192, 193, 194, 195, 195,196, 196, 197, 232, 267, 267, 268

Make mandatory 54, 54, 54, 54, 54, 55, 55, 55, 55,55, 55, 55, 55, 55, 58, 68, 68, 76,77, 108, 108, 152, 154, 158, 165, 165, 165,165, 165, 165, 166, 166, 166, 166, 166, 167,167, 193

Reduce Multiplicity 20, 23, 89, 91, 93, 138, 138, 138, 138,139, 139, 139, 139, 139, 157, 160, 160, 160,160, 161, 161, 161, 161, 161, 172, 172, 172,172, 172, 172, 172, 172, 173, 173, 173, 173,173, 173, 173, 173, 173, 173, 185

Ignore 69, 154, 198, 198, 198

Text rules 16, 17, 17, 18, 38, 39, 39, 47, 70,72, 73, 74, 75, 76, 77, 78, 79, 80,81, 82, 83, 85, 86, 87, 89, 143, 143,143, 144, 158, 186, 231

Conditional rules 90, 90

Fixed values 48, 48, 52, 129, 229

Truncates n.a.

Comments 19, 32, 41, 48, 48, 48, 48, 49, 49,49, 49, 49, 49, 49, 49, 51, 55, 56,56, 56, 56, 56, 56, 56, 57, 57, 57,57, 57, 57, 59, 69, 76, 77, 91, 108,108, 126, 127, 140, 146, 146, 146, 146, 146,146, 146, 149, 149, 150, 151, 152, 153, 154,157, 159, 162, 165

Annotations n.a.

31 May 2020 5

Usage Guideline

Restriction Type See page

Changed datatypes n.a.

Extensions n.a.

Synonyms 47, 47, 47, 52, 68, 68, 71, 71, 71,76, 77, 78, 79, 83, 84, 84, 85, 85,86, 87, 87, 88, 90, 91, 91, 92, 93,152, 153, 198, 231, 231, 232, 254, 254, 254,255

Other restrictions 23, 23, 24, 29, 29, 30, 30, 30, 30,30, 30, 30, 31, 31, 31, 31, 31, 34,82, 82, 83, 83, 87, 88, 89, 94, 110,110, 111, 111, 111, 111, 111, 111, 111, 112,112, 112, 112, 112, 112, 112, 113, 113, 113,113, 113, 113, 113, 114, 114, 114, 114, 114,118, 118, 149, 150, 150, 150, 153


Structure

2 Structure

31 May 2020 7

Usage Guideline

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] 15

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

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

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

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



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

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

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

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

Registry <Regy> [1..1] 133

Identification <Id> [1..1] 133

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

BusinessProcessingDate <BizPrcgDt> [0..1] 18

CopyDuplicate <CpyDplct> [0..1] 18

PossibleDuplicate <PssblDplct> [0..1] 19

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

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

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


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

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








Structure


Page



FIToFICustomerCreditTransferV08 <FIToFICstmrCdtTrf> [1..1]

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

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

CreationDateTime <CreDtTm> [1..1] 129

BatchBooking <BtchBookg> [0..1] 129

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

ControlSum <CtrlSum> [0..1] 130

TotalInterbankSettlementAmount <TtlIntrBkSttlmAmt> [0..1] 130

InterbankSettlementDate <IntrBkSttlmDt> [0..1] 130

SettlementInformation <SttlmInf> [1..1] 130

PaymentTypeInformation <PmtTpInf> [0..1] 131

InstructingAgent <InstgAgt> [0..1] 131

InstructedAgent <InstdAgt> [0..1] 132

CreditTransferTransactionInformation <CdtTrfTxInf> [1..*] ! R[1..1] 21

PaymentIdentification <PmtId> [1..1] 67

PaymentTypeInformation <PmtTpInf> [0..1] ! 67

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

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

SettlementPriority <SttlmPrty> [0..1] 69

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

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

AcceptanceDateTime <AccptncDtTm> [0..1] ! 70

PoolingAdjustmentDate <PoolgAdjstmntDt> [0..1] 70

InstructedAmount <InstdAmt> [0..1] ! 71

ExchangeRate <XchgRate> [0..1] ! 71

ChargeBearer <ChrgBr> [1..1] ! 71

ChargesInformation <ChrgsInf> [0..*] ! 72

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

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> [0..1] 73

31 May 2020 9

Usage Guideline


Page





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

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

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

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





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

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

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

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

DebtorAgent <DbtrAgt> [1..1] ! 84

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

CreditorAgent <CdtrAgt> [1..1] ! 85

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

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

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

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

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

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

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

RegulatoryReporting <RgltryRptg> [0..10] ! 91

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

RelatedRemittanceInformation <RltdRmtInf> [0..10] R[0..1] 93

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

SupplementaryData <SplmtryData> [0..*] 94


Structure


Page


PlaceAndName <PlcAndNm> [0..1] 205

Envelope <Envlp> [1..1] 205

31 May 2020 11

Usage Guideline

3 RulesR3 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

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

R8 InstructingAgentRule ✓

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

Error handling:



– Error Text: Invalid message content for instructing agent.

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

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

R11 GroupHeaderInterbankSettlementDateRule ✓

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

Error handling:



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

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

R13 PaymentTypeInformationRule ✓

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

Error handling:



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

R14 NumberOfTransactionsAndCreditTransfersRule

GroupHeader/NumberOfTransactions must equal the number of occurrences of CreditTransfer-TransactionInformation.

Error handling:



– Error Text: Invalid message content for number of transactions.

R15 SupplementaryDataRule

31 May 2020 13

Usage Guideline

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.008.001.08/SupplementaryDataRule) is removed.


Message Building Blocks

4 Message Building Blocks

Note The following chapter identifies the building blocks of the Lynx_FINAL_Phase2Mes-sages_SR2019 / Lynx_FIToFICustomerCreditTransferV08_pacs.008.001.08 message def-inition.

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 271

Usage Guideline details

• This element(pacs.008.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 141 for de-tails)



Page



4.1.3 ToXML Tag: To

31 May 2020 15

Usage Guideline

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 141 for de-tails)



Page



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 259


• on pacs.008.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.008.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 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.008.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.

31 May 2020 17

Usage Guideline

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



Page




• on pacs.008.001.08/.header/MarketPractice

– 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 229

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 253


• This element(pacs.008.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 234

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 271

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 227


• on pacs.008.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.

31 May 2020 19

Usage Guideline


• This element(pacs.008.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.

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 36 for details)



Page


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

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










• on pacs.008.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_FIToFICustomerCreditTransferV08_pacs.008.001.08 payload defi-nition.



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 128for 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 21

Usage Guideline

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



Page

































Page














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





• on pacs.008.001.08/CreditTransferTransactionInformation



– Lynx_RelatedRemitInfo_RemitInfo_MutuallyExclusiveRule:

In the interbank space, Related Remittance Information and Remittance Informa-tion are mutually exclusive and all may be absent.This rule is inherited verbatim from CBPR+.


– Lynx_CREDRule:

Charge information is mandatory if CRED is present - if no charges are taken, Zero must be used in "Amount" (any agent in the payment chain).This rule is inherited verbatim from CBPR+


31 May 2020 23

Usage Guideline

– Lynx_DEBTRule:

If Charge Bearer/DEBT is used then charge information is only mandatory in case of prepaid charges (that is if interbank settlement amount is higher than in-structed amount) and in that case zero amount is not allowed. Otherwise Charge information is optional (both Agent and currency always need to be provided).This rule is inherited verbatim from CBPR+.

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 204 for details)



Page




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


Message Components

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] 25

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

Used in element(s)

"Identification" on page 41, "Identification" on page 43

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 252

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 123 for details)



Page


SchemeName <SchmeNm> [0..1] 123

Issuer <Issr> [0..1] 123

31 May 2020 25

Usage Guideline

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



Page

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

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

Used in element(s)

"SchemeName" on page 123

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 240

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] 26


Used in element(s)

"AddressType" on page 162, "AddressType" on page 168


Presence: [1..1]

Definition: Type of address expressed as a code.


Message Components

Datatype: "AddressType2Code" on page 224


Presence: [1..1]

Definition: Type of address expressed as a proprietary code.

The Prtry block contains the following elements (see datatype "GenericIdentification30" on page 125for 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] 27

BranchIdentification <BrnchId> [0..1] 28

Used in element(s)

"InstructedAgent" on page 132, "InstructedReimbursementAgent" on page 195, "InstructingAgent"on page 131, "InstructingReimbursementAgent" on page 194, "ThirdReimbursementAgent" onpage 196

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.

31 May 2020 27

Usage Guideline

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



Page

BICFI <BICFI> [0..1] 105

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] 105

LEI <LEI> [0..1] 106

Name <Nm> [0..1] 106

PostalAddress <PstlAdr> [0..1] 106

Other <Othr> [0..1] 107

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 34 for de-tails)



Page


LEI <LEI> [0..1] 35

Name <Nm> [0..1] 35


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] ! 29

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


Message Components

Used in element(s)

"Agent" on page 47, "CreditorAgent" on page 85, "DebtorAgent" on page 84, "FinancialInsti-tutionIdentification" on page 142, "InstructedAgent" on page 76, "InstructingAgent" on page 75,"IntermediaryAgent2" on page 79, "IntermediaryAgent3" on page 80, "PreviousInstructingAgent1"on page 72, "PreviousInstructingAgent2" on page 73, "PreviousInstructingAgent3" on page 74


Presence: [1..1]


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



Page

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


LEI <LEI> [0..1] 109

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

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

Other <Othr> [0..1] 114


• on pacs.008.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.008.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification



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

31 May 2020 29

Usage Guideline



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



• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification


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

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



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



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



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



• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/FinancialInsti-tutionIdentification


Message Components






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










Presence: [0..1]



31 May 2020 31

Usage Guideline




Page


LEI <LEI> [0..1] 35

Name <Nm> [0..1] 35



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

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

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

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

• This element(pacs.008.001.08/CreditTransferTransactionInformation/ChargesInforma-tion/Agent/BranchIdentification) is removed.

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

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

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

• This element(pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryA-gent2/BranchIdentification) is removed.


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



• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchIdentification


Message Components

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)

"IntermediaryAgent1" on page 77


Presence: [1..1]


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



Page



LEI <LEI> [0..1] 116

Name <Nm> [0..1] 117


Other <Othr> [0..1] 118



31 May 2020 33

Usage Guideline




Presence: [0..1]






Page


LEI <LEI> [0..1] 35

Name <Nm> [0..1] 35




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



Page


LEI <LEI> [0..1] 35

Name <Nm> [0..1] 35



Message Components

Used in element(s)

"BranchIdentification" on page 28, "BranchIdentification" on page 31, "BranchIdentification" onpage 34

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 256


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

5.7.3 NameXML 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.008.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification/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.

31 May 2020 35

Usage Guideline

The PstlAdr block contains the following elements (see datatype "PostalAddress24" on page 162 fordetails)



Page

AddressType <AdrTp> [0..1] 162

Department <Dept> [0..1] 163

SubDepartment <SubDept> [0..1] 163

StreetName <StrtNm> [0..1] 163

BuildingNumber <BldgNb> [0..1] 164

BuildingName <BldgNm> [0..1] 164

Floor <Flr> [0..1] 164

PostBox <PstBx> [0..1] 164

Room <Room> [0..1] 164

PostCode <PstCd> [0..1] 164

TownName <TwnNm> [0..1] 165

TownLocationName <TwnLctnNm> [0..1] 165

DistrictName <DstrctNm> [0..1] 166

CountrySubDivision <CtrySubDvsn> [0..1] 166

Country <Ctry> [0..1] 166

AddressLine <AdrLine> [0..7] 167


• This element(pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent/BranchI-dentification/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.


Message Components



Page


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

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









Used in element(s)

"Related" on page 20

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 271


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

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

31 May 2020 37

Usage Guideline

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



Page



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

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



Page



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


Message Components

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

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

31 May 2020 39

Usage Guideline

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

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 234

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 271

5.8.10 PriorityXML Tag: Prty

Presence: [0..1]


Message Components

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

Datatype: "BusinessMessagePriorityCode" on page 227


• on pacs.008.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.008.001.08/.header/Related/Signature) is removed.

5.9 CashAccount38Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 42

Currency <Ccy> [0..1] 42

Name <Nm> [0..1] 42

Proxy <Prxy> [0..1] 43

Used in element(s)

"InstructedReimbursementAgentAccount" on page 195, "InstructingReimbursementAgentAccount" onpage 194, "SettlementAccount" on page 193, "ThirdReimbursementAgentAccount" on page 196


Presence: [1..1]

31 May 2020 41

Usage Guideline

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

The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 25 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 45for details)



Page

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


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 224


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.


Message Components


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 173 for details)



Page

Type <Tp> [0..1] 174


5.10 CashAccount38__1Definition: Provides the details to identify an account.



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44


Used in element(s)

"CreditorAccount" on page 88, "CreditorAgentAccount" on page 86, "DebtorAccount" onpage 83, "DebtorAgentAccount" on page 85, "IntermediaryAgent1Account" on page 78, "In-termediaryAgent2Account" on page 79, "IntermediaryAgent3Account" on page 81, "PreviousIn-structingAgent1Account" on page 73, "PreviousInstructingAgent2Account" on page 74, "Previ-ousInstructingAgent3Account" on page 75


Presence: [1..1]

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

31 May 2020 43

Usage Guideline

The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 25 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 45for details)



Page

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


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 224


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.



Message Components

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 174 for details)



Page

Type <Tp> [0..1] 174


5.11 CashAccountType2ChoiceDefinition: Nature or use of the account.



Page

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


Used in element(s)

"Type" on page 42, "Type" on page 44


Presence: [1..1]

Definition: Account type, in a coded form.

Datatype: "ExternalCashAccountType1Code" on page 241


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.

31 May 2020 45

Usage Guideline

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] 46


Used in element(s)

"CategoryPurpose" on page 156, "CategoryPurpose" on page 158


Presence: [1..1]

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

Datatype: "ExternalCategoryPurpose1Code" on page 242


Presence: [1..1]

Definition: Category purpose, in a proprietary form.


5.13 Charges7__1Definition: Provides information on the charges related to the payment transaction.



Page

Amount <Amt> [1..1] ! 46

Agent <Agt> [1..1] ! 47

Used in element(s)

"ChargesInformation" on page 72

5.13.1 AmountXML Tag: Amt

Presence: [1..1]

Definition: Transaction charges to be paid by the charge bearer.


Message Components

Datatype: "CBPR_Amount" on page 228


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Amount

Synonym (MT 103 - field 71F): Sender's Charges

• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Amount

Synonym (MT 103 - field 71G): Receiver's Charges

5.13.2 AgentXML Tag: Agt

Presence: [1..1]

Definition: Agent that takes the transaction charges or to which the transaction charges are due.

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



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent

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

• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent

Synonym (MT103 - implicit and understood from the payment chain): Party that has liftedcharges or to which charges are due

5.14 ClearingSystemIdentification2Choice

31 May 2020 47

Usage Guideline

Definition: Choice of a clearing system identifier.



Page

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


Used in element(s)

"ClearingSystemIdentification" on page 53, "ClearingSystemIdentification" on page 54


Presence: [1..1]

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

Datatype: "ExternalClearingSystemIdentification1Code" on page 243


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

Single value: CACPA

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

Single value: CACPA

• on pacs.008.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.008.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code


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


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



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentifica-tion/Code


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


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


• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification/Code




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







31 May 2020 49

Usage Guideline

Presence: [1..1]

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



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

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

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

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

• This element(pacs.008.001.08/CreditTransferTransactionInformation/ChargesInforma-tion/Agent/FinancialInstitutionIdentification/ClearingSystemMemberIdentification/Clear-ingSystemIdentification/Proprietary) is removed.

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

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

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

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

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


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


Message Components



5.15 ClearingSystemIdentification2Choice__1Definition: Choice of a clearing system identifier.



Page

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


Used in element(s)

"ClearingSystemIdentification" on page 58


Presence: [1..1]

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

Datatype: "ExternalClearingSystemIdentification1Code" on page 243





Presence: [1..1]

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

Datatype: "RestrictedFINXMax35Text" on page 267

31 May 2020 51

Usage Guideline



5.16 ClearingSystemIdentification3ChoiceDefinition: Specifies the clearing system identification.



Page

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


Used in element(s)

"ClearingSystem" on page 193


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 242


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

Single value: LYX

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

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


Presence: [1..1]

Definition: Clearing system identification in a proprietary form.



Message Components


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

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



Page

ClearingSystemIdentification <ClrSysId> [0..1] 53

MemberIdentification <MmbId> [1..1] 53

Used in element(s)

"ClearingSystemMemberIdentification" on page 105

5.17.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 47 for details)



Page

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


5.17.2 MemberIdentificationXML Tag: MmbId

Presence: [1..1]

Definition: Identification of a member of a clearing system.


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

31 May 2020 53

Usage Guideline



Page


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

Used in element(s)



Presence: [0..1]


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



Page

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



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

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

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


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


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


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification



Message Components

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


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


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


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


• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/ClearingSystemIdentification




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







Presence: [1..1]


Datatype: "CBPR__RestrictedFINXMax28Text" on page 230


• on pacs.008.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

31 May 2020 55

Usage Guideline

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.008.001.08/.header/Related/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/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.008.001.08/.header/Related/To/FinancialInstitutionIdentification/FinancialInstitutionI-dentification/ClearingSystemMemberIdentification/MemberIdentification


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


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/ClearingSystemMemberIdentification/MemberIdentification


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


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


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


Message Components

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.008.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.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/FinancialInsti-tutionIdentification/ClearingSystemMemberIdentification/MemberIdentification




• on pacs.008.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/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

31 May 2020 57

Usage Guideline

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

5.19 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]


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



Page

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






Presence: [1..1]


Datatype: "CBPR__RestrictedFINXMax28Text" on page 230


Message Components




5.20 Contact4Definition: Specifies the details of the contact person.



Page

NamePrefix <NmPrfx> [0..1] 59

Name <Nm> [0..1] 59

PhoneNumber <PhneNb> [0..1] 60

MobileNumber <MobNb> [0..1] 60

FaxNumber <FaxNb> [0..1] 60

EmailAddress <EmailAdr> [0..1] 60

EmailPurpose <EmailPurp> [0..1] 60

JobTitle <JobTitl> [0..1] 60

Responsibility <Rspnsblty> [0..1] 61


Other <Othr> [0..*] 61

PreferredMethod <PrefrdMtd> [0..1] 61

Used in element(s)

"ContactDetails" on page 147, "ContactDetails" on page 151

5.20.1 NamePrefixXML Tag: NmPrfx

Presence: [0..1]

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

Datatype: "NamePrefix2Code" on page 260

5.20.2 Name

31 May 2020 59

Usage Guideline

XML Tag: Nm

Presence: [0..1]

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


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

5.20.4 MobileNumberXML Tag: MobNb

Presence: [0..1]

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


5.20.5 FaxNumberXML Tag: FaxNb

Presence: [0..1]

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


5.20.6 EmailAddressXML Tag: EmailAdr

Presence: [0..1]

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


5.20.7 EmailPurposeXML Tag: EmailPurp

Presence: [0..1]

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


5.20.8 JobTitleXML Tag: JobTitl


Message Components

Presence: [0..1]

Definition: Title of the function.


5.20.9 ResponsibilityXML Tag: Rspnsblty

Presence: [0..1]

Definition: Role of a person in an organisation.


5.20.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 140 for de-tails)



Page

ChannelType <ChanlTp> [1..1] 140


5.20.12 PreferredMethodXML Tag: PrefrdMtd

Presence: [0..1]

Definition: Preferred method used to reach the contact.

Datatype: "PreferredContactMethod1Code" on page 262

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

31 May 2020 61

Usage Guideline



Page
































Message Components


Page













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




Rules

R34 InstructedAmountAndExchangeRate1Rule ✓

If InstructedAmount is present and the currency is different from the currency in InterbankSet-tlementAmount, then ExchangeRate must be present.

Error handling:



– Error Text: Invalid message content for exchange rate when instructed amount is present.


If InstructedAmount is present and the currency is the same as the currency in InterbankSettle-mentAmount, then ExchangeRate is not allowed.

Error handling:



– Error Text: Invalid message content for exchange rate when instructed amount is notpresent.

31 May 2020 63

Usage Guideline

R36 ChargesInformationAndInstructedAmountRule ✓

If ChargesInformation is present, then InstructedAmount must be present.

Error handling:



– Error Text: Invalid message content for instructed amount when charges information ispresent.

R37 ChargeBearerAndChargesInformationRule ✓

If ChargeBearer contains DEBT, then ChargesInformation may be present to communicatecharges that have been added for (the) InstructedAgent(s).

If ChargeBearer contains CRED, then at least one occurrence of ChargesInformation must bepresent to communicate charges that have been deducted from the InstructedAmount by (the)InstructingAgent(s).

If ChargeBearer contains SHAR or SLEV, then ChargesInformation is optional.

Error handling:



– Error Text: Invalid message content for charge bearer and charges information.

R38 InstructionForCreditorAgentRule ✓

If InstructionForCreditorAgent/Code contains CHQB (PayCreditorByCheque), then CreditorAc-count is not allowed.

Error handling:



– Error Text: Invalid message content for PayCreditorByCheque instruction for creditor agent.

R39 IntermediaryAgent2Rule ✓

If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.

Error handling:



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

R40 IntermediaryAgent3Rule ✓

If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.

Error handling:


Message Components




R41 IntermediaryAgent1AccountRule ✓

If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.

Error handling:



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



Error handling:






Error handling:





If InstructedAmount is not present, then ExchangeRate is not allowed.

Error handling:



– Error Text: Invalid message content for exchange rate and instructed amount.

R45 PreviousInstructingAgent2AccountRule ✓

If PreviousInstructingAgent2Account is present, then PreviousInstructingAgent2 must bepresent.

Error handling:

31 May 2020 65

Usage Guideline



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



Error handling:




R47 PreviousInstructionAgent2Rule ✓

If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.

Error handling:




R48 PreviousInstructionAgent3Rule ✓

If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be present.

Error handling:






Error handling:




Guidelines

1. ChargesInformationGuideline

The repetitive ChargesInformation should contain all information on charges amount and whichparty has taken the charges, separately for each agent along the payment chain.

2. UltimateDebtorGuideline


Message Components

UltimateDebtor may only be present if different from Debtor.

3. UltimateCreditorGuideline

UltimateCreditor may only be present if different from Creditor.

4. ChargesAmountGuideline

If ChargesInformation is present, then the currency of ChargesInformation/ChargesAmount is rec-ommended to be the same as the currency of InterbankSettlementAmount.

5. PreviousInstructingAgent1Guideline

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

Used in element(s)

"CreditTransferTransactionInformation" on page 21

5.21.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 151 for details)



Page

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

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

TransactionIdentification <TxId> [0..1] 153

UETR <UETR> [0..1] 154

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

5.21.2 PaymentTypeInformationXML Tag: PmtTpInf

Presence: [0..1]

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

31 May 2020 67

Usage Guideline

The PmtTpInf block contains the following elements (see datatype "PaymentTypeInformation28__1" onpage 156 for details)



Page

InstructionPriority <InstrPrty> [0..1] 157

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

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

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

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


• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation


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


• on pacs.008.001.08/CreditTransferTransactionInformation/InterbankSettlementAmount

Synonym (MT 103 - field 32A - subfield 2+3 Currency, Amount): Currency Code, Interbank Set-tled Amount

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


• on pacs.008.001.08/CreditTransferTransactionInformation/InterbankSettlementDate


• on pacs.008.001.08/CreditTransferTransactionInformation/InterbankSettlementDate


Message Components

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

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

5.21.6 SettlementTimeIndicationXML Tag: SttlmTmIndctn

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 189 for details)



Page

DebitDateTime <DbtDtTm> [0..1] 189

CreditDateTime <CdtDtTm> [0..1] 189


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

• on pacs.008.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.21.7 SettlementTimeRequestXML Tag: SttlmTmReq

Presence: [0..1]

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

31 May 2020 69

Usage Guideline

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



Page

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

TillTime <TillTm> [0..1] 198

FromTime <FrTm> [0..1] 198

RejectTime <RjctTm> [0..1] 198


• on pacs.008.001.08/CreditTransferTransactionInformation/SettlementTimeRequest

– 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.21.8 AcceptanceDateTimeXML Tag: AccptncDtTm

Presence: [0..1]

Definition: Point in time when the payment order from the initiating party meets the processing condi-tions of the account servicing agent. This means that the account servicing agent has received the pay-ment order and has applied checks such as authorisation, availability of funds.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/AcceptanceDateTime) isremoved.

5.21.9 PoolingAdjustmentDateXML Tag: PoolgAdjstmntDt

Presence: [0..1]

Definition: Date used for the correction of the value date of a cash pool movement that has been postedwith a different value date.



Message Components


• This element(pacs.008.001.08/CreditTransferTransactionInformation/PoolingAdjustmentDate)is removed.

5.21.10 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 228


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructedAmount

Synonym (MT 103 - field 33B): Currency/Instructed Amount

5.21.11 ExchangeRateXML Tag: XchgRate

Presence: [0..1]

Definition: Factor used to convert an amount from one currency into another. This reflects the price atwhich one currency was bought with another currency.

Datatype: "BaseOneRate" on page 227


• on pacs.008.001.08/CreditTransferTransactionInformation/ExchangeRate

Synonym (MT 103 - field 36): Exchange Rate

5.21.12 ChargeBearerXML Tag: ChrgBr

Presence: [1..1]

Definition: Specifies which party/parties will bear the charges associated with the processing of the pay-ment transaction.

Datatype: "ChargeBearerType1Code" on page 231


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargeBearer

31 May 2020 71

Usage Guideline

Synonym (MT 103 - field 71A): Details of Charges

5.21.13 ChargesInformationXML Tag: ChrgsInf

Presence: [0..*]

Definition: Provides information on the charges to be paid by the charge bearer(s) related to the pay-ment transaction.

The ChrgsInf block contains the following elements (see datatype "Charges7__1" on page 46 fordetails)



Page

Amount <Amt> [1..1] ! 46

Agent <Agt> [1..1] ! 47


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation

– Lynx_SHARRule:

If deduct taken then charge information is mandatory. It is optional for initia-tor (not taking deduct).This rule is inherited verbatim from CBPR+

5.21.14 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 28 for details)



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1


Message Components




5.21.15 PreviousInstructingAgent1AccountXML Tag: PrvsInstgAgt1Acct

Presence: [0..1]

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

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



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



Presence: [0..1]





Page



31 May 2020 73

Usage Guideline







Presence: [0..1]





Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



Presence: [0..1]



Message Components




Page









Presence: [0..1]





Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44


5.21.20 InstructingAgent

31 May 2020 75

Usage Guideline

XML 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 28 for details)



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/InstructingAgent







Synonym (MT 103 - Header): Sender


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

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


Message Components

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



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/InstructedAgent







Synonym (MT 103 - Header): Receiver


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

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

31 May 2020 77

Usage Guideline

The IntrmyAgt1 block contains the following elements (see datatype "BranchAndFinancialInstitutionI-dentification6__2" on page 33 for details)



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent1





Synonym (MT 103 - field 56a): Intermediary Institution

5.21.23 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 43 for details)



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



Message Components


• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent1Account

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


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]


31 May 2020 79

Usage Guideline




Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



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] 44


Name <Nm> [0..1] 44


5.21.28 UltimateDebtorXML Tag: UltmtDbtr

Presence: [0..1]

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

The UltmtDbtr block contains the following elements (see datatype "PartyIdentification135" onpage 144 for details)



Page

Name <Nm> [0..1] 144


Identification <Id> [0..1] ! 145

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

ContactDetails <CtctDtls> [0..1] 147


• on pacs.008.001.08/CreditTransferTransactionInformation/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)]

31 May 2020 81

Usage Guideline

• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor

– Lynx_NameAndPostalAddressPartyRule:

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

5.21.29 InitiatingPartyXML Tag: InitgPty

Presence: [0..1]

Definition: Party that initiates the payment.

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 144 for details)



Page

Name <Nm> [0..1] 144






• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty

– Lynx_CanadianParty(InitiatingParty)Rule :

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

• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty



5.21.30 DebtorXML Tag: Dbtr

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 148 for details)



Page

Name <Nm> [0..1] 148




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


• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor

– Lynx_CanadianParty(Debtor)Rule :

For a Canadian Debtor, one of the following options must 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)]


Synonym (MT 103 - field 50a): Ordering Customer


– Lynx_DebtorNameMandatoryIfRule:

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




5.21.31 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 83

Usage Guideline

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



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAccount

Synonym (MT 103 - field 50a - subfield 1): Ordering Customer - Account

• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAccount

Synonym: (empty)

5.21.32 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 28 for details)



Page




• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAgent


Message Components




• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAgent

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

5.21.33 DebtorAgentAccountXML 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 43 for details)



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAgentAccount

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

5.21.34 CreditorAgentXML Tag: CdtrAgt

Presence: [1..1]

Definition: Financial institution servicing an account for the creditor.

31 May 2020 85

Usage Guideline

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



Page


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


• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent




• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent

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

5.21.35 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 43 for details)



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



Message Components


• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgentAccount

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

5.21.36 CreditorXML Tag: Cdtr

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 148 for details)



Page

Name <Nm> [0..1] 148






• on pacs.008.001.08/CreditTransferTransactionInformation/Creditor

– Lynx_CanadianParty(Creditor)Rule :

For a Canadian Creditor, one of the following options must 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)]


Synonym (MT 103 - field 59a): Beneficiary Customer


– Lynx_CreditorNameMandatoryIfRule:

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


31 May 2020 87

Usage Guideline



5.21.37 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 43for details)



Page


Type <Tp> [0..1] 44


Name <Nm> [0..1] 44



• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAccount

Synonym (MT 103 - field 59a - subfield 1): Beneficiary Customer - Account

5.21.38 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 144 for details)



Page

Name <Nm> [0..1] 144






• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor

– Lynx Canadian Party (Ultimate Creditor) Rule :

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

• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor



5.21.39 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 133 for details)



Page

Code <Cd> [0..1] 133

InstructionInformation <InstrInf> [0..1] 134


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructionForCreditorAgent


31 May 2020 89

Usage Guideline


– Lynx_InstructionForCreditorAgent1Rule:

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_InstructionForCreditorAgent2Rule:

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

If PHOB is present

Then TELB is not allowed

Else TELB is optional


Synonym (MT 103 - field 23E): Instruction Code.

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

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



Page

Code <Cd> [0..1] 134

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


Message Components


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructionForNextAgent


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructionForNextAgent

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

5.21.41 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 175 for de-tails)



Page

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



• on pacs.008.001.08/CreditTransferTransactionInformation/Purpose

Synonym (MT 103 - field 26T): Transaction Type Code.

• on pacs.008.001.08/CreditTransferTransactionInformation/Purpose

Comment:Code is the preferred option.

5.21.42 RegulatoryReportingXML Tag: RgltryRptg

Presence: [0..10]

Definition: Information needed due to regulatory and statutory requirements.

31 May 2020 91

Usage Guideline

The RgltryRptg block contains the following elements (see datatype "RegulatoryReporting3" onpage 179 for details)



Page

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] 180

Authority <Authrty> [0..1] 180

Details <Dtls> [0..*] 180


• on pacs.008.001.08/CreditTransferTransactionInformation/RegulatoryReporting

Synonym (MT 103 - field 77B): Regulatory Reporting

5.21.43 TaxXML Tag: Tax

Presence: [0..1]

Definition: Provides details on the tax.

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



Page

Creditor <Cdtr> [0..1] 212

Debtor <Dbtr> [0..1] 213

AdministrationZone <AdmstnZone> [0..1] 213

ReferenceNumber <RefNb> [0..1] 213

Method <Mtd> [0..1] 213

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] 214

TotalTaxAmount <TtlTaxAmt> [0..1] 214

Date <Dt> [0..1] 214

SequenceNumber <SeqNb> [0..1] 214

Record <Rcrd> [0..*] 214


• This element(pacs.008.001.08/CreditTransferTransactionInformation/Tax) is removed.


Message Components

5.21.44 RelatedRemittanceInformationXML Tag: RltdRmtInf

Presence: [0..10]

Definition: Provides information related to the handling of the remittance information by any of theagents in the transaction processing chain.

The RltdRmtInf block contains the following elements (see datatype "RemittanceLocation7__1" onpage 186 for details)



Page

RemittanceIdentification <RmtId> [0..1] 187

RemittanceLocationDetails <RmtLctnDtls> [0..*] 187


• on pacs.008.001.08/CreditTransferTransactionInformation/RelatedRemittanceInformation


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

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



Page

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

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


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation

Synonym (MT 103 - field 70): Remittance Information

• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation

31 May 2020 93

Usage Guideline

– Lynx_Unstructured_Structured_MutuallyExclusiveRule:

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

5.21.46 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 204 for details)



Page




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

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



Page

Type <Tp> [0..1] 94

Reference <Ref> [0..1] 95

Used in element(s)

"CreditorReferenceInformation" on page 201


Presence: [0..1]

Definition: Specifies the type of creditor reference.


Message Components

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



Page

CodeOrProprietary <CdOrPrtry> [1..1] 96


5.22.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.23 CreditorReferenceType1ChoiceDefinition: Specifies the type of document referred by the creditor.



Page

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


Used in element(s)

"CodeOrProprietary" on page 96


Presence: [1..1]

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

Datatype: "DocumentType3Code" on page 237


31 May 2020 95

Usage Guideline

Presence: [1..1]

Definition: Creditor reference type, in a proprietary form.


5.24 CreditorReferenceType2Definition: Specifies the type of creditor reference.



Page



Used in element(s)

"Type" on page 94

5.24.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 95 for details)



Page

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


5.24.2 IssuerXML Tag: Issr

Presence: [0..1]

Definition: Entity that assigns the credit reference type.


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


Message Components



Page

BirthDate <BirthDt> [1..1] 97

ProvinceOfBirth <PrvcOfBirth> [0..1] 97

CityOfBirth <CityOfBirth> [1..1] 97

CountryOfBirth <CtryOfBirth> [1..1] 97

Used in element(s)

"DateAndPlaceOfBirth" on page 159

5.25.1 BirthDateXML Tag: BirthDt

Presence: [1..1]

Definition: Date on which a person is born.


5.25.2 ProvinceOfBirthXML Tag: PrvcOfBirth

Presence: [0..1]

Definition: Province where a person was born.


5.25.3 CityOfBirthXML Tag: CityOfBirth

Presence: [1..1]

Definition: City where a person was born.


5.25.4 CountryOfBirthXML Tag: CtryOfBirth

Presence: [1..1]

Definition: Country where a person was born.

Datatype: "CountryCode" on page 235

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

31 May 2020 97

Usage Guideline



Page

FromDate <FrDt> [1..1] 98

ToDate <ToDt> [1..1] 98

Used in element(s)

"FromToDate" on page 217

5.26.1 FromDateXML Tag: FrDt

Presence: [1..1]

Definition: Start date of the range.


5.26.2 ToDateXML Tag: ToDt

Presence: [1..1]

Definition: End date of the range.


5.27 DiscountAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 98

Amount <Amt> [1..1] 99

Used in element(s)

"DiscountAppliedAmount" on page 181, "DiscountAppliedAmount" on page 184


Presence: [0..1]

Definition: Specifies the type of the amount.


Message Components

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



Page

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



Presence: [1..1]

Definition: Amount of money, which has been typed.

Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 223

5.28 DiscountAmountType1ChoiceDefinition: Specifies the amount type.



Page

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


Used in element(s)

"Type" on page 98


Presence: [1..1]

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

Datatype: "ExternalDiscountAmountType1Code" on page 244


Presence: [1..1]

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


5.29 DocumentAdjustment1

31 May 2020 99

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] 100

CreditDebitIndicator <CdtDbtInd> [0..1] 100

Reason <Rsn> [0..1] 100

AdditionalInformation <AddtlInf> [0..1] 100

Used in element(s)

"AdjustmentAmountAndReason" on page 182, "AdjustmentAmountAndReason" on page 184


Presence: [1..1]

Definition: Amount of money of the document adjustment.


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

5.29.3 ReasonXML Tag: Rsn

Presence: [0..1]

Definition: Specifies the reason for the adjustment.


5.29.4 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Provides further details on the document adjustment.


5.30 DocumentLineIdentification1


Message Components

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



Page

Type <Tp> [0..1] 101

Number <Nb> [0..1] 101

RelatedDate <RltdDt> [0..1] 101

Used in element(s)

"Identification" on page 102


Presence: [0..1]

Definition: Specifies the type of referred document line identification.

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



Page



5.30.2 NumberXML Tag: Nb

Presence: [0..1]

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


5.30.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document line.


5.31 DocumentLineInformation1Definition: Provides document line information.

31 May 2020 101

Usage Guideline



Page

Identification <Id> [1..*] 102

Description <Desc> [0..1] 102

Amount <Amt> [0..1] 102

Used in element(s)

"LineDetails" on page 177


Presence: [1..*]

Definition: Provides identification of the document line.

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



Page

Type <Tp> [0..1] 101

Number <Nb> [0..1] 101


5.31.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 183 fordetails)



Page

DuePayableAmount <DuePyblAmt> [0..1] 183

DiscountAppliedAmount <DscntApldAmt> [0..*] 184

CreditNoteAmount <CdtNoteAmt> [0..1] 184

TaxAmount <TaxAmt> [0..*] 184

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 184

RemittedAmount <RmtdAmt> [0..1] 185

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



Page



Used in element(s)

"Type" on page 101


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 104 for details)



Page

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



31 May 2020 103

Usage Guideline

Presence: [0..1]

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


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



Page

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


Used in element(s)



Presence: [1..1]

Definition: Line identification type in a coded form.

Datatype: "ExternalDocumentLineType1Code" on page 245


Presence: [1..1]

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


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



Page

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


Used in element(s)



Message Components


Presence: [1..1]


Datatype: "ExternalFinancialInstitutionIdentification1Code" on page 245


Presence: [1..1]



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



Page



LEI <LEI> [0..1] 106

Name <Nm> [0..1] 106


Other <Othr> [0..1] 107

Used in element(s)

"FinancialInstitutionIdentification" on page 27

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

5.35.2 ClearingSystemMemberIdentificationXML Tag: ClrSysMmbId

Presence: [0..1]

31 May 2020 105

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 53 for details)



Page


MemberIdentification <MmbId> [1..1] 53


Presence: [0..1]

Definition: Legal entity identifier of the financial institution.



Presence: [0..1]




Presence: [0..1]



Message Components




Page







Floor <Flr> [0..1] 164


Room <Room> [0..1] 164









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 124 for details)



Page




31 May 2020 107

Usage Guideline

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



Page

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


LEI <LEI> [0..1] 109

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


Other <Othr> [0..1] 114

Used in element(s)



Presence: [0..1]




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


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


• on pacs.008.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.008.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 53 for details)



Page




Presence: [0..1]




Presence: [0..1]




Presence: [0..1]


31 May 2020 109

Usage Guideline

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



Page







Floor <Flr> [0..1] 170


Room <Room> [0..1] 171







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] 172


• on pacs.008.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.This rule is inherited verbatim from CBPR+.

• on pacs.008.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.This rule is inherited verbatim from CBPR+.

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


Message Components


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

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


If "PostalAddress" is used, and if AddressLine is absent, then Town Name and Country must be present.

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



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



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



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



• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/PostalAddress



• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/PostalAddress

31 May 2020 111

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.008.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/PostalAddress



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



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



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



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



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



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


Message Components



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



• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/FinancialInsti-tutionIdentification/PostalAddress












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

– Lynx_StructuredvsUnstructuredRule:



31 May 2020 113

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+



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+











Presence: [0..1]



Message Components




Page





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

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

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

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

• This element(pacs.008.001.08/CreditTransferTransactionInformation/ChargesInforma-tion/Agent/FinancialInstitutionIdentification/Other) is removed.

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

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

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

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

• This element(pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent2/Fi-nancialInstitutionIdentification/Other) is removed.


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



31 May 2020 115

Usage Guideline

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



Page



LEI <LEI> [0..1] 116

Name <Nm> [0..1] 117


Other <Othr> [0..1] 118

Used in element(s)



Presence: [0..1]




Presence: [0..1]


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



Page




Presence: [0..1]


Message Components




Presence: [0..1]




Presence: [0..1]





Page







Floor <Flr> [0..1] 170


Room <Room> [0..1] 171







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

31 May 2020 117

Usage Guideline









Presence: [0..1]





Page






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


Message Components



Page

Type <Tp> [1..1] 119

Garnishee <Grnshee> [0..1] 119

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 120


Date <Dt> [0..1] 120


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 121

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 121

Used in element(s)

"GarnishmentRemittance" on page 203


Presence: [1..1]

Definition: Specifies the type of garnishment.

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



Page



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

31 May 2020 119

Usage Guideline

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



Page

Name <Nm> [0..1] 144





5.38.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 144 for details)



Page

Name <Nm> [0..1] 144





5.38.4 ReferenceNumberXML Tag: RefNb

Presence: [0..1]

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


5.38.5 DateXML Tag: Dt

Presence: [0..1]

Definition: Date of payment which garnishment was taken from.


Message Components


5.38.6 RemittedAmountXML Tag: RmtdAmt

Presence: [0..1]

Definition: Amount of money remitted for the referred document.


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

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

5.39 GarnishmentType1Definition: Specifies the type of garnishment.



Page



Used in element(s)

"Type" on page 119


Presence: [1..1]

Definition: Provides the type details of the garnishment.

31 May 2020 121

Usage Guideline

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



Page

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



Presence: [0..1]

Definition: Identification of the issuer of the garnishment type.


5.40 GarnishmentType1ChoiceDefinition: Specifies the type of garnishment.



Page

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


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 246



Message Components

Presence: [1..1]

Definition: Proprietary identification of the type of garnishment.


5.41 GenericAccountIdentification1Definition: Information related to a generic account identification.



Page




Used in element(s)

"Other" on page 25


Presence: [1..1]

Definition: Identification assigned by an institution.


5.41.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 26 for details)



Page

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



Presence: [0..1]

Definition: Entity that assigns the identification.

31 May 2020 123

Usage Guideline


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



Page




Used in element(s)

"Other" on page 107, "Other" on page 114, "Other" on page 118


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Presence: [0..1]


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



Page

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



Presence: [0..1]




Message Components

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



Page




Used in element(s)

"Proprietary" on page 27


Presence: [1..1]

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

Datatype: "Exact4AlphaNumericText" on page 240


Presence: [1..1]




Presence: [0..1]

Definition: Short textual description of the scheme.


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

31 May 2020 125

Usage Guideline



Page


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


Used in element(s)

"Other" on page 138


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 139 for details)



Page

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

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


• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/OrganisationI-dentification/Other/SchemeName

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


Presence: [0..1]



Message Components


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



Page




Used in element(s)

"Other" on page 160


Presence: [1..1]

Definition: Unique and unambiguous identification of a person.



Presence: [0..1]


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



Page

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



• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/PrivateIdentifi-cation/Other/SchemeName

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

31 May 2020 127

Usage Guideline


Presence: [0..1]



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



Page












Rules

R31 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.008.001.08/GroupHeader/TotalInterbankSettlementAmountAnd-DateRule) is removed.


Message Components

Used in element(s)

"GroupHeader" on page 21

5.46.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.46.2 CreationDateTimeXML Tag: CreDtTm

Presence: [1..1]

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


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


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

5.46.4 NumberOfTransactionsXML Tag: NbOfTxs

Presence: [1..1]

Definition: Number of individual transactions contained in the message.

Datatype: "Max15NumericText" on page 257


• on pacs.008.001.08/GroupHeader/NumberOfTransactions

31 May 2020 129

Usage Guideline

Single value: 1

5.46.5 ControlSumXML Tag: CtrlSum

Presence: [0..1]

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

Datatype: "DecimalNumber" on page 237


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

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


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

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



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

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


Message Components

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



Page

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

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

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

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ! 194

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] ! 194

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ! 195

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] ! 195

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ! 196

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] ! 196

5.46.9 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" onpage 154 for details)



Page


ClearingChannel <ClrChanl> [0..1] 155

ServiceLevel <SvcLvl> [0..*] 155

LocalInstrument <LclInstrm> [0..1] 155

CategoryPurpose <CtgyPurp> [0..1] 156


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

5.46.10 InstructingAgentXML Tag: InstgAgt

31 May 2020 131

Usage Guideline

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 27 for details)



Page




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

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

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



Page




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

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



Page




Message Components

Used in element(s)

"MarketPractice" on page 17

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


5.48 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] 133

InstructionInformation <InstrInf> [0..1] 134

Used in element(s)

"InstructionForCreditorAgent" on page 89


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 254

31 May 2020 133

Usage Guideline

5.48.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.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] 134

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

Used in element(s)

"InstructionForNextAgent" on page 90


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.

Datatype: "Instruction4Code" on page 255


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

5.49.2 InstructionInformationXML Tag: InstrInf

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.



Message Components

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] 135


Used in element(s)

"LocalInstrument" on page 155


Presence: [1..1]

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

Datatype: "ExternalLocalInstrument1Code" on page 247


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.



Page

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


Used in element(s)

"LocalInstrument" on page 158


31 May 2020 135

Usage Guideline

Presence: [1..1]

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

Datatype: "ExternalLocalInstrument1Code" on page 247


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


Presence: [1..1]

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


5.52 NameAndAddress16__1Definition: Information that locates and identifies a party.



Page

Name <Nm> [1..1] 136

Address <Adr> [1..1] 136

Used in element(s)

"PostalAddress" on page 188


Presence: [1..1]

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


5.52.2 AddressXML Tag: Adr

Presence: [1..1]

Definition: Postal address of a party.


Message Components

The Adr block contains the following elements (see datatype "PostalAddress24__1" on page 167 fordetails)



Page







Floor <Flr> [0..1] 170


Room <Room> [0..1] 171







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

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



Page

AnyBIC <AnyBIC> [0..1] 137

LEI <LEI> [0..1] 138

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] 138

Used in element(s)

"OrganisationIdentification" on page 141

5.53.1 AnyBICXML Tag: AnyBIC

31 May 2020 137

Usage Guideline

Presence: [0..1]

Definition: Business identification code of the organisation.

Datatype: "AnyBICDec2014Identifier" on page 226


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 125 for details)



Page





• on pacs.008.001.08/CreditTransferTransactionInformation/Creditor/Identification/Organisa-tionIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/OrganisationI-dentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/Identification/Organi-sationIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/Garnishee/Identification/OrganisationIdentification/Other



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/GarnishmentAdministrator/Identification/OrganisationIdentifi-cation/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicee/Identification/OrganisationIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicer/Identification/OrganisationIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/Identification/Or-ganisationIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Identification/Or-ganisationIdentification/Other


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



Page

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


Used in element(s)



Presence: [1..1]


Datatype: "ExternalOrganisationIdentification1Code" on page 248


Presence: [1..1]


31 May 2020 139

Usage Guideline



• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/OrganisationI-dentification/Other/SchemeName/Proprietary

Comment:CBPR+ removes this

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



Page

ChannelType <ChanlTp> [1..1] 140


Used in element(s)

"Other" on page 61

5.55.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.56 Party38ChoiceDefinition: Nature or use of the account.


Message Components



Page

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

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

Used in element(s)

"Identification" on page 145, "Identification" on page 150

5.56.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 137 for details)



Page

AnyBIC <AnyBIC> [0..1] 137

LEI <LEI> [0..1] 138


5.56.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 159for details)



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 159


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

31 May 2020 141

Usage Guideline



Page



Used in element(s)

"From" on page 15, "From" on page 37, "To" on page 15, "To" on page 38

5.57.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 144for details)



Page

Name <Nm> [0..1] 144



CountryOfResidence <CtryOfRes> [0..1] 146



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

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

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

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

5.57.2 FinancialInstitutionIdentificationXML Tag: FIId

Presence: [1..1]

Definition: Identification of a financial institution.


Message Components

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



Page




• on pacs.008.001.08/.header/From/FinancialInstitutionIdentification




• on pacs.008.001.08/.header/To/FinancialInstitutionIdentification




• on pacs.008.001.08/.header/Related/To/FinancialInstitutionIdentification



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-

31 May 2020 143

Usage Guideline

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.

• on pacs.008.001.08/.header/Related/From/FinancialInstitutionIdentification




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



Page

Name <Nm> [0..1] 144


Identification <Id> [0..1] ! 145



Used in element(s)

"Garnishee" on page 119, "GarnishmentAdministrator" on page 120, "InitiatingParty" on page 82,"Invoicee" on page 202, "Invoicer" on page 202, "OrganisationIdentification" on page 142, "Ulti-mateCreditor" on page 88, "UltimateDebtor" on page 81


Presence: [0..1]



5.58.2 PostalAddress


Message Components

XML Tag: PstlAdr

Presence: [0..1]





Page







Floor <Flr> [0..1] 164


Room <Room> [0..1] 164

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








Presence: [0..1]

Definition: Unique and unambiguous identification of a party.

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



Page



31 May 2020 145

Usage Guideline


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Identification

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

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.008.001.08/CreditTransferTransactionInformation/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.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/Garnishee/CountryOfResidence


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/GarnishmentAdministrator/CountryOfResidence


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicee/CountryOfResidence


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicer/CountryOfResidence


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/CountryOfResi-dence


Message Components


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 59 for details)



Page


Name <Nm> [0..1] 59












• This element(pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/Contact-Details) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/Garnishee/ContactDetails) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/GarnishmentAdministrator/ContactDetails) is re-moved.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicee/ContactDetails) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicer/ContactDetails) is removed.

31 May 2020 147

Usage Guideline

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/Con-tactDetails) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Contact-Details) is removed.

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



Page

Name <Nm> [0..1] 148




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

Used in element(s)

"Creditor" on page 87, "Debtor" on page 82


Presence: [0..1]




Presence: [0..1]



Message Components




Page







Floor <Flr> [0..1] 170


Room <Room> [0..1] 171







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


• on pacs.008.001.08/CreditTransferTransactionInformation/Creditor/PostalAddress

Comment:Structured Postal Address is recommended.

• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/PostalAddress

Comment:Structured Postal Address is recommended.





31 May 2020 149

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 140 for details)



Page



5.59.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.008.001.08/CreditTransferTransactionInformation/Creditor/CountryOfResidence



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/CountryOfResidence


5.59.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 59 for details)



Page


Name <Nm> [0..1] 59












• This element(pacs.008.001.08/CreditTransferTransactionInformation/Creditor/ContactDetails)is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/Debtor/ContactDetails) isremoved.

5.60 PaymentIdentification7__1Definition: Provides further means of referencing a payment transaction.

31 May 2020 151

Usage Guideline



Page

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

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

TransactionIdentification <TxId> [0..1] 153

UETR <UETR> [0..1] 154

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

Rules

R51 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.60.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.008.001.08/CreditTransferTransactionInformation/PaymentIdentification/InstructionI-dentification



Synonym (MT 103 - field 20): Sender's Reference



Message Components

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.60.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.008.001.08/CreditTransferTransactionInformation/PaymentIdentification/EndToEndI-dentification

Synonym (MT 103 - field 70 - code /ROC/): Remittance Information

• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentIdentification/EndToEndI-dentification

Comment:If no End To End Identification is provided by the Debtor, then the element must be populated with "NOTPROVIDED".

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

31 May 2020 153

Usage Guideline


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


• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentIdentification/UETR


5.60.5 ClearingSystemReferenceXML Tag: ClrSysRef

Presence: [0..1]

Definition: Unique reference, as assigned by a clearing system, to unambiguously identify the instruc-tion.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/PaymentIdentifica-tion/ClearingSystemReference) will be ignored by the Receiver.

• on pacs.008.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.008. It is not a reference assigned by Lynx. Therefore, from a Lynx perspective, it is ignored.

5.61 PaymentTypeInformation28Definition: Provides further details of the type of payment.


Message Components



Page


ClearingChannel <ClrChanl> [0..1] 155

ServiceLevel <SvcLvl> [0..*] 155

LocalInstrument <LclInstrm> [0..1] 155

CategoryPurpose <CtgyPurp> [0..1] 156

Used in element(s)

"PaymentTypeInformation" on page 131

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 233

5.61.3 ServiceLevelXML 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 188for details)



Page

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


5.61.4 LocalInstrument

31 May 2020 155

Usage Guideline

XML Tag: LclInstrm

Presence: [0..1]

Definition: User community specific instrument.

Usage: This element is used to specify a local instrument, local clearing option and/or further qualify theservice or service level.

The LclInstrm block contains the following elements (see datatype "LocalInstrument2Choice" onpage 135 for details)



Page

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


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 45 for details)



Page

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


5.62 PaymentTypeInformation28__1Definition: Provides further details of the type of payment.



Page


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

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

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

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


Message Components

Used in element(s)

"PaymentTypeInformation" on page 67

5.62.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.62.2 ClearingChannelXML Tag: ClrChanl

Presence: [0..1]

Definition: Specifies the clearing channel to be used to process the payment instruction.

Datatype: "ClearingChannel2Code" on page 233


• This element(pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInforma-tion/ClearingChannel) is removed.

5.62.3 ServiceLevelXML 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 188for details)



Page

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



• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Ser-viceLevel


• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Ser-viceLevel

31 May 2020 157

Usage Guideline

Comment:Must contain at least 1 GPI code.

5.62.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 135 for details)



Page

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



• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/LocalIn-strument


• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/LocalIn-strument

– 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)

5.62.5 CategoryPurposeXML Tag: CtgyPurp

Presence: [0..1]

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


Message Components


The CtgyPurp block contains the following elements (see datatype "CategoryPurpose1Choice" onpage 45 for details)



Page

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



• on pacs.008.001.08/CreditTransferTransactionInformation/PaymentTypeInformation/Category-Purpose

Comment:Code is the preferred option.

5.63 PersonIdentification13Definition: Unique and unambiguous way to identify a person.



Page

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 159


Used in element(s)

"PrivateIdentification" on page 141

5.63.1 DateAndPlaceOfBirthXML Tag: DtAndPlcOfBirth

Presence: [0..1]

Definition: Date and place of birth of a person.

31 May 2020 159

Usage Guideline

The DtAndPlcOfBirth block contains the following elements (see datatype "DateAndPlaceOfBirth1" onpage 96 for details)



Page

BirthDate <BirthDt> [1..1] 97

ProvinceOfBirth <PrvcOfBirth> [0..1] 97

CityOfBirth <CityOfBirth> [1..1] 97

CountryOfBirth <CtryOfBirth> [1..1] 97


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 127 for details)



Page





• on pacs.008.001.08/CreditTransferTransactionInformation/Creditor/Identification/PrivateIdenti-fication/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/PrivateIdentifi-cation/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/Identification/Pri-vateIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/Garnishee/Identification/PrivateIdentification/Other



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/GarnishmentAdministrator/Identification/PrivateIdentifica-tion/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicee/Identification/PrivateIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicer/Identification/PrivateIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/Identification/Pri-vateIdentification/Other


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Identification/Pri-vateIdentification/Other


5.64 PersonIdentificationSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification scheme.



Page

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


Used in element(s)



Presence: [1..1]


Datatype: "ExternalPersonIdentification1Code" on page 248


Presence: [1..1]


31 May 2020 161

Usage Guideline



• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/Identification/PrivateIdentifi-cation/Other/SchemeName/Proprietary

Comment:CBPR+ removes this

5.65 PostalAddress24Definition: Information that locates and identifies a specific address, as defined by postal services.



Page







Floor <Flr> [0..1] 164


Room <Room> [0..1] 164

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







Used in element(s)

"PostalAddress" on page 106, "PostalAddress" on page 35, "PostalAddress" on page 144

5.65.1 AddressTypeXML Tag: AdrTp

Presence: [0..1]


Message Components

Definition: Identifies the nature of the postal address.

The AdrTp block contains the following elements (see datatype "AddressType3Choice" on page 26for details)



Page

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



• This element(pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/PostalAd-dress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/Garnishee/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/GarnishmentAdministrator/PostalAddress/Ad-dressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicee/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicer/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/Postal-Address/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Postal-Address/AddressType) is removed.

5.65.2 DepartmentXML Tag: Dept

Presence: [0..1]



5.65.3 SubDepartmentXML Tag: SubDept

Presence: [0..1]

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


5.65.4 StreetName

31 May 2020 163

Usage Guideline

XML 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

Presence: [0..1]

Definition: Building room number.


5.65.10 PostCodeXML Tag: PstCd


Message Components

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.



• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/PostalAd-dress/PostCode

Comment:It is recommended to add Post Code if available.

5.65.11 TownNameXML Tag: TwnNm

Presence: [0..1]

Definition: Name of a built-up area, with defined boundaries, and a local government.



• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/PostalAd-dress/TownName


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/Garnishee/PostalAddress/TownName


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/GarnishmentAdministrator/PostalAddress/TownName


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicee/PostalAddress/TownName


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicer/PostalAddress/TownName


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/PostalAd-dress/TownName


5.65.12 TownLocationNameXML Tag: TwnLctnNm

31 May 2020 165

Usage Guideline

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]

Definition: Nation with its own government.



• on pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/PostalAd-dress/Country


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/Garnishee/PostalAddress/Country


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/GarnishmentRemittance/GarnishmentAdministrator/PostalAddress/Country


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicee/PostalAddress/Country


• on pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Struc-tured/Invoicer/PostalAddress/Country



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/PostalAd-dress/Country


• on pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/PostalAd-dress/Country


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.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/InitiatingParty/PostalAd-dress/AddressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/Garnishee/PostalAddress/AddressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/GarnishmentRemittance/GarnishmentAdministrator/PostalAddress/Ad-dressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicee/PostalAddress/AddressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/RemittanceInforma-tion/Structured/Invoicer/PostalAddress/AddressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateCreditor/Postal-Address/AddressLine) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/UltimateDebtor/Postal-Address/AddressLine) is removed.

5.66 PostalAddress24__1Definition: Information that locates and identifies a specific address, as defined by postal services.

31 May 2020 167

Usage Guideline



Page







Floor <Flr> [0..1] 170


Room <Room> [0..1] 171







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] 172

Used in element(s)

"Address" on page 136, "PostalAddress" on page 109, "PostalAddress" on page 117, "PostalAd-dress" on page 148

5.66.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 26for details)



Page

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



Message Components


• This element(pacs.008.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/.header/Related/From/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/.header/Related/To/FinancialInstitutionIdentification/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/.header/To/FinancialInstitutionIdentification/FinancialInstitu-tionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/ChargesInforma-tion/Agent/FinancialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/Creditor/PostalAd-dress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/Debtor/PostalAd-dress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialIn-stitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/InstructedAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/InstructingAgent/Finan-cialInstitutionIdentification/PostalAddress/AddressType) is removed.

• This element(pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/Fi-nancialInstitutionIdentification/PostalAddress/AddressType) is removed.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/PreviousInstructingA-gent1/FinancialInstitutionIdentification/PostalAddress/AddressType) is removed.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/RelatedRemittanceInfor-mation/RemittanceLocationDetails/PostalAddress/Address/AddressType) is removed.

5.66.2 Department

31 May 2020 169

Usage Guideline

XML Tag: Dept

Presence: [0..1]



5.66.3 SubDepartmentXML Tag: SubDept

Presence: [0..1]

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


5.66.4 StreetNameXML Tag: StrtNm

Presence: [0..1]

Definition: Name of a street or thoroughfare.


5.66.5 BuildingNumberXML Tag: BldgNb

Presence: [0..1]

Definition: Number that identifies the position of a building on a street.


5.66.6 BuildingNameXML Tag: BldgNm

Presence: [0..1]

Definition: Name of the building or house.


5.66.7 FloorXML Tag: Flr

Presence: [0..1]

Definition: Floor or storey within a building.


5.66.8 PostBoxXML Tag: PstBx

Presence: [0..1]


Message Components

Definition: Numbered box in a post office, assigned to a person or organisation, where letters are keptuntil called for.


5.66.9 RoomXML Tag: Room

Presence: [0..1]

Definition: Building room number.


5.66.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.66.11 TownNameXML Tag: TwnNm

Presence: [0..1]

Definition: Name of a built-up area, with defined boundaries, and a local government.


5.66.12 TownLocationNameXML Tag: TwnLctnNm

Presence: [0..1]

Definition: Specific location name within the town.


5.66.13 DistrictNameXML Tag: DstrctNm

Presence: [0..1]

Definition: Identifies a subdivision within a country sub-division.


5.66.14 CountrySubDivisionXML Tag: CtrySubDvsn

Presence: [0..1]

Definition: Identifies a subdivision of a country such as state, region, county.

31 May 2020 171

Usage Guideline



Presence: [0..1]

Definition: Nation with its own government.


5.66.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.008.001.08/.header/From/FinancialInstitutionIdentification/FinancialInstitutionIdentifi-cation/PostalAddress/AddressLine


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


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


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


• on pacs.008.001.08/CreditTransferTransactionInformation/ChargesInformation/Agent/Finan-cialInstitutionIdentification/PostalAddress/AddressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/Creditor/PostalAddress/Ad-dressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/CreditorAgent/FinancialInstitutionI-dentification/PostalAddress/AddressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/Debtor/PostalAddress/AddressLine



Message Components

• on pacs.008.001.08/CreditTransferTransactionInformation/DebtorAgent/FinancialInstitutionI-dentification/PostalAddress/AddressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructedAgent/FinancialInstitu-tionIdentification/PostalAddress/AddressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/InstructingAgent/FinancialInstitu-tionIdentification/PostalAddress/AddressLine


• on pacs.008.001.08/CreditTransferTransactionInformation/IntermediaryAgent1/FinancialInsti-tutionIdentification/PostalAddress/AddressLine






• on pacs.008.001.08/CreditTransferTransactionInformation/PreviousInstructingAgent1/Finan-cialInstitutionIdentification/PostalAddress/AddressLine






• on pacs.008.001.08/CreditTransferTransactionInformation/RelatedRemittanceInformation/Re-mittanceLocationDetails/PostalAddress/Address/AddressLine


5.67 ProxyAccountIdentification1Definition: Information related to a proxy identification of the account.



Page

Type <Tp> [0..1] 174


31 May 2020 173

Usage Guideline

Used in element(s)

"Proxy" on page 43


Presence: [0..1]

Definition: Type of the proxy identification.

The Tp block contains the following elements (see datatype "ProxyAccountType1Choice" onpage 175 for details)



Page

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



Presence: [1..1]

Definition: Identification used to indicate the account identification under another specified name.


5.68 ProxyAccountIdentification1__1Definition: Information related to a proxy identification of the account.



Page

Type <Tp> [0..1] 174


Used in element(s)

"Proxy" on page 45


Presence: [0..1]

Definition: Type of the proxy identification.


Message Components

The Tp block contains the following elements (see datatype "ProxyAccountType1Choice" onpage 175 for details)



Page

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



Presence: [1..1]

Definition: Identification used to indicate the account identification under another specified name.

Datatype: "CBPR_RestrictedFINXMax320Text_Extended" on page 230

5.69 ProxyAccountType1ChoiceDefinition: Specifies the scheme used for the identification of an account alias.



Page

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


Used in element(s)

"Type" on page 174, "Type" on page 174


Presence: [1..1]


Datatype: "ExternalProxyAccountType1Code" on page 249


Presence: [1..1]



5.70 Purpose2Choice

31 May 2020 175

Usage Guideline

Definition: Specifies the underlying reason for the payment transaction.

Usage: Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) credi-tor to provide information concerning the nature of the payment. Purpose is a content element, which isnot used for processing by any of the agents involved in the payment chain.



Page

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


Used in element(s)

"Purpose" on page 91


Presence: [1..1]

Definition: Underlying reason for the payment transaction, as published in an external purpose code list.

Datatype: "ExternalPurpose1Code" on page 250


Presence: [1..1]

Definition: Purpose, in a proprietary form.


5.71 ReferredDocumentInformation7Definition: Set of elements used to identify the documents referred to in the remittance information.



Page

Type <Tp> [0..1] 177

Number <Nb> [0..1] 177


LineDetails <LineDtls> [0..*] 177

Used in element(s)

"ReferredDocumentInformation" on page 200


Message Components


Presence: [0..1]

Definition: Specifies the type of referred document.

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



Page



5.71.2 NumberXML Tag: Nb

Presence: [0..1]

Definition: Unique and unambiguous identification of the referred document.


5.71.3 RelatedDateXML Tag: RltdDt

Presence: [0..1]

Definition: Date associated with the referred document.


5.71.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 101 for details)



Page

Identification <Id> [1..*] 102

Description <Desc> [0..1] 102

Amount <Amt> [0..1] 102

31 May 2020 177

Usage Guideline

5.72 ReferredDocumentType3ChoiceDefinition: Specifies the type of the document referred in the remittance information.



Page

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


Used in element(s)



Presence: [1..1]

Definition: Document type in a coded form.

Datatype: "DocumentType6Code" on page 237


Presence: [1..1]

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


5.73 ReferredDocumentType4Definition: Specifies the type of the document referred in the remittance information.



Page



Used in element(s)

"Type" on page 177


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 178 for details)



Page

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



Presence: [0..1]

Definition: Identification of the issuer of the reference document type.


5.74 RegulatoryAuthority2Definition: Entity requiring the regulatory reporting information.



Page

Name <Nm> [0..1] 179


Used in element(s)

"Authority" on page 180


Presence: [0..1]

Definition: Name of the entity requiring the regulatory reporting information.



Presence: [0..1]

Definition: Country of the entity that requires the regulatory reporting information.


5.75 RegulatoryReporting3

31 May 2020 179

Usage Guideline

Definition: Information needed due to regulatory and/or statutory requirements.



Page

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] 180

Authority <Authrty> [0..1] 180


Used in element(s)

"RegulatoryReporting" on page 91

5.75.1 DebitCreditReportingIndicatorXML Tag: DbtCdtRptgInd

Presence: [0..1]

Definition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Datatype: "RegulatoryReportingType1Code" on page 264

5.75.2 AuthorityXML Tag: Authrty

Presence: [0..1]

Definition: Entity requiring the regulatory reporting information.

The Authrty block contains the following elements (see datatype "RegulatoryAuthority2" on page 179for details)



Page

Name <Nm> [0..1] 179


5.75.3 DetailsXML Tag: Dtls

Presence: [0..*]

Definition: Set of elements used to provide details on the regulatory reporting information.


Message Components

The Dtls block contains the following elements (see datatype "StructuredRegulatoryReporting3" onpage 198 for details)



Page

Type <Tp> [0..1] 199

Date <Dt> [0..1] 199


Code <Cd> [0..1] 199

Amount <Amt> [0..1] 200

Information <Inf> [0..*] 200

5.76 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 201

5.76.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


5.76.2 DiscountAppliedAmountXML Tag: DscntApldAmt

31 May 2020 181

Usage Guideline

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 98 for details)



Page

Type <Tp> [0..1] 98


5.76.3 CreditNoteAmountXML Tag: CdtNoteAmt

Presence: [0..1]

Definition: Amount specified for the referred document is the amount of a credit note.


5.76.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 206 for details)



Page

Type <Tp> [0..1] 206

Amount <Amt> [1..1] 207

5.76.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 99 for details)



Page

Amount <Amt> [1..1] 100


Reason <Rsn> [0..1] 100



Presence: [0..1]

Definition: Amount of money remitted for the referred document.


5.77 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 102

5.77.1 DuePayableAmountXML Tag: DuePyblAmt

Presence: [0..1]

Definition: Amount specified is the exact amount due and payable to the creditor.


31 May 2020 183

Usage Guideline

5.77.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 98 for details)



Page

Type <Tp> [0..1] 98


5.77.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 206 for details)



Page

Type <Tp> [0..1] 206

Amount <Amt> [1..1] 207

5.77.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 99 for details)



Page

Amount <Amt> [1..1] 100


Reason <Rsn> [0..1] 100



Presence: [0..1]

Definition: Amount of money remitted.


5.78 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] 185

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

Used in element(s)

"RemittanceInformation" on page 93

5.78.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.008.001.08/CreditTransferTransactionInformation/RemittanceInformation/Unstruc-tured

31 May 2020 185

Usage Guideline


5.78.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 200 for details)



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] 200

ReferredDocumentAmount <RfrdDocAmt> [0..1] 201

CreditorReferenceInformation <CdtrRefInf> [0..1] 201

Invoicer <Invcr> [0..1] 202

Invoicee <Invcee> [0..1] 202

TaxRemittance <TaxRmt> [0..1] 203

GarnishmentRemittance <GrnshmtRmt> [0..1] 203

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 204


• on pacs.008.001.08/CreditTransferTransactionInformation/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.79 RemittanceLocation7__1Definition: Provides information on the remittance advice.


Message Components



Page

RemittanceIdentification <RmtId> [0..1] 187

RemittanceLocationDetails <RmtLctnDtls> [0..*] 187

Used in element(s)

"RelatedRemittanceInformation" on page 93

5.79.1 RemittanceIdentificationXML Tag: RmtId

Presence: [0..1]

Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the remit-tance information sent separately from the payment instruction, such as a remittance advice.


5.79.2 RemittanceLocationDetailsXML Tag: RmtLctnDtls

Presence: [0..*]

Definition: Set of elements used to provide information on the location and/or delivery of the remittanceinformation.

The RmtLctnDtls block contains the following elements (see datatype "RemittanceLocationData1__1"on page 187 for details)



Page

Method <Mtd> [1..1] 188

ElectronicAddress <ElctrncAdr> [0..1] ! 188


5.80 RemittanceLocationData1__1Definition: Provides additional details on the remittance advice.



Page

Method <Mtd> [1..1] 188

ElectronicAddress <ElctrncAdr> [0..1] ! 188


31 May 2020 187

Usage Guideline

Used in element(s)

"RemittanceLocationDetails" on page 187

5.80.1 MethodXML Tag: Mtd

Presence: [1..1]

Definition: Method used to deliver the remittance advice information.

Datatype: "RemittanceLocationMethod2Code" on page 265

5.80.2 ElectronicAddressXML Tag: ElctrncAdr

Presence: [0..1]

Definition: Electronic address to which an agent is to send the remittance information.



Presence: [0..1]

Definition: Postal address to which an agent is to send the remittance information.

The PstlAdr block contains the following elements (see datatype "NameAndAddress16__1" onpage 136 for details)



Page

Name <Nm> [1..1] 136

Address <Adr> [1..1] 136

5.81 ServiceLevel8ChoiceDefinition: Specifies the service level of the transaction.



Page

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


Used in element(s)

"ServiceLevel" on page 155, "ServiceLevel" on page 157


Message Components


Presence: [1..1]

Definition: Specifies a pre-agreed service or level of service between the parties, as published in an ex-ternal service level code list.

Datatype: "ExternalServiceLevel1Code" on page 251


Presence: [1..1]

Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.


5.82 SettlementDateTimeIndication1Definition: Information on the occurred settlement time(s) of the payment transaction.



Page

DebitDateTime <DbtDtTm> [0..1] 189

CreditDateTime <CdtDtTm> [0..1] 189

Used in element(s)

"SettlementTimeIndication" on page 69

5.82.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.82.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).


31 May 2020 189

Usage Guideline

5.83 SettlementInstruction7Definition: Provides further details on the settlement of the instruction.



Page

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

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

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

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ! 194

InstructingReimbursementAgentAc-count

<InstgRmbrsmntAgtAcct> [0..1] ! 194

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ! 195

InstructedReimbursementAgentAc-count

<InstdRmbrsmntAgtAcct> [0..1] ! 195

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ! 196

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> [0..1] ! 196

Rules

R23 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.008.001.08/GroupHeader/SettlementInformation/ThirdReim-bursementAgentRule) is removed.

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


Message Components


– This rule(pacs.008.001.08/GroupHeader/SettlementInformation/Settlement-MethodAgentRule) is removed.

R25 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.008.001.08/GroupHeader/SettlementInformation/Settlement-MethodCoverRule) is removed.

R26 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.008.001.08/GroupHeader/SettlementInformation/Settlement-MethodCoverAgentRule) is removed.

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

R28 InstructingReimbursementAgentAccountRule ✓

If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgentmust be present.

31 May 2020 191

Usage Guideline

Error handling:



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


– This rule(pacs.008.001.08/GroupHeader/SettlementInformation/InstructingRe-imbursementAgentAccountRule) is removed.

R29 InstructedReimbursementAgentAccountRule ✓

If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgentmust be present.

Error handling:



– Error Text: Invalid message content for instructed reimbursement agent account.


– This rule(pacs.008.001.08/GroupHeader/SettlementInformation/InstructedReim-bursementAgentAccountRule) is removed.

R30 ThirdReimbursementAgentAccountRule ✓

If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must bepresent.

Error handling:



– Error Text: Invalid message content for third reimbursement agent account.


– This rule(pacs.008.001.08/GroupHeader/SettlementInformation/ThirdReim-bursementAgentAccountRule) is removed.

Used in element(s)

"SettlementInformation" on page 130

5.83.1 SettlementMethodXML Tag: SttlmMtd

Presence: [1..1]


Message Components

Definition: Method used to settle the (batch of) payment instructions.

Datatype: "SettlementMethod1Code" on page 267

5.83.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 41for details)



Page


Type <Tp> [0..1] 42


Name <Nm> [0..1] 42



• This element(pacs.008.001.08/GroupHeader/SettlementInformation/SettlementAccount) is re-moved.

5.83.3 ClearingSystemXML Tag: ClrSys

Presence: [0..1]


The ClrSys block contains the following elements (see datatype "ClearingSystemIdentification3Choice"on page 52 for details)



Page

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



• on pacs.008.001.08/GroupHeader/SettlementInformation/ClearingSystem

31 May 2020 193

Usage Guideline


5.83.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 27 for details)



Page




• This element(pacs.008.001.08/GroupHeader/SettlementInformation/InstructingReimbursemen-tAgent) is removed.

5.83.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 41 for details)



Page


Type <Tp> [0..1] 42


Name <Nm> [0..1] 42



Message Components


• This element(pacs.008.001.08/GroupHeader/SettlementInformation/InstructingReimbursemen-tAgentAccount) is removed.

5.83.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 27 for details)



Page




• This element(pacs.008.001.08/GroupHeader/SettlementInformation/InstructedReimbursement-Agent) is removed.

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

31 May 2020 195

Usage Guideline

The InstdRmbrsmntAgtAcct block contains the following elements (see datatype "CashAccount38" onpage 41 for details)



Page


Type <Tp> [0..1] 42


Name <Nm> [0..1] 42



• This element(pacs.008.001.08/GroupHeader/SettlementInformation/InstructedReimbursement-AgentAccount) is removed.

5.83.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 27 for details)



Page




• This element(pacs.008.001.08/GroupHeader/SettlementInformation/ThirdReimbursementA-gent) is removed.

5.83.9 ThirdReimbursementAgentAccountXML Tag: ThrdRmbrsmntAgtAcct

Presence: [0..1]


Message Components

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 41 for details)



Page


Type <Tp> [0..1] 42


Name <Nm> [0..1] 42



• This element(pacs.008.001.08/GroupHeader/SettlementInformation/ThirdReimbursementA-gentAccount) is removed.

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



Page

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

TillTime <TillTm> [0..1] 198

FromTime <FrTm> [0..1] 198

RejectTime <RjctTm> [0..1] 198

Used in element(s)

"SettlementTimeRequest" on page 69

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

31 May 2020 197

Usage Guideline


• This element(pacs.008.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/CLSTime) will be ignored by the Receiver.

• on pacs.008.001.08/CreditTransferTransactionInformation/SettlementTimeRequest/CLSTime

Synonym (MT 103 - field 13C - code CLSTIME): Time Indication

5.84.2 TillTimeXML Tag: TillTm

Presence: [0..1]

Definition: Time until when the payment may be settled.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/TillTime) will be ignored by the Receiver.

5.84.3 FromTimeXML Tag: FrTm

Presence: [0..1]

Definition: Time as from when the payment may be settled.


5.84.4 RejectTimeXML Tag: RjctTm

Presence: [0..1]

Definition: Time by when the payment must be settled to avoid rejection.



• This element(pacs.008.001.08/CreditTransferTransactionInformation/Settlement-TimeRequest/RejectTime) will be ignored by the Receiver.

5.85 StructuredRegulatoryReporting3Definition: Information needed due to regulatory and statutory requirements.


Message Components



Page

Type <Tp> [0..1] 199

Date <Dt> [0..1] 199


Code <Cd> [0..1] 199

Amount <Amt> [0..1] 200

Information <Inf> [0..*] 200

Used in element(s)

"Details" on page 180


Presence: [0..1]

Definition: Specifies the type of the information supplied in the regulatory reporting details.



Presence: [0..1]

Definition: Date related to the specified type of regulatory reporting details.



Presence: [0..1]

Definition: Country related to the specified type of regulatory reporting details.



Presence: [0..1]

Definition: Specifies the nature, purpose, and reason for the transaction to be reported for regulatoryand statutory requirements in a coded form.


31 May 2020 199

Usage Guideline


Presence: [0..1]

Definition: Amount of money to be reported for regulatory and statutory requirements.


5.85.6 InformationXML Tag: Inf

Presence: [0..*]

Definition: Additional details that cater for specific domestic regulatory requirements.


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



Page

ReferredDocumentInformation <RfrdDocInf> [0..*] 200

ReferredDocumentAmount <RfrdDocAmt> [0..1] 201

CreditorReferenceInformation <CdtrRefInf> [0..1] 201

Invoicer <Invcr> [0..1] 202

Invoicee <Invcee> [0..1] 202

TaxRemittance <TaxRmt> [0..1] 203

GarnishmentRemittance <GrnshmtRmt> [0..1] 203

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] 204

Used in element(s)

"Structured" on page 186

5.86.1 ReferredDocumentInformationXML Tag: RfrdDocInf

Presence: [0..*]

Definition: Provides the identification and the content of the referred document.


Message Components

The RfrdDocInf block contains the following elements (see datatype "ReferredDocumentInformation7"on page 176 for details)



Page

Type <Tp> [0..1] 177

Number <Nb> [0..1] 177


LineDetails <LineDtls> [0..*] 177

5.86.2 ReferredDocumentAmountXML Tag: RfrdDocAmt

Presence: [0..1]

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

The RfrdDocAmt block contains the following elements (see datatype "RemittanceAmount2" onpage 181 for details)



Page







5.86.3 CreditorReferenceInformationXML Tag: CdtrRefInf

Presence: [0..1]

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

31 May 2020 201

Usage Guideline

The CdtrRefInf block contains the following elements (see datatype "CreditorReferenceInformation2"on page 94 for details)



Page

Type <Tp> [0..1] 94

Reference <Ref> [0..1] 95

5.86.4 InvoicerXML Tag: Invcr

Presence: [0..1]

Definition: Identification of the organisation issuing the invoice, when it is different from the creditor orultimate creditor.

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



Page

Name <Nm> [0..1] 144





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


Message Components

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



Page

Name <Nm> [0..1] 144





5.86.6 TaxRemittanceXML Tag: TaxRmt

Presence: [0..1]

Definition: Provides remittance information about a payment made for tax-related purposes.

The TaxRmt block contains the following elements (see datatype "TaxInformation7" on page 208 fordetails)



Page



UltimateDebtor <UltmtDbtr> [0..1] 210



Method <Mtd> [0..1] 210



Date <Dt> [0..1] 211



5.86.7 GarnishmentRemittanceXML Tag: GrnshmtRmt

Presence: [0..1]

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

31 May 2020 203

Usage Guideline

The GrnshmtRmt block contains the following elements (see datatype "Garnishment3" on page 118for details)



Page

Type <Tp> [1..1] 119

Garnishee <Grnshee> [0..1] 119

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] 120


Date <Dt> [0..1] 120


FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] 121

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] 121

5.86.8 AdditionalRemittanceInformationXML Tag: AddtlRmtInf

Presence: [0..3]

Definition: Additional information, in free text form, to complement the structured remittance information.


5.87 SupplementaryData1Definition: Additional information that can not be captured in the structured fields and/or any other spe-cific block.



Page



Rules

R17 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 24, "SupplementaryData" on page 94


Message Components

5.87.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.87.2 EnvelopeXML Tag: Envlp

Presence: [1..1]

Definition: Technical element wrapping the supplementary data.

5.88 TaxAmount2Definition: Set of elements used to provide information on the tax amount(s) of tax record.



Page

Rate <Rate> [0..1] 205

TaxableBaseAmount <TaxblBaseAmt> [0..1] 205

TotalAmount <TtlAmt> [0..1] 206


Used in element(s)

"TaxAmount" on page 220

5.88.1 RateXML Tag: Rate

Presence: [0..1]

Definition: Rate used to calculate the tax.

Datatype: "PercentageRate" on page 262

5.88.2 TaxableBaseAmountXML Tag: TaxblBaseAmt

Presence: [0..1]

Definition: Amount of money on which the tax is based.


31 May 2020 205

Usage Guideline

5.88.3 TotalAmountXML Tag: TtlAmt

Presence: [0..1]

Definition: Total amount that is the result of the calculation of the tax for the record.


5.88.4 DetailsXML Tag: Dtls

Presence: [0..*]

Definition: Set of elements used to provide details on the tax period and amount.

The Dtls block contains the following elements (see datatype "TaxRecordDetails2" on page 220 fordetails)



Page

Period <Prd> [0..1] 221

Amount <Amt> [1..1] 221

5.89 TaxAmountAndType1Definition: Specifies the amount with a specific type.



Page

Type <Tp> [0..1] 206

Amount <Amt> [1..1] 207

Used in element(s)

"TaxAmount" on page 182, "TaxAmount" on page 184


Presence: [0..1]

Definition: Specifies the type of the amount.


Message Components

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



Page

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



Presence: [1..1]

Definition: Amount of money, which has been typed.


5.90 TaxAmountType1ChoiceDefinition: Specifies the amount type.



Page

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


Used in element(s)

"Type" on page 206


Presence: [1..1]

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

Datatype: "ExternalTaxAmountType1Code" on page 252


Presence: [1..1]

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


5.91 TaxAuthorisation1

31 May 2020 207

Usage Guideline

Definition: Details of the authorised tax paying party.



Page

Title <Titl> [0..1] 208

Name <Nm> [0..1] 208

Used in element(s)

"Authorisation" on page 217

5.91.1 TitleXML Tag: Titl

Presence: [0..1]

Definition: Title or position of debtor or the debtor's authorised representative.



Presence: [0..1]

Definition: Name of the debtor or the debtor's authorised representative.


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


Message Components



Page



UltimateDebtor <UltmtDbtr> [0..1] 210



Method <Mtd> [0..1] 210



Date <Dt> [0..1] 211



Used in element(s)

"TaxRemittance" on page 203


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 215 for details)



Page

TaxIdentification <TaxId> [0..1] 215

RegistrationIdentification <RegnId> [0..1] 215

TaxType <TaxTp> [0..1] 216


Presence: [0..1]

Definition: Identifies the party on the debit side of the transaction to which the tax applies.

31 May 2020 209

Usage Guideline

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



Page




Authorisation <Authstn> [0..1] 217

5.92.3 UltimateDebtorXML Tag: UltmtDbtr

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 216 for de-tails)



Page





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




Message Components

Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.92.7 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.92.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.92.10 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 261

5.92.11 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.

31 May 2020 211

Usage Guideline

The Rcrd block contains the following elements (see datatype "TaxRecord2" on page 218 for details)



Page

Type <Tp> [0..1] 218

Category <Ctgy> [0..1] 218

CategoryDetails <CtgyDtls> [0..1] 219

DebtorStatus <DbtrSts> [0..1] 219

CertificateIdentification <CertId> [0..1] 219

FormsCode <FrmsCd> [0..1] 219

Period <Prd> [0..1] 219

TaxAmount <TaxAmt> [0..1] 220


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



Page





Method <Mtd> [0..1] 213



Date <Dt> [0..1] 214



Used in element(s)

"Tax" on page 92



Message Components

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 215 for details)



Page





Presence: [0..1]

Definition: 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 216 for details)



Page





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



31 May 2020 213

Usage Guideline

Presence: [0..1]

Definition: Method used to indicate the underlying business or how the tax is paid.


5.93.6 TotalTaxableBaseAmountXML Tag: TtlTaxblBaseAmt

Presence: [0..1]

Definition: Total amount of money on which the tax is based.


5.93.7 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.93.9 SequenceNumberXML Tag: SeqNb

Presence: [0..1]

Definition: Sequential number of the tax report.

Datatype: "Number" on page 261

5.93.10 RecordXML Tag: Rcrd

Presence: [0..*]

Definition: Record of tax details.


Message Components

The Rcrd block contains the following elements (see datatype "TaxRecord2" on page 218 for details)



Page

Type <Tp> [0..1] 218






Period <Prd> [0..1] 219



5.94 TaxParty1Definition: Details about the entity involved in the tax paid or to be paid.



Page




Used in element(s)

"Creditor" on page 209, "Creditor" on page 212

5.94.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the creditor.


5.94.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.

31 May 2020 215

Usage Guideline


5.94.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.


5.95 TaxParty2Definition: Details about the entity involved in the tax paid or to be paid.



Page





Used in element(s)

"Debtor" on page 209, "Debtor" on page 213, "UltimateDebtor" on page 210

5.95.1 TaxIdentificationXML Tag: TaxId

Presence: [0..1]

Definition: Tax identification number of the debtor.


5.95.2 RegistrationIdentificationXML Tag: RegnId

Presence: [0..1]

Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.


5.95.3 TaxTypeXML Tag: TaxTp

Presence: [0..1]

Definition: Type of tax payer.



Message Components

5.95.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 207for details)



Page

Title <Titl> [0..1] 208

Name <Nm> [0..1] 208

5.96 TaxPeriod2Definition: Period of time details related to the tax payment.



Page

Year <Yr> [0..1] 217

Type <Tp> [0..1] 217

FromToDate <FrToDt> [0..1] 217

Used in element(s)

"Period" on page 219, "Period" on page 221

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

5.96.3 FromToDate

31 May 2020 217

Usage Guideline

XML Tag: FrToDt

Presence: [0..1]

Definition: Range of time between a start date and an end date for which the tax report is provided.

The FrToDt block contains the following elements (see datatype "DatePeriod2" on page 97 for de-tails)



Page

FromDate <FrDt> [1..1] 98

ToDate <ToDt> [1..1] 98

5.97 TaxRecord2Definition: Set of elements used to define the tax record.



Page

Type <Tp> [0..1] 218






Period <Prd> [0..1] 219



Used in element(s)

"Record" on page 211, "Record" on page 214


Presence: [0..1]

Definition: High level code to identify the type of tax details.


5.97.2 CategoryXML Tag: Ctgy


Message Components

Presence: [0..1]

Definition: Specifies the tax code as published by the tax authority.


5.97.3 CategoryDetailsXML Tag: CtgyDtls

Presence: [0..1]

Definition: Provides further details of the category tax code.


5.97.4 DebtorStatusXML Tag: DbtrSts

Presence: [0..1]

Definition: Code provided by local authority to identify the status of the party that has drawn up the set-tlement document.


5.97.5 CertificateIdentificationXML Tag: CertId

Presence: [0..1]

Definition: Identification number of the tax report as assigned by the taxing authority.


5.97.6 FormsCodeXML Tag: FrmsCd

Presence: [0..1]

Definition: Identifies, in a coded form, on which template the tax report is to be provided.


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

31 May 2020 219

Usage Guideline

The Prd block contains the following elements (see datatype "TaxPeriod2" on page 217 for details)



Page

Year <Yr> [0..1] 217

Type <Tp> [0..1] 217



Presence: [0..1]

Definition: Set of elements used to provide information on the amount of the tax record.

The TaxAmt block contains the following elements (see datatype "TaxAmount2" on page 205 for de-tails)



Page

Rate <Rate> [0..1] 205

TaxableBaseAmount <TaxblBaseAmt> [0..1] 205

TotalAmount <TtlAmt> [0..1] 206


5.97.9 AdditionalInformationXML Tag: AddtlInf

Presence: [0..1]

Definition: Further details of the tax record.


5.98 TaxRecordDetails2Definition: Provides information on the individual tax amount(s) per period of the tax record.



Page

Period <Prd> [0..1] 221

Amount <Amt> [1..1] 221


Message Components

Used in element(s)

"Details" on page 206

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

The Prd block contains the following elements (see datatype "TaxPeriod2" on page 217 for details)



Page

Year <Yr> [0..1] 217

Type <Tp> [0..1] 217



Presence: [1..1]

Definition: Underlying tax amount related to the specified period.


31 May 2020 221

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 222

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R32 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 130

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

R33 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 222

Restricts

"ParentCurrencyCode" on page 261

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 224

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Rules

R18 CurrencyAmount ✓


Note: The decimal separator is a dot.

Error handling:



– Error Text: Invalid currency code or too many decimal digits.

31 May 2020 223

Usage Guideline

Used in element(s)

"Amount" on page 100, "Amount" on page 99, "Amount" on page 207, "Amount" on page 200,"Amount" on page 221, "CreditNoteAmount" on page 182, "CreditNoteAmount" on page 184, "Due-PayableAmount" on page 181, "DuePayableAmount" on page 183, "RemittedAmount" on page 183,"RemittedAmount" on page 185, "RemittedAmount" on page 121, "TaxableBaseAmount" on page 205,"TotalAmount" on page 206, "TotalTaxAmount" on page 211, "TotalTaxAmount" on page 214, "Total-TaxableBaseAmount" on page 211, "TotalTaxableBaseAmount" on page 214

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

R19 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 42, "Currency" on page 44


"ActiveOrHistoricCurrencyAndAmount" on page 223

Restricts

"ParentCurrencyCode" on page 261

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 26

Restricts

"AddressTypeCode" on page 225

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 224

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 225

Usage Guideline


RVDB ReversalDebit Credit entry used to reverse a previouslybooked debit entry.

Is restricted by

"CreditDebitCode" on page 236

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

R22 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 137

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

R21 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 105, "BICFI" on page 108, "BICFI" on page 116

6.10 BaseOneRateDefinition: Rate expressed as a decimal, for example, 0.7 is 7/10 and 70%.

Type: Rate

Format

totalDigits 11

fractionDigits 10

Used in element(s)

"ExchangeRate" on page 71

6.11 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 129

6.12 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

31 May 2020 227

Usage Guideline

Rules

R5 ValidationByTable


Used in element(s)

"Priority" on page 40

6.13 CBPR_AmountDefinition:

This datatype has been created by the Publisher of this Usage Guideline.

Type: Amount



Ccy Ccy "CurrencyCode" on page 236

Format

minInclusive 0

totalDigits 14

fractionDigits 5

Rules

R1 CurrencyAmount


Note: The decimal separator is a dot

Error handling:



– Error Text: Invalid currency code or too many decimal digits

Used in element(s)

"Amount" on page 46, "InstructedAmount" on page 71

6.14 CBPR_Amount_2decimalsDefinition:

Type: Amount



Message Datatypes


Ccy Ccy "CurrencyCode" on page 236

Usage Guideline restrictions for this at-tribute

• on pacs.008.001.08/CreditTransfer-TransactionInformation/InterbankSet-tlementAmount/Ccy

Single value: CAD

Format

minInclusive 0

totalDigits 14

fractionDigits 2

Rules

R50 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.15 CBPR_DateTimeDefinition:


Type: DateTime

Format

pattern .*(\+|-)((0[0-9])|(1[0-3])):[0-5][0-9]

Used in element(s)

"CreationDate" on page 40, "CreationDateTime" on page 129

31 May 2020 229

Usage Guideline

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 197, "FromTime" on page 198, "RejectTime" on page 198, "TillTime" on page 198

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

Format

minLength 1

maxLength 28

pattern [0-9a-zA-Z/\-\?:\.,'\+ ]{1,28}

Used in element(s)

"MemberIdentification" on page 55, "MemberIdentification" on page 58


Message Datatypes

6.19 ChargeBearerType1CodeDefinition: Specifies which party(ies) will pay charges due for processing of the instruction.

Type: Code


CRED BorneByCreditor All transaction charges are to be borneby the creditor.

Usage Guideline restrictions for thiscode

• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/ChargeBearer/BorneBy-Creditor

Synonym (MT 103 - field 71A - codeBEN): Details of Charges

DEBT BorneByDebtor All transaction charges are to be borneby the debtor.


• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/ChargeBearer/BorneBy-Debtor

Synonym (MT 103 - field 71A - codeOUR): Details of Charges

SHAR Shared In a credit transfer context, means thattransaction charges on the sender sideare to be borne by the debtor, transac-tion charges on the receiver side are tobe borne by the creditor. In a direct debitcontext, means that transaction chargeson the sender side are to be borne bythe creditor, transaction charges on thereceiver side are to be borne by thedebtor.


• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/ChargeBearer/Shared

– Lynx_SHARRule:

If deduct taken then charge information is mandatory.

31 May 2020 231

Usage Guideline

Code Name Definition It is optional for initiator (not taking deduct).This rule is inherited verba-tim from CBPR+.

• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/ChargeBearer/Shared

Synonym (MT 103 - field 71A - codeSHA): Details of Charges

SLEV FollowingServiceLevel Charges are to be applied following therules agreed in the service level and/orscheme.


• This code(pacs.008.001.08/Cred-itTransferTransactionInforma-tion/ChargeBearer/FollowingSer-viceLevel) is removed.

• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/ChargeBearer/Follow-ingServiceLevel

Unknown type of restriction [prac-tice:InternalCommentRestriction]:

Used in element(s)

"ChargeBearer" on page 71

Restricts

"ChargeBearerTypeCode" on page 232

6.20 ChargeBearerTypeCodeDefinition: Specifies which party(ies) will pay charges due for processing of the instruction.

Type: Code


CRED BorneByCreditor All transaction charges are to be borneby the creditor.

DEBT BorneByDebtor All transaction charges are to be borneby the debtor.

SHAR Shared In a credit transfer context, means thattransaction charges on the sender sideare to be borne by the debtor, transac-tion charges on the receiver side are to


Message Datatypes


be borne by the creditor. In a direct debitcontext, means that transaction chargeson the sender side are to be borne bythe creditor, transaction charges on thereceiver side are to be borne by thedebtor.

SLEV FollowingServiceLevel Charges are to be applied following therules agreed in the service level and/orscheme.

Is restricted by

"ChargeBearerType1Code" on page 231

6.21 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 155, "ClearingChannel" on page 157

Restricts

"ClearingChannelCode" on page 233

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

31 May 2020 233

Usage Guideline


RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net settle-ment system.

Is restricted by

"ClearingChannel2Code" on page 233

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


• on pacs.008.001.08/.head-er/CopyDuplicate/CopyDupli-cate


• on pacs.008.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.008.001.08/.head-er/CopyDuplicate/Copy


• on pacs.008.001.08/.header/Re-lated/CopyDuplicate/Copy


Message Datatypes



DUPL Duplicate Message is for information/confirmationpurposes. It is a duplicate of a messagepreviously sent.

Used in element(s)

"CopyDuplicate" on page 40

Restricts

"CopyDuplicateCode" on page 235

6.24 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 234

6.25 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

R20 Country ✓

31 May 2020 235

Usage Guideline

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.

Used in element(s)

"Country" on page 179, "Country" on page 199, "Country" on page 166, "Country" on page 172, "Coun-tryOfBirth" on page 97, "CountryOfResidence" on page 146, "CountryOfResidence" on page 150

6.26 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 100

Restricts

"AmountDirectionCode" on page 225

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



Message Datatypes


"CBPR_Amount" on page 228, "CBPR_Amount_2decimals" on page 228

6.28 DecimalNumberDefinition: Number of objects represented as a decimal number, for example 0.75 or 45.6.

Type: Quantity

Format

totalDigits 18

fractionDigits 17

Used in element(s)

"ControlSum" on page 130

6.29 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 95

Restricts

"DocumentTypeCode" on page 238

6.30 DocumentType6CodeDefinition: Specifies a type of financial or commercial document.

Type: Code

31 May 2020 237

Usage Guideline


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.

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 178

Restricts

"DocumentTypeCode" on page 238

6.31 DocumentTypeCodeDefinition: Specifies a type of financial or commercial document.

Type: Code


Message Datatypes


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.

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.

31 May 2020 239

Usage Guideline


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.

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 237, "DocumentType6Code" on page 237

6.32 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.33 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 26

Restricts

"ExternalAccountIdentificationCode" on page 241


Message Datatypes

6.34 ExternalAccountIdentificationCodeDefinition: Specifies the external account 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

"ExternalAccountIdentification1Code" on page 240

6.35 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 45

Restricts

"ExternalCashAccountTypeCode" on page 241

6.36 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

31 May 2020 241

Usage Guideline

Format

minLength 1

maxLength 4

Is restricted by

"ExternalCashAccountType1Code" on page 241

6.37 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 52

Restricts

"ExternalCashClearingSystemCode" on page 242

6.38 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 242

6.39 ExternalCategoryPurpose1CodeDefinition: Specifies the category purpose, as published in an external category purpose code list.



Message Datatypes

Type: Code

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 46

Restricts

"ExternalCategoryPurposeCode" on page 243

6.40 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 242

6.41 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 48, "Code" on page 51

Restricts

"ExternalClearingSystemIdentificationCode" on page 244

31 May 2020 243

Usage Guideline

6.42 ExternalClearingSystemIdentificationCodeDefinition: Specifies the clearing system identification code, as published in an external clearing systemidentification code list.


Type: Code

Format

minLength 1

maxLength 5

Is restricted by

"ExternalClearingSystemIdentification1Code" on page 243

6.43 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 99

Restricts

"ExternalDiscountAmountTypeCode" on page 244

6.44 ExternalDiscountAmountTypeCodeDefinition: Specifies the nature, or use, of the amount in the format of character string with a maximumlength of 4 characters.



Type: Code


Message Datatypes

Format

minLength 1

maxLength 4

Is restricted by

"ExternalDiscountAmountType1Code" on page 244

6.45 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 104

Restricts

"ExternalDocumentLineTypeCode" on page 245

6.46 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 245

6.47 ExternalFinancialInstitutionIdentification1CodeDefinition: Specifies the external financial institution identification scheme name code in the format ofcharacter string with a maximum length of 4 characters.



Type: Code

31 May 2020 245

Usage Guideline

Format

minLength 1

maxLength 4

Used in element(s)

"Code" on page 105

Restricts

"ExternalFinancialInstitutionIdentificationCode" on page 246

6.48 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 245

6.49 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 122

Restricts

"ExternalGarnishmentTypeCode" on page 246

6.50 ExternalGarnishmentTypeCode


Message Datatypes

Definition: Specifies the garnishment type as published in an external document type code list.

Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalGarnishmentType1Code" on page 246

6.51 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 135, "Code" on page 135

Restricts

"ExternalLocalInstrumentCode" on page 247

6.52 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

31 May 2020 247

Usage Guideline

Is restricted by

"ExternalLocalInstrument1Code" on page 247

6.53 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 139

Restricts

"ExternalOrganisationIdentificationCode" on page 248

6.54 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 248

6.55 ExternalPersonIdentification1CodeDefinition: Specifies the external person 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

Used in element(s)

"Code" on page 161

Restricts

"ExternalPersonIdentificationCode" on page 249

6.56 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 248

6.57 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 175

31 May 2020 249

Usage Guideline

Restricts

"ExternalProxyAccountTypeCode" on page 250

6.58 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 249

6.59 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 176

Restricts

"ExternalPurposeCode" on page 250

6.60 ExternalPurposeCodeDefinition: Specifies the external purpose code in the format of character string with a maximum lengthof 4 characters.




Message Datatypes

Type: Code

Format

minLength 1

maxLength 4

Is restricted by

"ExternalPurpose1Code" on page 250

6.61 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 189

Restricts

"ExternalServiceLevelCode" on page 251

6.62 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 251

31 May 2020 251

Usage Guideline

6.63 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 207

Restricts

"ExternalTaxAmountTypeCode" on page 252

6.64 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 252

6.65 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

R16 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 25

6.66 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 97, "Date" on page 199, "Date" on page 211, "Date" on page 120, "Date" onpage 214, "FromDate" on page 98, "InterbankSettlementDate" on page 130, "InterbankSettlement-Date" on page 68, "PoolingAdjustmentDate" on page 70, "RelatedDate" on page 101, "RelatedDate" onpage 177, "ToDate" on page 98, "Year" on page 217

6.67 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 253

Usage Guideline

Used in element(s)

"AcceptanceDateTime" on page 70, "CreditDateTime" on page 189, "DebitDateTime" on page 189

6.68 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.008.001.08/Credit-TransferTransactionInforma-tion/InstructionForCreditor-Agent/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.008.001.08/Credit-TransferTransactionInforma-tion/InstructionForCreditorA-gent/Code/HoldCashForCredi-tor

Synonym (MT 103 - field 23E - codeHOLD): Instruction Code

PHOB PhoneBeneficiary Please advise/contact (ultimate) credi-tor/claimant by phone.


• on pacs.008.001.08/Credit-TransferTransactionInforma-tion/InstructionForCreditorA-gent/Code/PhoneBeneficiary


Message Datatypes


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.008.001.08/Credit-TransferTransactionInforma-tion/InstructionForCreditorA-gent/Code/Telecom

Synonym (MT 103 - field 23E - codeTELB): Instruction Code

Used in element(s)

"Code" on page 133

Restricts

"InstructionCode" on page 255

6.69 Instruction4CodeDefinition: Specifies further instructions concerning the processing of a payment instruction, provided bythe sending clearing agent to the next agent(s).

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 134

Restricts

"InstructionCode" on page 255

6.70 InstructionCodeDefinition: Specifies further instructions concerning the processing of a payment instruction.

31 May 2020 255

Usage Guideline

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.

PHOB PhoneBeneficiary Please advise/contact (ultimate) credi-tor/claimant by phone.

TELA TelecomNextAgent Please advise/contact next agent by themost efficient means of telecommunica-tion.

TELB Telecom Please advise/contact (ultimate) credi-tor/claimant by the most efficient meansof telecommunication.

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.

Is restricted by

"Instruction3Code" on page 254, "Instruction4Code" on page 255

6.71 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 106, "LEI" on page 35, "LEI" on page 138, "LEI" on page 109, "LEI" on page 116

6.72 Max10TextDefinition: Specifies a character string with a maximum length of 10 characters.

Type: Text


Message Datatypes

Format

minLength 1

maxLength 10

Used in element(s)

"Code" on page 199


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 100, "AdditionalInformation" on page 220, "AdditionalRemittanceIn-formation" on page 204, "InstructionInformation" on page 134, "InstructionInformation" on page 134,"Name" on page 208, "Name" on page 179, "Name" on page 106, "Name" on page 35, "Name" onpage 144, "Name" on page 59, "Name" on page 109, "Name" on page 117, "Name" on page 148,"Name" on page 136, "ReferenceNumber" on page 210, "ReferenceNumber" on page 120, "Referen-ceNumber" on page 213, "Unstructured" on page 185

6.75 Max15NumericTextDefinition: Specifies a numeric string with a maximum length of 15 digits.

Type: Text

Format

pattern [0-9]{1,15}

31 May 2020 257

Usage Guideline

Used in element(s)

"NumberOfTransactions" on page 129


Type: Text

Format

minLength 1

maxLength 16

Used in element(s)

"BuildingNumber" on page 164, "BuildingNumber" on page 170, "InstructionIdentification" on page 152,"PostBox" on page 164, "PostBox" on page 170, "PostCode" on page 164, "PostCode" on page 171


Type: Text

Format

minLength 1

maxLength 2048

Used in element(s)

"Description" on page 102, "ElectronicAddress" on page 188, "EmailAddress" on page 60, "Identifica-tion" on page 174, "Identification" on page 133


Type: Text

Format

minLength 1

maxLength 34

Used in element(s)




Message Datatypes

Type: Text

Format

minLength 1

maxLength 350

Used in element(s)

"PlaceAndName" on page 205, "Registry" on page 133


Type: Text

Format

minLength 1

maxLength 35

Used in element(s)

"AddressLine" on page 172, "AdministrationZone" on page 210, "AdministrationZone" on page 213,"BuildingName" on page 164, "BuildingName" on page 170, "BusinessMessageIdentifier" on page 38,"BusinessService" on page 39, "Category" on page 218, "CategoryDetails" on page 219, "CertificateI-dentification" on page 219, "CityOfBirth" on page 97, "ClearingSystemReference" on page 154, "Coun-trySubDivision" on page 166, "CountrySubDivision" on page 171, "DebtorStatus" on page 219, "Dis-trictName" on page 166, "DistrictName" on page 171, "EmailPurpose" on page 60, "EndToEndIden-tification" on page 153, "FormsCode" on page 219, "Identification" on page 124, "Identification" onpage 126, "Identification" on page 127, "Identification" on page 35, "Information" on page 200, "Is-suer" on page 124, "Issuer" on page 123, "Issuer" on page 126, "Issuer" on page 128, "Issuer" onpage 96, "Issuer" on page 125, "Issuer" on page 103, "Issuer" on page 122, "Issuer" on page 179,"JobTitle" on page 60, "MemberIdentification" on page 53, "MessageDefinitionIdentifier" on page 39,"MessageIdentification" on page 129, "Method" on page 210, "Method" on page 213, "Number" onpage 101, "Number" on page 177, "Proprietary" on page 52, "Proprietary" on page 49, "Proprietary"on page 105, "Proprietary" on page 26, "Proprietary" on page 45, "Proprietary" on page 139, "Propri-etary" on page 161, "Proprietary" on page 176, "Proprietary" on page 95, "Proprietary" on page 99,"Proprietary" on page 207, "Proprietary" on page 189, "Proprietary" on page 135, "Proprietary" onpage 46, "Proprietary" on page 104, "Proprietary" on page 122, "Proprietary" on page 178, "Proprietary"on page 175, "ProvinceOfBirth" on page 97, "Reference" on page 95, "RegistrationIdentification" onpage 215, "RegistrationIdentification" on page 216, "RemittanceIdentification" on page 187, "Respon-sibility" on page 61, "SchemeName" on page 125, "TaxIdentification" on page 215, "TaxIdentification"on page 216, "TaxType" on page 216, "TaxType" on page 216, "Title" on page 208, "TownLocation-Name" on page 165, "TownLocationName" on page 171, "TownName" on page 165, "TownName" onpage 171, "TransactionIdentification" on page 153, "Type" on page 199, "Type" on page 218


Type: Text

31 May 2020 259

Usage Guideline

Format

minLength 1

maxLength 3

Used in element(s)



Type: Text

Format

minLength 1

maxLength 4

Used in element(s)

"ChannelType" on page 140, "Reason" on page 100

6.83 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 167, "Department" on page 163, "Department" on page 61, "Department" onpage 169, "Floor" on page 164, "Floor" on page 170, "Name" on page 42, "Name" on page 44, "Room"on page 164, "Room" on page 171, "StreetName" on page 163, "StreetName" on page 170, "SubDe-partment" on page 163, "SubDepartment" on page 170

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


Message Datatypes


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 59

Restricts

"NamePrefixCode" on page 261

6.85 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 260

6.86 NumberDefinition: Number of objects represented as an integer.

Type: Quantity

Format

totalDigits 18

fractionDigits 0

Used in element(s)

"SequenceNumber" on page 211, "SequenceNumber" on page 214

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

31 May 2020 261

Usage Guideline

Type: Code

Format

pattern [A-Z]{3,3}

Is restricted by

"ActiveCurrencyCode" on page 222, "ActiveOrHistoricCurrencyCode" on page 224

6.88 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 205

6.89 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 60, "MobileNumber" on page 60, "PhoneNumber" on page 60

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


Message Datatypes


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 61

Restricts

"PreferredContactMethodCode" on page 263

6.91 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 262

6.92 Priority2CodeDefinition: Specifies the priority level of an event.

Type: Code


HIGH High Priority level is high.

NORM Normal Priority level is normal.

31 May 2020 263

Usage Guideline

Used in element(s)

"InstructionPriority" on page 155, "InstructionPriority" on page 157

Restricts

"PriorityCode" on page 264

6.93 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 69

Restricts

"PriorityCode" on page 264

6.94 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 263, "Priority3Code" on page 264

6.95 RegulatoryReportingType1CodeDefinition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Type: Code


Message Datatypes


BOTH Both Regulatory information applies to bothcredit and debit sides.

CRED Credit Regulatory information applies to thecredit side.

DEBT Debit Regulatory information applies to thedebit side.

Used in element(s)

"DebitCreditReportingIndicator" on page 180

Restricts

"RegulatoryReportingTypeCode" on page 265

6.96 RegulatoryReportingTypeCodeDefinition: Identifies whether the regulatory reporting information applies to the debit side, to the creditside or to both debit and credit sides of the transaction.

Type: Code


BOTH Both Regulatory information applies to bothcredit and debit sides.

CRED Credit Regulatory information applies to thecredit side.

DEBT Debit Regulatory information applies to thedebit side.

Is restricted by

"RegulatoryReportingType1Code" on page 264

6.97 RemittanceLocationMethod2CodeDefinition: Specifies the method used to deliver the remittance advice information.

Type: Code


EDIC ElectronicDataInterchange Remittance advice information must besent through Electronic Data Interchange(EDI).

EMAL EMail Remittance advice information must besent through e-mail.

FAXI Fax Remittance advice information must befaxed.

POST Post Remittance advice information must besent through postal services.

31 May 2020 265

Usage Guideline


SMSM SMS Remittance advice information must besent through by phone as a short mes-sage service (SMS).

URID UniformResourceIdentifier Remittance advice information needsto be sent to a Uniform Resource Iden-tifier (URI). URI is a compact string ofcharacters that uniquely identify an ab-stract or physical resource. URI's are thesuper-set of identifiers, such as URLs,email addresses, ftp sites, etc, and assuch, provide the syntax for all of theidentification schemes.

Used in element(s)

"Method" on page 188

Restricts

"RemittanceLocationMethodCode" on page 266

6.98 RemittanceLocationMethodCodeDefinition: Specifies the method used to deliver the remittance advice information.

Type: Code


EDIC ElectronicDataInterchange Remittance advice information must besent through Electronic Data Interchange(EDI).

EMAL EMail Remittance advice information must besent through e-mail.

FAXI Fax Remittance advice information must befaxed.

POST Post Remittance advice information must besent through postal services.

SMSM SMS Remittance advice information must besent through by phone as a short mes-sage service (SMS).

URID UniformResourceIdentifier Remittance advice information needsto be sent to a Uniform Resource Iden-tifier (URI). URI is a compact string ofcharacters that uniquely identify an ab-stract or physical resource. URI's are thesuper-set of identifiers, such as URLs,email addresses, ftp sites, etc, and assuch, provide the syntax for all of theidentification schemes.

Is restricted by

"RemittanceLocationMethod2Code" on page 265


Message Datatypes

6.99 RestrictedFINXMax35TextDefinition: Specifies a character string with a maximum length of 35 characters limited to character setX, that is, a-z A-Z / - ? : ( ) . , ' + .

Type: Text

Format

minLength 1

maxLength 35

pattern [0-9a-zA-Z/\-\?:\.,'\+ ]{1,35}

Used in element(s)


6.100 SettlementMethod1CodeDefinition: 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.008.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.008.001.08/Group-Header/SettlementInformation/Set-tlementMethod/InstructedAgent) isremoved.

31 May 2020 267

Usage Guideline


INGA InstructingAgent Settlement is done by the agent instruct-ing and forwarding the payment to thenext party in the payment chain.


• This code(pacs.008.001.08/Group-Header/SettlementInformation/Set-tlementMethod/InstructingAgent) isremoved.

Used in element(s)

"SettlementMethod" on page 192

Restricts

"SettlementMethodCode" on page 268

6.101 SettlementMethodCodeDefinition: Specifies the method used to settle the payment instruction.

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 267

6.102 TaxRecordPeriod1CodeDefinition: Specifies the period related to the tax payment.

Type: Code


HLF1 FirstHalf Tax is related to the first half of the peri-od.


Message Datatypes


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.

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 217

Restricts

"TaxRecordPeriodCode" on page 269

6.103 TaxRecordPeriodCodeDefinition: Specifies the period related to the tax payment.

Type: Code

31 May 2020 269

Usage Guideline


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.

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 268

6.104 TrueFalseIndicatorDefinition: A flag indicating a True or False value.

Type: Indicator

Meaning When True: True


Message Datatypes

Meaning When False: False

Used in element(s)

"EmployeeTerminationIndicator" on page 121, "FamilyMedicalInsuranceIndicator" on page 121

6.105 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 154

6.106 UnicodeChartsCodeDefinition: codelist containing the names of the UNICODE code block name as specified on http://uni-code.org/Public/UNIDATA/Blocks.txt.

Type: Code

Rules



Used in element(s)

"CharacterSet" on page 37

6.107 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 40

31 May 2020 271

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.


ferv08 pacs.008.001 - payments canada€¦ · message functionality message functionality this...

Documents