Standards

Standards MX

Message Reference Guide

FIToFICustomerCreditTransferV10 (pacs.008.001.10)
This publication includes information exported from the MyStandards web platform.

For the official documentation of the messages included in this publication, see the relevant Standards MX Message
Reference Guides available on swift.com > Support > Documentation
Standards MX

Table of Contents

1 MX pacs.008.001.10 FIToFICustomerCreditTransferV10 ................................................................... 3

1.1 MessageDefinition Functionality ................................................................................................................. 3
1.2 Structure ......................................................................................................................................................... 4
1.3 Constraints ................................................................................................................................................... 13
1.4 Message Building Blocks .......................................................................................................................... 24

2 Message Items Types ................................................................................................................................... 142

2.1 MessageComponents ............................................................................................................................... 142
2.2 Message Datatypes .................................................................................................................................. 200
.Legal Notices ............................................................................................................................................................... 240

2 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1 MX pacs.008.001.10
FIToFICustomerCreditTransferV10

1.1 MessageDefinition Functionality

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

CreditTransferTransactionInformation 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 relationship in the currency
of the transfer, or do not wish to use their account relationship, 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
FinancialInstitutionCreditTransfer to a reimbursement agent. This payment method is called the Cover
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.

Outline
The FIToFICustomerCreditTransferV10 MessageDefinition is composed of 3 MessageBuildingBlocks:

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

3
Standards MX

1.2 Structure
Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page
No.

Message root <Document> <FIToFICstmrCdtTrf> [1..1] ✓C12,

✓C16,
✓C21,
C29,
✓C30,
C41,
C46,
✓C47,
✓C49

GroupHeader <GrpHdr> [1..1] ✓C45 24

MessageIdentification <MsgId> [1..1] Text 26

CreationDateTime <CreDtTm> [1..1] DateTime 27

BatchBooking <BtchBookg> [0..1] Indicator 27

NumberOfTransactions <NbOfTxs> [1..1] Text 27

ControlSum <CtrlSum> [0..1] Quantity 27

TotalInterbankSettlementAmount <TtlIntrBkSttlmAmt> [0..1] Amount ✓C1, 27

✓C10
InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 28

SettlementInformation <SttlmInf> [1..1] ✓C20, 28

✓C22,
✓C37,
✓C38,
✓C39,
✓C40,
✓C43,
✓C44
SettlementMethod <SttlmMtd> [1..1] CodeSet 31

SettlementAccount <SttlmAcct> [0..1] ✓C15, 32

C14

Identification <Id> [0..1] ± 32

Type <Tp> [0..1] ± 33

Currency <Ccy> [0..1] CodeSet ✓C2 33

Name <Nm> [0..1] Text 33

Proxy <Prxy> [0..1] ± 34

ClearingSystem <ClrSys> [0..1] 34

{Or Code <Cd> [1..1] CodeSet 34

Or} Proprietary <Prtry> [1..1] Text 34

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 35

4 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

InstructingReimbursementAgentAccount [0..1] ✓C15, 35

<InstgRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 36

Type <Tp> [0..1] ± 36

Currency <Ccy> [0..1] CodeSet ✓C2 36

Name <Nm> [0..1] Text 37

Proxy <Prxy> [0..1] ± 37

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 37

InstructedReimbursementAgentAccount [0..1] ✓C15, 37

<InstdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 38

Type <Tp> [0..1] ± 38

Currency <Ccy> [0..1] CodeSet ✓C2 39

Name <Nm> [0..1] Text 39

Proxy <Prxy> [0..1] ± 39

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 40

ThirdReimbursementAgentAccount [0..1] ✓C15, 40

<ThrdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 41

Type <Tp> [0..1] ± 41

Currency <Ccy> [0..1] CodeSet ✓C2 41

Name <Nm> [0..1] Text 42

Proxy <Prxy> [0..1] ± 42

PaymentTypeInformation <PmtTpInf> [0..1] ± 42

InstructingAgent <InstgAgt> [0..1] ± 43

InstructedAgent <InstdAgt> [0..1] ± 43

CreditTransferTransactionInformation <CdtTrfTxInf> [1..*] ✓C5, 44

✓C7,
✓C17,
✓C18,
✓C19,
✓C23,
✓C24,
✓C25,
✓C26,
✓C27,
✓C28,
✓C31,
✓C33,
✓C34,
✓C35,

5
Standards MX

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.
✓C36,
C6, C8,
C32,
C50,
C51

PaymentIdentification <PmtId> [1..1] ± ✓C48 55

PaymentTypeInformation <PmtTpInf> [0..1] ± 56

InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] Amount ✓C1, 57

✓C10
InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 57

SettlementPriority <SttlmPrty> [0..1] CodeSet 57

SettlementTimeIndication <SttlmTmIndctn> [0..1] 58

DebitDateTime <DbtDtTm> [0..1] DateTime 58

CreditDateTime <CdtDtTm> [0..1] DateTime 58

SettlementTimeRequest <SttlmTmReq> [0..1] ± 58

AcceptanceDateTime <AccptncDtTm> [0..1] DateTime 58

PoolingAdjustmentDate <PoolgAdjstmntDt> [0..1] Date 59

InstructedAmount <InstdAmt> [0..1] Amount ✓C2, 59

✓C11
ExchangeRate <XchgRate> [0..1] Rate 59

ChargeBearer <ChrgBr> [1..1] CodeSet 60

ChargesInformation <ChrgsInf> [0..*] ± 60

MandateRelatedInformation <MndtRltdInf> [0..1] ± 60

PreviousInstructingAgent1 <PrvsInstgAgt1> [0..1] ± 61

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> [0..1] ✓C15, 61

C14

Identification <Id> [0..1] ± 62

Type <Tp> [0..1] ± 62

Currency <Ccy> [0..1] CodeSet ✓C2 63

Name <Nm> [0..1] Text 63

Proxy <Prxy> [0..1] ± 63

PreviousInstructingAgent2 <PrvsInstgAgt2> [0..1] ± 64

PreviousInstructingAgent2Account <PrvsInstgAgt2Acct> [0..1] ✓C15, 64

C14

Identification <Id> [0..1] ± 65

Type <Tp> [0..1] ± 65

6 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

Currency <Ccy> [0..1] CodeSet ✓C2 65

Name <Nm> [0..1] Text 66

Proxy <Prxy> [0..1] ± 66

PreviousInstructingAgent3 <PrvsInstgAgt3> [0..1] ± 66

PreviousInstructingAgent3Account <PrvsInstgAgt3Acct> [0..1] ✓C15, 67

C14

Identification <Id> [0..1] ± 67

Type <Tp> [0..1] ± 68

Currency <Ccy> [0..1] CodeSet ✓C2 68

Name <Nm> [0..1] Text 68

Proxy <Prxy> [0..1] ± 69

InstructingAgent <InstgAgt> [0..1] ± 69

InstructedAgent <InstdAgt> [0..1] ± 69

IntermediaryAgent1 <IntrmyAgt1> [0..1] ± 70

IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] ✓C15, 70

C14

Identification <Id> [0..1] ± 71

Type <Tp> [0..1] ± 71

Currency <Ccy> [0..1] CodeSet ✓C2 71

Name <Nm> [0..1] Text 72

Proxy <Prxy> [0..1] ± 72

IntermediaryAgent2 <IntrmyAgt2> [0..1] ± 72

IntermediaryAgent2Account <IntrmyAgt2Acct> [0..1] ✓C15, 72

C14

Identification <Id> [0..1] ± 73

Type <Tp> [0..1] ± 73

Currency <Ccy> [0..1] CodeSet ✓C2 74

Name <Nm> [0..1] Text 74

Proxy <Prxy> [0..1] ± 74

IntermediaryAgent3 <IntrmyAgt3> [0..1] ± 75

IntermediaryAgent3Account <IntrmyAgt3Acct> [0..1] ✓C15, 75

C14

Identification <Id> [0..1] ± 76

Type <Tp> [0..1] ± 76

7
Standards MX

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

Currency <Ccy> [0..1] CodeSet ✓C2 76

Name <Nm> [0..1] Text 77

Proxy <Prxy> [0..1] ± 77

UltimateDebtor <UltmtDbtr> [0..1] ± 77

InitiatingParty <InitgPty> [0..1] ± 78

Debtor <Dbtr> [1..1] ± 78

DebtorAccount <DbtrAcct> [0..1] ✓C15, 79

C14

Identification <Id> [0..1] ± 79

Type <Tp> [0..1] ± 79

Currency <Ccy> [0..1] CodeSet ✓C2 80

Name <Nm> [0..1] Text 80

Proxy <Prxy> [0..1] ± 80

DebtorAgent <DbtrAgt> [1..1] ± 81

DebtorAgentAccount <DbtrAgtAcct> [0..1] ✓C15, 81

C14

Identification <Id> [0..1] ± 82

Type <Tp> [0..1] ± 82

Currency <Ccy> [0..1] CodeSet ✓C2 82

Name <Nm> [0..1] Text 83

Proxy <Prxy> [0..1] ± 83

CreditorAgent <CdtrAgt> [1..1] ± 83

CreditorAgentAccount <CdtrAgtAcct> [0..1] ✓C15, 84

C14

Identification <Id> [0..1] ± 84

Type <Tp> [0..1] ± 85

Currency <Ccy> [0..1] CodeSet ✓C2 85

Name <Nm> [0..1] Text 85

Proxy <Prxy> [0..1] ± 86

Creditor <Cdtr> [1..1] ± 86

CreditorAccount <CdtrAcct> [0..1] ✓C15, 86

C14

Identification <Id> [0..1] ± 87

Type <Tp> [0..1] ± 87

8 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

Currency <Ccy> [0..1] CodeSet ✓C2 88

Name <Nm> [0..1] Text 88

Proxy <Prxy> [0..1] ± 88

UltimateCreditor <UltmtCdtr> [0..1] ± 89

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] ± 89

InstructionForNextAgent <InstrForNxtAgt> [0..*] 89

Code <Cd> [0..1] CodeSet 90

InstructionInformation <InstrInf> [0..1] Text 90

Purpose <Purp> [0..1] ± 90

RegulatoryReporting <RgltryRptg> [0..10] ± 90

Tax <Tax> [0..1] 91

Creditor <Cdtr> [0..1] ± 93

Debtor <Dbtr> [0..1] ± 93

AdministrationZone <AdmstnZone> [0..1] Text 93

ReferenceNumber <RefNb> [0..1] Text 93

Method <Mtd> [0..1] Text 94

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 94

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 94
✓C11
Date <Dt> [0..1] Date 95

SequenceNumber <SeqNb> [0..1] Quantity 95

Record <Rcrd> [0..*] 95

Type <Tp> [0..1] Text 96

Category <Ctgy> [0..1] Text 96

CategoryDetails <CtgyDtls> [0..1] Text 97

DebtorStatus <DbtrSts> [0..1] Text 97

CertificateIdentification <CertId> [0..1] Text 97

FormsCode <FrmsCd> [0..1] Text 97

Period <Prd> [0..1] 97

Year <Yr> [0..1] Year 97

Type <Tp> [0..1] CodeSet 97

FromToDate <FrToDt> [0..1] ± 98

9
Standards MX

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

TaxAmount <TaxAmt> [0..1] 99

Rate <Rate> [0..1] Rate 99

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 99

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 100
✓C11
Details <Dtls> [0..*] 101

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 103

RelatedRemittanceInformation <RltdRmtInf> [0..10] ± 103

RemittanceInformation <RmtInf> [0..1] 103

Unstructured <Ustrd> [0..*] Text 107

Structured <Strd> [0..*] 107

ReferredDocumentInformation <RfrdDocInf> [0..*] 110

Type <Tp> [0..1] 112

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

Number <Nb> [0..1] Text 114

RelatedDate <RltdDt> [0..1] Date 114

LineDetails <LineDtls> [0..*] 114

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

10 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 122

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11
ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 125

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 125

Invoicer <Invcr> [0..1] ± 126

Invoicee <Invcee> [0..1] ± 126

TaxRemittance <TaxRmt> [0..1] 127

Creditor <Cdtr> [0..1] ± 129

Debtor <Dbtr> [0..1] ± 129

11
Standards MX

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

UltimateDebtor <UltmtDbtr> [0..1] ± 129

AdministrationZone <AdmstnZone> [0..1] Text 130

ReferenceNumber <RefNb> [0..1] Text 130

Method <Mtd> [0..1] Text 130

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 130

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 131
✓C11
Date <Dt> [0..1] Date 131

SequenceNumber <SeqNb> [0..1] Quantity 132

Record <Rcrd> [0..*] 132

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11

12 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement/BuildingBlock<XML Tag> Mult. Type Constr. Page

No.

AdditionalInformation <AddtlInf> [0..1] Text 139

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 139

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 140

SupplementaryData <SplmtryData> [0..*] ± C42 140

SupplementaryData <SplmtryData> [0..*] ± C42 141

1.3 Constraints
C1 ActiveCurrency ✓
(Rule)
The currency code must be a valid active currency code, not yet withdrawn on the day the
message containing the currency is exchanged. Valid active currency codes are registered
with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and are not yet
withdrawn on the day the message containing the Currency is exchanged. (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00005

– Error Text: Invalid currency code

C2 ActiveOrHistoricCurrency ✓
(Rule)
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the
Currency is exchanged. (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

C3 AnyBIC ✓
(Rule)
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 the ISO directory of BICs, and consists of eight (8) or eleven (11) contiguous
characters. (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00008

13
Standards MX

– Error Text: Invalid BIC.

C4 BICFI ✓
(Rule)
Valid BICs for financial institutions are registered and published by the ISO 9362 Registration
Authority in the ISO directory of BICs, and consist of eight (8) or eleven (11) contiguous
characters. (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00001

– Error Text: Invalid FI BIC.

C5 ChargeBearerAndChargesInformationRule ✓
(Rule)
If ChargeBearer contains DEBT, then ChargesInformation may be present to communicate
charges that have been added for (the) InstructedAgent(s).

If ChargeBearer contains CRED, then at least one occurrence of ChargesInformation must be

present to communicate charges that have been deducted from the InstructedAmount by (the)
InstructingAgent(s).

If ChargeBearer contains SHAR or SLEV, then ChargesInformation is

optional. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00046

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

C6 ChargesAmountGuideline
(Guideline)
If ChargesInformation is present, then the currency of ChargesInformation/ChargesAmount is
recommended to be the same as the currency of InterbankSettlementAmount.

C7 ChargesInformationAndInstructedAmountRule ✓
(Rule)
If ChargesInformation is present, then InstructedAmount must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00048

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

14 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

C8 ChargesInformationGuideline
(Guideline)
The repetitive ChargesInformation should contain all information on charges amount and which
party has taken the charges, separately for each agent along the payment chain.

C9 Country ✓
(Rule)
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code). (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00004

– Error Text: Invalid Country Code.

C10 CurrencyAmount ✓
(Rule)
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot. (Algorithm)

Error handling:

– Error severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

C11 CurrencyAmount ✓
(Rule)
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot. (Algorithm)

Error handling:

– Error severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

C12 GroupHeaderInterbankSettlementDateRule ✓
(Rule)
If GroupHeader/InterbankSettlementDate is present, then
CreditTransferTransactionInformation/InterbankSettlementDate is not
allowed. (CrossElementComplexRule)

15
Standards MX

Error handling:

– Error severity: Fatal

– Error Code: X00045

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

This constraint is defined at the MessageDefinition level.

C13 IBAN ✓
(Rule)
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN. (Algorithm)
Error handling:

– Error severity: Fatal

– Error Code: D00003

– Error Text: Invalid IBAN format or invalid check digits.

C14 IdentificationAndProxyGuideline
(Guideline)
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

C15 IdentificationOrProxyPresenceRule ✓
(Rule)
Identification must be present or Proxy must be present. Both may be
present. (CrossElementSimpleRule)
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

C16 InstructedAgentRule ✓
(Rule)
If GroupHeader/InstructedAgent is present, then CreditTransferTransactionInformation/
InstructedAgent is not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00008

– Error Text: Invalid message content for instructed agent.

This constraint is defined at the MessageDefinition level.

16 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

C17 InstructedAmountAndExchangeRate1Rule ✓
(Rule)
If InstructedAmount is present and the currency is different from the
currency in InterbankSettlementAmount, then ExchangeRate must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00049

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

C18 InstructedAmountAndExchangeRate2Rule ✓
(Rule)
If InstructedAmount is present and the currency is the same as the currency in
InterbankSettlementAmount, then ExchangeRate is not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00050

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

C19 InstructedAmountAndExchangeRate3Rule ✓
(Rule)
If InstructedAmount is not present, then ExchangeRate is not
allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00061

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

C20 InstructedReimbursementAgentAccountRule ✓
(Rule)
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00037

– Error Text: Invalid message content for instructed reimbursement agent account.

C21 InstructingAgentRule ✓
(Rule)

17
Standards MX

If GroupHeader/InstructingAgent is present, then CreditTransferTransactionInformation/

InstructingAgent is not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00007

– Error Text: Invalid message content for instructing agent.

This constraint is defined at the MessageDefinition level.

C22 InstructingReimbursementAgentAccountRule ✓
(Rule)
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00038

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

C23 InstructionForCreditorAgentRule ✓
(Rule)
If InstructionForCreditorAgent/Code contains CHQB (PayCreditorByCheque), then
CreditorAccount is not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00051

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

C24 IntermediaryAgent1AccountRule ✓
(Rule)
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00052

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

C25 IntermediaryAgent2AccountRule ✓
(Rule)
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be
present. (CrossElementComplexRule)

18 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Error handling:

– Error severity: Fatal

– Error Code: X00053

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

C26 IntermediaryAgent2Rule ✓
(Rule)
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00056

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

C27 IntermediaryAgent3AccountRule ✓
(Rule)
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00054

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

C28 IntermediaryAgent3Rule ✓
(Rule)
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00057

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

C29 NumberOfTransactionsAndCreditTransfersRule
(Rule)
GroupHeader/NumberOfTransactions must equal the number of occurrences of
CreditTransferTransactionInformation. (CrossElementSimpleRule)
Error handling:

– Error severity: Fatal

– Error Code: X00062

19
Standards MX

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

This constraint is defined at the MessageDefinition level.

C30 PaymentTypeInformationRule ✓
(Rule)
If GroupHeader/PaymentTypeInformation is present, then
CreditTransferTransactionInformation/PaymentTypeInformation is not
allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00009

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

This constraint is defined at the MessageDefinition level.

C31 PreviousInstructingAgent1AccountRule ✓
(Rule)
If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00411

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

C32 PreviousInstructingAgent1Guideline
(Guideline)
It is recommended that, when present, PreviousInstructingAgent1 is the closest to the
DebtorAgent in the payment chain.

C33 PreviousInstructingAgent2AccountRule ✓
(Rule)
If PreviousInstructingAgent2Account is present, then PreviousInstructingAgent2 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00412

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

C34 PreviousInstructingAgent2Rule ✓
(Rule)
If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be
present. (CrossElementComplexRule)

20 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Error handling:

– Error severity: Fatal

– Error Code: X00415

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

C35 PreviousInstructingAgent3AccountRule ✓
(Rule)
If PreviousInstructingAgent3Account is present, then PreviousInstructingAgent3 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00413

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

C36 PreviousInstructingAgent3Rule ✓
(Rule)
If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00416

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

C37 SettlementMethodAgentRule ✓
(Rule)
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and
ClearingSystem are not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00018

– Error Text: Invalid message content for settlement method INGA or INDA.

C38 SettlementMethodClearingRule ✓
(Rule)
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00019

21
Standards MX

– Error Text: Invalid message content for settlement method CLRG.

C39 SettlementMethodCoverAgentRule ✓
(Rule)
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00076

– Error Text: Invalid message content for cover settlement method and reimbursement agents.

C40 SettlementMethodCoverRule ✓
(Rule)
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00075

– Error Text: Invalid message content for cover settlement method with settlement account
and clearing system.

C41 SupplementaryDataRule
(Rule)
The SupplementaryData building block at message level must not be used to provide additional
information about a transaction. The SupplementaryData element at transaction level should be
used for that purpose.
This constraint is defined at the MessageDefinition level.

C42 SupplementaryDataRule
(Rule)
This component may not be used without the explicit approval of a SEG and submission to the
RA of ISO 20022 compliant structure(s) to be used in the Envelope element.

C43 ThirdReimbursementAgentAccountRule ✓
(Rule)
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00039

– Error Text: Invalid message content for third reimbursement agent account.

22 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

C44 ThirdReimbursementAgentRule ✓
(Rule)
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00040

– Error Text: Invalid message content for third reimbursement agent.

C45 TotalInterbankSettlementAmountAndDateRule ✓
(Rule)
If TotalInterbankSettlementAmount is present, then InterbankSettlementDate must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00044

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

C46 TotalInterbankSettlementAmountAndSumRule
(Rule)
If GroupHeader/TotalInterbankSettlementAmount is present, then it must
equal the sum of all occurrences of CreditTransferTransactionInformation/
InterbankSettlementAmount. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00043

– Error Text: Invalid message content for the total interbank settlement amount and sum of
individual interbank settlement amounts.
This constraint is defined at the MessageDefinition level.

C47 TotalInterbankSettlementAmountRule ✓
(Rule)
If GroupHeader/TotalInterbankSettlementAmount is present, then all occurrences
of CreditTransferTransactionInformation/InterbankSettlementAmount
must have the same currency as the currency of GroupHeader/
TotalInterbankSettlementAmount. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00042

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

23
Standards MX

This constraint is defined at the MessageDefinition level.

C48 TransactionIdentificationPresenceRule ✓
(Rule)
TransactionIdentification or UETR must be present. Both may be
present (CrossElementSimpleRule)
Error handling:

– Error severity: Fatal

– Error Code: X00420

– Error Text: No transaction identification is present

C49 TransactionInterbankSettlementDateRule ✓
(Rule)
If GroupHeader/InterbankSettlementDate is not present, then
CreditTransferTransactionInformation/InterbankSettlementDate must be
present. (CrossElementComplexRule)
Error handling:

– Error severity: Fatal

– Error Code: X00290

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

This constraint is defined at the MessageDefinition level.

C50 UltimateCreditorGuideline
(Guideline)
UltimateCreditor may only be present if different from Creditor.

C51 UltimateDebtorGuideline
(Guideline)
UltimateDebtor may only be present if different from Debtor.

1.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

1.4.1 GroupHeader <GrpHdr>

Presence: [1..1]
Definition: Set of characteristics shared by all individual transactions included in the message.
Impacted by: ✓C45 TotalInterbankSettlementAmountAndDateRule ✓

24 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

GroupHeader <GrpHdr> contains the following GroupHeader96 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

MessageIdentification <MsgId> [1..1] Text 26

CreationDateTime <CreDtTm> [1..1] DateTime 27

BatchBooking <BtchBookg> [0..1] Indicator 27

NumberOfTransactions <NbOfTxs> [1..1] Text 27

ControlSum <CtrlSum> [0..1] Quantity 27

TotalInterbankSettlementAmount <TtlIntrBkSttlmAmt> [0..1] Amount ✓C1, 27

✓C10
InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 28

SettlementInformation <SttlmInf> [1..1] ✓C20, 28

✓C22,
✓C37,
✓C38,
✓C39,
✓C40,
✓C43,
✓C44
SettlementMethod <SttlmMtd> [1..1] CodeSet 31

SettlementAccount <SttlmAcct> [0..1] ✓C15, 32

C14

Identification <Id> [0..1] ± 32

Type <Tp> [0..1] ± 33

Currency <Ccy> [0..1] CodeSet ✓C2 33

Name <Nm> [0..1] Text 33

Proxy <Prxy> [0..1] ± 34

ClearingSystem <ClrSys> [0..1] 34

{Or Code <Cd> [1..1] CodeSet 34

Or} Proprietary <Prtry> [1..1] Text 34

InstructingReimbursementAgent [0..1] ± 35
<InstgRmbrsmntAgt>

InstructingReimbursementAgentAccount [0..1] ✓C15, 35

<InstgRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 36

Type <Tp> [0..1] ± 36

Currency <Ccy> [0..1] CodeSet ✓C2 36

Name <Nm> [0..1] Text 37

Proxy <Prxy> [0..1] ± 37

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 37

25
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructedReimbursementAgentAccount [0..1] ✓C15, 37

<InstdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 38

Type <Tp> [0..1] ± 38

Currency <Ccy> [0..1] CodeSet ✓C2 39

Name <Nm> [0..1] Text 39

Proxy <Prxy> [0..1] ± 39

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 40

ThirdReimbursementAgentAccount [0..1] ✓C15, 40

<ThrdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 41

Type <Tp> [0..1] ± 41

Currency <Ccy> [0..1] CodeSet ✓C2 41

Name <Nm> [0..1] Text 42

Proxy <Prxy> [0..1] ± 42

PaymentTypeInformation <PmtTpInf> [0..1] ± 42

InstructingAgent <InstgAgt> [0..1] ± 43

InstructedAgent <InstdAgt> [0..1] ± 43

Constraints

• TotalInterbankSettlementAmountAndDateRule
If TotalInterbankSettlementAmount is present, then InterbankSettlementDate must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00044

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

1.4.1.1 MessageIdentification <MsgId>

Presence: [1..1]
Definition: Point to point reference, as assigned by the instructing party, and sent to the next party in the
chain to unambiguously identify the message.

Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party
for a pre-agreed period.
Datatype: Max35Text on page 238

26 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.1.2 CreationDateTime <CreDtTm>

Presence: [1..1]
Definition: Date and time at which the message was created.
Datatype: ISODateTime on page 232

1.4.1.3 BatchBooking <BtchBookg>

Presence: [0..1]
Definition: Identifies whether a single entry per individual transaction or a batch entry for the sum of the
amounts of all transactions within the group of a message is requested.

Usage: Batch booking is used to request and not order a possible batch booking.
Datatype: One of the following values must be used (see BatchBookingIndicator on page 235):

• Meaning When True: Identifies that a batch entry for the sum of the amounts of all transactions in the
batch or message is requested.

• Meaning When False: Identifies that a single entry for each of the transactions in the batch or
message is requested.

1.4.1.4 NumberOfTransactions <NbOfTxs>

Presence: [1..1]
Definition: Number of individual transactions contained in the message.
Datatype: Max15NumericText on page 237

1.4.1.5 ControlSum <CtrlSum>

Presence: [0..1]
Definition: Total of all individual amounts included in the message, irrespective of currencies.
Datatype: DecimalNumber on page 235

1.4.1.6 TotalInterbankSettlementAmount <TtlIntrBkSttlmAmt>

Presence: [0..1]
Definition: Total amount of money moved between the instructing agent and the instructed agent.
Impacted by: ✓C1 ActiveCurrency ✓, ✓C10 CurrencyAmount ✓
Datatype: ActiveCurrencyAndAmount on page 200

Constraints

• ActiveCurrency
The currency code must be a valid active currency code, not yet withdrawn on the day the message
containing the currency is exchanged. Valid active currency codes are registered with the ISO 4217
Maintenance Agency, consist of three (3) contiguous letters, and are not yet withdrawn on the day
the message containing the Currency is exchanged.

27
Standards MX

Error handling:

– Error severity: Fatal

– Error Code: D00005

– Error Text: Invalid currency code

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.1.7 InterbankSettlementDate <IntrBkSttlmDt>

Presence: [0..1]
Definition: Date on which the amount of money ceases to be available to the agent that owes it and
when the amount of money becomes available to the agent to which it is due.
Datatype: ISODate on page 232

1.4.1.8 SettlementInformation <SttlmInf>

Presence: [1..1]
Definition: Specifies the details on how the settlement of the transaction(s) between the instructing
agent and the instructed agent is completed.
Impacted by: ✓C20 InstructedReimbursementAgentAccountRule ✓, ✓C22
InstructingReimbursementAgentAccountRule ✓, ✓C37 SettlementMethodAgentRule ✓, ✓C38
SettlementMethodClearingRule ✓, ✓C39 SettlementMethodCoverAgentRule ✓, ✓C40
SettlementMethodCoverRule ✓, ✓C43 ThirdReimbursementAgentAccountRule ✓, ✓C44
ThirdReimbursementAgentRule ✓

28 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 31

SettlementAccount <SttlmAcct> [0..1] ✓C15, 32

C14

Identification <Id> [0..1] ± 32

Type <Tp> [0..1] ± 33

Currency <Ccy> [0..1] CodeSet ✓C2 33

Name <Nm> [0..1] Text 33

Proxy <Prxy> [0..1] ± 34

ClearingSystem <ClrSys> [0..1] 34

{Or Code <Cd> [1..1] CodeSet 34

Or} Proprietary <Prtry> [1..1] Text 34

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 35

InstructingReimbursementAgentAccount [0..1] ✓C15, 35

<InstgRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 36

Type <Tp> [0..1] ± 36

Currency <Ccy> [0..1] CodeSet ✓C2 36

Name <Nm> [0..1] Text 37

Proxy <Prxy> [0..1] ± 37

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 37

InstructedReimbursementAgentAccount [0..1] ✓C15, 37

<InstdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 38

Type <Tp> [0..1] ± 38

Currency <Ccy> [0..1] CodeSet ✓C2 39

Name <Nm> [0..1] Text 39

Proxy <Prxy> [0..1] ± 39

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 40

ThirdReimbursementAgentAccount [0..1] ✓C15, 40

<ThrdRmbrsmntAgtAcct> C14

Identification <Id> [0..1] ± 41

Type <Tp> [0..1] ± 41

Currency <Ccy> [0..1] CodeSet ✓C2 41

29
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 42

Proxy <Prxy> [0..1] ± 42

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
Error handling:

– Error severity: Fatal

– Error Code: X00037

– Error Text: Invalid message content for instructed reimbursement agent account.

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
Error handling:

– Error severity: Fatal

– Error Code: X00038

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

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00018

– Error Text: Invalid message content for settlement method INGA or INDA.

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00019

– Error Text: Invalid message content for settlement method CLRG.

30 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00076

– Error Text: Invalid message content for cover settlement method and reimbursement agents.

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00075

– Error Text: Invalid message content for cover settlement method with settlement account and
clearing system.

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00039

– Error Text: Invalid message content for third reimbursement agent account.

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
Error handling:

– Error severity: Fatal

– Error Code: X00040

– Error Text: Invalid message content for third reimbursement agent.

1.4.1.8.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: SettlementMethod1Code on page 229

CodeName Name Definition

INDA InstructedAgent Settlement is done by the agent

instructed to execute a payment
instruction.

31
Standards MX

CodeName Name Definition

INGA InstructingAgent Settlement is done by the agent

instructing and forwarding the payment
to the next party in the payment chain.

COVE CoverMethod Settlement is done through a cover

payment.

CLRG ClearingSystem Settlement is done through a payment

clearing system.

1.4.1.8.2 SettlementAccount <SttlmAcct>

Presence: [0..1]
Definition: A specific purpose account used to post debit and credit entries as a result of the transaction.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
SettlementAccount <SttlmAcct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 32

Type <Tp> [0..1] ± 33

Currency <Ccy> [0..1] CodeSet ✓C2 33

Name <Nm> [0..1] Text 33

Proxy <Prxy> [0..1] ± 34

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.1.8.2.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.

32 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Identification <Id> contains one of the following elements (see AccountIdentification4Choice on

page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.1.8.2.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.1.8.2.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.1.8.2.4 Name <Nm>

Presence: [0..1]

33
Standards MX

Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.1.8.2.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.1.8.3 ClearingSystem <ClrSys>

Presence: [0..1]
Definition: Specification of a pre-agreed offering between clearing agents or the channel through which
the payment instruction is processed.
ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 34

Or} Proprietary <Prtry> [1..1] Text 34

1.4.1.8.3.1 Code <Cd>

Presence: [1..1]
Definition: Infrastructure through which the payment instruction is processed, as published in an
external clearing system identification code list.
Datatype: ExternalCashClearingSystem1Code on page 211

1.4.1.8.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: Max35Text on page 238

34 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.1.8.4 InstructingReimbursementAgent <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
InstructingReimbursementAgent must be used.
InstructingReimbursementAgent <InstgRmbrsmntAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.1.8.5 InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructing reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following
CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 36

Type <Tp> [0..1] ± 36

Currency <Ccy> [0..1] CodeSet ✓C2 36

Name <Nm> [0..1] Text 37

Proxy <Prxy> [0..1] ± 37

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

35
Standards MX

1.4.1.8.5.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.1.8.5.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.1.8.5.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

36 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

– Error Text: Invalid currency code.

1.4.1.8.5.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.1.8.5.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.1.8.6 InstructedReimbursementAgent <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

InstructedAgent will claim reimbursement from that branch/will be paid by that branch.

Usage: If InstructingAgent and InstructedAgent have the same reimbursement agent, then only
InstructingReimbursementAgent must be used.
InstructedReimbursementAgent <InstdRmbrsmntAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.1.8.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]

37
Standards MX

Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following
CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 38

Type <Tp> [0..1] ± 38

Currency <Ccy> [0..1] CodeSet ✓C2 39

Name <Nm> [0..1] Text 39

Proxy <Prxy> [0..1] ± 39

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.1.8.7.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.1.8.7.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.

38 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.1.8.7.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.1.8.7.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.1.8.7.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.

39
Standards MX

Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.1.8.8 ThirdReimbursementAgent <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

InstructedAgent will claim reimbursement from that branch/will be paid by that branch.
ThirdReimbursementAgent <ThrdRmbrsmntAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.1.8.9 ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the third reimbursement agent account at its
servicing agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following
CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 41

Type <Tp> [0..1] ± 41

Currency <Ccy> [0..1] CodeSet ✓C2 41

Name <Nm> [0..1] Text 42

Proxy <Prxy> [0..1] ± 42

40 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.1.8.9.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.1.8.9.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.1.8.9.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

41
Standards MX

Impacted by: ✓C2 ActiveOrHistoricCurrency ✓

Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.1.8.9.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.1.8.9.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.1.9 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

42 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

PaymentTypeInformation <PmtTpInf> contains the following elements (see

PaymentTypeInformation28 on page 178 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 178

ClearingChannel <ClrChanl> [0..1] CodeSet 178

ServiceLevel <SvcLvl> [0..*] 179

{Or Code <Cd> [1..1] CodeSet 179

Or} Proprietary <Prtry> [1..1] Text 179

LocalInstrument <LclInstrm> [0..1] 179

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

Or} Proprietary <Prtry> [1..1] Text 180

CategoryPurpose <CtgyPurp> [0..1] 180

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

Or} Proprietary <Prtry> [1..1] Text 180

1.4.1.10 InstructingAgent <InstgAgt>

Presence: [0..1]
Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).
InstructingAgent <InstgAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.1.11 InstructedAgent <InstdAgt>

Presence: [0..1]
Definition: Agent that is instructed by the previous party in the chain to carry out the (set of)
instruction(s).
InstructedAgent <InstdAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

43
Standards MX

1.4.2 CreditTransferTransactionInformation <CdtTrfTxInf>

Presence: [1..*]
Definition: Set of elements providing information specific to the individual credit transfer(s).
Impacted by: ✓C5 ChargeBearerAndChargesInformationRule ✓,
✓C7 ChargesInformationAndInstructedAmountRule ✓, ✓C17
InstructedAmountAndExchangeRate1Rule ✓, ✓C18 InstructedAmountAndExchangeRate2Rule ✓,
✓C19 InstructedAmountAndExchangeRate3Rule ✓, ✓C23 InstructionForCreditorAgentRule ✓,
✓C24 IntermediaryAgent1AccountRule ✓, ✓C25 IntermediaryAgent2AccountRule ✓,
✓C26 IntermediaryAgent2Rule ✓, ✓C27 IntermediaryAgent3AccountRule ✓, ✓C28
IntermediaryAgent3Rule ✓, ✓C31 PreviousInstructingAgent1AccountRule ✓, ✓C33
PreviousInstructingAgent2AccountRule ✓, ✓C34 PreviousInstructingAgent2Rule ✓, ✓C35
PreviousInstructingAgent3AccountRule ✓, ✓C36 PreviousInstructingAgent3Rule ✓, C6
ChargesAmountGuideline, C8 ChargesInformationGuideline, C32 PreviousInstructingAgent1Guideline,
C50 UltimateCreditorGuideline, C51 UltimateDebtorGuideline

44 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

CreditTransferTransactionInformation <CdtTrfTxInf> contains the following

CreditTransferTransaction50 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PaymentIdentification <PmtId> [1..1] ± ✓C48 55

PaymentTypeInformation <PmtTpInf> [0..1] ± 56

InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] Amount ✓C1, 57

