ISO 20022

Exceptions and Investigations - Maintenance 2020 -

2021

Message Definition Report - Part 2

For evaluation by the Payments SEG
This document provides details of the Message Definitions for Exceptions and Investigations - Maintenance 2020 - 2021.

December 2020
For evaluation by the Payments SEG Table of Contents

Table of Contents

1 Message Set Overview ...................................................................................................................................... 4

1.1 List of MessageDefinitions ........................................................................................................................... 4

2 DRAFT1camt.026.001.09 UnableToApplyV09 ......................................................................................... 6

2.1 MessageDefinition Functionality .................................................................................................................. 6
2.2 Structure .......................................................................................................................................................... 8
2.3 Constraints ...................................................................................................................................................... 8
2.4 Message Building Blocks ............................................................................................................................ 10

3 DRAFT1camt.027.001.09 ClaimNonReceiptV09 ................................................................................... 17

3.1 MessageDefinition Functionality ................................................................................................................ 17
3.2 Structure ........................................................................................................................................................ 19
3.3 Constraints .................................................................................................................................................... 19
3.4 Message Building Blocks ............................................................................................................................ 21

4 DRAFT1camt.028.001.11 AdditionalPaymentInformationV11 ....................................................... 28

4.1 MessageDefinition Functionality ................................................................................................................ 28
4.2 Structure ........................................................................................................................................................ 29
4.3 Constraints .................................................................................................................................................... 29
4.4 Message Building Blocks ............................................................................................................................ 32

5 DRAFT1camt.029.001.11 ResolutionOfInvestigationV11 ................................................................. 39

5.1 MessageDefinition Functionality ................................................................................................................ 39
5.2 Structure ........................................................................................................................................................ 41
5.3 Constraints .................................................................................................................................................... 43
5.4 Message Building Blocks ............................................................................................................................ 47

6 DRAFT1camt.037.001.09 DebitAuthorisationRequestV09 ............................................................... 80

6.1 MessageDefinition Functionality ................................................................................................................ 80
6.2 Structure ........................................................................................................................................................ 81
6.3 Constraints .................................................................................................................................................... 81
6.4 Message Building Blocks ............................................................................................................................ 83

7 DRAFT1camt.055.001.10 CustomerPaymentCancellationRequestV10 ..................................... 86

7.1 MessageDefinition Functionality ................................................................................................................ 86
7.2 Structure ........................................................................................................................................................ 88
7.3 Constraints .................................................................................................................................................... 89
7.4 Message Building Blocks ............................................................................................................................ 92

8 DRAFT1camt.056.001.10 FIToFIPaymentCancellationRequestV10 .......................................... 106

8.1 MessageDefinition Functionality .............................................................................................................. 106
8.2 Structure ...................................................................................................................................................... 108
8.3 Constraints .................................................................................................................................................. 109
8.4 Message Building Blocks .......................................................................................................................... 111

Exceptions and Investigations - Maintenance 2020 - 2021 2 December 2020

For evaluation by the Payments SEG Table of Contents

9 DRAFT1camt.087.001.08 RequestToModifyPaymentV08 .............................................................. 121

9.1 MessageDefinition Functionality .............................................................................................................. 121
9.2 Structure ...................................................................................................................................................... 124
9.3 Constraints .................................................................................................................................................. 125
9.4 Message Building Blocks .......................................................................................................................... 127

10 Message Items Types .................................................................................................................................... 144

10.1 MessageComponents ............................................................................................................................... 144
10.2 Message Datatypes ................................................................................................................................... 459

Exceptions and Investigations - Maintenance 2020 - 2021 3 December 2020

For evaluation by the Payments SEG Message Set Overview

1 Message Set Overview

Introduction
Set of messages used for the processing of the payments exceptions and investigations.

It only includes the new versions of the MessageDefinitions that have been impacted by the
maintenance cycle 2020/2021 (MCR #170).

1.1 List of MessageDefinitions

The following table lists all MessageDefinitions described in this book.

MessageDefinition Definition

DRAFT1camt.026.001.09 The UnableToApply message is sent by a case creator

UnableToApplyV09 or a case assigner to a case assignee. This message
is used to initiate an investigation of a payment
instruction that cannot be executed or reconciled.

DRAFT1camt.027.001.09 The ClaimNonReceipt message is sent by a case

ClaimNonReceiptV09 creator/case assigner to a case assignee.

This message is used to initiate an investigation for

missing funds at the creditor (missing credit entry to its
account) or at an agent along the processing chain
(missing cover for a received payment instruction).

DRAFT1camt.028.001.11 The AdditionalPaymentInformation message is sent by

AdditionalPaymentInformationV11 an account servicing institution to an account owner.

This message is used to provide additional or

corrected information on a payment instruction or
statement entry, in order to allow reconciliation.

DRAFT1camt.029.001.11 The ResolutionOfInvestigation message is sent by a

ResolutionOfInvestigationV11 case assignee to a case creator/case assigner.

This message is used to inform of the resolution of a

case, and optionally provides details about.

- the corrective action undertaken by the case

assignee;

- information on the return where applicable.

DRAFT1camt.037.001.09 The DebitAuthorisationRequest message is sent by an

DebitAuthorisationRequestV09 account servicing institution to an account owner. This
message is used to request authorisation to debit an
account.

DRAFT1camt.055.001.10 The CustomerPaymentCancellationRequest message

CustomerPaymentCancellationRequestV10 is sent by a case creator/case assigner to a case
assignee.

This message is used to request the cancellation of an

original payment instruction. The
CustomerPaymentCancellationRequest message is
issued by the initiating party to request the cancellation
of an initiation payment message previously sent (such
as CustomerCreditTransferInitiation or
CustomerDirectDebitInitiation).

Exceptions and Investigations - Maintenance 2020 - 2021 4 December 2020

For evaluation by the Payments SEG Message Set Overview

MessageDefinition Definition

DRAFT1camt.056.001.10 The FIToFIPaymentCancellationRequest message is

FIToFIPaymentCancellationRequestV10 sent by a case creator/case assigner to a case
assignee.

This message is used to request the cancellation of an

original payment instruction. The
FIToFIPaymentCancellationRequest message is
exchanged between the instructing agent and the
instructed agent to request the cancellation of a
interbank payment message previously sent (such as
FIToFICustomerCreditTransfer,
FIToFICustomerDirectDebit or
FinancialInstitutionCreditTransfer).

The FIToFIPaymentCancellationRequest message

supports both the request for cancellation (the
instructed agent - or assignee - has not yet processed
and forwarded the payment instruction) as well as the
request for refund (payment has been fully processed
already by the instructed agent - or assignee).

DRAFT1camt.087.001.08 The RequestToModifyPayment message is sent by a

RequestToModifyPaymentV08 case creator/case assigner to a case assignee.

This message is used to request the modification of

characteristics of an original payment instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 5 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

2 DRAFT1camt.026.001.09
UnableToApplyV09

2.1 MessageDefinition Functionality

Scope

The UnableToApply message is sent by a case creator or a case assigner to a case assignee. This
message is used to initiate an investigation of a payment instruction that cannot be executed or
reconciled.

Usage

The Unable To Apply case occurs in two situations:

- an agent cannot execute the payment instruction due to missing or incorrect information;

- a creditor cannot reconcile the payment entry as it is received unexpectedly, or missing or incorrect
information prevents reconciliation.

The UnableToApply message:

- always follows the reverse route of the original payment instruction;

- must be forwarded to the preceding agents in the payment processing chain, where appropriate;

- covers one and only one payment instruction (or payment entry) at a time; if several payment
instructions cannot be executed or several payment entries cannot be reconciled, then multiple
UnableToApply messages must be sent.

Depending on what stage the payment is and what has been done to it, for example incorrect routing,
errors/omissions when processing the instruction or even the absence of any error, the unable to apply
case may lead to a:

- AdditionalPaymentInformation message, sent to the case creator/case assigner, if a truncation or

omission in a payment instruction prevented reconciliation;

- CustomerPaymentCancellationRequest or FIToFIPaymentCancellationRequest message, sent to the

subsequent agent in the payment processing chain, if the original payment instruction has been
incorrectly routed through the chain of agents (this also entails a new corrected payment instruction
being issued). Prior to sending the payment cancellation request, the agent should first send a
resolution indicating that a cancellation will follow (CWFW);

- RequestToModifyPayment message, sent to the subsequent agent in the payment processing chain, if
a truncation or omission has occurred during the processing of the original payment instruction. Prior to
sending the modify payment request, the agent should first send a resolution indicating that a
modification will follow (MWFW);

- DebitAuthorisationRequest message, sent to the case creator/case assigner, if the payment

instruction has reached an incorrect creditor.

The UnableToApply message has the following main characteristics:

Exceptions and Investigations - Maintenance 2020 - 2021 6 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

The case creator (the instructed party/creditor of a payment instruction) assigns a unique case
identification and optionally the reason code for the UnableToApply message. This information will be
passed unchanged to all subsequent case assignees.

The case creator specifies the identification of the underlying payment instruction. This identification
needs to be updated by the subsequent case assigner(s) in order to match the one used with their case
assignee(s).

The UnableToApply Justification element allows the assigner to indicate whether a specific element
causes the unable to apply situation (incorrect element and/or mismatched element can be listed) or
whether any supplementary information needs to be forwarded.
Outline
The UnableToApplyV09 MessageDefinition is composed of 5 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. Underlying
References the payment instruction or statement entry that a party is unable to execute or unable
to reconcile.

D. Justification
Explains the reason why the case creator is unable to apply the instruction.

E. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

Exceptions and Investigations - Maintenance 2020 - 2021 7 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

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

Message root <Document> <UblToApply> [1..1]

Assignment <Assgnmt> [1..1] ± 10

Case <Case> [0..1] ± 11

Underlying <Undrlyg> [1..1] ± 11

Justification <Justfn> [1..1] 11

{Or AnyInformation <AnyInf> [1..1] Indicator 12

Or MissingOrIncorrectInformation <MssngOrIncrrctInf> [1..1] 12

AntiMoneyLaunderingRequest <AMLReq> [0..1] Indicator 13

MissingInformation <MssngInf> [0..10] C3 13

Type <Tp> [1..1] 14

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

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

AdditionalMissingInformation <AddtlMssngInf> [0..1] Text 14

IncorrectInformation <IncrrctInf> [0..10] C2 14

Type <Tp> [1..1] 15

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

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

AdditionalIncorrectInformation <AddtlIncrrctInf> [0..1] Text 15

Or} PossibleDuplicateInstruction <PssblDplctInstr> [1..1] Indicator 15

SupplementaryData <SplmtryData> [0..*] ± C22 16

2.3 Constraints
C1 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.

C2 AdditionalIncorrectInformationRule
If Code is equal to NARR (Narrative), then AdditionalIncorrectInformation must be present.

C3 AdditionalMissingInformationRule
If Code is equal to NARR (Narrative), then AdditionalMissingInformation must be present.

Exceptions and Investigations - Maintenance 2020 - 2021 8 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

C4 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C5 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

C8 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

C10 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C12 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C13 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C14 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C15 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must
be present.

C16 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.

Exceptions and Investigations - Maintenance 2020 - 2021 9 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

C17 OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

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

C19 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C20 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C21 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C23 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C24 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

2.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

2.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.

Exceptions and Investigations - Maintenance 2020 - 2021 10 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

2.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

2.4.3 Underlying <Undrlyg>

Presence: [1..1]
Definition: References the payment instruction or statement entry that a party is unable to execute or
unable to reconcile.
Underlying <Undrlyg> contains one of the following elements (see "UnderlyingTransaction7Choice"
on page 211 for details)

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

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

2.4.4 Justification <Justfn>

Presence: [1..1]
Definition: Explains the reason why the case creator is unable to apply the instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 11 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

Justification <Justfn> contains one of the following UnableToApplyJustification4Choice elements

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

No.

{Or AnyInformation <AnyInf> [1..1] Indicator 12

Or MissingOrIncorrectInformation <MssngOrIncrrctInf> [1..1] 12

AntiMoneyLaunderingRequest <AMLReq> [0..1] Indicator 13

MissingInformation <MssngInf> [0..10] C3 13

Type <Tp> [1..1] 14

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

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

AdditionalMissingInformation <AddtlMssngInf> [0..1] Text 14

IncorrectInformation <IncrrctInf> [0..10] C2 14

Type <Tp> [1..1] 15

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

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

AdditionalIncorrectInformation <AddtlIncrrctInf> [0..1] Text 15

Or} PossibleDuplicateInstruction <PssblDplctInstr> [1..1] Indicator 15

2.4.4.1 AnyInformation <AnyInf>

Presence: [1..1]
Definition: Indicates whether or not all available information on the underlying payment instruction is
requested.
Datatype: One of the following values must be used (see "YesNoIndicator" on page 480):

• Meaning When True: Yes

• Meaning When False: No

2.4.4.2 MissingOrIncorrectInformation <MssngOrIncrrctInf>

Presence: [1..1]
Definition: Set of elements used to indicate which information is missing or incorrect.

Exceptions and Investigations - Maintenance 2020 - 2021 12 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

MissingOrIncorrectInformation <MssngOrIncrrctInf> contains the following

MissingOrIncorrectData1 elements

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

No.

AntiMoneyLaunderingRequest <AMLReq> [0..1] Indicator 13

MissingInformation <MssngInf> [0..10] C3 13

Type <Tp> [1..1] 14

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

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

AdditionalMissingInformation <AddtlMssngInf> [0..1] Text 14

IncorrectInformation <IncrrctInf> [0..10] C2 14

Type <Tp> [1..1] 15

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

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

AdditionalIncorrectInformation <AddtlIncrrctInf> [0..1] Text 15

2.4.4.2.1 AntiMoneyLaunderingRequest <AMLReq>

Presence: [0..1]
Definition: Indicates whether the request is related to an AML (Anti Money Laundering) investigation or
not.
Datatype: One of the following values must be used (see "AMLIndicator" on page 479):

• Meaning When True: Indicates that the investigation is related to an anti-money laundering
investigation request.

• Meaning When False: Indicates that the investigation is not related to an anti-money laundering
investigation request.

2.4.4.2.2 MissingInformation <MssngInf>

Presence: [0..10]
Definition: Indicates the missing information.
Impacted by: C3 "AdditionalMissingInformationRule"
MissingInformation <MssngInf> contains the following UnableToApplyMissing2 elements

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

No.

Type <Tp> [1..1] 14

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

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

AdditionalMissingInformation <AddtlMssngInf> [0..1] Text 14

Exceptions and Investigations - Maintenance 2020 - 2021 13 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

Constraints

• AdditionalMissingInformationRule
If Code is equal to NARR (Narrative), then AdditionalMissingInformation must be present.
On Condition
/Type/Code is within DataType <<Code>> ValidationRuleNarrative1Code
Following Must be True
/AdditionalMissingInformation Must be present

2.4.4.2.2.1 Type <Tp>

Presence: [1..1]
Definition: Specifies which data type is mising in the transaction.
Type <Tp> contains one of the following MissingData1Choice elements

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

No.

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

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

2.4.4.2.2.1.1 Code <Cd>

Presence: [1..1]
Definition: Missing data type, in a coded form.
Datatype: "ExternalUnableToApplyMissingData1Code" on page 471

2.4.4.2.2.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Missing data type, in a proprietary form.
Datatype: "Max35Text" on page 483

2.4.4.2.2.2 AdditionalMissingInformation <AddtlMssngInf>

Presence: [0..1]
Definition: Further details about the missing information.
Datatype: "Max140Text" on page 482

2.4.4.2.3 IncorrectInformation <IncrrctInf>

Presence: [0..10]
Definition: Indicates, in a coded form, the incorrect information.
Impacted by: C2 "AdditionalIncorrectInformationRule"

Exceptions and Investigations - Maintenance 2020 - 2021 14 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

IncorrectInformation <IncrrctInf> contains the following UnableToApplyIncorrect2 elements

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

No.

Type <Tp> [1..1] 15

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

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

AdditionalIncorrectInformation <AddtlIncrrctInf> [0..1] Text 15

Constraints

• AdditionalIncorrectInformationRule
If Code is equal to NARR (Narrative), then AdditionalIncorrectInformation must be present.
On Condition
/Type/Code is within DataType <<Code>> ValidationRuleNarrative1Code
Following Must be True
/AdditionalIncorrectInformation Must be present

2.4.4.2.3.1 Type <Tp>

Presence: [1..1]
Definition: Specifies which data type is incorrect in the transaction.
Type <Tp> contains one of the following IncorrectData1Choice elements

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

No.

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

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

2.4.4.2.3.1.1 Code <Cd>

Presence: [1..1]
Definition: Incorrect data type, in a coded form.
Datatype: "ExternalUnableToApplyIncorrectData1Code" on page 471

2.4.4.2.3.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Incorrect data type, in a proprietary form.
Datatype: "Max35Text" on page 483

2.4.4.2.3.2 AdditionalIncorrectInformation <AddtlIncrrctInf>

Presence: [0..1]
Definition: Further details about the incorrect information.
Datatype: "Max140Text" on page 482

2.4.4.3 PossibleDuplicateInstruction <PssblDplctInstr>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 15 December 2020

For evaluation by the Payments SEG DRAFT1camt.026.001.09 UnableToApplyV09

Definition: Indicates whether or not the referred item is a possible duplicate of a previous instruction or
entry.
Datatype: One of the following values must be used (see "TrueFalseIndicator" on page 480):

• Meaning When True: True

• Meaning When False: False

2.4.5 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C22 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 16 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

3 DRAFT1camt.027.001.09
ClaimNonReceiptV09

3.1 MessageDefinition Functionality

Scope

The ClaimNonReceipt message is sent by a case creator/case assigner to a case assignee.

This message is used to initiate an investigation for missing funds at the creditor (missing credit entry to
its account) or at an agent along the processing chain (missing cover for a received payment
instruction).

Usage

The claim non receipt case occurs in two situations:

- The creditor is expecting funds from a particular debtor and cannot find the corresponding credit entry
on its account. In this situation, it is understood that the creditor will contact its debtor, and that the
debtor will trigger the claim non receipt case on its behalf. A workflow where the creditor directly
addresses a ClaimNonReceipt message to its account servicing institution is not retained;

- An agent in the processing chain cannot find a cover payment corresponding to a received payment
instruction. In this situation, the agent may directly trigger the investigation by sending a
ClaimNonReceipt message to the sender of the original payment instruction.

The ClaimNonReceipt message covers one and only one payment instruction at a time. If several
expected payment instructions/cover instructions are found missing, then multiple ClaimNonReceipt
messages must be sent.

Depending on the result of the investigation by a case assignee (incorrect routing, errors/omissions
when processing the instruction or even the absence of an error) and the stage at which the payment
instruction is being process, the claim non receipt case may lead to a:

- CustomerPaymentCancellationRequest or FIToFIPaymentCancellationRequest message, sent to the

subsequent agent in the payment processing chain, if the original payment instruction has been
incorrectly routed through the chain of agents. (This also implies that a new, corrected, payment
instruction is issued);

- RequestToModifyPayment message, sent to the subsequent agent in the payment processing chain, if
a truncation or omission has occurred during the processing of the original payment instruction.

If the above situations occur, the assignee wanting to request a payment cancellation or payment
modification should first send out a ResolutionOfInvestigation with a confirmation status that indicates
that either cancellation (CWFW) modification (MWFW) or unable to apply (UWFW) will follow. (See
section on ResolutionOfInvestigation for more details).

In the cover is missing, the case assignee may also simply issue the omitted cover payment or when
the initial cover information was incorrect, update the cover (through modification and/or cancellation as
required) with the correction information provided in the ClaimNonReceipt message. The case assignee
will issue a ResolutionOfInvestigation message with the CorrectionTransaction element mentioning the
references of the cover payment.

Exceptions and Investigations - Maintenance 2020 - 2021 17 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

The ClaimNonReceipt message may be forwarded to subsequent case assignees.

The ClaimNonReceipt message has the following main characteristics:

- Case identification: The case creator assigns a unique case identification. This information will be
passed unchanged to subsequent case assignee(s);

- Underlying payment: The case creator refers to the underlying payment instruction for the
unambiguous identification of the payment instruction. This identification needs to be updated by the
subsequent case assigner(s) in order to match the one used with their case assignee(s);

- Missing cover indicator: The MissingCoverIndicator element distinguishes between a missing cover
situation (when set to YES - true) or a missing funds situation (when set to NO - false);

- CoverCorrection: The CoverCorrection element allows the case assigner to provide corrected cover
information, when these are incorrect in the underlying payment instruction for which the cover is
issued.
Outline
The ClaimNonReceiptV09 MessageDefinition is composed of 6 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. Underlying
Identifies the payment instruction for which the Creditor has not received the funds.

Usage: In case of a missing cover, it must be the identification of the related payment instruction.

In case of a claim non receipt initiated by the debtor, it must be the identification of the instruction.

D. CoverDetails
Provides the cover related information of a claim non receipt investigation.

Usage:

The absence of the cover details means that the message is not a cover related investigation.

E. InstructionForAssignee
Further information related to the processing of the investigation that may need to be acted upon
by the assignee.

F. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

Exceptions and Investigations - Maintenance 2020 - 2021 18 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

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

Message root <Document> <ClmNonRct> [1..1]

Assignment <Assgnmt> [1..1] ± 21

Case <Case> [0..1] ± 22

Underlying <Undrlyg> [1..1] ± 22

CoverDetails <CoverDtls> [0..1] 22

MissingCoverIndicator <MssngCoverInd> [1..1] Indicator 23

CoverCorrection <CoverCrrctn> [0..1] C12, 23

C14

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 24

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 25

<InstdRmbrsmntAgtAcct>

InstructionForAssignee <InstrForAssgne> [0..1] 26

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

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

SupplementaryData <SplmtryData> [0..*] ± C22 26

3.3 Constraints
C1 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.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

Exceptions and Investigations - Maintenance 2020 - 2021 19 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

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

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

C8 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C10 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C11 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C12 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C13 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C14 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAcount is present, then InstructingReimbursementAgent
must be present.

C15 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must
be present.

C16 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.

C17 OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

Exceptions and Investigations - Maintenance 2020 - 2021 20 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

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

C19 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C20 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C21 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C23 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C24 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

3.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

3.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

Exceptions and Investigations - Maintenance 2020 - 2021 21 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

3.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

3.4.3 Underlying <Undrlyg>

Presence: [1..1]
Definition: Identifies the payment instruction for which the Creditor has not received the funds.

Usage: In case of a missing cover, it must be the identification of the related payment instruction.

In case of a claim non receipt initiated by the debtor, it must be the identification of the instruction.
Underlying <Undrlyg> contains one of the following elements (see "UnderlyingTransaction7Choice"
on page 211 for details)

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

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

3.4.4 CoverDetails <CoverDtls>

Presence: [0..1]
Definition: Provides the cover related information of a claim non receipt investigation.

Usage:

The absence of the cover details means that the message is not a cover related investigation.

Exceptions and Investigations - Maintenance 2020 - 2021 22 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

CoverDetails <CoverDtls> contains the following MissingCover5 elements

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

No.

MissingCoverIndicator <MssngCoverInd> [1..1] Indicator 23

CoverCorrection <CoverCrrctn> [0..1] C12, 23

C14

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 24

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 25

<InstdRmbrsmntAgtAcct>

3.4.4.1 MissingCoverIndicator <MssngCoverInd>

Presence: [1..1]
Definition: Indicates whether or not the claim is related to a missing cover.
Datatype: One of the following values must be used (see "YesNoIndicator" on page 480):

• Meaning When True: Yes

• Meaning When False: No

3.4.4.2 CoverCorrection <CoverCrrctn>

Presence: [0..1]
Definition: Set of elements provided to update incorrect settlement information for the cover related to
the received payment instruction.
Impacted by: C12 "InstructedReimbursementAgentAccountRule", C14
"InstructingReimbursementAgentAccountRule"
CoverCorrection <CoverCrrctn> contains the following SettlementInstruction13 elements

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

No.

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 24

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 25

<InstdRmbrsmntAgtAcct>

Constraints

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

Exceptions and Investigations - Maintenance 2020 - 2021 23 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAcount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

3.4.4.2.1 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 181 for details)

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

No.

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

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

3.4.4.2.2 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following
elements (see "CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 24 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

3.4.4.2.3 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 181 for details)

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

No.

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

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

3.4.4.2.4 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following
elements (see "CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 25 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

3.4.5 InstructionForAssignee <InstrForAssgne>

Presence: [0..1]
Definition: Further information related to the processing of the investigation that may need to be acted
upon by the assignee.
InstructionForAssignee <InstrForAssgne> contains the following InstructionForAssignee1
elements

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

No.

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

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

3.4.5.1 Code <Cd>

Presence: [0..1]
Definition: Coded information related to the processing of the investigation instruction, provided by the
assigner, and intended for the assignee.
Datatype: "ExternalAgentInstruction1Code" on page 464

3.4.5.2 InstructionInformation <InstrInf>

Presence: [0..1]
Definition: Further information complementing the coded instruction or instruction to the assignee.
Datatype: "Max140Text" on page 482

3.4.6 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C22 "SupplementaryDataRule"

Exceptions and Investigations - Maintenance 2020 - 2021 26 December 2020

For evaluation by the Payments SEG DRAFT1camt.027.001.09 ClaimNonReceiptV09

SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on

page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 27 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

4 DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

4.1 MessageDefinition Functionality

Scope

The AdditionalPaymentInformation message is sent by an account servicing institution to an account

owner.

This message is used to provide additional or corrected information on a payment instruction or

statement entry, in order to allow reconciliation.

Usage

The AdditionalPaymentInformation message provides elements which are usually not reported in a
statement or advice (for example full remittance information or identification of parties other than the
account servicing institution and the account owner). It complements information about a payment
instruction that has already been received, in the form of one or several entries of the original payment
instruction.

The AdditionalPaymentInformation message covers one and only one original payment instruction. If
several payment instructions need further details, multiple AdditionalPaymentInformation messages
must be used, one for each of the payment instructions.

The AdditionalPaymentInformation message may be used as a result of two investigation processes

and in a way outlined below.

- A ClaimNonReceipt workflow raised by the creditor or recipient of the payment: This means that the
payment instruction has reached the creditor or beneficiary. The account owner needs further details or
correct information for its reconciliation processes. The AdditionalPaymentInformation can be used to
provide the missing information;

- A RequestToModifyPayment workflow raised by the debtor or one of the intermediate agents

upstream: When the payment instruction has reached its intended recipient and the modification does
not affect the accounting at the account servicing institution, this AdditionalPaymentInformation
message allows the account owner to receive further particulars or correct information about a payment
instruction or an entry passed to its account.

The AdditionalPayment Information message cannot be used to trigger a request for modification of a
payment instruction activity. A RequestToModifyPayment message must be used. In other words, if a
debtor or one of intermediate agent (excluding the account servicing institution of the creditor) realises
the some information was missing in the original payment instruction, he should not use an
AdditionalPaymentInformation but instead a RequestToModifyPayment message.

It is assumed that when an account servicing institution sends out an AdditionalPaymentInformation

message, the institution is fairly confident that this will resolve the case. Therefore it does not need to
wait for a Resolution Of Investigation message. Neither does the account owner, or whoever receives
the additional information, need to send back a ResolutionOfInvestigation message. Positive resolution
in this case is implicit. Both parties are expected to close the case. In the event that the problem does
not go away, a party can re-open the case.
Outline

Exceptions and Investigations - Maintenance 2020 - 2021 28 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

The AdditionalPaymentInformationV11 MessageDefinition is composed of 5 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. Underlying
Identifies the underlying payment instruction.

D. Information
Additional information to the underlying payment instruction.

E. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

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

Message root <Document> <AddtlPmtInf> [1..1]

Assignment <Assgnmt> [1..1] ± 32

Case <Case> [0..1] ± 33

Underlying <Undrlyg> [1..1] ± 33

Information <Inf> [1..1] ± C7, C9, 33

C15,
C16,
C17,
C18,
C19,
C20,
C24,
C26,
C27,
C28,
C29,
C25

SupplementaryData <SplmtryData> [0..*] ± C34 38

4.3 Constraints
C1 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)

Exceptions and Investigations - Maintenance 2020 - 2021 29 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

contiguous letters, and may be or not be withdrawn on the day the message containing the
Currency is exchanged.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

C7 CreditorAgentAccountRule
If CreditorAgentAccount is present, then CreditorAgent must be present.

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

Note: The decimal separator is a dot.

C9 DebtorAgentAccountRule
If DebtorAgentAccount is present, then DebtorAgent must be present.

C10 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C12 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C13 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

Exceptions and Investigations - Maintenance 2020 - 2021 30 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

C14 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C15 IntermediaryAgent1AccountRule
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.

C16 IntermediaryAgent1Rule
If IntermediaryAgent1 is present, then CreditorAgent must be present.

C17 IntermediaryAgent2AccountRule
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be present.

C18 IntermediaryAgent2Rule
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.

C19 IntermediaryAgent3AccountRule
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be present.

C20 IntermediaryAgent3Rule
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.

C21 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must
be present.

C22 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.

C23 OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

C24 PreviousInstructingAgent1AccountRule
If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must be
present.

C25 PreviousInstructingAgent1Guideline
It is recommended that, when present, PreviousInstructingAgent1 is the closest to the
DebtorAgent in the payment chain.

C26 PreviousInstructingAgent2AccountRule
If PreviousInstructingAgent2Account is present, then PreviousInstructingAgent2 must be
present.

C27 PreviousInstructingAgent2Rule
If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.

C28 PreviousInstructingAgent3AccountRule
If PreviousInstructingAgent3Account is present, then PreviousInstructingAgent3 must be
present.

Exceptions and Investigations - Maintenance 2020 - 2021 31 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

C29 PreviousInstructingAgent3Rule
If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be present.

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

C31 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C32 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C33 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C35 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C36 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

4.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

4.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.

Exceptions and Investigations - Maintenance 2020 - 2021 32 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

4.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

4.4.3 Underlying <Undrlyg>

Presence: [1..1]
Definition: Identifies the underlying payment instruction.
Underlying <Undrlyg> contains one of the following elements (see "UnderlyingTransaction7Choice"
on page 211 for details)

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

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

4.4.4 Information <Inf>

Presence: [1..1]
Definition: Additional information to the underlying payment instruction.
Impacted by: C7 "CreditorAgentAccountRule", C9 "DebtorAgentAccountRule", C15
"IntermediaryAgent1AccountRule", C16 "IntermediaryAgent1Rule", C17
"IntermediaryAgent2AccountRule", C18 "IntermediaryAgent2Rule", C19
"IntermediaryAgent3AccountRule", C20 "IntermediaryAgent3Rule", C24
"PreviousInstructingAgent1AccountRule", C26 "PreviousInstructingAgent2AccountRule", C27

Exceptions and Investigations - Maintenance 2020 - 2021 33 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

"PreviousInstructingAgent2Rule", C28 "PreviousInstructingAgent3AccountRule", C29

"PreviousInstructingAgent3Rule", C25 "PreviousInstructingAgent1Guideline"

Exceptions and Investigations - Maintenance 2020 - 2021 34 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

Information <Inf> contains the following elements (see "PaymentComplementaryInformation10" on

page 260 for details)

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

No.

InstructionIdentification <InstrId> [0..1] Text 264

EndToEndIdentification <EndToEndId> [0..1] Text 264

TransactionIdentification <TxId> [0..1] Text 265

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

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 265

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 266

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 266

Amount <Amt> [0..1] ± 266

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 266

ChargeBearer <ChrgBr> [0..1] CodeSet 267

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 268

DebtorAgent <DbtrAgt> [0..1] ± 269

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 269

SettlementInformation <SttlmInf> [0..1] C11, 270

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 272

ClearingSystem <ClrSys> [0..1] 273

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

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

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 274

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 275

<InstdRmbrsmntAgtAcct>

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

Exceptions and Investigations - Maintenance 2020 - 2021 35 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

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

No.

ThirdReimbursementAgentAccount [0..1] ± C10, C9 276

<ThrdRmbrsmntAgtAcct>

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

IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] ± C10, C9 277

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

IntermediaryAgent2Account <IntrmyAgt2Acct> [0..1] ± C10, C9 278

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

IntermediaryAgent3Account <IntrmyAgt3Acct> [0..1] ± C10, C9 279

CreditorAgent <CdtrAgt> [0..1] ± 279

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 280

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 281

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

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

InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text 282

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

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> [0..1] ± C10, C9 283

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

PreviousInstructingAgent2Account <PrvsInstgAgt2Acct> [0..1] ± C10, C9 284

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

PreviousInstructingAgent3Account <PrvsInstgAgt3Acct> [0..1] ± C10, C9 285

InstructionForNextAgent <InstrForNxtAgt> [0..*] 285

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

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

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

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

RemittanceInformation <RmtInf> [0..1] ± 287

Constraints

• CreditorAgentAccountRule
If CreditorAgentAccount is present, then CreditorAgent must be present.
On Condition
/CreditorAgent is absent
Following Must be True
/CreditorAgentAccount Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 36 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

• DebtorAgentAccountRule
If DebtorAgentAccount is present, then DebtorAgent must be present.
On Condition
/DebtorAgent is absent
Following Must be True
/DebtorAgentAccount Must be absent

• IntermediaryAgent1AccountRule
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.
On Condition
/IntermediaryAgent1 is absent
Following Must be True
/IntermediaryAgent1Account Must be absent

• IntermediaryAgent1Rule
If IntermediaryAgent1 is present, then CreditorAgent must be present.
On Condition
/IntermediaryAgent1 is present
Following Must be True
/CreditorAgent Must be present

• IntermediaryAgent2AccountRule
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be present.
On Condition
/IntermediaryAgent2 is absent
Following Must be True
/IntermediaryAgent2Account Must be absent

• IntermediaryAgent2Rule
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.
On Condition
/IntermediaryAgent2 is present
Following Must be True
/IntermediaryAgent1 Must be present

• IntermediaryAgent3AccountRule
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be present.
On Condition
/IntermediaryAgent3 is absent
Following Must be True
/IntermediaryAgent3Account Must be absent

• IntermediaryAgent3Rule
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.
On Condition
/IntermediaryAgent3 is present
Following Must be True
/IntermediaryAgent2 Must be present

• PreviousInstructingAgent1AccountRule
If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must be present.
On Condition
/PreviousInstructingAgent1 is absent
Following Must be True
/PreviousInstructingAgent1Account Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 37 December 2020

For evaluation by the Payments SEG DRAFT1camt.028.001.11
AdditionalPaymentInformationV11

• 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.
On Condition
/PreviousInstructingAgent2 is absent
Following Must be True
/PreviousInstructingAgent2Account Must be absent

• PreviousInstructingAgent2Rule
If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.
On Condition
/PreviousInstructingAgent2 is present
Following Must be True
/PreviousInstructingAgent1 Must be present

• PreviousInstructingAgent3AccountRule
If PreviousInstructingAgent3Account is present, then PreviousInstructingAgent3 must be present.
On Condition
/PreviousInstructingAgent3 is absent
Following Must be True
/PreviousInstructingAgent3Account Must be absent

• PreviousInstructingAgent3Rule
If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be present.
On Condition
/PreviousInstructingAgent3 is present
Following Must be True
/PreviousInstructingAgent2 Must be present

4.4.5 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C34 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 38 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5 DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.1 MessageDefinition Functionality

Scope

The ResolutionOfInvestigation message is sent by a case assignee to a case creator/case assigner.

This message is used to inform of the resolution of a case, and optionally provides details about.

- the corrective action undertaken by the case assignee;

- information on the return where applicable.

Usage

The ResolutionOfInvestigation message is used by the case assignee to inform a case creator or case
assigner about the resolution of a:

- request to cancel payment case;

- request to modify payment case;

- unable to apply case;

- claim non receipt case.

The ResolutionOfInvestigation message covers one and only one case at a time. If the case assignee
needs to communicate about several cases, then several Resolution Of Investigation messages must
be sent.

The ResolutionOfInvestigation message provides:

- the final outcome of the case, whether positive or negative;

- optionally, the details of the corrective action undertaken by the case assignee and the information of
the return.

Whenever a payment instruction has been generated to solve the case under investigation following a
claim non receipt or an unable to apply, the optional CorrectionTransaction component present in the
message must be completed.

Whenever the action of modifying or cancelling a payment results in funds being returned or reversed,
an investigating agent may provide the details in the resolution related investigation component, to
identify the return or reversal transaction. These details will facilitate the account reconciliations at the
initiating bank and the intermediaries. It must be stressed that the return or reversal of funds is outside
the scope of this Exceptions and Investigation service. The features given here is only meant to
transmit the information of return or reversal when it is available through the resolution of the case.

The ResolutionOfInvestigation message must:

- be forwarded by all subsequent case assignee(s) until it reaches the case creator;

Exceptions and Investigations - Maintenance 2020 - 2021 39 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

- not be used in place of a RejectCaseAssignment or CaseStatusReport or

NotificationOfCaseAssignment message.

Take note of an exceptional rule that allows the use of ResolutionOfInvestigation in lieu of a
CaseStatusReport. CaseStatusReport is a response-message to a CaseStatusReportRequest. The
latter which is sent when the assigner has reached its own time-out threshold to receive a response.
However it may happen that when the request arrives, the investigating agent has just obtained a
resolution. In such a situation, it would be redundant to send a CaseStatusReport when then followed
immediately by a ResolutionOfInvestigation. It is therefore quite acceptable for the investigating agent,
the assignee, to skip the Case Status Report and send the ResolutionOfInvestigation message directly.

The ResolutionOfInvestigation message should be the sole message to respond to a cancellation

request. Details of the underlying transactions and the related statuses for which the cancellation
request has been issued may be provided in the CancellationDetails component.
Outline
The ResolutionOfInvestigationV11 MessageDefinition is composed of 10 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. ResolvedCase
Identifies a resolved case.

C. Status
Indicates the status of the investigation.

D. CancellationDetails
Specifies the details of the underlying transactions being cancelled.

E. ModificationDetails
Specifies the details of the underlying transaction being modified.

F. ClaimNonReceiptDetails
Specifies the details of the underlying transaction for which a claim non receipt has been initiated.

G. StatementDetails
Details on the underlying statement entry.

H. CorrectionTransaction
References a transaction initiated to fix the case under investigation.

I. ResolutionRelatedInformation
Reference to fix the case under investigation as part of the resolution.

J. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

Exceptions and Investigations - Maintenance 2020 - 2021 40 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

Message root <Document> <RsltnOfInvstgtn> [1..1] C22,

C23,
C24,
C25,
C28

Assignment <Assgnmt> [1..1] ± 47

ResolvedCase <RslvdCase> [0..1] ± 47

Status <Sts> [1..1] ± 48

CancellationDetails <CxlDtls> [0..*] C12, 48

C13,
C14

OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts> [0..1] C7, C26 50

OriginalGroupCancellationIdentification <OrgnlGrpCxlId> [0..1] Text 51

ResolvedCase <RslvdCase> [0..1] ± 52

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 52

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 52

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 52

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 52

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 52

GroupCancellationStatus <GrpCxlSts> [0..1] CodeSet 52

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 53

NumberOfTransactionsPerCancellationStatus [0..*] 53
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 53

DetailedStatus <DtldSts> [1..1] CodeSet 53

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 54

OriginalPaymentInformationAndStatus <OrgnlPmtInfAndSts> [0..*] C8, C29, 54

C27

OriginalPaymentInformationCancellationIdentification [0..1] Text 56

<OrgnlPmtInfCxlId>

ResolvedCase <RslvdCase> [0..1] ± 56

OriginalPaymentInformationIdentification <OrgnlPmtInfId> [1..1] Text 56

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 56

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 56

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 57

Exceptions and Investigations - Maintenance 2020 - 2021 41 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

PaymentInformationCancellationStatus <PmtInfCxlSts> [0..1] CodeSet 57

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 57

NumberOfTransactionsPerCancellationStatus [0..*] 57
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 58

DetailedStatus <DtldSts> [1..1] CodeSet 58

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 58

TransactionInformationAndStatus <TxInfAndSts> [0..*] ± 58

TransactionInformationAndStatus <TxInfAndSts> [0..*] ± 60

ModificationDetails <ModDtls> [0..1] ± 63

ClaimNonReceiptDetails <ClmNonRctDtls> [0..1] 66

{Or Accepted <Accptd> [1..1] 66

DateProcessed <DtPrcd> [1..1] Date 66

OriginalNextAgent <OrgnlNxtAgt> [0..1] ± 67

Or} Rejected <Rjctd> [1..1] 67

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

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

StatementDetails <StmtDtls> [0..1] ± 67

CorrectionTransaction <CrrctnTx> [0..1] 68

{Or Initiation <Initn> [1..1] C18, 69

C30

GroupHeader <GrpHdr> [0..1] 70

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

MessageNameIdentification <MsgNmId> [1..1] Text 71

CreationDateTime <CreDtTm> [0..1] DateTime 71

PaymentInformationIdentification <PmtInfId> [0..1] Text 71

InstructionIdentification <InstrId> [0..1] Text 71

EndToEndIdentification <EndToEndId> [0..1] Text 71

UETR <UETR> [0..1] IdentifierSet 72

InstructedAmount <InstdAmt> [1..1] Amount C2, C10 72

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 72

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 72

Or} Interbank <IntrBk> [1..1] C19 73

Exceptions and Investigations - Maintenance 2020 - 2021 42 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

GroupHeader <GrpHdr> [0..1] 73

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

MessageNameIdentification <MsgNmId> [1..1] Text 74

CreationDateTime <CreDtTm> [0..1] DateTime 74

InstructionIdentification <InstrId> [0..1] Text 74

EndToEndIdentification <EndToEndId> [0..1] Text 74

TransactionIdentification <TxId> [0..1] Text 74

UETR <UETR> [0..1] IdentifierSet 75

InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] Amount C2, C10 75

InterbankSettlementDate <IntrBkSttlmDt> [1..1] Date 75

ResolutionRelatedInformation <RsltnRltdInf> [0..1] 75

EndToEndIdentification <EndToEndId> [0..1] Text 76

TransactionIdentification <TxId> [0..1] Text 76

UETR <UETR> [0..1] IdentifierSet 76

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C2, C10 76

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 77

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

Compensation <Compstn> [0..1] ± 77

Charges <Chrgs> [0..*] ± 78

SupplementaryData <SplmtryData> [0..*] ± C35 78

5.3 Constraints
C1 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.

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

C3 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

Exceptions and Investigations - Maintenance 2020 - 2021 43 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

C4 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

C7 CancellationStatusReasonInformationRule
If GroupCancellationStatus is present and is different from RJCR or PNCR, then
CancellationStatusReasonInformation/AdditionalInformation is not allowed.

C8 CancellationStatusReasonInformationRule
If PaymentInformationCancellationStatus is present and is different from RJCR
(RejectedCancellationRequest) or PNCR (PendingCancellationRequest), then
CancellationStatusReasonInformation/AdditionalInformation is not allowed.

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

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

Note: The decimal separator is a dot.

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

Note: The decimal separator is a dot.

C12 GroupOrInitiationTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus
level, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

C13 GroupOrInterbankTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus
level, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

C14 GroupOrPaymentInformationResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus
level, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

C15 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

Exceptions and Investigations - Maintenance 2020 - 2021 44 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

C17 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C18 IdentificationRule
Either InstructionIdentification, EndToEndIdentification or UETR must be present.

C19 IdentificationRule
Either InstructionIdentification, EndToEndIdentification, TransactionIdentification or UETR must
be present.

C20 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C21 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C22 MessageOrGroupResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/ResolvedCase is present
And /CancellationDetails[1] is present
And /CancellationDetails[1]/OriginalGroupInformationAndStatus[1] is
present
Following Must be True
/CancellationDetails[1]/OriginalGroupInformationAndStatus/ResolvedCase
Must be absent
This constraint is defined at the MessageDefinition level.

C23 MessageOrInitiationTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/ResolvedCase is present
And /CancellationDetails[1] is present
And /CancellationDetails[1]/OriginalPaymentInformationAndStatus[*] is
present
And /CancellationDetails[1]/OriginalPaymentInformationAndStatus[*]/
TransactionInformationAndStatus[*] is present
Following Must be True
/CancellationDetails[*]/OriginalPaymentInformationAndStatus[*]/
TransactionInformationAndStatus[*]/ResolvedCase Must be absent
This constraint is defined at the MessageDefinition level.

C24 MessageOrInterbankTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

Exceptions and Investigations - Maintenance 2020 - 2021 45 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

On Condition
/ResolvedCase is present
And /CancellationDetails[1] is present
And /CancellationDetails[1]/TransactionInformationAndStatus[*] is present
Following Must be True
/CancellationDetails[*]/TransactionInformationAndStatus[*]/ResolvedCase
Must be absent
This constraint is defined at the MessageDefinition level.

C25 MessageOrPaymentInformationResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/ResolvedCase is present
And /CancellationDetails[1] is present
And /CancellationDetails[1]/OriginalPaymentInformationAndStatus[1] is
present
Following Must be True
/CancellationDetails[*]/OriginalPaymentInformationAndStatus[*]/
ResolvedCase Must be absent
This constraint is defined at the MessageDefinition level.

C26 NumberOfTransactionsPerCancellationStatusGuideline
OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if
GroupCancellationStatus equals PACR.

C27 NumberOfTransactionsPerCancellationStatusGuideline
OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if
GroupCancellationStatus equals PACR (PartialCancellationRequest).

C28 PartialOrRejectedCancellationRule
If Status/Confirmation is present and equal to PECR or RJCR then CancellationDetails must be
present.
On Condition
/Status/Confirmation is present
And /Status/Confirmation is within DataType <<Code>>
InvestigationExecutionConfirmation4Code
Following Must be True
/CancellationDetails[*] Must be present
This constraint is defined at the MessageDefinition level.

C29 PaymentInformationOrTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus
level, OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

C30 RequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

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

C32 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

Exceptions and Investigations - Maintenance 2020 - 2021 46 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

C33 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C34 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C36 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C37 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

5.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

5.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

5.4.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies a resolved case.

Exceptions and Investigations - Maintenance 2020 - 2021 47 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

5.4.3 Status <Sts>

Presence: [1..1]
Definition: Indicates the status of the investigation.
Status <Sts> contains one of the following elements (see "InvestigationStatus5Choice" on page 185
for details)

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

No.

{Or Confirmation <Conf> [1..1] CodeSet 186

Or RejectedModification <RjctdMod> [1..*] 186

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

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

Or DuplicateOf <DplctOf> [1..1] ± 186

Or} AssignmentCancellationConfirmation <AssgnmtCxlConf> [1..1] Indicator 187

5.4.4 CancellationDetails <CxlDtls>

Presence: [0..*]
Definition: Specifies the details of the underlying transactions being cancelled.
Impacted by: C12 "GroupOrInitiationTransactionResolvedCaseRule", C13
"GroupOrInterbankTransactionResolvedCaseRule", C14
"GroupOrPaymentInformationResolvedCaseRule"

Exceptions and Investigations - Maintenance 2020 - 2021 48 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

CancellationDetails <CxlDtls> contains the following UnderlyingTransaction29 elements

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

No.

OriginalGroupInformationAndStatus [0..1] C7, C26 50

<OrgnlGrpInfAndSts>

OriginalGroupCancellationIdentification [0..1] Text 51

<OrgnlGrpCxlId>

ResolvedCase <RslvdCase> [0..1] ± 52

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 52

OriginalMessageNameIdentification [1..1] Text 52

<OrgnlMsgNmId>

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 52

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 52

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 52

GroupCancellationStatus <GrpCxlSts> [0..1] CodeSet 52

CancellationStatusReasonInformation [0..*] ± 53
<CxlStsRsnInf>

NumberOfTransactionsPerCancellationStatus [0..*] 53
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 53

DetailedStatus <DtldSts> [1..1] CodeSet 53

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 54

OriginalPaymentInformationAndStatus [0..*] C8, C29, 54

<OrgnlPmtInfAndSts> C27

OriginalPaymentInformationCancellationIdentificati [0..1] Text 56

on <OrgnlPmtInfCxlId>

ResolvedCase <RslvdCase> [0..1] ± 56

OriginalPaymentInformationIdentification [1..1] Text 56

<OrgnlPmtInfId>

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 56

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 56

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 57

PaymentInformationCancellationStatus [0..1] CodeSet 57

<PmtInfCxlSts>

CancellationStatusReasonInformation [0..*] ± 57
<CxlStsRsnInf>

NumberOfTransactionsPerCancellationStatus [0..*] 57
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 58

DetailedStatus <DtldSts> [1..1] CodeSet 58

Exceptions and Investigations - Maintenance 2020 - 2021 49 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 58

TransactionInformationAndStatus <TxInfAndSts> [0..*] ± 58

TransactionInformationAndStatus <TxInfAndSts> [0..*] ± 60

Constraints

• GroupOrInitiationTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus level,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/OriginalGroupInformationAndStatus is present
And /OriginalGroupInformationAndStatus/ResolvedCase is present
And /OriginalPaymentInformationAndStatus[1] is present
And /OriginalPaymentInformationAndStatus[1]/
TransactionInformationAndStatus[1] is present
Following Must be True
/OriginalPaymentInformationAndStatus[*]/TransactionInformationAndStatus[*]/
ResolvedCase Must be absent

• GroupOrInterbankTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus level,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/OriginalGroupInformationAndStatus is present
And /OriginalGroupInformationAndStatus/ResolvedCase is present
And /TransactionInformationAndStatus[1] is present
Following Must be True
/TransactionInformationAndStatus[*]/ResolvedCase Must be absent

• GroupOrPaymentInformationResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus level,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.
On Condition
/OriginalGroupInformationAndStatus is present
And /OriginalGroupInformationAndStatus/ResolvedCase is present
And /OriginalPaymentInformationAndStatus[1] is present
Following Must be True
/OriginalPaymentInformationAndStatus[*]/ResolvedCase Must be absent

5.4.4.1 OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts>

Presence: [0..1]
Definition: Provides information on the original cancellation message, to which the resolution refers.
Impacted by: C7 "CancellationStatusReasonInformationRule", C26
"NumberOfTransactionsPerCancellationStatusGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 50 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

OriginalGroupInformationAndStatus <OrgnlGrpInfAndSts> contains the following

OriginalGroupHeader14 elements

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

No.

OriginalGroupCancellationIdentification [0..1] Text 51

<OrgnlGrpCxlId>

ResolvedCase <RslvdCase> [0..1] ± 52

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 52

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 52

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 52

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 52

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 52

GroupCancellationStatus <GrpCxlSts> [0..1] CodeSet 52

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 53

NumberOfTransactionsPerCancellationStatus [0..*] 53
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 53

DetailedStatus <DtldSts> [1..1] CodeSet 53

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 54

Constraints

• CancellationStatusReasonInformationRule
If GroupCancellationStatus is present and is different from RJCR or PNCR, then
CancellationStatusReasonInformation/AdditionalInformation is not allowed.
On Condition
/CancellationStatusReasonInformation[1] is present
And /CancellationStatusReasonInformation[*]/AdditionalInformation[*] is
present
And /GroupCancellationStatus is present
Following Must be True
/GroupCancellationStatus Must be equal to value 'PendingCancellationRequest'
Or /GroupCancellationStatus Must be equal to value
'RejectedCancellationRequest'

• NumberOfTransactionsPerCancellationStatusGuideline
OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if
GroupCancellationStatus equals PACR.

5.4.4.1.1 OriginalGroupCancellationIdentification <OrgnlGrpCxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original assigner, to unambiguously identify the
original group cancellation request.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 51 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.4.1.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies the case.
ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

5.4.4.1.3 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]
Definition: Point to point reference, as assigned by the original instructing party, to unambiguously
identify the original message.
Datatype: "Max35Text" on page 483

5.4.4.1.4 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

5.4.4.1.5 OriginalCreationDateTime <OrgnlCreDtTm>

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

5.4.4.1.6 OriginalNumberOfTransactions <OrgnlNbOfTxs>

Presence: [0..1]
Definition: Number of individual transactions contained in the original message.
Datatype: "Max15NumericText" on page 482

5.4.4.1.7 OriginalControlSum <OrgnlCtrlSum>

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

5.4.4.1.8 GroupCancellationStatus <GrpCxlSts>

Presence: [0..1]
Definition: Specifies the status of a group cancellation request.
Datatype: "GroupCancellationStatus1Code" on page 472

Exceptions and Investigations - Maintenance 2020 - 2021 52 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

CodeName Name Definition

PACR PartiallyAcceptedCancellationRequest Cancellation is partially accepted.

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

5.4.4.1.9 CancellationStatusReasonInformation <CxlStsRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation status reason.
CancellationStatusReasonInformation <CxlStsRsnInf> contains the following elements (see
"CancellationStatusReason4" on page 446 for details)

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

No.

Originator <Orgtr> [0..1] ± 446

Reason <Rsn> [0..1] 446

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

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

AdditionalInformation <AddtlInf> [0..*] Text 447

5.4.4.1.10 NumberOfTransactionsPerCancellationStatus <NbOfTxsPerCxlSts>

Presence: [0..*]
Definition: Detailed information on the number of transactions for each identical cancellation status.
NumberOfTransactionsPerCancellationStatus <NbOfTxsPerCxlSts> contains the following
NumberOfTransactionsPerStatus1 elements

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

No.

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 53

DetailedStatus <DtldSts> [1..1] CodeSet 53

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 54

5.4.4.1.10.1 DetailedNumberOfTransactions <DtldNbOfTxs>

Presence: [1..1]
Definition: Number of individual transactions contained in the message, detailed per status.
Datatype: "Max15NumericText" on page 482

5.4.4.1.10.2 DetailedStatus <DtldSts>

Presence: [1..1]
Definition: Common transaction status for all individual transactions reported with the same status.
Datatype: "TransactionIndividualStatus1Code" on page 476

Exceptions and Investigations - Maintenance 2020 - 2021 53 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

CodeName Name Definition

ACTC AcceptedTechnicalValidation Authentication and syntactical and

semantical validation are successful.

RJCT Rejected Payment initiation or individual

transaction included in the payment
initiation has been rejected.

PDNG Pending Payment initiation or individual

transaction included in the payment
initiation is pending. Further checks and
status update will be performed.

ACCP AcceptedCustomerProfile Preceding check of technical validation

was successful. Customer profile check
was also successful.

ACSP AcceptedSettlementInProcess All preceding checks such as technical

validation and customer profile were
successful and therefore the payment
initiation has been accepted for
execution.

ACSC AcceptedSettlementCompleted Settlement on the debtor's account has

been completed.

Usage : this can be used by the first

agent to report to the debtor that the
transaction has been completed.
Warning : this status is provided for
transaction status reasons, not for
financial information. It can only be used
after bilateral agreement

ACCR AcceptedCancellationRequest Cancellation is accepted.

ACWC AcceptedWithChange Instruction is accepted but a change will

be made, such as date or remittance not
sent.

5.4.4.1.10.3 DetailedControlSum <DtldCtrlSum>

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

5.4.4.2 OriginalPaymentInformationAndStatus <OrgnlPmtInfAndSts>

Presence: [0..*]
Definition: Provides information on the original (group of) transactions, to which the cancellation status
refers.
Impacted by: C8 "CancellationStatusReasonInformationRule", C29
"PaymentInformationOrTransactionResolvedCaseRule", C27
"NumberOfTransactionsPerCancellationStatusGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 54 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

OriginalPaymentInformationAndStatus <OrgnlPmtInfAndSts> contains the following

OriginalPaymentInstruction43 elements

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

No.

OriginalPaymentInformationCancellationIdentificatio [0..1] Text 56

n <OrgnlPmtInfCxlId>

ResolvedCase <RslvdCase> [0..1] ± 56

OriginalPaymentInformationIdentification [1..1] Text 56

<OrgnlPmtInfId>

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 56

OriginalNumberOfTransactions <OrgnlNbOfTxs> [0..1] Text 56

OriginalControlSum <OrgnlCtrlSum> [0..1] Quantity 57

PaymentInformationCancellationStatus [0..1] CodeSet 57

<PmtInfCxlSts>

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 57

NumberOfTransactionsPerCancellationStatus [0..*] 57
<NbOfTxsPerCxlSts>

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 58

DetailedStatus <DtldSts> [1..1] CodeSet 58

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 58

TransactionInformationAndStatus <TxInfAndSts> [0..*] ± 58

Constraints

• CancellationStatusReasonInformationRule
If PaymentInformationCancellationStatus is present and is different from RJCR
(RejectedCancellationRequest) or PNCR (PendingCancellationRequest), then
CancellationStatusReasonInformation/AdditionalInformation is not allowed.
On Condition
/CancellationStatusReasonInformation[1] is present
And /CancellationStatusReasonInformation[*]/AdditionalInformation[*] is
present
And /PaymentInformationCancellationStatus is present
Following Must be True
/PaymentInformationCancellationStatus Must be equal to value
'PendingCancellationRequest'
Or /PaymentInformationCancellationStatus Must be equal to value
'RejectedCancellationRequest'

• NumberOfTransactionsPerCancellationStatusGuideline
OriginalGroupInformationAndStatus/NumberOfTransactionsPerStatus should only be present if
GroupCancellationStatus equals PACR (PartialCancellationRequest).

• PaymentInformationOrTransactionResolvedCaseRule
ResolvedCase may be present at either ResolvedCase, OriginalGroupInformationAndStatus level,
OriginalPaymentInformationAndStatus or TransactionInformationAndStatus level.

Exceptions and Investigations - Maintenance 2020 - 2021 55 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

On Condition
/ResolvedCase is present
And /TransactionInformationAndStatus[1] is present
Following Must be True
/TransactionInformationAndStatus[*]/ResolvedCase Must be absent

5.4.4.2.1 OriginalPaymentInformationCancellationIdentification <OrgnlPmtInfCxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original assigner, to unambiguously identify the
original payment information cancellation request.
Datatype: "Max35Text" on page 483

5.4.4.2.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies the resolved case.
ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

5.4.4.2.3 OriginalPaymentInformationIdentification <OrgnlPmtInfId>

Presence: [1..1]
Definition: Unique identification, as assigned by the original sending party, to unambiguously identify the
original payment information group.
Datatype: "Max35Text" on page 483

5.4.4.2.4 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Provides information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

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

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

5.4.4.2.5 OriginalNumberOfTransactions <OrgnlNbOfTxs>

Presence: [0..1]
Definition: Number of individual transactions contained in the original payment information group.

Exceptions and Investigations - Maintenance 2020 - 2021 56 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

Datatype: "Max15NumericText" on page 482

5.4.4.2.6 OriginalControlSum <OrgnlCtrlSum>

Presence: [0..1]
Definition: Total of all individual amounts included in the original payment information group,
irrespective of currencies.
Datatype: "DecimalNumber" on page 480

5.4.4.2.7 PaymentInformationCancellationStatus <PmtInfCxlSts>

Presence: [0..1]
Definition: Specifies the status of a cancellation request, related to a payment information group.
Datatype: "GroupCancellationStatus1Code" on page 472

CodeName Name Definition

PACR PartiallyAcceptedCancellationRequest Cancellation is partially accepted.

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

5.4.4.2.8 CancellationStatusReasonInformation <CxlStsRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation status reason.
CancellationStatusReasonInformation <CxlStsRsnInf> contains the following elements (see
"CancellationStatusReason4" on page 446 for details)

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

No.

Originator <Orgtr> [0..1] ± 446

Reason <Rsn> [0..1] 446

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

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

AdditionalInformation <AddtlInf> [0..*] Text 447

5.4.4.2.9 NumberOfTransactionsPerCancellationStatus <NbOfTxsPerCxlSts>

Presence: [0..*]
Definition: Detailed information on the number of transactions for each identical cancellation status.

Exceptions and Investigations - Maintenance 2020 - 2021 57 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

NumberOfTransactionsPerCancellationStatus <NbOfTxsPerCxlSts> contains the following

NumberOfCancellationsPerStatus1 elements

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

No.

DetailedNumberOfTransactions <DtldNbOfTxs> [1..1] Text 58

DetailedStatus <DtldSts> [1..1] CodeSet 58

DetailedControlSum <DtldCtrlSum> [0..1] Quantity 58

5.4.4.2.9.1 DetailedNumberOfTransactions <DtldNbOfTxs>

Presence: [1..1]
Definition: Number of individual cancellation requests contained in the message, detailed per status.
Datatype: "Max15NumericText" on page 482

5.4.4.2.9.2 DetailedStatus <DtldSts>

Presence: [1..1]
Definition: Common cancellation request status for all individual cancellation requests reported.
Datatype: "CancellationIndividualStatus1Code" on page 461

CodeName Name Definition

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

5.4.4.2.9.3 DetailedControlSum <DtldCtrlSum>

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

5.4.4.2.10 TransactionInformationAndStatus <TxInfAndSts>

Presence: [0..*]
Definition: Provides information on the original transactions to which the cancellation request message
refers.

Exceptions and Investigations - Maintenance 2020 - 2021 58 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

TransactionInformationAndStatus <TxInfAndSts> contains the following elements (see

"PaymentTransaction139" on page 309 for details)

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

No.

CancellationStatusIdentification <CxlStsId> [0..1] Text 311

ResolvedCase <RslvdCase> [0..1] ± 311

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 312

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 312

UETR <UETR> [0..1] IdentifierSet 312

TransactionCancellationStatus <TxCxlSts> [0..1] CodeSet 312

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 312

OriginalInstructedAmount <OrgnlInstdAmt> [0..1] Amount C1, C7 313

OriginalRequestedExecutionDate <OrgnlReqdExctnDt> [0..1] ± 313

OriginalRequestedCollectionDate <OrgnlReqdColltnDt> [0..1] Date 314

OriginalTransactionReference <OrgnlTxRef> [0..1] 314

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 316

Amount <Amt> [0..1] ± 316

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 317

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 317

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 317

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 317

SettlementInformation <SttlmInf> [0..1] C11, 317

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 320

ClearingSystem <ClrSys> [0..1] 320

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

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

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 321

<InstgRmbrsmntAgtAcct>

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

Exceptions and Investigations - Maintenance 2020 - 2021 59 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

InstructedReimbursementAgentAccount [0..1] ± C10, C9 322

<InstdRmbrsmntAgtAcct>

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

ThirdReimbursementAgentAccount [0..1] ± C10, C9 323

<ThrdRmbrsmntAgtAcct>

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

PaymentMethod <PmtMtd> [0..1] CodeSet 325

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

RemittanceInformation <RmtInf> [0..1] ± 326

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 326

DebtorAgent <DbtrAgt> [0..1] ± 327

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 327

CreditorAgent <CdtrAgt> [0..1] ± 328

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 328

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 329

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

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

5.4.4.3 TransactionInformationAndStatus <TxInfAndSts>

Presence: [0..*]
Definition: Provides details on the original transactions to which the cancellation request message
refers.

Exceptions and Investigations - Maintenance 2020 - 2021 60 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

TransactionInformationAndStatus <TxInfAndSts> contains the following elements (see

"PaymentTransaction138" on page 331 for details)

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

No.

CancellationStatusIdentification <CxlStsId> [0..1] Text 334

ResolvedCase <RslvdCase> [0..1] ± 334

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 334

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 334

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 334

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 335

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 335

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 335

TransactionCancellationStatus <TxCxlSts> [0..1] CodeSet 335

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 335

ResolutionRelatedInformation <RsltnRltdInf> [0..1] 336

EndToEndIdentification <EndToEndId> [0..1] Text 336

TransactionIdentification <TxId> [0..1] Text 336

UETR <UETR> [0..1] IdentifierSet 336

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 336

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 337

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

Compensation <Compstn> [0..1] ± 337

Charges <Chrgs> [0..*] ± 338

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 338

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 339

Assigner <Assgnr> [0..1] ± 339

Assignee <Assgne> [0..1] ± 339

OriginalTransactionReference <OrgnlTxRef> [0..1] 339

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 341

Amount <Amt> [0..1] ± 341

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 342

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 342

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 342

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 342

Exceptions and Investigations - Maintenance 2020 - 2021 61 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

SettlementInformation <SttlmInf> [0..1] C11, 342

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 345

ClearingSystem <ClrSys> [0..1] 345

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

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

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 346

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 347

<InstdRmbrsmntAgtAcct>

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

ThirdReimbursementAgentAccount [0..1] ± C10, C9 348

<ThrdRmbrsmntAgtAcct>

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

PaymentMethod <PmtMtd> [0..1] CodeSet 350

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

RemittanceInformation <RmtInf> [0..1] ± 351

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 351

DebtorAgent <DbtrAgt> [0..1] ± 352

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 352

CreditorAgent <CdtrAgt> [0..1] ± 353

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 353

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 354

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 62 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.5 ModificationDetails <ModDtls>

Presence: [0..1]
Definition: Specifies the details of the underlying transaction being modified.

Exceptions and Investigations - Maintenance 2020 - 2021 63 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

ModificationDetails <ModDtls> contains the following elements (see "PaymentTransaction132" on

page 379 for details)

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

No.

ModificationStatusIdentification <ModStsId> [0..1] Text 382

ResolvedCase <RslvdCase> [0..1] ± 382

OriginalGroupInformation <OrgnlGrpInf> [1..1] ± 382

OriginalPaymentInformationIdentification [0..1] Text 382

<OrgnlPmtInfId>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 383

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 383

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 383

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 383

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 383

ModificationStatusReasonInformation <ModStsRsnInf> [0..*] 383

Originator <Orgtr> [0..1] ± 384

Reason <Rsn> [0..1] 384

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

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

AdditionalInformation <AddtlInf> [0..*] Text 385

ResolutionRelatedInformation <RsltnRltdInf> [0..1] 385

EndToEndIdentification <EndToEndId> [0..1] Text 385

TransactionIdentification <TxId> [0..1] Text 385

UETR <UETR> [0..1] IdentifierSet 385

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 386

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 386

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

Compensation <Compstn> [0..1] ± 386

Charges <Chrgs> [0..*] ± 387

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 387

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 388

Assigner <Assgnr> [0..1] ± 388

Assignee <Assgne> [0..1] ± 388

OriginalTransactionReference <OrgnlTxRef> [0..1] 388

Exceptions and Investigations - Maintenance 2020 - 2021 64 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 390

Amount <Amt> [0..1] ± 390

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 391

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 391

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 391

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 391

SettlementInformation <SttlmInf> [0..1] C11, 391

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 394

ClearingSystem <ClrSys> [0..1] 394

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

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

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 395

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 396

<InstdRmbrsmntAgtAcct>

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

ThirdReimbursementAgentAccount [0..1] ± C10, C9 397

<ThrdRmbrsmntAgtAcct>

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

PaymentMethod <PmtMtd> [0..1] CodeSet 399

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

RemittanceInformation <RmtInf> [0..1] ± 400

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 400

DebtorAgent <DbtrAgt> [0..1] ± 401

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 401

Exceptions and Investigations - Maintenance 2020 - 2021 65 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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

No.

CreditorAgent <CdtrAgt> [0..1] ± 402

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 402

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 403

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

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

5.4.6 ClaimNonReceiptDetails <ClmNonRctDtls>

Presence: [0..1]
Definition: Specifies the details of the underlying transaction for which a claim non receipt has been
initiated.
ClaimNonReceiptDetails <ClmNonRctDtls> contains one of the following ClaimNonReceipt2Choice
elements

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

No.

{Or Accepted <Accptd> [1..1] 66

DateProcessed <DtPrcd> [1..1] Date 66

OriginalNextAgent <OrgnlNxtAgt> [0..1] ± 67

Or} Rejected <Rjctd> [1..1] 67

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

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

5.4.6.1 Accepted <Accptd>

Presence: [1..1]
Definition: Claim non-receipt is accepted and processed by the agent.
Accepted <Accptd> contains the following ClaimNonReceipt2 elements

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

No.

DateProcessed <DtPrcd> [1..1] Date 66

OriginalNextAgent <OrgnlNxtAgt> [0..1] ± 67

5.4.6.1.1 DateProcessed <DtPrcd>

Presence: [1..1]
Definition: Specifies the date the original payment instruction was processed.
Datatype: "ISODate" on page 477

Exceptions and Investigations - Maintenance 2020 - 2021 66 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.6.1.2 OriginalNextAgent <OrgnlNxtAgt>

Presence: [0..1]
Definition: Specifies the next party the original payment instruction was sent to.
OriginalNextAgent <OrgnlNxtAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

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

No.

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

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

5.4.6.2 Rejected <Rjctd>

Presence: [1..1]
Definition: Specifies that the claim non receipt has been rejected and provides the reason for the
rejection.
Rejected <Rjctd> contains one of the following ClaimNonReceiptRejectReason1Choice elements

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

No.

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

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

5.4.6.2.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the rejection, in a coded form.
Datatype: "ExternalClaimNonReceiptRejection1Code" on page 466

5.4.6.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the rejection, in a proprietary form.
Datatype: "Max35Text" on page 483

5.4.7 StatementDetails <StmtDtls>

Presence: [0..1]
Definition: Details on the underlying statement entry.

Exceptions and Investigations - Maintenance 2020 - 2021 67 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

StatementDetails <StmtDtls> contains the following elements (see "StatementResolutionEntry4" on

page 189 for details)

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

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 189

OriginalStatementIdentification <OrgnlStmtId> [0..1] Text 189

UETR <UETR> [0..1] IdentifierSet 190

AccountServicerReference <AcctSvcrRef> [0..1] Text 190

CorrectedAmount <CrrctdAmt> [0..1] Amount C1, C7 190

Charges <Chrgs> [0..*] ± 190

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

5.4.8 CorrectionTransaction <CrrctnTx>

Presence: [0..1]
Definition: References a transaction initiated to fix the case under investigation.

Exceptions and Investigations - Maintenance 2020 - 2021 68 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

CorrectionTransaction <CrrctnTx> contains one of the following CorrectiveTransaction5Choice

elements

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

No.

{Or Initiation <Initn> [1..1] C18, 69

C30

GroupHeader <GrpHdr> [0..1] 70

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

MessageNameIdentification <MsgNmId> [1..1] Text 71

CreationDateTime <CreDtTm> [0..1] DateTime 71

PaymentInformationIdentification <PmtInfId> [0..1] Text 71

InstructionIdentification <InstrId> [0..1] Text 71

EndToEndIdentification <EndToEndId> [0..1] Text 71

UETR <UETR> [0..1] IdentifierSet 72

InstructedAmount <InstdAmt> [1..1] Amount C2, C10 72

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 72

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 72

Or} Interbank <IntrBk> [1..1] C19 73

GroupHeader <GrpHdr> [0..1] 73

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

MessageNameIdentification <MsgNmId> [1..1] Text 74

CreationDateTime <CreDtTm> [0..1] DateTime 74

InstructionIdentification <InstrId> [0..1] Text 74

EndToEndIdentification <EndToEndId> [0..1] Text 74

TransactionIdentification <TxId> [0..1] Text 74

UETR <UETR> [0..1] IdentifierSet 75

InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] Amount C2, C10 75

InterbankSettlementDate <IntrBkSttlmDt> [1..1] Date 75

5.4.8.1 Initiation <Initn>

Presence: [1..1]
Definition: Set of elements used to reference the details of the corrective payment initiation.
Impacted by: C18 "IdentificationRule", C30 "RequestedDateRule"

Exceptions and Investigations - Maintenance 2020 - 2021 69 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

Initiation <Initn> contains the following CorrectivePaymentInitiation5 elements

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

No.

GroupHeader <GrpHdr> [0..1] 70

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

MessageNameIdentification <MsgNmId> [1..1] Text 71

CreationDateTime <CreDtTm> [0..1] DateTime 71

PaymentInformationIdentification <PmtInfId> [0..1] Text 71

InstructionIdentification <InstrId> [0..1] Text 71

EndToEndIdentification <EndToEndId> [0..1] Text 71

UETR <UETR> [0..1] IdentifierSet 72

InstructedAmount <InstdAmt> [1..1] Amount C2, C10 72

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 72

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 72

Constraints

• IdentificationRule
Either InstructionIdentification, EndToEndIdentification or UETR must be present.
Following Must be True
/InstructionIdentification Must be present
And /EndToEndIdentification Must be present
And /UETR Must be present

• RequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.
Following Must be True
/RequestedExecutionDate Must be present
And /RequestedCollectionDate Must be present

5.4.8.1.1 GroupHeader <GrpHdr>

Presence: [0..1]
Definition: Set of elements used to provide corrective information for the group header of the message
under investigation.
GroupHeader <GrpHdr> contains the following CorrectiveGroupInformation1 elements

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

No.

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

MessageNameIdentification <MsgNmId> [1..1] Text 71

CreationDateTime <CreDtTm> [0..1] DateTime 71

Exceptions and Investigations - Maintenance 2020 - 2021 70 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.8.1.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 483

5.4.8.1.1.2 MessageNameIdentification <MsgNmId>

Presence: [1..1]
Definition: Specifies the message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

5.4.8.1.1.3 CreationDateTime <CreDtTm>

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

5.4.8.1.2 PaymentInformationIdentification <PmtInfId>

Presence: [0..1]
Definition: Unique identification, as assigned by a sending party, to unambiguously identify the payment
information group within the message.
Datatype: "Max35Text" on page 483

5.4.8.1.3 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 483

5.4.8.1.4 EndToEndIdentification <EndToEndId>

Presence: [0..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 483

Exceptions and Investigations - Maintenance 2020 - 2021 71 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.8.1.5 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

5.4.8.1.6 InstructedAmount <InstdAmt>

Presence: [1..1]
Definition: Amount of money to be moved between the debtor and creditor, before deduction of
charges, expressed in the currency as ordered by the initiating party.
Impacted by: C2 "ActiveOrHistoricCurrency", C10 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

5.4.8.1.7 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date or date time at which the initiating party requests the clearing agent to process the
payment.

Usage: This is the date or date time on which the debtor's account is to be debited. If payment by
cheque, the date when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

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

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

5.4.8.1.8 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date at which the creditor requests the amount of money to be collected from the debtor.
Datatype: "ISODate" on page 477

Exceptions and Investigations - Maintenance 2020 - 2021 72 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.8.2 Interbank <IntrBk>

Presence: [1..1]
Definition: Set of elements used to reference the details of the corrective interbank payment transaction.
Impacted by: C19 "IdentificationRule"
Interbank <IntrBk> contains the following CorrectiveInterbankTransaction3 elements

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

No.

GroupHeader <GrpHdr> [0..1] 73

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

MessageNameIdentification <MsgNmId> [1..1] Text 74

CreationDateTime <CreDtTm> [0..1] DateTime 74

InstructionIdentification <InstrId> [0..1] Text 74

EndToEndIdentification <EndToEndId> [0..1] Text 74

TransactionIdentification <TxId> [0..1] Text 74

UETR <UETR> [0..1] IdentifierSet 75

InterbankSettlementAmount <IntrBkSttlmAmt> [1..1] Amount C2, C10 75

InterbankSettlementDate <IntrBkSttlmDt> [1..1] Date 75

Constraints

• IdentificationRule
Either InstructionIdentification, EndToEndIdentification, TransactionIdentification or UETR must be
present.
Following Must be True
/InstructionIdentification Must be present
And /EndToEndIdentification Must be present
And /TransactionIdentification Must be present
And /UETR Must be present

5.4.8.2.1 GroupHeader <GrpHdr>

Presence: [0..1]
Definition: Set of elements used to provide corrective information for the group header of the message
under investigation.
GroupHeader <GrpHdr> contains the following CorrectiveGroupInformation1 elements

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

No.

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

MessageNameIdentification <MsgNmId> [1..1] Text 74

CreationDateTime <CreDtTm> [0..1] DateTime 74

Exceptions and Investigations - Maintenance 2020 - 2021 73 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

5.4.8.2.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 483

5.4.8.2.1.2 MessageNameIdentification <MsgNmId>

Presence: [1..1]
Definition: Specifies the message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

5.4.8.2.1.3 CreationDateTime <CreDtTm>

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

5.4.8.2.2 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 483

5.4.8.2.3 EndToEndIdentification <EndToEndId>

Presence: [0..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 483

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

Exceptions and Investigations - Maintenance 2020 - 2021 74 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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 483

5.4.8.2.5 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

5.4.8.2.6 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [1..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C2 "ActiveOrHistoricCurrency", C10 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

5.4.8.2.7 InterbankSettlementDate <IntrBkSttlmDt>

Presence: [1..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 477

5.4.9 ResolutionRelatedInformation <RsltnRltdInf>

Presence: [0..1]
Definition: Reference to fix the case under investigation as part of the resolution.

Exceptions and Investigations - Maintenance 2020 - 2021 75 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

ResolutionRelatedInformation <RsltnRltdInf> contains the following ResolutionData3 elements

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

No.

EndToEndIdentification <EndToEndId> [0..1] Text 76

TransactionIdentification <TxId> [0..1] Text 76

UETR <UETR> [0..1] IdentifierSet 76

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C2, C10 76

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 77

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

Compensation <Compstn> [0..1] ± 77

Charges <Chrgs> [0..*] ± 78

5.4.9.1 EndToEndIdentification <EndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

5.4.9.2 TransactionIdentification <TxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

5.4.9.3 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

5.4.9.4 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C2 "ActiveOrHistoricCurrency", C10 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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)

Exceptions and Investigations - Maintenance 2020 - 2021 76 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.

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

Note: The decimal separator is a dot.

5.4.9.5 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 477

5.4.9.6 ClearingChannel <ClrChanl>

Presence: [0..1]
Definition: Specifies the clearing channel to be used to process the payment instruction.
Datatype: "ClearingChannel2Code" on page 462

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.

5.4.9.7 Compensation <Compstn>

Presence: [0..1]
Definition: Provides the details of the compensation made due to the modification or cancellation of a
previous payment.

Exceptions and Investigations - Maintenance 2020 - 2021 77 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

Compensation <Compstn> contains the following elements (see "Compensation4" on page 152 for
details)

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

No.

Amount <Amt> [1..1] Amount C1, C11 152

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

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 153

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

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 154

Reason <Rsn> [1..1] 155

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

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

5.4.9.8 Charges <Chrgs>

Presence: [0..*]
Definition: Provides information on the charges to be paid by the charge bearer(s) related to the
payment transaction.
Charges <Chrgs> contains the following elements (see "Charges9" on page 155 for details)

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

No.

Amount <Amt> [1..1] Amount C1, C7 155

Agent <Agt> [1..1] ± 156

AgentAccount <AgtAcct> [0..1] ± C10, C9 156

5.4.10 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C35 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

Exceptions and Investigations - Maintenance 2020 - 2021 78 December 2020

For evaluation by the Payments SEG DRAFT1camt.029.001.11
ResolutionOfInvestigationV11

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.

Exceptions and Investigations - Maintenance 2020 - 2021 79 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

6 DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

6.1 MessageDefinition Functionality

Scope

The DebitAuthorisationRequest message is sent by an account servicing institution to an account

owner. This message is used to request authorisation to debit an account.

Usage

The DebitAuthorisationRequest message must be answered with a DebitAuthorisationResponse

message.

The DebitAuthorisationRequest message can be used to request debit authorisation in a:

- request to modify payment case (in the case of a lower final amount or change of creditor);

- request to cancel payment case (full amount);

- unable to apply case (the creditor whose account has been credited is not the intended beneficiary);

- claim non receipt case (the creditor whose account has been credited is not the intended beneficiary).

The DebitAuthorisationRequest message covers one and only one payment instruction at a time. If an
account servicing institution needs to request debit authorisation for several instructions, then multiple
DebitAuthorisationRequest messages must be sent.

The DebitAuthorisationRequest must be used exclusively between the account servicing institution and
the account owner. It must not be used in place of a RequestToModifyPayment or
CustomerPaymentCancellationRequest or FIToFIPaymentCancellationRequest message between
subsequent agents.
Outline
The DebitAuthorisationRequestV09 MessageDefinition is composed of 5 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. Underlying
Identifies the underlying payment instruction.

D. Detail
Detailed information about the request.

Exceptions and Investigations - Maintenance 2020 - 2021 80 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

E. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

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

Message root <Document> <DbtAuthstnReq> [1..1]

Assignment <Assgnmt> [1..1] ± 83

Case <Case> [0..1] ± 83

Underlying <Undrlyg> [1..1] ± 84

Detail <Dtl> [1..1] 84

CancellationReason <CxlRsn> [1..1] ± 84

AmountToDebit <AmtToDbt> [0..1] Amount C1, C7 84

ValueDateToDebit <ValDtToDbt> [0..1] Date 85

AdditionalCancellationReasonInformation <AddtlCxlRsnInf> [0..*] Text 85

SupplementaryData <SplmtryData> [0..*] ± C20 85

6.3 Constraints
C1 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.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 81 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

C8 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C10 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C11 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C12 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C13 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must
be present.

C14 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.

C15 OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

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

C17 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C18 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

Exceptions and Investigations - Maintenance 2020 - 2021 82 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

C19 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C21 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C22 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

6.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

6.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

6.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

Exceptions and Investigations - Maintenance 2020 - 2021 83 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

6.4.3 Underlying <Undrlyg>

Presence: [1..1]
Definition: Identifies the underlying payment instruction.
Underlying <Undrlyg> contains one of the following elements (see "UnderlyingTransaction7Choice"
on page 211 for details)

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

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

6.4.4 Detail <Dtl>

Presence: [1..1]
Definition: Detailed information about the request.
Detail <Dtl> contains the following DebitAuthorisation2 elements

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

No.

CancellationReason <CxlRsn> [1..1] ± 84

AmountToDebit <AmtToDbt> [0..1] Amount C1, C7 84

ValueDateToDebit <ValDtToDbt> [0..1] Date 85

AdditionalCancellationReasonInformation [0..*] Text 85

<AddtlCxlRsnInf>

6.4.4.1 CancellationReason <CxlRsn>

Presence: [1..1]
Definition: Specifies the reason for the cancellation request.
CancellationReason <CxlRsn> contains one of the following elements (see
"CancellationReason33Choice" on page 445 for details)

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

No.

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

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

6.4.4.2 AmountToDebit <AmtToDbt>

Presence: [0..1]
Definition: Amount of money requested for debit authorisation.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 84 December 2020

For evaluation by the Payments SEG DRAFT1camt.037.001.09
DebitAuthorisationRequestV09

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.

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

Note: The decimal separator is a dot.

6.4.4.3 ValueDateToDebit <ValDtToDbt>

Presence: [0..1]
Definition: Value date for debiting the amount.
Datatype: "ISODate" on page 477

6.4.4.4 AdditionalCancellationReasonInformation <AddtlCxlRsnInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

6.4.5 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C20 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 85 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

7 DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

7.1 MessageDefinition Functionality

Scope

The CustomerPaymentCancellationRequest message is sent by a case creator/case assigner to a case

assignee.

This message is used to request the cancellation of an original payment instruction. The
CustomerPaymentCancellationRequest message is issued by the initiating party to request the
cancellation of an initiation payment message previously sent (such as CustomerCreditTransferInitiation
or CustomerDirectDebitInitiation).

Usage

The CustomerPaymentCancellationRequest message must be answered with a:

- ResolutionOfInvestigation message with a positive final outcome when the case assignee can perform
the requested cancellation;

- ResolutionOfInvestigation message with a negative final outcome when the case assignee may
perform the requested cancellation but fails to do so (too late, irrevocable instruction);

- RejectInvestigation message when the case assignee is unable or not authorised to perform the
requested cancellation;

- NotificationOfCaseAssignment message to indicate whether the case assignee will take on the case
himself or reassign the case to a subsequent party in the payment processing chain.

A CustomerPaymentCancellationRequest message concerns one and only one original payment

instruction at a time.

When a case assignee successfully performs a cancellation, it must return the corresponding funds to
the case assigner. It may provide some details about the return in the ResolutionOfInvestigation
message.

The processing of a CustomerPaymentCancellationRequest message case may lead to a

DebitAuthorisationRequest message sent to the creditor by its account servicing institution.

The CustomerPaymentCancellationRequest message may be used to escalate a case after an

unsuccessful request to modify the payment. In this scenario, the case identification remains the same
as in the original CustomerPaymentCancellationRequest message and the element
ReopenCaseIndication is set to 'Yes' or 'true'.

The CustomerPaymentCancellationRequest message has the following main characteristics: the case
creator assigns a unique case identification and the reason code for the cancellation request. This
information will be passed unchanged to all subsequent case assignee(s).

For the CustomerPaymentCancellationRequest message the case has been made optional, as the
message might be used outside of a case management environment where the case identification is not
relevant.

Exceptions and Investigations - Maintenance 2020 - 2021 86 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Moreover, the case identification may be present at different levels:

- One unique case is defined per cancellation request message: If multiple underlying groups, payment
information blocks or transactions are present in the message and the case assignee has already
forwarded the transaction for which the cancellation is requested, the case cannot be forwarded to the
next party in the chain (see rule on uniqueness of the case) and the case creator will have to issue
individual cancellation requests for each underlying individual transaction. In response to this
cancellation request, the case must also be present at the message level in the Resolution of
Investigation message;

- One case per original group, payment information or transaction present in the cancellation request:
For each group, payment information block or transaction within the payment information, a unique
case has been assigned. This means, when a payment instruction has already been forwarded by the
case assignee, the cancellation request may be forwarded to next party in the payment chain, with the
unique case assigned to the transaction. When the group can only be cancelled partially, new
cancellation requests need however to be issued for the individual transactions within the group for
which the cancellation request has not been successful. In response to this cancellation request, the
case must be present in the cancellation details identifying the original group or transaction in the
Resolution of Investigation message;

- No case used in cancellation request message: The cancellation of a payment instruction can be
initiated by either the debtor/creditor or any subsequent agent in the payment instruction processing
chain.
Outline
The CustomerPaymentCancellationRequestV10 MessageDefinition is composed of 5
MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. ControlData
Provides details on the number of transactions and the control sum of the message.

D. Underlying
Identifies the payment instruction to be cancelled.

E. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

Exceptions and Investigations - Maintenance 2020 - 2021 87 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

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

Message root <Document> <CstmrPmtCxlReq> [1..1] C19,

C20,
C21,
C29

Assignment <Assgnmt> [1..1] ± 92

Case <Case> [0..1] ± 92

ControlData <CtrlData> [0..1] 93

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

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

Underlying <Undrlyg> [1..*] C8, C9, 93

C10,
C11,
C12,
C13

OriginalGroupInformationAndCancellation [0..1] 96
<OrgnlGrpInfAndCxl>

GroupCancellationIdentification <GrpCxlId> [0..1] Text 96

Case <Case> [0..1] ± 96

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 97

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 97

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 97

NumberOfTransactions <NbOfTxs> [0..1] Text 97

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

GroupCancellation <GrpCxl> [0..1] Indicator 97

CancellationReasonInformation <CxlRsnInf> [0..*] 98

Originator <Orgtr> [0..1] ± 98

Reason <Rsn> [0..1] ± 98

AdditionalInformation <AddtlInf> [0..*] Text 98

OriginalPaymentInformationAndCancellation [0..*] C22, 99

<OrgnlPmtInfAndCxl> C23,
C24

PaymentCancellationIdentification <PmtCxlId> [0..1] Text 100

Case <Case> [0..1] ± 100

OriginalPaymentInformationIdentification <OrgnlPmtInfId> [1..1] Text 100

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 100

Exceptions and Investigations - Maintenance 2020 - 2021 88 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

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

No.

NumberOfTransactions <NbOfTxs> [0..1] Text 101

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

PaymentInformationCancellation <PmtInfCxl> [0..1] Indicator 101

CancellationReasonInformation <CxlRsnInf> [0..*] 101

Originator <Orgtr> [0..1] ± 101

Reason <Rsn> [0..1] ± 102

AdditionalInformation <AddtlInf> [0..*] Text 102

TransactionInformation <TxInf> [0..*] ± 102

SupplementaryData <SplmtryData> [0..*] ± C30 104

7.3 Constraints
C1 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.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

Exceptions and Investigations - Maintenance 2020 - 2021 89 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

C8 GroupCancellationAndNumberOfTransactionsRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then
NumberOfTransactions must equal the number of occurrences of TransactionInformation.

C9 GroupCancellationAndReasonRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalGroupInformationAndCancellation/CancellationReasonInformation/Reason must
present.

C10 GroupCancellationFalseAndPaymentInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then
OriginalPaymentInformationAndCancellation must be present.

C11 GroupCancellationTrueAndPaymentInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalPaymentInformationAndCancellation is not allowed.

C12 GroupOrPaymentInformationCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.

C13 GroupOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.

C14 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C16 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C17 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C18 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C19 MessageOrGroupCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/Case is present
And /Underlying[1]/OriginalGroupInformationAndCancellation is present
Following Must be True
/Underlying[*]/OriginalGroupInformationAndCancellation/Case Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 90 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

This constraint is defined at the MessageDefinition level.

C20 MessageOrPaymentInformationCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/Case is present
And /Underlying[1]/OriginalPaymentInformationAndCancellation[1] is present
Following Must be True
/Underlying[*]/OriginalPaymentInformationAndCancellation[*]/Case Must be
absent
This constraint is defined at the MessageDefinition level.

C21 MessageOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/Case is present
And /Underlying[1]/OriginalPaymentInformationAndCancellation[1]/
TransactionInformation[1]/Case is present
Following Must be True
/Underlying[*]/OriginalPaymentInformationAndCancellation[*]/
TransactionInformation[*]/Case Must be absent
This constraint is defined at the MessageDefinition level.

C22 PaymentInformationCancellationFalseAndTransactionInformationRule
If PaymentInformationCancellation is false, then TransactionInformation must be present.

C23 PaymentInformationCancellationTrueAndTransactionInformationRule
If PaymentInformationCancellation is true, then TransactionInformation is not allowed.

C24 PaymentInformationOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.

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

C26 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C27 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C28 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

Exceptions and Investigations - Maintenance 2020 - 2021 91 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

C29 SupplementaryDataRule
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.

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

C31 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C32 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

7.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

7.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

7.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.

Exceptions and Investigations - Maintenance 2020 - 2021 92 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

7.4.3 ControlData <CtrlData>

Presence: [0..1]
Definition: Provides details on the number of transactions and the control sum of the message.
ControlData <CtrlData> contains the following ControlData1 elements

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

No.

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

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

7.4.3.1 NumberOfTransactions <NbOfTxs>

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

7.4.3.2 ControlSum <CtrlSum>

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

7.4.4 Underlying <Undrlyg>

Presence: [1..*]
Definition: Identifies the payment instruction to be cancelled.
Impacted by: C8 "GroupCancellationAndNumberOfTransactionsRule", C9
"GroupCancellationAndReasonRule", C10 "GroupCancellationFalseAndPaymentInformationRule", C11
"GroupCancellationTrueAndPaymentInformationRule", C12 "GroupOrPaymentInformationCaseRule",
C13 "GroupOrTransactionCaseRule"

Exceptions and Investigations - Maintenance 2020 - 2021 93 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Underlying <Undrlyg> contains the following UnderlyingTransaction30 elements

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

No.

OriginalGroupInformationAndCancellation [0..1] 96
<OrgnlGrpInfAndCxl>

GroupCancellationIdentification <GrpCxlId> [0..1] Text 96

Case <Case> [0..1] ± 96

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 97

OriginalMessageNameIdentification [1..1] Text 97

<OrgnlMsgNmId>

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 97

NumberOfTransactions <NbOfTxs> [0..1] Text 97

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

GroupCancellation <GrpCxl> [0..1] Indicator 97

CancellationReasonInformation <CxlRsnInf> [0..*] 98

Originator <Orgtr> [0..1] ± 98

Reason <Rsn> [0..1] ± 98

AdditionalInformation <AddtlInf> [0..*] Text 98

OriginalPaymentInformationAndCancellation [0..*] C22, 99

<OrgnlPmtInfAndCxl> C23,
C24

PaymentCancellationIdentification <PmtCxlId> [0..1] Text 100

Case <Case> [0..1] ± 100

OriginalPaymentInformationIdentification [1..1] Text 100

<OrgnlPmtInfId>

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 100

NumberOfTransactions <NbOfTxs> [0..1] Text 101

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

PaymentInformationCancellation <PmtInfCxl> [0..1] Indicator 101

CancellationReasonInformation <CxlRsnInf> [0..*] 101

Originator <Orgtr> [0..1] ± 101

Reason <Rsn> [0..1] ± 102

AdditionalInformation <AddtlInf> [0..*] Text 102

TransactionInformation <TxInf> [0..*] ± 102

Exceptions and Investigations - Maintenance 2020 - 2021 94 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Constraints

• GroupCancellationAndNumberOfTransactionsRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then NumberOfTransactions
must equal the number of occurrences of TransactionInformation.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is absent
Following Must be True
/OriginalGroupInformationAndCancellation/NumberOfTransactions Must be equal
to value 'number occurrences TransactionInformation'

• GroupCancellationAndReasonRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalGroupInformationAndCancellation/CancellationReasonInformation/Reason must present.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'true'
Following Must be True
/OriginalGroupInformationAndCancellation/CancellationReasonInformation[*]
Must be present
And /OriginalGroupInformationAndCancellation/CancellationReasonInformation[*]/
Reason Must be present

• GroupCancellationFalseAndPaymentInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then
OriginalPaymentInformationAndCancellation must be present.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'false'
Following Must be True
/OriginalPaymentInformationAndCancellation[1] Must be present

• GroupCancellationTrueAndPaymentInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalPaymentInformationAndCancellation is not allowed.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'true'
Following Must be True
/OriginalPaymentInformationAndCancellation[*] Must be absent

• GroupOrPaymentInformationCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/OriginalGroupInformationAndCancellation is present
And /OriginalGroupInformationAndCancellation/Case is present
And /OriginalPaymentInformationAndCancellation[1] is present
Following Must be True
/OriginalPaymentInformationAndCancellation[*]/Case Must be absent

• GroupOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.

Exceptions and Investigations - Maintenance 2020 - 2021 95 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

On Condition
/OriginalGroupInformationAndCancellation is present
And /OriginalGroupInformationAndCancellation/Case is present
And /OriginalPaymentInformationAndCancellation[1] is present
And /OriginalPaymentInformationAndCancellation[*]/TransactionInformation[1]
is present
Following Must be True
/OriginalPaymentInformationAndCancellation[*]/TransactionInformation[*]/Case
Must be absent

7.4.4.1 OriginalGroupInformationAndCancellation <OrgnlGrpInfAndCxl>

Presence: [0..1]
Definition: Provides information on the original message, to which the cancellation refers.
OriginalGroupInformationAndCancellation <OrgnlGrpInfAndCxl> contains the following
OriginalGroupHeader15 elements

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

No.

GroupCancellationIdentification <GrpCxlId> [0..1] Text 96

Case <Case> [0..1] ± 96

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 97

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 97

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 97

NumberOfTransactions <NbOfTxs> [0..1] Text 97

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

GroupCancellation <GrpCxl> [0..1] Indicator 97

CancellationReasonInformation <CxlRsnInf> [0..*] 98

Originator <Orgtr> [0..1] ± 98

Reason <Rsn> [0..1] ± 98

AdditionalInformation <AddtlInf> [0..*] Text 98

7.4.4.1.1 GroupCancellationIdentification <GrpCxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the assigner, to unambiguously identify the group
cancellation request.

Usage: The group cancellation request identification can be used for reconciliation or to link tasks
related to the cancellation request.
Datatype: "Max35Text" on page 483

7.4.4.1.2 Case <Case>

Presence: [0..1]
Definition: Uniquely and unambiguously identifies an exception or an investigation workflow.

Exceptions and Investigations - Maintenance 2020 - 2021 96 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

7.4.4.1.3 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]
Definition: Point to point reference, as assigned by the original instructing party, to unambiguously
identify the original message.
Datatype: "Max35Text" on page 483

7.4.4.1.4 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

7.4.4.1.5 OriginalCreationDateTime <OrgnlCreDtTm>

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

7.4.4.1.6 NumberOfTransactions <NbOfTxs>

Presence: [0..1]
Definition: Number of individual transactions contained in the original message.
Datatype: "Max15NumericText" on page 482

7.4.4.1.7 ControlSum <CtrlSum>

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

7.4.4.1.8 GroupCancellation <GrpCxl>

Presence: [0..1]
Definition: Indicates whether the cancellation request applies to a whole group of transactions or to
individual transactions within an original group.
Datatype: One of the following values must be used (see "GroupCancellationIndicator" on page 479):

• Meaning When True: Indicates that the cancellation applies to the complete group.

• Meaning When False: Indicates that the cancellation applies to individual items within the group.

Exceptions and Investigations - Maintenance 2020 - 2021 97 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

7.4.4.1.9 CancellationReasonInformation <CxlRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation reason.
CancellationReasonInformation <CxlRsnInf> contains the following PaymentCancellationReason5
elements

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

No.

Originator <Orgtr> [0..1] ± 98

Reason <Rsn> [0..1] ± 98

AdditionalInformation <AddtlInf> [0..*] Text 98

7.4.4.1.9.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation request.
Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

7.4.4.1.9.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the cancellation.
Reason <Rsn> contains one of the following elements (see "CancellationReason33Choice" on
page 445 for details)

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

No.

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

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

7.4.4.1.9.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

Exceptions and Investigations - Maintenance 2020 - 2021 98 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

7.4.4.2 OriginalPaymentInformationAndCancellation <OrgnlPmtInfAndCxl>

Presence: [0..*]
Definition: Provides information on the original (group of) transactions, to which the cancellation request
refers.
Impacted by: C22 "PaymentInformationCancellationFalseAndTransactionInformationRule", C23
"PaymentInformationCancellationTrueAndTransactionInformationRule", C24
"PaymentInformationOrTransactionCaseRule"
OriginalPaymentInformationAndCancellation <OrgnlPmtInfAndCxl> contains the following
OriginalPaymentInstruction44 elements

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

No.

PaymentCancellationIdentification <PmtCxlId> [0..1] Text 100

Case <Case> [0..1] ± 100

OriginalPaymentInformationIdentification [1..1] Text 100

<OrgnlPmtInfId>

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 100

NumberOfTransactions <NbOfTxs> [0..1] Text 101

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

PaymentInformationCancellation <PmtInfCxl> [0..1] Indicator 101

CancellationReasonInformation <CxlRsnInf> [0..*] 101

Originator <Orgtr> [0..1] ± 101

Reason <Rsn> [0..1] ± 102

AdditionalInformation <AddtlInf> [0..*] Text 102

TransactionInformation <TxInf> [0..*] ± 102

Constraints

• PaymentInformationCancellationFalseAndTransactionInformationRule
If PaymentInformationCancellation is false, then TransactionInformation must be present.
On Condition
/PaymentInformationCancellation is present
And /PaymentInformationCancellation is equal to value 'false'
Following Must be True
/TransactionInformation[1] Must be present

• PaymentInformationCancellationTrueAndTransactionInformationRule
If PaymentInformationCancellation is true, then TransactionInformation is not allowed.
On Condition
/PaymentInformationCancellation is present
And /PaymentInformationCancellation is equal to value 'true'
Following Must be True
/TransactionInformation[*] Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 99 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

• PaymentInformationOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/Case is present
And /TransactionInformation[1] is present
Following Must be True
/TransactionInformation[*]/Case Must be absent

7.4.4.2.1 PaymentCancellationIdentification <PmtCxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the assigner, to unambiguously identify the cancellation
request.

Usage: The cancellation request identification can be used for reconciliation or to link tasks relating to
the cancellation request.
Datatype: "Max35Text" on page 483

7.4.4.2.2 Case <Case>

Presence: [0..1]
Definition: Identifies the case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

7.4.4.2.3 OriginalPaymentInformationIdentification <OrgnlPmtInfId>

Presence: [1..1]
Definition: Unique and unambiguous identifier of the original payment information block, as assigned by
the original sending party.
Datatype: "Max35Text" on page 483

7.4.4.2.4 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Information concerning the original group of transactions, to which the message refers.

Exceptions and Investigations - Maintenance 2020 - 2021 100 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see

"OriginalGroupInformation29" on page 195 for details)

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

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

7.4.4.2.5 NumberOfTransactions <NbOfTxs>

Presence: [0..1]
Definition: Number of individual transactions contained in the cancellation payment information group.
Datatype: "Max15NumericText" on page 482

7.4.4.2.6 ControlSum <CtrlSum>

Presence: [0..1]
Definition: Total of all individual amounts included in the cancellation payment information group,
irrespective of currencies.
Datatype: "DecimalNumber" on page 480

7.4.4.2.7 PaymentInformationCancellation <PmtInfCxl>

Presence: [0..1]
Definition: Indicates whether or not the cancellation applies to a whole group of transactions or to
individual transactions within the original group.
Datatype: One of the following values must be used (see "GroupCancellationIndicator" on page 479):

• Meaning When True: Indicates that the cancellation applies to the complete group.

• Meaning When False: Indicates that the cancellation applies to individual items within the group.

7.4.4.2.8 CancellationReasonInformation <CxlRsnInf>

Presence: [0..*]
Definition: Detailed information on the cancellation reason.
CancellationReasonInformation <CxlRsnInf> contains the following PaymentCancellationReason5
elements

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

No.

Originator <Orgtr> [0..1] ± 101

Reason <Rsn> [0..1] ± 102

AdditionalInformation <AddtlInf> [0..*] Text 102

7.4.4.2.8.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation request.

Exceptions and Investigations - Maintenance 2020 - 2021 101 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

7.4.4.2.8.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the cancellation.
Reason <Rsn> contains one of the following elements (see "CancellationReason33Choice" on
page 445 for details)

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

No.

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

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

7.4.4.2.8.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

7.4.4.2.9 TransactionInformation <TxInf>

Presence: [0..*]
Definition: Information concerning the original transactions, to which the cancellation request message
refers.

Exceptions and Investigations - Maintenance 2020 - 2021 102 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

TransactionInformation <TxInf> contains the following elements (see "PaymentTransaction140" on

page 287 for details)

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

No.

CancellationIdentification <CxlId> [0..1] Text 289

Case <Case> [0..1] ± 289

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 290

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 290

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 290

OriginalInstructedAmount <OrgnlInstdAmt> [0..1] Amount C1, C7 290

OriginalRequestedExecutionDate <OrgnlReqdExctnDt> [0..1] ± 291

OriginalRequestedCollectionDate <OrgnlReqdColltnDt> [0..1] Date 291

CancellationReasonInformation <CxlRsnInf> [0..*] 291

Originator <Orgtr> [0..1] ± 291

Reason <Rsn> [0..1] ± 292

AdditionalInformation <AddtlInf> [0..*] Text 292

OriginalTransactionReference <OrgnlTxRef> [0..1] 292

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 294

Amount <Amt> [0..1] ± 294

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 295

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 295

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 295

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 295

SettlementInformation <SttlmInf> [0..1] C11, 295

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 298

ClearingSystem <ClrSys> [0..1] 298

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

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 103 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

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

No.

InstructingReimbursementAgentAccount [0..1] ± C10, C9 299

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 300

<InstdRmbrsmntAgtAcct>

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

ThirdReimbursementAgentAccount [0..1] ± C10, C9 301

<ThrdRmbrsmntAgtAcct>

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

PaymentMethod <PmtMtd> [0..1] CodeSet 303

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

RemittanceInformation <RmtInf> [0..1] ± 304

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 304

DebtorAgent <DbtrAgt> [0..1] ± 305

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 305

CreditorAgent <CdtrAgt> [0..1] ± 306

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 306

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 307

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

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

SupplementaryData <SplmtryData> [0..*] ± C22 309

7.4.5 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C30 "SupplementaryDataRule"

Exceptions and Investigations - Maintenance 2020 - 2021 104 December 2020

For evaluation by the Payments SEG DRAFT1camt.055.001.10
CustomerPaymentCancellationRequestV10

SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on

page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 105 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

8 DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

8.1 MessageDefinition Functionality

Scope

The FIToFIPaymentCancellationRequest message is sent by a case creator/case assigner to a case

assignee.

This message is used to request the cancellation of an original payment instruction. The
FIToFIPaymentCancellationRequest message is exchanged between the instructing agent and the
instructed agent to request the cancellation of a interbank payment message previously sent (such as
FIToFICustomerCreditTransfer, FIToFICustomerDirectDebit or FinancialInstitutionCreditTransfer).

The FIToFIPaymentCancellationRequest message supports both the request for cancellation (the
instructed agent - or assignee - has not yet processed and forwarded the payment instruction) as well
as the request for refund (payment has been fully processed already by the instructed agent - or
assignee).

Usage

The FIToFIPaymentCancellationRequest message must be answered with a:

- ResolutionOfInvestigation message with a positive final outcome when the case assignee can perform
the requested cancellation;

- ResolutionOfInvestigation message with a negative final outcome when the case assignee may
perform the requested cancellation but fails to do so (too late, irrevocable instruction);

- RejectInvestigation message when the case assignee is unable or not authorised to perform the
requested cancellation;

- NotificationOfCaseAssignment message to indicate whether the case assignee will take on the case
himself or reassign the case to a subsequent party in the payment processing chain.

A FIToFIPaymentCancellationRequest message concerns one and only one original payment

instruction at a time.

When a case assignee successfully performs a cancellation, it must return the corresponding funds to
the case assigner. It may provide some details about the return in the ResolutionOfInvestigation
message.

The processing of a FIToFIPaymentCancellationRequest message case may lead to a

DebitAuthorisationRequest message sent to the creditor by its account servicing institution.

The FIToFIPaymentCancellationRequest message may be used to escalate a case after an

unsuccessful request to modify the payment. In this scenario, the case identification remains the same
as in the original FIToFIPaymentCancellationRequest message and the element ReopenCaseIndication
is set to 'Yes' or 'true'.

Exceptions and Investigations - Maintenance 2020 - 2021 106 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

The FIToFIPaymentCancellationRequest message has the following main characteristics: the case
creator assigns a unique case identification and the reason code for the cancellation request. This
information will be passed unchanged to all subsequent case assignee(s).

For the FIToFIPaymentCancellationRequest message the case has been made optional, as the
message might be used outside of a case management environment where the case identification is not
relevant.

Moreover, the case identification may be present at different levels:

- One unique case is defined per cancellation request message: If multiple underlying groups or
transactions are present in the message and the case assignee has already forwarded the transaction
for which the cancellation is requested, the case cannot be forwarded to the next party in the chain (see
rule on uniqueness of the case) and the case creator will have to issue individual cancellation requests
for each underlying individual transaction. In response to this cancellation request, the case must also
be present at the message level in the Resolution of Investigation message;

- One case per original group or transaction present in the cancellation request: For each group or
transaction, a unique case has been assigned. This means, when a payment instruction has already
been forwarded by the case assignee, the cancellation request may be forwarded to next party in the
payment chain, with the unique case assigned to the transaction. When the group can only be
cancelled partially, new cancellation requests need however to be issued for the individual transactions
within the group for which the cancellation request has not been successful. In response to this
cancellation request, the case must be present in the cancellation details identifying the original group
or transaction in the Resolution of Investigation message;

- No case used in cancellation request message.

Cancellation of a cover payment:

The cancellation of a payment instruction for which cover is provided by a separate instruction always
results in the cancellation of the whole transaction, including the cover. The case assignee performing
the cancellation must initiate the return of funds to the case creator. The case assigner must not
request the cancellation of the cover separately.

Cancellation request initiators:

The cancellation of a payment instruction can be initiated by either the debtor/creditor or any
subsequent agent in the payment instruction processing chain.
Outline
The FIToFIPaymentCancellationRequestV10 MessageDefinition is composed of 5
MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. ControlData
Provides details on the number of transactions and the control sum of the message.

Exceptions and Investigations - Maintenance 2020 - 2021 107 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

D. Underlying
Identifies the payment instruction to be cancelled.

E. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

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

Message root <Document> <FIToFIPmtCxlReq> [1..1] C18,

C19,
C24

Assignment <Assgnmt> [1..1] ± 111

Case <Case> [0..1] ± 112

ControlData <CtrlData> [0..1] 112

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

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

Underlying <Undrlyg> [1..*] C8, C9, 112

C10,
C11,
C12

OriginalGroupInformationAndCancellation [0..1] 114

<OrgnlGrpInfAndCxl>

GroupCancellationIdentification <GrpCxlId> [0..1] Text 115

Case <Case> [0..1] ± 115

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 115

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 116

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 116

NumberOfTransactions <NbOfTxs> [0..1] Text 116

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

GroupCancellation <GrpCxl> [0..1] Indicator 116

CancellationReasonInformation <CxlRsnInf> [0..*] 116

Originator <Orgtr> [0..1] ± 117

Reason <Rsn> [0..1] ± 117

AdditionalInformation <AddtlInf> [0..*] Text 117

TransactionInformation <TxInf> [0..*] ± 117

SupplementaryData <SplmtryData> [0..*] ± C25 119

Exceptions and Investigations - Maintenance 2020 - 2021 108 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

8.3 Constraints
C1 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.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

C8 GroupCancellationAndNumberOfTransactionsRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then
NumberOfTransactions must equal the number of occurrences of TransactionInformation.

C9 GroupCancellationAndReasonRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalGroupInformationAndCancellation/CancellationReasonInformation/Reason must
present.

C10 GroupCancellationFalseAndTransactionInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then
TransactionInformation must be present.

C11 GroupCancellationTrueAndTransactionInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
TransactionInformation is not allowed.

Exceptions and Investigations - Maintenance 2020 - 2021 109 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

C12 GroupOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.

C13 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C15 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C16 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C17 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C18 MessageOrGroupCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation or
TransactionInformation level.
On Condition
/Case is present
And /Underlying[1] is present
And /Underlying[1]/OriginalGroupInformationAndCancellation is present
Following Must be True
/Underlying[*]/OriginalGroupInformationAndCancellation/Case Must be absent
This constraint is defined at the MessageDefinition level.

C19 MessageOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation or
TransactionInformation level.
On Condition
/Case is present
And /Underlying[1] is present
And /Underlying[1]/TransactionInformation[1] is present
Following Must be True
/Underlying[*]/TransactionInformation[*]/Case Must be absent
This constraint is defined at the MessageDefinition level.

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

C21 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

Exceptions and Investigations - Maintenance 2020 - 2021 110 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

C22 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C23 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

C24 SupplementaryDataRule
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.

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

C26 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C27 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

8.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

8.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

Exceptions and Investigations - Maintenance 2020 - 2021 111 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

8.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

8.4.3 ControlData <CtrlData>

Presence: [0..1]
Definition: Provides details on the number of transactions and the control sum of the message.
ControlData <CtrlData> contains the following ControlData1 elements

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

No.

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

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

8.4.3.1 NumberOfTransactions <NbOfTxs>

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

8.4.3.2 ControlSum <CtrlSum>

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

8.4.4 Underlying <Undrlyg>

Presence: [1..*]
Definition: Identifies the payment instruction to be cancelled.
Impacted by: C8 "GroupCancellationAndNumberOfTransactionsRule", C9
"GroupCancellationAndReasonRule", C10 "GroupCancellationFalseAndTransactionInformationRule",
C11 "GroupCancellationTrueAndTransactionInformationRule", C12 "GroupOrTransactionCaseRule"

Exceptions and Investigations - Maintenance 2020 - 2021 112 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

Underlying <Undrlyg> contains the following UnderlyingTransaction28 elements

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

No.

OriginalGroupInformationAndCancellation [0..1] 114

<OrgnlGrpInfAndCxl>

GroupCancellationIdentification <GrpCxlId> [0..1] Text 115

Case <Case> [0..1] ± 115

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 115

OriginalMessageNameIdentification [1..1] Text 116

<OrgnlMsgNmId>

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 116

NumberOfTransactions <NbOfTxs> [0..1] Text 116

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

GroupCancellation <GrpCxl> [0..1] Indicator 116

CancellationReasonInformation <CxlRsnInf> [0..*] 116

Originator <Orgtr> [0..1] ± 117

Reason <Rsn> [0..1] ± 117

AdditionalInformation <AddtlInf> [0..*] Text 117

TransactionInformation <TxInf> [0..*] ± 117

Constraints

• GroupCancellationAndNumberOfTransactionsRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then NumberOfTransactions
must equal the number of occurrences of TransactionInformation.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'false'
Following Must be True
/OriginalGroupInformationAndCancellation/NumberOfTransactions Must be equal
to value 'Number Occurrences TransactionInformation'

• GroupCancellationAndReasonRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then
OriginalGroupInformationAndCancellation/CancellationReasonInformation/Reason must present.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'true'
Following Must be True
/OriginalGroupInformationAndCancellation/CancellationReasonInformation[*]/
Reason Must be present

Exceptions and Investigations - Maintenance 2020 - 2021 113 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

• GroupCancellationFalseAndTransactionInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is false, then TransactionInformation
must be present.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'false'
Following Must be True
/TransactionInformation[1] Must be present

• GroupCancellationTrueAndTransactionInformationRule
If OriginalGroupInformationAndCancellation/GroupCancellation is true, then TransactionInformation
is not allowed.
On Condition
/OriginalGroupInformationAndCancellation/GroupCancellation is present
And /OriginalGroupInformationAndCancellation/GroupCancellation is equal to
value 'true'
Following Must be True
/TransactionInformation[*] Must be absent

• GroupOrTransactionCaseRule
Case may be present at either Case, OriginalGroupInformationAndCancellation,
OriginalPaymentInformationAndCancellation or TransactionInformation level.
On Condition
/OriginalGroupInformationAndCancellation is present
And /OriginalGroupInformationAndCancellation/Case is present
And /TransactionInformation[1] is present
Following Must be True
/TransactionInformation[*]/Case Must be absent

8.4.4.1 OriginalGroupInformationAndCancellation <OrgnlGrpInfAndCxl>

Presence: [0..1]
Definition: Provides information on the original message, to which the cancellation refers.

Exceptions and Investigations - Maintenance 2020 - 2021 114 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

OriginalGroupInformationAndCancellation <OrgnlGrpInfAndCxl> contains the following

OriginalGroupHeader15 elements

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

No.

GroupCancellationIdentification <GrpCxlId> [0..1] Text 115

Case <Case> [0..1] ± 115

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 115

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 116

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 116

NumberOfTransactions <NbOfTxs> [0..1] Text 116

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

GroupCancellation <GrpCxl> [0..1] Indicator 116

CancellationReasonInformation <CxlRsnInf> [0..*] 116

Originator <Orgtr> [0..1] ± 117

Reason <Rsn> [0..1] ± 117

AdditionalInformation <AddtlInf> [0..*] Text 117

8.4.4.1.1 GroupCancellationIdentification <GrpCxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the assigner, to unambiguously identify the group
cancellation request.

Usage: The group cancellation request identification can be used for reconciliation or to link tasks
related to the cancellation request.
Datatype: "Max35Text" on page 483

8.4.4.1.2 Case <Case>

Presence: [0..1]
Definition: Uniquely and unambiguously identifies an exception or an investigation workflow.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

8.4.4.1.3 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 115 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

Definition: Point to point reference, as assigned by the original instructing party, to unambiguously
identify the original message.
Datatype: "Max35Text" on page 483

8.4.4.1.4 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

8.4.4.1.5 OriginalCreationDateTime <OrgnlCreDtTm>

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

8.4.4.1.6 NumberOfTransactions <NbOfTxs>

Presence: [0..1]
Definition: Number of individual transactions contained in the original message.
Datatype: "Max15NumericText" on page 482

8.4.4.1.7 ControlSum <CtrlSum>

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

8.4.4.1.8 GroupCancellation <GrpCxl>

Presence: [0..1]
Definition: Indicates whether the cancellation request applies to a whole group of transactions or to
individual transactions within an original group.
Datatype: One of the following values must be used (see "GroupCancellationIndicator" on page 479):

• Meaning When True: Indicates that the cancellation applies to the complete group.

• Meaning When False: Indicates that the cancellation applies to individual items within the group.

8.4.4.1.9 CancellationReasonInformation <CxlRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation reason.

Exceptions and Investigations - Maintenance 2020 - 2021 116 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

CancellationReasonInformation <CxlRsnInf> contains the following PaymentCancellationReason5

elements

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

No.

Originator <Orgtr> [0..1] ± 117

Reason <Rsn> [0..1] ± 117

AdditionalInformation <AddtlInf> [0..*] Text 117

8.4.4.1.9.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation request.
Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

8.4.4.1.9.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the cancellation.
Reason <Rsn> contains one of the following elements (see "CancellationReason33Choice" on
page 445 for details)

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

No.

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

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

8.4.4.1.9.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

8.4.4.2 TransactionInformation <TxInf>

Presence: [0..*]
Definition: Provides information on the original transactions to which the cancellation request message
refers.

Exceptions and Investigations - Maintenance 2020 - 2021 117 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

TransactionInformation <TxInf> contains the following elements (see "PaymentTransaction137" on

page 356 for details)

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

No.

CancellationIdentification <CxlId> [0..1] Text 358

Case <Case> [0..1] ± 359

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 359

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 359

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 359

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 359

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 360

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 360

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 360

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 360

Assigner <Assgnr> [0..1] ± 360

Assignee <Assgne> [0..1] ± 361

CancellationReasonInformation <CxlRsnInf> [0..*] 361

Originator <Orgtr> [0..1] ± 361

Reason <Rsn> [0..1] ± 362

AdditionalInformation <AddtlInf> [0..*] Text 362

OriginalTransactionReference <OrgnlTxRef> [0..1] 362

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 364

Amount <Amt> [0..1] ± 364

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 365

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 365

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 365

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 365

SettlementInformation <SttlmInf> [0..1] C11, 365

C13,
C18,
C19,
C20,
C21,
C23,
C24

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

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 368

Exceptions and Investigations - Maintenance 2020 - 2021 118 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

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

No.

ClearingSystem <ClrSys> [0..1] 368

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

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

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 369

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 370

<InstdRmbrsmntAgtAcct>

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

ThirdReimbursementAgentAccount [0..1] ± C10, C9 371

<ThrdRmbrsmntAgtAcct>

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

PaymentMethod <PmtMtd> [0..1] CodeSet 373

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

RemittanceInformation <RmtInf> [0..1] ± 374

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 374

DebtorAgent <DbtrAgt> [0..1] ± 375

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 375

CreditorAgent <CdtrAgt> [0..1] ± 376

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 376

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 377

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

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

SupplementaryData <SplmtryData> [0..*] ± C22 379

8.4.5 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C25 "SupplementaryDataRule"

Exceptions and Investigations - Maintenance 2020 - 2021 119 December 2020

For evaluation by the Payments SEG DRAFT1camt.056.001.10
FIToFIPaymentCancellationRequestV10

SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on

page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 120 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

9 DRAFT1camt.087.001.08
RequestToModifyPaymentV08

9.1 MessageDefinition Functionality

Scope

The RequestToModifyPayment message is sent by a case creator/case assigner to a case assignee.

This message is used to request the modification of characteristics of an original payment instruction.

Usage

The RequestToModifyPayment message must be answered with a:

- ResolutionOfInvestigation message with a positive final outcome when the case assignee can perform
the requested modification;

- ResolutionOfInvestigation message with a negative final outcome when the case assignee may
perform the requested modification but fails to do so (too late, irrevocable instruction, one requested
element cannot be modified);

- RejectCaseAssignment message when the case assignee is unable or not authorised to perform the
requested modification;

- NotificationOfCaseAssignment message to indicate whether the case assignee will take on the case
himself or reassign the case to a subsequent party in the payment processing chain.

The RequestToModifyPayment message covers one and only one original instruction at a time. If
several original payment instructions need to be modified, then multiple RequestToModifyPayment
messages must be sent.

The RequestToModifyPayment message can be sent to request the modification of one or several
elements of the original payment instruction. If many elements need to be modified, it is recommended
to cancel the original payment instruction and initiate a new one.

The RequestToModifyPayment must be processed on an all or nothing basis. If one of the elements to
be modified cannot be altered, the assignment must be rejected in full by means of a negative
ResolutionOfInvestigation message. (See section on ResolutionOfInvestigation for more details).

The RequestToModifyPayment message must never be sent to request the modification of the currency
of the original payment instruction. If the currency is wrong, use a
CustomerPaymentCancellationRequest or a FIToFIPaymentCancellationRequest message to cancel it
and issue and a new payment instruction.

The RequestToModifyPayment message may be forwarded to subsequent case assignee(s).

When a RequestToModifyPayment message is used to decrease the amount of the original payment
instruction, the modification will trigger a return of funds from the case assignee to the case creator. The
assignee may indicate, within the ResolutionOfInvestigation message, the amount to be returned, the
date it is or will be returned and the channel through which the return will be done.

Exceptions and Investigations - Maintenance 2020 - 2021 121 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

The RequestToModifyPayment message must never be sent to request the increase of the amount of
the original payment instruction. To increase the amount in a payment, the debtor can do one of the
following:

- Cancel the first payment using a CustomerPaymentCancellationRequest or a

FIToFIPaymentCancellationRequest message and make a new payment with a higher and correct
amount;

- Simply send a second payment with the supplementary amount.

Depending on the requested modification(s) and the processing stage of the original payment
instruction, the processing of a request to modify payment case may end with one of the following:

- an AdditionalPaymentInformation message sent to the creditor of the original payment instruction;

- a DebitAuthorisationRequest message sent to the creditor of the original payment instruction;

- a CustomerPaymentCancellationRequest or a FIToFIPaymentCancellationRequest message sent to a

subsequent case assignee.

The RequestToModifyPayment message can be sent to correct characteristics of an original payment

instruction following receipt of an UnableToApply message. In this scenario, the case identification will
remain the same.

The RequestToModifyPayment message has the following main characteristics:

The case creator assigns a unique case identification. This information will be passed unchanged to all
subsequent case assignee(s).

Lowering the amount of an original payment instruction for which cover is provided by a separate
instruction will systematically mean the modification of the whole transaction, including the cover. The
case assignee performing the amount modification must initiate the return of funds in excess to the
case creator.

The modification of the agent's or agents' information on an original payment instruction for which cover
is provided by a separate instruction will systematically mean the whole transaction is modified, that is
the cover is executed through the agent(s) mentioned in the RequestToModifyPayment message. The
cover payment must not be modified separately.

The modification of a payment instruction can be initiated by either the debtor or any subsequent agent
in the payment processing chain.

The case creator provides the information to be modified in line with agreements made with the case
assignee. If the case assignee needs in turn to assign the case to a subsequent case assignee, the
requested modification(s) must be in line with the agreement made with the next case assignee and a
NotificationOfCaseAssignment message must be sent to the case assigner. Otherwise, the request to
modify payment case must be rejected (by means of a negative ResolutionOfInvestigation message).
Outline
The RequestToModifyPaymentV08 MessageDefinition is composed of 6 MessageBuildingBlocks:

A. Assignment
Identifies the assignment of an investigation case from an assigner to an assignee.

Exceptions and Investigations - Maintenance 2020 - 2021 122 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Usage: The assigner must be the sender of this confirmation and the assignee must be the
receiver.

B. Case
Identifies the investigation case.

C. Underlying
Identifies the payment transaction to be modified.

D. Modification
Identifies the list of modifications requested.

E. InstructionForAssignee
Further information related to the processing of the investigation that may need to be acted upon
by the assignee.

F. SupplementaryData
Additional information that cannot be captured in the structured elements and/or any other specific
block.

Exceptions and Investigations - Maintenance 2020 - 2021 123 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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

Message root <Document> <ReqToModfyPmt> [1..1]

Assignment <Assgnmt> [1..1] ± 127

Case <Case> [0..1] ± 127

Underlying <Undrlyg> [1..1] ± 128

Modification <Mod> [1..1] 128

InstructionIdentification <InstrId> [0..1] Text 130

EndToEndIdentification <EndToEndId> [0..1] Text 130

TransactionIdentification <TxId> [0..1] Text 130

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

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 131

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 131

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 131

SettlementTimeIndication <SttlmTmIndctn> [0..1] 132

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

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

Amount <Amt> [0..1] ± 132

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 133

ChargeBearer <ChrgBr> [0..1] CodeSet 133

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 134

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 135

SettlementInformation <SttlmInf> [0..1] C12, 135

C14

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 136

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 137

<InstdRmbrsmntAgtAcct>

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 138

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

Exceptions and Investigations - Maintenance 2020 - 2021 124 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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

No.

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 139

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

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

InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text 140

InstructionForNextAgent <InstrForNxtAgt> [0..*] 141

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

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

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

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

RemittanceInformation <RmtInf> [0..1] ± 142

InstructionForAssignee <InstrForAssgne> [0..1] 142

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

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

SupplementaryData <SplmtryData> [0..*] ± C22 143

9.3 Constraints
C1 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.

C2 AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.

C3 AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 125 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

C6 Country
The code is checked against the list of country names obtained from the United Nations (ISO
3166, Alpha-2 code).

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

Note: The decimal separator is a dot.

C8 IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

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

C10 IdentificationOrProxyPresenceRule
Identification must be present or Proxy must be present. Both may be present.

C11 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C12 InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent
must be present.

C13 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent
must be present.

C14 InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAcount is present, then InstructingReimbursementAgent
must be present.

C15 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must
be present.

C16 OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.

C17 OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.

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

Exceptions and Investigations - Maintenance 2020 - 2021 126 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

C19 SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s)
are not allowed.

C20 SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.

C21 SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not
allowed.

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

C23 ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be
present.

C24 ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.

9.4 Message Building Blocks

This chapter describes the MessageBuildingBlocks of this MessageDefinition.

9.4.1 Assignment <Assgnmt>

Presence: [1..1]
Definition: Identifies the assignment of an investigation case from an assigner to an assignee.

Usage: The assigner must be the sender of this confirmation and the assignee must be the receiver.
Assignment <Assgnmt> contains the following elements (see "CaseAssignment5" on page 187 for
details)

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

9.4.2 Case <Case>

Presence: [0..1]
Definition: Identifies the investigation case.

Exceptions and Investigations - Maintenance 2020 - 2021 127 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Case <Case> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

9.4.3 Underlying <Undrlyg>

Presence: [1..1]
Definition: Identifies the payment transaction to be modified.
Underlying <Undrlyg> contains one of the following elements (see "UnderlyingTransaction7Choice"
on page 211 for details)

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

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

9.4.4 Modification <Mod>

Presence: [1..1]
Definition: Identifies the list of modifications requested.

Exceptions and Investigations - Maintenance 2020 - 2021 128 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Modification <Mod> contains the following RequestedModification10 elements

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

No.

InstructionIdentification <InstrId> [0..1] Text 130

EndToEndIdentification <EndToEndId> [0..1] Text 130

TransactionIdentification <TxId> [0..1] Text 130

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

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 131

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 131

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 131

SettlementTimeIndication <SttlmTmIndctn> [0..1] 132

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

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

Amount <Amt> [0..1] ± 132

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 133

ChargeBearer <ChrgBr> [0..1] CodeSet 133

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

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

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 134

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 135

SettlementInformation <SttlmInf> [0..1] C12, 135

C14

InstructingReimbursementAgent [0..1] ± 136

<InstgRmbrsmntAgt>

InstructingReimbursementAgentAccount [0..1] ± C10, C9 136

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 137

<InstdRmbrsmntAgtAcct>

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 138

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

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 139

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

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

InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text 140

InstructionForNextAgent <InstrForNxtAgt> [0..*] 141

Exceptions and Investigations - Maintenance 2020 - 2021 129 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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

No.

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

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

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

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

RemittanceInformation <RmtInf> [0..1] ± 142

9.4.4.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 483

9.4.4.2 EndToEndIdentification <EndToEndId>

Presence: [0..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.
Datatype: "Max35Text" on page 483

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

Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to
the transaction on the interbank level. The instructing agent has to make sure that the transaction
identification is unique for a pre-agreed period.
Datatype: "Max35Text" on page 483

9.4.4.4 PaymentTypeInformation <PmtTpInf>

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

Exceptions and Investigations - Maintenance 2020 - 2021 130 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

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

No.

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

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

ServiceLevel <SvcLvl> [0..*] 406

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

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

LocalInstrument <LclInstrm> [0..1] 406

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

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

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

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

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

9.4.4.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

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

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

9.4.4.6 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

9.4.4.7 InterbankSettlementDate <IntrBkSttlmDt>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 131 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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 477

9.4.4.8 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

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

No.

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

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

9.4.4.8.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 477

9.4.4.8.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 477

9.4.4.9 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

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

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 132 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

9.4.4.10 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

9.4.4.11 ChargeBearer <ChrgBr>

Presence: [0..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the
payment transaction.
Datatype: "ChargeBearerType1Code" on page 461

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.

9.4.4.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.

Exceptions and Investigations - Maintenance 2020 - 2021 133 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

UltimateDebtor <UltmtDbtr> contains the following elements (see "PartyIdentification135" on

page 206 for details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

9.4.4.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor. In the context of the payment
model, the debtor is also the debit account owner.
Debtor <Dbtr> contains the following elements (see "PartyIdentification135" on page 206 for details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

9.4.4.14 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 134 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

9.4.4.15 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

9.4.4.16 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Instruction between two clearing agents stipulating the cash transfer characteristics between
the two parties.

Exceptions and Investigations - Maintenance 2020 - 2021 135 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Impacted by: C12 "InstructedReimbursementAgentAccountRule", C14

"InstructingReimbursementAgentAccountRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction13 elements

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

No.

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

InstructingReimbursementAgentAccount [0..1] ± C10, C9 136

<InstgRmbrsmntAgtAcct>

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

InstructedReimbursementAgentAccount [0..1] ± C10, C9 137

<InstdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAcount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

9.4.4.16.1 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 181 for details)

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

No.

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

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 136 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following
elements (see "CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

9.4.4.16.3 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 181 for details)

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

No.

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

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

9.4.4.16.4 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 137 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

9.4.4.17 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 138 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

9.4.4.18 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains the following elements (see "PartyIdentification135" on page 206 for details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

9.4.4.19 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 139 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

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

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

9.4.4.21 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 194 for
details)

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

No.

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

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

9.4.4.22 InstructionForDebtorAgent <InstrForDbtrAgt>

Presence: [0..1]
Definition: Further information related to the processing of the payment instruction, provided by the
initiating party, and intended for the debtor agent.

Exceptions and Investigations - Maintenance 2020 - 2021 140 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

Datatype: "Max140Text" on page 482

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

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

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

No.

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

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

9.4.4.23.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 472

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.

9.4.4.23.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 482

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

Exceptions and Investigations - Maintenance 2020 - 2021 141 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

InstructionForCreditorAgent <InstrForCdtrAgt> contains the following elements (see

"InstructionForCreditorAgent3" on page 210 for details)

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

No.

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

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

9.4.4.25 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 417 for details)

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

No.

RemittanceIdentification <RmtId> [0..1] Text 417

RemittanceLocationDetails <RmtLctnDtls> [0..*] ± 417

9.4.4.26 RemittanceInformation <RmtInf>

Presence: [0..1]
Definition: Structured information that enables the matching, that is reconciliation, of a payment with the
items that the payment is intended to settle, such as commercial invoices in an account receivable
system.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

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

No.

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

Structured <Strd> [0..*] ± 437

9.4.5 InstructionForAssignee <InstrForAssgne>

Presence: [0..1]
Definition: Further information related to the processing of the investigation that may need to be acted
upon by the assignee.
InstructionForAssignee <InstrForAssgne> contains the following InstructionForAssignee1
elements

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

No.

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 142 December 2020

For evaluation by the Payments SEG DRAFT1camt.087.001.08
RequestToModifyPaymentV08

9.4.5.1 Code <Cd>

Presence: [0..1]
Definition: Coded information related to the processing of the investigation instruction, provided by the
assigner, and intended for the assignee.
Datatype: "ExternalAgentInstruction1Code" on page 464

9.4.5.2 InstructionInformation <InstrInf>

Presence: [0..1]
Definition: Further information complementing the coded instruction or instruction to the assignee.
Datatype: "Max140Text" on page 482

9.4.6 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C22 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

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

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

Exceptions and Investigations - Maintenance 2020 - 2021 143 December 2020

For evaluation by the Payments SEG Message Items Types

10 Message Items Types

10.1 MessageComponents
10.1.1 Account
10.1.1.1 CashAccountType2Choice
Definition: Nature or use of the account.

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

No.

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

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

10.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Account type, in a coded form.
Datatype: "ExternalCashAccountType1Code" on page 465

10.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Nature or use of the account in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.1.2 CashAccount40
Definition: Provides the details to identify an account.

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 144 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

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

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

No.

{Or IBAN <IBAN> [1..1] IdentifierSet C8 148

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

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

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

No.

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

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

10.1.1.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: C1 "ActiveOrHistoricCurrency"
Datatype: "ActiveOrHistoricCurrencyCode" on page 461

Exceptions and Investigations - Maintenance 2020 - 2021 145 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.1.2.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 483

10.1.1.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 147 for
details)

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

No.

Type <Tp> [0..1] 147

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

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

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

10.1.1.3 GenericAccountIdentification1
Definition: Information related to a generic account identification.

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

No.

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

SchemeName <SchmeNm> [0..1] 147

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

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

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

10.1.1.3.1 Identification <Id>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 146 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Identification assigned by an institution.

Datatype: "Max34Text" on page 482

10.1.1.3.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following AccountSchemeName1Choice elements

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

No.

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

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

10.1.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: "ExternalAccountIdentification1Code" on page 464

10.1.1.3.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 483

10.1.1.3.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.1.4 ProxyAccountIdentification1
Definition: Information related to a proxy identification of the account.

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

No.

Type <Tp> [0..1] 147

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

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

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

10.1.1.4.1 Type <Tp>

Presence: [0..1]
Definition: Type of the proxy identification.

Exceptions and Investigations - Maintenance 2020 - 2021 147 December 2020

For evaluation by the Payments SEG Message Items Types

Type <Tp> contains one of the following ProxyAccountType1Choice elements

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

No.

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

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

10.1.1.4.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 470

10.1.1.4.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 483

10.1.1.4.2 Identification <Id>

Presence: [1..1]
Definition: Identification used to indicate the account identification under another specified name.
Datatype: "Max2048Text" on page 482

10.1.2 Account Identification

10.1.2.1 AccountIdentification4Choice
Definition: Specifies the unique identification of an account as assigned by the account servicer.

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

No.

{Or IBAN <IBAN> [1..1] IdentifierSet C8 148

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

10.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.
Impacted by: C8 "IBAN"
Datatype: "IBAN2007Identifier" on page 478

Exceptions and Investigations - Maintenance 2020 - 2021 148 December 2020

For evaluation by the Payments SEG Message Items Types

Constraints

• IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

10.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.
Other <Othr> contains the following elements (see "GenericAccountIdentification1" on page 146 for
details)

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

No.

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

SchemeName <SchmeNm> [0..1] 147

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

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

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

10.1.3 Amount
10.1.3.1 AmountType4Choice
Definition: Specifies the 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.

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

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

10.1.3.1.1 InstructedAmount <InstdAmt>

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

Usage: This amount has to be transported unchanged through the transaction chain.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 149 December 2020

For evaluation by the Payments SEG Message Items Types

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.

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

Note: The decimal separator is a dot.

10.1.3.1.2 EquivalentAmount <EqvtAmt>

Presence: [1..1]
Definition: Amount of money to be moved between the debtor and creditor, expressed in the currency of
the debtor's account, and the currency in which the amount is to be moved.
EquivalentAmount <EqvtAmt> contains the following EquivalentAmount2 elements

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

No.

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

10.1.3.1.2.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money to be moved between debtor and creditor, before deduction of charges,
expressed in the currency of the debtor's account, and to be moved in a different currency.

Usage: The first agent will convert the equivalent amount into the amount to be moved.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

10.1.3.1.2.2 CurrencyOfTransfer <CcyOfTrf>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 150 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Specifies the currency of the to be transferred amount, which is different from the currency of
the debtor's account.
Impacted by: C1 "ActiveOrHistoricCurrency"
Datatype: "ActiveOrHistoricCurrencyCode" on page 461

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.

10.1.4 Charge
10.1.4.1 Charges6
Definition: Provides further details on the charges related to the payment transaction.

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

No.

TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount C1, C7 151

Record <Rcrd> [0..*] ± 151

10.1.4.1.1 TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt>

Presence: [0..1]
Definition: Total of all charges and taxes applied to the entry.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

10.1.4.1.2 Record <Rcrd>

Presence: [0..*]
Definition: Provides details of the individual charges record.

Exceptions and Investigations - Maintenance 2020 - 2021 151 December 2020

For evaluation by the Payments SEG Message Items Types

Record <Rcrd> contains the following elements (see "ChargesRecord3" on page 157 for details)

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

No.

Amount <Amt> [1..1] Amount C1, C7 157

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 158

ChargeIncludedIndicator <ChrgInclInd> [0..1] Indicator 158

Type <Tp> [0..1] 158

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

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

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

Bearer <Br> [0..1] CodeSet 159

Agent <Agt> [0..1] ± 159

Tax <Tax> [0..1] 160

Identification <Id> [0..1] Text 160

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

Amount <Amt> [0..1] Amount C1, C7 160

10.1.4.2 Compensation4
Definition: Specifies the details of a payment compensation.

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

No.

Amount <Amt> [1..1] Amount C1, C11 152

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

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 153

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

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 154

Reason <Rsn> [1..1] 155

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

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

10.1.4.2.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money to be paid in compensation.
Impacted by: C1 "ActiveCurrency", C11 "CurrencyAmount"
Datatype: "ActiveCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 152 December 2020

For evaluation by the Payments SEG Message Items Types

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.

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

Note: The decimal separator is a dot.

10.1.4.2.2 DebtorAgent <DbtrAgt>

Presence: [1..1]
Definition: Financial institution servicing an account for the debtor.

Usage: The debtor agent is the payer of the compensation amount.

DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

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

No.

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

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

10.1.4.2.3 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 153 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.4.2.4 CreditorAgent <CdtrAgt>

Presence: [1..1]
Definition: Financial institution servicing an account for the creditor.

Usage: The creditor agent is the payee of the compensation amount.

CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

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

No.

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

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

10.1.4.2.5 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 154 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.4.2.6 Reason <Rsn>

Presence: [1..1]
Definition: Reason for the payment compensation.
Reason <Rsn> contains one of the following CompensationReason1Choice elements

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

No.

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

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

10.1.4.2.6.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the payment compensation, in a coded form.
Datatype: "ExternalPaymentCompensationReason1Code" on page 469

10.1.4.2.6.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the payment compensation, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.4.3 Charges9
Definition: Provides information on the charges related to the payment transaction.

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

No.

Amount <Amt> [1..1] Amount C1, C7 155

Agent <Agt> [1..1] ± 156

AgentAccount <AgtAcct> [0..1] ± C10, C9 156

10.1.4.3.1 Amount <Amt>

Presence: [1..1]
Definition: Transaction charges to be paid by the charge bearer.

Exceptions and Investigations - Maintenance 2020 - 2021 155 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"

Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

10.1.4.3.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 181 for details)

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

No.

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

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

10.1.4.3.3 AgentAccount <AgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the agent to which a credit entry will be made
as a result of the charges.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
AgentAccount <AgtAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 156 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.4.4 ChargesRecord3
Definition: Provides further individual record details on the charges related to the payment transaction.

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

No.

Amount <Amt> [1..1] Amount C1, C7 157

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 158

ChargeIncludedIndicator <ChrgInclInd> [0..1] Indicator 158

Type <Tp> [0..1] 158

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

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

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

Bearer <Br> [0..1] CodeSet 159

Agent <Agt> [0..1] ± 159

Tax <Tax> [0..1] 160

Identification <Id> [0..1] Text 160

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

Amount <Amt> [0..1] Amount C1, C7 160

10.1.4.4.1 Amount <Amt>

Presence: [1..1]
Definition: Transaction charges to be paid by the charge bearer.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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)

Exceptions and Investigations - Maintenance 2020 - 2021 157 December 2020

For evaluation by the Payments SEG Message Items Types

contiguous letters, and may be or not be withdrawn on the day the message containing the Currency
is exchanged.

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

Note: The decimal separator is a dot.

10.1.4.4.2 CreditDebitIndicator <CdtDbtInd>

Presence: [0..1]
Definition: Indicates whether the charges amount is a credit or a debit amount.

Usage: A zero amount is considered to be a credit.

Datatype: "CreditDebitCode" on page 463

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

10.1.4.4.3 ChargeIncludedIndicator <ChrgInclInd>

Presence: [0..1]
Definition: Indicates whether the charge should be included in the amount or is added as pre-advice.
Datatype: One of the following values must be used (see "ChargeIncludedIndicator" on page 479):

• Meaning When True: Included

• Meaning When False: Pre-advised

10.1.4.4.4 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of charge.
Type <Tp> contains one of the following ChargeType3Choice elements

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

No.

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

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

10.1.4.4.4.1 Code <Cd>

Presence: [1..1]
Definition: Charge type, in a coded form.
Datatype: "ExternalChargeType1Code" on page 466

10.1.4.4.4.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Type of charge in a proprietary form, as defined by the issuer.

Exceptions and Investigations - Maintenance 2020 - 2021 158 December 2020

For evaluation by the Payments SEG Message Items Types

Proprietary <Prtry> contains the following elements (see "GenericIdentification3" on page 183 for
details)

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

No.

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

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

10.1.4.4.5 Rate <Rate>

Presence: [0..1]
Definition: Rate used to calculate the amount of the charge or fee.
Datatype: "PercentageRate" on page 480

10.1.4.4.6 Bearer <Br>

Presence: [0..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the
payment transaction.
Datatype: "ChargeBearerType1Code" on page 461

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.

10.1.4.4.7 Agent <Agt>

Presence: [0..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 181 for details)

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

No.

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 159 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.4.4.8 Tax <Tax>

Presence: [0..1]
Definition: Provides details on the tax applied to charges.
Tax <Tax> contains the following TaxCharges2 elements

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

No.

Identification <Id> [0..1] Text 160

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

Amount <Amt> [0..1] Amount C1, C7 160

10.1.4.4.8.1 Identification <Id>

Presence: [0..1]
Definition: Unique reference to unambiguously identify the nature of the tax levied, such as Value
Added Tax (VAT).
Datatype: "Max35Text" on page 483

10.1.4.4.8.2 Rate <Rate>

Presence: [0..1]
Definition: Rate used to calculate the tax.
Datatype: "PercentageRate" on page 480

10.1.4.4.8.3 Amount <Amt>

Presence: [0..1]
Definition: Amount of money resulting from the calculation of the tax.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

10.1.5 Date Period

10.1.5.1 DatePeriod2
Definition: Range of time defined by a start date and an end date.

Exceptions and Investigations - Maintenance 2020 - 2021 160 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

FromDate <FrDt> [1..1] Date 161

ToDate <ToDt> [1..1] Date 161

10.1.5.1.1 FromDate <FrDt>

Presence: [1..1]
Definition: Start date of the range.
Datatype: "ISODate" on page 477

10.1.5.1.2 ToDate <ToDt>

Presence: [1..1]
Definition: End date of the range.
Datatype: "ISODate" on page 477

10.1.6 Date Time

10.1.6.1 DateAndDateTime2Choice
Definition: Choice between a date or a date and time format.

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

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.6.1.1 Date <Dt>

Presence: [1..1]
Definition: Specified date.
Datatype: "ISODate" on page 477

10.1.6.1.2 DateTime <DtTm>

Presence: [1..1]
Definition: Specified date and time.
Datatype: "ISODateTime" on page 477

10.1.7 Direct Debit

10.1.7.1 CreditTransferMandateData1
Definition: Provides further details related to a credit transfer mandate signed between the creditor and
the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 161 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

MandateIdentification <MndtId> [0..1] Text 162

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

DateOfSignature <DtOfSgntr> [0..1] Date 163

DateOfVerification <DtOfVrfctn> [0..1] DateTime 163

ElectronicSignature <ElctrncSgntr> [0..1] Binary 163

FirstPaymentDate <FrstPmtDt> [0..1] Date 163

FinalPaymentDate <FnlPmtDt> [0..1] Date 163

Frequency <Frqcy> [0..1] ± 163

Reason <Rsn> [0..1] 164

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

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

10.1.7.1.1 MandateIdentification <MndtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the creditor, to unambiguously identify the mandate.
Datatype: "Max35Text" on page 483

10.1.7.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 192 for details)

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

No.

ServiceLevel <SvcLvl> [0..1] 192

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

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

LocalInstrument <LclInstrm> [0..1] 192

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

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

CategoryPurpose <CtgyPurp> [0..1] 193

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

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

Classification <Clssfctn> [0..1] ± 193

Exceptions and Investigations - Maintenance 2020 - 2021 162 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.7.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 477

10.1.7.1.4 DateOfVerification <DtOfVrfctn>

Presence: [0..1]
Definition: Date on which the credit transfer mandate has been verified.
Datatype: "ISODateTime" on page 477

10.1.7.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 460

10.1.7.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 477

10.1.7.1.7 FinalPaymentDate <FnlPmtDt>

Presence: [0..1]
Definition: Date of the final payment of a recurrent credit transfer as per the mandate.
Datatype: "ISODate" on page 477

10.1.7.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 196
for details)

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

No.

{Or Type <Tp> [1..1] CodeSet 196

Or Period <Prd> [1..1] 196

Type <Tp> [1..1] CodeSet 197

CountPerPeriod <CntPerPrd> [1..1] Quantity 197

Or} PointInTime <PtInTm> [1..1] 197

Type <Tp> [1..1] CodeSet 198

PointInTime <PtInTm> [1..1] Text 198

Exceptions and Investigations - Maintenance 2020 - 2021 163 December 2020

For evaluation by the Payments SEG Message Items Types

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

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

No.

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

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

10.1.7.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 468

10.1.7.1.9.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the mandate setup, in a proprietary form.
Datatype: "Max70Text" on page 483

10.1.7.2 MandateRelatedInformation15
Definition: Provides further details related to a direct debit mandate signed between the creditor and the
debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 164 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

MandateIdentification <MndtId> [0..1] Text 165

DateOfSignature <DtOfSgntr> [0..1] Date 165

AmendmentIndicator <AmdmntInd> [0..1] Indicator 165

AmendmentInformationDetails <AmdmntInfDtls> [0..1] ± 166

ElectronicSignature <ElctrncSgntr> [0..1] Text 166

FirstCollectionDate <FrstColltnDt> [0..1] Date 166

FinalCollectionDate <FnlColltnDt> [0..1] Date 167

Frequency <Frqcy> [0..1] ± 167

Reason <Rsn> [0..1] 167

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

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

TrackingDays <TrckgDays> [0..1] Text 168

Constraints

• AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.
On Condition
/AmendmentIndicator is equal to value 'false'
Following Must be True
/AmendmentInformationDetails Must be absent

• AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.
On Condition
/AmendmentIndicator is equal to value 'true'
Following Must be True
/AmendmentInformationDetails Must be present

10.1.7.2.1 MandateIdentification <MndtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the creditor, to unambiguously identify the mandate.
Datatype: "Max35Text" on page 483

10.1.7.2.2 DateOfSignature <DtOfSgntr>

Presence: [0..1]
Definition: Date on which the direct debit mandate has been signed by the debtor.
Datatype: "ISODate" on page 477

10.1.7.2.3 AmendmentIndicator <AmdmntInd>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 165 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Indicator notifying whether the underlying mandate is amended or not.

Datatype: One of the following values must be used (see "TrueFalseIndicator" on page 480):

• Meaning When True: True

• Meaning When False: False

10.1.7.2.4 AmendmentInformationDetails <AmdmntInfDtls>

Presence: [0..1]
Definition: List of mandate elements that have been modified.
AmendmentInformationDetails <AmdmntInfDtls> contains the following elements (see
"AmendmentInformationDetails14" on page 169 for details)

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

No.

OriginalMandateIdentification <OrgnlMndtId> [0..1] Text 170

OriginalCreditorSchemeIdentification [0..1] ± 170

<OrgnlCdtrSchmeId>

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] ± 171

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] ± C10, C9 171

OriginalDebtor <OrgnlDbtr> [0..1] ± 171

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] ± C10, C9 172

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] ± 172

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] ± C10, C9 173

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] Date 173

OriginalFrequency <OrgnlFrqcy> [0..1] ± 173

OriginalReason <OrgnlRsn> [0..1] 174

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

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

OriginalTrackingDays <OrgnlTrckgDays> [0..1] Text 174

10.1.7.2.5 ElectronicSignature <ElctrncSgntr>

Presence: [0..1]
Definition: Additional security provisions, such as a digital signature, as provided by the debtor.
Datatype: "Max1025Text" on page 481

10.1.7.2.6 FirstCollectionDate <FrstColltnDt>

Presence: [0..1]
Definition: Date of the first collection of a direct debit as per the mandate.
Datatype: "ISODate" on page 477

Exceptions and Investigations - Maintenance 2020 - 2021 166 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.7.2.7 FinalCollectionDate <FnlColltnDt>

Presence: [0..1]
Definition: Date of the final collection of a direct debit as per the mandate.
Datatype: "ISODate" on page 477

10.1.7.2.8 Frequency <Frqcy>

Presence: [0..1]
Definition: Regularity with which direct debit instructions are to be created and processed.
Frequency <Frqcy> contains one of the following elements (see "Frequency36Choice" on page 196
for details)

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

No.

{Or Type <Tp> [1..1] CodeSet 196

Or Period <Prd> [1..1] 196

Type <Tp> [1..1] CodeSet 197

CountPerPeriod <CntPerPrd> [1..1] Quantity 197

Or} PointInTime <PtInTm> [1..1] 197

Type <Tp> [1..1] CodeSet 198

PointInTime <PtInTm> [1..1] Text 198

10.1.7.2.9 Reason <Rsn>

Presence: [0..1]
Definition: Reason for the direct debit mandate to allow the user to distinguish between different
mandates for the same creditor.
Reason <Rsn> contains one of the following MandateSetupReason1Choice elements

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

No.

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

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

10.1.7.2.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 468

10.1.7.2.9.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the mandate setup, in a proprietary form.
Datatype: "Max70Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 167 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.7.2.10 TrackingDays <TrckgDays>

Presence: [0..1]
Definition: Specifies the number of days the direct debit instruction must be tracked.
Datatype: "Exact2NumericText" on page 481

10.1.7.3 MandateRelatedData2Choice
Definition: Choice of mandate related information.

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

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.7.3.1 DirectDebitMandate <DrctDbtMndt>

Presence: [0..1]
Definition: Specific direct debit mandate data.
Impacted by: C2 "AmendmentIndicatorFalseRule", C3 "AmendmentIndicatorTrueRule"
DirectDebitMandate <DrctDbtMndt> contains the following elements (see
"MandateRelatedInformation15" on page 164 for details)

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

No.

MandateIdentification <MndtId> [0..1] Text 165

DateOfSignature <DtOfSgntr> [0..1] Date 165

AmendmentIndicator <AmdmntInd> [0..1] Indicator 165

AmendmentInformationDetails <AmdmntInfDtls> [0..1] ± 166

ElectronicSignature <ElctrncSgntr> [0..1] Text 166

FirstCollectionDate <FrstColltnDt> [0..1] Date 166

FinalCollectionDate <FnlColltnDt> [0..1] Date 167

Frequency <Frqcy> [0..1] ± 167

Reason <Rsn> [0..1] 167

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

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

TrackingDays <TrckgDays> [0..1] Text 168

Constraints

• AmendmentIndicatorFalseRule
If AmendmentIndicator is false, then AmendmentInformationDetails is not allowed.
On Condition
/AmendmentIndicator is equal to value 'false'

Exceptions and Investigations - Maintenance 2020 - 2021 168 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/AmendmentInformationDetails Must be absent

• AmendmentIndicatorTrueRule
If AmendmentIndicator is true, then AmendementInformationDetails must be present.
On Condition
/AmendmentIndicator is equal to value 'true'
Following Must be True
/AmendmentInformationDetails Must be present

10.1.7.3.2 CreditTransferMandate <CdtTrfMndt>

Presence: [0..1]
Definition: Specific credit transfer mandate data.
CreditTransferMandate <CdtTrfMndt> contains the following elements (see
"CreditTransferMandateData1" on page 161 for details)

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

No.

MandateIdentification <MndtId> [0..1] Text 162

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

DateOfSignature <DtOfSgntr> [0..1] Date 163

DateOfVerification <DtOfVrfctn> [0..1] DateTime 163

ElectronicSignature <ElctrncSgntr> [0..1] Binary 163

FirstPaymentDate <FrstPmtDt> [0..1] Date 163

FinalPaymentDate <FnlPmtDt> [0..1] Date 163

Frequency <Frqcy> [0..1] ± 163

Reason <Rsn> [0..1] 164

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

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

10.1.7.4 AmendmentInformationDetails14
Definition: Provides further details on the list of direct debit mandate elements that have been modified
when the amendment indicator has been set.

Exceptions and Investigations - Maintenance 2020 - 2021 169 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

OriginalMandateIdentification <OrgnlMndtId> [0..1] Text 170

OriginalCreditorSchemeIdentification [0..1] ± 170

<OrgnlCdtrSchmeId>

OriginalCreditorAgent <OrgnlCdtrAgt> [0..1] ± 171

OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> [0..1] ± C10, C9 171

OriginalDebtor <OrgnlDbtr> [0..1] ± 171

OriginalDebtorAccount <OrgnlDbtrAcct> [0..1] ± C10, C9 172

OriginalDebtorAgent <OrgnlDbtrAgt> [0..1] ± 172

OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> [0..1] ± C10, C9 173

OriginalFinalCollectionDate <OrgnlFnlColltnDt> [0..1] Date 173

OriginalFrequency <OrgnlFrqcy> [0..1] ± 173

OriginalReason <OrgnlRsn> [0..1] 174

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

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

OriginalTrackingDays <OrgnlTrckgDays> [0..1] Text 174

10.1.7.4.1 OriginalMandateIdentification <OrgnlMndtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the creditor, to unambiguously identify the original
mandate.
Datatype: "Max35Text" on page 483

10.1.7.4.2 OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId>

Presence: [0..1]
Definition: Original creditor scheme identification that has been modified.
OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

Exceptions and Investigations - Maintenance 2020 - 2021 170 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.7.4.3 OriginalCreditorAgent <OrgnlCdtrAgt>

Presence: [0..1]
Definition: Original creditor agent that has been modified.
OriginalCreditorAgent <OrgnlCdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

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

No.

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

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

10.1.7.4.4 OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct>

Presence: [0..1]
Definition: Original creditor agent account that has been modified.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
OriginalCreditorAgentAccount <OrgnlCdtrAgtAcct> contains the following elements (see
"CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.7.4.5 OriginalDebtor <OrgnlDbtr>

Presence: [0..1]
Definition: Original debtor that has been modified.

Exceptions and Investigations - Maintenance 2020 - 2021 171 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalDebtor <OrgnlDbtr> contains the following elements (see "PartyIdentification135" on

page 206 for details)

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

No.

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

PostalAddress <PstlAdr> [0..1] ± 206

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

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.7.4.6 OriginalDebtorAccount <OrgnlDbtrAcct>

Presence: [0..1]
Definition: Original debtor account that has been modified.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
OriginalDebtorAccount <OrgnlDbtrAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.7.4.7 OriginalDebtorAgent <OrgnlDbtrAgt>

Presence: [0..1]
Definition: Original debtor agent that has been modified.

Exceptions and Investigations - Maintenance 2020 - 2021 172 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalDebtorAgent <OrgnlDbtrAgt> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

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

No.

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

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

10.1.7.4.8 OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct>

Presence: [0..1]
Definition: Original debtor agent account that has been modified.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
OriginalDebtorAgentAccount <OrgnlDbtrAgtAcct> contains the following elements (see
"CashAccount40" on page 144 for details)

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

No.

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

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

Currency <Ccy> [0..1] CodeSet C1 145

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

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

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.7.4.9 OriginalFinalCollectionDate <OrgnlFnlColltnDt>

Presence: [0..1]
Definition: Original final collection date that has been modified.
Datatype: "ISODate" on page 477

10.1.7.4.10 OriginalFrequency <OrgnlFrqcy>

Presence: [0..1]
Definition: Original frequency that has been modified.

Exceptions and Investigations - Maintenance 2020 - 2021 173 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalFrequency <OrgnlFrqcy> contains one of the following elements (see "Frequency36Choice"

on page 196 for details)

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

No.

{Or Type <Tp> [1..1] CodeSet 196

Or Period <Prd> [1..1] 196

Type <Tp> [1..1] CodeSet 197

CountPerPeriod <CntPerPrd> [1..1] Quantity 197

Or} PointInTime <PtInTm> [1..1] 197

Type <Tp> [1..1] CodeSet 198

PointInTime <PtInTm> [1..1] Text 198

10.1.7.4.11 OriginalReason <OrgnlRsn>

Presence: [0..1]
Definition: Original reason for the mandate to allow the user to distinguish between different mandates
for the same creditor.
OriginalReason <OrgnlRsn> contains one of the following MandateSetupReason1Choice elements

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

No.

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

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

10.1.7.4.11.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the mandate setup, as published in an external reason code list.
Datatype: "ExternalMandateSetupReason1Code" on page 468

10.1.7.4.11.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the mandate setup, in a proprietary form.
Datatype: "Max70Text" on page 483

10.1.7.4.12 OriginalTrackingDays <OrgnlTrckgDays>

Presence: [0..1]
Definition: Original number of tracking days that has been modified.
Datatype: "Exact2NumericText" on page 481

Exceptions and Investigations - Maintenance 2020 - 2021 174 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.8 Document
10.1.8.1 CreditorReferenceInformation2
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.

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

No.

Type <Tp> [0..1] 175

CodeOrProprietary <CdOrPrtry> [1..1] 175

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

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

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

Reference <Ref> [0..1] Text 176

10.1.8.1.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of creditor reference.
Type <Tp> contains the following CreditorReferenceType2 elements

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

No.

CodeOrProprietary <CdOrPrtry> [1..1] 175

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

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

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

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

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

No.

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

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

10.1.8.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Type of creditor reference, in a coded form.
Datatype: "DocumentType3Code" on page 463

Exceptions and Investigations - Maintenance 2020 - 2021 175 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.8.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Creditor reference type, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.8.1.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the credit reference type.
Datatype: "Max35Text" on page 483

10.1.8.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 483

10.1.9 Financial Institution Identification

10.1.9.1 ClearingSystemMemberIdentification2
Definition: Unique identification, as assigned by a clearing system, to unambiguously identify a member
of the clearing system.

Exceptions and Investigations - Maintenance 2020 - 2021 176 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

ClearingSystemIdentification <ClrSysId> [0..1] ± 177

MemberIdentification <MmbId> [1..1] Text 177

10.1.9.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 447 for details)

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

No.

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

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

10.1.9.1.2 MemberIdentification <MmbId>

Presence: [1..1]
Definition: Identification of a member of a clearing system.
Datatype: "Max35Text" on page 483

10.1.9.2 FinancialInstitutionIdentification18
Definition: Specifies the details to identify a financial institution.

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

No.

BICFI <BICFI> [0..1] IdentifierSet C5 177

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] ± 178

LEI <LEI> [0..1] IdentifierSet 178

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

PostalAddress <PstlAdr> [0..1] ± 178

Other <Othr> [0..1] ± 179

10.1.9.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)".
Impacted by: C5 "BICFI"
Datatype: "BICFIDec2014Identifier" on page 478

Exceptions and Investigations - Maintenance 2020 - 2021 177 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.9.2.2 ClearingSystemMemberIdentification <ClrSysMmbId>

Presence: [0..1]
Definition: Information used to identify a member within a clearing system.
ClearingSystemMemberIdentification <ClrSysMmbId> contains the following elements (see
"ClearingSystemMemberIdentification2" on page 176 for details)

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

No.

ClearingSystemIdentification <ClrSysId> [0..1] ± 177

MemberIdentification <MmbId> [1..1] Text 177

10.1.9.2.3 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identifier of the financial institution.
Datatype: "LEIIdentifier" on page 479

10.1.9.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 482

10.1.9.2.5 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

Exceptions and Investigations - Maintenance 2020 - 2021 178 December 2020

For evaluation by the Payments SEG Message Items Types

PostalAddress <PstlAdr> contains the following elements (see "PostalAddress24" on page 413 for
details)

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

No.

AddressType <AdrTp> [0..1] 414

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

Or} Proprietary <Prtry> [1..1] ± 415

Department <Dept> [0..1] Text 415

SubDepartment <SubDept> [0..1] Text 415

StreetName <StrtNm> [0..1] Text 415

BuildingNumber <BldgNb> [0..1] Text 415

BuildingName <BldgNm> [0..1] Text 416

Floor <Flr> [0..1] Text 416

PostBox <PstBx> [0..1] Text 416

Room <Room> [0..1] Text 416

PostCode <PstCd> [0..1] Text 416

TownName <TwnNm> [0..1] Text 416

TownLocationName <TwnLctnNm> [0..1] Text 416

DistrictName <DstrctNm> [0..1] Text 416

CountrySubDivision <CtrySubDvsn> [0..1] Text 417

Country <Ctry> [0..1] CodeSet C6 417

AddressLine <AdrLine> [0..7] Text 417

10.1.9.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 182 for
details)

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

No.

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

SchemeName <SchmeNm> [0..1] 183

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

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 179 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.9.3 BranchData3
Definition: Information that locates and identifies a specific branch of a financial institution.

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

No.

Identification <Id> [0..1] Text 180

LEI <LEI> [0..1] IdentifierSet 180

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

PostalAddress <PstlAdr> [0..1] ± 180

10.1.9.3.1 Identification <Id>

Presence: [0..1]
Definition: Unique and unambiguous identification of a branch of a financial institution.
Datatype: "Max35Text" on page 483

10.1.9.3.2 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identification for the branch of the financial institution.
Datatype: "LEIIdentifier" on page 479

10.1.9.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 482

10.1.9.3.4 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

Exceptions and Investigations - Maintenance 2020 - 2021 180 December 2020

For evaluation by the Payments SEG Message Items Types

PostalAddress <PstlAdr> contains the following elements (see "PostalAddress24" on page 413 for
details)

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

No.

AddressType <AdrTp> [0..1] 414

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

Or} Proprietary <Prtry> [1..1] ± 415

Department <Dept> [0..1] Text 415

SubDepartment <SubDept> [0..1] Text 415

StreetName <StrtNm> [0..1] Text 415

BuildingNumber <BldgNb> [0..1] Text 415

BuildingName <BldgNm> [0..1] Text 416

Floor <Flr> [0..1] Text 416

PostBox <PstBx> [0..1] Text 416

Room <Room> [0..1] Text 416

PostCode <PstCd> [0..1] Text 416

TownName <TwnNm> [0..1] Text 416

TownLocationName <TwnLctnNm> [0..1] Text 416

DistrictName <DstrctNm> [0..1] Text 416

CountrySubDivision <CtrySubDvsn> [0..1] Text 417

Country <Ctry> [0..1] CodeSet C6 417

AddressLine <AdrLine> [0..7] Text 417

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

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

No.

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

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

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

Exceptions and Investigations - Maintenance 2020 - 2021 181 December 2020

For evaluation by the Payments SEG Message Items Types

FinancialInstitutionIdentification <FinInstnId> contains the following elements (see

"FinancialInstitutionIdentification18" on page 177 for details)

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

No.

BICFI <BICFI> [0..1] IdentifierSet C5 177

ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] ± 178

LEI <LEI> [0..1] IdentifierSet 178

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

PostalAddress <PstlAdr> [0..1] ± 178

Other <Othr> [0..1] ± 179

10.1.9.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 180 for
details)

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

No.

Identification <Id> [0..1] Text 180

LEI <LEI> [0..1] IdentifierSet 180

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

PostalAddress <PstlAdr> [0..1] ± 180

10.1.9.5 GenericFinancialIdentification1
Definition: Information related to an identification of a financial institution.

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

No.

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

SchemeName <SchmeNm> [0..1] 183

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

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

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

10.1.9.5.1 Identification <Id>

Presence: [1..1]
Definition: Unique and unambiguous identification of a person.

Exceptions and Investigations - Maintenance 2020 - 2021 182 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.9.5.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
FinancialIdentificationSchemeName1Choice elements

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

No.

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

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

10.1.9.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 467

10.1.9.5.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 483

10.1.9.5.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.10 Identification Information

10.1.10.1 GenericIdentification3
Definition: Information related to an identification, for example, party identification or account
identification.

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

No.

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

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

10.1.10.1.1 Identification <Id>

Presence: [1..1]
Definition: Name or number assigned by an entity to enable recognition of that entity, for example,
account identifier.

Exceptions and Investigations - Maintenance 2020 - 2021 183 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.10.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.10.2 GenericIdentification30
Definition: Information related to an identification, for example, party identification or account
identification.

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

No.

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

Issuer <Issr> [1..1] Text 184

SchemeName <SchmeNm> [0..1] Text 184

10.1.10.2.1 Identification <Id>

Presence: [1..1]
Definition: Proprietary information, often a code, issued by the data source scheme issuer.
Datatype: "Exact4AlphaNumericText" on page 481

10.1.10.2.2 Issuer <Issr>

Presence: [1..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.10.2.3 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Short textual description of the scheme.
Datatype: "Max35Text" on page 483

10.1.11 Investigation
10.1.11.1 UnderlyingStatementEntry3
Definition: Provides further details on the underlying statement entry, to which the investigation
message refers.

Exceptions and Investigations - Maintenance 2020 - 2021 184 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 185

OriginalStatementIdentification <OrgnlStmtId> [0..1] Text 185

OriginalEntryIdentification <OrgnlNtryId> [0..1] Text 185

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 185

10.1.11.1.1 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Set of elements used to provide information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

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

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.11.1.2 OriginalStatementIdentification <OrgnlStmtId>

Presence: [0..1]
Definition: Unique identification, as assigned by the account servicer, to unambiguously identify the
original statement.
Datatype: "Max35Text" on page 483

10.1.11.1.3 OriginalEntryIdentification <OrgnlNtryId>

Presence: [0..1]
Definition: Original unique identification, as assigned by the account servicer, to unambiguously identify
the original entry.
Datatype: "Max35Text" on page 483

10.1.11.1.4 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.11.2 InvestigationStatus5Choice
Definition: Specifies the status of an investigation case.

Exceptions and Investigations - Maintenance 2020 - 2021 185 December 2020

For evaluation by the Payments SEG Message Items Types

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

No.

{Or Confirmation <Conf> [1..1] CodeSet 186

Or RejectedModification <RjctdMod> [1..*] 186

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

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

Or DuplicateOf <DplctOf> [1..1] ± 186

Or} AssignmentCancellationConfirmation <AssgnmtCxlConf> [1..1] Indicator 187

10.1.11.2.1 Confirmation <Conf>

Presence: [1..1]
Definition: Specifies the status of the investigation, in a coded form.
Datatype: "ExternalInvestigationExecutionConfirmation1Code" on page 468

10.1.11.2.2 RejectedModification <RjctdMod>

Presence: [1..*]
Definition: Reason for the rejection of a modification request, in a coded form.
RejectedModification <RjctdMod> contains one of the following ModificationStatusReason1Choice
elements

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

No.

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

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

10.1.11.2.2.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the modification status, in a coded form.
Datatype: "ExternalPaymentModificationRejection1Code" on page 469

10.1.11.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the status, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.11.2.3 DuplicateOf <DplctOf>

Presence: [1..1]
Definition: Indicates a duplicated case.

Usage: When present, the case identified in the message must be closed. The case identified as
duplicated (in this component) will be pursued.

Exceptions and Investigations - Maintenance 2020 - 2021 186 December 2020

For evaluation by the Payments SEG Message Items Types

DuplicateOf <DplctOf> contains the following elements (see "Case5" on page 188 for details)

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.11.2.4 AssignmentCancellationConfirmation <AssgnmtCxlConf>

Presence: [1..1]
Definition: Indicates whether the cancellation of the assignment is confirmed or rejected.

Usage: If yes, the cancellation of the assignment is confirmed.

If no, the cancellation of the assignment is rejected and the investigation process will continue.
Datatype: One of the following values must be used (see "YesNoIndicator" on page 480):

• Meaning When True: Yes

• Meaning When False: No

10.1.11.3 CaseAssignment5
Definition: Represents the assignment of a case to a party.

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

No.

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

Assigner <Assgnr> [1..1] ± 187

Assignee <Assgne> [1..1] ± 188

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

10.1.11.3.1 Identification <Id>

Presence: [1..1]
Definition: Uniquely identifies the case assignment.
Datatype: "Max35Text" on page 483

10.1.11.3.2 Assigner <Assgnr>

Presence: [1..1]
Definition: Party who assigns the case.

Usage: This is also the sender of the message.

Exceptions and Investigations - Maintenance 2020 - 2021 187 December 2020

For evaluation by the Payments SEG Message Items Types

Assigner <Assgnr> contains one of the following elements (see "Party40Choice" on page 209 for
details)

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

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.11.3.3 Assignee <Assgne>

Presence: [1..1]
Definition: Party to which the case is assigned.

Usage: This is also the receiver of the message.

Assignee <Assgne> contains one of the following elements (see "Party40Choice" on page 209 for
details)

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

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.11.3.4 CreationDateTime <CreDtTm>

Presence: [1..1]
Definition: Date and time at which the assignment was created.
Datatype: "ISODateTime" on page 477

10.1.11.4 Case5
Definition: Provides further details to identify an investigation case.

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

No.

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

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.11.4.1 Identification <Id>

Presence: [1..1]
Definition: Uniquely identifies the case.
Datatype: "Max35Text" on page 483

10.1.11.4.2 Creator <Cretr>

Presence: [1..1]
Definition: Party that created the investigation case.

Exceptions and Investigations - Maintenance 2020 - 2021 188 December 2020

For evaluation by the Payments SEG Message Items Types

Creator <Cretr> contains one of the following elements (see "Party40Choice" on page 209 for details)

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

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.11.4.3 ReopenCaseIndication <ReopCaseIndctn>

Presence: [0..1]
Definition: Indicates whether or not the case was previously closed and is now re-opened.
Datatype: One of the following values must be used (see "YesNoIndicator" on page 480):

• Meaning When True: Yes

• Meaning When False: No

10.1.11.5 StatementResolutionEntry4
Definition: Provides further details on the statement entry for the resolution of the investigation.

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

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 189

OriginalStatementIdentification <OrgnlStmtId> [0..1] Text 189

UETR <UETR> [0..1] IdentifierSet 190

AccountServicerReference <AcctSvcrRef> [0..1] Text 190

CorrectedAmount <CrrctdAmt> [0..1] Amount C1, C7 190

Charges <Chrgs> [0..*] ± 190

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

10.1.11.5.1 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Provides information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

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

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.11.5.2 OriginalStatementIdentification <OrgnlStmtId>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 189 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Unique identification, as assigned by the account servicer, to unambiguously identify the
original statement.
Datatype: "Max35Text" on page 483

10.1.11.5.3 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.11.5.4 AccountServicerReference <AcctSvcrRef>

Presence: [0..1]
Definition: Unique reference, as assigned by the account servicing institution, to unambiguously identify
the entry.
Datatype: "Max35Text" on page 483

10.1.11.5.5 CorrectedAmount <CrrctdAmt>

Presence: [0..1]
Definition: Corrected debit or credit amount, compared to the original entry where the amount is
incorrect.

Usage: This amount may only be present if an incorrect statement entry has been reported.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

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

Note: The decimal separator is a dot.

10.1.11.5.6 Charges <Chrgs>

Presence: [0..*]
Definition: Provides information on the charges included in the original entry amount.
Charges <Chrgs> contains the following elements (see "Charges6" on page 151 for details)

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

No.

TotalChargesAndTaxAmount <TtlChrgsAndTaxAmt> [0..1] Amount C1, C7 151

Record <Rcrd> [0..*] ± 151

Exceptions and Investigations - Maintenance 2020 - 2021 190 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.11.5.7 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 194 for
details)

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

No.

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

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

10.1.12 Mandate
10.1.12.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.

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

No.

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

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

10.1.12.1.1 Code <Cd>

Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: "MandateClassification1Code" on page 472

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.

10.1.12.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 191 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.12.2 MandateTypeInformation2
Definition: Set of elements used to further detail the information related to the type of payment.

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

No.

ServiceLevel <SvcLvl> [0..1] 192

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

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

LocalInstrument <LclInstrm> [0..1] 192

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

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

CategoryPurpose <CtgyPurp> [0..1] 193

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

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

Classification <Clssfctn> [0..1] ± 193

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

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

No.

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

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

10.1.12.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 470

10.1.12.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 483

10.1.12.2.2 LocalInstrument <LclInstrm>

Presence: [0..1]
Definition: User community specific instrument.

Exceptions and Investigations - Maintenance 2020 - 2021 192 December 2020

For evaluation by the Payments SEG Message Items Types

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

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

No.

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

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

10.1.12.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 468

10.1.12.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the local instrument, as a proprietary code.
Datatype: "Max35Text" on page 483

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

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

No.

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

Or} Proprietary <Prtry> [1..1] Text 193

10.1.12.2.3.1 Code <Cd>

Presence: [1..1]
Definition: Category purpose, as published in an external category purpose code list.
Datatype: "ExternalCategoryPurpose1Code" on page 465

10.1.12.2.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.12.2.4 Classification <Clssfctn>

Presence: [0..1]
Definition: Type of direct debit instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 193 December 2020

For evaluation by the Payments SEG Message Items Types

Classification <Clssfctn> contains one of the following elements (see "MandateClassification1Choice"

on page 191 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 191

Or} Proprietary <Prtry> [1..1] Text 191

10.1.13 Miscellaneous
10.1.13.1 SupplementaryData1
Definition: Additional information that can not be captured in the structured fields and/or any other
specific block.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

10.1.13.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 483

10.1.13.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.

10.1.13.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.

Exceptions and Investigations - Maintenance 2020 - 2021 194 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.13.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 470

10.1.13.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Purpose, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.13.3 OriginalGroupInformation29
Definition: Unique and unambiguous identifier of the group of transactions as assigned by the original
instructing party.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.13.3.1 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]
Definition: Point to point reference assigned by the original instructing party to unambiguously identify
the original message.
Datatype: "Max35Text" on page 483

10.1.13.3.2 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers, for example,
pacs.003.001.01 or MT103.
Datatype: "Max35Text" on page 483

10.1.13.3.3 OriginalCreationDateTime <OrgnlCreDtTm>

Presence: [0..1]
Definition: Original date and time at which the message was created.
Datatype: "ISODateTime" on page 477

Exceptions and Investigations - Maintenance 2020 - 2021 195 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.13.4 Frequency36Choice
Definition: Choice of format for a frequency, for example, the frequency of payment.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Type <Tp> [1..1] CodeSet 196

Or Period <Prd> [1..1] 196

Type <Tp> [1..1] CodeSet 197

CountPerPeriod <CntPerPrd> [1..1] Quantity 197

Or} PointInTime <PtInTm> [1..1] 197

Type <Tp> [1..1] CodeSet 198

PointInTime <PtInTm> [1..1] Text 198

10.1.13.4.1 Type <Tp>

Presence: [1..1]
Definition: Specifies a frequency in terms of a specified period type.
Datatype: "Frequency6Code" on page 471

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.

10.1.13.4.2 Period <Prd>

Presence: [1..1]
Definition: Specifies a frequency in terms of a count per period within a specified period type.

Exceptions and Investigations - Maintenance 2020 - 2021 196 December 2020

For evaluation by the Payments SEG Message Items Types

Period <Prd> contains the following FrequencyPeriod1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] CodeSet 197

CountPerPeriod <CntPerPrd> [1..1] Quantity 197

10.1.13.4.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 471

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.

10.1.13.4.2.2 CountPerPeriod <CntPerPrd>

Presence: [1..1]
Definition: Number of instructions to be created and processed during the specified period.
Datatype: "DecimalNumber" on page 480

10.1.13.4.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] CodeSet 198

PointInTime <PtInTm> [1..1] Text 198

Exceptions and Investigations - Maintenance 2020 - 2021 197 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.13.4.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 471

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.

10.1.13.4.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 481

10.1.13.5 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.

Exceptions and Investigations - Maintenance 2020 - 2021 198 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 199

DiscountAppliedAmount <DscntApldAmt> [0..*] 200

Type <Tp> [0..1] 200

{Or Code <Cd> [1..1] CodeSet 200

Or} Proprietary <Prtry> [1..1] Text 200

Amount <Amt> [1..1] Amount C1, C7 200

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 201

TaxAmount <TaxAmt> [0..*] 201

Type <Tp> [0..1] 201

{Or Code <Cd> [1..1] CodeSet 202

Or} Proprietary <Prtry> [1..1] Text 202

Amount <Amt> [1..1] Amount C1, C7 202

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 202

Amount <Amt> [1..1] Amount C1, C7 203

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 203

Reason <Rsn> [0..1] Text 203

AdditionalInformation <AddtlInf> [0..1] Text 203

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 204

10.1.13.5.1 DuePayableAmount <DuePyblAmt>

Presence: [0..1]
Definition: Amount specified is the exact amount due and payable to the creditor.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

Exceptions and Investigations - Maintenance 2020 - 2021 199 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.13.5.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.
DiscountAppliedAmount <DscntApldAmt> contains the following DiscountAmountAndType1
elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 200

{Or Code <Cd> [1..1] CodeSet 200

Or} Proprietary <Prtry> [1..1] Text 200

Amount <Amt> [1..1] Amount C1, C7 200

10.1.13.5.2.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.
Type <Tp> contains one of the following DiscountAmountType1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 200

Or} Proprietary <Prtry> [1..1] Text 200

10.1.13.5.2.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: "ExternalDiscountAmountType1Code" on page 467

10.1.13.5.2.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: "Max35Text" on page 483

10.1.13.5.2.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 200 December 2020

For evaluation by the Payments SEG Message Items Types

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.13.5.3 CreditNoteAmount <CdtNoteAmt>

Presence: [0..1]
Definition: Amount specified for the referred document is the amount of a credit note.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.13.5.4 TaxAmount <TaxAmt>

Presence: [0..*]
Definition: Quantity of cash resulting from the calculation of the tax.
TaxAmount <TaxAmt> contains the following TaxAmountAndType1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 201

{Or Code <Cd> [1..1] CodeSet 202

Or} Proprietary <Prtry> [1..1] Text 202

Amount <Amt> [1..1] Amount C1, C7 202

10.1.13.5.4.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.

Exceptions and Investigations - Maintenance 2020 - 2021 201 December 2020

For evaluation by the Payments SEG Message Items Types

Type <Tp> contains one of the following TaxAmountType1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 202

Or} Proprietary <Prtry> [1..1] Text 202

10.1.13.5.4.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: "ExternalTaxAmountType1Code" on page 471

10.1.13.5.4.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the amount type, in a free-text form.
Datatype: "Max35Text" on page 483

10.1.13.5.4.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.13.5.5 AdjustmentAmountAndReason <AdjstmntAmtAndRsn>

Presence: [0..*]
Definition: Specifies detailed information on the amount and reason of the document adjustment.

Exceptions and Investigations - Maintenance 2020 - 2021 202 December 2020

For evaluation by the Payments SEG Message Items Types

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> contains the following

DocumentAdjustment1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C7 203

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 203

Reason <Rsn> [0..1] Text 203

AdditionalInformation <AddtlInf> [0..1] Text 203

10.1.13.5.5.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money of the document adjustment.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.13.5.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 463

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

10.1.13.5.5.3 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the adjustment.
Datatype: "Max4Text" on page 483

10.1.13.5.5.4 AdditionalInformation <AddtlInf>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 203 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Provides further details on the document adjustment.

Datatype: "Max140Text" on page 482

10.1.13.5.6 RemittedAmount <RmtdAmt>

Presence: [0..1]
Definition: Amount of money remitted for the referred document.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.14 Organisation Identification

10.1.14.1 OrganisationIdentification29
Definition: Unique and unambiguous way to identify an organisation.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AnyBIC <AnyBIC> [0..1] IdentifierSet C4 204

LEI <LEI> [0..1] IdentifierSet 205

Other <Othr> [0..*] 205

Identification <Id> [1..1] Text 205

SchemeName <SchmeNm> [0..1] 205

{Or Code <Cd> [1..1] CodeSet 205

Or} Proprietary <Prtry> [1..1] Text 206

Issuer <Issr> [0..1] Text 206

10.1.14.1.1 AnyBIC <AnyBIC>

Presence: [0..1]
Definition: Business identification code of the organisation.
Impacted by: C4 "AnyBIC"
Datatype: "AnyBICDec2014Identifier" on page 478

Exceptions and Investigations - Maintenance 2020 - 2021 204 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.14.1.2 LEI <LEI>

Presence: [0..1]
Definition: Legal entity identification as an alternate identification for a party.
Datatype: "LEIIdentifier" on page 479

10.1.14.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 205

SchemeName <SchmeNm> [0..1] 205

{Or Code <Cd> [1..1] CodeSet 205

Or} Proprietary <Prtry> [1..1] Text 206

Issuer <Issr> [0..1] Text 206

10.1.14.1.3.1 Identification <Id>

Presence: [1..1]
Definition: Identification assigned by an institution.
Datatype: "Max35Text" on page 483

10.1.14.1.3.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
OrganisationIdentificationSchemeName1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 205

Or} Proprietary <Prtry> [1..1] Text 206

10.1.14.1.3.2.1 Code <Cd>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 205 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Name of the identification scheme, in a coded form as published in an external list.
Datatype: "ExternalOrganisationIdentification1Code" on page 468

10.1.14.1.3.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 483

10.1.14.1.3.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.15 Party Identification

10.1.15.1 PartyIdentification135
Definition: Specifies the identification of a person or an organisation.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.15.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 482

10.1.15.1.2 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Information that locates and identifies a specific address, as defined by postal services.

Exceptions and Investigations - Maintenance 2020 - 2021 206 December 2020

For evaluation by the Payments SEG Message Items Types

PostalAddress <PstlAdr> contains the following elements (see "PostalAddress24" on page 413 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 414

{Or Code <Cd> [1..1] CodeSet 414

Or} Proprietary <Prtry> [1..1] ± 415

Department <Dept> [0..1] Text 415

SubDepartment <SubDept> [0..1] Text 415

StreetName <StrtNm> [0..1] Text 415

BuildingNumber <BldgNb> [0..1] Text 415

BuildingName <BldgNm> [0..1] Text 416

Floor <Flr> [0..1] Text 416

PostBox <PstBx> [0..1] Text 416

Room <Room> [0..1] Text 416

PostCode <PstCd> [0..1] Text 416

TownName <TwnNm> [0..1] Text 416

TownLocationName <TwnLctnNm> [0..1] Text 416

DistrictName <DstrctNm> [0..1] Text 416

CountrySubDivision <CtrySubDvsn> [0..1] Text 417

Country <Ctry> [0..1] CodeSet C6 417

AddressLine <AdrLine> [0..7] Text 417

10.1.15.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 208 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or OrganisationIdentification <OrgId> [1..1] ± 208

Or} PrivateIdentification <PrvtId> [1..1] ± 209

10.1.15.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.

Exceptions and Investigations - Maintenance 2020 - 2021 207 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C6 "Country"

Datatype: "CountryCode" on page 462

Constraints

• Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166,
Alpha-2 code).

10.1.15.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 410 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

NamePrefix <NmPrfx> [0..1] CodeSet 411

Name <Nm> [0..1] Text 411

PhoneNumber <PhneNb> [0..1] Text 411

MobileNumber <MobNb> [0..1] Text 412

FaxNumber <FaxNb> [0..1] Text 412

EmailAddress <EmailAdr> [0..1] Text 412

EmailPurpose <EmailPurp> [0..1] Text 412

JobTitle <JobTitl> [0..1] Text 412

Responsibility <Rspnsblty> [0..1] Text 412

Department <Dept> [0..1] Text 412

Other <Othr> [0..*] 412

ChannelType <ChanlTp> [1..1] Text 413

Identification <Id> [0..1] Text 413

PreferredMethod <PrefrdMtd> [0..1] CodeSet 413

10.1.15.2 Party38Choice
Definition: Nature or use of the account.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or OrganisationIdentification <OrgId> [1..1] ± 208

Or} PrivateIdentification <PrvtId> [1..1] ± 209

10.1.15.2.1 OrganisationIdentification <OrgId>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 208 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Unique and unambiguous way to identify an organisation.

OrganisationIdentification <OrgId> contains the following elements (see
"OrganisationIdentification29" on page 204 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AnyBIC <AnyBIC> [0..1] IdentifierSet C4 204

LEI <LEI> [0..1] IdentifierSet 205

Other <Othr> [0..*] 205

Identification <Id> [1..1] Text 205

SchemeName <SchmeNm> [0..1] 205

{Or Code <Cd> [1..1] CodeSet 205

Or} Proprietary <Prtry> [1..1] Text 206

Issuer <Issr> [0..1] Text 206

10.1.15.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 408 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 408

BirthDate <BirthDt> [1..1] Date 409

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 409

CityOfBirth <CityOfBirth> [1..1] Text 409

CountryOfBirth <CtryOfBirth> [1..1] CodeSet C6 409

Other <Othr> [0..*] 409

Identification <Id> [1..1] Text 409

SchemeName <SchmeNm> [0..1] 410

{Or Code <Cd> [1..1] CodeSet 410

Or} Proprietary <Prtry> [1..1] Text 410

Issuer <Issr> [0..1] Text 410

10.1.15.3 Party40Choice
Definition: Identification of a person, an organisation or a financial institution.

Exceptions and Investigations - Maintenance 2020 - 2021 209 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.15.3.1 Party <Pty>

Presence: [1..1]
Definition: Identification of a person or an organisation.
Party <Pty> contains the following elements (see "PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.15.3.2 Agent <Agt>

Presence: [1..1]
Definition: Identification of a financial institution.
Agent <Agt> contains the following elements (see "BranchAndFinancialInstitutionIdentification6" on
page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16 Payment
10.1.16.1 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.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 211

InstructionInformation <InstrInf> [0..1] Text 211

Exceptions and Investigations - Maintenance 2020 - 2021 210 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.1.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 creditor's agent.
Datatype: "ExternalCreditorAgentInstruction1Code" on page 466

10.1.16.1.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 482

10.1.16.2 UnderlyingTransaction7Choice
Definition: Provides details of the underlying transaction, on which the investigation is processed.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Initiation <Initn> [1..1] ± C15, 211

C17

Or Interbank <IntrBk> [1..1] ± C16 214

Or} StatementEntry <StmtNtry> [1..1] ± 216

10.1.16.2.1 Initiation <Initn>

Presence: [1..1]
Definition: Set of elements used to reference the details of the original payment initiation.
Impacted by: C15 "OriginalIdentificationRule", C17 "OriginalRequestedDateRule"

Exceptions and Investigations - Maintenance 2020 - 2021 211 December 2020

For evaluation by the Payments SEG Message Items Types

Initiation <Initn> contains the following elements (see "UnderlyingPaymentInstruction7" on page 238
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] 240

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 241

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 241

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 241

OriginalMessageDeliveryChannel [0..1] Text 241

<OrgnlMsgDlvryChanl>

OriginalPaymentInformationIdentification [0..1] Text 241

<OrgnlPmtInfId>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 241

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 242

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 242

OriginalInstructedAmount <OrgnlInstdAmt> [1..1] Amount C1, C7 242

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 242

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 243

OriginalTransactionReference <OrgnlTxRef> [0..1] 243

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 245

Amount <Amt> [0..1] ± 245

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 246

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 246

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 246

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 246

SettlementInformation <SttlmInf> [0..1] C11, 246

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 248

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 249

ClearingSystem <ClrSys> [0..1] 249

{Or Code <Cd> [1..1] CodeSet 250

Or} Proprietary <Prtry> [1..1] Text 250

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 250

Exceptions and Investigations - Maintenance 2020 - 2021 212 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructingReimbursementAgentAccount [0..1] ± C10, C9 250

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 251

InstructedReimbursementAgentAccount [0..1] ± C10, C9 251

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 252

ThirdReimbursementAgentAccount [0..1] ± C10, C9 252

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 253

PaymentMethod <PmtMtd> [0..1] CodeSet 254

MandateRelatedInformation <MndtRltdInf> [0..1] ± 254

RemittanceInformation <RmtInf> [0..1] ± 255

UltimateDebtor <UltmtDbtr> [0..1] ± 255

Debtor <Dbtr> [0..1] ± 255

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 255

DebtorAgent <DbtrAgt> [0..1] ± 256

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 256

CreditorAgent <CdtrAgt> [0..1] ± 257

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 257

Creditor <Cdtr> [0..1] ± 258

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 258

UltimateCreditor <UltmtCdtr> [0..1] ± 259

Purpose <Purp> [0..1] ± 259

Constraints

• OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must be
present.
Following Must be True
/OriginalInstructionIdentification Must be present
Or /OriginalEndToEndIdentification Must be present
Or /OriginalUETR Must be present

• OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.
Following Must be True
/RequestedExecutionDate Must be present
Or /RequestedCollectionDate Must be present

Exceptions and Investigations - Maintenance 2020 - 2021 213 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.2.2 Interbank <IntrBk>

Presence: [1..1]
Definition: Set of elements used to reference the details of the original interbank payment transaction.
Impacted by: C16 "OriginalIdentificationRule"

Exceptions and Investigations - Maintenance 2020 - 2021 214 December 2020

For evaluation by the Payments SEG Message Items Types

Interbank <IntrBk> contains the following elements (see "UnderlyingPaymentTransaction6" on

page 217 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] 219

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 220

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 220

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 220

OriginalMessageDeliveryChannel [0..1] Text 220

<OrgnlMsgDlvryChanl>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 220

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 220

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 221

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 221

OriginalInterbankSettlementAmount [1..1] Amount C1, C7 221

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [1..1] Date 221

OriginalTransactionReference <OrgnlTxRef> [0..1] 221

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 223

Amount <Amt> [0..1] ± 223

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 224

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 224

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 224

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 224

SettlementInformation <SttlmInf> [0..1] C11, 224

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 226

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 227

ClearingSystem <ClrSys> [0..1] 227

{Or Code <Cd> [1..1] CodeSet 228

Or} Proprietary <Prtry> [1..1] Text 228

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 228

Exceptions and Investigations - Maintenance 2020 - 2021 215 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructingReimbursementAgentAccount [0..1] ± C10, C9 228

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 229

InstructedReimbursementAgentAccount [0..1] ± C10, C9 229

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 230

ThirdReimbursementAgentAccount [0..1] ± C10, C9 230

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 231

PaymentMethod <PmtMtd> [0..1] CodeSet 232

MandateRelatedInformation <MndtRltdInf> [0..1] ± 232

RemittanceInformation <RmtInf> [0..1] ± 233

UltimateDebtor <UltmtDbtr> [0..1] ± 233

Debtor <Dbtr> [0..1] ± 233

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 233

DebtorAgent <DbtrAgt> [0..1] ± 234

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 234

CreditorAgent <CdtrAgt> [0..1] ± 235

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 235

Creditor <Cdtr> [0..1] ± 236

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 236

UltimateCreditor <UltmtCdtr> [0..1] ± 237

Purpose <Purp> [0..1] ± 237

Constraints

• OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.
Following Must be True
/OriginalInstructionIdentification Must be present
Or /OriginalEndToEndIdentification Must be present
Or /OriginalTransactionIdentification Must be present
Or /OriginalUETR Must be present

10.1.16.2.3 StatementEntry <StmtNtry>

Presence: [1..1]
Definition: Reference details on the underlying statement cash entry.

Exceptions and Investigations - Maintenance 2020 - 2021 216 December 2020

For evaluation by the Payments SEG Message Items Types

StatementEntry <StmtNtry> contains the following elements (see "UnderlyingStatementEntry3" on

page 184 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 185

OriginalStatementIdentification <OrgnlStmtId> [0..1] Text 185

OriginalEntryIdentification <OrgnlNtryId> [0..1] Text 185

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 185

10.1.16.3 UnderlyingPaymentTransaction6
Definition: Provides further details on the original payment transaction, to which the investigation
message refers.

Exceptions and Investigations - Maintenance 2020 - 2021 217 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] 219

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 220

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 220

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 220

OriginalMessageDeliveryChannel [0..1] Text 220

<OrgnlMsgDlvryChanl>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 220

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 220

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 221

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 221

OriginalInterbankSettlementAmount [1..1] Amount C1, C7 221

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [1..1] Date 221

OriginalTransactionReference <OrgnlTxRef> [0..1] 221

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 223

Amount <Amt> [0..1] ± 223

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 224

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 224

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 224

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 224

SettlementInformation <SttlmInf> [0..1] C11, 224

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 226

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 227

ClearingSystem <ClrSys> [0..1] 227

{Or Code <Cd> [1..1] CodeSet 228

Or} Proprietary <Prtry> [1..1] Text 228

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 228

InstructingReimbursementAgentAccount [0..1] ± C10, C9 228

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 229

Exceptions and Investigations - Maintenance 2020 - 2021 218 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructedReimbursementAgentAccount [0..1] ± C10, C9 229

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 230

ThirdReimbursementAgentAccount [0..1] ± C10, C9 230

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 231

PaymentMethod <PmtMtd> [0..1] CodeSet 232

MandateRelatedInformation <MndtRltdInf> [0..1] ± 232

RemittanceInformation <RmtInf> [0..1] ± 233

UltimateDebtor <UltmtDbtr> [0..1] ± 233

Debtor <Dbtr> [0..1] ± 233

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 233

DebtorAgent <DbtrAgt> [0..1] ± 234

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 234

CreditorAgent <CdtrAgt> [0..1] ± 235

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 235

Creditor <Cdtr> [0..1] ± 236

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 236

UltimateCreditor <UltmtCdtr> [0..1] ± 237

Purpose <Purp> [0..1] ± 237

Constraints

• OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification,
OriginalTransactionIdentification or OriginalUETR must be present.
Following Must be True
/OriginalInstructionIdentification Must be present
Or /OriginalEndToEndIdentification Must be present
Or /OriginalTransactionIdentification Must be present
Or /OriginalUETR Must be present

10.1.16.3.1 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Set of elements used to provide information on the original message.

Exceptions and Investigations - Maintenance 2020 - 2021 219 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalGroupInformation <OrgnlGrpInf> contains the following UnderlyingGroupInformation1

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 220

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 220

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 220

OriginalMessageDeliveryChannel <OrgnlMsgDlvryChanl> [0..1] Text 220

10.1.16.3.1.1 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]
Definition: Point to point reference, as assigned by the original instructing party, to unambiguously
identify the original message.
Datatype: "Max35Text" on page 483

10.1.16.3.1.2 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

10.1.16.3.1.3 OriginalCreationDateTime <OrgnlCreDtTm>

Presence: [0..1]
Definition: Date and time at which the original message was created.
Datatype: "ISODateTime" on page 477

10.1.16.3.1.4 OriginalMessageDeliveryChannel <OrgnlMsgDlvryChanl>

Presence: [0..1]
Definition: Original channel used for the delivery of the message, to allow the receiver of the request to
locate the payment with greater ease.
Datatype: "Max35Text" on page 483

10.1.16.3.2 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.3.3 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 220 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.3.4 OriginalTransactionIdentification <OrgnlTxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

10.1.16.3.5 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.3.6 OriginalInterbankSettlementAmount <OrgnlIntrBkSttlmAmt>

Presence: [1..1]
Definition: Amount of money moved between the instructing agent and the instructed agent, as provided
in the original instruction.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.3.7 OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt>

Presence: [1..1]
Definition: Date, as provided in the original transaction, 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 477

10.1.16.3.8 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 221 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 223

Amount <Amt> [0..1] ± 223

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 224

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 224

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 224

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 224

SettlementInformation <SttlmInf> [0..1] C11, 224

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 226

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 227

ClearingSystem <ClrSys> [0..1] 227

{Or Code <Cd> [1..1] CodeSet 228

Or} Proprietary <Prtry> [1..1] Text 228

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 228

InstructingReimbursementAgentAccount [0..1] ± C10, C9 228

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 229

InstructedReimbursementAgentAccount [0..1] ± C10, C9 229

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 230

ThirdReimbursementAgentAccount [0..1] ± C10, C9 230

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 231

PaymentMethod <PmtMtd> [0..1] CodeSet 232

MandateRelatedInformation <MndtRltdInf> [0..1] ± 232

RemittanceInformation <RmtInf> [0..1] ± 233

UltimateDebtor <UltmtDbtr> [0..1] ± 233

Debtor <Dbtr> [0..1] ± 233

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 233

Exceptions and Investigations - Maintenance 2020 - 2021 222 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 234

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 234

CreditorAgent <CdtrAgt> [0..1] ± 235

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 235

Creditor <Cdtr> [0..1] ± 236

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 236

UltimateCreditor <UltmtCdtr> [0..1] ± 237

Purpose <Purp> [0..1] ± 237

10.1.16.3.8.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.3.8.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 223 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.3.8.3 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 477

10.1.16.3.8.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.3.8.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.3.8.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.3.8.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 224 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 226

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 227

ClearingSystem <ClrSys> [0..1] 227

{Or Code <Cd> [1..1] CodeSet 228

Or} Proprietary <Prtry> [1..1] Text 228

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 228

InstructingReimbursementAgentAccount [0..1] ± C10, C9 228

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 229

InstructedReimbursementAgentAccount [0..1] ± C10, C9 229

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 230

ThirdReimbursementAgentAccount [0..1] ± C10, C9 230

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 225 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.3.8.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 226 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.3.8.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 227 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 228

Or} Proprietary <Prtry> [1..1] Text 228

10.1.16.3.8.7.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 465

10.1.16.3.8.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.3.8.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.3.8.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 228 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.3.8.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 229 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.3.8.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 230 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 231 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.3.8.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.3.8.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 232 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.3.8.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.3.8.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.3.8.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.3.8.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 233 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.3.8.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 234 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.3.8.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 235 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.3.8.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 236 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.3.8.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.3.8.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 237 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.4 UnderlyingPaymentInstruction7
Definition: Provides further details on the original payment initiation, to which the investigation message
refers.

Exceptions and Investigations - Maintenance 2020 - 2021 238 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalGroupInformation <OrgnlGrpInf> [0..1] 240

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 241

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 241

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 241

OriginalMessageDeliveryChannel [0..1] Text 241

<OrgnlMsgDlvryChanl>

OriginalPaymentInformationIdentification [0..1] Text 241

<OrgnlPmtInfId>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 241

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 242

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 242

OriginalInstructedAmount <OrgnlInstdAmt> [1..1] Amount C1, C7 242

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 242

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 243

OriginalTransactionReference <OrgnlTxRef> [0..1] 243

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 245

Amount <Amt> [0..1] ± 245

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 246

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 246

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 246

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 246

SettlementInformation <SttlmInf> [0..1] C11, 246

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 248

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 249

ClearingSystem <ClrSys> [0..1] 249

{Or Code <Cd> [1..1] CodeSet 250

Or} Proprietary <Prtry> [1..1] Text 250

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 250

InstructingReimbursementAgentAccount [0..1] ± C10, C9 250

<InstgRmbrsmntAgtAcct>

Exceptions and Investigations - Maintenance 2020 - 2021 239 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 251

InstructedReimbursementAgentAccount [0..1] ± C10, C9 251

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 252

ThirdReimbursementAgentAccount [0..1] ± C10, C9 252

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 253

PaymentMethod <PmtMtd> [0..1] CodeSet 254

MandateRelatedInformation <MndtRltdInf> [0..1] ± 254

RemittanceInformation <RmtInf> [0..1] ± 255

UltimateDebtor <UltmtDbtr> [0..1] ± 255

Debtor <Dbtr> [0..1] ± 255

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 255

DebtorAgent <DbtrAgt> [0..1] ± 256

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 256

CreditorAgent <CdtrAgt> [0..1] ± 257

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 257

Creditor <Cdtr> [0..1] ± 258

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 258

UltimateCreditor <UltmtCdtr> [0..1] ± 259

Purpose <Purp> [0..1] ± 259

Constraints

• OriginalIdentificationRule
Either OriginalInstructionIdentification, OriginalEndToEndIdentification or OriginalUETR must be
present.
Following Must be True
/OriginalInstructionIdentification Must be present
Or /OriginalEndToEndIdentification Must be present
Or /OriginalUETR Must be present

• OriginalRequestedDateRule
Either RequestedExecutionDate or RequestedCollectionDate must be present.
Following Must be True
/RequestedExecutionDate Must be present
Or /RequestedCollectionDate Must be present

10.1.16.4.1 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 240 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Set of elements used to provide information on the original message.

OriginalGroupInformation <OrgnlGrpInf> contains the following UnderlyingGroupInformation1
elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 241

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 241

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 241

OriginalMessageDeliveryChannel <OrgnlMsgDlvryChanl> [0..1] Text 241

10.1.16.4.1.1 OriginalMessageIdentification <OrgnlMsgId>

Presence: [1..1]
Definition: Point to point reference, as assigned by the original instructing party, to unambiguously
identify the original message.
Datatype: "Max35Text" on page 483

10.1.16.4.1.2 OriginalMessageNameIdentification <OrgnlMsgNmId>

Presence: [1..1]
Definition: Specifies the original message name identifier to which the message refers.
Datatype: "Max35Text" on page 483

10.1.16.4.1.3 OriginalCreationDateTime <OrgnlCreDtTm>

Presence: [0..1]
Definition: Date and time at which the original message was created.
Datatype: "ISODateTime" on page 477

10.1.16.4.1.4 OriginalMessageDeliveryChannel <OrgnlMsgDlvryChanl>

Presence: [0..1]
Definition: Original channel used for the delivery of the message, to allow the receiver of the request to
locate the payment with greater ease.
Datatype: "Max35Text" on page 483

10.1.16.4.2 OriginalPaymentInformationIdentification <OrgnlPmtInfId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original sending party, to unambiguously identify the
original payment information group.
Datatype: "Max35Text" on page 483

10.1.16.4.3 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 241 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.16.4.4 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.4.5 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.4.6 OriginalInstructedAmount <OrgnlInstdAmt>

Presence: [1..1]
Definition: Amount of money, as provided in the original transaction, to be moved between the debtor
and the creditor, before deduction of charges, expressed in the currency, as ordered by the original
initiating party.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.4.7 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.

Exceptions and Investigations - Maintenance 2020 - 2021 242 December 2020

For evaluation by the Payments SEG Message Items Types

RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see

"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.4.8 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date at which the creditor requests the amount of money to be collected from the debtor.
Datatype: "ISODate" on page 477

10.1.16.4.9 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 243 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 245

Amount <Amt> [0..1] ± 245

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 246

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 246

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 246

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 246

SettlementInformation <SttlmInf> [0..1] C11, 246

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 248

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 249

ClearingSystem <ClrSys> [0..1] 249

{Or Code <Cd> [1..1] CodeSet 250

Or} Proprietary <Prtry> [1..1] Text 250

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 250

InstructingReimbursementAgentAccount [0..1] ± C10, C9 250

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 251

InstructedReimbursementAgentAccount [0..1] ± C10, C9 251

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 252

ThirdReimbursementAgentAccount [0..1] ± C10, C9 252

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 253

PaymentMethod <PmtMtd> [0..1] CodeSet 254

MandateRelatedInformation <MndtRltdInf> [0..1] ± 254

RemittanceInformation <RmtInf> [0..1] ± 255

UltimateDebtor <UltmtDbtr> [0..1] ± 255

Debtor <Dbtr> [0..1] ± 255

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 255

Exceptions and Investigations - Maintenance 2020 - 2021 244 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 256

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 256

CreditorAgent <CdtrAgt> [0..1] ± 257

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 257

Creditor <Cdtr> [0..1] ± 258

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 258

UltimateCreditor <UltmtCdtr> [0..1] ± 259

Purpose <Purp> [0..1] ± 259

10.1.16.4.9.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.4.9.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 245 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.4.9.3 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 477

10.1.16.4.9.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.4.9.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.4.9.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.4.9.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 246 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 248

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 249

ClearingSystem <ClrSys> [0..1] 249

{Or Code <Cd> [1..1] CodeSet 250

Or} Proprietary <Prtry> [1..1] Text 250

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 250

InstructingReimbursementAgentAccount [0..1] ± C10, C9 250

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 251

InstructedReimbursementAgentAccount [0..1] ± C10, C9 251

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 252

ThirdReimbursementAgentAccount [0..1] ± C10, C9 252

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 247 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.4.9.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 248 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.4.9.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 249 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 250

Or} Proprietary <Prtry> [1..1] Text 250

10.1.16.4.9.7.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 465

10.1.16.4.9.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.4.9.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.4.9.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 250 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.4.9.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 251 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.4.9.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 252 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 253 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.4.9.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.4.9.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 254 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.4.9.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.4.9.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.4.9.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.4.9.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 255 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.4.9.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 256 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.4.9.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 257 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.4.9.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 258 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.4.9.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.4.9.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 259 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.5 PaymentComplementaryInformation10
Definition: Provides further additional details on the underlying payment instruction that cannot be
transferred in a regular statement message.

Exceptions and Investigations - Maintenance 2020 - 2021 260 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionIdentification <InstrId> [0..1] Text 264

EndToEndIdentification <EndToEndId> [0..1] Text 264

TransactionIdentification <TxId> [0..1] Text 265

PaymentTypeInformation <PmtTpInf> [0..1] ± 265

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 265

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 266

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 266

Amount <Amt> [0..1] ± 266

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 266

ChargeBearer <ChrgBr> [0..1] CodeSet 267

UltimateDebtor <UltmtDbtr> [0..1] ± 267

Debtor <Dbtr> [0..1] ± 268

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 268

DebtorAgent <DbtrAgt> [0..1] ± 269

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 269

SettlementInformation <SttlmInf> [0..1] C11, 270

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 272

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 272

ClearingSystem <ClrSys> [0..1] 273

{Or Code <Cd> [1..1] CodeSet 273

Or} Proprietary <Prtry> [1..1] Text 273

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 273

InstructingReimbursementAgentAccount [0..1] ± C10, C9 274

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 274

InstructedReimbursementAgentAccount [0..1] ± C10, C9 275

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 275

ThirdReimbursementAgentAccount [0..1] ± C10, C9 276

<ThrdRmbrsmntAgtAcct>

Exceptions and Investigations - Maintenance 2020 - 2021 261 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

IntermediaryAgent1 <IntrmyAgt1> [0..1] ± 276

IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] ± C10, C9 277

IntermediaryAgent2 <IntrmyAgt2> [0..1] ± 277

IntermediaryAgent2Account <IntrmyAgt2Acct> [0..1] ± C10, C9 278

IntermediaryAgent3 <IntrmyAgt3> [0..1] ± 278

IntermediaryAgent3Account <IntrmyAgt3Acct> [0..1] ± C10, C9 279

CreditorAgent <CdtrAgt> [0..1] ± 279

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 280

Creditor <Cdtr> [0..1] ± 280

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 281

UltimateCreditor <UltmtCdtr> [0..1] ± 281

Purpose <Purp> [0..1] ± 282

InstructionForDebtorAgent <InstrForDbtrAgt> [0..1] Text 282

PreviousInstructingAgent1 <PrvsInstgAgt1> [0..1] ± 282

PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> [0..1] ± C10, C9 283

PreviousInstructingAgent2 <PrvsInstgAgt2> [0..1] ± 283

PreviousInstructingAgent2Account <PrvsInstgAgt2Acct> [0..1] ± C10, C9 284

PreviousInstructingAgent3 <PrvsInstgAgt3> [0..1] ± 284

PreviousInstructingAgent3Account <PrvsInstgAgt3Acct> [0..1] ± C10, C9 285

InstructionForNextAgent <InstrForNxtAgt> [0..*] 285

Code <Cd> [0..1] CodeSet 286

InstructionInformation <InstrInf> [0..1] Text 286

InstructionForCreditorAgent <InstrForCdtrAgt> [0..*] ± 286

RelatedRemittanceInformation <RltdRmtInf> [0..10] ± 286

RemittanceInformation <RmtInf> [0..1] ± 287

Constraints

• CreditorAgentAccountRule
If CreditorAgentAccount is present, then CreditorAgent must be present.
On Condition
/CreditorAgent is absent
Following Must be True
/CreditorAgentAccount Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 262 December 2020

For evaluation by the Payments SEG Message Items Types

• DebtorAgentAccountRule
If DebtorAgentAccount is present, then DebtorAgent must be present.
On Condition
/DebtorAgent is absent
Following Must be True
/DebtorAgentAccount Must be absent

• IntermediaryAgent1AccountRule
If IntermediaryAgent1Account is present, then IntermediaryAgent1 must be present.
On Condition
/IntermediaryAgent1 is absent
Following Must be True
/IntermediaryAgent1Account Must be absent

• IntermediaryAgent1Rule
If IntermediaryAgent1 is present, then CreditorAgent must be present.
On Condition
/IntermediaryAgent1 is present
Following Must be True
/CreditorAgent Must be present

• IntermediaryAgent2AccountRule
If IntermediaryAgent2Account is present, then IntermediaryAgent2 must be present.
On Condition
/IntermediaryAgent2 is absent
Following Must be True
/IntermediaryAgent2Account Must be absent

• IntermediaryAgent2Rule
If IntermediaryAgent2 is present, then IntermediaryAgent1 must be present.
On Condition
/IntermediaryAgent2 is present
Following Must be True
/IntermediaryAgent1 Must be present

• IntermediaryAgent3AccountRule
If IntermediaryAgent3Account is present, then IntermediaryAgent3 must be present.
On Condition
/IntermediaryAgent3 is absent
Following Must be True
/IntermediaryAgent3Account Must be absent

• IntermediaryAgent3Rule
If IntermediaryAgent3 is present, then IntermediaryAgent2 must be present.
On Condition
/IntermediaryAgent3 is present
Following Must be True
/IntermediaryAgent2 Must be present

• PreviousInstructingAgent1AccountRule
If PreviousInstructingAgent1Account is present, then PreviousInstructingAgent1 must be present.
On Condition
/PreviousInstructingAgent1 is absent
Following Must be True
/PreviousInstructingAgent1Account Must be absent

Exceptions and Investigations - Maintenance 2020 - 2021 263 December 2020

For evaluation by the Payments SEG Message Items Types

• 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.
On Condition
/PreviousInstructingAgent2 is absent
Following Must be True
/PreviousInstructingAgent2Account Must be absent

• PreviousInstructingAgent2Rule
If PreviousInstructingAgent2 is present, then PreviousInstructingAgent1 must be present.
On Condition
/PreviousInstructingAgent2 is present
Following Must be True
/PreviousInstructingAgent1 Must be present

• PreviousInstructingAgent3AccountRule
If PreviousInstructingAgent3Account is present, then PreviousInstructingAgent3 must be present.
On Condition
/PreviousInstructingAgent3 is absent
Following Must be True
/PreviousInstructingAgent3Account Must be absent

• PreviousInstructingAgent3Rule
If PreviousInstructingAgent3 is present, then PreviousInstructingAgent2 must be present.
On Condition
/PreviousInstructingAgent3 is present
Following Must be True
/PreviousInstructingAgent2 Must be present

10.1.16.5.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 483

10.1.16.5.2 EndToEndIdentification <EndToEndId>

Presence: [0..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.

Exceptions and Investigations - Maintenance 2020 - 2021 264 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.16.5.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.

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 483

10.1.16.5.4 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.
PaymentTypeInformation <PmtTpInf> contains the following elements (see
"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.5.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.

Exceptions and Investigations - Maintenance 2020 - 2021 265 December 2020

For evaluation by the Payments SEG Message Items Types

RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see

"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.5.6 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.5.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 477

10.1.16.5.8 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

10.1.16.5.9 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 266 December 2020

For evaluation by the Payments SEG Message Items Types

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.5.10 ChargeBearer <ChrgBr>

Presence: [0..1]
Definition: Specifies which party/parties will bear the charges associated with the processing of the
payment transaction.
Datatype: "ChargeBearerType1Code" on page 461

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.

10.1.16.5.11 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.

Exceptions and Investigations - Maintenance 2020 - 2021 267 December 2020

For evaluation by the Payments SEG Message Items Types

UltimateDebtor <UltmtDbtr> contains the following elements (see "PartyIdentification135" on

page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.5.12 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains the following elements (see "PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.5.13 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

Exceptions and Investigations - Maintenance 2020 - 2021 268 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.14 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.15 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

Exceptions and Investigations - Maintenance 2020 - 2021 269 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.16 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Instruction between two clearing agents stipulating the cash transfer characteristics between
the two parties.
Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13
"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 272

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 272

ClearingSystem <ClrSys> [0..1] 273

{Or Code <Cd> [1..1] CodeSet 273

Or} Proprietary <Prtry> [1..1] Text 273

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 273

InstructingReimbursementAgentAccount [0..1] ± C10, C9 274

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 274

InstructedReimbursementAgentAccount [0..1] ± C10, C9 275

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 275

ThirdReimbursementAgentAccount [0..1] ± C10, C9 276

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.

Exceptions and Investigations - Maintenance 2020 - 2021 270 December 2020

For evaluation by the Payments SEG Message Items Types

On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'
Following Must be True
/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent

Exceptions and Investigations - Maintenance 2020 - 2021 271 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.5.16.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

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.

10.1.16.5.16.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

Exceptions and Investigations - Maintenance 2020 - 2021 272 December 2020

For evaluation by the Payments SEG Message Items Types

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.16.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 273

Or} Proprietary <Prtry> [1..1] Text 273

10.1.16.5.16.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 465

10.1.16.5.16.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.5.16.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.

Exceptions and Investigations - Maintenance 2020 - 2021 273 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgent <InstgRmbrsmntAgt> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.16.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following
elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.16.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.

Exceptions and Investigations - Maintenance 2020 - 2021 274 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgent <InstdRmbrsmntAgt> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.16.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following
elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.16.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.

Exceptions and Investigations - Maintenance 2020 - 2021 275 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgent <ThrdRmbrsmntAgt> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.16.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.17 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.

Exceptions and Investigations - Maintenance 2020 - 2021 276 December 2020

For evaluation by the Payments SEG Message Items Types

IntermediaryAgent1 <IntrmyAgt1> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
IntermediaryAgent1Account <IntrmyAgt1Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.19 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.

Exceptions and Investigations - Maintenance 2020 - 2021 277 December 2020

For evaluation by the Payments SEG Message Items Types

IntermediaryAgent2 <IntrmyAgt2> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
IntermediaryAgent2Account <IntrmyAgt2Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.21 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.

Exceptions and Investigations - Maintenance 2020 - 2021 278 December 2020

For evaluation by the Payments SEG Message Items Types

IntermediaryAgent3 <IntrmyAgt3> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.22 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
IntermediaryAgent3Account <IntrmyAgt3Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.23 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.

Exceptions and Investigations - Maintenance 2020 - 2021 279 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgent <CdtrAgt> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.24 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on
page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.25 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.

Exceptions and Investigations - Maintenance 2020 - 2021 280 December 2020

For evaluation by the Payments SEG Message Items Types

Creditor <Cdtr> contains the following elements (see "PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.5.26 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.27 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.

Exceptions and Investigations - Maintenance 2020 - 2021 281 December 2020

For evaluation by the Payments SEG Message Items Types

UltimateCreditor <UltmtCdtr> contains the following elements (see "PartyIdentification135" on

page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.5.28 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 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.5.29 InstructionForDebtorAgent <InstrForDbtrAgt>

Presence: [0..1]
Definition: Further information related to the processing of the payment instruction, provided by the
initiating party, and intended for the debtor agent.
Datatype: "Max140Text" on page 482

10.1.16.5.30 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.

Exceptions and Investigations - Maintenance 2020 - 2021 282 December 2020

For evaluation by the Payments SEG Message Items Types

PreviousInstructingAgent1 <PrvsInstgAgt1> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.31 PreviousInstructingAgent1Account <PrvsInstgAgt1Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent 1 at its servicing
agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
PreviousInstructingAgent1Account <PrvsInstgAgt1Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.32 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.

Exceptions and Investigations - Maintenance 2020 - 2021 283 December 2020

For evaluation by the Payments SEG Message Items Types

PreviousInstructingAgent2 <PrvsInstgAgt2> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.33 PreviousInstructingAgent2Account <PrvsInstgAgt2Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent 2 at its servicing
agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
PreviousInstructingAgent2Account <PrvsInstgAgt2Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.34 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.

Exceptions and Investigations - Maintenance 2020 - 2021 284 December 2020

For evaluation by the Payments SEG Message Items Types

PreviousInstructingAgent3 <PrvsInstgAgt3> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.5.35 PreviousInstructingAgent3Account <PrvsInstgAgt3Acct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the previous instructing agent 3 at its servicing
agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
PreviousInstructingAgent3Account <PrvsInstgAgt3Acct> contains the following elements (see
"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.5.36 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.

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.

Exceptions and Investigations - Maintenance 2020 - 2021 285 December 2020

For evaluation by the Payments SEG Message Items Types

InstructionForNextAgent <InstrForNxtAgt> contains the following InstructionForNextAgent1

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 286

InstructionInformation <InstrInf> [0..1] Text 286

10.1.16.5.36.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 472

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.

10.1.16.5.36.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 482

10.1.16.5.37 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 210 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Code <Cd> [0..1] CodeSet 211

InstructionInformation <InstrInf> [0..1] Text 211

10.1.16.5.38 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.

Exceptions and Investigations - Maintenance 2020 - 2021 286 December 2020

For evaluation by the Payments SEG Message Items Types

RelatedRemittanceInformation <RltdRmtInf> contains the following elements (see

"RemittanceLocation7" on page 417 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

RemittanceIdentification <RmtId> [0..1] Text 417

RemittanceLocationDetails <RmtLctnDtls> [0..*] ± 417

10.1.16.5.39 RemittanceInformation <RmtInf>

Presence: [0..1]
Definition: Structured information that enables the matching, that is reconciliation, of a payment with the
items that the payment is intended to settle, such as commercial invoices in an account receivable
system.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.6 PaymentTransaction140
Definition: Provides reference and status information on the original transactions, included in the
original instruction, to which the cancellation request message applies.

Exceptions and Investigations - Maintenance 2020 - 2021 287 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CancellationIdentification <CxlId> [0..1] Text 289

Case <Case> [0..1] ± 289

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 290

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 290

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 290

OriginalInstructedAmount <OrgnlInstdAmt> [0..1] Amount C1, C7 290

OriginalRequestedExecutionDate <OrgnlReqdExctnDt> [0..1] ± 291

OriginalRequestedCollectionDate <OrgnlReqdColltnDt> [0..1] Date 291

CancellationReasonInformation <CxlRsnInf> [0..*] 291

Originator <Orgtr> [0..1] ± 291

Reason <Rsn> [0..1] ± 292

AdditionalInformation <AddtlInf> [0..*] Text 292

OriginalTransactionReference <OrgnlTxRef> [0..1] 292

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 294

Amount <Amt> [0..1] ± 294

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 295

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 295

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 295

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 295

SettlementInformation <SttlmInf> [0..1] C11, 295

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 297

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 298

ClearingSystem <ClrSys> [0..1] 298

{Or Code <Cd> [1..1] CodeSet 299

Or} Proprietary <Prtry> [1..1] Text 299

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 299

InstructingReimbursementAgentAccount [0..1] ± C10, C9 299

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 300

Exceptions and Investigations - Maintenance 2020 - 2021 288 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructedReimbursementAgentAccount [0..1] ± C10, C9 300

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 301

ThirdReimbursementAgentAccount [0..1] ± C10, C9 301

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 302

PaymentMethod <PmtMtd> [0..1] CodeSet 303

MandateRelatedInformation <MndtRltdInf> [0..1] ± 303

RemittanceInformation <RmtInf> [0..1] ± 304

UltimateDebtor <UltmtDbtr> [0..1] ± 304

Debtor <Dbtr> [0..1] ± 304

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 304

DebtorAgent <DbtrAgt> [0..1] ± 305

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 305

CreditorAgent <CdtrAgt> [0..1] ± 306

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 306

Creditor <Cdtr> [0..1] ± 307

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 307

UltimateCreditor <UltmtCdtr> [0..1] ± 308

Purpose <Purp> [0..1] ± 308

SupplementaryData <SplmtryData> [0..*] ± C22 309

10.1.16.6.1 CancellationIdentification <CxlId>

Presence: [0..1]
Definition: Unique identification, as assigned by the assigner, to unambiguously identify a cancellation
request.

Usage: The cancellation request identification can be used for reconciliation or to link tasks relating to
the cancellation request.
Datatype: "Max35Text" on page 483

10.1.16.6.2 Case <Case>

Presence: [0..1]
Definition: Set of elements to uniquely and unambiguously identify an exception or an investigation
workflow.

Exceptions and Investigations - Maintenance 2020 - 2021 289 December 2020

For evaluation by the Payments SEG Message Items Types

Case <Case> contains the following elements (see "Case5" on page 188 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 188

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.16.6.3 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.6.4 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.6.5 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.6.6 OriginalInstructedAmount <OrgnlInstdAmt>

Presence: [0..1]
Definition: Amount of money, as provided in the original transaction, to be moved between the debtor
and the creditor, before deduction of charges, expressed in the currency, as ordered by the original
initiating party.

Usage: This amount has to be transported unchanged through the transaction chain.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Exceptions and Investigations - Maintenance 2020 - 2021 290 December 2020

For evaluation by the Payments SEG Message Items Types

Note: The decimal separator is a dot.

10.1.16.6.7 OriginalRequestedExecutionDate <OrgnlReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party originally requested the clearing agent to process the
payment.
OriginalRequestedExecutionDate <OrgnlReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.6.8 OriginalRequestedCollectionDate <OrgnlReqdColltnDt>

Presence: [0..1]
Definition: Date at which the creditor originally requested the collection of the amount of money from the
debtor.
Datatype: "ISODate" on page 477

10.1.16.6.9 CancellationReasonInformation <CxlRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation reason.
CancellationReasonInformation <CxlRsnInf> contains the following PaymentCancellationReason5
elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 291

Reason <Rsn> [0..1] ± 292

AdditionalInformation <AddtlInf> [0..*] Text 292

10.1.16.6.9.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation request.

Exceptions and Investigations - Maintenance 2020 - 2021 291 December 2020

For evaluation by the Payments SEG Message Items Types

Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.6.9.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the cancellation.
Reason <Rsn> contains one of the following elements (see "CancellationReason33Choice" on
page 445 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 445

Or} Proprietary <Prtry> [1..1] Text 446

10.1.16.6.9.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

10.1.16.6.10 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 292 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 294

Amount <Amt> [0..1] ± 294

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 295

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 295

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 295

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 295

SettlementInformation <SttlmInf> [0..1] C11, 295

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 297

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 298

ClearingSystem <ClrSys> [0..1] 298

{Or Code <Cd> [1..1] CodeSet 299

Or} Proprietary <Prtry> [1..1] Text 299

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 299

InstructingReimbursementAgentAccount [0..1] ± C10, C9 299

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 300

InstructedReimbursementAgentAccount [0..1] ± C10, C9 300

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 301

ThirdReimbursementAgentAccount [0..1] ± C10, C9 301

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 302

PaymentMethod <PmtMtd> [0..1] CodeSet 303

MandateRelatedInformation <MndtRltdInf> [0..1] ± 303

RemittanceInformation <RmtInf> [0..1] ± 304

UltimateDebtor <UltmtDbtr> [0..1] ± 304

Debtor <Dbtr> [0..1] ± 304

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 304

Exceptions and Investigations - Maintenance 2020 - 2021 293 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 305

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 305

CreditorAgent <CdtrAgt> [0..1] ± 306

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 306

Creditor <Cdtr> [0..1] ± 307

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 307

UltimateCreditor <UltmtCdtr> [0..1] ± 308

Purpose <Purp> [0..1] ± 308

10.1.16.6.10.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.6.10.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 294 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.6.10.3 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 477

10.1.16.6.10.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.6.10.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.6.10.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.6.10.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 295 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 297

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 298

ClearingSystem <ClrSys> [0..1] 298

{Or Code <Cd> [1..1] CodeSet 299

Or} Proprietary <Prtry> [1..1] Text 299

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 299

InstructingReimbursementAgentAccount [0..1] ± C10, C9 299

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 300

InstructedReimbursementAgentAccount [0..1] ± C10, C9 300

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 301

ThirdReimbursementAgentAccount [0..1] ± C10, C9 301

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 296 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.6.10.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 297 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.6.10.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 298 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 299

Or} Proprietary <Prtry> [1..1] Text 299

10.1.16.6.10.7.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 465

10.1.16.6.10.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.6.10.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.6.10.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 299 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.6.10.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 300 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.6.10.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 301 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 302 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.6.10.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.6.10.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 303 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.6.10.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.6.10.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.6.10.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.6.10.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 304 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.6.10.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 305 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.6.10.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 306 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.6.10.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 307 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.6.10.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.6.10.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 308 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.6.11 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C22 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

10.1.16.7 PaymentTransaction139
Definition: Provides reference and status information on the original transactions, included in the
original instruction, to which the cancellation request message applies.

Exceptions and Investigations - Maintenance 2020 - 2021 309 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CancellationStatusIdentification <CxlStsId> [0..1] Text 311

ResolvedCase <RslvdCase> [0..1] ± 311

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 312

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 312

UETR <UETR> [0..1] IdentifierSet 312

TransactionCancellationStatus <TxCxlSts> [0..1] CodeSet 312

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 312

OriginalInstructedAmount <OrgnlInstdAmt> [0..1] Amount C1, C7 313

OriginalRequestedExecutionDate <OrgnlReqdExctnDt> [0..1] ± 313

OriginalRequestedCollectionDate <OrgnlReqdColltnDt> [0..1] Date 314

OriginalTransactionReference <OrgnlTxRef> [0..1] 314

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 316

Amount <Amt> [0..1] ± 316

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 317

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 317

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 317

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 317

SettlementInformation <SttlmInf> [0..1] C11, 317

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 319

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 320

ClearingSystem <ClrSys> [0..1] 320

{Or Code <Cd> [1..1] CodeSet 321

Or} Proprietary <Prtry> [1..1] Text 321

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 321

InstructingReimbursementAgentAccount [0..1] ± C10, C9 321

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 322

InstructedReimbursementAgentAccount [0..1] ± C10, C9 322

<InstdRmbrsmntAgtAcct>

Exceptions and Investigations - Maintenance 2020 - 2021 310 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 323

ThirdReimbursementAgentAccount [0..1] ± C10, C9 323

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 324

PaymentMethod <PmtMtd> [0..1] CodeSet 325

MandateRelatedInformation <MndtRltdInf> [0..1] ± 325

RemittanceInformation <RmtInf> [0..1] ± 326

UltimateDebtor <UltmtDbtr> [0..1] ± 326

Debtor <Dbtr> [0..1] ± 326

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 326

DebtorAgent <DbtrAgt> [0..1] ± 327

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 327

CreditorAgent <CdtrAgt> [0..1] ± 328

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 328

Creditor <Cdtr> [0..1] ± 329

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 329

UltimateCreditor <UltmtCdtr> [0..1] ± 330

Purpose <Purp> [0..1] ± 330

10.1.16.7.1 CancellationStatusIdentification <CxlStsId>

Presence: [0..1]
Definition: Unique and unambiguous identifier of a cancellation request status, as assigned by the
assigner.

Usage: The cancellation status identification can be used for reconciliation or to link tasks relating to the
cancellation request.
Datatype: "Max35Text" on page 483

10.1.16.7.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies the resolved case.

Exceptions and Investigations - Maintenance 2020 - 2021 311 December 2020

For evaluation by the Payments SEG Message Items Types

ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 188

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.16.7.3 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.7.4 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.7.5 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.7.6 TransactionCancellationStatus <TxCxlSts>

Presence: [0..1]
Definition: Specifies the status of the transaction cancellation request.
Datatype: "CancellationIndividualStatus1Code" on page 461

CodeName Name Definition

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

10.1.16.7.7 CancellationStatusReasonInformation <CxlStsRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation status reason.

Exceptions and Investigations - Maintenance 2020 - 2021 312 December 2020

For evaluation by the Payments SEG Message Items Types

CancellationStatusReasonInformation <CxlStsRsnInf> contains the following elements (see

"CancellationStatusReason4" on page 446 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 446

Reason <Rsn> [0..1] 446

{Or Code <Cd> [1..1] CodeSet 447

Or} Proprietary <Prtry> [1..1] Text 447

AdditionalInformation <AddtlInf> [0..*] Text 447

10.1.16.7.8 OriginalInstructedAmount <OrgnlInstdAmt>

Presence: [0..1]
Definition: Amount of money, as provided in the original transaction, to be moved between the debtor
and the creditor, before deduction of charges, expressed in the currency, as ordered by the original
initiating party.

Usage: This amount has to be transported unchanged through the transaction chain.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.7.9 OriginalRequestedExecutionDate <OrgnlReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party originally requested the clearing agent to process the
payment.
OriginalRequestedExecutionDate <OrgnlReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

Exceptions and Investigations - Maintenance 2020 - 2021 313 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.7.10 OriginalRequestedCollectionDate <OrgnlReqdColltnDt>

Presence: [0..1]
Definition: Date at which the creditor originally requested the collection of the amount of money from the
debtor.
Datatype: "ISODate" on page 477

10.1.16.7.11 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 314 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 316

Amount <Amt> [0..1] ± 316

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 317

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 317

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 317

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 317

SettlementInformation <SttlmInf> [0..1] C11, 317

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 319

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 320

ClearingSystem <ClrSys> [0..1] 320

{Or Code <Cd> [1..1] CodeSet 321

Or} Proprietary <Prtry> [1..1] Text 321

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 321

InstructingReimbursementAgentAccount [0..1] ± C10, C9 321

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 322

InstructedReimbursementAgentAccount [0..1] ± C10, C9 322

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 323

ThirdReimbursementAgentAccount [0..1] ± C10, C9 323

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 324

PaymentMethod <PmtMtd> [0..1] CodeSet 325

MandateRelatedInformation <MndtRltdInf> [0..1] ± 325

RemittanceInformation <RmtInf> [0..1] ± 326

UltimateDebtor <UltmtDbtr> [0..1] ± 326

Debtor <Dbtr> [0..1] ± 326

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 326

Exceptions and Investigations - Maintenance 2020 - 2021 315 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 327

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 327

CreditorAgent <CdtrAgt> [0..1] ± 328

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 328

Creditor <Cdtr> [0..1] ± 329

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 329

UltimateCreditor <UltmtCdtr> [0..1] ± 330

Purpose <Purp> [0..1] ± 330

10.1.16.7.11.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.7.11.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 316 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.7.11.3 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 477

10.1.16.7.11.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.7.11.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.7.11.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.7.11.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 317 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 319

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 320

ClearingSystem <ClrSys> [0..1] 320

{Or Code <Cd> [1..1] CodeSet 321

Or} Proprietary <Prtry> [1..1] Text 321

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 321

InstructingReimbursementAgentAccount [0..1] ± C10, C9 321

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 322

InstructedReimbursementAgentAccount [0..1] ± C10, C9 322

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 323

ThirdReimbursementAgentAccount [0..1] ± C10, C9 323

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 318 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.7.11.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 319 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.7.11.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 320 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 321

Or} Proprietary <Prtry> [1..1] Text 321

10.1.16.7.11.7.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 465

10.1.16.7.11.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.7.11.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.7.11.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 321 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.7.11.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 322 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.7.11.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 323 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 324 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.7.11.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.7.11.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 325 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.7.11.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.7.11.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.7.11.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.7.11.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 326 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.7.11.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 327 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.7.11.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 328 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.7.11.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 329 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.7.11.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.7.11.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 330 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.8 PaymentTransaction138
Definition: Provides further details on the reference and status on the original transactions, included in
the original instruction, to which the cancellation request message applies.

Exceptions and Investigations - Maintenance 2020 - 2021 331 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CancellationStatusIdentification <CxlStsId> [0..1] Text 334

ResolvedCase <RslvdCase> [0..1] ± 334

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 334

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 334

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 334

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 335

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 335

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 335

TransactionCancellationStatus <TxCxlSts> [0..1] CodeSet 335

CancellationStatusReasonInformation <CxlStsRsnInf> [0..*] ± 335

ResolutionRelatedInformation <RsltnRltdInf> [0..1] 336

EndToEndIdentification <EndToEndId> [0..1] Text 336

TransactionIdentification <TxId> [0..1] Text 336

UETR <UETR> [0..1] IdentifierSet 336

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 336

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 337

ClearingChannel <ClrChanl> [0..1] CodeSet 337

Compensation <Compstn> [0..1] ± 337

Charges <Chrgs> [0..*] ± 338

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 338

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 339

Assigner <Assgnr> [0..1] ± 339

Assignee <Assgne> [0..1] ± 339

OriginalTransactionReference <OrgnlTxRef> [0..1] 339

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 341

Amount <Amt> [0..1] ± 341

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 342

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 342

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 342

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 342

SettlementInformation <SttlmInf> [0..1] C11, 342

C13,

Exceptions and Investigations - Maintenance 2020 - 2021 332 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 344

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 345

ClearingSystem <ClrSys> [0..1] 345

{Or Code <Cd> [1..1] CodeSet 346

Or} Proprietary <Prtry> [1..1] Text 346

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 346

InstructingReimbursementAgentAccount [0..1] ± C10, C9 346

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 347

InstructedReimbursementAgentAccount [0..1] ± C10, C9 347

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 348

ThirdReimbursementAgentAccount [0..1] ± C10, C9 348

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 349

PaymentMethod <PmtMtd> [0..1] CodeSet 350

MandateRelatedInformation <MndtRltdInf> [0..1] ± 350

RemittanceInformation <RmtInf> [0..1] ± 351

UltimateDebtor <UltmtDbtr> [0..1] ± 351

Debtor <Dbtr> [0..1] ± 351

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 351

DebtorAgent <DbtrAgt> [0..1] ± 352

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 352

CreditorAgent <CdtrAgt> [0..1] ± 353

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 353

Creditor <Cdtr> [0..1] ± 354

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 354

UltimateCreditor <UltmtCdtr> [0..1] ± 355

Purpose <Purp> [0..1] ± 355

Exceptions and Investigations - Maintenance 2020 - 2021 333 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.8.1 CancellationStatusIdentification <CxlStsId>

Presence: [0..1]
Definition: Unique and unambiguous identifier of a cancellation request status, as assigned by the
assigner.

Usage: The cancellation status identification can be used for reconciliation or to link tasks relating to the
cancellation request.
Datatype: "Max35Text" on page 483

10.1.16.8.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies the resolved case.
ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 188

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.16.8.3 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Provides information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.16.8.4 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.8.5 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 334 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.8.6 OriginalTransactionIdentification <OrgnlTxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

10.1.16.8.7 OriginalClearingSystemReference <OrgnlClrSysRef>

Presence: [0..1]
Definition: Unique reference, as assigned by the original clearing system, to unambiguously identify the
original instruction.
Datatype: "Max35Text" on page 483

10.1.16.8.8 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.8.9 TransactionCancellationStatus <TxCxlSts>

Presence: [0..1]
Definition: Specifies the status of the transaction cancellation request.
Datatype: "CancellationIndividualStatus1Code" on page 461

CodeName Name Definition

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

10.1.16.8.10 CancellationStatusReasonInformation <CxlStsRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation status reason.
CancellationStatusReasonInformation <CxlStsRsnInf> contains the following elements (see
"CancellationStatusReason4" on page 446 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 446

Reason <Rsn> [0..1] 446

{Or Code <Cd> [1..1] CodeSet 447

Or} Proprietary <Prtry> [1..1] Text 447

AdditionalInformation <AddtlInf> [0..*] Text 447

Exceptions and Investigations - Maintenance 2020 - 2021 335 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.8.11 ResolutionRelatedInformation <RsltnRltdInf>

Presence: [0..1]
Definition: Reference of a return or a reversal transaction that is initiated to fix the case under
investigation as part of the resolution.
ResolutionRelatedInformation <RsltnRltdInf> contains the following ResolutionData3 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

EndToEndIdentification <EndToEndId> [0..1] Text 336

TransactionIdentification <TxId> [0..1] Text 336

UETR <UETR> [0..1] IdentifierSet 336

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 336

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 337

ClearingChannel <ClrChanl> [0..1] CodeSet 337

Compensation <Compstn> [0..1] ± 337

Charges <Chrgs> [0..*] ± 338

10.1.16.8.11.1 EndToEndIdentification <EndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.8.11.2 TransactionIdentification <TxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

10.1.16.8.11.3 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.8.11.4 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 336 December 2020

For evaluation by the Payments SEG Message Items Types

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.8.11.5 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 477

10.1.16.8.11.6 ClearingChannel <ClrChanl>

Presence: [0..1]
Definition: Specifies the clearing channel to be used to process the payment instruction.
Datatype: "ClearingChannel2Code" on page 462

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.

10.1.16.8.11.7 Compensation <Compstn>

Presence: [0..1]
Definition: Provides the details of the compensation made due to the modification or cancellation of a
previous payment.

Exceptions and Investigations - Maintenance 2020 - 2021 337 December 2020

For evaluation by the Payments SEG Message Items Types

Compensation <Compstn> contains the following elements (see "Compensation4" on page 152 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C11 152

DebtorAgent <DbtrAgt> [1..1] ± 153

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 153

CreditorAgent <CdtrAgt> [1..1] ± 154

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 154

Reason <Rsn> [1..1] 155

{Or Code <Cd> [1..1] CodeSet 155

Or} Proprietary <Prtry> [1..1] Text 155

10.1.16.8.11.8 Charges <Chrgs>

Presence: [0..*]
Definition: Provides information on the charges to be paid by the charge bearer(s) related to the
payment transaction.
Charges <Chrgs> contains the following elements (see "Charges9" on page 155 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C7 155

Agent <Agt> [1..1] ± 156

AgentAccount <AgtAcct> [0..1] ± C10, C9 156

10.1.16.8.12 OriginalInterbankSettlementAmount <OrgnlIntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent, as provided
in the original instruction.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Exceptions and Investigations - Maintenance 2020 - 2021 338 December 2020

For evaluation by the Payments SEG Message Items Types

Note: The decimal separator is a dot.

10.1.16.8.13 OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt>

Presence: [0..1]
Definition: Date, as provided in the original transaction, 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 477

10.1.16.8.14 Assigner <Assgnr>

Presence: [0..1]
Definition: Party who assigns the case.

Usage: This is also the agent that instructs the next party in the chain to carry out the (set of)
cancellation request(s).
Assigner <Assgnr> contains one of the following elements (see "Party40Choice" on page 209 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.15 Assignee <Assgne>

Presence: [0..1]
Definition: Party to which the case is assigned.

Usage: This is also the agent that is instructed by the previous party in the chain to carry out the (set of)
cancellation request(s).
Assignee <Assgne> contains one of the following elements (see "Party40Choice" on page 209 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.16 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 339 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 341

Amount <Amt> [0..1] ± 341

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 342

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 342

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 342

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 342

SettlementInformation <SttlmInf> [0..1] C11, 342

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 344

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 345

ClearingSystem <ClrSys> [0..1] 345

{Or Code <Cd> [1..1] CodeSet 346

Or} Proprietary <Prtry> [1..1] Text 346

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 346

InstructingReimbursementAgentAccount [0..1] ± C10, C9 346

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 347

InstructedReimbursementAgentAccount [0..1] ± C10, C9 347

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 348

ThirdReimbursementAgentAccount [0..1] ± C10, C9 348

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 349

PaymentMethod <PmtMtd> [0..1] CodeSet 350

MandateRelatedInformation <MndtRltdInf> [0..1] ± 350

RemittanceInformation <RmtInf> [0..1] ± 351

UltimateDebtor <UltmtDbtr> [0..1] ± 351

Debtor <Dbtr> [0..1] ± 351

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 351

Exceptions and Investigations - Maintenance 2020 - 2021 340 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 352

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 352

CreditorAgent <CdtrAgt> [0..1] ± 353

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 353

Creditor <Cdtr> [0..1] ± 354

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 354

UltimateCreditor <UltmtCdtr> [0..1] ± 355

Purpose <Purp> [0..1] ± 355

10.1.16.8.16.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.8.16.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 341 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.8.16.3 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 477

10.1.16.8.16.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.8.16.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.8.16.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.8.16.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 342 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 344

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 345

ClearingSystem <ClrSys> [0..1] 345

{Or Code <Cd> [1..1] CodeSet 346

Or} Proprietary <Prtry> [1..1] Text 346

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 346

InstructingReimbursementAgentAccount [0..1] ± C10, C9 346

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 347

InstructedReimbursementAgentAccount [0..1] ± C10, C9 347

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 348

ThirdReimbursementAgentAccount [0..1] ± C10, C9 348

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 343 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.8.16.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 344 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.8.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 345 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 346

Or} Proprietary <Prtry> [1..1] Text 346

10.1.16.8.16.7.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 465

10.1.16.8.16.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.8.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.8.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 346 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.8.16.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 347 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.8.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 348 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 349 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.8.16.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.8.16.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 350 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.8.16.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.8.16.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.16.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.16.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 351 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.8.16.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 352 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.8.16.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 353 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.16.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 354 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.8.16.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.8.16.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 355 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.9 PaymentTransaction137
Definition: Provides reference and status information on the original transactions, included in the
original instruction, to which the cancellation request message applies.

Exceptions and Investigations - Maintenance 2020 - 2021 356 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CancellationIdentification <CxlId> [0..1] Text 358

Case <Case> [0..1] ± 359

OriginalGroupInformation <OrgnlGrpInf> [0..1] ± 359

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 359

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 359

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 359

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 360

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 360

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 360

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 360

Assigner <Assgnr> [0..1] ± 360

Assignee <Assgne> [0..1] ± 361

CancellationReasonInformation <CxlRsnInf> [0..*] 361

Originator <Orgtr> [0..1] ± 361

Reason <Rsn> [0..1] ± 362

AdditionalInformation <AddtlInf> [0..*] Text 362

OriginalTransactionReference <OrgnlTxRef> [0..1] 362

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 364

Amount <Amt> [0..1] ± 364

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 365

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 365

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 365

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 365

SettlementInformation <SttlmInf> [0..1] C11, 365

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 367

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 368

ClearingSystem <ClrSys> [0..1] 368

{Or Code <Cd> [1..1] CodeSet 369

Exceptions and Investigations - Maintenance 2020 - 2021 357 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Or} Proprietary <Prtry> [1..1] Text 369

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 369

InstructingReimbursementAgentAccount [0..1] ± C10, C9 369

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 370

InstructedReimbursementAgentAccount [0..1] ± C10, C9 370

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 371

ThirdReimbursementAgentAccount [0..1] ± C10, C9 371

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 372

PaymentMethod <PmtMtd> [0..1] CodeSet 373

MandateRelatedInformation <MndtRltdInf> [0..1] ± 373

RemittanceInformation <RmtInf> [0..1] ± 374

UltimateDebtor <UltmtDbtr> [0..1] ± 374

Debtor <Dbtr> [0..1] ± 374

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 374

DebtorAgent <DbtrAgt> [0..1] ± 375

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 375

CreditorAgent <CdtrAgt> [0..1] ± 376

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 376

Creditor <Cdtr> [0..1] ± 377

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 377

UltimateCreditor <UltmtCdtr> [0..1] ± 378

Purpose <Purp> [0..1] ± 378

SupplementaryData <SplmtryData> [0..*] ± C22 379

10.1.16.9.1 CancellationIdentification <CxlId>

Presence: [0..1]
Definition: Unique and unambiguous identifier of a cancellation request, as assigned by the assigner.

Usage: The cancellation request identification can be used for reconciliation or to link tasks relating to
the cancellation request.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 358 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.9.2 Case <Case>

Presence: [0..1]
Definition: Set of elements to uniquely and unambiguously identify an exception or an investigation
workflow.
Case <Case> contains the following elements (see "Case5" on page 188 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 188

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.16.9.3 OriginalGroupInformation <OrgnlGrpInf>

Presence: [0..1]
Definition: Provides information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.16.9.4 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.9.5 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.9.6 OriginalTransactionIdentification <OrgnlTxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 359 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.9.7 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.9.8 OriginalClearingSystemReference <OrgnlClrSysRef>

Presence: [0..1]
Definition: Unique reference, as assigned by the original clearing system, to unambiguously identify the
original instruction.
Datatype: "Max35Text" on page 483

10.1.16.9.9 OriginalInterbankSettlementAmount <OrgnlIntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent, as provided
in the original instruction.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.9.10 OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt>

Presence: [0..1]
Definition: Date, as provided in the original transaction, 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 477

10.1.16.9.11 Assigner <Assgnr>

Presence: [0..1]
Definition: Party who assigns the case.

Usage: This is also the agent that instructs the next party in the chain to carry out the (set of)
cancellation request(s).

Exceptions and Investigations - Maintenance 2020 - 2021 360 December 2020

For evaluation by the Payments SEG Message Items Types

Assigner <Assgnr> contains the following elements (see

"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.12 Assignee <Assgne>

Presence: [0..1]
Definition: Party to which the case is assigned.

Usage: This is also the agent that is instructed by the previous party in the chain to carry out the (set of)
cancellation request(s).
Assignee <Assgne> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.13 CancellationReasonInformation <CxlRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the cancellation reason.
CancellationReasonInformation <CxlRsnInf> contains the following PaymentCancellationReason5
elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 361

Reason <Rsn> [0..1] ± 362

AdditionalInformation <AddtlInf> [0..*] Text 362

10.1.16.9.13.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation request.

Exceptions and Investigations - Maintenance 2020 - 2021 361 December 2020

For evaluation by the Payments SEG Message Items Types

Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.9.13.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the cancellation.
Reason <Rsn> contains one of the following elements (see "CancellationReason33Choice" on
page 445 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 445

Or} Proprietary <Prtry> [1..1] Text 446

10.1.16.9.13.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation request reason.
Datatype: "Max105Text" on page 481

10.1.16.9.14 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 362 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 364

Amount <Amt> [0..1] ± 364

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 365

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 365

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 365

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 365

SettlementInformation <SttlmInf> [0..1] C11, 365

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 367

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 368

ClearingSystem <ClrSys> [0..1] 368

{Or Code <Cd> [1..1] CodeSet 369

Or} Proprietary <Prtry> [1..1] Text 369

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 369

InstructingReimbursementAgentAccount [0..1] ± C10, C9 369

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 370

InstructedReimbursementAgentAccount [0..1] ± C10, C9 370

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 371

ThirdReimbursementAgentAccount [0..1] ± C10, C9 371

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 372

PaymentMethod <PmtMtd> [0..1] CodeSet 373

MandateRelatedInformation <MndtRltdInf> [0..1] ± 373

RemittanceInformation <RmtInf> [0..1] ± 374

UltimateDebtor <UltmtDbtr> [0..1] ± 374

Debtor <Dbtr> [0..1] ± 374

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 374

Exceptions and Investigations - Maintenance 2020 - 2021 363 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 375

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 375

CreditorAgent <CdtrAgt> [0..1] ± 376

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 376

Creditor <Cdtr> [0..1] ± 377

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 377

UltimateCreditor <UltmtCdtr> [0..1] ± 378

Purpose <Purp> [0..1] ± 378

10.1.16.9.14.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.9.14.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 364 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.9.14.3 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 477

10.1.16.9.14.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.9.14.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.9.14.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.9.14.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 365 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 367

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 368

ClearingSystem <ClrSys> [0..1] 368

{Or Code <Cd> [1..1] CodeSet 369

Or} Proprietary <Prtry> [1..1] Text 369

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 369

InstructingReimbursementAgentAccount [0..1] ± C10, C9 369

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 370

InstructedReimbursementAgentAccount [0..1] ± C10, C9 370

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 371

ThirdReimbursementAgentAccount [0..1] ± C10, C9 371

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 366 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.9.14.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 367 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.9.14.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 368 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 369

Or} Proprietary <Prtry> [1..1] Text 369

10.1.16.9.14.7.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 465

10.1.16.9.14.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.9.14.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.14.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 369 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.14.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 370 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.14.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 371 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 372 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.9.14.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.9.14.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 373 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.9.14.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.9.14.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.9.14.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.9.14.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 374 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.14.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 375 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.9.14.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 376 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.9.14.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 377 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.9.14.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.9.14.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 378 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.16.9.15 SupplementaryData <SplmtryData>

Presence: [0..*]
Definition: Additional information that cannot be captured in the structured elements and/or any other
specific block.
Impacted by: C22 "SupplementaryDataRule"
SupplementaryData <SplmtryData> contains the following elements (see "SupplementaryData1" on
page 194 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

PlaceAndName <PlcAndNm> [0..1] Text 194

Envelope <Envlp> [1..1] (External Schema) 194

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.

10.1.16.10 PaymentTransaction132
Definition: Provides further details on the reference and status on the original transactions, included in
the original instruction, to which the cancellation request message applies.

Exceptions and Investigations - Maintenance 2020 - 2021 379 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ModificationStatusIdentification <ModStsId> [0..1] Text 382

ResolvedCase <RslvdCase> [0..1] ± 382

OriginalGroupInformation <OrgnlGrpInf> [1..1] ± 382

OriginalPaymentInformationIdentification [0..1] Text 382

<OrgnlPmtInfId>

OriginalInstructionIdentification <OrgnlInstrId> [0..1] Text 383

OriginalEndToEndIdentification <OrgnlEndToEndId> [0..1] Text 383

OriginalTransactionIdentification <OrgnlTxId> [0..1] Text 383

OriginalClearingSystemReference <OrgnlClrSysRef> [0..1] Text 383

OriginalUETR <OrgnlUETR> [0..1] IdentifierSet 383

ModificationStatusReasonInformation <ModStsRsnInf> [0..*] 383

Originator <Orgtr> [0..1] ± 384

Reason <Rsn> [0..1] 384

{Or Code <Cd> [1..1] CodeSet 384

Or} Proprietary <Prtry> [1..1] Text 384

AdditionalInformation <AddtlInf> [0..*] Text 385

ResolutionRelatedInformation <RsltnRltdInf> [0..1] 385

EndToEndIdentification <EndToEndId> [0..1] Text 385

TransactionIdentification <TxId> [0..1] Text 385

UETR <UETR> [0..1] IdentifierSet 385

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 386

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 386

ClearingChannel <ClrChanl> [0..1] CodeSet 386

Compensation <Compstn> [0..1] ± 386

Charges <Chrgs> [0..*] ± 387

OriginalInterbankSettlementAmount [0..1] Amount C1, C7 387

<OrgnlIntrBkSttlmAmt>

OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt> [0..1] Date 388

Assigner <Assgnr> [0..1] ± 388

Assignee <Assgne> [0..1] ± 388

OriginalTransactionReference <OrgnlTxRef> [0..1] 388

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 390

Amount <Amt> [0..1] ± 390

Exceptions and Investigations - Maintenance 2020 - 2021 380 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 391

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 391

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 391

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 391

SettlementInformation <SttlmInf> [0..1] C11, 391

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 393

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 394

ClearingSystem <ClrSys> [0..1] 394

{Or Code <Cd> [1..1] CodeSet 395

Or} Proprietary <Prtry> [1..1] Text 395

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 395

InstructingReimbursementAgentAccount [0..1] ± C10, C9 395

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 396

InstructedReimbursementAgentAccount [0..1] ± C10, C9 396

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 397

ThirdReimbursementAgentAccount [0..1] ± C10, C9 397

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 398

PaymentMethod <PmtMtd> [0..1] CodeSet 399

MandateRelatedInformation <MndtRltdInf> [0..1] ± 399

RemittanceInformation <RmtInf> [0..1] ± 400

UltimateDebtor <UltmtDbtr> [0..1] ± 400

Debtor <Dbtr> [0..1] ± 400

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 400

DebtorAgent <DbtrAgt> [0..1] ± 401

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 401

CreditorAgent <CdtrAgt> [0..1] ± 402

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 402

Exceptions and Investigations - Maintenance 2020 - 2021 381 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Creditor <Cdtr> [0..1] ± 403

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 403

UltimateCreditor <UltmtCdtr> [0..1] ± 404

Purpose <Purp> [0..1] ± 404

10.1.16.10.1 ModificationStatusIdentification <ModStsId>

Presence: [0..1]
Definition: Unique and unambiguous identifier of a modification request status, as assigned by the
assigner.

Usage: The modification status identification can be used for reconciliation or to link tasks relating to the
modification request.
Datatype: "Max35Text" on page 483

10.1.16.10.2 ResolvedCase <RslvdCase>

Presence: [0..1]
Definition: Identifies the resolved case.
ResolvedCase <RslvdCase> contains the following elements (see "Case5" on page 188 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 188

Creator <Cretr> [1..1] ± 188

ReopenCaseIndication <ReopCaseIndctn> [0..1] Indicator 189

10.1.16.10.3 OriginalGroupInformation <OrgnlGrpInf>

Presence: [1..1]
Definition: Provides information on the original message.
OriginalGroupInformation <OrgnlGrpInf> contains the following elements (see
"OriginalGroupInformation29" on page 195 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

OriginalMessageIdentification <OrgnlMsgId> [1..1] Text 195

OriginalMessageNameIdentification <OrgnlMsgNmId> [1..1] Text 195

OriginalCreationDateTime <OrgnlCreDtTm> [0..1] DateTime 195

10.1.16.10.4 OriginalPaymentInformationIdentification <OrgnlPmtInfId>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 382 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Unique identification, as assigned by the original sending party, to unambiguously identify the
original payment information group.
Datatype: "Max35Text" on page 483

10.1.16.10.5 OriginalInstructionIdentification <OrgnlInstrId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original instructing party for the original instructed
party, to unambiguously identify the original instruction.
Datatype: "Max35Text" on page 483

10.1.16.10.6 OriginalEndToEndIdentification <OrgnlEndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.10.7 OriginalTransactionIdentification <OrgnlTxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

10.1.16.10.8 OriginalClearingSystemReference <OrgnlClrSysRef>

Presence: [0..1]
Definition: Unique reference, as assigned by the original clearing system, to unambiguously identify the
original instruction.
Datatype: "Max35Text" on page 483

10.1.16.10.9 OriginalUETR <OrgnlUETR>

Presence: [0..1]
Definition: Universally unique identifier to provide the original end-to-end reference of a payment
transaction.
Datatype: "UUIDv4Identifier" on page 479

10.1.16.10.10 ModificationStatusReasonInformation <ModStsRsnInf>

Presence: [0..*]
Definition: Provides detailed information on the modification status reason.

Exceptions and Investigations - Maintenance 2020 - 2021 383 December 2020

For evaluation by the Payments SEG Message Items Types

ModificationStatusReasonInformation <ModStsRsnInf> contains the following

ModificationStatusReason2 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 384

Reason <Rsn> [0..1] 384

{Or Code <Cd> [1..1] CodeSet 384

Or} Proprietary <Prtry> [1..1] Text 384

AdditionalInformation <AddtlInf> [0..*] Text 385

10.1.16.10.10.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation status.
Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.10.10.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the status report.
Reason <Rsn> contains one of the following ModificationStatusReason1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 384

Or} Proprietary <Prtry> [1..1] Text 384

10.1.16.10.10.2.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the modification status, in a coded form.
Datatype: "ExternalPaymentModificationRejection1Code" on page 469

10.1.16.10.10.2.2 Proprietary <Prtry>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 384 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Reason for the status, in a proprietary form.

Datatype: "Max35Text" on page 483

10.1.16.10.10.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation status reason.
Datatype: "Max105Text" on page 481

10.1.16.10.11 ResolutionRelatedInformation <RsltnRltdInf>

Presence: [0..1]
Definition: Reference of a return or a reversal transaction that is initiated to fix the case under
investigation as part of the resolution.
ResolutionRelatedInformation <RsltnRltdInf> contains the following ResolutionData3 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

EndToEndIdentification <EndToEndId> [0..1] Text 385

TransactionIdentification <TxId> [0..1] Text 385

UETR <UETR> [0..1] IdentifierSet 385

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 386

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 386

ClearingChannel <ClrChanl> [0..1] CodeSet 386

Compensation <Compstn> [0..1] ± 386

Charges <Chrgs> [0..*] ± 387

10.1.16.10.11.1 EndToEndIdentification <EndToEndId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original initiating party, to unambiguously identify
the original transaction.
Datatype: "Max35Text" on page 483

10.1.16.10.11.2 TransactionIdentification <TxId>

Presence: [0..1]
Definition: Unique identification, as assigned by the original first instructing agent, to unambiguously
identify the transaction.
Datatype: "Max35Text" on page 483

10.1.16.10.11.3 UETR <UETR>

Presence: [0..1]
Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction.
Datatype: "UUIDv4Identifier" on page 479

Exceptions and Investigations - Maintenance 2020 - 2021 385 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.10.11.4 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.10.11.5 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 477

10.1.16.10.11.6 ClearingChannel <ClrChanl>

Presence: [0..1]
Definition: Specifies the clearing channel to be used to process the payment instruction.
Datatype: "ClearingChannel2Code" on page 462

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.

10.1.16.10.11.7 Compensation <Compstn>

Presence: [0..1]
Definition: Provides the details of the compensation made due to the modification or cancellation of a
previous payment.

Exceptions and Investigations - Maintenance 2020 - 2021 386 December 2020

For evaluation by the Payments SEG Message Items Types

Compensation <Compstn> contains the following elements (see "Compensation4" on page 152 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C11 152

DebtorAgent <DbtrAgt> [1..1] ± 153

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 153

CreditorAgent <CdtrAgt> [1..1] ± 154

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 154

Reason <Rsn> [1..1] 155

{Or Code <Cd> [1..1] CodeSet 155

Or} Proprietary <Prtry> [1..1] Text 155

10.1.16.10.11.8 Charges <Chrgs>

Presence: [0..*]
Definition: Provides information on the charges to be paid by the charge bearer(s) related to the
payment transaction.
Charges <Chrgs> contains the following elements (see "Charges9" on page 155 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C7 155

Agent <Agt> [1..1] ± 156

AgentAccount <AgtAcct> [0..1] ± C10, C9 156

10.1.16.10.12 OriginalInterbankSettlementAmount <OrgnlIntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent, as provided
in the original instruction.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Exceptions and Investigations - Maintenance 2020 - 2021 387 December 2020

For evaluation by the Payments SEG Message Items Types

Note: The decimal separator is a dot.

10.1.16.10.13 OriginalInterbankSettlementDate <OrgnlIntrBkSttlmDt>

Presence: [0..1]
Definition: Date, as provided in the original transaction, 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 477

10.1.16.10.14 Assigner <Assgnr>

Presence: [0..1]
Definition: Party who assigns the case.

Usage: This is also the agent that instructs the next party in the chain to carry out the (set of)
cancellation request(s).
Assigner <Assgnr> contains one of the following elements (see "Party40Choice" on page 209 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.15 Assignee <Assgne>

Presence: [0..1]
Definition: Party to which the case is assigned.

Usage: This is also the agent that is instructed by the previous party in the chain to carry out the (set of)
cancellation request(s).
Assignee <Assgne> contains one of the following elements (see "Party40Choice" on page 209 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.16 OriginalTransactionReference <OrgnlTxRef>

Presence: [0..1]
Definition: Key elements used to identify the original transaction that is being referred to.

Exceptions and Investigations - Maintenance 2020 - 2021 388 December 2020

For evaluation by the Payments SEG Message Items Types

OriginalTransactionReference <OrgnlTxRef> contains the following

OriginalTransactionReference35 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InterbankSettlementAmount <IntrBkSttlmAmt> [0..1] Amount C1, C7 390

Amount <Amt> [0..1] ± 390

InterbankSettlementDate <IntrBkSttlmDt> [0..1] Date 391

RequestedCollectionDate <ReqdColltnDt> [0..1] Date 391

RequestedExecutionDate <ReqdExctnDt> [0..1] ± 391

CreditorSchemeIdentification <CdtrSchmeId> [0..1] ± 391

SettlementInformation <SttlmInf> [0..1] C11, 391

C13,
C18,
C19,
C20,
C21,
C23,
C24

SettlementMethod <SttlmMtd> [1..1] CodeSet 393

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 394

ClearingSystem <ClrSys> [0..1] 394

{Or Code <Cd> [1..1] CodeSet 395

Or} Proprietary <Prtry> [1..1] Text 395

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 395

InstructingReimbursementAgentAccount [0..1] ± C10, C9 395

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 396

InstructedReimbursementAgentAccount [0..1] ± C10, C9 396

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 397

ThirdReimbursementAgentAccount [0..1] ± C10, C9 397

<ThrdRmbrsmntAgtAcct>

PaymentTypeInformation <PmtTpInf> [0..1] ± 398

PaymentMethod <PmtMtd> [0..1] CodeSet 399

MandateRelatedInformation <MndtRltdInf> [0..1] ± 399

RemittanceInformation <RmtInf> [0..1] ± 400

UltimateDebtor <UltmtDbtr> [0..1] ± 400

Debtor <Dbtr> [0..1] ± 400

DebtorAccount <DbtrAcct> [0..1] ± C10, C9 400

Exceptions and Investigations - Maintenance 2020 - 2021 389 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DebtorAgent <DbtrAgt> [0..1] ± 401

DebtorAgentAccount <DbtrAgtAcct> [0..1] ± C10, C9 401

CreditorAgent <CdtrAgt> [0..1] ± 402

CreditorAgentAccount <CdtrAgtAcct> [0..1] ± C10, C9 402

Creditor <Cdtr> [0..1] ± 403

CreditorAccount <CdtrAcct> [0..1] ± C10, C9 403

UltimateCreditor <UltmtCdtr> [0..1] ± 404

Purpose <Purp> [0..1] ± 404

10.1.16.10.16.1 InterbankSettlementAmount <IntrBkSttlmAmt>

Presence: [0..1]
Definition: Amount of money moved between the instructing agent and the instructed agent.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.16.10.16.2 Amount <Amt>

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.
Amount <Amt> contains one of the following elements (see "AmountType4Choice" on page 149 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or InstructedAmount <InstdAmt> [1..1] Amount C1, C7 149

Or} EquivalentAmount <EqvtAmt> [1..1] 150

Amount <Amt> [1..1] Amount C1, C7 150

CurrencyOfTransfer <CcyOfTrf> [1..1] CodeSet C1 150

Exceptions and Investigations - Maintenance 2020 - 2021 390 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.16.10.16.3 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 477

10.1.16.10.16.4 RequestedCollectionDate <ReqdColltnDt>

Presence: [0..1]
Definition: Date and time at which the creditor requests that the amount of money is to be collected from
the debtor.
Datatype: "ISODate" on page 477

10.1.16.10.16.5 RequestedExecutionDate <ReqdExctnDt>

Presence: [0..1]
Definition: Date at which the initiating party requests the clearing agent to process the payment.

Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date
when the cheque must be generated by the bank.
RequestedExecutionDate <ReqdExctnDt> contains one of the following elements (see
"DateAndDateTime2Choice" on page 161 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Date <Dt> [1..1] Date 161

Or} DateTime <DtTm> [1..1] DateTime 161

10.1.16.10.16.6 CreditorSchemeIdentification <CdtrSchmeId>

Presence: [0..1]
Definition: Credit party that signs the mandate.
CreditorSchemeIdentification <CdtrSchmeId> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.16.10.16.7 SettlementInformation <SttlmInf>

Presence: [0..1]
Definition: Specifies the details on how the settlement of the original transaction(s) between the
instructing agent and the instructed agent was completed.

Exceptions and Investigations - Maintenance 2020 - 2021 391 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C11 "InstructedReimbursementAgentAccountRule", C13

"InstructingReimbursementAgentAccountRule", C18 "SettlementMethodAgentRule", C19
"SettlementMethodClearingRule", C20 "SettlementMethodCoverAgentRule", C21
"SettlementMethodCoverRule", C23 "ThirdReimbursementAgentAccountRule", C24
"ThirdReimbursementAgentRule"
SettlementInformation <SttlmInf> contains the following SettlementInstruction11 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

SettlementMethod <SttlmMtd> [1..1] CodeSet 393

SettlementAccount <SttlmAcct> [0..1] ± C10, C9 394

ClearingSystem <ClrSys> [0..1] 394

{Or Code <Cd> [1..1] CodeSet 395

Or} Proprietary <Prtry> [1..1] Text 395

InstructingReimbursementAgent <InstgRmbrsmntAgt> [0..1] ± 395

InstructingReimbursementAgentAccount [0..1] ± C10, C9 395

<InstgRmbrsmntAgtAcct>

InstructedReimbursementAgent <InstdRmbrsmntAgt> [0..1] ± 396

InstructedReimbursementAgentAccount [0..1] ± C10, C9 396

<InstdRmbrsmntAgtAcct>

ThirdReimbursementAgent <ThrdRmbrsmntAgt> [0..1] ± 397

ThirdReimbursementAgentAccount [0..1] ± C10, C9 397

<ThrdRmbrsmntAgtAcct>

Constraints

• InstructedReimbursementAgentAccountRule
If InstructedReimbursementAgentAccount is present, then InstructedReimbursementAgent must be
present.
On Condition
/InstructedReimbursementAgent is absent
Following Must be True
/InstructedReimbursementAgentAccount Must be absent

• InstructingReimbursementAgentAccountRule
If InstructingReimbursementAgentAccount is present, then InstructingReimbursementAgent must be
present.
On Condition
/InstructingReimbursementAgent is absent
Following Must be True
/InstructingReimbursementAgentAccount Must be absent

• SettlementMethodAgentRule
If SettlementMethod is equal to INDA or INGA, then ReimbursementAgent(s) and ClearingSystem
are not allowed.
On Condition
/SettlementMethod is equal to value 'InstructingAgent'
Or /SettlementMethod is equal to value 'InstructedAgent'

Exceptions and Investigations - Maintenance 2020 - 2021 392 December 2020

For evaluation by the Payments SEG Message Items Types

Following Must be True

/ClearingSystem Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodClearingRule
If SettlementMethod is equal to CLRG, then SettlementAccount and ReimbursementAgent(s) are not
allowed.
On Condition
/SettlementMethod is equal to value 'ClearingSystem'
Following Must be True
/SettlementAccount Must be absent
And /InstructingReimbursementAgent Must be absent
And /InstructedReimbursementAgent Must be absent
And /ThirdReimbursementAgent Must be absent

• SettlementMethodCoverAgentRule
If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or
InstructingReimbursementAgent must be present.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/InstructingReimbursementAgent Must be present
Or /InstructedReimbursementAgent Must be present

• SettlementMethodCoverRule
If SettlementMethod is equal to COVE, then SettlementAccount and ClearingSystem are not allowed.
On Condition
/SettlementMethod is equal to value 'CoverMethod'
Following Must be True
/SettlementAccount Must be absent
And /ClearingSystem Must be absent

• ThirdReimbursementAgentAccountRule
If ThirdReimbursementAgentAccount is present, then ThirdReimbursementAgent must be present.
On Condition
/ThirdReimbursementAgent is absent
Following Must be True
/ThirdReimbursementAgentAccount Must be absent

• ThirdReimbursementAgentRule
If ThirdReimbursementAgent is present, then InstructingReimbursementAgent and
InstructedReimbursementAgent must both be present.
On Condition
/ThirdReimbursementAgent is present
Following Must be True
/InstructingReimbursementAgent Must be present
And /InstructedReimbursementAgent Must be present

10.1.16.10.16.7.1 SettlementMethod <SttlmMtd>

Presence: [1..1]
Definition: Method used to settle the (batch of) payment instructions.
Datatype: "SettlementMethod1Code" on page 475

Exceptions and Investigations - Maintenance 2020 - 2021 393 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.1.16.10.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"
SettlementAccount <SttlmAcct> contains the following elements (see "CashAccount40" on page 144
for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.7.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.

Exceptions and Investigations - Maintenance 2020 - 2021 394 December 2020

For evaluation by the Payments SEG Message Items Types

ClearingSystem <ClrSys> contains one of the following ClearingSystemIdentification3Choice

elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 395

Or} Proprietary <Prtry> [1..1] Text 395

10.1.16.10.16.7.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 465

10.1.16.10.16.7.3.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Clearing system identification in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.16.10.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.10.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 395 December 2020

For evaluation by the Payments SEG Message Items Types

InstructingReimbursementAgentAccount <InstgRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.10.16.7.7 InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct>

Presence: [0..1]
Definition: Unambiguous identification of the account of the instructed reimbursement agent account at
its servicing agent in the payment chain.
Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 396 December 2020

For evaluation by the Payments SEG Message Items Types

InstructedReimbursementAgentAccount <InstdRmbrsmntAgtAcct> contains the following

elements (see "CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.7.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 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.10.16.7.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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 397 December 2020

For evaluation by the Payments SEG Message Items Types

ThirdReimbursementAgentAccount <ThrdRmbrsmntAgtAcct> contains the following elements (see

"CashAccount40" on page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.8 PaymentTypeInformation <PmtTpInf>

Presence: [0..1]
Definition: Set of elements used to further specify the type of transaction.

Exceptions and Investigations - Maintenance 2020 - 2021 398 December 2020

For evaluation by the Payments SEG Message Items Types

PaymentTypeInformation <PmtTpInf> contains the following elements (see

"PaymentTypeInformation27" on page 405 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.16.10.16.9 PaymentMethod <PmtMtd>

Presence: [0..1]
Definition: Specifies the means of payment that will be used to move the amount of money.
Datatype: "PaymentMethod4Code" on page 473

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.1.16.10.16.10 MandateRelatedInformation <MndtRltdInf>

Presence: [0..1]
Definition: Provides further details of the mandate signed between the creditor and the debtor.

Exceptions and Investigations - Maintenance 2020 - 2021 399 December 2020

For evaluation by the Payments SEG Message Items Types

MandateRelatedInformation <MndtRltdInf> contains one of the following elements (see

"MandateRelatedData2Choice" on page 168 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or DirectDebitMandate <DrctDbtMndt> [0..1] ± C2, C3 168

Or} CreditTransferMandate <CdtTrfMndt> [0..1] ± 169

10.1.16.10.16.11 RemittanceInformation <RmtInf>

Presence: [0..1]
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.
RemittanceInformation <RmtInf> contains the following elements (see "RemittanceInformation21" on
page 437 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.16.10.16.12 UltimateDebtor <UltmtDbtr>

Presence: [0..1]
Definition: Ultimate party that owes an amount of money to the (ultimate) creditor.
UltimateDebtor <UltmtDbtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.16.13 Debtor <Dbtr>

Presence: [0..1]
Definition: Party that owes an amount of money to the (ultimate) creditor.
Debtor <Dbtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.16.14 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.

Exceptions and Investigations - Maintenance 2020 - 2021 400 December 2020

For evaluation by the Payments SEG Message Items Types

Impacted by: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

DebtorAccount <DbtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.15 DebtorAgent <DbtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the debtor.
DebtorAgent <DbtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.10.16.16 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 401 December 2020

For evaluation by the Payments SEG Message Items Types

DebtorAgentAccount <DbtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.17 CreditorAgent <CdtrAgt>

Presence: [0..1]
Definition: Financial institution servicing an account for the creditor.
CreditorAgent <CdtrAgt> contains the following elements (see
"BranchAndFinancialInstitutionIdentification6" on page 181 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FinancialInstitutionIdentification <FinInstnId> [1..1] ± 181

BranchIdentification <BrnchId> [0..1] ± 182

10.1.16.10.16.18 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 402 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAgentAccount <CdtrAgtAcct> contains the following elements (see "CashAccount40" on

page 144 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.19 Creditor <Cdtr>

Presence: [0..1]
Definition: Party to which an amount of money is due.
Creditor <Cdtr> contains one of the following elements (see "Party40Choice" on page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.16.20 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: C10 "IdentificationOrProxyPresenceRule", C9 "IdentificationAndProxyGuideline"

Exceptions and Investigations - Maintenance 2020 - 2021 403 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorAccount <CdtrAcct> contains the following elements (see "CashAccount40" on page 144 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [0..1] ± 145

Type <Tp> [0..1] ± 145

Currency <Ccy> [0..1] CodeSet C1 145

Name <Nm> [0..1] Text 146

Proxy <Prxy> [0..1] ± 146

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.
Following Must be True
/Identification Must be present
And /Proxy Must be present

10.1.16.10.16.21 UltimateCreditor <UltmtCdtr>

Presence: [0..1]
Definition: Ultimate party to which an amount of money is due.
UltimateCreditor <UltmtCdtr> contains one of the following elements (see "Party40Choice" on
page 209 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Party <Pty> [1..1] ± 210

Or} Agent <Agt> [1..1] ± 210

10.1.16.10.16.22 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.

Exceptions and Investigations - Maintenance 2020 - 2021 404 December 2020

For evaluation by the Payments SEG Message Items Types

Purpose <Purp> contains one of the following elements (see "Purpose2Choice" on page 194 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 195

Or} Proprietary <Prtry> [1..1] Text 195

10.1.17 Payment Type

10.1.17.1 PaymentTypeInformation27
Definition: Provides further details of the type of payment.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

InstructionPriority <InstrPrty> [0..1] CodeSet 405

ClearingChannel <ClrChanl> [0..1] CodeSet 405

ServiceLevel <SvcLvl> [0..*] 406

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

LocalInstrument <LclInstrm> [0..1] 406

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

SequenceType <SeqTp> [0..1] CodeSet 407

CategoryPurpose <CtgyPurp> [0..1] 407

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.17.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 474

CodeName Name Definition

HIGH High Priority level is high.

NORM Normal Priority level is normal.

10.1.17.1.2 ClearingChannel <ClrChanl>

Presence: [0..1]
Definition: Specifies the clearing channel to be used to process the payment instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 405 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "ClearingChannel2Code" on page 462

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.

10.1.17.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 406

Or} Proprietary <Prtry> [1..1] Text 406

10.1.17.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 470

10.1.17.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 483

10.1.17.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.
LocalInstrument <LclInstrm> contains one of the following LocalInstrument2Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 407

Exceptions and Investigations - Maintenance 2020 - 2021 406 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.17.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 468

10.1.17.1.4.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Specifies the local instrument, as a proprietary code.
Datatype: "Max35Text" on page 483

10.1.17.1.5 SequenceType <SeqTp>

Presence: [0..1]
Definition: Identifies the direct debit sequence, such as first, recurrent, final or one-off.
Datatype: "SequenceType3Code" on page 474

CodeName Name Definition

FRST First First collection of a series of direct debit

instructions.

RCUR Recurring Direct debit instruction where the

debtor's authorisation is used for regular
direct debit transactions initiated by the
creditor.

FNAL Final Final collection of a series of direct debit

instructions.

OOFF OneOff Direct debit instruction where the

debtor's authorisation is used to initiate
one single direct debit transaction.

RPRE Represented Collection used to re-present previously

reversed or returned direct debit
transactions.

10.1.17.1.6 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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 407

Or} Proprietary <Prtry> [1..1] Text 408

10.1.17.1.6.1 Code <Cd>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 407 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Category purpose, as published in an external category purpose code list.

Datatype: "ExternalCategoryPurpose1Code" on page 465

10.1.17.1.6.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Category purpose, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.18 Person Identification

10.1.18.1 PersonIdentification13
Definition: Unique and unambiguous way to identify a person.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] 408

BirthDate <BirthDt> [1..1] Date 409

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 409

CityOfBirth <CityOfBirth> [1..1] Text 409

CountryOfBirth <CtryOfBirth> [1..1] CodeSet C6 409

Other <Othr> [0..*] 409

Identification <Id> [1..1] Text 409

SchemeName <SchmeNm> [0..1] 410

{Or Code <Cd> [1..1] CodeSet 410

Or} Proprietary <Prtry> [1..1] Text 410

Issuer <Issr> [0..1] Text 410

10.1.18.1.1 DateAndPlaceOfBirth <DtAndPlcOfBirth>

Presence: [0..1]
Definition: Date and place of birth of a person.
DateAndPlaceOfBirth <DtAndPlcOfBirth> contains the following DateAndPlaceOfBirth1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

BirthDate <BirthDt> [1..1] Date 409

ProvinceOfBirth <PrvcOfBirth> [0..1] Text 409

CityOfBirth <CityOfBirth> [1..1] Text 409

CountryOfBirth <CtryOfBirth> [1..1] CodeSet C6 409

Exceptions and Investigations - Maintenance 2020 - 2021 408 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.18.1.1.1 BirthDate <BirthDt>

Presence: [1..1]
Definition: Date on which a person is born.
Datatype: "ISODate" on page 477

10.1.18.1.1.2 ProvinceOfBirth <PrvcOfBirth>

Presence: [0..1]
Definition: Province where a person was born.
Datatype: "Max35Text" on page 483

10.1.18.1.1.3 CityOfBirth <CityOfBirth>

Presence: [1..1]
Definition: City where a person was born.
Datatype: "Max35Text" on page 483

10.1.18.1.1.4 CountryOfBirth <CtryOfBirth>

Presence: [1..1]
Definition: Country where a person was born.
Impacted by: C6 "Country"
Datatype: "CountryCode" on page 462

Constraints

• Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166,
Alpha-2 code).

10.1.18.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 409

SchemeName <SchmeNm> [0..1] 410

{Or Code <Cd> [1..1] CodeSet 410

Or} Proprietary <Prtry> [1..1] Text 410

Issuer <Issr> [0..1] Text 410

10.1.18.1.2.1 Identification <Id>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 409 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Unique and unambiguous identification of a person.

Datatype: "Max35Text" on page 483

10.1.18.1.2.2 SchemeName <SchmeNm>

Presence: [0..1]
Definition: Name of the identification scheme.
SchemeName <SchmeNm> contains one of the following
PersonIdentificationSchemeName1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 410

Or} Proprietary <Prtry> [1..1] Text 410

10.1.18.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 469

10.1.18.1.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Name of the identification scheme, in a free text form.
Datatype: "Max35Text" on page 483

10.1.18.1.2.3 Issuer <Issr>

Presence: [0..1]
Definition: Entity that assigns the identification.
Datatype: "Max35Text" on page 483

10.1.18.2 Contact4
Definition: Specifies the details of the contact person.

Exceptions and Investigations - Maintenance 2020 - 2021 410 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

NamePrefix <NmPrfx> [0..1] CodeSet 411

Name <Nm> [0..1] Text 411

PhoneNumber <PhneNb> [0..1] Text 411

MobileNumber <MobNb> [0..1] Text 412

FaxNumber <FaxNb> [0..1] Text 412

EmailAddress <EmailAdr> [0..1] Text 412

EmailPurpose <EmailPurp> [0..1] Text 412

JobTitle <JobTitl> [0..1] Text 412

Responsibility <Rspnsblty> [0..1] Text 412

Department <Dept> [0..1] Text 412

Other <Othr> [0..*] 412

ChannelType <ChanlTp> [1..1] Text 413

Identification <Id> [0..1] Text 413

PreferredMethod <PrefrdMtd> [0..1] CodeSet 413

10.1.18.2.1 NamePrefix <NmPrfx>

Presence: [0..1]
Definition: Specifies the terms used to formally address a person.
Datatype: "NamePrefix2Code" on page 473

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).

10.1.18.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 482

10.1.18.2.3 PhoneNumber <PhneNb>

Presence: [0..1]
Definition: Collection of information that identifies a phone number, as defined by telecom services.

Exceptions and Investigations - Maintenance 2020 - 2021 411 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "PhoneNumber" on page 483

10.1.18.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 483

10.1.18.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 483

10.1.18.2.6 EmailAddress <EmailAdr>

Presence: [0..1]
Definition: Address for electronic mail (e-mail).
Datatype: "Max2048Text" on page 482

10.1.18.2.7 EmailPurpose <EmailPurp>

Presence: [0..1]
Definition: Purpose for which an email address may be used.
Datatype: "Max35Text" on page 483

10.1.18.2.8 JobTitle <JobTitl>

Presence: [0..1]
Definition: Title of the function.
Datatype: "Max35Text" on page 483

10.1.18.2.9 Responsibility <Rspnsblty>

Presence: [0..1]
Definition: Role of a person in an organisation.
Datatype: "Max35Text" on page 483

10.1.18.2.10 Department <Dept>

Presence: [0..1]
Definition: Identification of a division of a large organisation or building.
Datatype: "Max70Text" on page 483

10.1.18.2.11 Other <Othr>

Presence: [0..*]
Definition: Contact details in another form.

Exceptions and Investigations - Maintenance 2020 - 2021 412 December 2020

For evaluation by the Payments SEG Message Items Types

Other <Othr> contains the following OtherContact1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ChannelType <ChanlTp> [1..1] Text 413

Identification <Id> [0..1] Text 413

10.1.18.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 483

10.1.18.2.11.2 Identification <Id>

Presence: [0..1]
Definition: Communication value such as phone number or email address.
Datatype: "Max128Text" on page 481

10.1.18.2.12 PreferredMethod <PrefrdMtd>

Presence: [0..1]
Definition: Preferred method used to reach the contact.
Datatype: "PreferredContactMethod1Code" on page 473

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.

10.1.19 Postal Address

10.1.19.1 PostalAddress24
Definition: Information that locates and identifies a specific address, as defined by postal services.

Exceptions and Investigations - Maintenance 2020 - 2021 413 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 414

{Or Code <Cd> [1..1] CodeSet 414

Or} Proprietary <Prtry> [1..1] ± 415

Department <Dept> [0..1] Text 415

SubDepartment <SubDept> [0..1] Text 415

StreetName <StrtNm> [0..1] Text 415

BuildingNumber <BldgNb> [0..1] Text 415

BuildingName <BldgNm> [0..1] Text 416

Floor <Flr> [0..1] Text 416

PostBox <PstBx> [0..1] Text 416

Room <Room> [0..1] Text 416

PostCode <PstCd> [0..1] Text 416

TownName <TwnNm> [0..1] Text 416

TownLocationName <TwnLctnNm> [0..1] Text 416

DistrictName <DstrctNm> [0..1] Text 416

CountrySubDivision <CtrySubDvsn> [0..1] Text 417

Country <Ctry> [0..1] CodeSet C6 417

AddressLine <AdrLine> [0..7] Text 417

10.1.19.1.1 AddressType <AdrTp>

Presence: [0..1]
Definition: Identifies the nature of the postal address.
AddressType <AdrTp> contains one of the following AddressType3Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 414

Or} Proprietary <Prtry> [1..1] ± 415

10.1.19.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Type of address expressed as a code.
Datatype: "AddressType2Code" on page 461

CodeName Name Definition

ADDR Postal Address is the complete postal address.

Exceptions and Investigations - Maintenance 2020 - 2021 414 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

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.

10.1.19.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 184 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..1] Text 184

Issuer <Issr> [1..1] Text 184

SchemeName <SchmeNm> [0..1] Text 184

10.1.19.1.2 Department <Dept>

Presence: [0..1]
Definition: Identification of a division of a large organisation or building.
Datatype: "Max70Text" on page 483

10.1.19.1.3 SubDepartment <SubDept>

Presence: [0..1]
Definition: Identification of a sub-division of a large organisation or building.
Datatype: "Max70Text" on page 483

10.1.19.1.4 StreetName <StrtNm>

Presence: [0..1]
Definition: Name of a street or thoroughfare.
Datatype: "Max70Text" on page 483

10.1.19.1.5 BuildingNumber <BldgNb>

Presence: [0..1]
Definition: Number that identifies the position of a building on a street.
Datatype: "Max16Text" on page 482

Exceptions and Investigations - Maintenance 2020 - 2021 415 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.19.1.6 BuildingName <BldgNm>

Presence: [0..1]
Definition: Name of the building or house.
Datatype: "Max35Text" on page 483

10.1.19.1.7 Floor <Flr>

Presence: [0..1]
Definition: Floor or storey within a building.
Datatype: "Max70Text" on page 483

10.1.19.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 482

10.1.19.1.9 Room <Room>

Presence: [0..1]
Definition: Building room number.
Datatype: "Max70Text" on page 483

10.1.19.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 482

10.1.19.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 483

10.1.19.1.12 TownLocationName <TwnLctnNm>

Presence: [0..1]
Definition: Specific location name within the town.
Datatype: "Max35Text" on page 483

10.1.19.1.13 DistrictName <DstrctNm>

Presence: [0..1]
Definition: Identifies a subdivision within a country sub-division.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 416 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.19.1.14 CountrySubDivision <CtrySubDvsn>

Presence: [0..1]
Definition: Identifies a subdivision of a country such as state, region, county.
Datatype: "Max35Text" on page 483

10.1.19.1.15 Country <Ctry>

Presence: [0..1]
Definition: Nation with its own government.
Impacted by: C6 "Country"
Datatype: "CountryCode" on page 462

Constraints

• Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166,
Alpha-2 code).

10.1.19.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 483

10.1.20 Remittance
10.1.20.1 RemittanceLocation7
Definition: Provides information on the remittance advice.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

RemittanceIdentification <RmtId> [0..1] Text 417

RemittanceLocationDetails <RmtLctnDtls> [0..*] ± 417

10.1.20.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 483

10.1.20.1.2 RemittanceLocationDetails <RmtLctnDtls>

Presence: [0..*]
Definition: Set of elements used to provide information on the location and/or delivery of the remittance
information.

Exceptions and Investigations - Maintenance 2020 - 2021 417 December 2020

For evaluation by the Payments SEG Message Items Types

RemittanceLocationDetails <RmtLctnDtls> contains the following elements (see

"RemittanceLocationData1" on page 443 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Method <Mtd> [1..1] CodeSet 444

ElectronicAddress <ElctrncAdr> [0..1] Text 444

PostalAddress <PstlAdr> [0..1] 444

Name <Nm> [1..1] Text 444

Address <Adr> [1..1] ± 445

10.1.20.2 StructuredRemittanceInformation17
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.

Exceptions and Investigations - Maintenance 2020 - 2021 418 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ReferredDocumentInformation <RfrdDocInf> [0..*] 420

Type <Tp> [0..1] 422

CodeOrProprietary <CdOrPrtry> [1..1] 422

{Or Code <Cd> [1..1] CodeSet 422

Or} Proprietary <Prtry> [1..1] Text 423

Issuer <Issr> [0..1] Text 423

Number <Nb> [0..1] Text 423

RelatedDate <RltdDt> [0..1] Date 424

LineDetails <LineDtls> [0..*] 424

Identification <Id> [1..*] 425

Type <Tp> [0..1] 426

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

Number <Nb> [0..1] Text 427

RelatedDate <RltdDt> [0..1] Date 427

Description <Desc> [0..1] Text 427

Amount <Amt> [0..1] 427

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 428

DiscountAppliedAmount <DscntApldAmt> [0..*] 429

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 430

TaxAmount <TaxAmt> [0..*] 430

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Amount <Amt> [1..1] Amount C1, C7 431

Exceptions and Investigations - Maintenance 2020 - 2021 419 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AdjustmentAmountAndReason [0..*] 431

<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 433

ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 433

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 434

Invoicer <Invcr> [0..1] ± 435

Invoicee <Invcee> [0..1] ± 435

TaxRemittance <TaxRmt> [0..1] ± 436

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 436

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 437

10.1.20.2.1 ReferredDocumentInformation <RfrdDocInf>

Presence: [0..*]
Definition: Provides the identification and the content of the referred document.

Exceptions and Investigations - Maintenance 2020 - 2021 420 December 2020

For evaluation by the Payments SEG Message Items Types

ReferredDocumentInformation <RfrdDocInf> contains the following

ReferredDocumentInformation7 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 422

CodeOrProprietary <CdOrPrtry> [1..1] 422

{Or Code <Cd> [1..1] CodeSet 422

Or} Proprietary <Prtry> [1..1] Text 423

Issuer <Issr> [0..1] Text 423

Number <Nb> [0..1] Text 423

RelatedDate <RltdDt> [0..1] Date 424

LineDetails <LineDtls> [0..*] 424

Identification <Id> [1..*] 425

Type <Tp> [0..1] 426

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

Number <Nb> [0..1] Text 427

RelatedDate <RltdDt> [0..1] Date 427

Description <Desc> [0..1] Text 427

Amount <Amt> [0..1] 427

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 428

DiscountAppliedAmount <DscntApldAmt> [0..*] 429

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 430

TaxAmount <TaxAmt> [0..*] 430

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Amount <Amt> [1..1] Amount C1, C7 431

Exceptions and Investigations - Maintenance 2020 - 2021 421 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 431

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 433

10.1.20.2.1.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of referred document.
Type <Tp> contains the following ReferredDocumentType4 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 422

{Or Code <Cd> [1..1] CodeSet 422

Or} Proprietary <Prtry> [1..1] Text 423

Issuer <Issr> [0..1] Text 423

10.1.20.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 422

Or} Proprietary <Prtry> [1..1] Text 423

10.1.20.2.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Document type in a coded form.
Datatype: "DocumentType6Code" on page 463

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.

Exceptions and Investigations - Maintenance 2020 - 2021 422 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

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.

10.1.20.2.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Proprietary identification of the type of the remittance document.
Datatype: "Max35Text" on page 483

10.1.20.2.1.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Identification of the issuer of the reference document type.
Datatype: "Max35Text" on page 483

10.1.20.2.1.2 Number <Nb>

Presence: [0..1]
Definition: Unique and unambiguous identification of the referred document.

Exceptions and Investigations - Maintenance 2020 - 2021 423 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.20.2.1.3 RelatedDate <RltdDt>

Presence: [0..1]
Definition: Date associated with the referred document.
Datatype: "ISODate" on page 477

10.1.20.2.1.4 LineDetails <LineDtls>

Presence: [0..*]
Definition: Set of elements used to provide the content of the referred document line.

Exceptions and Investigations - Maintenance 2020 - 2021 424 December 2020

For evaluation by the Payments SEG Message Items Types

LineDetails <LineDtls> contains the following DocumentLineInformation1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Identification <Id> [1..*] 425

Type <Tp> [0..1] 426

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

Number <Nb> [0..1] Text 427

RelatedDate <RltdDt> [0..1] Date 427

Description <Desc> [0..1] Text 427

Amount <Amt> [0..1] 427

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 428

DiscountAppliedAmount <DscntApldAmt> [0..*] 429

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 430

TaxAmount <TaxAmt> [0..*] 430

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Amount <Amt> [1..1] Amount C1, C7 431

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 431

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 433

10.1.20.2.1.4.1 Identification <Id>

Presence: [1..*]
Definition: Provides identification of the document line.

Exceptions and Investigations - Maintenance 2020 - 2021 425 December 2020

For evaluation by the Payments SEG Message Items Types

Identification <Id> contains the following DocumentLineIdentification1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 426

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

Number <Nb> [0..1] Text 427

RelatedDate <RltdDt> [0..1] Date 427

10.1.20.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

10.1.20.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

10.1.20.2.1.4.1.1.1.1 Code <Cd>

Presence: [1..1]
Definition: Line identification type in a coded form.
Datatype: "ExternalDocumentLineType1Code" on page 467

10.1.20.2.1.4.1.1.1.2 Proprietary <Prtry>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 426 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Proprietary identification of the type of the remittance document.

Datatype: "Max35Text" on page 483

10.1.20.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 483

10.1.20.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 483

10.1.20.2.1.4.1.3 RelatedDate <RltdDt>

Presence: [0..1]
Definition: Date associated with the referred document line.
Datatype: "ISODate" on page 477

10.1.20.2.1.4.2 Description <Desc>

Presence: [0..1]
Definition: Description associated with the document line.
Datatype: "Max2048Text" on page 482

10.1.20.2.1.4.3 Amount <Amt>

Presence: [0..1]
Definition: Provides details on the amounts of the document line.

Exceptions and Investigations - Maintenance 2020 - 2021 427 December 2020

For evaluation by the Payments SEG Message Items Types

Amount <Amt> contains the following RemittanceAmount3 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 428

DiscountAppliedAmount <DscntApldAmt> [0..*] 429

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 430

TaxAmount <TaxAmt> [0..*] 430

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Amount <Amt> [1..1] Amount C1, C7 431

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 431

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 433

10.1.20.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: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

Exceptions and Investigations - Maintenance 2020 - 2021 428 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

10.1.20.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

10.1.20.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 467

10.1.20.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 483

10.1.20.2.1.4.3.2.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

Exceptions and Investigations - Maintenance 2020 - 2021 429 December 2020

For evaluation by the Payments SEG Message Items Types

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.2.1.4.3.3 CreditNoteAmount <CdtNoteAmt>

Presence: [0..1]
Definition: Amount of a credit note.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.2.1.4.3.4 TaxAmount <TaxAmt>

Presence: [0..*]
Definition: Amount of the tax.
TaxAmount <TaxAmt> contains the following TaxAmountAndType1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Amount <Amt> [1..1] Amount C1, C7 431

10.1.20.2.1.4.3.4.1 Type <Tp>

Presence: [0..1]
Definition: Specifies the type of the amount.

Exceptions and Investigations - Maintenance 2020 - 2021 430 December 2020

For evaluation by the Payments SEG Message Items Types

Type <Tp> contains one of the following TaxAmountType1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

10.1.20.2.1.4.3.4.1.1 Code <Cd>

Presence: [1..1]
Definition: Specifies the amount type, in a coded form.
Datatype: "ExternalTaxAmountType1Code" on page 471

10.1.20.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 483

10.1.20.2.1.4.3.4.2 Amount <Amt>

Presence: [1..1]
Definition: Amount of money, which has been typed.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.2.1.4.3.5 AdjustmentAmountAndReason <AdjstmntAmtAndRsn>

Presence: [0..*]
Definition: Specifies detailed information on the amount and reason of the adjustment.

Exceptions and Investigations - Maintenance 2020 - 2021 431 December 2020

For evaluation by the Payments SEG Message Items Types

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> contains the following

DocumentAdjustment1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

10.1.20.2.1.4.3.5.1 Amount <Amt>

Presence: [1..1]
Definition: Amount of money of the document adjustment.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.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 463

CodeName Name Definition

CRDT Credit Operation is an increase.

DBIT Debit Operation is a decrease.

10.1.20.2.1.4.3.5.3 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the adjustment.
Datatype: "Max4Text" on page 483

10.1.20.2.1.4.3.5.4 AdditionalInformation <AddtlInf>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 432 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Provides further details on the document adjustment.

Datatype: "Max140Text" on page 482

10.1.20.2.1.4.3.6 RemittedAmount <RmtdAmt>

Presence: [0..1]
Definition: Amount of money remitted.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.2.2 ReferredDocumentAmount <RfrdDocAmt>

Presence: [0..1]
Definition: Provides details on the amounts of the referred document.

Exceptions and Investigations - Maintenance 2020 - 2021 433 December 2020

For evaluation by the Payments SEG Message Items Types

ReferredDocumentAmount <RfrdDocAmt> contains the following elements (see

"RemittanceAmount2" on page 198 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 199

DiscountAppliedAmount <DscntApldAmt> [0..*] 200

Type <Tp> [0..1] 200

{Or Code <Cd> [1..1] CodeSet 200

Or} Proprietary <Prtry> [1..1] Text 200

Amount <Amt> [1..1] Amount C1, C7 200

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 201

TaxAmount <TaxAmt> [0..*] 201

Type <Tp> [0..1] 201

{Or Code <Cd> [1..1] CodeSet 202

Or} Proprietary <Prtry> [1..1] Text 202

Amount <Amt> [1..1] Amount C1, C7 202

AdjustmentAmountAndReason <AdjstmntAmtAndRsn> [0..*] 202

Amount <Amt> [1..1] Amount C1, C7 203

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 203

Reason <Rsn> [0..1] Text 203

AdditionalInformation <AddtlInf> [0..1] Text 203

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 204

10.1.20.2.3 CreditorReferenceInformation <CdtrRefInf>

Presence: [0..1]
Definition: Reference information provided by the creditor to allow the identification of the underlying
documents.

Exceptions and Investigations - Maintenance 2020 - 2021 434 December 2020

For evaluation by the Payments SEG Message Items Types

CreditorReferenceInformation <CdtrRefInf> contains the following elements (see

"CreditorReferenceInformation2" on page 175 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] 175

CodeOrProprietary <CdOrPrtry> [1..1] 175

{Or Code <Cd> [1..1] CodeSet 175

Or} Proprietary <Prtry> [1..1] Text 176

Issuer <Issr> [0..1] Text 176

Reference <Ref> [0..1] Text 176

10.1.20.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 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.20.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 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

Exceptions and Investigations - Maintenance 2020 - 2021 435 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.2.6 TaxRemittance <TaxRmt>

Presence: [0..1]
Definition: Provides remittance information about a payment made for tax-related purposes.
TaxRemittance <TaxRmt> contains the following elements (see "TaxData1" on page 454 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Creditor <Cdtr> [0..1] ± 454

Debtor <Dbtr> [0..1] ± 455

UltimateDebtor <UltmtDbtr> [0..1] ± 455

AdministrationZone <AdmstnZone> [0..1] Text 455

ReferenceNumber <RefNb> [0..1] Text 456

Method <Mtd> [0..1] Text 456

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount C1, C7 456

TotalTaxAmount <TtlTaxAmt> [0..1] Amount C1, C7 456

Date <Dt> [0..1] Date 457

SequenceNumber <SeqNb> [0..1] Quantity 457

Record <Rcrd> [0..*] ± 457

10.1.20.2.7 GarnishmentRemittance <GrnshmtRmt>

Presence: [0..1]
Definition: Provides remittance information about a payment for garnishment-related purposes.

Exceptions and Investigations - Maintenance 2020 - 2021 436 December 2020

For evaluation by the Payments SEG Message Items Types

GarnishmentRemittance <GrnshmtRmt> contains the following elements (see "Garnishment3" on

page 440 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] 441

CodeOrProprietary <CdOrPrtry> [1..1] 441

{Or Code <Cd> [1..1] CodeSet 441

Or} Proprietary <Prtry> [1..1] Text 441

Issuer <Issr> [0..1] Text 441

Garnishee <Grnshee> [0..1] ± 442

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] ± 442

ReferenceNumber <RefNb> [0..1] Text 442

Date <Dt> [0..1] Date 442

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 442

FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] Indicator 443

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] Indicator 443

10.1.20.2.8 AdditionalRemittanceInformation <AddtlRmtInf>

Presence: [0..3]
Definition: Additional information, in free text form, to complement the structured remittance information.
Datatype: "Max140Text" on page 482

10.1.20.3 RemittanceInformation21
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.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Unstructured <Ustrd> [0..*] Text 437

Structured <Strd> [0..*] ± 437

10.1.20.3.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 482

10.1.20.3.2 Structured <Strd>

Presence: [0..*]

Exceptions and Investigations - Maintenance 2020 - 2021 437 December 2020

For evaluation by the Payments SEG Message Items Types

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.

Exceptions and Investigations - Maintenance 2020 - 2021 438 December 2020

For evaluation by the Payments SEG Message Items Types

Structured <Strd> contains the following elements (see "StructuredRemittanceInformation17" on

page 418 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

ReferredDocumentInformation <RfrdDocInf> [0..*] 420

Type <Tp> [0..1] 422

CodeOrProprietary <CdOrPrtry> [1..1] 422

{Or Code <Cd> [1..1] CodeSet 422

Or} Proprietary <Prtry> [1..1] Text 423

Issuer <Issr> [0..1] Text 423

Number <Nb> [0..1] Text 423

RelatedDate <RltdDt> [0..1] Date 424

LineDetails <LineDtls> [0..*] 424

Identification <Id> [1..*] 425

Type <Tp> [0..1] 426

CodeOrProprietary <CdOrPrtry> [1..1] 426

{Or Code <Cd> [1..1] CodeSet 426

Or} Proprietary <Prtry> [1..1] Text 426

Issuer <Issr> [0..1] Text 427

Number <Nb> [0..1] Text 427

RelatedDate <RltdDt> [0..1] Date 427

Description <Desc> [0..1] Text 427

Amount <Amt> [0..1] 427

DuePayableAmount <DuePyblAmt> [0..1] Amount C1, C7 428

DiscountAppliedAmount <DscntApldAmt> [0..*] 429

Type <Tp> [0..1] 429

{Or Code <Cd> [1..1] CodeSet 429

Or} Proprietary <Prtry> [1..1] Text 429

Amount <Amt> [1..1] Amount C1, C7 429

CreditNoteAmount <CdtNoteAmt> [0..1] Amount C1, C7 430

TaxAmount <TaxAmt> [0..*] 430

Type <Tp> [0..1] 430

{Or Code <Cd> [1..1] CodeSet 431

Or} Proprietary <Prtry> [1..1] Text 431

Exceptions and Investigations - Maintenance 2020 - 2021 439 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Amount <Amt> [1..1] Amount C1, C7 431

AdjustmentAmountAndReason [0..*] 431

<AdjstmntAmtAndRsn>

Amount <Amt> [1..1] Amount C1, C7 432

CreditDebitIndicator <CdtDbtInd> [0..1] CodeSet 432

Reason <Rsn> [0..1] Text 432

AdditionalInformation <AddtlInf> [0..1] Text 432

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 433

ReferredDocumentAmount <RfrdDocAmt> [0..1] ± 433

CreditorReferenceInformation <CdtrRefInf> [0..1] ± 434

Invoicer <Invcr> [0..1] ± 435

Invoicee <Invcee> [0..1] ± 435

TaxRemittance <TaxRmt> [0..1] ± 436

GarnishmentRemittance <GrnshmtRmt> [0..1] ± 436

AdditionalRemittanceInformation <AddtlRmtInf> [0..3] Text 437

10.1.20.4 Garnishment3
Definition: Provides remittance information about a payment for garnishment-related purposes.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [1..1] 441

CodeOrProprietary <CdOrPrtry> [1..1] 441

{Or Code <Cd> [1..1] CodeSet 441

Or} Proprietary <Prtry> [1..1] Text 441

Issuer <Issr> [0..1] Text 441

Garnishee <Grnshee> [0..1] ± 442

GarnishmentAdministrator <GrnshmtAdmstr> [0..1] ± 442

ReferenceNumber <RefNb> [0..1] Text 442

Date <Dt> [0..1] Date 442

RemittedAmount <RmtdAmt> [0..1] Amount C1, C7 442

FamilyMedicalInsuranceIndicator <FmlyMdclInsrncInd> [0..1] Indicator 443

EmployeeTerminationIndicator <MplyeeTermntnInd> [0..1] Indicator 443

Exceptions and Investigations - Maintenance 2020 - 2021 440 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.4.1 Type <Tp>

Presence: [1..1]
Definition: Specifies the type of garnishment.
Type <Tp> contains the following GarnishmentType1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

CodeOrProprietary <CdOrPrtry> [1..1] 441

{Or Code <Cd> [1..1] CodeSet 441

Or} Proprietary <Prtry> [1..1] Text 441

Issuer <Issr> [0..1] Text 441

10.1.20.4.1.1 CodeOrProprietary <CdOrPrtry>

Presence: [1..1]
Definition: Provides the type details of the garnishment.
CodeOrProprietary <CdOrPrtry> contains one of the following GarnishmentType1Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 441

Or} Proprietary <Prtry> [1..1] Text 441

10.1.20.4.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 467

10.1.20.4.1.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Proprietary identification of the type of garnishment.
Datatype: "Max35Text" on page 483

10.1.20.4.1.2 Issuer <Issr>

Presence: [0..1]
Definition: Identification of the issuer of the garnishment type.
Datatype: "Max35Text" on page 483

Exceptions and Investigations - Maintenance 2020 - 2021 441 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.4.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 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.20.4.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.
GarnishmentAdministrator <GrnshmtAdmstr> contains the following elements (see
"PartyIdentification135" on page 206 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.20.4.4 ReferenceNumber <RefNb>

Presence: [0..1]
Definition: Reference information that is specific to the agency receiving the garnishment.
Datatype: "Max140Text" on page 482

10.1.20.4.5 Date <Dt>

Presence: [0..1]
Definition: Date of payment which garnishment was taken from.
Datatype: "ISODate" on page 477

10.1.20.4.6 RemittedAmount <RmtdAmt>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 442 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Amount of money remitted for the referred document.

Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.20.4.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 480):

• Meaning When True: True

• Meaning When False: False

10.1.20.4.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 480):

• Meaning When True: True

• Meaning When False: False

10.1.20.5 RemittanceLocationData1
Definition: Provides additional details on the remittance advice.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Method <Mtd> [1..1] CodeSet 444

ElectronicAddress <ElctrncAdr> [0..1] Text 444

PostalAddress <PstlAdr> [0..1] 444

Name <Nm> [1..1] Text 444

Address <Adr> [1..1] ± 445

Exceptions and Investigations - Maintenance 2020 - 2021 443 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.5.1 Method <Mtd>

Presence: [1..1]
Definition: Method used to deliver the remittance advice information.
Datatype: "RemittanceLocationMethod2Code" on page 474

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).

10.1.20.5.2 ElectronicAddress <ElctrncAdr>

Presence: [0..1]
Definition: Electronic address to which an agent is to send the remittance information.
Datatype: "Max2048Text" on page 482

10.1.20.5.3 PostalAddress <PstlAdr>

Presence: [0..1]
Definition: Postal address to which an agent is to send the remittance information.
PostalAddress <PstlAdr> contains the following NameAndAddress16 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [1..1] Text 444

Address <Adr> [1..1] ± 445

10.1.20.5.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 482

Exceptions and Investigations - Maintenance 2020 - 2021 444 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.20.5.3.2 Address <Adr>

Presence: [1..1]
Definition: Postal address of a party.
Address <Adr> contains the following elements (see "PostalAddress24" on page 413 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

AddressType <AdrTp> [0..1] 414

{Or Code <Cd> [1..1] CodeSet 414

Or} Proprietary <Prtry> [1..1] ± 415

Department <Dept> [0..1] Text 415

SubDepartment <SubDept> [0..1] Text 415

StreetName <StrtNm> [0..1] Text 415

BuildingNumber <BldgNb> [0..1] Text 415

BuildingName <BldgNm> [0..1] Text 416

Floor <Flr> [0..1] Text 416

PostBox <PstBx> [0..1] Text 416

Room <Room> [0..1] Text 416

PostCode <PstCd> [0..1] Text 416

TownName <TwnNm> [0..1] Text 416

TownLocationName <TwnLctnNm> [0..1] Text 416

DistrictName <DstrctNm> [0..1] Text 416

CountrySubDivision <CtrySubDvsn> [0..1] Text 417

Country <Ctry> [0..1] CodeSet C6 417

AddressLine <AdrLine> [0..7] Text 417

10.1.21 Status
10.1.21.1 CancellationReason33Choice
Definition: Specifies the reason for the cancellation request.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 445

Or} Proprietary <Prtry> [1..1] Text 446

10.1.21.1.1 Code <Cd>

Presence: [1..1]

Exceptions and Investigations - Maintenance 2020 - 2021 445 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Reason for the cancellation request, in a coded form.

Datatype: "ExternalCancellationReason1Code" on page 465

10.1.21.1.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the cancellation request, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.21.2 CancellationStatusReason4
Definition: Provides further details on the status of the cancellation request.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Originator <Orgtr> [0..1] ± 446

Reason <Rsn> [0..1] 446

{Or Code <Cd> [1..1] CodeSet 447

Or} Proprietary <Prtry> [1..1] Text 447

AdditionalInformation <AddtlInf> [0..*] Text 447

10.1.21.2.1 Originator <Orgtr>

Presence: [0..1]
Definition: Party that issues the cancellation status.
Originator <Orgtr> contains the following elements (see "PartyIdentification135" on page 206 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Name <Nm> [0..1] Text 206

PostalAddress <PstlAdr> [0..1] ± 206

Identification <Id> [0..1] ± 207

CountryOfResidence <CtryOfRes> [0..1] CodeSet C6 207

ContactDetails <CtctDtls> [0..1] ± 208

10.1.21.2.2 Reason <Rsn>

Presence: [0..1]
Definition: Specifies the reason for the status report.

Exceptions and Investigations - Maintenance 2020 - 2021 446 December 2020

For evaluation by the Payments SEG Message Items Types

Reason <Rsn> contains one of the following CancellationStatusReason3Choice elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 447

Or} Proprietary <Prtry> [1..1] Text 447

10.1.21.2.2.1 Code <Cd>

Presence: [1..1]
Definition: Reason for the cancellation status, in a coded form.
Datatype: "ExternalPaymentCancellationRejection1Code" on page 469

10.1.21.2.2.2 Proprietary <Prtry>

Presence: [1..1]
Definition: Reason for the status, in a proprietary form.
Datatype: "Max35Text" on page 483

10.1.21.2.3 AdditionalInformation <AddtlInf>

Presence: [0..*]
Definition: Further details on the cancellation status reason.
Datatype: "Max105Text" on page 481

10.1.22 System Identification

10.1.22.1 ClearingSystemIdentification2Choice
Definition: Choice of a clearing system identifier.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

{Or Code <Cd> [1..1] CodeSet 447

Or} Proprietary <Prtry> [1..1] Text 447

10.1.22.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 466

10.1.22.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 483

Exceptions and Investigations - Maintenance 2020 - 2021 447 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.23 Tax
10.1.23.1 TaxParty1
Definition: Details about the entity involved in the tax paid or to be paid.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 448

RegistrationIdentification <RegnId> [0..1] Text 448

TaxType <TaxTp> [0..1] Text 448

10.1.23.1.1 TaxIdentification <TaxId>

Presence: [0..1]
Definition: Tax identification number of the creditor.
Datatype: "Max35Text" on page 483

10.1.23.1.2 RegistrationIdentification <RegnId>

Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: "Max35Text" on page 483

10.1.23.1.3 TaxType <TaxTp>

Presence: [0..1]
Definition: Type of tax payer.
Datatype: "Max35Text" on page 483

10.1.23.2 TaxRecord3
Definition: Set of elements used to define the tax record.

Exceptions and Investigations - Maintenance 2020 - 2021 448 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] Text 449

Category <Ctgy> [0..1] Text 449

CategoryDetails <CtgyDtls> [0..1] Text 449

DebtorStatus <DbtrSts> [0..1] Text 449

CertificateIdentification <CertId> [0..1] Text 450

FormsCode <FrmsCd> [0..1] Text 450

Period <Prd> [0..1] ± 450

TaxAmount <TaxAmt> [0..1] 450

Rate <Rate> [0..1] Rate 450

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount C1, C7 451

TotalAmount <TtlAmt> [0..1] Amount C1, C7 451

Details <Dtls> [0..*] 451

Period <Prd> [0..1] ± 452

Amount <Amt> [1..1] Amount C1, C7 452

AdditionalInformation <AddtlInf> [0..1] Text 452

10.1.23.2.1 Type <Tp>

Presence: [0..1]
Definition: High level code to identify the type of tax details.
Datatype: "Max35Text" on page 483

10.1.23.2.2 Category <Ctgy>

Presence: [0..1]
Definition: Specifies the tax code as published by the tax authority.
Datatype: "Max35Text" on page 483

10.1.23.2.3 CategoryDetails <CtgyDtls>

Presence: [0..1]
Definition: Provides further details of the category tax code.
Datatype: "Max35Text" on page 483

10.1.23.2.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 483

Exceptions and Investigations - Maintenance 2020 - 2021 449 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.23.2.5 CertificateIdentification <CertId>

Presence: [0..1]
Definition: Identification number of the tax report as assigned by the taxing authority.
Datatype: "Max35Text" on page 483

10.1.23.2.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 483

10.1.23.2.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 elements (see "TaxPeriod3" on page 452 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 453

Type <Tp> [0..1] CodeSet 453

FromToDate <FrToDt> [0..1] ± 454

10.1.23.2.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Rate <Rate> [0..1] Rate 450

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount C1, C7 451

TotalAmount <TtlAmt> [0..1] Amount C1, C7 451

Details <Dtls> [0..*] 451

Period <Prd> [0..1] ± 452

Amount <Amt> [1..1] Amount C1, C7 452

10.1.23.2.8.1 Rate <Rate>

Presence: [0..1]
Definition: Rate used to calculate the tax.
Datatype: "PercentageRate" on page 480

Exceptions and Investigations - Maintenance 2020 - 2021 450 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.23.2.8.2 TaxableBaseAmount <TaxblBaseAmt>

Presence: [0..1]
Definition: Amount of money on which the tax is based.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.23.2.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: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.23.2.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

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Period <Prd> [0..1] ± 452

Amount <Amt> [1..1] Amount C1, C7 452

Exceptions and Investigations - Maintenance 2020 - 2021 451 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.23.2.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 elements (see "TaxPeriod3" on page 452 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 453

Type <Tp> [0..1] CodeSet 453

FromToDate <FrToDt> [0..1] ± 454

10.1.23.2.8.4.2 Amount <Amt>

Presence: [1..1]
Definition: Underlying tax amount related to the specified period.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.23.2.9 AdditionalInformation <AddtlInf>

Presence: [0..1]
Definition: Further details of the tax record.
Datatype: "Max140Text" on page 482

10.1.23.3 TaxPeriod3
Definition: Period of time details related to the tax payment.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Year <Yr> [0..1] Year 453

Type <Tp> [0..1] CodeSet 453

FromToDate <FrToDt> [0..1] ± 454

Exceptions and Investigations - Maintenance 2020 - 2021 452 December 2020

For evaluation by the Payments SEG Message Items Types

10.1.23.3.1 Year <Yr>

Presence: [0..1]
Definition: Year related to the tax payment.
Datatype: "ISOYear" on page 484

10.1.23.3.2 Type <Tp>

Presence: [0..1]
Definition: Identification of the period related to the tax payment.
Datatype: "TaxRecordPeriod1Code" on page 475

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.

Exceptions and Investigations - Maintenance 2020 - 2021 453 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

HLF2 SecondHalf Tax is related to the second half of the

period.

10.1.23.3.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 160 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

FromDate <FrDt> [1..1] Date 161

ToDate <ToDt> [1..1] Date 161

10.1.23.4 TaxData1
Definition: Details about tax paid, or to be paid, to the government in accordance with the law, including
pre-defined parameters such as thresholds and type of account.

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Creditor <Cdtr> [0..1] ± 454

Debtor <Dbtr> [0..1] ± 455

UltimateDebtor <UltmtDbtr> [0..1] ± 455

AdministrationZone <AdmstnZone> [0..1] Text 455

ReferenceNumber <RefNb> [0..1] Text 456

Method <Mtd> [0..1] Text 456

TotalTaxableBaseAmount <TtlTaxblBaseAmt> [0..1] Amount C1, C7 456

TotalTaxAmount <TtlTaxAmt> [0..1] Amount C1, C7 456

Date <Dt> [0..1] Date 457

SequenceNumber <SeqNb> [0..1] Quantity 457

Record <Rcrd> [0..*] ± 457

10.1.23.4.1 Creditor <Cdtr>

Presence: [0..1]
Definition: Party on the credit side of the transaction to which the tax applies.

Exceptions and Investigations - Maintenance 2020 - 2021 454 December 2020

For evaluation by the Payments SEG Message Items Types

Creditor <Cdtr> contains the following elements (see "TaxParty1" on page 448 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 448

RegistrationIdentification <RegnId> [0..1] Text 448

TaxType <TaxTp> [0..1] Text 448

10.1.23.4.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 457 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 458

RegistrationIdentification <RegnId> [0..1] Text 458

TaxType <TaxTp> [0..1] Text 458

Authorisation <Authstn> [0..1] 458

Title <Titl> [0..1] Text 458

Name <Nm> [0..1] Text 458

10.1.23.4.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.
UltimateDebtor <UltmtDbtr> contains the following elements (see "TaxParty2" on page 457 for
details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 458

RegistrationIdentification <RegnId> [0..1] Text 458

TaxType <TaxTp> [0..1] Text 458

Authorisation <Authstn> [0..1] 458

Title <Titl> [0..1] Text 458

Name <Nm> [0..1] Text 458

10.1.23.4.4 AdministrationZone <AdmstnZone>

Presence: [0..1]
Definition: Territorial part of a country to which the tax payment is related.

Exceptions and Investigations - Maintenance 2020 - 2021 455 December 2020

For evaluation by the Payments SEG Message Items Types

Datatype: "Max35Text" on page 483

10.1.23.4.5 ReferenceNumber <RefNb>

Presence: [0..1]
Definition: Tax reference information that is specific to a taxing agency.
Datatype: "Max140Text" on page 482

10.1.23.4.6 Method <Mtd>

Presence: [0..1]
Definition: Method used to indicate the underlying business or how the tax is paid.
Datatype: "Max35Text" on page 483

10.1.23.4.7 TotalTaxableBaseAmount <TtlTaxblBaseAmt>

Presence: [0..1]
Definition: Total amount of money on which the tax is based.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.1.23.4.8 TotalTaxAmount <TtlTaxAmt>

Presence: [0..1]
Definition: Total amount of money as result of the calculation of the tax.
Impacted by: C1 "ActiveOrHistoricCurrency", C7 "CurrencyAmount"
Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 459

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Exceptions and Investigations - Maintenance 2020 - 2021 456 December 2020

For evaluation by the Payments SEG Message Items Types

Note: The decimal separator is a dot.

10.1.23.4.9 Date <Dt>

Presence: [0..1]
Definition: Date by which tax is due.
Datatype: "ISODate" on page 477

10.1.23.4.10 SequenceNumber <SeqNb>

Presence: [0..1]
Definition: Sequential number of the tax report.
Datatype: "Number" on page 480

10.1.23.4.11 Record <Rcrd>

Presence: [0..*]
Definition: Record of tax details.
Record <Rcrd> contains the following elements (see "TaxRecord3" on page 448 for details)

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Type <Tp> [0..1] Text 449

Category <Ctgy> [0..1] Text 449

CategoryDetails <CtgyDtls> [0..1] Text 449

DebtorStatus <DbtrSts> [0..1] Text 449

CertificateIdentification <CertId> [0..1] Text 450

FormsCode <FrmsCd> [0..1] Text 450

Period <Prd> [0..1] ± 450

TaxAmount <TaxAmt> [0..1] 450

Rate <Rate> [0..1] Rate 450

TaxableBaseAmount <TaxblBaseAmt> [0..1] Amount C1, C7 451

TotalAmount <TtlAmt> [0..1] Amount C1, C7 451

Details <Dtls> [0..*] 451

Period <Prd> [0..1] ± 452

Amount <Amt> [1..1] Amount C1, C7 452

AdditionalInformation <AddtlInf> [0..1] Text 452

10.1.23.5 TaxParty2
Definition: Details about the entity involved in the tax paid or to be paid.

Exceptions and Investigations - Maintenance 2020 - 2021 457 December 2020

For evaluation by the Payments SEG Message Items Types

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

TaxIdentification <TaxId> [0..1] Text 458

RegistrationIdentification <RegnId> [0..1] Text 458

TaxType <TaxTp> [0..1] Text 458

Authorisation <Authstn> [0..1] 458

Title <Titl> [0..1] Text 458

Name <Nm> [0..1] Text 458

10.1.23.5.1 TaxIdentification <TaxId>

Presence: [0..1]
Definition: Tax identification number of the debtor.
Datatype: "Max35Text" on page 483

10.1.23.5.2 RegistrationIdentification <RegnId>

Presence: [0..1]
Definition: Unique identification, as assigned by an organisation, to unambiguously identify a party.
Datatype: "Max35Text" on page 483

10.1.23.5.3 TaxType <TaxTp>

Presence: [0..1]
Definition: Type of tax payer.
Datatype: "Max35Text" on page 483

10.1.23.5.4 Authorisation <Authstn>

Presence: [0..1]
Definition: Details of the authorised tax paying party.
Authorisation <Authstn> contains the following TaxAuthorisation1 elements

Or MessageElement<XML Tag> Mult. Type Constr. Page

No.

Title <Titl> [0..1] Text 458

Name <Nm> [0..1] Text 458

10.1.23.5.4.1 Title <Titl>

Presence: [0..1]
Definition: Title or position of debtor or the debtor's authorised representative.
Datatype: "Max35Text" on page 483

10.1.23.5.4.2 Name <Nm>

Presence: [0..1]

Exceptions and Investigations - Maintenance 2020 - 2021 458 December 2020

For evaluation by the Payments SEG Message Items Types

Definition: Name of the debtor or the debtor's authorised representative.

Datatype: "Max140Text" on page 482

10.2 Message Datatypes

10.2.1 Amount
10.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 460

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.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 461

Exceptions and Investigations - Maintenance 2020 - 2021 459 December 2020

For evaluation by the Payments SEG Message Items Types

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.

• CurrencyAmount
The number of fractional digits (or minor unit of currency) must comply with ISO 4217.

Note: The decimal separator is a dot.

10.2.2 Binary
10.2.2.1 Max10KBinary
Definition: Binary data of 10K maximum.
Type: Binary

Format

minLength 1

maxLength 10240

10.2.3 CodeSet
10.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

Exceptions and Investigations - Maintenance 2020 - 2021 460 December 2020

For evaluation by the Payments SEG Message Items Types

Maintenance Agency, consist of three (3) contiguous letters, and are not yet withdrawn on the day
the message containing the Currency is exchanged.

10.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

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.

10.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.

10.2.3.4 CancellationIndividualStatus1Code
Definition: Specifies the status of a cancellation request.
Type: CodeSet

CodeName Name Definition

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

10.2.3.5 ChargeBearerType1Code
Definition: Specifies which party(ies) will pay charges due for processing of the instruction.

Exceptions and Investigations - Maintenance 2020 - 2021 461 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.2.3.6 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.

10.2.3.7 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}

Exceptions and Investigations - Maintenance 2020 - 2021 462 December 2020

For evaluation by the Payments SEG Message Items Types

Constraints

• Country
The code is checked against the list of country names obtained from the United Nations (ISO 3166,
Alpha-2 code).

10.2.3.8 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.

10.2.3.9 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.

10.2.3.10 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.

Exceptions and Investigations - Maintenance 2020 - 2021 463 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

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.

10.2.3.11 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

Format

minLength 1

maxLength 4

10.2.3.12 ExternalAgentInstruction1Code
Definition: Specifies further instructions for the agent concerning the processing of an instruction.

External code sets can be downloaded from www.iso20022.org.

Exceptions and Investigations - Maintenance 2020 - 2021 464 December 2020

For evaluation by the Payments SEG Message Items Types

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.13 ExternalCancellationReason1Code
Definition: Specifies the cancellation reason, as published in an external cancellation reason code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.14 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

10.2.3.15 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

10.2.3.16 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.

Exceptions and Investigations - Maintenance 2020 - 2021 465 December 2020

For evaluation by the Payments SEG Message Items Types

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.17 ExternalChargeType1Code
Definition: Specifies the nature, or use, of the charges 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

10.2.3.18 ExternalClaimNonReceiptRejection1Code
Definition: Specifies the reason for the rejection of a claim non receipt, as published in an external claim
non receipt rejection code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.19 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

10.2.3.20 ExternalCreditorAgentInstruction1Code
Definition: Specifies further instructions concerning the processing of a payment instruction, as provided
to the creditor agent.

Exceptions and Investigations - Maintenance 2020 - 2021 466 December 2020

For evaluation by the Payments SEG Message Items Types

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.21 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

10.2.3.22 ExternalDocumentLineType1Code
Definition: Specifies the document line type as published in an external document type code list.
Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.23 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

10.2.3.24 ExternalGarnishmentType1Code
Definition: Specifies the garnishment type as published in an external document type code list.
Type: CodeSet

Exceptions and Investigations - Maintenance 2020 - 2021 467 December 2020

For evaluation by the Payments SEG Message Items Types

Format

minLength 1

maxLength 4

10.2.3.25 ExternalInvestigationExecutionConfirmation1Code
Definition: Specifies the result of an investigation, as published in an external investigation execution
confirmation code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1
maxLength 4

10.2.3.26 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

10.2.3.27 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

10.2.3.28 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.

Exceptions and Investigations - Maintenance 2020 - 2021 468 December 2020

For evaluation by the Payments SEG Message Items Types

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.29 ExternalPaymentCancellationRejection1Code
Definition: Specifies the reason for the rejection of a cancellation, as published in an external payment
cancellation rejection code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.30 ExternalPaymentCompensationReason1Code
Definition: Specifies the reason for compensation for the processing of a payment, as published in an
external code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.31 ExternalPaymentModificationRejection1Code
Definition: Specifies the reason for the rejection of a modification, as published in an external payment
modification rejection code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.32 ExternalPersonIdentification1Code
Definition: Specifies the external person identification scheme name code in the format of character
string with a maximum length of 4 characters.

Exceptions and Investigations - Maintenance 2020 - 2021 469 December 2020

For evaluation by the Payments SEG Message Items Types

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

10.2.3.33 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

10.2.3.34 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

10.2.3.35 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

Exceptions and Investigations - Maintenance 2020 - 2021 470 December 2020

For evaluation by the Payments SEG Message Items Types

maxLength 4

10.2.3.36 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

10.2.3.37 ExternalUnableToApplyIncorrectData1Code
Definition: Specifies the reason of an unable to apply due to incorrect data, as published in an external
unable to apply incorrect data code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.38 ExternalUnableToApplyMissingData1Code
Definition: Specifies the reason of an unable to apply due to missing data, as published in an external
unable to apply missing data code set.

External code sets can be downloaded from www.iso20022.org.

Type: CodeSet

Format

minLength 1

maxLength 4

10.2.3.39 Frequency6Code
Definition: Specifies the regularity of an event.
Type: CodeSet

CodeName Name Definition

YEAR Annual Event takes place every year or once a

year.

Exceptions and Investigations - Maintenance 2020 - 2021 471 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

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.

10.2.3.40 GroupCancellationStatus1Code
Definition: Specifies the status of a group of cancellation requests.
Type: CodeSet

CodeName Name Definition

PACR PartiallyAcceptedCancellationRequest Cancellation is partially accepted.

RJCR RejectedCancellationRequest Cancellation request is rejected

ACCR AcceptedCancellationRequest Cancellation is accepted.

PDCR PendingCancellationRequest Cancellation request is pending.

10.2.3.41 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.

10.2.3.42 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.

Exceptions and Investigations - Maintenance 2020 - 2021 472 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

VARI Variable Direct debit amount is variable.

10.2.3.43 NamePrefix2Code
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.

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).

10.2.3.44 PaymentMethod4Code
Definition: Specifies the transfer method that will be used to transfer an amount of money.
Type: CodeSet

CodeName Name Definition

CHK Cheque Written order to a bank to pay a certain

amount of money from one person to
another person.

TRF CreditTransfer Transfer of an amount of money in the

books of the account servicer.

DD DirectDebit Collection of an amount of money from

the debtor's bank account by the
creditor. The amount of money and
dates of collections may vary.

TRA TransferAdvice Transfer of an amount of money in the

books of the account servicer. An advice
should be sent back to the account
owner.

10.2.3.45 PreferredContactMethod1Code
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.

Exceptions and Investigations - Maintenance 2020 - 2021 473 December 2020

For evaluation by the Payments SEG Message Items Types

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.

10.2.3.46 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.

10.2.3.47 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).

10.2.3.48 SequenceType3Code
Definition: Specifies the type of the current transaction that belongs to a sequence of transactions.
Type: CodeSet

CodeName Name Definition

FRST First First collection of a series of direct debit

instructions.

Exceptions and Investigations - Maintenance 2020 - 2021 474 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

RCUR Recurring Direct debit instruction where the

debtor's authorisation is used for regular
direct debit transactions initiated by the
creditor.

FNAL Final Final collection of a series of direct debit

instructions.

OOFF OneOff Direct debit instruction where the

debtor's authorisation is used to initiate
one single direct debit transaction.

RPRE Represented Collection used to re-present previously

reversed or returned direct debit
transactions.

10.2.3.49 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.

10.2.3.50 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.

Exceptions and Investigations - Maintenance 2020 - 2021 475 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

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.

10.2.3.51 TransactionIndividualStatus1Code
Definition: Specifies the status of a single payment transaction.
Type: CodeSet

CodeName Name Definition

ACTC AcceptedTechnicalValidation Authentication and syntactical and

semantical validation are successful.

RJCT Rejected Payment initiation or individual

transaction included in the payment
initiation has been rejected.

PDNG Pending Payment initiation or individual

transaction included in the payment
initiation is pending. Further checks and
status update will be performed.

ACCP AcceptedCustomerProfile Preceding check of technical validation

was successful. Customer profile check
was also successful.

ACSP AcceptedSettlementInProcess All preceding checks such as technical

validation and customer profile were
successful and therefore the payment
initiation has been accepted for
execution.

Exceptions and Investigations - Maintenance 2020 - 2021 476 December 2020

For evaluation by the Payments SEG Message Items Types

CodeName Name Definition

ACSC AcceptedSettlementCompleted Settlement on the debtor's account has

been completed.

Usage : this can be used by the first

agent to report to the debtor that the
transaction has been completed.
Warning : this status is provided for
transaction status reasons, not for
financial information. It can only be used
after bilateral agreement

ACCR AcceptedCancellationRequest Cancellation is accepted.

ACWC AcceptedWithChange Instruction is accepted but a change will

be made, such as date or remittance not
sent.

10.2.4 Date
10.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

10.2.5 DateTime
10.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

Exceptions and Investigations - Maintenance 2020 - 2021 477 December 2020

For evaluation by the Payments SEG Message Items Types

10.2.6 IdentifierSet
10.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.

10.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.

10.2.6.3 IBAN2007Identifier
Definition: An identifier used internationally by financial institutions to uniquely identify the account of a
customer at a financial institution, as described in the latest edition of the international standard ISO
13616: 2007 - "Banking and related financial services - International Bank Account Number (IBAN)".
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}

Exceptions and Investigations - Maintenance 2020 - 2021 478 December 2020

For evaluation by the Payments SEG Message Items Types

Constraints

• IBAN
A valid IBAN consists of all three of the following components: Country Code, check digits and
BBAN.

10.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}

10.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}

10.2.7 Indicator
10.2.7.1 AMLIndicator
Definition: Indicates the status of an anti-money laundering investigation.
Type: Indicator
Meaning When True: Indicates that the investigation is related to an anti-money laundering investigation
request.
Meaning When False: Indicates that the investigation is not related to an anti-money laundering
investigation request.

10.2.7.2 ChargeIncludedIndicator
Definition: Indicates whether charges have already been included.
Type: Indicator
Meaning When True: Included
Meaning When False: Pre-advised

10.2.7.3 GroupCancellationIndicator
Definition: Indicates whether or not it is a group cancellation.
Type: Indicator

Exceptions and Investigations - Maintenance 2020 - 2021 479 December 2020

For evaluation by the Payments SEG Message Items Types

Meaning When True: Indicates that the cancellation applies to the complete group.
Meaning When False: Indicates that the cancellation applies to individual items within the group.

10.2.7.4 TrueFalseIndicator
Definition: A flag indicating a True or False value.
Type: Indicator
Meaning When True: True
Meaning When False: False

10.2.7.5 YesNoIndicator
Definition: Indicates a "Yes" or "No" type of answer for an element.
Type: Indicator
Meaning When True: Yes
Meaning When False: No

10.2.8 Quantity
10.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

10.2.8.2 Number
Definition: Number of objects represented as an integer.
Type: Quantity

Format

totalDigits 18

fractionDigits 0

10.2.9 Rate
10.2.9.1 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

Exceptions and Investigations - Maintenance 2020 - 2021 480 December 2020

For evaluation by the Payments SEG Message Items Types

Format

totalDigits 11

fractionDigits 10

baseValue 100.0

10.2.10 Text
10.2.10.1 Exact2NumericText
Definition: Specifies a numeric string with an exact length of 2 digits.
Type: Text

Format

pattern [0-9]{2}

10.2.10.2 Exact4AlphaNumericText
Definition: Specifies an alphanumeric string with a length of 4 characters.
Type: Text

Format

pattern [a-zA-Z0-9]{4}

10.2.10.3 Max1025Text
Definition: Specifies a character string with a maximum length of 1025 characters.
Type: Text

Format

minLength 1

maxLength 1025

10.2.10.4 Max105Text
Definition: Specifies a character string with a maximum length of 105 characters.
Type: Text

Format

minLength 1

maxLength 105

10.2.10.5 Max128Text
Definition: Specifies a character string with a maximum length of 128 characters.
Type: Text

Exceptions and Investigations - Maintenance 2020 - 2021 481 December 2020

For evaluation by the Payments SEG Message Items Types

Format

minLength 1

maxLength 128

10.2.10.6 Max140Text
Definition: Specifies a character string with a maximum length of 140 characters.
Type: Text

Format

minLength 1

maxLength 140

10.2.10.7 Max15NumericText
Definition: Specifies a numeric string with a maximum length of 15 digits.
Type: Text

Format

pattern [0-9]{1,15}

10.2.10.8 Max16Text
Definition: Specifies a character string with a maximum length of 16 characters.
Type: Text

Format

minLength 1

maxLength 16

10.2.10.9 Max2048Text
Definition: Specifies a character string with a maximum length of 2048 characters.
Type: Text

Format

minLength 1

maxLength 2048

10.2.10.10 Max34Text
Definition: Specifies a character string with a maximum length of 34 characters.
Type: Text

Exceptions and Investigations - Maintenance 2020 - 2021 482 December 2020

For evaluation by the Payments SEG Message Items Types

Format

minLength 1

maxLength 34

10.2.10.11 Max350Text
Definition: Specifies a character string with a maximum length of 350 characters.
Type: Text

Format

minLength 1

maxLength 350

10.2.10.12 Max35Text
Definition: Specifies a character string with a maximum length of 35 characters.
Type: Text

Format

minLength 1

maxLength 35

10.2.10.13 Max4Text
Definition: Specifies a character string with a maximum length of 4 characters.
Type: Text

Format

minLength 1

maxLength 4

10.2.10.14 Max70Text
Definition: Specifies a character string with a maximum length of 70characters.
Type: Text

Format

minLength 1

maxLength 70

10.2.10.15 PhoneNumber
Definition: The collection of information which identifies a specific phone or FAX number as defined by
telecom services.

Exceptions and Investigations - Maintenance 2020 - 2021 483 December 2020

For evaluation by the Payments SEG Message Items Types

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}

10.2.11 Year
10.2.11.1 ISOYear
Definition: Year represented by YYYY (ISO 8601).
Type: Year

Exceptions and Investigations - Maintenance 2020 - 2021 484 December 2020