✓C10
InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 57

SettlementPriority <SttlmPrty> [0..1] CodeSet 57

SettlementTimeIndication <SttlmTmIndctn> [0..1] 58

DebitDateTime <DbtDtTm> [0..1] DateTime 58

CreditDateTime <CdtDtTm> [0..1] DateTime 58

SettlementTimeRequest <SttlmTmReq> [0..1] ± 58

AcceptanceDateTime <AccptncDtTm> [0..1] DateTime 58

PoolingAdjustmentDate <PoolgAdjstmntDt> [0..1] Date 59

InstructedAmount <InstdAmt> [0..1] Amount ✓C2, 59

✓C11
ExchangeRate <XchgRate> [0..1] Rate 59

ChargeBearer <ChrgBr> [1..1] CodeSet 60

ChargesInformation <ChrgsInf> [0..*] ± 60

MandateRelatedInformation <MndtRltdInf> [0..1] ± 60

PreviousInstructingAgent1 <PrvsInstgAgt1> [0..1] ± 61

PreviousInstructingAgent1Account [0..1] ✓C15, 61

<PrvsInstgAgt1Acct> C14

Identification <Id> [0..1] ± 62

Type <Tp> [0..1] ± 62

Currency <Ccy> [0..1] CodeSet ✓C2 63

Name <Nm> [0..1] Text 63

Proxy <Prxy> [0..1] ± 63

PreviousInstructingAgent2 <PrvsInstgAgt2> [0..1] ± 64

PreviousInstructingAgent2Account [0..1] ✓C15, 64

<PrvsInstgAgt2Acct> C14

Identification <Id> [0..1] ± 65

Type <Tp> [0..1] ± 65

Currency <Ccy> [0..1] CodeSet ✓C2 65

45
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 66

Proxy <Prxy> [0..1] ± 66

PreviousInstructingAgent3 <PrvsInstgAgt3> [0..1] ± 66

PreviousInstructingAgent3Account [0..1] ✓C15, 67

<PrvsInstgAgt3Acct> C14

Identification <Id> [0..1] ± 67

Type <Tp> [0..1] ± 68

Currency <Ccy> [0..1] CodeSet ✓C2 68

Name <Nm> [0..1] Text 68

Proxy <Prxy> [0..1] ± 69

InstructingAgent <InstgAgt> [0..1] ± 69

InstructedAgent <InstdAgt> [0..1] ± 69

IntermediaryAgent1 <IntrmyAgt1> [0..1] ± 70

IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] ✓C15, 70

C14

Identification <Id> [0..1] ± 71

Type <Tp> [0..1] ± 71

Currency <Ccy> [0..1] CodeSet ✓C2 71

Name <Nm> [0..1] Text 72

Proxy <Prxy> [0..1] ± 72

IntermediaryAgent2 <IntrmyAgt2> [0..1] ± 72

IntermediaryAgent2Account <IntrmyAgt2Acct> [0..1] ✓C15, 72

C14

Identification <Id> [0..1] ± 73

Type <Tp> [0..1] ± 73

Currency <Ccy> [0..1] CodeSet ✓C2 74

Name <Nm> [0..1] Text 74

Proxy <Prxy> [0..1] ± 74

IntermediaryAgent3 <IntrmyAgt3> [0..1] ± 75

IntermediaryAgent3Account <IntrmyAgt3Acct> [0..1] ✓C15, 75

C14

Identification <Id> [0..1] ± 76

Type <Tp> [0..1] ± 76

Currency <Ccy> [0..1] CodeSet ✓C2 76

46 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 77

Proxy <Prxy> [0..1] ± 77

UltimateDebtor <UltmtDbtr> [0..1] ± 77

InitiatingParty <InitgPty> [0..1] ± 78

Debtor <Dbtr> [1..1] ± 78

DebtorAccount <DbtrAcct> [0..1] ✓C15, 79

C14

Identification <Id> [0..1] ± 79

Type <Tp> [0..1] ± 79

Currency <Ccy> [0..1] CodeSet ✓C2 80

Name <Nm> [0..1] Text 80

Proxy <Prxy> [0..1] ± 80

DebtorAgent <DbtrAgt> [1..1] ± 81

DebtorAgentAccount <DbtrAgtAcct> [0..1] ✓C15, 81

C14

Identification <Id> [0..1] ± 82

Type <Tp> [0..1] ± 82

Currency <Ccy> [0..1] CodeSet ✓C2 82

Name <Nm> [0..1] Text 83

Proxy <Prxy> [0..1] ± 83

CreditorAgent <CdtrAgt> [1..1] ± 83

CreditorAgentAccount <CdtrAgtAcct> [0..1] ✓C15, 84

C14

Identification <Id> [0..1] ± 84

Type <Tp> [0..1] ± 85

Currency <Ccy> [0..1] CodeSet ✓C2 85

Name <Nm> [0..1] Text 85

Proxy <Prxy> [0..1] ± 86

Creditor <Cdtr> [1..1] ± 86

CreditorAccount <CdtrAcct> [0..1] ✓C15, 86

C14

Identification <Id> [0..1] ± 87

Type <Tp> [0..1] ± 87

Currency <Ccy> [0..1] CodeSet ✓C2 88

47
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 88

Proxy <Prxy> [0..1] ± 88

UltimateCreditor <UltmtCdtr> [0..1] ± 89

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] ± 89

InstructionForNextAgent <InstrForNxtAgt> [0..*] 89

Code <Cd> [0..1] CodeSet 90

InstructionInformation <InstrInf> [0..1] Text 90

Purpose <Purp> [0..1] ± 90

RegulatoryReporting <RgltryRptg> [0..10] ± 90

Tax <Tax> [0..1] 91

Creditor <Cdtr> [0..1] ± 93

Debtor <Dbtr> [0..1] ± 93

AdministrationZone <AdmstnZone> [0..1] Text 93

ReferenceNumber <RefNb> [0..1] Text 93

Method <Mtd> [0..1] Text 94

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 94

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 94
✓C11
Date <Dt> [0..1] Date 95

SequenceNumber <SeqNb> [0..1] Quantity 95

Record <Rcrd> [0..*] 95

Type <Tp> [0..1] Text 96

Category <Ctgy> [0..1] Text 96

CategoryDetails <CtgyDtls> [0..1] Text 97

DebtorStatus <DbtrSts> [0..1] Text 97

CertificateIdentification <CertId> [0..1] Text 97

FormsCode <FrmsCd> [0..1] Text 97

Period <Prd> [0..1] 97

Year <Yr> [0..1] Year 97

Type <Tp> [0..1] CodeSet 97

FromToDate <FrToDt> [0..1] ± 98

TaxAmount <TaxAmt> [0..1] 99

48 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Rate <Rate> [0..1] Rate 99

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 99

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 100
✓C11
Details <Dtls> [0..*] 101

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 103

RelatedRemittanceInformation <RltdRmtInf> [0..10] ± 103

RemittanceInformation <RmtInf> [0..1] 103

Unstructured <Ustrd> [0..*] Text 107

Structured <Strd> [0..*] 107

ReferredDocumentInformation <RfrdDocInf> [0..*] 110

Type <Tp> [0..1] 112

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

Number <Nb> [0..1] Text 114

RelatedDate <RltdDt> [0..1] Date 114

LineDetails <LineDtls> [0..*] 114

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

49
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason [0..*] 122
<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11
ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 125

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 125

Invoicer <Invcr> [0..1] ± 126

Invoicee <Invcee> [0..1] ± 126

TaxRemittance <TaxRmt> [0..1] 127

Creditor <Cdtr> [0..1] ± 129

Debtor <Dbtr> [0..1] ± 129

UltimateDebtor <UltmtDbtr> [0..1] ± 129

50 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AdministrationZone <AdmstnZone> [0..1] Text 130

ReferenceNumber <RefNb> [0..1] Text 130

Method <Mtd> [0..1] Text 130

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 130

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 131
✓C11
Date <Dt> [0..1] Date 131

SequenceNumber <SeqNb> [0..1] Quantity 132

Record <Rcrd> [0..*] 132

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 139

51
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 139

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 140

SupplementaryData <SplmtryData> [0..*] ± C42 140

Constraints

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

If ChargeBearer contains CRED, then at least one occurrence of ChargesInformation must be

present 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 severity: Fatal

– Error Code: X00046

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

• ChargesAmountGuideline
If ChargesInformation is present, then the currency of ChargesInformation/ChargesAmount is
recommended to be the same as the currency of InterbankSettlementAmount.

• ChargesInformationAndInstructedAmountRule
If ChargesInformation is present, then InstructedAmount must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00048

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

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

• InstructedAmountAndExchangeRate1Rule
If InstructedAmount is present and the currency is different from the currency in
InterbankSettlementAmount, then ExchangeRate must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00049

52 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

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

• InstructedAmountAndExchangeRate2Rule
If InstructedAmount is present and the currency is the same as the currency in
InterbankSettlementAmount, then ExchangeRate is not allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00050

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

• InstructedAmountAndExchangeRate3Rule
If InstructedAmount is not present, then ExchangeRate is not allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00061

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

• InstructionForCreditorAgentRule
If InstructionForCreditorAgent/Code contains CHQB (PayCreditorByCheque), then CreditorAccount
is not allowed.
Error handling:

– Error severity: Fatal

– Error Code: X00051

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

• IntermediaryAgent1AccountRule
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00052

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

• IntermediaryAgent2AccountRule
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00053

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

53
Standards MX

• IntermediaryAgent2Rule
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00056

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

• IntermediaryAgent3AccountRule
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00054

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

• IntermediaryAgent3Rule
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00057

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

• PreviousInstructingAgent1AccountRule
If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00411

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

• PreviousInstructingAgent1Guideline
It is recommended that, when present, PreviousInstructingAgent1 is the closest to the DebtorAgent
in the payment chain.

• PreviousInstructingAgent2AccountRule
If PreviousInstructingAgent2Account is present, then PreviousInstructingAgent2 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00412

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

54 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

• PreviousInstructingAgent2Rule
If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00415

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

• PreviousInstructingAgent3AccountRule
If PreviousInstructingAgent3Account is present, then PreviousInstructingAgent3 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00413

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

• PreviousInstructingAgent3Rule
If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be present.
Error handling:

– Error severity: Fatal

– Error Code: X00416

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

• UltimateCreditorGuideline
UltimateCreditor may only be present if different from Creditor.

• UltimateDebtorGuideline
UltimateDebtor may only be present if different from Debtor.

1.4.2.1 PaymentIdentification <PmtId>

Presence: [1..1]
Definition: Set of elements used to reference a payment instruction.
Impacted by: ✓C48 TransactionIdentificationPresenceRule ✓

55
Standards MX

PaymentIdentification <PmtId> contains the following elements (see PaymentIdentification13 on

page 160 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionIdentification <InstrId> [0..1] Text 161

EndToEndIdentification <EndToEndId> [1..1] Text 161

TransactionIdentification <TxId> [0..1] Text 161

UETR <UETR> [0..1] IdentifierSet 162

ClearingSystemReference <ClrSysRef> [0..1] Text 162

Constraints

• TransactionIdentificationPresenceRule
TransactionIdentification or UETR must be present. Both may be present
Error handling:

– Error severity: Fatal

– Error Code: X00420

– Error Text: No transaction identification is present

1.4.2.2 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.
PaymentTypeInformation <PmtTpInf> contains the following elements (see
PaymentTypeInformation28 on page 178 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 178

ClearingChannel <ClrChanl> [0..1] CodeSet 178

ServiceLevel <SvcLvl> [0..*] 179

{Or Code <Cd> [1..1] CodeSet 179

Or} Proprietary <Prtry> [1..1] Text 179

LocalInstrument <LclInstrm> [0..1] 179

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

Or} Proprietary <Prtry> [1..1] Text 180

CategoryPurpose <CtgyPurp> [0..1] 180

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

Or} Proprietary <Prtry> [1..1] Text 180

56 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.3 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [1..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: ✓C1 ActiveCurrency ✓, ✓C10 CurrencyAmount ✓
Datatype: ActiveCurrencyAndAmount on page 200

Constraints

• ActiveCurrency
The currency code must be a valid active currency code, not yet withdrawn on the day the message
containing the currency is exchanged. Valid active currency codes are registered with the ISO 4217
Maintenance Agency, consist of three (3) contiguous letters, and are not yet withdrawn on the day
the message containing the Currency is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00005

– Error Text: Invalid currency code

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.4 InterbankSettlementDate <IntrBkSttlmDt>

Presence: [0..1]
Definition: Date on which the amount of money ceases to be available to the agent that owes it and
when the amount of money becomes available to the agent to which it is due.
Datatype: ISODate on page 232

1.4.2.5 SettlementPriority <SttlmPrty>

Presence: [0..1]
Definition: Indicator of the urgency or order of importance that the instructing party would like the
instructed party to apply to the processing of the settlement instruction.
Datatype: Priority3Code on page 227

CodeName Name Definition

URGT Urgent Priority level is urgent (highest priority

possible).

HIGH High Priority level is high.

57
Standards MX

CodeName Name Definition

NORM Normal Priority level is normal.

1.4.2.6 SettlementTimeIndication <SttlmTmIndctn>

Presence: [0..1]
Definition: Provides information on the occurred settlement time(s) of the payment transaction.
SettlementTimeIndication <SttlmTmIndctn> contains the following SettlementDateTimeIndication1
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebitDateTime <DbtDtTm> [0..1] DateTime 58

CreditDateTime <CdtDtTm> [0..1] DateTime 58

1.4.2.6.1 DebitDateTime <DbtDtTm>

Presence: [0..1]
Definition: Date and time at which a payment has been debited at the transaction administrator. In
the case of TARGET, the date and time at which the payment has been debited at the central bank,
expressed in Central European Time (CET).
Datatype: ISODateTime on page 232

1.4.2.6.2 CreditDateTime <CdtDtTm>

Presence: [0..1]
Definition: Date and time at which a payment has been credited at the transaction administrator. In the
case of TARGET, the date and time at which the payment has been credited at the receiving central
bank, expressed in Central European Time (CET).
Datatype: ISODateTime on page 232

1.4.2.7 SettlementTimeRequest <SttlmTmReq>

Presence: [0..1]
Definition: Provides information on the requested settlement time(s) of the payment instruction.
SettlementTimeRequest <SttlmTmReq> contains the following elements (see
SettlementTimeRequest2 on page 176 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CLSTime <CLSTm> [0..1] Time 177

TillTime <TillTm> [0..1] Time 177

FromTime <FrTm> [0..1] Time 177

RejectTime <RjctTm> [0..1] Time 177

1.4.2.8 AcceptanceDateTime <AccptncDtTm>

Presence: [0..1]

58 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Definition: Point in time when the payment order from the initiating party meets the processing
conditions of the account servicing agent. This means that the account servicing agent has received the
payment order and has applied checks such as authorisation, availability of funds.
Datatype: ISODateTime on page 232

1.4.2.9 PoolingAdjustmentDate <PoolgAdjstmntDt>

Presence: [0..1]
Definition: Date used for the correction of the value date of a cash pool movement that has been posted
with a different value date.
Datatype: ISODate on page 232

1.4.2.10 InstructedAmount <InstdAmt>

Presence: [0..1]
Definition: Amount of money to be moved between the debtor and creditor, before deduction of
charges, expressed in the currency as ordered by the initiating party.

Usage: This amount has to be transported unchanged through the transaction chain.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.11 ExchangeRate <XchgRate>

Presence: [0..1]

59
Standards MX

Definition: Factor used to convert an amount from one currency into another. This reflects the price at
which one currency was bought with another currency.
Datatype: BaseOneRate on page 235

1.4.2.12 ChargeBearer <ChrgBr>

Presence: [1..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the
payment transaction.
Datatype: ChargeBearerType1Code on page 204

CodeName Name Definition

DEBT BorneByDebtor All transaction charges are to be borne

by the debtor.

CRED BorneByCreditor All transaction charges are to be borne

by the creditor.

SHAR Shared In a credit transfer context, means that

transaction charges on the sender
side are to be borne by the debtor,
transaction charges on the receiver
side are to be borne by the creditor.
In a direct debit context, means that
transaction charges on the sender
side are to be borne by the creditor,
transaction charges on the receiver side
are to be borne by the debtor.

SLEV FollowingServiceLevel Charges are to be applied following the

rules agreed in the service level and/or
scheme.

1.4.2.13 ChargesInformation <ChrgsInf>

Presence: [0..*]
Definition: Provides information on the charges to be paid by the charge bearer(s) related to the
payment transaction.
ChargesInformation <ChrgsInf> contains the following elements (see Charges7 on page 145 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount 145

Agent <Agt> [1..1] ± 145

1.4.2.14 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

60 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

MandateRelatedInformation <MndtRltdInf> contains the following elements (see

CreditTransferMandateData1 on page 146 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

MandateIdentification <MndtId> [0..1] Text 146

Type <Tp> [0..1] ± 147

DateOfSignature <DtOfSgntr> [0..1] Date 147

DateOfVerification <DtOfVrfctn> [0..1] DateTime 147

ElectronicSignature <ElctrncSgntr> [0..1] Binary 147

FirstPaymentDate <FrstPmtDt> [0..1] Date 147

FinalPaymentDate <FnlPmtDt> [0..1] Date 147

Frequency <Frqcy> [0..1] ± 148

Reason <Rsn> [0..1] 148

{Or Code <Cd> [1..1] CodeSet 148

Or} Proprietary <Prtry> [1..1] Text 148

1.4.2.15 PreviousInstructingAgent1 <PrvsInstgAgt1>

Presence: [0..1]
Definition: Agent between the debtor's agent and the instructing agent.

Usage: If more than one previous instructing agent is present, then PreviousInstructingAgent1 identifies
the agent between the DebtorAgent and the PreviousInstructingAgent2.
PreviousInstructingAgent1 <PrvsInstgAgt1> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.16 PreviousInstructingAgent1Account <PrvsInstgAgt1Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent at its servicing
agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline

61
Standards MX

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> contains the following CashAccount40

elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 62

Type <Tp> [0..1] ± 62

Currency <Ccy> [0..1] CodeSet ✓C2 63

Name <Nm> [0..1] Text 63

Proxy <Prxy> [0..1] ± 63

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.16.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.16.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.

62 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.16.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.16.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.16.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.

63
Standards MX

Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.17 PreviousInstructingAgent2 <PrvsInstgAgt2>

Presence: [0..1]
Definition: Agent between the debtor's agent and the instructing agent.

Usage: If more than two previous instructing agent are present, then PreviousInstructingAgent2
identifies the agent between the PreviousInstructingAgent1 and the PreviousInstructingAgent3.
PreviousInstructingAgent2 <PrvsInstgAgt2> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.18 PreviousInstructingAgent2Account <PrvsInstgAgt2Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent at its servicing
agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
PreviousInstructingAgent2Account <PrvsInstgAgt2Acct> contains the following CashAccount40
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 65

Type <Tp> [0..1] ± 65

Currency <Ccy> [0..1] CodeSet ✓C2 65

Name <Nm> [0..1] Text 66

Proxy <Prxy> [0..1] ± 66

64 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.18.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.18.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.18.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

65
Standards MX

Impacted by: ✓C2 ActiveOrHistoricCurrency ✓

Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.18.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.18.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.19 PreviousInstructingAgent3 <PrvsInstgAgt3>

Presence: [0..1]
Definition: Agent between the debtor's agent and the instructing agent.

Usage: If PreviousInstructingAgent3 is present, then PreviousInstructingAgent3 identifies the agent

between the PreviousInstructingAgent2 and the InstructingAgent.

66 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

PreviousInstructingAgent3 <PrvsInstgAgt3> contains the following elements (see

BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.20 PreviousInstructingAgent3Account <PrvsInstgAgt3Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent at its servicing
agent in the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
PreviousInstructingAgent3Account <PrvsInstgAgt3Acct> contains the following CashAccount40
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 67

Type <Tp> [0..1] ± 68

Currency <Ccy> [0..1] CodeSet ✓C2 68

Name <Nm> [0..1] Text 68

Proxy <Prxy> [0..1] ± 69

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.20.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.

67
Standards MX

Identification <Id> contains one of the following elements (see AccountIdentification4Choice on

page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.20.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.20.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.20.4 Name <Nm>

Presence: [0..1]

68 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.20.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.21 InstructingAgent <InstgAgt>

Presence: [0..1]
Definition: Agent that instructs the next party in the chain to carry out the (set of) instruction(s).
InstructingAgent <InstgAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.22 InstructedAgent <InstdAgt>

Presence: [0..1]
Definition: Agent that is instructed by the previous party in the chain to carry out the (set of)
instruction(s).
InstructedAgent <InstdAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

69
Standards MX

1.4.2.23 IntermediaryAgent1 <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
between the DebtorAgent and the IntermediaryAgent2.
IntermediaryAgent1 <IntrmyAgt1> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.24 IntermediaryAgent1Account <IntrmyAgt1Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the intermediary agent 1 at its servicing agent in
the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
IntermediaryAgent1Account <IntrmyAgt1Acct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 71

Type <Tp> [0..1] ± 71

Currency <Ccy> [0..1] CodeSet ✓C2 71

Name <Nm> [0..1] Text 72

Proxy <Prxy> [0..1] ± 72

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

70 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.24.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.24.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.24.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

71
Standards MX

– Error Text: Invalid currency code.

1.4.2.24.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.24.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.25 IntermediaryAgent2 <IntrmyAgt2>

Presence: [0..1]
Definition: Agent between the debtor's agent and the creditor's agent.

Usage: If more than two intermediary agents are present, then IntermediaryAgent2 identifies the agent
between the IntermediaryAgent1 and the IntermediaryAgent3.
IntermediaryAgent2 <IntrmyAgt2> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.26 IntermediaryAgent2Account <IntrmyAgt2Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the intermediary agent 2 at its servicing agent in
the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline

72 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

IntermediaryAgent2Account <IntrmyAgt2Acct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 73

Type <Tp> [0..1] ± 73

Currency <Ccy> [0..1] CodeSet ✓C2 74

Name <Nm> [0..1] Text 74

Proxy <Prxy> [0..1] ± 74

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.26.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.26.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.

73
Standards MX

Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.26.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.26.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.26.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.

74 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.27 IntermediaryAgent3 <IntrmyAgt3>

Presence: [0..1]
Definition: Agent between the debtor's agent and the creditor's agent.

Usage: If IntermediaryAgent3 is present, then it identifies the agent between the IntermediaryAgent 2
and the CreditorAgent.
IntermediaryAgent3 <IntrmyAgt3> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.28 IntermediaryAgent3Account <IntrmyAgt3Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the intermediary agent 3 at its servicing agent in
the payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
IntermediaryAgent3Account <IntrmyAgt3Acct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 76

Type <Tp> [0..1] ± 76

Currency <Ccy> [0..1] CodeSet ✓C2 76

Name <Nm> [0..1] Text 77

Proxy <Prxy> [0..1] ± 77

75
Standards MX

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.28.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.28.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.28.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

76 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Impacted by: ✓C2 ActiveOrHistoricCurrency ✓

Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.28.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.28.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.29 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.

77
Standards MX

UltimateDebtor <UltmtDbtr> contains the following elements (see PartyIdentification135 on

page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

1.4.2.30 InitiatingParty <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.
InitiatingParty <InitgPty> contains the following elements (see PartyIdentification135 on page 172
for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

1.4.2.31 Debtor <Dbtr>

Presence: [1..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains the following elements (see PartyIdentification135 on page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

78 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.32 DebtorAccount <DbtrAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the debtor to which a debit entry will be made
as a result of the transaction.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
DebtorAccount <DbtrAcct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 79

Type <Tp> [0..1] ± 79

Currency <Ccy> [0..1] CodeSet ✓C2 80

Name <Nm> [0..1] Text 80

Proxy <Prxy> [0..1] ± 80

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.32.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.32.2 Type <Tp>

Presence: [0..1]

79
Standards MX

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

Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.32.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.32.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.32.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.

80 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.33 DebtorAgent <DbtrAgt>

Presence: [1..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.34 DebtorAgentAccount <DbtrAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the debtor agent at its servicing agent in the
payment chain.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
DebtorAgentAccount <DbtrAgtAcct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 82

Type <Tp> [0..1] ± 82

Currency <Ccy> [0..1] CodeSet ✓C2 82

Name <Nm> [0..1] Text 83

Proxy <Prxy> [0..1] ± 83

81
Standards MX

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.34.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.34.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.34.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.

82 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Impacted by: ✓C2 ActiveOrHistoricCurrency ✓

Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.34.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.34.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.35 CreditorAgent <CdtrAgt>

Presence: [1..1]
Definition: Financial institution servicing an account for the creditor.

83
Standards MX

CreditorAgent <CdtrAgt> contains the following elements (see

BranchAndFinancialInstitutionIdentification6 on page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

1.4.2.36 CreditorAgentAccount <CdtrAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the creditor agent at its servicing agent to which
a credit entry will be made as a result of the payment transaction.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline
CreditorAgentAccount <CdtrAgtAcct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 84

Type <Tp> [0..1] ± 85

Currency <Ccy> [0..1] CodeSet ✓C2 85

Name <Nm> [0..1] Text 85

Proxy <Prxy> [0..1] ± 86

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.36.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.

84 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Identification <Id> contains one of the following elements (see AccountIdentification4Choice on

page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.36.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.
Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.36.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.36.4 Name <Nm>

Presence: [0..1]

85
Standards MX

Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.36.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.
Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.37 Creditor <Cdtr>

Presence: [1..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains the following elements (see PartyIdentification135 on page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

1.4.2.38 CreditorAccount <CdtrAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the creditor to which a credit entry will be
posted as a result of the payment transaction.
Impacted by: ✓C15 IdentificationOrProxyPresenceRule ✓, C14 IdentificationAndProxyGuideline

86 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

CreditorAccount <CdtrAcct> contains the following CashAccount40 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 87

Type <Tp> [0..1] ± 87

Currency <Ccy> [0..1] CodeSet ✓C2 88

Name <Nm> [0..1] Text 88

Proxy <Prxy> [0..1] ± 88

Constraints

• IdentificationAndProxyGuideline
If the account identification is not defined through a conventional identification such as an email
address or a mobile number, then the proxy element should be used for the identification of the
account.

• IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.
Error handling:

– Error severity: Fatal

– Error Code: X00498

– Error Text: Missing account identification or account proxy.

1.4.2.38.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification for the account between the account owner and the
account servicer.
Identification <Id> contains one of the following elements (see AccountIdentification4Choice on
page 144 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

1.4.2.38.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the nature, or use of the account.

87
Standards MX

Type <Tp> contains one of the following elements (see CashAccountType2Choice on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

1.4.2.38.3 Currency <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
currencies

and the initiating party needs to identify which currency needs to be used for settlement on the account.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓
Datatype: ActiveOrHistoricCurrencyCode on page 202

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

1.4.2.38.4 Name <Nm>

Presence: [0..1]
Definition: Name of the account, as assigned by the account servicing institution, in agreement with the
account owner in order to provide an additional means of identification of the account.

Usage: The account name is different from the account owner name. The account name is used in
certain user communities to provide a means of identifying the account, in addition to the account
owner's identity and the account number.
Datatype: Max70Text on page 238

1.4.2.38.5 Proxy <Prxy>

Presence: [0..1]
Definition: Specifies an alternate assumed name for the identification of the account.

88 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Proxy <Prxy> contains the following elements (see ProxyAccountIdentification1 on page 143 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

1.4.2.39 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains the following elements (see PartyIdentification135 on
page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

1.4.2.40 InstructionForCreditorAgent <InstrForCdtrAgt>

Presence: [0..*]
Definition: Further information related to the processing of the payment instruction, provided by the
initiating party, and intended for the creditor agent.
InstructionForCreditorAgent <InstrForCdtrAgt> contains the following elements (see
InstructionForCreditorAgent3 on page 177 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 177

InstructionInformation <InstrInf> [0..1] Text 178

1.4.2.41 InstructionForNextAgent <InstrForNxtAgt>

Presence: [0..*]
Definition: Further information related to the processing of the payment instruction that may need to be
acted upon by the next agent.

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

89
Standards MX

The instruction can relate to a level of service, can be an instruction that has to be executed by the
agent, or can be information required by the next agent.
InstructionForNextAgent <InstrForNxtAgt> contains the following InstructionForNextAgent1
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 90

InstructionInformation <InstrInf> [0..1] Text 90

1.4.2.41.1 Code <Cd>

Presence: [0..1]
Definition: Coded information related to the processing of the payment instruction, provided by the
initiating party, and intended for the next agent in the payment chain.
Datatype: Instruction4Code on page 223

CodeName Name Definition

PHOA PhoneNextAgent Please advise/contact next agent by

phone.

TELA TelecomNextAgent Please advise/contact next agent

by the most efficient means of
telecommunication.

1.4.2.41.2 InstructionInformation <InstrInf>

Presence: [0..1]
Definition: Further information complementing the coded instruction or instruction to the next agent that
is bilaterally agreed or specific to a user community.
Datatype: Max140Text on page 237

1.4.2.42 Purpose <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)
creditor to provide information concerning the nature of the payment. Purpose is a content element,
which is not used for processing by any of the agents involved in the payment chain.
Purpose <Purp> contains one of the following elements (see Purpose2Choice on page 165 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 166

Or} Proprietary <Prtry> [1..1] Text 166

1.4.2.43 RegulatoryReporting <RgltryRptg>

Presence: [0..10]

90 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Definition: Information needed due to regulatory and statutory requirements.

RegulatoryReporting <RgltryRptg> contains the following elements (see RegulatoryReporting3 on
page 189 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] CodeSet 190

Authority <Authrty> [0..1] 190

Name <Nm> [0..1] Text 190

Country <Ctry> [0..1] CodeSet 191

Details <Dtls> [0..*] 191

Type <Tp> [0..1] Text 191

Date <Dt> [0..1] Date 191

Country <Ctry> [0..1] CodeSet 191

Code <Cd> [0..1] Text 191

Amount <Amt> [0..1] Amount 192

Information <Inf> [0..*] Text 192

1.4.2.44 Tax <Tax>

Presence: [0..1]
Definition: Provides details on the tax.

91
Standards MX

Tax <Tax> contains the following TaxInformation10 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Creditor <Cdtr> [0..1] ± 93

Debtor <Dbtr> [0..1] ± 93

AdministrationZone <AdmstnZone> [0..1] Text 93

ReferenceNumber <RefNb> [0..1] Text 93

Method <Mtd> [0..1] Text 94

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 94

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 94
✓C11
Date <Dt> [0..1] Date 95

SequenceNumber <SeqNb> [0..1] Quantity 95

Record <Rcrd> [0..*] 95

Type <Tp> [0..1] Text 96

Category <Ctgy> [0..1] Text 96

CategoryDetails <CtgyDtls> [0..1] Text 97

DebtorStatus <DbtrSts> [0..1] Text 97

CertificateIdentification <CertId> [0..1] Text 97

FormsCode <FrmsCd> [0..1] Text 97

Period <Prd> [0..1] 97

Year <Yr> [0..1] Year 97

Type <Tp> [0..1] CodeSet 97

FromToDate <FrToDt> [0..1] ± 98

TaxAmount <TaxAmt> [0..1] 99

Rate <Rate> [0..1] Rate 99

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 99

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 100
✓C11
Details <Dtls> [0..*] 101

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

92 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 103

1.4.2.44.1 Creditor <Cdtr>

Presence: [0..1]
Definition: Party on the credit side of the transaction to which the tax applies.
Creditor <Cdtr> contains the following elements (see TaxParty1 on page 198 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 198

RegistrationIdentification <RegnId> [0..1] Text 198

TaxType <TaxTp> [0..1] Text 199

1.4.2.44.2 Debtor <Dbtr>

Presence: [0..1]
Definition: Party on the debit side of the transaction to which the tax applies.
Debtor <Dbtr> contains the following elements (see TaxParty2 on page 199 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 199

RegistrationIdentification <RegnId> [0..1] Text 199

TaxType <TaxTp> [0..1] Text 199

Authorisation <Authstn> [0..1] 199

Title <Titl> [0..1] Text 200

Name <Nm> [0..1] Text 200

1.4.2.44.3 AdministrationZone <AdmstnZone>

Presence: [0..1]
Definition: Territorial part of a country to which the tax payment is related.
Datatype: Max35Text on page 238

1.4.2.44.4 ReferenceNumber <RefNb>

Presence: [0..1]
Definition: Tax reference information that is specific to a taxing agency.
Datatype: Max140Text on page 237

93
Standards MX

1.4.2.44.5 Method <Mtd>

Presence: [0..1]
Definition: Method used to indicate the underlying business or how the tax is paid.
Datatype: Max35Text on page 238

1.4.2.44.6 TotalTaxableBaseAmount <TtlTaxblBaseAmt>

Presence: [0..1]
Definition: Total amount of money on which the tax is based.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.44.7 TotalTaxAmount <TtlTaxAmt>

Presence: [0..1]
Definition: Total amount of money as result of the calculation of the tax.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)

94 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.44.8 Date <Dt>

Presence: [0..1]
Definition: Date by which tax is due.
Datatype: ISODate on page 232

1.4.2.44.9 SequenceNumber <SeqNb>

Presence: [0..1]
Definition: Sequential number of the tax report.
Datatype: Number on page 235

1.4.2.44.10 Record <Rcrd>

Presence: [0..*]
Definition: Record of tax details.

95
Standards MX

Record <Rcrd> contains the following TaxRecord3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] Text 96

Category <Ctgy> [0..1] Text 96

CategoryDetails <CtgyDtls> [0..1] Text 97

DebtorStatus <DbtrSts> [0..1] Text 97

CertificateIdentification <CertId> [0..1] Text 97

FormsCode <FrmsCd> [0..1] Text 97

Period <Prd> [0..1] 97

Year <Yr> [0..1] Year 97

Type <Tp> [0..1] CodeSet 97

FromToDate <FrToDt> [0..1] ± 98

TaxAmount <TaxAmt> [0..1] 99

Rate <Rate> [0..1] Rate 99

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 99

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 100
✓C11
Details <Dtls> [0..*] 101

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 103

1.4.2.44.10.1 Type <Tp>

Presence: [0..1]
Definition: High level code to identify the type of tax details.
Datatype: Max35Text on page 238

1.4.2.44.10.2 Category <Ctgy>

Presence: [0..1]
Definition: Specifies the tax code as published by the tax authority.
Datatype: Max35Text on page 238

96 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.44.10.3 CategoryDetails <CtgyDtls>

Presence: [0..1]
Definition: Provides further details of the category tax code.
Datatype: Max35Text on page 238

1.4.2.44.10.4 DebtorStatus <DbtrSts>

Presence: [0..1]
Definition: Code provided by local authority to identify the status of the party that has drawn up the
settlement document.
Datatype: Max35Text on page 238

1.4.2.44.10.5 CertificateIdentification <CertId>

Presence: [0..1]
Definition: Identification number of the tax report as assigned by the taxing authority.
Datatype: Max35Text on page 238

1.4.2.44.10.6 FormsCode <FrmsCd>

Presence: [0..1]
Definition: Identifies, in a coded form, on which template the tax report is to be provided.
Datatype: Max35Text on page 238

1.4.2.44.10.7 Period <Prd>

Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
Period <Prd> contains the following TaxPeriod3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 97

Type <Tp> [0..1] CodeSet 97

FromToDate <FrToDt> [0..1] ± 98

1.4.2.44.10.7.1 Year <Yr>

Presence: [0..1]
Definition: Year related to the tax payment.
Datatype: ISOYear on page 239

1.4.2.44.10.7.2 Type <Tp>

Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: TaxRecordPeriod1Code on page 230

97
Standards MX

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

1.4.2.44.10.7.3 FromToDate <FrToDt>

Presence: [0..1]
Definition: Range of time between a start date and an end date for which the tax report is provided.

98 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

FromToDate <FrToDt> contains the following elements (see DatePeriod2 on page 145 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 146

ToDate <ToDt> [1..1] Date 146

1.4.2.44.10.8 TaxAmount <TaxAmt>

Presence: [0..1]
Definition: Set of elements used to provide information on the amount of the tax record.
TaxAmount <TaxAmt> contains the following TaxAmount3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Rate <Rate> [0..1] Rate 99

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 99

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 100
✓C11
Details <Dtls> [0..*] 101

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11

1.4.2.44.10.8.1 Rate <Rate>

Presence: [0..1]
Definition: Rate used to calculate the tax.
Datatype: PercentageRate on page 236

1.4.2.44.10.8.2 TaxableBaseAmount <TaxblBaseAmt>

Presence: [0..1]
Definition: Amount of money on which the tax is based.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)

99
Standards MX

contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.44.10.8.3 TotalAmount <TtlAmt>

Presence: [0..1]
Definition: Total amount that is the result of the calculation of the tax for the record.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

100 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.44.10.8.4 Details <Dtls>

Presence: [0..*]
Definition: Set of elements used to provide details on the tax period and amount.
Details <Dtls> contains the following TaxRecordDetails3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Period <Prd> [0..1] 101

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

Amount <Amt> [1..1] Amount ✓C2, 102

✓C11

1.4.2.44.10.8.4.1 Period <Prd>

Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
Period <Prd> contains the following TaxPeriod3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 101

Type <Tp> [0..1] CodeSet 101

FromToDate <FrToDt> [0..1] ± 102

1.4.2.44.10.8.4.1.1 Year <Yr>

Presence: [0..1]
Definition: Year related to the tax payment.
Datatype: ISOYear on page 239

1.4.2.44.10.8.4.1.2 Type <Tp>

Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: TaxRecordPeriod1Code on page 230

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

101
Standards MX

CodeName Name Definition

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

1.4.2.44.10.8.4.1.3 FromToDate <FrToDt>

Presence: [0..1]
Definition: Range of time between a start date and an end date for which the tax report is provided.
FromToDate <FrToDt> contains the following elements (see DatePeriod2 on page 145 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 146

ToDate <ToDt> [1..1] Date 146

1.4.2.44.10.8.4.2 Amount <Amt>

Presence: [1..1]
Definition: Underlying tax amount related to the specified period.

102 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓

Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.44.10.9 AdditionalInformation <AddtlInf>

Presence: [0..1]
Definition: Further details of the tax record.
Datatype: Max140Text on page 237

1.4.2.45 RelatedRemittanceInformation <RltdRmtInf>

Presence: [0..10]
Definition: Provides information related to the handling of the remittance information by any of the
agents in the transaction processing chain.
RelatedRemittanceInformation <RltdRmtInf> contains the following elements (see
RemittanceLocation7 on page 192 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

RemittanceIdentification <RmtId> [0..1] Text 192

RemittanceLocationDetails <RmtLctnDtls> [0..*] ± 192

1.4.2.46 RemittanceInformation <RmtInf>

Presence: [0..1]

103
Standards MX

Definition: Information supplied to enable the matching of an entry with the items that the transfer is
intended to settle, such as commercial invoices in an accounts' receivable system.

104 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

RemittanceInformation <RmtInf> contains the following RemittanceInformation21 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 107

Structured <Strd> [0..*] 107

ReferredDocumentInformation <RfrdDocInf> [0..*] 110

Type <Tp> [0..1] 112

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

Number <Nb> [0..1] Text 114

RelatedDate <RltdDt> [0..1] Date 114

LineDetails <LineDtls> [0..*] 114

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

105
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason [0..*] 122
<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11
ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 125

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 125

Invoicer <Invcr> [0..1] ± 126

Invoicee <Invcee> [0..1] ± 126

TaxRemittance <TaxRmt> [0..1] 127

Creditor <Cdtr> [0..1] ± 129

Debtor <Dbtr> [0..1] ± 129

UltimateDebtor <UltmtDbtr> [0..1] ± 129

AdministrationZone <AdmstnZone> [0..1] Text 130

ReferenceNumber <RefNb> [0..1] Text 130

Method <Mtd> [0..1] Text 130

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 130

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 131
✓C11
Date <Dt> [0..1] Date 131

SequenceNumber <SeqNb> [0..1] Quantity 132

Record <Rcrd> [0..*] 132

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

106 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 139

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 139

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 140

1.4.2.46.1 Unstructured <Ustrd>

Presence: [0..*]
Definition: Information supplied to enable the matching/reconciliation of an entry with the items that the
payment is intended to settle, such as commercial invoices in an accounts' receivable system, in an
unstructured form.
Datatype: Max140Text on page 237

1.4.2.46.2 Structured <Strd>

Presence: [0..*]
Definition: Information supplied to enable the matching/reconciliation of an entry with the items that
the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in a
structured form.

107
Standards MX

Structured <Strd> contains the following StructuredRemittanceInformation17 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ReferredDocumentInformation <RfrdDocInf> [0..*] 110

Type <Tp> [0..1] 112

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

Number <Nb> [0..1] Text 114

RelatedDate <RltdDt> [0..1] Date 114

LineDetails <LineDtls> [0..*] 114

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

108 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason [0..*] 122
<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11
ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 125

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 125

Invoicer <Invcr> [0..1] ± 126

Invoicee <Invcee> [0..1] ± 126

TaxRemittance <TaxRmt> [0..1] 127

Creditor <Cdtr> [0..1] ± 129

Debtor <Dbtr> [0..1] ± 129

UltimateDebtor <UltmtDbtr> [0..1] ± 129

AdministrationZone <AdmstnZone> [0..1] Text 130

ReferenceNumber <RefNb> [0..1] Text 130

Method <Mtd> [0..1] Text 130

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 130

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 131
✓C11
Date <Dt> [0..1] Date 131

SequenceNumber <SeqNb> [0..1] Quantity 132

Record <Rcrd> [0..*] 132

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

109
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 139

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 139

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 140

1.4.2.46.2.1 ReferredDocumentInformation <RfrdDocInf>

Presence: [0..*]
Definition: Provides the identification and the content of the referred document.

110 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

ReferredDocumentInformation <RfrdDocInf> contains the following

ReferredDocumentInformation7 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 112

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

Number <Nb> [0..1] Text 114

RelatedDate <RltdDt> [0..1] Date 114

LineDetails <LineDtls> [0..*] 114

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

111
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason [0..*] 122
<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11

1.4.2.46.2.1.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of referred document.
Type <Tp> contains the following ReferredDocumentType4 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 112

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

Issuer <Issr> [0..1] Text 113

1.4.2.46.2.1.1.1 CodeOrProprietary <CdOrPrtry>

Presence: [1..1]
Definition: Provides the type details of the referred document.
CodeOrProprietary <CdOrPrtry> contains one of the following ReferredDocumentType3Choice
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 112

Or} Proprietary <Prtry> [1..1] Text 113

1.4.2.46.2.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Document type in a coded form.
Datatype: DocumentType6Code on page 207

112 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

CodeName Name Definition

MSIN MeteredServiceInvoice Document is an invoice claiming

payment for the supply of metered
services, for example gas or electricity
supplied to a fixed meter.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the

final amount settled for a commercial
transaction.

DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the final

amount settled for a commercial
transaction.

CINV CommercialInvoice Document is an invoice.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.

HIRI HireInvoice Document is an invoice for the hiring of

human resources or renting goods or
equipment.

SBIN SelfBilledInvoice Document is an invoice issued by the

debtor.

CMCN CommercialContract Document is an agreement between

the parties, stipulating the terms and
conditions of the delivery of goods or
services.

SOAC StatementOfAccount Document is a statement of the

transactions posted to the debtor's
account at the supplier.

DISP DispatchAdvice Document is a dispatch advice.

BOLD BillOfLading Document is a shipping notice.

VCHR Voucher Document is an electronic payment

document.

AROI AccountReceivableOpenItem Document is a payment that applies to a

specific source document.

TSUT TradeServicesUtilityTransaction Document is a transaction identifier as

assigned by the Trade Services Utility.

PUOR PurchaseOrder Document is a purchase order.

1.4.2.46.2.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Proprietary identification of the type of the remittance document.
Datatype: Max35Text on page 238

1.4.2.46.2.1.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Identification of the issuer of the reference document type.
Datatype: Max35Text on page 238

113
Standards MX

1.4.2.46.2.1.2 Number <Nb>

Presence: [0..1]
Definition: Unique and unambiguous identification of the referred document.
Datatype: Max35Text on page 238

1.4.2.46.2.1.3 RelatedDate <RltdDt>

Presence: [0..1]
Definition: Date associated with the referred document.
Datatype: ISODate on page 232

1.4.2.46.2.1.4 LineDetails <LineDtls>

Presence: [0..*]
Definition: Set of elements used to provide the content of the referred document line.

114 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

LineDetails <LineDtls> contains the following DocumentLineInformation1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..*] 116

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

Description <Desc> [0..1] Text 117

Amount <Amt> [0..1] 117

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason [0..*] 122
<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11

115
Standards MX

1.4.2.46.2.1.4.1 Identification <Id>

Presence: [1..*]
Definition: Provides identification of the document line.
Identification <Id> contains the following DocumentLineIdentification1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 116

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

Number <Nb> [0..1] Text 117

RelatedDate <RltdDt> [0..1] Date 117

1.4.2.46.2.1.4.1.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of referred document line identification.
Type <Tp> contains the following DocumentLineType1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 116

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

Issuer <Issr> [0..1] Text 117

1.4.2.46.2.1.4.1.1.1 CodeOrProprietary <CdOrPrtry>

Presence: [1..1]
Definition: Provides the type details of the referred document line identification.
CodeOrProprietary <CdOrPrtry> contains one of the following DocumentLineType1Choice
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 116

Or} Proprietary <Prtry> [1..1] Text 117

1.4.2.46.2.1.4.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Line identification type in a coded form.

116 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Datatype: ExternalDocumentLineType1Code on page 214

1.4.2.46.2.1.4.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Proprietary identification of the type of the remittance document.
Datatype: Max35Text on page 238

1.4.2.46.2.1.4.1.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Identification of the issuer of the reference document line identificationtype.
Datatype: Max35Text on page 238

1.4.2.46.2.1.4.1.2 Number <Nb>

Presence: [0..1]
Definition: Identification of the type specified for the referred document line.
Datatype: Max35Text on page 238

1.4.2.46.2.1.4.1.3 RelatedDate <RltdDt>

Presence: [0..1]
Definition: Date associated with the referred document line.
Datatype: ISODate on page 232

1.4.2.46.2.1.4.2 Description <Desc>

Presence: [0..1]
Definition: Description associated with the document line.
Datatype: Max2048Text on page 237

1.4.2.46.2.1.4.3 Amount <Amt>

Presence: [0..1]
Definition: Provides details on the amounts of the document line.

117
Standards MX

Amount <Amt> contains the following RemittanceAmount3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount ✓C2, 118

✓C11
DiscountAppliedAmount <DscntApldAmt> [0..*] 119

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11
CreditNoteAmount <CdtNoteAmt> [0..1] Amount ✓C2, 120
✓C11
TaxAmount <TaxAmt> [0..*] 121

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11
AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 122

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

RemittedAmount <RmtdAmt> [0..1] Amount ✓C2, 124

✓C11

1.4.2.46.2.1.4.3.1 DuePayableAmount <DuePyblAmt>

Presence: [0..1]
Definition: Amount specified is the exact amount due and payable to the creditor.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.

118 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.1.4.3.2 DiscountAppliedAmount <DscntApldAmt>

Presence: [0..*]
Definition: Amount of discount to be applied to the amount due and payable to the creditor.
DiscountAppliedAmount <DscntApldAmt> contains the following DiscountAmountAndType1
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 119

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

Amount <Amt> [1..1] Amount ✓C2, 120

✓C11

1.4.2.46.2.1.4.3.2.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.
Type <Tp> contains one of the following DiscountAmountType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 119

Or} Proprietary <Prtry> [1..1] Text 120

1.4.2.46.2.1.4.3.2.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: ExternalDiscountAmountType1Code on page 213

119
Standards MX

1.4.2.46.2.1.4.3.2.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: Max35Text on page 238

1.4.2.46.2.1.4.3.2.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.1.4.3.3 CreditNoteAmount <CdtNoteAmt>

Presence: [0..1]
Definition: Amount of a credit note.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)

120 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.1.4.3.4 TaxAmount <TaxAmt>

Presence: [0..*]
Definition: Amount of the tax.
TaxAmount <TaxAmt> contains the following TaxAmountAndType1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 121

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

Or} Proprietary <Prtry> [1..1] Text 122

Amount <Amt> [1..1] Amount ✓C2, 122

✓C11

1.4.2.46.2.1.4.3.4.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.
Type <Tp> contains one of the following TaxAmountType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

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

Or} Proprietary <Prtry> [1..1] Text 122

1.4.2.46.2.1.4.3.4.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.

121
Standards MX

Datatype: ExternalTaxAmountType1Code on page 221

1.4.2.46.2.1.4.3.4.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: Max35Text on page 238

1.4.2.46.2.1.4.3.4.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.1.4.3.5 AdjustmentAmountAndReason <AdjstmntAmtAndRsn>

Presence: [0..*]
Definition: Specifies detailed information on the amount and reason of the adjustment.

122 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> contains the following

DocumentAdjustment1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount ✓C2, 123

✓C11
CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 123

Reason <Rsn> [0..1] Text 124

AdditionalInformation <AddtlInf> [0..1] Text 124

1.4.2.46.2.1.4.3.5.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money of the document adjustment.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.1.4.3.5.2 CreditDebitIndicator <CdtDbtInd>

Presence: [0..1]
Definition: Specifies whether the adjustment must be subtracted or added to the total amount.
Datatype: CreditDebitCode on page 206

123
Standards MX

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

1.4.2.46.2.1.4.3.5.3 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the adjustment.
Datatype: Max4Text on page 238

1.4.2.46.2.1.4.3.5.4 AdditionalInformation <AddtlInf>

Presence: [0..1]
Definition: Provides further details on the document adjustment.
Datatype: Max140Text on page 237

1.4.2.46.2.1.4.3.6 RemittedAmount <RmtdAmt>

Presence: [0..1]
Definition: Amount of money remitted.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

124 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.46.2.2 ReferredDocumentAmount <RfrdDocAmt>

Presence: [0..1]
Definition: Provides details on the amounts of the referred document.
ReferredDocumentAmount <RfrdDocAmt> contains the following elements (see RemittanceAmount2
on page 166 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount 167

DiscountAppliedAmount <DscntApldAmt> [0..*] 167

Type <Tp> [0..1] 168

{Or Code <Cd> [1..1] CodeSet 168

Or} Proprietary <Prtry> [1..1] Text 168

Amount <Amt> [1..1] Amount 168

CreditNoteAmount <CdtNoteAmt> [0..1] Amount 168

TaxAmount <TaxAmt> [0..*] 168

Type <Tp> [0..1] 169

{Or Code <Cd> [1..1] CodeSet 169

Or} Proprietary <Prtry> [1..1] Text 169

Amount <Amt> [1..1] Amount 169

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 169

Amount <Amt> [1..1] Amount 170

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 170

Reason <Rsn> [0..1] Text 170

AdditionalInformation <AddtlInf> [0..1] Text 170

RemittedAmount <RmtdAmt> [0..1] Amount 170

1.4.2.46.2.3 CreditorReferenceInformation <CdtrRefInf>

Presence: [0..1]
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.

125
Standards MX

CreditorReferenceInformation <CdtrRefInf> contains the following elements (see

CreditorReferenceInformation2 on page 149 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 149

CodeOrProprietary <CdOrPrtry> [1..1] 149

{Or Code <Cd> [1..1] CodeSet 149

Or} Proprietary <Prtry> [1..1] Text 150

Issuer <Issr> [0..1] Text 150

Reference <Ref> [0..1] Text 150

1.4.2.46.2.4 Invoicer <Invcr>

Presence: [0..1]
Definition: Identification of the organisation issuing the invoice, when it is different from the creditor or
ultimate creditor.
Invoicer <Invcr> contains the following elements (see PartyIdentification135 on page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

1.4.2.46.2.5 Invoicee <Invcee>

Presence: [0..1]
Definition: Identification of the party to whom an invoice is issued, when it is different from the debtor or
ultimate debtor.
Invoicee <Invcee> contains the following elements (see PartyIdentification135 on page 172 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

126 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

1.4.2.46.2.6 TaxRemittance <TaxRmt>

Presence: [0..1]
Definition: Provides remittance information about a payment made for tax-related purposes.

127
Standards MX

TaxRemittance <TaxRmt> contains the following TaxData1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Creditor <Cdtr> [0..1] ± 129

Debtor <Dbtr> [0..1] ± 129

UltimateDebtor <UltmtDbtr> [0..1] ± 129

AdministrationZone <AdmstnZone> [0..1] Text 130

ReferenceNumber <RefNb> [0..1] Text 130

Method <Mtd> [0..1] Text 130

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount ✓C2, 130

✓C11
TotalTaxAmount <TtlTaxAmt> [0..1] Amount ✓C2, 131
✓C11
Date <Dt> [0..1] Date 131

SequenceNumber <SeqNb> [0..1] Quantity 132

Record <Rcrd> [0..*] 132

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

128 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 139

1.4.2.46.2.6.1 Creditor <Cdtr>

Presence: [0..1]
Definition: Party on the credit side of the transaction to which the tax applies.
Creditor <Cdtr> contains the following elements (see TaxParty1 on page 198 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 198

RegistrationIdentification <RegnId> [0..1] Text 198

TaxType <TaxTp> [0..1] Text 199

1.4.2.46.2.6.2 Debtor <Dbtr>

Presence: [0..1]
Definition: Party on the debit side of the transaction to which the tax applies.
Debtor <Dbtr> contains the following elements (see TaxParty2 on page 199 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 199

RegistrationIdentification <RegnId> [0..1] Text 199

TaxType <TaxTp> [0..1] Text 199

Authorisation <Authstn> [0..1] 199

Title <Titl> [0..1] Text 200

Name <Nm> [0..1] Text 200

1.4.2.46.2.6.3 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to the
taxing authority.

129
Standards MX

UltimateDebtor <UltmtDbtr> contains the following elements (see TaxParty2 on page 199 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 199

RegistrationIdentification <RegnId> [0..1] Text 199

TaxType <TaxTp> [0..1] Text 199

Authorisation <Authstn> [0..1] 199

Title <Titl> [0..1] Text 200

Name <Nm> [0..1] Text 200

1.4.2.46.2.6.4 AdministrationZone <AdmstnZone>

Presence: [0..1]
Definition: Territorial part of a country to which the tax payment is related.
Datatype: Max35Text on page 238

1.4.2.46.2.6.5 ReferenceNumber <RefNb>

Presence: [0..1]
Definition: Tax reference information that is specific to a taxing agency.
Datatype: Max140Text on page 237

1.4.2.46.2.6.6 Method <Mtd>

Presence: [0..1]
Definition: Method used to indicate the underlying business or how the tax is paid.
Datatype: Max35Text on page 238

1.4.2.46.2.6.7 TotalTaxableBaseAmount <TtlTaxblBaseAmt>

Presence: [0..1]
Definition: Total amount of money on which the tax is based.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

130 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.6.8 TotalTaxAmount <TtlTaxAmt>

Presence: [0..1]
Definition: Total amount of money as result of the calculation of the tax.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.6.9 Date <Dt>

Presence: [0..1]
Definition: Date by which tax is due.
Datatype: ISODate on page 232

131
Standards MX

1.4.2.46.2.6.10 SequenceNumber <SeqNb>

Presence: [0..1]
Definition: Sequential number of the tax report.
Datatype: Number on page 235

1.4.2.46.2.6.11 Record <Rcrd>

Presence: [0..*]
Definition: Record of tax details.
Record <Rcrd> contains the following TaxRecord3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] Text 132

Category <Ctgy> [0..1] Text 133

CategoryDetails <CtgyDtls> [0..1] Text 133

DebtorStatus <DbtrSts> [0..1] Text 133

CertificateIdentification <CertId> [0..1] Text 133

FormsCode <FrmsCd> [0..1] Text 133

Period <Prd> [0..1] 133

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

TaxAmount <TaxAmt> [0..1] 135

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11
AdditionalInformation <AddtlInf> [0..1] Text 139

1.4.2.46.2.6.11.1 Type <Tp>

Presence: [0..1]

132 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Definition: High level code to identify the type of tax details.

Datatype: Max35Text on page 238

1.4.2.46.2.6.11.2 Category <Ctgy>

Presence: [0..1]
Definition: Specifies the tax code as published by the tax authority.
Datatype: Max35Text on page 238

1.4.2.46.2.6.11.3 CategoryDetails <CtgyDtls>

Presence: [0..1]
Definition: Provides further details of the category tax code.
Datatype: Max35Text on page 238

1.4.2.46.2.6.11.4 DebtorStatus <DbtrSts>

Presence: [0..1]
Definition: Code provided by local authority to identify the status of the party that has drawn up the
settlement document.
Datatype: Max35Text on page 238

1.4.2.46.2.6.11.5 CertificateIdentification <CertId>

Presence: [0..1]
Definition: Identification number of the tax report as assigned by the taxing authority.
Datatype: Max35Text on page 238

1.4.2.46.2.6.11.6 FormsCode <FrmsCd>

Presence: [0..1]
Definition: Identifies, in a coded form, on which template the tax report is to be provided.
Datatype: Max35Text on page 238

1.4.2.46.2.6.11.7 Period <Prd>

Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
Period <Prd> contains the following TaxPeriod3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 133

Type <Tp> [0..1] CodeSet 134

FromToDate <FrToDt> [0..1] ± 134

1.4.2.46.2.6.11.7.1 Year <Yr>

Presence: [0..1]
Definition: Year related to the tax payment.

133
Standards MX

Datatype: ISOYear on page 239

1.4.2.46.2.6.11.7.2 Type <Tp>

Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: TaxRecordPeriod1Code on page 230

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

1.4.2.46.2.6.11.7.3 FromToDate <FrToDt>

Presence: [0..1]

134 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Definition: Range of time between a start date and an end date for which the tax report is provided.
FromToDate <FrToDt> contains the following elements (see DatePeriod2 on page 145 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 146

ToDate <ToDt> [1..1] Date 146

1.4.2.46.2.6.11.8 TaxAmount <TaxAmt>

Presence: [0..1]
Definition: Set of elements used to provide information on the amount of the tax record.
TaxAmount <TaxAmt> contains the following TaxAmount3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Rate <Rate> [0..1] Rate 135

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount ✓C2, 135

✓C11
TotalAmount <TtlAmt> [0..1] Amount ✓C2, 136
✓C11
Details <Dtls> [0..*] 137

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11

1.4.2.46.2.6.11.8.1 Rate <Rate>

Presence: [0..1]
Definition: Rate used to calculate the tax.
Datatype: PercentageRate on page 236

1.4.2.46.2.6.11.8.2 TaxableBaseAmount <TaxblBaseAmt>

Presence: [0..1]
Definition: Amount of money on which the tax is based.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

135
Standards MX

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.6.11.8.3 TotalAmount <TtlAmt>

Presence: [0..1]
Definition: Total amount that is the result of the calculation of the tax for the record.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

136 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Error handling:

– Error severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.6.11.8.4 Details <Dtls>

Presence: [0..*]
Definition: Set of elements used to provide details on the tax period and amount.
Details <Dtls> contains the following TaxRecordDetails3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Period <Prd> [0..1] 137

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

Amount <Amt> [1..1] Amount ✓C2, 139

✓C11

1.4.2.46.2.6.11.8.4.1 Period <Prd>

Presence: [0..1]
Definition: Set of elements used to provide details on the period of time related to the tax payment.
Period <Prd> contains the following TaxPeriod3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 137

Type <Tp> [0..1] CodeSet 137

FromToDate <FrToDt> [0..1] ± 138

1.4.2.46.2.6.11.8.4.1.1 Year <Yr>

Presence: [0..1]
Definition: Year related to the tax payment.
Datatype: ISOYear on page 239

1.4.2.46.2.6.11.8.4.1.2 Type <Tp>

Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: TaxRecordPeriod1Code on page 230

137
Standards MX

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

1.4.2.46.2.6.11.8.4.1.3 FromToDate <FrToDt>

Presence: [0..1]
Definition: Range of time between a start date and an end date for which the tax report is provided.

138 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

FromToDate <FrToDt> contains the following elements (see DatePeriod2 on page 145 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 146

ToDate <ToDt> [1..1] Date 146

1.4.2.46.2.6.11.8.4.2 Amount <Amt>

Presence: [1..1]
Definition: Underlying tax amount related to the specified period.
Impacted by: ✓C2 ActiveOrHistoricCurrency ✓, ✓C11 CurrencyAmount ✓
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

1.4.2.46.2.6.11.9 AdditionalInformation <AddtlInf>

Presence: [0..1]
Definition: Further details of the tax record.
Datatype: Max140Text on page 237

1.4.2.46.2.7 GarnishmentRemittance <GrnshmtRmt>

Presence: [0..1]
Definition: Provides remittance information about a payment for garnishment-related purposes.

139
Standards MX

GarnishmentRemittance <GrnshmtRmt> contains the following elements (see Garnishment3 on

page 193 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] 193

CodeOrProprietary <CdOrPrtry> [1..1] 193

{Or Code <Cd> [1..1] CodeSet 194

Or} Proprietary <Prtry> [1..1] Text 194

Issuer <Issr> [0..1] Text 194

Garnishee <Grnshee> [0..1] ± 194

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] ± 194

ReferenceNumber <RefNb> [0..1] Text 195

Date <Dt> [0..1] Date 195

RemittedAmount <RmtdAmt> [0..1] Amount 195

FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] Indicator 195

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] Indicator 195

1.4.2.46.2.8 AdditionalRemittanceInformation <AddtlRmtInf>

Presence: [0..3]
Definition: Additional information, in free text form, to complement the structured remittance information.
Datatype: Max140Text on page 237

1.4.2.47 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C42 SupplementaryDataRule
SupplementaryData <SplmtryData> contains the following elements (see SupplementaryData1 on
page 165 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 165

Envelope <Envlp> [1..1] (External 165

Schema)

140 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 MX pacs.008.001.10 FIToFICustomerCreditTransferV10

Constraints

• SupplementaryDataRule
This component may not be used without the explicit approval of a SEG and submission to the RA of
ISO 20022 compliant structure(s) to be used in the Envelope element.

1.4.3 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C42 SupplementaryDataRule
SupplementaryData <SplmtryData> contains the following elements (see SupplementaryData1 on
page 165 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 165

Envelope <Envlp> [1..1] (External 165

Schema)

Constraints

• SupplementaryDataRule
This component may not be used without the explicit approval of a SEG and submission to the RA of
ISO 20022 compliant structure(s) to be used in the Envelope element.

141
Standards MX

2 Message Items Types

2.1 MessageComponents
2.1.1 Account
2.1.1.1 CashAccountType2Choice
Definition: Nature or use of the account.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 142

Or} Proprietary <Prtry> [1..1] Text 142

2.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Account type, in a coded form.
Datatype: ExternalCashAccountType1Code on page 210

2.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Nature or use of the account in a proprietary form.
Datatype: Max35Text on page 238

2.1.1.2 GenericAccountIdentification1
Definition: Information related to a generic account identification.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 142

SchemeName <SchmeNm> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 143

Or} Proprietary <Prtry> [1..1] Text 143

Issuer <Issr> [0..1] Text 143

2.1.1.2.1 Identification <Id>

Presence: [1..1]
Definition: Identification assigned by an institution.
Datatype: Max34Text on page 238

142 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.1.2.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following AccountSchemeName1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 143

Or} Proprietary <Prtry> [1..1] Text 143

2.1.1.2.2.1 Code <Cd>

Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: ExternalAccountIdentification1Code on page 209

2.1.1.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: Max35Text on page 238

2.1.1.2.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: Max35Text on page 238

2.1.1.3 ProxyAccountIdentification1
Definition: Information related to a proxy identification of the account.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

Identification <Id> [1..1] Text 144

2.1.1.3.1 Type <Tp>

Presence: [0..1]
Definition: Type of the proxy identification.

143
Standards MX

Type <Tp> contains one of the following ProxyAccountType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 144

Or} Proprietary <Prtry> [1..1] Text 144

2.1.1.3.1.1 Code <Cd>

Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: ExternalProxyAccountType1Code on page 219

2.1.1.3.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: Max35Text on page 238

2.1.1.3.2 Identification <Id>

Presence: [1..1]
Definition: Identification used to indicate the account identification under another specified name.
Datatype: Max2048Text on page 237

2.1.2 Account Identification

2.1.2.1 AccountIdentification4Choice
Definition: Specifies the unique identification of an account as assigned by the account servicer.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or IBAN <IBAN> [1..1] IdentifierSet 144

Or} Other <Othr> [1..1] ± 144

2.1.2.1.1 IBAN <IBAN>

Presence: [1..1]
Definition: International Bank Account Number (IBAN) - identifier used internationally by financial
institutions to uniquely identify the account of a customer. Further specifications of the format and
content of the IBAN can be found in the standard ISO 13616 "Banking and related financial services -
International Bank Account Number (IBAN)" version 1997-10-01, or later revisions.
Datatype: IBAN2007Identifier on page 234

2.1.2.1.2 Other <Othr>

Presence: [1..1]
Definition: Unique identification of an account, as assigned by the account servicer, using an
identification scheme.

144 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Other <Othr> contains the following elements (see GenericAccountIdentification1 on page 142 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 142

SchemeName <SchmeNm> [0..1] 143

{Or Code <Cd> [1..1] CodeSet 143

Or} Proprietary <Prtry> [1..1] Text 143

Issuer <Issr> [0..1] Text 143

2.1.3 Charge
2.1.3.1 Charges7
Definition: Provides information on the charges related to the payment transaction.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount 145

Agent <Agt> [1..1] ± 145

2.1.3.1.1 Amount <Amt>

Presence: [1..1]
Definition: Transaction charges to be paid by the charge bearer.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.3.1.2 Agent <Agt>

Presence: [1..1]
Definition: Agent that takes the transaction charges or to which the transaction charges are due.
Agent <Agt> contains the following elements (see BranchAndFinancialInstitutionIdentification6 on
page 155 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

2.1.4 Date Period

2.1.4.1 DatePeriod2
Definition: Range of time defined by a start date and an end date.

145
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 146

ToDate <ToDt> [1..1] Date 146

2.1.4.1.1 FromDate <FrDt>

Presence: [1..1]
Definition: Start date of the range.
Datatype: ISODate on page 232

2.1.4.1.2 ToDate <ToDt>

Presence: [1..1]
Definition: End date of the range.
Datatype: ISODate on page 232

2.1.5 Direct Debit

2.1.5.1 CreditTransferMandateData1
Definition: Provides further details related to a credit transfer mandate signed between the creditor and
the debtor.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

MandateIdentification <MndtId> [0..1] Text 146

Type <Tp> [0..1] ± 147

DateOfSignature <DtOfSgntr> [0..1] Date 147

DateOfVerification <DtOfVrfctn> [0..1] DateTime 147

ElectronicSignature <ElctrncSgntr> [0..1] Binary 147

FirstPaymentDate <FrstPmtDt> [0..1] Date 147

FinalPaymentDate <FnlPmtDt> [0..1] Date 147

Frequency <Frqcy> [0..1] ± 148

Reason <Rsn> [0..1] 148

{Or Code <Cd> [1..1] CodeSet 148

Or} Proprietary <Prtry> [1..1] Text 148

2.1.5.1.1 MandateIdentification <MndtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the creditor, to unambiguously identify the mandate.
Datatype: Max35Text on page 238

146 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.5.1.2 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of mandate, such as paper, electronic or scheme.
Type <Tp> contains the following elements (see MandateTypeInformation2 on page 163 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ServiceLevel <SvcLvl> [0..1] 163

{Or Code <Cd> [1..1] CodeSet 163

Or} Proprietary <Prtry> [1..1] Text 163

LocalInstrument <LclInstrm> [0..1] 163

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

CategoryPurpose <CtgyPurp> [0..1] 164

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

Classification <Clssfctn> [0..1] ± 164

2.1.5.1.3 DateOfSignature <DtOfSgntr>

Presence: [0..1]
Definition: Date on which the credit transfer mandate has been signed by the debtor.
Datatype: ISODate on page 232

2.1.5.1.4 DateOfVerification <DtOfVrfctn>

Presence: [0..1]
Definition: Date on which the credit transfer mandate has been verified.
Datatype: ISODateTime on page 232

2.1.5.1.5 ElectronicSignature <ElctrncSgntr>

Presence: [0..1]
Definition: Additional security provisions, such as a digital signature, as provided by the debtor.
Datatype: Max10KBinary on page 202

2.1.5.1.6 FirstPaymentDate <FrstPmtDt>

Presence: [0..1]
Definition: Date of the first payment of a recurrent credit transfer as per the mandate.
Datatype: ISODate on page 232

2.1.5.1.7 FinalPaymentDate <FnlPmtDt>

Presence: [0..1]

147
Standards MX

Definition: Date of the final payment of a recurrent credit transfer as per the mandate.
Datatype: ISODate on page 232

2.1.5.1.8 Frequency <Frqcy>

Presence: [0..1]
Definition: Regularity with which credit transfer instructions are to be created and processed.
Frequency <Frqcy> contains one of the following elements (see Frequency36Choice on page 157
for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Type <Tp> [1..1] CodeSet 158

Or Period <Prd> [1..1] 158

Type <Tp> [1..1] CodeSet 158

CountPerPeriod <CntPerPrd> [1..1] Quantity 159

Or} PointInTime <PtInTm> [1..1] 159

Type <Tp> [1..1] CodeSet 159

PointInTime <PtInTm> [1..1] Text 160

2.1.5.1.9 Reason <Rsn>

Presence: [0..1]
Definition: Reason for the setup of the credit transfer mandate.

Usage:

The reason will allow the user to distinguish between different mandates for the same creditor.
Reason <Rsn> contains one of the following MandateSetupReason1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 148

Or} Proprietary <Prtry> [1..1] Text 148

2.1.5.1.9.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the mandate setup, as published in an external reason code list.
Datatype: ExternalMandateSetupReason1Code on page 217

2.1.5.1.9.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the mandate setup, in a proprietary form.
Datatype: Max70Text on page 238

148 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.6 Document
2.1.6.1 CreditorReferenceInformation2
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 149

CodeOrProprietary <CdOrPrtry> [1..1] 149

{Or Code <Cd> [1..1] CodeSet 149

Or} Proprietary <Prtry> [1..1] Text 150

Issuer <Issr> [0..1] Text 150

Reference <Ref> [0..1] Text 150

2.1.6.1.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of creditor reference.
Type <Tp> contains the following CreditorReferenceType2 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 149

{Or Code <Cd> [1..1] CodeSet 149

Or} Proprietary <Prtry> [1..1] Text 150

Issuer <Issr> [0..1] Text 150

2.1.6.1.1.1 CodeOrProprietary <CdOrPrtry>

Presence: [1..1]
Definition: Coded or proprietary format creditor reference type.
CodeOrProprietary <CdOrPrtry> contains one of the following CreditorReferenceType1Choice
elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 149

Or} Proprietary <Prtry> [1..1] Text 150

2.1.6.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Type of creditor reference, in a coded form.

149
Standards MX

Datatype: DocumentType3Code on page 207

CodeName Name Definition

RADM RemittanceAdviceMessage Document is a remittance advice sent

separately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment

instruction to which the current payment
instruction is related, for example, in a
cover scenario.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-

arranged foreign exchange transaction
to which the payment transaction refers.

DISP DispatchAdvice Document is a dispatch advice.

PUOR PurchaseOrder Document is a purchase order.

SCOR StructuredCommunicationReference Document is a structured communication

reference provided by the creditor to
identify the referred transaction.

2.1.6.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Creditor reference type, in a proprietary form.
Datatype: Max35Text on page 238

2.1.6.1.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the credit reference type.
Datatype: Max35Text on page 238

2.1.6.1.2 Reference <Ref>

Presence: [0..1]
Definition: Unique reference, as assigned by the creditor, to unambiguously refer to the payment
transaction.

Usage: If available, the initiating party should provide this reference in the structured remittance
information, to enable reconciliation by the creditor upon receipt of the amount of money.

If the business context requires the use of a creditor reference or a payment remit identification, and
only one identifier can be passed through the end-to-end chain, the creditor's reference or payment
remittance identification should be quoted in the end-to-end transaction identification.
Datatype: Max35Text on page 238

2.1.7 Financial Institution Identification

2.1.7.1 ClearingSystemMemberIdentification2
Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a member
of the clearing system.

150 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ClearingSystemIdentification <ClrSysId> [0..1] ± 151

MemberIdentification <MmbId> [1..1] Text 151

2.1.7.1.1 ClearingSystemIdentification <ClrSysId>

Presence: [0..1]
Definition: Specification of a pre-agreed offering between clearing agents or the channel through which
the payment instruction is processed.
ClearingSystemIdentification <ClrSysId> contains one of the following elements (see
ClearingSystemIdentification2Choice on page 198 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

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

Or} Proprietary <Prtry> [1..1] Text 198

2.1.7.1.2 MemberIdentification <MmbId>

Presence: [1..1]
Definition: Identification of a member of a clearing system.
Datatype: Max35Text on page 238

2.1.7.2 FinancialInstitutionIdentification18
Definition: Specifies the details to identify a financial institution.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

BICFI <BICFI> [0..1] IdentifierSet 151

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] ± 151

LEI <LEI> [0..1] IdentifierSet 152

Name <Nm> [0..1] Text 152

PostalAddress <PstlAdr> [0..1] ± 152

Other <Othr> [0..1] ± 153

2.1.7.2.1 BICFI <BICFI>

Presence: [0..1]
Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as described
in ISO 9362 "Banking - Banking telecommunication messages - Business identifier code (BIC)".
Datatype: BICFIDec2014Identifier on page 233

2.1.7.2.2 ClearingSystemMemberIdentification <ClrSysMmbId>

Presence: [0..1]

151
Standards MX

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

ClearingSystemMemberIdentification <ClrSysMmbId> contains the following elements (see
ClearingSystemMemberIdentification2 on page 150 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ClearingSystemIdentification <ClrSysId> [0..1] ± 151

MemberIdentification <MmbId> [1..1] Text 151

2.1.7.2.3 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identifier of the financial institution.
Datatype: LEIIdentifier on page 234

2.1.7.2.4 Name <Nm>

Presence: [0..1]
Definition: Name by which an agent is known and which is usually used to identify that agent.
Datatype: Max140Text on page 237

2.1.7.2.5 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

152 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

PostalAddress <PstlAdr> contains the following elements (see PostalAddress24 on page 186 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 186

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

Department <Dept> [0..1] Text 187

SubDepartment <SubDept> [0..1] Text 187

StreetName <StrtNm> [0..1] Text 188

BuildingNumber <BldgNb> [0..1] Text 188

BuildingName <BldgNm> [0..1] Text 188

Floor <Flr> [0..1] Text 188

PostBox <PstBx> [0..1] Text 188

Room <Room> [0..1] Text 188

PostCode <PstCd> [0..1] Text 188

TownName <TwnNm> [0..1] Text 188

TownLocationName <TwnLctnNm> [0..1] Text 189

DistrictName <DstrctNm> [0..1] Text 189

CountrySubDivision <CtrySubDvsn> [0..1] Text 189

Country <Ctry> [0..1] CodeSet 189

AddressLine <AdrLine> [0..7] Text 189

2.1.7.2.6 Other <Othr>

Presence: [0..1]
Definition: Unique identification of an agent, as assigned by an institution, using an identification
scheme.
Other <Othr> contains the following elements (see GenericFinancialIdentification1 on page 156 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 156

SchemeName <SchmeNm> [0..1] 157

{Or Code <Cd> [1..1] CodeSet 157

Or} Proprietary <Prtry> [1..1] Text 157

Issuer <Issr> [0..1] Text 157

153
Standards MX

2.1.7.3 BranchData3
Definition: Information that locates and identifies a specific branch of a financial institution.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] Text 154

LEI <LEI> [0..1] IdentifierSet 154

Name <Nm> [0..1] Text 154

PostalAddress <PstlAdr> [0..1] ± 154

2.1.7.3.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification of a branch of a financial institution.
Datatype: Max35Text on page 238

2.1.7.3.2 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identification for the branch of the financial institution.
Datatype: LEIIdentifier on page 234

2.1.7.3.3 Name <Nm>

Presence: [0..1]
Definition: Name by which an agent is known and which is usually used to identify that agent.
Datatype: Max140Text on page 237

2.1.7.3.4 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

154 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

PostalAddress <PstlAdr> contains the following elements (see PostalAddress24 on page 186 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 186

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

Department <Dept> [0..1] Text 187

SubDepartment <SubDept> [0..1] Text 187

StreetName <StrtNm> [0..1] Text 188

BuildingNumber <BldgNb> [0..1] Text 188

BuildingName <BldgNm> [0..1] Text 188

Floor <Flr> [0..1] Text 188

PostBox <PstBx> [0..1] Text 188

Room <Room> [0..1] Text 188

PostCode <PstCd> [0..1] Text 188

TownName <TwnNm> [0..1] Text 188

TownLocationName <TwnLctnNm> [0..1] Text 189

DistrictName <DstrctNm> [0..1] Text 189

CountrySubDivision <CtrySubDvsn> [0..1] Text 189

Country <Ctry> [0..1] CodeSet 189

AddressLine <AdrLine> [0..7] Text 189

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

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 155

BranchIdentification <BrnchId> [0..1] ± 156

2.1.7.4.1 FinancialInstitutionIdentification <FinInstnId>

Presence: [1..1]
Definition: Unique and unambiguous identification of a financial institution, as assigned under an
internationally recognised or proprietary identification scheme.

155
Standards MX

FinancialInstitutionIdentification <FinInstnId> contains the following elements (see

FinancialInstitutionIdentification18 on page 151 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

BICFI <BICFI> [0..1] IdentifierSet 151

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] ± 151

LEI <LEI> [0..1] IdentifierSet 152

Name <Nm> [0..1] Text 152

PostalAddress <PstlAdr> [0..1] ± 152

Other <Othr> [0..1] ± 153

2.1.7.4.2 BranchIdentification <BrnchId>

Presence: [0..1]
Definition: Identifies a specific branch of a financial institution.

Usage: This component should be used in case the identification information in the financial institution
component does not provide identification up to branch level.
BranchIdentification <BrnchId> contains the following elements (see BranchData3 on page 154 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] Text 154

LEI <LEI> [0..1] IdentifierSet 154

Name <Nm> [0..1] Text 154

PostalAddress <PstlAdr> [0..1] ± 154

2.1.7.5 GenericFinancialIdentification1
Definition: Information related to an identification of a financial institution.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 156

SchemeName <SchmeNm> [0..1] 157

{Or Code <Cd> [1..1] CodeSet 157

Or} Proprietary <Prtry> [1..1] Text 157

Issuer <Issr> [0..1] Text 157

2.1.7.5.1 Identification <Id>

Presence: [1..1]
Definition: Unique and unambiguous identification of a person.

156 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Datatype: Max35Text on page 238

2.1.7.5.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
FinancialIdentificationSchemeName1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 157

Or} Proprietary <Prtry> [1..1] Text 157

2.1.7.5.2.1 Code <Cd>

Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: ExternalFinancialInstitutionIdentification1Code on page 215

2.1.7.5.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: Max35Text on page 238

2.1.7.5.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: Max35Text on page 238

2.1.8 Frequency
2.1.8.1 Frequency36Choice
Definition: Choice of format for a frequency, for example, the frequency of payment.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Type <Tp> [1..1] CodeSet 158

Or Period <Prd> [1..1] 158

Type <Tp> [1..1] CodeSet 158

CountPerPeriod <CntPerPrd> [1..1] Quantity 159

Or} PointInTime <PtInTm> [1..1] 159

Type <Tp> [1..1] CodeSet 159

PointInTime <PtInTm> [1..1] Text 160

157
Standards MX

2.1.8.1.1 Type <Tp>

Presence: [1..1]
Definition: Specifies a frequency in terms of a specified period type.
Datatype: Frequency6Code on page 221

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

MNTH Monthly Event takes place every month or once a

month.

QURT Quarterly Event takes place every three months or

four times a year.

MIAN SemiAnnual Event takes place every six months or

two times a year.

WEEK Weekly Event takes place once a week.

DAIL Daily Event takes place every day.

ADHO Adhoc Event takes place on request or as

necessary.

INDA IntraDay Event takes place several times a day.

FRTN Fortnightly Event takes place every two weeks.

2.1.8.1.2 Period <Prd>

Presence: [1..1]
Definition: Specifies a frequency in terms of a count per period within a specified period type.
Period <Prd> contains the following FrequencyPeriod1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] CodeSet 158

CountPerPeriod <CntPerPrd> [1..1] Quantity 159

2.1.8.1.2.1 Type <Tp>

Presence: [1..1]
Definition: Period for which the number of instructions are to be created and processed.
Datatype: Frequency6Code on page 221

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

MNTH Monthly Event takes place every month or once a

month.

QURT Quarterly Event takes place every three months or

four times a year.

158 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

CodeName Name Definition

MIAN SemiAnnual Event takes place every six months or

two times a year.

WEEK Weekly Event takes place once a week.

DAIL Daily Event takes place every day.

ADHO Adhoc Event takes place on request or as

necessary.

INDA IntraDay Event takes place several times a day.

FRTN Fortnightly Event takes place every two weeks.

2.1.8.1.2.2 CountPerPeriod <CntPerPrd>

Presence: [1..1]
Definition: Number of instructions to be created and processed during the specified period.
Datatype: DecimalNumber on page 235

2.1.8.1.3 PointInTime <PtInTm>

Presence: [1..1]
Definition: Specifies a frequency in terms of an exact point in time or moment within a specified period
type.
PointInTime <PtInTm> contains the following FrequencyAndMoment1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] CodeSet 159

PointInTime <PtInTm> [1..1] Text 160

2.1.8.1.3.1 Type <Tp>

Presence: [1..1]
Definition: Period for which the number of instructions are to be created and processed.
Datatype: Frequency6Code on page 221

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

MNTH Monthly Event takes place every month or once a

month.

QURT Quarterly Event takes place every three months or

four times a year.

MIAN SemiAnnual Event takes place every six months or

two times a year.

WEEK Weekly Event takes place once a week.

DAIL Daily Event takes place every day.

159
Standards MX

CodeName Name Definition

ADHO Adhoc Event takes place on request or as

necessary.

INDA IntraDay Event takes place several times a day.

FRTN Fortnightly Event takes place every two weeks.

2.1.8.1.3.2 PointInTime <PtInTm>

Presence: [1..1]
Definition: Further information on the exact point in time the event should take place.
Datatype: Exact2NumericText on page 236

2.1.9 Identification Information

2.1.9.1 GenericIdentification30
Definition: Information related to an identification, for example, party identification or account
identification.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 160

Issuer <Issr> [1..1] Text 160

SchemeName <SchmeNm> [0..1] Text 160

2.1.9.1.1 Identification <Id>

Presence: [1..1]
Definition: Proprietary information, often a code, issued by the data source scheme issuer.
Datatype: Exact4AlphaNumericText on page 236

2.1.9.1.2 Issuer <Issr>

Presence: [1..1]
Definition: Entity that assigns the identification.
Datatype: Max35Text on page 238

2.1.9.1.3 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Short textual description of the scheme.
Datatype: Max35Text on page 238

2.1.9.2 PaymentIdentification13
Definition: Provides further means of referencing a payment transaction.

160 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionIdentification <InstrId> [0..1] Text 161

EndToEndIdentification <EndToEndId> [1..1] Text 161

TransactionIdentification <TxId> [0..1] Text 161

UETR <UETR> [0..1] IdentifierSet 162

ClearingSystemReference <ClrSysRef> [0..1] Text 162

Constraints

• TransactionIdentificationPresenceRule
TransactionIdentification or UETR must be present. Both may be present
Error handling:

– Error severity: Fatal

– Error Code: X00420

– Error Text: No transaction identification is present

2.1.9.2.1 InstructionIdentification <InstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by an instructing party for an instructed party, to
unambiguously identify the instruction.

Usage: The instruction identification is a point to point reference that can be used between the
instructing party and the instructed party to refer to the individual instruction. It can be included in
several messages related to the instruction.
Datatype: Max35Text on page 238

2.1.9.2.2 EndToEndIdentification <EndToEndId>

Presence: [1..1]
Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the
transaction. 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
transaction. 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
identification must be passed on throughout the entire end-to-end chain.
Datatype: Max35Text on page 238

2.1.9.2.3 TransactionIdentification <TxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the first instructing agent, to unambiguously identify the
transaction that is passed on, unchanged, throughout the entire interbank chain.

161
Standards MX

Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to
the transaction on the interbank level.

Usage: The instructing agent has to make sure that the transaction identification is unique for a pre-
agreed period.
Datatype: Max35Text on page 238

2.1.9.2.4 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: UUIDv4Identifier on page 234

2.1.9.2.5 ClearingSystemReference <ClrSysRef>

Presence: [0..1]
Definition: Unique reference, as assigned by a clearing system, to unambiguously identify the
instruction.
Datatype: Max35Text on page 238

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

Usage: This is used by the initiating party to provide information concerning the processing of the
payment. It is likely to trigger special processing by any of the agents involved in the payment chain.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 162

Or} Proprietary <Prtry> [1..1] Text 162

2.1.10.1.1 Code <Cd>

Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: MandateClassification1Code on page 224

CodeName Name Definition

FIXE Fixed Direct debit amount is fixed.

USGB UsageBased Direct debit amount is based on usage.

VARI Variable Direct debit amount is variable.

2.1.10.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.

162 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Datatype: Max35Text on page 238

2.1.10.2 MandateTypeInformation2
Definition: Set of elements used to further detail the information related to the type of payment.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ServiceLevel <SvcLvl> [0..1] 163

{Or Code <Cd> [1..1] CodeSet 163

Or} Proprietary <Prtry> [1..1] Text 163

LocalInstrument <LclInstrm> [0..1] 163

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

CategoryPurpose <CtgyPurp> [0..1] 164

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

Classification <Clssfctn> [0..1] ± 164

2.1.10.2.1 ServiceLevel <SvcLvl>

Presence: [0..1]
Definition: Agreement under which or rules under which the mandate resides.
ServiceLevel <SvcLvl> contains one of the following ServiceLevel8Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 163

Or} Proprietary <Prtry> [1..1] Text 163

2.1.10.2.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as published in an
external service level code list.
Datatype: ExternalServiceLevel1Code on page 220

2.1.10.2.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.
Datatype: Max35Text on page 238

2.1.10.2.2 LocalInstrument <LclInstrm>

Presence: [0..1]

163
Standards MX

Definition: User community specific instrument.

Usage: This element is used to specify a local instrument, local clearing option and/or further qualify the
service or service level.
LocalInstrument <LclInstrm> contains one of the following LocalInstrument2Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

2.1.10.2.2.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the local instrument, as published in an external local instrument code list.
Datatype: ExternalLocalInstrument1Code on page 216

2.1.10.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the local instrument, as a proprietary code.
Datatype: Max35Text on page 238

2.1.10.2.3 CategoryPurpose <CtgyPurp>

Presence: [0..1]
Definition: Specifies the high level purpose of the mandate based on a set of pre-defined categories.
CategoryPurpose <CtgyPurp> contains one of the following CategoryPurpose1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 164

Or} Proprietary <Prtry> [1..1] Text 164

2.1.10.2.3.1 Code <Cd>

Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: ExternalCategoryPurpose1Code on page 211

2.1.10.2.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: Max35Text on page 238

2.1.10.2.4 Classification <Clssfctn>

Presence: [0..1]
Definition: Type of direct debit instruction.

164 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Classification <Clssfctn> contains one of the following elements (see MandateClassification1Choice

on page 162 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 162

Or} Proprietary <Prtry> [1..1] Text 162

2.1.11 Miscellaneous
2.1.11.1 SupplementaryData1
Definition: Additional information that can not be captured in the structured fields and/or any other
specific block.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 165

Envelope <Envlp> [1..1] (External 165

Schema)

Constraints

• SupplementaryDataRule
This component may not be used without the explicit approval of a SEG and submission to the RA of
ISO 20022 compliant structure(s) to be used in the Envelope element.

2.1.11.1.1 PlaceAndName <PlcAndNm>

Presence: [0..1]
Definition: Unambiguous reference to the location where the supplementary data must be inserted in
the message instance.

In the case of XML, this is expressed by a valid XPath.

Datatype: Max350Text on page 238

2.1.11.1.2 Envelope <Envlp>

Presence: [1..1]
Definition: Technical element wrapping the supplementary data.
Type: (External Schema)
Technical component that contains the validated supplementary data information. This technical
envelope allows to segregate the supplementary data information from any other information.

2.1.11.2 Purpose2Choice
Definition: Specifies the underlying reason for the payment transaction.

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

165
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 166

Or} Proprietary <Prtry> [1..1] Text 166

2.1.11.2.1 Code <Cd>

Presence: [1..1]
Definition: Underlying reason for the payment transaction, as published in an external purpose code list.
Datatype: ExternalPurpose1Code on page 219

2.1.11.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Purpose, in a proprietary form.
Datatype: Max35Text on page 238

2.1.11.3 RemittanceAmount2
Definition: Nature of the amount and currency on a document referred to in the remittance section,
typically either the original amount due/payable or the amount actually remitted for the referenced
document.

166 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount 167

DiscountAppliedAmount <DscntApldAmt> [0..*] 167

Type <Tp> [0..1] 168

{Or Code <Cd> [1..1] CodeSet 168

Or} Proprietary <Prtry> [1..1] Text 168

Amount <Amt> [1..1] Amount 168

CreditNoteAmount <CdtNoteAmt> [0..1] Amount 168

TaxAmount <TaxAmt> [0..*] 168

Type <Tp> [0..1] 169

{Or Code <Cd> [1..1] CodeSet 169

Or} Proprietary <Prtry> [1..1] Text 169

Amount <Amt> [1..1] Amount 169

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 169

Amount <Amt> [1..1] Amount 170

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 170

Reason <Rsn> [0..1] Text 170

AdditionalInformation <AddtlInf> [0..1] Text 170

RemittedAmount <RmtdAmt> [0..1] Amount 170

2.1.11.3.1 DuePayableAmount <DuePyblAmt>

Presence: [0..1]
Definition: Amount specified is the exact amount due and payable to the creditor.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.11.3.2 DiscountAppliedAmount <DscntApldAmt>

Presence: [0..*]
Definition: Amount specified for the referred document is the amount of discount to be applied to the
amount due and payable to the creditor.

167
Standards MX

DiscountAppliedAmount <DscntApldAmt> contains the following DiscountAmountAndType1

elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 168

{Or Code <Cd> [1..1] CodeSet 168

Or} Proprietary <Prtry> [1..1] Text 168

Amount <Amt> [1..1] Amount 168

2.1.11.3.2.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.
Type <Tp> contains one of the following DiscountAmountType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 168

Or} Proprietary <Prtry> [1..1] Text 168

2.1.11.3.2.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: ExternalDiscountAmountType1Code on page 213

2.1.11.3.2.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: Max35Text on page 238

2.1.11.3.2.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.11.3.3 CreditNoteAmount <CdtNoteAmt>

Presence: [0..1]
Definition: Amount specified for the referred document is the amount of a credit note.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.11.3.4 TaxAmount <TaxAmt>

Presence: [0..*]
Definition: Quantity of cash resulting from the calculation of the tax.

168 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

TaxAmount <TaxAmt> contains the following TaxAmountAndType1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 169

{Or Code <Cd> [1..1] CodeSet 169

Or} Proprietary <Prtry> [1..1] Text 169

Amount <Amt> [1..1] Amount 169

2.1.11.3.4.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.
Type <Tp> contains one of the following TaxAmountType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 169

Or} Proprietary <Prtry> [1..1] Text 169

2.1.11.3.4.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: ExternalTaxAmountType1Code on page 221

2.1.11.3.4.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: Max35Text on page 238

2.1.11.3.4.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.11.3.5 AdjustmentAmountAndReason <AdjstmntAmtAndRsn>

Presence: [0..*]
Definition: Specifies detailed information on the amount and reason of the document adjustment.

169
Standards MX

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> contains the following

DocumentAdjustment1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount 170

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 170

Reason <Rsn> [0..1] Text 170

AdditionalInformation <AddtlInf> [0..1] Text 170

2.1.11.3.5.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money of the document adjustment.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.11.3.5.2 CreditDebitIndicator <CdtDbtInd>

Presence: [0..1]
Definition: Specifies whether the adjustment must be subtracted or added to the total amount.
Datatype: CreditDebitCode on page 206

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

2.1.11.3.5.3 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the adjustment.
Datatype: Max4Text on page 238

2.1.11.3.5.4 AdditionalInformation <AddtlInf>

Presence: [0..1]
Definition: Provides further details on the document adjustment.
Datatype: Max140Text on page 237

2.1.11.3.6 RemittedAmount <RmtdAmt>

Presence: [0..1]
Definition: Amount of money remitted for the referred document.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

170 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.12 Organisation Identification

2.1.12.1 OrganisationIdentification29
Definition: Unique and unambiguous way to identify an organisation.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AnyBIC <AnyBIC> [0..1] IdentifierSet 171

LEI <LEI> [0..1] IdentifierSet 171

Other <Othr> [0..*] 171

Identification <Id> [1..1] Text 172

SchemeName <SchmeNm> [0..1] 172

{Or Code <Cd> [1..1] CodeSet 172

Or} Proprietary <Prtry> [1..1] Text 172

Issuer <Issr> [0..1] Text 172

2.1.12.1.1 AnyBIC <AnyBIC>

Presence: [0..1]
Definition: Business identification code of the organisation.
Datatype: AnyBICDec2014Identifier on page 233

2.1.12.1.2 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identification as an alternate identification for a party.
Datatype: LEIIdentifier on page 234

2.1.12.1.3 Other <Othr>

Presence: [0..*]
Definition: Unique identification of an organisation, as assigned by an institution, using an identification
scheme.
Other <Othr> contains the following GenericOrganisationIdentification1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 172

SchemeName <SchmeNm> [0..1] 172

{Or Code <Cd> [1..1] CodeSet 172

Or} Proprietary <Prtry> [1..1] Text 172

Issuer <Issr> [0..1] Text 172

171
Standards MX

2.1.12.1.3.1 Identification <Id>

Presence: [1..1]
Definition: Identification assigned by an institution.
Datatype: Max35Text on page 238

2.1.12.1.3.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
OrganisationIdentificationSchemeName1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 172

Or} Proprietary <Prtry> [1..1] Text 172

2.1.12.1.3.2.1 Code <Cd>

Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: ExternalOrganisationIdentification1Code on page 217

2.1.12.1.3.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: Max35Text on page 238

2.1.12.1.3.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: Max35Text on page 238

2.1.13 Party Identification

2.1.13.1 PartyIdentification135
Definition: Specifies the identification of a person or an organisation.

172 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

2.1.13.1.1 Name <Nm>

Presence: [0..1]
Definition: Name by which a party is known and which is usually used to identify that party.
Datatype: Max140Text on page 237

2.1.13.1.2 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

173
Standards MX

PostalAddress <PstlAdr> contains the following elements (see PostalAddress24 on page 186 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 186

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

Department <Dept> [0..1] Text 187

SubDepartment <SubDept> [0..1] Text 187

StreetName <StrtNm> [0..1] Text 188

BuildingNumber <BldgNb> [0..1] Text 188

BuildingName <BldgNm> [0..1] Text 188

Floor <Flr> [0..1] Text 188

PostBox <PstBx> [0..1] Text 188

Room <Room> [0..1] Text 188

PostCode <PstCd> [0..1] Text 188

TownName <TwnNm> [0..1] Text 188

TownLocationName <TwnLctnNm> [0..1] Text 189

DistrictName <DstrctNm> [0..1] Text 189

CountrySubDivision <CtrySubDvsn> [0..1] Text 189

Country <Ctry> [0..1] CodeSet 189

AddressLine <AdrLine> [0..7] Text 189

2.1.13.1.3 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification of a party.
Identification <Id> contains one of the following elements (see Party38Choice on page 175 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or OrganisationIdentification <OrgId> [1..1] ± 175

Or} PrivateIdentification <PrvtId> [1..1] ± 176

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

174 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Datatype: CountryCode on page 206

2.1.13.1.5 ContactDetails <CtctDtls>

Presence: [0..1]
Definition: Set of elements used to indicate how to contact the party.
ContactDetails <CtctDtls> contains the following elements (see Contact4 on page 183 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

NamePrefix <NmPrfx> [0..1] CodeSet 183

Name <Nm> [0..1] Text 184

PhoneNumber <PhneNb> [0..1] Text 184

MobileNumber <MobNb> [0..1] Text 184

FaxNumber <FaxNb> [0..1] Text 184

EmailAddress <EmailAdr> [0..1] Text 184

EmailPurpose <EmailPurp> [0..1] Text 184

JobTitle <JobTitl> [0..1] Text 184

Responsibility <Rspnsblty> [0..1] Text 185

Department <Dept> [0..1] Text 185

Other <Othr> [0..*] 185

ChannelType <ChanlTp> [1..1] Text 185

Identification <Id> [0..1] Text 185

PreferredMethod <PrefrdMtd> [0..1] CodeSet 185

2.1.13.2 Party38Choice
Definition: Nature or use of the account.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or OrganisationIdentification <OrgId> [1..1] ± 175

Or} PrivateIdentification <PrvtId> [1..1] ± 176

2.1.13.2.1 OrganisationIdentification <OrgId>

Presence: [1..1]
Definition: Unique and unambiguous way to identify an organisation.

175
Standards MX

OrganisationIdentification <OrgId> contains the following elements (see OrganisationIdentification29

on page 171 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AnyBIC <AnyBIC> [0..1] IdentifierSet 171

LEI <LEI> [0..1] IdentifierSet 171

Other <Othr> [0..*] 171

Identification <Id> [1..1] Text 172

SchemeName <SchmeNm> [0..1] 172

{Or Code <Cd> [1..1] CodeSet 172

Or} Proprietary <Prtry> [1..1] Text 172

Issuer <Issr> [0..1] Text 172

2.1.13.2.2 PrivateIdentification <PrvtId>

Presence: [1..1]
Definition: Unique and unambiguous identification of a person, for example a passport.
PrivateIdentification <PrvtId> contains the following elements (see PersonIdentification13 on
page 180 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 181

BirthDate <BirthDt> [1..1] Date 181

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 181

CityOfBirth <CityOfBirth> [1..1] Text 181

CountryOfBirth <CtryOfBirth> [1..1] CodeSet 182

Other <Othr> [0..*] 182

Identification <Id> [1..1] Text 182

SchemeName <SchmeNm> [0..1] 182

{Or Code <Cd> [1..1] CodeSet 182

Or} Proprietary <Prtry> [1..1] Text 183

Issuer <Issr> [0..1] Text 183

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

176 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CLSTime <CLSTm> [0..1] Time 177

TillTime <TillTm> [0..1] Time 177

FromTime <FrTm> [0..1] Time 177

RejectTime <RjctTm> [0..1] Time 177

2.1.14.1.1 CLSTime <CLSTm>

Presence: [0..1]
Definition: Time by which the amount of money must be credited, with confirmation, to the CLS Bank's
account at the central bank.

Usage: Time must be expressed in Central European Time (CET).

Datatype: ISOTime on page 239

2.1.14.1.2 TillTime <TillTm>

Presence: [0..1]
Definition: Time until when the payment may be settled.
Datatype: ISOTime on page 239

2.1.14.1.3 FromTime <FrTm>

Presence: [0..1]
Definition: Time as from when the payment may be settled.
Datatype: ISOTime on page 239

2.1.14.1.4 RejectTime <RjctTm>

Presence: [0..1]
Definition: Time by when the payment must be settled to avoid rejection.
Datatype: ISOTime on page 239

2.1.14.2 InstructionForCreditorAgent3
Definition: Further information related to the processing of the payment instruction that may need
to be acted upon by the creditor's agent. The instruction may relate to a level of service, or may be
an instruction that has to be executed by the creditor's agent, or may be information required by the
creditor's agent.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 177

InstructionInformation <InstrInf> [0..1] Text 178

2.1.14.2.1 Code <Cd>

Presence: [0..1]

177
Standards MX

Definition: Coded information related to the processing of the payment instruction, provided by the
initiating party, and intended for the creditor's agent.
Datatype: ExternalCreditorAgentInstruction1Code on page 213

2.1.14.2.2 InstructionInformation <InstrInf>

Presence: [0..1]
Definition: Further information complementing the coded instruction or instruction to the creditor's agent
that is bilaterally agreed or specific to a user community.
Datatype: Max140Text on page 237

2.1.15 Payment Type

2.1.15.1 PaymentTypeInformation28
Definition: Provides further details of the type of payment.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 178

ClearingChannel <ClrChanl> [0..1] CodeSet 178

ServiceLevel <SvcLvl> [0..*] 179

{Or Code <Cd> [1..1] CodeSet 179

Or} Proprietary <Prtry> [1..1] Text 179

LocalInstrument <LclInstrm> [0..1] 179

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

Or} Proprietary <Prtry> [1..1] Text 180

CategoryPurpose <CtgyPurp> [0..1] 180

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

Or} Proprietary <Prtry> [1..1] Text 180

2.1.15.1.1 InstructionPriority <InstrPrty>

Presence: [0..1]
Definition: Indicator of the urgency or order of importance that the instructing party would like the
instructed party to apply to the processing of the instruction.
Datatype: Priority2Code on page 226

CodeName Name Definition

HIGH High Priority level is high.

NORM Normal Priority level is normal.

2.1.15.1.2 ClearingChannel <ClrChanl>

Presence: [0..1]

178 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Definition: Specifies the clearing channel to be used to process the payment instruction.
Datatype: ClearingChannel2Code on page 205

CodeName Name Definition

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross

settlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net

settlement system.

MPNS MassPaymentNetSystem Clearing channel is a mass payment net

settlement system.

BOOK BookTransfer Payment through internal book transfer.

2.1.15.1.3 ServiceLevel <SvcLvl>

Presence: [0..*]
Definition: Agreement under which or rules under which the transaction should be processed.
ServiceLevel <SvcLvl> contains one of the following ServiceLevel8Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 179

Or} Proprietary <Prtry> [1..1] Text 179

2.1.15.1.3.1 Code <Cd>

Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as published in an
external service level code list.
Datatype: ExternalServiceLevel1Code on page 220

2.1.15.1.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies a pre-agreed service or level of service between the parties, as a proprietary code.
Datatype: Max35Text on page 238

2.1.15.1.4 LocalInstrument <LclInstrm>

Presence: [0..1]
Definition: User community specific instrument.

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

179
Standards MX

LocalInstrument <LclInstrm> contains one of the following LocalInstrument2Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

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

Or} Proprietary <Prtry> [1..1] Text 180

2.1.15.1.4.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the local instrument, as published in an external local instrument code list.
Datatype: ExternalLocalInstrument1Code on page 216

2.1.15.1.4.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the local instrument, as a proprietary code.
Datatype: Max35Text on page 238

2.1.15.1.5 CategoryPurpose <CtgyPurp>

Presence: [0..1]
Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.

Usage: This is used by the initiating party to provide information concerning the processing of the
payment. It is likely to trigger special processing by any of the agents involved in the payment chain.
CategoryPurpose <CtgyPurp> contains one of the following CategoryPurpose1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

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

Or} Proprietary <Prtry> [1..1] Text 180

2.1.15.1.5.1 Code <Cd>

Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: ExternalCategoryPurpose1Code on page 211

2.1.15.1.5.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: Max35Text on page 238

2.1.16 Person Identification

2.1.16.1 PersonIdentification13
Definition: Unique and unambiguous way to identify a person.

180 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 181

BirthDate <BirthDt> [1..1] Date 181

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 181

CityOfBirth <CityOfBirth> [1..1] Text 181

CountryOfBirth <CtryOfBirth> [1..1] CodeSet 182

Other <Othr> [0..*] 182

Identification <Id> [1..1] Text 182

SchemeName <SchmeNm> [0..1] 182

{Or Code <Cd> [1..1] CodeSet 182

Or} Proprietary <Prtry> [1..1] Text 183

Issuer <Issr> [0..1] Text 183

2.1.16.1.1 DateAndPlaceOfBirth <DtAndPlcOfBirth>

Presence: [0..1]
Definition: Date and place of birth of a person.
DateAndPlaceOfBirth <DtAndPlcOfBirth> contains the following DateAndPlaceOfBirth1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

BirthDate <BirthDt> [1..1] Date 181

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 181

CityOfBirth <CityOfBirth> [1..1] Text 181

CountryOfBirth <CtryOfBirth> [1..1] CodeSet 182

2.1.16.1.1.1 BirthDate <BirthDt>

Presence: [1..1]
Definition: Date on which a person is born.
Datatype: ISODate on page 232

2.1.16.1.1.2 ProvinceOfBirth <PrvcOfBirth>

Presence: [0..1]
Definition: Province where a person was born.
Datatype: Max35Text on page 238

2.1.16.1.1.3 CityOfBirth <CityOfBirth>

Presence: [1..1]
Definition: City where a person was born.

181
Standards MX

Datatype: Max35Text on page 238

2.1.16.1.1.4 CountryOfBirth <CtryOfBirth>

Presence: [1..1]
Definition: Country where a person was born.
Datatype: CountryCode on page 206

2.1.16.1.2 Other <Othr>

Presence: [0..*]
Definition: Unique identification of a person, as assigned by an institution, using an identification
scheme.
Other <Othr> contains the following GenericPersonIdentification1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 182

SchemeName <SchmeNm> [0..1] 182

{Or Code <Cd> [1..1] CodeSet 182

Or} Proprietary <Prtry> [1..1] Text 183

Issuer <Issr> [0..1] Text 183

2.1.16.1.2.1 Identification <Id>

Presence: [1..1]
Definition: Unique and unambiguous identification of a person.
Datatype: Max35Text on page 238

2.1.16.1.2.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
PersonIdentificationSchemeName1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 182

Or} Proprietary <Prtry> [1..1] Text 183

2.1.16.1.2.2.1 Code <Cd>

Presence: [1..1]
Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: ExternalPersonIdentification1Code on page 218

182 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.16.1.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: Max35Text on page 238

2.1.16.1.2.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: Max35Text on page 238

2.1.16.2 Contact4
Definition: Specifies the details of the contact person.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

NamePrefix <NmPrfx> [0..1] CodeSet 183

Name <Nm> [0..1] Text 184

PhoneNumber <PhneNb> [0..1] Text 184

MobileNumber <MobNb> [0..1] Text 184

FaxNumber <FaxNb> [0..1] Text 184

EmailAddress <EmailAdr> [0..1] Text 184

EmailPurpose <EmailPurp> [0..1] Text 184

JobTitle <JobTitl> [0..1] Text 184

Responsibility <Rspnsblty> [0..1] Text 185

Department <Dept> [0..1] Text 185

Other <Othr> [0..*] 185

ChannelType <ChanlTp> [1..1] Text 185

Identification <Id> [0..1] Text 185

PreferredMethod <PrefrdMtd> [0..1] CodeSet 185

2.1.16.2.1 NamePrefix <NmPrfx>

Presence: [0..1]
Definition: Specifies the terms used to formally address a person.
Datatype: NamePrefix2Code on page 224

CodeName Name Definition

DOCT Doctor Title of the person is Doctor or Dr.

MADM Madam Title of the person is Madam.

MISS Miss Title of the person is Miss.

183
Standards MX

CodeName Name Definition

MIST Mister Title of the person is Mister or Mr.

MIKS GenderNeutral Title of the person is gender neutral

(Mx).

2.1.16.2.2 Name <Nm>

Presence: [0..1]
Definition: Name by which a party is known and which is usually used to identify that party.
Datatype: Max140Text on page 237

2.1.16.2.3 PhoneNumber <PhneNb>

Presence: [0..1]
Definition: Collection of information that identifies a phone number, as defined by telecom services.
Datatype: PhoneNumber on page 239

2.1.16.2.4 MobileNumber <MobNb>

Presence: [0..1]
Definition: Collection of information that identifies a mobile phone number, as defined by telecom
services.
Datatype: PhoneNumber on page 239

2.1.16.2.5 FaxNumber <FaxNb>

Presence: [0..1]
Definition: Collection of information that identifies a FAX number, as defined by telecom services.
Datatype: PhoneNumber on page 239

2.1.16.2.6 EmailAddress <EmailAdr>

Presence: [0..1]
Definition: Address for electronic mail (e-mail).
Datatype: Max2048Text on page 237

2.1.16.2.7 EmailPurpose <EmailPurp>

Presence: [0..1]
Definition: Purpose for which an email address may be used.
Datatype: Max35Text on page 238

2.1.16.2.8 JobTitle <JobTitl>

Presence: [0..1]
Definition: Title of the function.
Datatype: Max35Text on page 238

184 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.16.2.9 Responsibility <Rspnsblty>

Presence: [0..1]
Definition: Role of a person in an organisation.
Datatype: Max35Text on page 238

2.1.16.2.10 Department <Dept>

Presence: [0..1]
Definition: Identification of a division of a large organisation or building.
Datatype: Max70Text on page 238

2.1.16.2.11 Other <Othr>

Presence: [0..*]
Definition: Contact details in another form.
Other <Othr> contains the following OtherContact1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ChannelType <ChanlTp> [1..1] Text 185

Identification <Id> [0..1] Text 185

2.1.16.2.11.1 ChannelType <ChanlTp>

Presence: [1..1]
Definition: Method used to contact the financial institution's contact for the specific tax region.
Datatype: Max4Text on page 238

2.1.16.2.11.2 Identification <Id>

Presence: [0..1]
Definition: Communication value such as phone number or email address.
Datatype: Max128Text on page 237

2.1.16.2.12 PreferredMethod <PrefrdMtd>

Presence: [0..1]
Definition: Preferred method used to reach the contact.
Datatype: PreferredContactMethod1Code on page 225

CodeName Name Definition

LETT Letter Preferred method used to reach the

contact is per letter.

MAIL Email Preferred method used to reach the

contact is per email.

PHON Phone Preferred method used to reach the

contact is per phone.

185
Standards MX

CodeName Name Definition

FAXX Fax Preferred method used to reach the

contact is per fax.

CELL MobileOrCellPhone Preferred method used to reach the

contact is per mobile or cell phone.

2.1.17 Postal Address

2.1.17.1 PostalAddress24
Definition: Information that locates and identifies a specific address, as defined by postal services.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 186

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

Department <Dept> [0..1] Text 187

SubDepartment <SubDept> [0..1] Text 187

StreetName <StrtNm> [0..1] Text 188

BuildingNumber <BldgNb> [0..1] Text 188

BuildingName <BldgNm> [0..1] Text 188

Floor <Flr> [0..1] Text 188

PostBox <PstBx> [0..1] Text 188

Room <Room> [0..1] Text 188

PostCode <PstCd> [0..1] Text 188

TownName <TwnNm> [0..1] Text 188

TownLocationName <TwnLctnNm> [0..1] Text 189

DistrictName <DstrctNm> [0..1] Text 189

CountrySubDivision <CtrySubDvsn> [0..1] Text 189

Country <Ctry> [0..1] CodeSet 189

AddressLine <AdrLine> [0..7] Text 189

2.1.17.1.1 AddressType <AdrTp>

Presence: [0..1]
Definition: Identifies the nature of the postal address.

186 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

AddressType <AdrTp> contains one of the following AddressType3Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

2.1.17.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Type of address expressed as a code.
Datatype: AddressType2Code on page 203

CodeName Name Definition

ADDR Postal Address is the complete postal address.

PBOX POBox Address is a postal office (PO) box.

HOME Residential Address is the home address.

BIZZ Business Address is the business address.

MLTO MailTo Address is the address to which mail is

sent.

DLVY DeliveryTo Address is the address to which delivery

is to take place.

2.1.17.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Type of address expressed as a proprietary code.
Proprietary <Prtry> contains the following elements (see GenericIdentification30 on page 160 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 160

Issuer <Issr> [1..1] Text 160

SchemeName <SchmeNm> [0..1] Text 160

2.1.17.1.2 Department <Dept>

Presence: [0..1]
Definition: Identification of a division of a large organisation or building.
Datatype: Max70Text on page 238

2.1.17.1.3 SubDepartment <SubDept>

Presence: [0..1]
Definition: Identification of a sub-division of a large organisation or building.
Datatype: Max70Text on page 238

187
Standards MX

2.1.17.1.4 StreetName <StrtNm>

Presence: [0..1]
Definition: Name of a street or thoroughfare.
Datatype: Max70Text on page 238

2.1.17.1.5 BuildingNumber <BldgNb>

Presence: [0..1]
Definition: Number that identifies the position of a building on a street.
Datatype: Max16Text on page 237

2.1.17.1.6 BuildingName <BldgNm>

Presence: [0..1]
Definition: Name of the building or house.
Datatype: Max35Text on page 238

2.1.17.1.7 Floor <Flr>

Presence: [0..1]
Definition: Floor or storey within a building.
Datatype: Max70Text on page 238

2.1.17.1.8 PostBox <PstBx>

Presence: [0..1]
Definition: Numbered box in a post office, assigned to a person or organisation, where letters are kept
until called for.
Datatype: Max16Text on page 237

2.1.17.1.9 Room <Room>

Presence: [0..1]
Definition: Building room number.
Datatype: Max70Text on page 238

2.1.17.1.10 PostCode <PstCd>

Presence: [0..1]
Definition: Identifier consisting of a group of letters and/or numbers that is added to a postal address to
assist the sorting of mail.
Datatype: Max16Text on page 237

2.1.17.1.11 TownName <TwnNm>

Presence: [0..1]
Definition: Name of a built-up area, with defined boundaries, and a local government.
Datatype: Max35Text on page 238

188 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.17.1.12 TownLocationName <TwnLctnNm>

Presence: [0..1]
Definition: Specific location name within the town.
Datatype: Max35Text on page 238

2.1.17.1.13 DistrictName <DstrctNm>

Presence: [0..1]
Definition: Identifies a subdivision within a country sub-division.
Datatype: Max35Text on page 238

2.1.17.1.14 CountrySubDivision <CtrySubDvsn>

Presence: [0..1]
Definition: Identifies a subdivision of a country such as state, region, county.
Datatype: Max35Text on page 238

2.1.17.1.15 Country <Ctry>

Presence: [0..1]
Definition: Nation with its own government.
Datatype: CountryCode on page 206

2.1.17.1.16 AddressLine <AdrLine>

Presence: [0..7]
Definition: Information that locates and identifies a specific address, as defined by postal services,
presented in free format text.
Datatype: Max70Text on page 238

2.1.18 Regulatory Reporting

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

189
Standards MX

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebitCreditReportingIndicator <DbtCdtRptgInd> [0..1] CodeSet 190

Authority <Authrty> [0..1] 190

Name <Nm> [0..1] Text 190

Country <Ctry> [0..1] CodeSet 191

Details <Dtls> [0..*] 191

Type <Tp> [0..1] Text 191

Date <Dt> [0..1] Date 191

Country <Ctry> [0..1] CodeSet 191

Code <Cd> [0..1] Text 191

Amount <Amt> [0..1] Amount 192

Information <Inf> [0..*] Text 192

2.1.18.1.1 DebitCreditReportingIndicator <DbtCdtRptgInd>

Presence: [0..1]
Definition: Identifies whether the regulatory reporting information applies to the debit side, to the credit
side or to both debit and credit sides of the transaction.
Datatype: RegulatoryReportingType1Code on page 227

CodeName Name Definition

CRED Credit Regulatory information applies to the

credit side.

DEBT Debit Regulatory information applies to the

debit side.

BOTH Both Regulatory information applies to both

credit and debit sides.

2.1.18.1.2 Authority <Authrty>

Presence: [0..1]
Definition: Entity requiring the regulatory reporting information.
Authority <Authrty> contains the following RegulatoryAuthority2 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 190

Country <Ctry> [0..1] CodeSet 191

2.1.18.1.2.1 Name <Nm>

Presence: [0..1]
Definition: Name of the entity requiring the regulatory reporting information.

190 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Datatype: Max140Text on page 237

2.1.18.1.2.2 Country <Ctry>

Presence: [0..1]
Definition: Country of the entity that requires the regulatory reporting information.
Datatype: CountryCode on page 206

2.1.18.1.3 Details <Dtls>

Presence: [0..*]
Definition: Set of elements used to provide details on the regulatory reporting information.
Details <Dtls> contains the following StructuredRegulatoryReporting3 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] Text 191

Date <Dt> [0..1] Date 191

Country <Ctry> [0..1] CodeSet 191

Code <Cd> [0..1] Text 191

Amount <Amt> [0..1] Amount 192

Information <Inf> [0..*] Text 192

2.1.18.1.3.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the information supplied in the regulatory reporting details.
Datatype: Max35Text on page 238

2.1.18.1.3.2 Date <Dt>

Presence: [0..1]
Definition: Date related to the specified type of regulatory reporting details.
Datatype: ISODate on page 232

2.1.18.1.3.3 Country <Ctry>

Presence: [0..1]
Definition: Country related to the specified type of regulatory reporting details.
Datatype: CountryCode on page 206

2.1.18.1.3.4 Code <Cd>

Presence: [0..1]
Definition: Specifies the nature, purpose, and reason for the transaction to be reported for regulatory
and statutory requirements in a coded form.
Datatype: Max10Text on page 236

191
Standards MX

2.1.18.1.3.5 Amount <Amt>

Presence: [0..1]
Definition: Amount of money to be reported for regulatory and statutory requirements.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.18.1.3.6 Information <Inf>

Presence: [0..*]
Definition: Additional details that cater for specific domestic regulatory requirements.
Datatype: Max35Text on page 238

2.1.19 Remittance
2.1.19.1 RemittanceLocation7
Definition: Provides information on the remittance advice.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

RemittanceIdentification <RmtId> [0..1] Text 192

RemittanceLocationDetails <RmtLctnDtls> [0..*] ± 192

2.1.19.1.1 RemittanceIdentification <RmtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the
remittance information sent separately from the payment instruction, such as a remittance advice.
Datatype: Max35Text on page 238

2.1.19.1.2 RemittanceLocationDetails <RmtLctnDtls>

Presence: [0..*]
Definition: Set of elements used to provide information on the location and/or delivery of the remittance
information.
RemittanceLocationDetails <RmtLctnDtls> contains the following elements (see
RemittanceLocationData1 on page 196 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Method <Mtd> [1..1] CodeSet 196

ElectronicAddress <ElctrncAdr> [0..1] Text 196

PostalAddress <PstlAdr> [0..1] 196

Name <Nm> [1..1] Text 197

Address <Adr> [1..1] ± 197

192 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.19.2 Garnishment3
Definition: Provides remittance information about a payment for garnishment-related purposes.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] 193

CodeOrProprietary <CdOrPrtry> [1..1] 193

{Or Code <Cd> [1..1] CodeSet 194

Or} Proprietary <Prtry> [1..1] Text 194

Issuer <Issr> [0..1] Text 194

Garnishee <Grnshee> [0..1] ± 194

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] ± 194

ReferenceNumber <RefNb> [0..1] Text 195

Date <Dt> [0..1] Date 195

RemittedAmount <RmtdAmt> [0..1] Amount 195

FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] Indicator 195

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] Indicator 195

2.1.19.2.1 Type <Tp>

Presence: [1..1]
Definition: Specifies the type of garnishment.
Type <Tp> contains the following GarnishmentType1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 193

{Or Code <Cd> [1..1] CodeSet 194

Or} Proprietary <Prtry> [1..1] Text 194

Issuer <Issr> [0..1] Text 194

2.1.19.2.1.1 CodeOrProprietary <CdOrPrtry>

Presence: [1..1]
Definition: Provides the type details of the garnishment.
CodeOrProprietary <CdOrPrtry> contains one of the following GarnishmentType1Choice elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 194

Or} Proprietary <Prtry> [1..1] Text 194

193
Standards MX

2.1.19.2.1.1.1 Code <Cd>

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 215

2.1.19.2.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Proprietary identification of the type of garnishment.
Datatype: Max35Text on page 238

2.1.19.2.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Identification of the issuer of the garnishment type.
Datatype: Max35Text on page 238

2.1.19.2.2 Garnishee <Grnshee>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor, in this case, to the
garnisher.
Garnishee <Grnshee> contains the following elements (see PartyIdentification135 on page 172 for
details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

2.1.19.2.3 GarnishmentAdministrator <GrnshmtAdmstr>

Presence: [0..1]
Definition: Party on the credit side of the transaction who administers the garnishment on behalf of the
ultimate beneficiary.

194 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

GarnishmentAdministrator <GrnshmtAdmstr> contains the following elements (see

PartyIdentification135 on page 172 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 173

PostalAddress <PstlAdr> [0..1] ± 173

Identification <Id> [0..1] ± 174

CountryOfResidence <CtryOfRes> [0..1] CodeSet 174

ContactDetails <CtctDtls> [0..1] ± 175

2.1.19.2.4 ReferenceNumber <RefNb>

Presence: [0..1]
Definition: Reference information that is specific to the agency receiving the garnishment.
Datatype: Max140Text on page 237

2.1.19.2.5 Date <Dt>

Presence: [0..1]
Definition: Date of payment which garnishment was taken from.
Datatype: ISODate on page 232

2.1.19.2.6 RemittedAmount <RmtdAmt>

Presence: [0..1]
Definition: Amount of money remitted for the referred document.
Datatype: ActiveOrHistoricCurrencyAndAmount on page 201

2.1.19.2.7 FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd>

Presence: [0..1]
Definition: Indicates if the person to whom the garnishment applies (that is, the ultimate debtor) has
family medical insurance coverage available.
Datatype: One of the following values must be used (see TrueFalseIndicator on page 235):

• Meaning When True: True

• Meaning When False: False

2.1.19.2.8 EmployeeTerminationIndicator <MplyeeTermntnInd>

Presence: [0..1]
Definition: Indicates if the employment of the person to whom the garnishment applies (that is, the
ultimate debtor) has been terminated.
Datatype: One of the following values must be used (see TrueFalseIndicator on page 235):

• Meaning When True: True

• Meaning When False: False

195
Standards MX

2.1.19.3 RemittanceLocationData1
Definition: Provides additional details on the remittance advice.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Method <Mtd> [1..1] CodeSet 196

ElectronicAddress <ElctrncAdr> [0..1] Text 196

PostalAddress <PstlAdr> [0..1] 196

Name <Nm> [1..1] Text 197

Address <Adr> [1..1] ± 197

2.1.19.3.1 Method <Mtd>

Presence: [1..1]
Definition: Method used to deliver the remittance advice information.
Datatype: RemittanceLocationMethod2Code on page 228

CodeName Name Definition

FAXI Fax Remittance advice information must be

faxed.

EDIC ElectronicDataInterchange Remittance advice information must be

sent through Electronic Data Interchange
(EDI).

URID UniformResourceIdentifier Remittance advice information needs

to be sent to a Uniform Resource
Identifier (URI). URI is a compact string
of characters that uniquely identify an
abstract or physical resource. URI's
are the super-set of identifiers, such as
URLs, email addresses, ftp sites, etc,
and as such, provide the syntax for all of
the identification schemes.

EMAL EMail Remittance advice information must be

sent through e-mail.

POST Post Remittance advice information must be

sent through postal services.

SMSM SMS Remittance advice information must

be sent through by phone as a short
message service (SMS).

2.1.19.3.2 ElectronicAddress <ElctrncAdr>

Presence: [0..1]
Definition: Electronic address to which an agent is to send the remittance information.
Datatype: Max2048Text on page 237

2.1.19.3.3 PostalAddress <PstlAdr>

Presence: [0..1]

196 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

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

PostalAddress <PstlAdr> contains the following NameAndAddress16 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [1..1] Text 197

Address <Adr> [1..1] ± 197

2.1.19.3.3.1 Name <Nm>

Presence: [1..1]
Definition: Name by which a party is known and is usually used to identify that party.
Datatype: Max140Text on page 237

2.1.19.3.3.2 Address <Adr>

Presence: [1..1]
Definition: Postal address of a party.
Address <Adr> contains the following elements (see PostalAddress24 on page 186 for details)

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 186

{Or Code <Cd> [1..1] CodeSet 187

Or} Proprietary <Prtry> [1..1] ± 187

Department <Dept> [0..1] Text 187

SubDepartment <SubDept> [0..1] Text 187

StreetName <StrtNm> [0..1] Text 188

BuildingNumber <BldgNb> [0..1] Text 188

BuildingName <BldgNm> [0..1] Text 188

Floor <Flr> [0..1] Text 188

PostBox <PstBx> [0..1] Text 188

Room <Room> [0..1] Text 188

PostCode <PstCd> [0..1] Text 188

TownName <TwnNm> [0..1] Text 188

TownLocationName <TwnLctnNm> [0..1] Text 189

DistrictName <DstrctNm> [0..1] Text 189

CountrySubDivision <CtrySubDvsn> [0..1] Text 189

Country <Ctry> [0..1] CodeSet 189

AddressLine <AdrLine> [0..7] Text 189

197
Standards MX

2.1.20 System Identification

2.1.20.1 ClearingSystemIdentification2Choice
Definition: Choice of a clearing system identifier.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

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

Or} Proprietary <Prtry> [1..1] Text 198

2.1.20.1.1 Code <Cd>

Presence: [1..1]
Definition: Identification of a clearing system, in a coded form as published in an external list.
Datatype: ExternalClearingSystemIdentification1Code on page 212

2.1.20.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Identification code for a clearing system, that has not yet been identified in the list of clearing
systems.
Datatype: Max35Text on page 238

2.1.21 Tax
2.1.21.1 TaxParty1
Definition: Details about the entity involved in the tax paid or to be paid.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 198

RegistrationIdentification <RegnId> [0..1] Text 198

TaxType <TaxTp> [0..1] Text 199

2.1.21.1.1 TaxIdentification <TaxId>

Presence: [0..1]
Definition: Tax identification number of the creditor.
Datatype: Max35Text on page 238

2.1.21.1.2 RegistrationIdentification <RegnId>

Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: Max35Text on page 238

198 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.1.21.1.3 TaxType <TaxTp>

Presence: [0..1]
Definition: Type of tax payer.
Datatype: Max35Text on page 238

2.1.21.2 TaxParty2
Definition: Details about the entity involved in the tax paid or to be paid.

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 199

RegistrationIdentification <RegnId> [0..1] Text 199

TaxType <TaxTp> [0..1] Text 199

Authorisation <Authstn> [0..1] 199

Title <Titl> [0..1] Text 200

Name <Nm> [0..1] Text 200

2.1.21.2.1 TaxIdentification <TaxId>

Presence: [0..1]
Definition: Tax identification number of the debtor.
Datatype: Max35Text on page 238

2.1.21.2.2 RegistrationIdentification <RegnId>

Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: Max35Text on page 238

2.1.21.2.3 TaxType <TaxTp>

Presence: [0..1]
Definition: Type of tax payer.
Datatype: Max35Text on page 238

2.1.21.2.4 Authorisation <Authstn>

Presence: [0..1]
Definition: Details of the authorised tax paying party.
Authorisation <Authstn> contains the following TaxAuthorisation1 elements

Index Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Title <Titl> [0..1] Text 200

Name <Nm> [0..1] Text 200

199
Standards MX

2.1.21.2.4.1 Title <Titl>

Presence: [0..1]
Definition: Title or position of debtor or the debtor's authorised representative.
Datatype: Max35Text on page 238

2.1.21.2.4.2 Name <Nm>

Presence: [0..1]
Definition: Name of the debtor or the debtor's authorised representative.
Datatype: Max140Text on page 237

2.2 Message Datatypes

2.2.1 Amount
2.2.1.1 ActiveCurrencyAndAmount
Definition: A number of monetary units specified in an active currency where the unit of currency is
explicit and compliant with ISO 4217.
Type: Amount
This data type contains the following XML attribute:

Name Attribute XML Name Datatype

Currency Ccy ActiveCurrencyCode on page 202

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Constraints

• ActiveCurrency
The currency code must be a valid active currency code, not yet withdrawn on the day the message
containing the currency is exchanged. Valid active currency codes are registered with the ISO 4217
Maintenance Agency, consist of three (3) contiguous letters, and are not yet withdrawn on the day
the message containing the Currency is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00005

– Error Text: Invalid currency code

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

200 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Note: The decimal separator is a dot.

Error handling:

– Error severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

2.2.1.2 ActiveOrHistoricCurrencyAndAmount
Definition: A number of monetary units specified in an active or a historic currency where the unit of
currency is explicit and compliant with ISO 4217.
Type: Amount
This data type contains the following XML attribute:

Name Attribute XML Name Datatype

Currency Ccy ActiveOrHistoricCurrencyCode on page 202

Format

minInclusive 0

totalDigits 18

fractionDigits 5

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

• 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 severity: Fatal

– Error Code: D00007

– Error Text: Invalid currency code or too many decimal digits.

201
Standards MX

2.2.2 Binary
2.2.2.1 Max10KBinary
Definition: Binary data of 10K maximum.
Type: Binary

Format

minLength 1

maxLength 10240

2.2.3 CodeSet
2.2.3.1 ActiveCurrencyCode
Definition: A code allocated to a currency by a Maintenance Agency under an international identification
scheme as described in the latest edition of the international standard ISO 4217 "Codes for the
representation of currencies and funds".
Type: CodeSet

Format

pattern [A-Z]{3,3}

Constraints

• ActiveCurrency
The currency code must be a valid active currency code, not yet withdrawn on the day the message
containing the currency is exchanged. Valid active currency codes are registered with the ISO 4217
Maintenance Agency, consist of three (3) contiguous letters, and are not yet withdrawn on the day
the message containing the Currency is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00005

– Error Text: Invalid currency code

Restricts
ParentCurrencyCode on page 225

2.2.3.2 ActiveOrHistoricCurrencyCode
Definition: A code allocated to a currency by a Maintenance Agency under an international identification
scheme, as described in the latest edition of the international standard ISO 4217 "Codes for the
representation of currencies and funds".
Type: CodeSet

202 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Format

pattern [A-Z]{3,3}

Constraints

• ActiveOrHistoricCurrency
The Currency Code must be registered, or have already been registered. Valid active or historic
currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3)
contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.
Error handling:

– Error severity: Fatal

– Error Code: D00006

– Error Text: Invalid currency code.

Restricts
ParentCurrencyCode on page 225

2.2.3.3 AddressType2Code
Definition: Specifies the type of address.
Type: CodeSet

CodeName Name Definition

ADDR Postal Address is the complete postal address.

PBOX POBox Address is a postal office (PO) box.

HOME Residential Address is the home address.

BIZZ Business Address is the business address.

MLTO MailTo Address is the address to which mail is

sent.

DLVY DeliveryTo Address is the address to which delivery

is to take place.

Restricts
AddressTypeCode on page 203

2.2.3.4 AddressTypeCode
Definition: Specifies the type of address.
Type: CodeSet

CodeName Name Definition

HOME Residential Address is the home address.

BIZZ Business Address is the business address.

ADDR Postal Address is the complete postal address.

203
Standards MX

CodeName Name Definition

PBOX POBox Address is a postal office (PO) box.

MLTO MailTo Address is the address to which mail is

sent.

DLVY DeliveryTo Address is the address to which delivery

is to take place.

Is restricted by
AddressType2Code on page 203

2.2.3.5 AmountDirectionCode
Definition: Specifies if an operation is an increase or a decrease or the result of a reversal operation.
Type: CodeSet

CodeName Name Definition

DBIT Debit Operation is a decrease.

CRDT Credit Operation is an increase.

RVDB ReversalDebit Credit entry used to reverse a previously

booked debit entry.

RVCD ReversalCredit Debit entry used to reverse a previously

booked credit entry.

Is restricted by
CreditDebitCode on page 206

2.2.3.6 ChargeBearerType1Code
Definition: Specifies which party(ies) will pay charges due for processing of the instruction.
Type: CodeSet

CodeName Name Definition

DEBT BorneByDebtor All transaction charges are to be borne

by the debtor.

CRED BorneByCreditor All transaction charges are to be borne

by the creditor.

SHAR Shared In a credit transfer context, means that

transaction charges on the sender
side are to be borne by the debtor,
transaction charges on the receiver
side are to be borne by the creditor.
In a direct debit context, means that
transaction charges on the sender
side are to be borne by the creditor,
transaction charges on the receiver side
are to be borne by the debtor.

SLEV FollowingServiceLevel Charges are to be applied following the

rules agreed in the service level and/or
scheme.

204 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Restricts
ChargeBearerTypeCode on page 205

2.2.3.7 ChargeBearerTypeCode
Definition: Specifies which party(ies) will pay charges due for processing of the instruction.
Type: CodeSet

CodeName Name Definition

DEBT BorneByDebtor All transaction charges are to be borne

by the debtor.

CRED BorneByCreditor All transaction charges are to be borne

by the creditor.

SHAR Shared In a credit transfer context, means that

transaction charges on the sender
side are to be borne by the debtor,
transaction charges on the receiver
side are to be borne by the creditor.
In a direct debit context, means that
transaction charges on the sender
side are to be borne by the creditor,
transaction charges on the receiver side
are to be borne by the debtor.

SLEV FollowingServiceLevel Charges are to be applied following the

rules agreed in the service level and/or
scheme.

Is restricted by
ChargeBearerType1Code on page 204

2.2.3.8 ClearingChannel2Code
Definition: Specifies the clearing channel for the routing of the transaction, as part of the payment type
identification.
Type: CodeSet

CodeName Name Definition

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross

settlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net

settlement system.

MPNS MassPaymentNetSystem Clearing channel is a mass payment net

settlement system.

BOOK BookTransfer Payment through internal book transfer.

Restricts
ClearingChannelCode on page 205

2.2.3.9 ClearingChannelCode
Definition: Specifies the clearing channel for the routing of the transaction, as part of the payment type
identification.

205
Standards MX

Type: CodeSet

CodeName Name Definition

RTGS RealTimeGrossSettlementSystem Clearing channel is a real-time gross

settlement system.

RTNS RealTimeNetSettlementSystem Clearing channel is a real-time net

settlement system.

MPNS MassPaymentNetSystem Clearing channel is a mass payment net

settlement system.

BOOK BookTransfer Payment through internal book transfer.

Is restricted by
ClearingChannel2Code on page 205

2.2.3.10 CountryCode
Definition: Code to identify a country, a dependency, or another area of particular geopolitical interest,
on the basis of country names obtained from the United Nations (ISO 3166, Alpha-2 code).
Type: CodeSet

Format

pattern [A-Z]{2,2}

Constraints

• Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166,
Alpha-2 code).
Error handling:

– Error severity: Fatal

– Error Code: D00004

– Error Text: Invalid Country Code.

2.2.3.11 CreditDebitCode
Definition: Specifies if an operation is an increase or a decrease.
Type: CodeSet

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

Restricts
AmountDirectionCode on page 204

206 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.3.12 DocumentType3Code
Definition: Specifies a type of financial or commercial document.
Type: CodeSet

CodeName Name Definition

RADM RemittanceAdviceMessage Document is a remittance advice sent

separately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment

instruction to which the current payment
instruction is related, for example, in a
cover scenario.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-

arranged foreign exchange transaction
to which the payment transaction refers.

DISP DispatchAdvice Document is a dispatch advice.

PUOR PurchaseOrder Document is a purchase order.

SCOR StructuredCommunicationReference Document is a structured communication

reference provided by the creditor to
identify the referred transaction.

Restricts
DocumentTypeCode on page 208

2.2.3.13 DocumentType6Code
Definition: Specifies a type of financial or commercial document.
Type: CodeSet

CodeName Name Definition

MSIN MeteredServiceInvoice Document is an invoice claiming

payment for the supply of metered
services, for example gas or electricity
supplied to a fixed meter.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the

final amount settled for a commercial
transaction.

DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the final

amount settled for a commercial
transaction.

CINV CommercialInvoice Document is an invoice.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.

HIRI HireInvoice Document is an invoice for the hiring of

human resources or renting goods or
equipment.

SBIN SelfBilledInvoice Document is an invoice issued by the

debtor.

CMCN CommercialContract Document is an agreement between

the parties, stipulating the terms and

207
Standards MX

CodeName Name Definition

conditions of the delivery of goods or
services.

SOAC StatementOfAccount Document is a statement of the

transactions posted to the debtor's
account at the supplier.

DISP DispatchAdvice Document is a dispatch advice.

BOLD BillOfLading Document is a shipping notice.

VCHR Voucher Document is an electronic payment

document.

AROI AccountReceivableOpenItem Document is a payment that applies to a

specific source document.

TSUT TradeServicesUtilityTransaction Document is a transaction identifier as

assigned by the Trade Services Utility.

PUOR PurchaseOrder Document is a purchase order.

Restricts
DocumentTypeCode on page 208

2.2.3.14 DocumentTypeCode
Definition: Specifies a type of financial or commercial document.
Type: CodeSet

CodeName Name Definition

MSIN MeteredServiceInvoice Document is an invoice claiming

payment for the supply of metered
services, for example gas or electricity
supplied to a fixed meter.

CNFA CreditNoteRelatedToFinancialAdjustment Document is a credit note for the

final amount settled for a commercial
transaction.

DNFA DebitNoteRelatedToFinancialAdjustment Document is a debit note for the final

amount settled for a commercial
transaction.

CINV CommercialInvoice Document is an invoice.

CREN CreditNote Document is a credit note.

DEBN DebitNote Document is a debit note.

HIRI HireInvoice Document is an invoice for the hiring of

human resources or renting goods or
equipment.

SBIN SelfBilledInvoice Document is an invoice issued by the

debtor.

RADM RemittanceAdviceMessage Document is a remittance advice sent

separately from the current transaction.

RPIN RelatedPaymentInstruction Document is a linked payment

instruction to which the current payment

208 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

CodeName Name Definition

instruction is related, for example, in a
cover scenario.

CMCN CommercialContract Document is an agreement between

the parties, stipulating the terms and
conditions of the delivery of goods or
services.

FXDR ForeignExchangeDealReference Document is a pre-agreed or pre-

arranged foreign exchange transaction
to which the payment transaction refers.

SOAC StatementOfAccount Document is a statement of the

transactions posted to the debtor's
account at the supplier.

DISP DispatchAdvice Document is a dispatch advice.

PUOR PurchaseOrder Document is a purchase order.

SCOR StructuredCommunicationReference Document is a structured communication

reference provided by the creditor to
identify the referred transaction.

BOLD BillOfLading Document is a shipping notice.

VCHR Voucher Document is an electronic payment

document.

AROI AccountReceivableOpenItem Document is a payment that applies to a

specific source document.

TSUT TradeServicesUtilityTransaction Document is a transaction identifier as

assigned by the Trade Services Utility.

HRCP CashierReceipt When the Sale system print the Cashier

copy of the Payment receipt.

CRCP CustomerReceipt When the Sale System requires the POI

system to print the Customer receipt.

JNRL Journal When the POI or the Sale System wants

to store a message on the journal printer
or electronic journal of the Sale Terminal
(it is sometimes a Sale Logging/Journal
Printer).

SRCP SaleReceipt When the Sale System requires the POI

system to print the Sale receipt.

Is restricted by
DocumentType3Code on page 207, DocumentType6Code on page 207

2.2.3.15 ExternalAccountIdentification1Code
Definition: Specifies the external account identification scheme name code in the format of character
string 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: CodeSet

209
Standards MX

Format

minLength 1

maxLength 4

Restricts
ExternalAccountIdentificationCode on page 210

2.2.3.16 ExternalAccountIdentificationCode
Definition: Specifies the external account identification scheme name code in the format of character
string 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: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalAccountIdentification1Code on page 209

2.2.3.17 ExternalCashAccountType1Code
Definition: Specifies the nature, or use, of the cash account in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalCashAccountTypeCode on page 210

2.2.3.18 ExternalCashAccountTypeCode
Definition: Specifies the nature, or use, of the cash account in the format of character string with a
maximum length of 4 characters.

The list of valid codes is an external code list published separately.

210 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalCashAccountType1Code on page 210

2.2.3.19 ExternalCashClearingSystem1Code
Definition: Specifies the cash clearing system, as published in an external cash clearing system code
list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 3

Restricts
ExternalCashClearingSystemCode on page 211

2.2.3.20 ExternalCashClearingSystemCode
Definition: Specifies the cash clearing system, as published in an external cash clearing system code
list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalCashClearingSystem1Code on page 211

2.2.3.21 ExternalCategoryPurpose1Code
Definition: Specifies the category purpose, as published in an external category purpose code list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

211
Standards MX

Format

minLength 1

maxLength 4

Restricts
ExternalCategoryPurposeCode on page 212

2.2.3.22 ExternalCategoryPurposeCode
Definition: Specifies the category purpose, as published in an external category purpose code list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalCategoryPurpose1Code on page 211

2.2.3.23 ExternalClearingSystemIdentification1Code
Definition: Specifies the clearing system identification code, as published in an external clearing system
identification code list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 5

Restricts
ExternalClearingSystemIdentificationCode on page 212

2.2.3.24 ExternalClearingSystemIdentificationCode
Definition: Specifies the clearing system identification code, as published in an external clearing system
identification code list.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

212 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

maxLength 5

Is restricted by
ExternalClearingSystemIdentification1Code on page 212

2.2.3.25 ExternalCreditorAgentInstruction1Code
Definition: Specifies further instructions concerning the processing of a payment instruction, as provided
to the creditor agent.
Type: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalCreditorAgentInstructionCode on page 213

2.2.3.26 ExternalCreditorAgentInstructionCode
Definition: Specifies further instructions concerning the processing of a payment instruction, as provided
to the creditor agent.
Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalCreditorAgentInstruction1Code on page 213

2.2.3.27 ExternalDiscountAmountType1Code
Definition: Specifies the nature, or use, of the amount in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

213
Standards MX

Restricts
ExternalDiscountAmountTypeCode on page 214

2.2.3.28 ExternalDiscountAmountTypeCode
Definition: Specifies the nature, or use, of the amount in the format of character string 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: CodeSet

Format

minLength 1
maxLength 4

Is restricted by
ExternalDiscountAmountType1Code on page 213

2.2.3.29 ExternalDocumentLineType1Code
Definition: Specifies the document line type as published in an external document type code list.
Type: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalDocumentLineTypeCode on page 214

2.2.3.30 ExternalDocumentLineTypeCode
Definition: Specifies the document line type as published in an external document type code list.
Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalDocumentLineType1Code on page 214

214 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.3.31 ExternalFinancialInstitutionIdentification1Code
Definition: Specifies the external financial institution identification scheme name code in the format of
character string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalFinancialInstitutionIdentificationCode on page 215

2.2.3.32 ExternalFinancialInstitutionIdentificationCode
Definition: Specifies the external financial institution identification scheme name code in the format of
character string 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: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalFinancialInstitutionIdentification1Code on page 215

2.2.3.33 ExternalGarnishmentType1Code
Definition: Specifies the garnishment type as published in an external document type code list.
Type: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalGarnishmentTypeCode on page 216

215
Standards MX

2.2.3.34 ExternalGarnishmentTypeCode
Definition: Specifies the garnishment type as published in an external document type code list.
Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalGarnishmentType1Code on page 215

2.2.3.35 ExternalLocalInstrument1Code
Definition: Specifies the external local instrument code in the format of character string with a maximum
length of 35 characters.

The list of valid codes is an external code list published separately.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 35

Restricts
ExternalLocalInstrumentCode on page 216

2.2.3.36 ExternalLocalInstrumentCode
Definition: Specifies the external local instrument code in the format of character string with a maximum
length of 35 characters.

The list of valid codes is an external code list published separately.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 35

Is restricted by
ExternalLocalInstrument1Code on page 216

216 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.3.37 ExternalMandateSetupReason1Code
Definition: Specifies the external mandate setup reason code in the format of character string with a
maximum length of 4 characters.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalMandateSetupReasonCode on page 217

2.2.3.38 ExternalMandateSetupReasonCode
Definition: Specifies the external mandate setup reason code in the format of character string with a
maximum length of 4 characters.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalMandateSetupReason1Code on page 217

2.2.3.39 ExternalOrganisationIdentification1Code
Definition: Specifies the external organisation identification scheme name code in the format of
character string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalOrganisationIdentificationCode on page 218

217
Standards MX

2.2.3.40 ExternalOrganisationIdentificationCode
Definition: Specifies the external organisation identification scheme name code in the format of
character string 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: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalOrganisationIdentification1Code on page 217

2.2.3.41 ExternalPersonIdentification1Code
Definition: Specifies the external person identification scheme name code in the format of character
string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalPersonIdentificationCode on page 218

2.2.3.42 ExternalPersonIdentificationCode
Definition: Specifies the external person identification scheme name code in the format of character
string 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: CodeSet

Format

minLength 1

maxLength 4

218 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Is restricted by
ExternalPersonIdentification1Code on page 218

2.2.3.43 ExternalProxyAccountType1Code
Definition: Specifies the external proxy account type code, as published in the proxy account type
external code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalProxyAccountTypeCode on page 219

2.2.3.44 ExternalProxyAccountTypeCode
Definition: Specifies the external proxy account type code, as published in the proxy account type
external code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalProxyAccountType1Code on page 219

2.2.3.45 ExternalPurpose1Code
Definition: Specifies the external purpose code in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

219
Standards MX

Restricts
ExternalPurposeCode on page 220

2.2.3.46 ExternalPurposeCode
Definition: Specifies the external purpose code in the format of character string 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: CodeSet

Format

minLength 1
maxLength 4

Is restricted by
ExternalPurpose1Code on page 219

2.2.3.47 ExternalServiceLevel1Code
Definition: Specifies the external service level code in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalServiceLevelCode on page 220

2.2.3.48 ExternalServiceLevelCode
Definition: Specifies the nature, or use, of the amount in the format of character string 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: CodeSet

220 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Format

minLength 1

maxLength 4

Is restricted by
ExternalServiceLevel1Code on page 220

2.2.3.49 ExternalTaxAmountType1Code
Definition: Specifies the nature, or use, of the amount in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

Restricts
ExternalTaxAmountTypeCode on page 221

2.2.3.50 ExternalTaxAmountTypeCode
Definition: Specifies the nature, or use, of the amount in the format of character string 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: CodeSet

Format

minLength 1

maxLength 4

Is restricted by
ExternalTaxAmountType1Code on page 221

2.2.3.51 Frequency6Code
Definition: Specifies the regularity of an event.
Type: CodeSet

221
Standards MX

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

MNTH Monthly Event takes place every month or once a

month.

QURT Quarterly Event takes place every three months or

four times a year.

MIAN SemiAnnual Event takes place every six months or

two times a year.

WEEK Weekly Event takes place once a week.

DAIL Daily Event takes place every day.

ADHO Adhoc Event takes place on request or as

necessary.

INDA IntraDay Event takes place several times a day.

FRTN Fortnightly Event takes place every two weeks.

Restricts
FrequencyCode on page 222

2.2.3.52 FrequencyCode
Definition: Specifies the regularity of an event.
Type: CodeSet

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

MNTH Monthly Event takes place every month or once a

month.

QURT Quarterly Event takes place every three months or

four times a year.

MIAN SemiAnnual Event takes place every six months or

two times a year.

WEEK Weekly Event takes place once a week.

DAIL Daily Event takes place every day.

ADHO Adhoc Event takes place on request or as

necessary.

INDA IntraDay Event takes place several times a day.

OVNG Overnight Event takes place overnight.

TEND TenDays Event takes place every ten business

days.

FRTN Fortnightly Event takes place every two weeks.

MOVE TriggeredByMovement Event takes place at the end of the day

if there was a movement on the account,
otherwise nothing is sent that day.

222 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

CodeName Name Definition

NEVR Never Event does never take place.

RATE Rate Event takes place based on a change of

a rate.

CRED OnCreditEvent Event occurs due to a credit event

occurring for an issuer.

UPFR Upfront Event that takes place at the initiation of

a trade or agreement.

EXPI OnExpiry Event occurs on expiry of a financial

contract.

HOUL Hourly Event takes place every hours.

Is restricted by
Frequency6Code on page 221

2.2.3.53 Instruction4Code
Definition: Specifies further instructions concerning the processing of a payment instruction, provided by
the sending clearing agent to the next agent(s).
Type: CodeSet

CodeName Name Definition

PHOA PhoneNextAgent Please advise/contact next agent by

phone.

TELA TelecomNextAgent Please advise/contact next agent

by the most efficient means of
telecommunication.

Restricts
InstructionCode on page 223

2.2.3.54 InstructionCode
Definition: Specifies further instructions concerning the processing of a payment instruction.
Type: CodeSet

CodeName Name Definition

PBEN PayTheBeneficiary (Ultimate) creditor to be paid only after

verification of identity.

TTIL TimeTill Payment instruction is valid and eligible

for execution until the date and time
stipulated. Otherwise, the payment
instruction will be rejected.

TFRO TimeFrom Payment instruction will be valid and

eligible for execution from the date and
time stipulated.

CHQB PayCreditorByCheque (Ultimate) creditor must be paid by

cheque.

223
Standards MX

CodeName Name Definition

HOLD HoldCashForCreditor Amount of money must be held for the

(ultimate) creditor, who will call. Pay on
identification.

PHOB PhoneBeneficiary Please advise/contact (ultimate) creditor/

claimant by phone.

TELB Telecom Please advise/contact (ultimate) creditor/

claimant by the most efficient means of
telecommunication.

PHOA PhoneNextAgent Please advise/contact next agent by

phone.

TELA TelecomNextAgent Please advise/contact next agent

by the most efficient means of
telecommunication.

Is restricted by
Instruction4Code on page 223

2.2.3.55 MandateClassification1Code
Definition: Specifies the type of direct debit amount, such as fixed or variable.
Type: CodeSet

CodeName Name Definition

FIXE Fixed Direct debit amount is fixed.

USGB UsageBased Direct debit amount is based on usage.

VARI Variable Direct debit amount is variable.

Restricts
MandateClassificationCode on page 224

2.2.3.56 MandateClassificationCode
Definition: Specifies the type of direct debit amount, such as fixed or variable.
Type: CodeSet

CodeName Name Definition

FIXE Fixed Direct debit amount is fixed.

VARI Variable Direct debit amount is variable.

USGB UsageBased Direct debit amount is based on usage.

Is restricted by
MandateClassification1Code on page 224

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

224 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

Type: CodeSet

CodeName Name Definition

DOCT Doctor Title of the person is Doctor or Dr.

MADM Madam Title of the person is Madam.

MISS Miss Title of the person is Miss.

MIST Mister Title of the person is Mister or Mr.

MIKS GenderNeutral Title of the person is gender neutral

(Mx).

Restricts
NamePrefixCode on page 225

2.2.3.58 NamePrefixCode
Definition: Specifies the terms used to formally address a person.
Type: CodeSet

CodeName Name Definition

DOCT Doctor Title of the person is Doctor or Dr.

MIST Mister Title of the person is Mister or Mr.

MISS Miss Title of the person is Miss.

MADM Madam Title of the person is Madam.

MIKS GenderNeutral Title of the person is gender neutral

(Mx).

Is restricted by
NamePrefix2Code on page 224

2.2.3.59 ParentCurrencyCode
Definition: Code allocated to a currency, by a maintenance agency, under an international identification
scheme as described in the latest edition of the international standard ISO 4217 "Codes for the
representation of currencies and funds". Valid currency codes are registered with the ISO 4217
Maintenance Agency, and consist of three contiguous letters.
Type: CodeSet

Format

pattern [A-Z]{3,3}

Is restricted by
ActiveCurrencyCode on page 202, ActiveOrHistoricCurrencyCode on page 202

2.2.3.60 PreferredContactMethod1Code
Definition: Preferred method used to reach the individual contact within an organisation.

225
Standards MX

Type: CodeSet

CodeName Name Definition

LETT Letter Preferred method used to reach the

contact is per letter.

MAIL Email Preferred method used to reach the

contact is per email.

PHON Phone Preferred method used to reach the

contact is per phone.

FAXX Fax Preferred method used to reach the

contact is per fax.

CELL MobileOrCellPhone Preferred method used to reach the

contact is per mobile or cell phone.

Restricts
PreferredContactMethodCode on page 226

2.2.3.61 PreferredContactMethodCode
Definition: Preferred method used to reach the individual contact within an organisation.
Type: CodeSet

CodeName Name Definition

LETT Letter Preferred method used to reach the

contact is per letter.

MAIL Email Preferred method used to reach the

contact is per email.

PHON Phone Preferred method used to reach the

contact is per phone.

FAXX Fax Preferred method used to reach the

contact is per fax.

CELL MobileOrCellPhone Preferred method used to reach the

contact is per mobile or cell phone.

Is restricted by
PreferredContactMethod1Code on page 225

2.2.3.62 Priority2Code
Definition: Specifies the priority level of an event.
Type: CodeSet

CodeName Name Definition

HIGH High Priority level is high.

NORM Normal Priority level is normal.

Restricts
PriorityCode on page 227

226 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.3.63 Priority3Code
Definition: Specifies the priority level of an event.
Type: CodeSet

CodeName Name Definition

URGT Urgent Priority level is urgent (highest priority

possible).

HIGH High Priority level is high.

NORM Normal Priority level is normal.

Restricts
PriorityCode on page 227

2.2.3.64 PriorityCode
Definition: Specifies the priority level of an event.
Type: CodeSet

CodeName Name Definition

URGT Urgent Priority level is urgent (highest priority

possible).

HIGH High Priority level is high.

NORM Normal Priority level is normal.

LOWW Low Priority level is low.

Is restricted by
Priority2Code on page 226, Priority3Code on page 227

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

CodeName Name Definition

CRED Credit Regulatory information applies to the

credit side.

DEBT Debit Regulatory information applies to the

debit side.

BOTH Both Regulatory information applies to both

credit and debit sides.

Restricts
RegulatoryReportingTypeCode on page 228

227
Standards MX

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

CodeName Name Definition

CRED Credit Regulatory information applies to the

credit side.

DEBT Debit Regulatory information applies to the

debit side.

BOTH Both Regulatory information applies to both

credit and debit sides.

Is restricted by
RegulatoryReportingType1Code on page 227

2.2.3.67 RemittanceLocationMethod2Code
Definition: Specifies the method used to deliver the remittance advice information.
Type: CodeSet

CodeName Name Definition

FAXI Fax Remittance advice information must be

faxed.

EDIC ElectronicDataInterchange Remittance advice information must be

sent through Electronic Data Interchange
(EDI).

URID UniformResourceIdentifier Remittance advice information needs

to be sent to a Uniform Resource
Identifier (URI). URI is a compact string
of characters that uniquely identify an
abstract or physical resource. URI's
are the super-set of identifiers, such as
URLs, email addresses, ftp sites, etc,
and as such, provide the syntax for all of
the identification schemes.

EMAL EMail Remittance advice information must be

sent through e-mail.

POST Post Remittance advice information must be

sent through postal services.

SMSM SMS Remittance advice information must

be sent through by phone as a short
message service (SMS).

Restricts
RemittanceLocationMethodCode on page 228

2.2.3.68 RemittanceLocationMethodCode
Definition: Specifies the method used to deliver the remittance advice information.
Type: CodeSet

228 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

CodeName Name Definition

FAXI Fax Remittance advice information must be

faxed.

EDIC ElectronicDataInterchange Remittance advice information must be

sent through Electronic Data Interchange
(EDI).

URID UniformResourceIdentifier Remittance advice information needs

to be sent to a Uniform Resource
Identifier (URI). URI is a compact string
of characters that uniquely identify an
abstract or physical resource. URI's
are the super-set of identifiers, such as
URLs, email addresses, ftp sites, etc,
and as such, provide the syntax for all of
the identification schemes.

EMAL EMail Remittance advice information must be

sent through e-mail.

POST Post Remittance advice information must be

sent through postal services.

SMSM SMS Remittance advice information must

be sent through by phone as a short
message service (SMS).

Is restricted by
RemittanceLocationMethod2Code on page 228

2.2.3.69 SettlementMethod1Code
Definition: Specifies the method used to settle the credit transfer instruction.
Type: CodeSet

CodeName Name Definition

INDA InstructedAgent Settlement is done by the agent

instructed to execute a payment
instruction.

INGA InstructingAgent Settlement is done by the agent

instructing and forwarding the payment
to the next party in the payment chain.

COVE CoverMethod Settlement is done through a cover

payment.

CLRG ClearingSystem Settlement is done through a payment

clearing system.

Restricts
SettlementMethodCode on page 229

2.2.3.70 SettlementMethodCode
Definition: Specifies the method used to settle the payment instruction.
Type: CodeSet

229
Standards MX

CodeName Name Definition

INDA InstructedAgent Settlement is done by the agent

instructed to execute a payment
instruction.

INGA InstructingAgent Settlement is done by the agent

instructing and forwarding the payment
to the next party in the payment chain.

COVE CoverMethod Settlement is done through a cover

payment.

CLRG ClearingSystem Settlement is done through a payment

clearing system.

Is restricted by
SettlementMethod1Code on page 229

2.2.3.71 TaxRecordPeriod1Code
Definition: Specifies the period related to the tax payment.
Type: CodeSet

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

230 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

CodeName Name Definition

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

Restricts
TaxRecordPeriodCode on page 231

2.2.3.72 TaxRecordPeriodCode
Definition: Specifies the period related to the tax payment.
Type: CodeSet

CodeName Name Definition

MM01 FirstMonth Tax is related to the second month of the

period.

MM02 SecondMonth Tax is related to the first month of the

period.

MM03 ThirdMonth Tax is related to the third month of the

period.

MM04 FourthMonth Tax is related to the fourth month of the

period.

MM05 FifthMonth Tax is related to the fifth month of the

period.

MM06 SixthMonth Tax is related to the sixth month of the

period.

MM07 SeventhMonth Tax is related to the seventh month of

the period.

MM08 EighthMonth Tax is related to the eighth month of the

period.

MM09 NinthMonth Tax is related to the ninth month of the

period.

MM10 TenthMonth Tax is related to the tenth month of the

period.

MM11 EleventhMonth Tax is related to the eleventh month of

the period.

MM12 TwelfthMonth Tax is related to the twelfth month of the

period.

QTR1 FirstQuarter Tax is related to the first quarter of the

period.

231
Standards MX

CodeName Name Definition

QTR2 SecondQuarter Tax is related to the second quarter of

the period.

QTR3 ThirdQuarter Tax is related to the third quarter of the

period.

QTR4 FourthQuarter Tax is related to the forth quarter of the

period.

HLF1 FirstHalf Tax is related to the first half of the

period.

HLF2 SecondHalf Tax is related to the second half of the

period.

Is restricted by
TaxRecordPeriod1Code on page 230

2.2.4 Date
2.2.4.1 ISODate
Definition: A particular point in the progression of time in a calendar year expressed in the YYYY-MM-
DD format. This representation is defined in "XML Schema Part 2: Datatypes Second Edition - W3C
Recommendation 28 October 2004" which is aligned with ISO 8601.
Type: Date

2.2.5 DateTime
2.2.5.1 ISODateTime
Definition: A particular point in the progression of time defined by a mandatory date and a mandatory
time component, expressed in either UTC time format (YYYY-MM-DDThh:mm:ss.sssZ), local time
with UTC offset format (YYYY-MM-DDThh:mm:ss.sss+/-hh:mm), or local time format (YYYY-MM-
DDThh:mm:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second
Edition - W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

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
maximum number of digits that are allowed.
Type: DateTime

232 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.6 IdentifierSet
2.2.6.1 AnyBICDec2014Identifier
Definition: Code allocated to a financial or non-financial institution by the ISO 9362 Registration
Authority, as described in ISO 9362: 2014 - "Banking - Banking telecommunication messages -
Business identifier code (BIC)".
Type: IdentifierSet
Identification scheme: SWIFT; AnyBICIdentifier

Format

pattern [A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}

Constraints

• 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 the ISO
directory of BICs, and consists of eight (8) or eleven (11) contiguous characters.
Error handling:

– Error severity: Fatal

– Error Code: D00008

– Error Text: Invalid BIC.

2.2.6.2 BICFIDec2014Identifier
Definition: Code allocated to a financial institution by the ISO 9362 Registration Authority as described
in ISO 9362: 2014 - "Banking - Banking telecommunication messages - Business identifier code (BIC)".
Type: IdentifierSet
Identification scheme: SWIFT; BICIdentifier

Format

pattern [A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}

Constraints

• BICFI
Valid BICs for financial institutions are registered and published by the ISO 9362 Registration
Authority in the ISO directory of BICs, and consist of eight (8) or eleven (11) contiguous characters.
Error handling:

– Error severity: Fatal

– Error Code: D00001

233
Standards MX

– Error Text: Invalid FI BIC.

2.2.6.3 IBAN2007Identifier
Definition: The International Bank Account Number is a code used internationally by financial
institutions to uniquely identify the account of a customer at a financial institution as described in the
2007 edition of the ISO 13616 standard "Banking and related financial services - International Bank
Account Number (IBAN)" and replaced by the more recent edition of the standard.
Type: IdentifierSet
Identification scheme: National Banking Association; International Bank Account Number (ISO 13616)

Format

pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}

Constraints

• IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.
Error handling:

– Error severity: Fatal

– Error Code: D00003

– Error Text: Invalid IBAN format or invalid check digits.

2.2.6.4 LEIIdentifier
Definition: Legal Entity Identifier is a code allocated to a party as described in ISO 17442 "Financial
Services - Legal Entity Identifier (LEI)".
Type: IdentifierSet
Identification scheme: Global LEI System; LEIIdentifier

Format

pattern [A-Z0-9]{18,18}[0-9]{2,2}

2.2.6.5 UUIDv4Identifier
Definition: Universally Unique IDentifier (UUID) version 4, as described in IETC RFC 4122 "Universally
Unique IDentifier (UUID) URN Namespace".
Type: IdentifierSet
Identification scheme: RFC4122; UUIDv4

Format

pattern [a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}

234 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.7 Indicator
2.2.7.1 BatchBookingIndicator
Definition: Identifies whether the sending party requests a single debit or credit entry per individual
transaction or a batch entry for the sum of the amounts of all transactions.
Type: Indicator
Meaning When True: Identifies that a batch entry for the sum of the amounts of all transactions in the
batch or message is requested.
Meaning When False: Identifies that a single entry for each of the transactions in the batch or message
is requested.

2.2.7.2 TrueFalseIndicator
Definition: A flag indicating a True or False value.
Type: Indicator
Meaning When True: True
Meaning When False: False

2.2.8 Quantity
2.2.8.1 DecimalNumber
Definition: Number of objects represented as a decimal number, for example 0.75 or 45.6.
Type: Quantity

Format

totalDigits 18

fractionDigits 17

2.2.8.2 Number
Definition: Number of objects represented as an integer.
Type: Quantity

Format

totalDigits 18

fractionDigits 0

2.2.9 Rate
2.2.9.1 BaseOneRate
Definition: Rate expressed as a decimal, for example, 0.7 is 7/10 and 70%.
Type: Rate

235
Standards MX

Format

totalDigits 11

fractionDigits 10

baseValue 1.0

2.2.9.2 PercentageRate
Definition: Rate expressed as a percentage, that is, in hundredths, for example, 0.7 is 7/10 of a percent,
and 7.0 is 7%.
Type: Rate

Format

totalDigits 11
fractionDigits 10

baseValue 100.0

2.2.10 Text
2.2.10.1 Exact2NumericText
Definition: Specifies a numeric string with an exact length of 2 digits.
Type: Text

Format

pattern [0-9]{2}

2.2.10.2 Exact4AlphaNumericText
Definition: Specifies an alphanumeric string with a length of 4 characters.
Type: Text

Format

pattern [a-zA-Z0-9]{4}

2.2.10.3 Max10Text
Definition: Specifies a character string with a maximum length of 10 characters.
Type: Text

Format

minLength 1

maxLength 10

236 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.10.4 Max128Text
Definition: Specifies a character string with a maximum length of 128 characters.
Type: Text

Format

minLength 1

maxLength 128

2.2.10.5 Max140Text
Definition: Specifies a character string with a maximum length of 140 characters.
Type: Text

Format

minLength 1

maxLength 140

2.2.10.6 Max15NumericText
Definition: Specifies a numeric string with a maximum length of 15 digits.
Type: Text

Format

pattern [0-9]{1,15}

2.2.10.7 Max16Text
Definition: Specifies a character string with a maximum length of 16 characters.
Type: Text

Format

minLength 1

maxLength 16

2.2.10.8 Max2048Text
Definition: Specifies a character string with a maximum length of 2048 characters.
Type: Text

Format

minLength 1

maxLength 2048

237
Standards MX

2.2.10.9 Max34Text
Definition: Specifies a character string with a maximum length of 34 characters.
Type: Text

Format

minLength 1

maxLength 34

2.2.10.10 Max350Text
Definition: Specifies a character string with a maximum length of 350 characters.
Type: Text

Format

minLength 1

maxLength 350

2.2.10.11 Max35Text
Definition: Specifies a character string with a maximum length of 35 characters.
Type: Text

Format

minLength 1

maxLength 35

2.2.10.12 Max4Text
Definition: Specifies a character string with a maximum length of 4 characters.
Type: Text

Format

minLength 1

maxLength 4

2.2.10.13 Max70Text
Definition: Specifies a character string with a maximum length of 70characters.
Type: Text

Format

minLength 1

maxLength 70

238 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)

 Message Items Types

2.2.10.14 PhoneNumber
Definition: The collection of information which identifies a specific phone or FAX number as defined by
telecom services.

It consists of a "+" followed by the country code (from 1 to 3 characters) then a "-" and finally, any
combination of numbers, "(", ")", "+" and "-" (up to 30 characters).
Type: Text

Format

pattern \+[0-9]{1,3}-[0-9()+\-]{1,30}

2.2.11 Time
2.2.11.1 ISOTime
Definition: A particular point in the progression of time in a calendar day expressed in either UTC time
format (hh:mm:ss.sssZ), local time with UTC offset format (hh:mm:ss.sss+/-hh:mm), or local time format
(hh:mm:ss.sss). These representations are defined in "XML Schema Part 2: Datatypes Second Edition -
W3C Recommendation 28 October 2004" which is aligned with ISO 8601.

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
maximum number of digits that are allowed.
Type: Time

2.2.12 Year
2.2.12.1 ISOYear
Definition: Year represented by YYYY (ISO 8601).
Type: Year

239
Standards MX

Legal Notices
Copyright
SWIFT © . All rights reserved.
You may copy this publication within your organisation. Any such copy must include these legal notices.

Confidentiality
This publication may contain SWIFT or third-party confidential information. Do not disclose this
publication outside your organisation without the prior written consent of SWIFT.

Disclaimer
The information in this publication may change from time to time. You must always refer to the latest
available version.

SWIFT Standards Intellectual Property Rights (IPR) Policy - End-User License Agreement
SWIFT Standards are licensed subject to the terms and conditions of the SWIFT Standards IPR Policy
- End-User License Agreement available at www.swift.com > About SWIFT > Legal > SWIFT Standards
IPR Policy.

Translations
The English version of SWIFT documentation is the only official version.

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
registered trademarks of their respective owners.

240 Message Reference Guide - FIToFICustomerCreditTransferV10 (pacs.008.001.10)