Functional Specification of the Clearing Service of …..."20" – participant of STEP2 or another SEPA payment system. Where a message has been addressed to an entity with an 11-digit

Appendix 1

to Latvijas Banka's Board Regulation No. 1591/1

of 31 October 2019

Functional Specification of the Clearing Service of the the Electronic Clearing

System of Latvijas Banka (EKS)

Contents

1. Message exchange in the clearing service ................................................................ 2

2. Clearing service procedures ...................................................................................... 4 3. Timetable of the clearing cycles ............................................................................... 5

4. Generating files ......................................................................................................... 6

5. Generating bulk headers and messages .................................................................. 15 6. File and message validation .................................................................................. 108 7. Clearing result file ................................................................................................ 112 8. Warning message .................................................................................................. 113 9. Account statement ................................................................................................ 113

10. Information on direct and indirect participants of STEP2 system ....................... 114

2

The "Functional Specification of the clearing service of the Electronic Clearing System

of Latvijas Banka (EKS)" (hereinafter, the Specification) establishes the requirements for

preparing the files to be processed in the clearing service of the electronic clearing system

of Latvijas Banka (hereinafter, the EKS) and the relevant messages to be included in the

files, the structure of the messages associated with their processing as well as the time

frame of the clearing cycles.

The terms used in the Specification are consistent with the terms used in Appendix 1

"System Rules for Participation in the EKS" to Latvijas Banka's Council Procedure

No. 183/3 "Participation Procedure in Latvijas Banka's Electronic Clearing System" of

9 September 2010 and their explanation.

1. Message exchange in the clearing service

The clearing service accepts and processes messages generated in accordance with the

SEPA Credit Transfer Scheme Rulebook approved by the European Payments Council,

the SEPA Credit Transfer Scheme Inter-Bank Implementation Guidelines approved by

the European Payments Council and ISO 20022 XML messaging standards (hereinafter,

ISO 20022) and included in the appropriate file type.

Message name Message type The type of the file

where the message is

included

File sender

Payment messages

SEPA credit transfer

message

pacs.008.001.02 PE– credit transfer and

payment return file

EKS or

participant

SEPA payment return

message

pacs.004.001.02 PE EKS or

participant

Information messages

SEPA payment

cancellation request

message

camt.056.001.01 PE EKS or

participant

SEPA resolution of

investigation (negative

response to the

cancellation request)

message

camt.029.001.03 PE EKS or

participant

Status request message pacs.028.001.01 PE file or IE – input

inquiry file

Participant

OE – output inquiry

file

EKS

SEPA claim of non-receipt

message

camt.027.001.06 IE

Participant

OE

EKS

SEPA claim for value date

correction message

camt.087.001.05 IE Participant

OE

EKS

3

SEPA resolution of

investigation (response to

the investigation request)

message

camt.029.001.08 IE

Participant

OE EKS

Status message pacs.002.001.03 VE file – PE file

validation result file or

QE file – IE file

validation result file

EKS

Moved payment

notification message

pacs.002.001.03 FE – moved payments

file

EKS

Excluded payment

rejection message

pacs.002.001.03 UE– excluded

payment rejection file

EKS

Clearing result message – TE – clearing result

file

EKS

Warning message – ME– warning file EKS

Cover account statement

message

– KE– cover account

statement file

EKS

The messages to be submitted by participants to the clearing service may be addressed to

the EKS participants using the services of the clearing service, their indirect participants

and addressable BIC holders as well as the entities reachable via STEP2 (see Chart 1).

Entity(addressable BIC)

Participant

Participant

EKS STEP2

EntityEntity

€


Entity(addressable

BIC)


registered BIC

of part icipant

€

registered BIC

of part icipant

€ €

€

€

€ €

€ €

registered BIC

of part icipant

Chart 1. The operation scheme of the clearing service

Latvijas Banka shall establish and maintain a list containing information on entities

reachable via the clearing service, including entities reachable via STEP2 (the routing

table). The routing table shall be updated at least once a month. Regular updates shall

take effect on the first Tuesday following the first Saturday of each month. The updated

tables shall be available for downloading at the file exchange service no later than on the

last Friday before the changes take effect. The title of the routing table shall be

BICYYYYMMDD.txt where the part of the BIC code shall always remain the same,

4

whereas the part "YYYYMMDD" shall be the date when the updated table takes effect.

The routing table is a text file with the following structure:

No. Element Format Description

1. Name 105a Name.

2. BIC 11a 11-digit BIC or

8-digit BIC with the extension "XXX".

3. Valid from 8n Date when the data become valid (YYYYMMDD).

4. Valid until 8n Date up to which the data are valid (YYYYMMDD).

5. Type of

participation

2n Refers to the participant's reachability:

"00" – not reachable;

"05" – participant;

"06" – indirect participant or addressable BIC holder;

"20" – participant of STEP2 or another SEPA

payment system.

Where a message has been addressed to an entity with an 11-digit BIC which cannot be

found in the routing table, the clearing service shall verify whether an 8-digit BIC with

the extension "XXX" corresponding to the 11-digit BIC is included in the routing table

and, if so, the message shall be accepted and the routing shall be established in accordance

with the routing instructions for the respective 8-digit BIC with the extension "XXX".

Where a participant, indirect participant or addressable BIC holder chooses to receive all

incoming SEPA payments using the clearing service, Latvijas Banka shall be indicated in

the STEP2 directory as a participant through which respective participant, indirect

participant or addressable BIC holder receives the incoming payments.

In addition to the routing table, Latvijas Banka shall provide to participants information

on direct and indirect participants of STEP2 system which shall be updated at least once

a month. The relevant files shall be formatted according to Section 10 herein and shall be

available to participants for download in the file exchange service.

2. Clearing service procedures

The payment processing diagram (see Chart 2) depicts a sequence of clearing service

procedures described in Appendix 1 "System Rules for Participation in the EKS" to

Latvijas Banka's Council Procedure No. 183/3 "Participation Procedure in Latvijas

Banka's Electronic Clearing System" of 9 September 2010, executed from the moment of

the message submission to the clearing service until the sending of the processed message

to a participant or entity reachable via STEP2. The present document does not describe

the procedures for information exchange and settlement between the payment systems as

well as between the participants and indirect participants or addressable BIC holders.

5

Receipt of payment message files and their

registration in the archive

Validation of payment message files

Validation of payment messages

Acceptance/rejection of payment messages

Calculation of the multilateral net positions

Transmission of the clearing results and payment message files

Settlement in TARGET2 or on cover accounts

Processing of the settlement confirmations

and generation of the clearing results

Registration of clearing results and payment

messages in the archive

Transmission of the clearing results and

payment message files

€

Registered BICof participant

EKS

STEP2

EKS

€

Entity

€

Registered BIC of participant

STEP2

Booking of a pre-deposits (only for respective

users)

Chart 2. Clearing service procedures

3. Timetable of the clearing cycles

The clearing service daytime processing shall take place from 8:30 to 21:30 on TARGET2

business days and from 8:00 to 19:00 on TARGET2 holidays. The files submitted by

participants shall be processed in the clearing service in accordance with the timetable of

the clearing cycles.

6

Clearing

cycle

No.

Acceptance of

messages to be sent to

other SEPA payment

systems1

Value date (T – the

value date of the

current business day)

Sending

cut-off

time

Calculation

and sending

of payment

orders for the

settlement

1. Open for receipt T 9:14 9:15–9:30





6. Not open for receipt T 18:14 18:15–18:30

7.2 Open for receipt T + 13 20:59 21:00–21:15

1 Messages are accepted for transmission to the participants of other SEPA payment systems only on

TARGET2 business days. 2 Only on TARGET2 business days. 3 The clearing service accepts files with the value date of the next TARGET2 business day.

4. Generating files

4.1. File name

Each file accepted or transmitted by the clearing service is assigned a unique name in the

format ccdddnnnn.ext with the following elements.

File name element Explanation

cc File type according to Section 1 herein.

ddd The value date of the messages in the file expressed as a number

of days from the beginning of the current year (e.g., January 1

shall be "001", February 25 shall be "056").

nnnn File sequence number on the respective value date.

ext The extension of the encrypted and digitally signed file ("ent" or

"p7m").

4.2. The format to be used for generating files

4.2.1. Mandatory set of characters

Participants shall maintain the following set of UTF-8 characters:

– capital letters of the Latin alphabet (from A to Z);

– small letters of the Latin alphabet (from a to z);

– digits;

– characters – '/', '-', '?', ':', '(', ')', '.', ',', ''' and '+';

– space.

UTF-8 encoding is used for character encoding with a respective indication in the XML

file header.

Example <?xml version="1.0" encoding="UTF-8">

7

4.2.2. Use of letters of the Latin alphabet with Latvian diacritical marks

Latvijas Banka shall maintain and publish on its website a list indicating the consent given

by a participant (with respect to each its registered BIC), indirect participant and

addressable BIC holder to process SEPA credit transfer orders and SEPA payment return

orders containing the letters of the Latin alphabet with Latvian diacritical marks.

The participant's choice to process or not to process the SEPA credit transfer orders and

SEPA payment return orders containing the letters of the Latin alphabet with Latvian

diacritical marks shall apply to its relevant indirect participant and addressable BIC

holder.

The clearing service shall transmit all UTF-8 characters without verifying which sets of

characters are supported by each participant.

A participant is entitled to reject payment messages where characters not listed in

Paragraph 4.2.1 herein have been used, if the participant has not agreed to their

processing.

4.3. Requirements for the contents of a PE type file

Each PE type file may comprise 999 message bulks containing message types according

to Section 1 herein. Each bulk may only comprise the bulk header and messages of the

same type. The total number of messages per file shall not exceed 15 000.

If PE file comprises several message bulks, the bulks shall be sorted in the following

sequence:

– bulks of SEPA credit transfer messages (pacs.008);

– bulks of SEPA payment cancellation request messages (camt.056);

– bulks of SEPA payment return messages (pasc.004);

– bulks of SEPA resolution of investigation (negative response to the cancellation

request) messages camt.029.001.03;

– bulks of status request messages (pacs.028) (may be included only in files sent to

the clearing service).

The messages included in the files generated by the clearing service and addressed to an

indirect participant or addressable BIC holder are placed in separate bulks.

4.4. Requirements for the contents of IE and OE files

Each IE and OE file may comprise 999 message bulks containing message types

according to Section 1 herein. Each bulk may only comprise the bulk header and several

messages of the same type. The total number of messages per file shall not exceed 15 000.

If an IE or OE file comprises several message bulks, the bulks shall be sorted in the

following sequence:

– bulks of SEPA claim of non-receipt messages (camt.027) (only one message per

bulk is allowed);

– bulks of SEPA claim for value date correction messages (camt.087) (only one

message per bulk is allowed);

– bulks of camt.029.001.08 (only one message per bulk is allowed);

8

– bulks of EPA resolution of investigation (response to the investigation request)

message (pacs.028).

4.5. Use of address fields

4.5.1. Parties involved in the message execution

The headers of the bulk and the file comprises fields identifying the parties involved in

executing the message:

– <SndgInst> (in the header of the file) – the BIC of the file sender;

– <RcvgInst> (in the header of the file) – the BIC of the file recipient;

– <InstgAgt> (in the header of the bulk) – the BIC of the bulk sender;

– <InstdAgt> (in the header of the bulk) – the BIC of the bulk recipient;

– <InstgAgt> (in the message) – the BIC of the instructing entity. To be indicated in the

SEPA credit transfer orders and SEPA payment return orders delivered by the clearing

service to a participant;

– <CdtrAgt> (in the message) – creditor agent – the BIC of the financial institution

which holds the creditor's account and receives a SEPA credit transfer message or SEPA

payment return message and credits funds to the creditor's account subject to the

information provided in the message. This BIC is used for message routing;

– <DbtrAgt> (in the message) – debtor agent – the BIC of the financial institution which

holds the debtor's account and receives a payment order from the debtor and sends a SEPA

credit transfer message or SEPA payment return message containing information

provided by the debtor.

Use of fields in messages addressed to institutions reachable via STEP2 is identical to

that of sending messages to participants. Where the clearing service identifies that,

according to the routing table, the BIC indicated in <CdtrAgt> corresponds to the entity

reachable via STEP2, it shall send the message to STEP2.

4.5.2. Use of fields in a SEPA credit transfer message where the sender and recipient of

the message are participants

€

BankB_BIC

€

BankA_BIC

EKS

FileHeader SndgInst BankA_BIC

RcvgInst LACBLV2X

GrpHdr InstgAgt BankA_BIC

InstdAgt

CdtTrfTxInf InstgAgtCdtrAgt BankB_BIC

FileHeader SndgInst LACBLV2X

RcvgInst BankB_BIC

GrpHdr InstgAgt

InstdAgt BankB_BIC

CdtTrfTxInf InstgAgt BankA_BIC

CdtrAgt BankB_BIC

9

4.5.3. Use of fields in a SEPA credit transfer message where the sender and recipient of

the message are indirect participants or addressable BIC holders

€ €

EKS

FileHeader SndgInst BankB_BIC

RcvgInst LACBLV2X

GrpHdr InstgAgt BankB_BIC

InstdAgt

CdtTrfTxInf InstgAgt

CdtrAgt BankD_BIC

FileHeader SndgInst

RcvgInst BankC_BIC

GrpHdr InstgAgt

InstdAgt BankC_BIC

CdtTrfTxInf InstgAgt BankB_BIC

CdtrAgt BankD_BIC

BankB_BIC

BankA_BIC

BankC_BIC

BankD_BIC

LACBLV2X

€ €

4.5.4. Use of fields in a rejection message

€

BankA_BIC

EKS


RcvgInst LACBLV2X


InstdAgt



RcvgInst BankA_BIC

GrpHdr InstgAgt

InstdAgt

CdtTrfTxInf InstgAgtCdtrAgt

10

4.5.5. Use of fields in a SEPA payment return message

In a SEPA payment return message, the BIC of the original payment message beneficiary

shall be indicated in field <CdtrAgt>.

€

BankB_BIC

€

BankA_BIC

EKS

FileHeader SndgInst BankB_BIC

RcvgInst LACBLV2X

GrpHdr InstgAgt BankB_BIC

InstdAgt



RcvgInst BankA_BIC

GrpHdr InstgAgt

InstdAgt BankA_BIC


4.5.6. Use of fields in a SEPA credit transfer message where the message recipient is

reachable via STEP2

€

BankC_BIC

€

BankA_BIC

EKS


RcvgInst LACBLV2X


InstdAgt

CdtTrfTxInf InstgAgtCdtrAgt BankC_BIC

FileHeader SndgInst STEP2_BIC

RcvgInst BankC_BIC

GrpHdr InstgAgt

InstdAgt BankC_BIC

CdtTrfTxInf InstgAgt LACBLV2X

CdtrAgt BankC_BIC

STEP2


RcvgInst STEP2_BIC

GrpHdr InstgAgt LACBLV2X

InstdAgt

CdtTrfTxInf InstgAgtCdtrAgt BankC_BIC

11

4.6. XML file header

File header shall be included into those files where the file type is envisaged for sending

multiple messages, i.e. PE type files, VE type files, UE type files, IE type files, OE type

files, QE type files, FE type files and ME type files. A header shall be included in the ME

files only if they contain pacs.002.001.03 messages.

4.6.1. Header of the PE file to be sent to the clearing service No. Status1 Element name XML element Format2 Description

1. M Sender SndgInst 4!a2!a2!

c

The BIC of the file sender.

2. M Recipient RcvgInst 4!a2!a2!

c

BIC of Latvijas Banka

(LACBLV2X)

3. M File reference FileRef 16!c File reference.

4. M Service identifier SrvcId 3!a Only code "SCT" is allowed.

5. M Test code TstCode 1!a Only code "T" in test environment

or code "P" in production

environment is allowed.

6. M File type FType 3!a Only code "ICF" is allowed.

7. M File date and

time

FDtTm ISODate

Time

Date and time of file creation.

8. M Number of

pacs.008 bulks

NumCTBlk 8n Number of SEPA credit transfer

message bulks in the file.

9. M Number of

camt.056 bulks

NumPCRBlk 8n Number of SEPA payment

cancellation request message bulks

in the file.

10. M Number of

pacs.004 bulks

NumRFRBlk 8n Number of SEPA payment return


11. M Number of

camt.029 bulks

NumROIBlk 8n Number of negative response to

payment cancellation request


12. M Number of

pacs.028 bulks

NumSRBlk 8n Number of Status request message

bulks in the file. 1The indicators used for presenting fields hereinafter are as follows:

M – mandatory,

O – optional. 2 The indicators used for field formats hereinafter are as follows:

n – numbers (from 0 to 9),

a – capital letters of the Latin alphabet (from A to Z),

c – capital letters of the Latin alphabet and numbers,

x – any character compliant with the requirements of Paragraph 4.2 herein.

Field length indicators:

nn – maximum field length (minimum is 1),

nn! – fixed field length, e.g. 3!.

Date and time indicators:

ISODate – YYYY-MM-DD,

ISODateTime – YYYY-MM-DDThh:mm:ss (part Thh:mm:ss is optional).

4.6.2. Header of the PE type file generated by the clearing service No. Status Element name XML element Format Description

1. M Sender SndgInst 4!a2!a2!c The BIC of Latvijas Banka

(LACBLV2X).

2. M Recipient RcvgInst 4!a2!a2!c The BIC of the file recipient.

3. M Service identifier SrvcId 3!a Only code "SCT" is used.

4. M Test code TstCode 1!a Only code "T" in test environment

or code "P" in production

environment is used.

5. M File type FType 3!a Only code "SCF" is used.


12

7. M Routing indicator RoutingInd 3!a Only code "ALL" is used.

8. M File value date FileBusDt ISODate File value date.

9. M File cycle number FileCycleNo 2!n The cycle in which this file was

created by the clearing service.

4.6.3. VE type file header No. Status Element name XML element Format Description


(LACBLV2X).



4. M Test code TstCode 1!a Only code "T" in test

environment or code "P" in

production environment is

used.

5. M File type FType 3!a Only code "CVF" is used.


7. M File date and time FileDtTm ISODateTime Date and time of file

creation.

8. O Original file

reference

OrigFRef 16c Original file reference

9. M Original file name OrigFName 32x Original file name.

10. O Original date and

time

OrigDtTm ISODateTime Date and time of original file

creation.

11. M File acceptance or

rejection reason

FileRjctRsn 3!c Only listed codes are used

(Table 13).


13. M File cycle number FileCycleNo 2!n The cycle in which the file

was created.

4.6.4. IE type file header No. Status Element name XML element Format Description

1. M Sender SndgInst 4!a2!a2!c The BIC of the file sender.

2. M Recipient RcvgInst 4!a2!a2!c The BIC of Latvijas Banka

(LACBLV2X)

3. M File reference FileRef 16!c File reference

4. M Service identifier SrvcId 3!a Only code "SCT" is

allowed.




allowed.

6. M File type FType 3!a Only code "IQF" is allowed.

7. M File date and time FDtTm ISODateTime Date and time of file

creation.

8. M Number of

camt.027 bulks

NumCNRBlk 8n Number of SEPA claim of

non-receipt message bulks

in the file.

9. M Number of

camt.087 bulks

NumRMPBlk 8n Number of SEPA claim for

value date correction


10. M Number of

camt.029 bulks

NumROQBlk 8n Number of SEPA resolution

of investigation (response to

the investigation request)


11. M Number of pacs.028

bulks

NumSRBlk 8n Number of status request


13

4.6.5. OE type file header No. Status Element name XML element Format Description


(LACBLV2X).






used.

5. M File type FType 3!a Only code "OQF" is used.


7. M Routing indicator RoutingInd 3!a Only code "ALL" is used.


9. M File cycle number FileCycleNo 2!n The cycle in which this file

was created.

4.6.6. QE type file header No. Status Element name XML element Format Description


(LACBLV2X).






used.

5. M File type FType 3!a Only code "QVF" is used.


7. M File value date FileDtTm ISODateTime Date and time of file

creation.

8. O Original file

reference

OrigFRef 16c Original file reference

9. M Original file name OrigFName 32x Original IQF file name.

10. O Original date and

time

OrigDtTm ISODateTime Date and time of original file

creation.

11. M File acceptance or

rejection reason

FileRjctRsn 3!c Only listed codes are used

(Table 13).



was created.

4.6.7. UE type file header No. Sta

tus

Element name XML element Format Description

1. O Sender SndgInst 4!a2!a2!c The BIC of Latvijas Banka

(LACBLV2X).

2. O Recipient RcvgInst 4!a2!a2!c The BIC of the file

recipient.

3. O Service identifier SrvcId 3!a Only code "SCT" is used.

4. O Test code TstCode 1!a Only code "T" in test



used.

5. O File type FType 3!a Only code "CCF" is used.

6. O File reference FileRef 16c File reference.

14

7. O File date and time FileDtTm ISODateTime Date and time of file

creation.

8. O File value date FileBusDt ISODate File value date.

9. O File Cycle Number FileCycleNo 2!n The cycle in which the file

was created.

4.6.8. FE type file header No. Status Element name XML element Format Description

1. O Sender SndgInst 4!a2!a2!c The BIC of Latvijas Banka

(LACBLV2X).

2. O Recipient RcvgInst 4!a2!a2!c The BIC of the file

recipient.

3. O Service identifier SrvcId 3!a Only code "SCT" is used.

4. O Test code TstCode 1!a Only code "T" in test



used.

5. O File type FType 3!a Only code "PCF" is used.

6. O File reference FileRef 16c File reference.

7. O File date and time FileDtTm ISODateTime Date and time of file

creation.

8. O File value date FileBusDt ISODate File value date.

9. O File cycle number FileCycleNo 2!n The cycle in which the file

was created.

4.6.9. ME type file header No. Status Element name XML element Format Description


(LACBLV2X).






used.

5. M File type FType 3!a Only code "RCF" is used.

6. M File reference FileRef 16c File reference.

7. M File date and time FileDtTm ISODateTime Date and time of file

creation.



was created.

15

5. Generating bulk headers and messages

5.1. SEPA credit transfer message

A SEPA credit transfer message shall be generated in accordance with ISO 20022 pacs.008.001.02 message rules and included into the PE

type file.

5.1.1. Bulk header

ISO

number

Usage1 Element Description Link 22

Notes

1.0 [1..1] └┬ <GrpHdr>

│

SEPA credit transfer message bulk

information

1.1 [1..1] ├─ <MsgId> Bulk identifier X

1.2 [1..1] ├─ <CreDtTm> Date and time of bulk creation X

1.4 [1..1] ├─ <NbOfTxs>

│

Number of SEPA credit transfer

messages in the bulk

X Must be equal to the actual number of all

SEPA credit transfer messages in the bulk.

1.6 [1..1] ├─ <TtlIntrBkSttlmAmt>

│

Amount of SEPA credit transfer


X Must be equal to the total amount of all

SEPA credit transfer messages in the bulk.

1.7 [1..1] ├─ <IntrBkSttlmDt> Value date X

1.8 [1..1] ├┬ <SttlmInf>

1.9 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

1.11 [1..1] │└┬ <ClrSys>

1.13 [1..1] │ └─ <Prtry> Clearing system proprietary code X Only code "EKS" is allowed.

1.32 [0..1] ├┬ <InstgAgt>

││

││

Bulk sender Must be used in the files to be sent to the

clearing service. Is not used in the files

generated by the clearing service.

6.1.0 [1..1] │└┬ <FinInstnId>

6.1.1 [1..1] │ └─ <BIC> The BIC of the bulk sender X

1.33 [0..1] └┬ <InstdAgt>

│

│

Bulk recipient Used in the files generated by the clearing

service. Not allowed in the files to be sent to

the clearing service.

6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> The BIC of the bulk recipient X

1 The use hereinafter only refers to the specific element; subordinate elements (also mandatory) must only be used if a superior element is used.

[0..1] – element is optional but may be used no more than once;

16

[1..1] – the use of one such element is mandatory;

[1..n] – one or several such elements must be used:

{Or/Or} – the use of one of the two elements is mandatory. 2 The formats are described in Paragraph 5.14 herein in accordance with the ISO number and the message type.

5.1.2. SEPA credit transfer message structure

ISO

number

Usage Element Description Link Notes

2.0 [1..n] └┬ <CdtTrfTxInf>

│

SEPA credit transfer message

information

At least one message should be included

in a bulk.

2.1 [1..1] ├┬ <PmtId> Payment identification

2.2 [0..1] │├─ <InstrId> Instruction identifier X Assigned by the instructing agent (bulk

sender).

2.3 [1..1] │├─ <EndToEndId>

││

Identifier assigned by the debtor X Where it is not available, only value

"NOTPROVIDED" is allowed.

2.4 [1..1] │└─ <TxId> Message identifier X Assigned by the agent holding the

debtor's account.

2.6 [1..1] ├┬ <PmtTpInf> Payment type information Mandatory in each message.

2.9 [1..1] │├┬ <SvcLvl> Service level Mandatory.

2.10 [1..1] ││└─ <Cd> Code X Only code "SEPA" is allowed.

2.12 [0..1] │├┬ <LclInstrm>

│││

User community specific instrument

information

Only used if bilaterally agreed between

the debtor agent and the creditor agent.

2.13 {Or ││├─ <Cd>

│││

│││

X Only ISO 20022 codes are allowed

(Table 1). Cannot be used at the same

time as 2.14.

2.14 Or} ││└─ <Prtry> X Cannot be used at the same time as 2.13.

2.15 [0..1] │└┬ <CtgyPurp> Category purpose

2.16 {Or │ ├─ <Cd>

│ │

│ │



time as 2.17.

2.17 Or} │ └─ <Prtry> X Cannot be used at the same time as 2.16.

2.18 [1..1] ├─ <IntrBkSttlmAmt> Interbank settlement amount X

2.33 [1..1] ├─ <ChrgBr> Charge bearer X Only code "SLEV" is allowed.

2.39 [0..1] ├┬ <InstgAgt>

││

││

Instructing agent Used in the files generated by the clearing

service. Not allowed in the files to be sent

to the clearing service.

17

││

││

6.1.0 [1..1] │└┬ <FinInstnId> Financial institution identification

6.1.1 [1..1] │ └─ <BIC> BIC X Only BIC is allowed.

2.47 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

9.1.0 [0..1] │├─ <Nm> Name X

9.1.12 [0..1] │└┬ <Id> Ultimate debtor identification

9.1.13 {Or │ ├┬ <OrgId> Organisation identification Cannot be used at the same time as

9.1.21.

9.1.14 {Or │ │├─ <BICOrBEI> BIC or BEI X Cannot be used at the same time as

9.1.15.

9.1.15 Or} │ │└┬ <Othr> Other type of identification Cannot be used at the same time as

9.1.14.

9.1.16 [1..1] │ │ ├─ <Id> Identifier X

9.1.17 [0..1] │ │ ├┬ <SchmeNm> Scheme name

9.1.18 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││

Scheme name code X Only ISO 20022 codes are allowed


time as 9.1.19.

9.1.19 Or} │ │ │└─ <Prtry> Scheme name X Cannot be used at the same time as

9.1.18.

9.1.20 [0..1] │ │ └─ <Issr> Issuer of identifier X

9.1.21 Or} │ └┬ <PrvtId> Natural person identification Cannot be used at the same time as

9.1.13.

9.1.22 {Or │ ├┬ <DtAndPlcOfBirth> Date and place of birth Cannot be used at the same time as

9.1.27.

9.1.23 [1..1] │ │├─ <BirthDt> Date of birth X

9.1.24 [0..1] │ │├─ <PrvcOfBirth> Province of birth X

9.1.25 [1..1] │ │├─ <CityOfBirth> City of birth X

9.1.26 [1..1] │ │└─ <CtryOfBirth>

│ │

Country of birth X Only ISO 3166 Alpha-2 codes are

allowed.

9.1.27 Or} │ └┬ <Othr> Other type of identification Cannot be used at the same time as

9.1.22.

9.1.28 [1..1] │ ├─ <Id> Identifier X

9.1.29 [0..1] │ ├┬ <SchmeNm> Scheme name

18

9.1.30 {Or │ │├─ <Cd>

│ ││

│ ││



time as 9.1.31.

9.1.31 Or} │ │└─ <Prtry> Scheme name X Cannot be used at the same time as

9.1.30.

9.1.32 [0..1] │ └─ <Issr> Issuer of identifier X

2.49 [1..1] ├┬ <Dbtr> Debtor

9.1.0 [1..1] │├─ <Nm> Debtor name X Mandatory.

9.1.1 [0..1] │├┬ <PstlAdr> Address

9.1.10 [0..1] ││├─ <Ctry>

│││

Country X Only ISO 3166 Alpha-2 codes are

allowed.

9.1.11 [0..2] ││└─ <AdrLine>

││

Address line X No more than two occurrences of the

element are allowed.

9.1.12 [0..1] │└┬ <Id> Debtor identification


9.1.21.


9.1.15.


9.1.14.

9.1.16 [1..1] │ │ ├─ <Id> Identifier X


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



time as 9.1.19.


9.1.18.



9.1.13.

9.1.22 {Or │ ├┬ <DtAndPlcOf

│ ││ Birth>

Date and place of birth Cannot be used at the same time as

9.1.27.




19

9.1.26 [1..1] │ │└─ <CtryOfBirth>

│ │

Country of birth X Only ISO 3166 Alpha-2 codes are

allowed.


9.1.22.

9.1.28 [1..1] │ ├─ <Id> Identifier X


9.1.30 {Or │ │├─ <Cd>

│ ││

│ ││



time as 9.1.31.


9.1.30.


2.50 [1..1] ├┬ <DbtrAcct> Debtor account Mandatory.

1.1.0 [1..1] │└┬ <Id> Debtor account identification

1.1.1 [1..1] │ └─ <IBAN> IBAN X

2.51 [1..1] ├┬ <DbtrAgt> Debtor agent Only BIC is allowed.


6.1.1 [1..1] │ └─ <BIC>

│

BIC X The specified BIC shall be reachable

according to the routing table.

2.53 [1..1] ├┬ <CdtrAgt> Creditor agent Only BIC is allowed.


6.1.1 [1..1] │ └─ <BIC>

│

BIC X The specified BIC shall be reachable

according to the routing table.

2.55 [1..1] ├┬ <Cdtr> Creditor

9.1.0 [1..1] │├─ <Nm> Creditor name X Mandatory.


9.1.10 [0..1] ││├─ <Ctry>

│││

Country X Only ISO 3166 Alpha-2 codes are

allowed.

9.1.11 [0..2] ││└─ <AdrLine>

││

Address line X No more than two occurrences of the

element are allowed.

9.1.12 [0..1] │└┬ <Id> Identification


9.1.21.


9.1.15.

20


9.1.14.

9.1.16 [1..1] │ │ ├─ <Id> Identifier X


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││



time as 9.1.19.


9.1.18.



9.1.13.


│ ││ Birth>

Date and place of birth Cannot be used at the same time as

9.1.27.




9.1.26 [1..1] │ │└─ <CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are

allowed.


9.1.22.

9.1.28 [1..1] │ ├─ <Id> Identifier X


9.1.30 {Or │ │├─ <Cd>

│ ││



time as 9.1.31.


9.1.30.


2.56 [1..1] ├┬ <CdtrAcct> Creditor account Mandatory.

1.1.0 [1..1] │└┬ <Id>

│ │

Creditor account identification

1.1.1 [1..1] │ └─ <IBAN> IBAN X

2.57 [0..1] ├┬ <UltmtCdtr> Ultimate creditor

9.1.0 [0..1] │├─ <Nm> Name X

9.1.12 [0..1] │└┬ <Id> Ultimate creditor identification

21

9.1.13 {Or │ ├┬ <OrgId> Organisation identification Cannot be used at the same time as 9.1.21.

9.1.14 {Or │ │├─ <BICOrBEI> BIC or BEI X Cannot be used at the same time as 9.1.15.

9.1.15 Or} │ │└┬ <Othr> Other type of identification Cannot be used at the same time as 9.1.14.

9.1.16 [1..1] │ │ ├─ <Id> Identifier X


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││


(Table 3). Cannot be used at the same time

as 9.1.19.

9.1.19 Or} │ │ │└─ <Prtry> Scheme name X Cannot be used at the same time as 9.1.18.


9.1.21 Or} │ └┬ <PrvtId> Natural person identification Cannot be used at the same time as 9.1.13.

9.1.22 {Or │ ├┬ <DtAndPlcOfBirth> Date and place of birth Cannot be used at the same time as 9.1.27.




9.1.26 [1..1] │ │└─ <CtryOfBirth>

│ │

Country of birth X Only ISO 3166 Alpha-2 codes are allowed.

9.1.27 Or} │ └┬ <Othr> Other type of identification Cannot be used at the same time as 9.1.22.

9.1.28 [1..1] │ ├─ <Id> Identifier X


9.1.30 {Or │ │├─ <Cd>

│ ││

│ ││



as 9.1.31.

9.1.31 Or} │ │└─ <Prtry> Scheme name X Cannot be used at the same time as 9.1.30.


2.64 [0..1] ├┬ <Purp> Payment purpose

2.65 [1..1] │└─ <Cd> Payment purpose ISO code X Only ISO 20022 codes are allowed

(Table 5).

2.75 [0..1] └┬ <RmtInf> Remittance information Only 2.76 or 2.77 is allowed.

2.76 {Or ├─ <Ustrd> Unstructured X Cannot be used at the same time as 2.77.

2.77 Or} └┬ <Strd>

│

│

Structured Cannot be used at the same time as 2.76.

Only one element occurrence is allowed

with a maximum of 140 characters.

2.97 [0..1] └┬ <CdtrRefInf> Creditor reference information

2.98 [1..1] ├┬ <Tp>

││

Creditor reference information type Allowed to use only with 2.103.

22

2.99 [1..1] │├┬ <CdOrPrtry>

2.100 [1..1] ││└─ <Cd>

││

Creditor reference information type

code

X Only code "SCOR" is allowed.

2.102 [0..1] │└─ <Issr>

│

Issuer of creditor reference

information type

X

2.103 [1..1] └─ <Ref> Reference assigned by the creditor X Allowed to use only with 2.98.

5.2. SEPA payment return message

A SEPA payment return message shall be generated in accordance with ISO 20022 pacs. 004.001.02 message rules and included into the PE

type file.

5.2.1. Bulk header

ISO

number

Usag

e

Element Description Link Notes

1.0 [1..1] └┬ <GrpHdr>

│

SEPA payment return message bulk

information

1.1 [1..1] ├─ <MsgId> Bulk identifier X

1.2 [1..1] ├─ <CreDtTm> Date and time of bulk creation X

1.7 [1..1] ├─ <NbOfTxs>

│

Number of SEPA payment return


X Must be equal to the actual number of all SEPA

payment return messages in the bulk.

1.10 [1..1] ├─ <TtlRtrdIntr

│ BkSttlmAmt>

Amount of SEPA payment return


X Must be equal to the total amount of all SEPA

payment return messages in the bulk.


1.12 [1..1] ├┬ <SttlmInf>

1.13 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

1.15 [1..1] │└┬ <ClrSys>

1.17 [1..1] │ └─ <Prtry> Clearing system proprietary code X Only code "EKS" is allowed.

1.24 [0..1] ├┬ <InstgAgt>

││

││

Bulk sender Must be indicated in the files to be sent to the

clearing service. Is not used in the files generated by


6.1.0 [1..1] │└┬ <FinInstnId>


23

1.25 [0..1] └┬ <InstdAgt>

│

│

Bulk recipient Used in the files generated by the clearing service.

Not allowed in the files to be sent to the clearing

service.

6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> The BIC of the bulk recipient X

5.2.2. SEPA payment return message structure

ISO

number


3.0 [1..n] └┬ <TxInf> Message information

3.1 [1..1] ├─ <RtrId>

│

SEPA payment return message

identifier

X

3.2 [1..1] ├┬ <OrgnlGrpInf> Information on the original bulk

3.3 [1..1] │├─ <OrgnlMsgId> Message identifier of the original bulk X

3.4 [1..1] │└─ <OrgnlMsgNmId>

│

│

│

Type of messages in the original bulk X Only code "pacs.008" is allowed in the files to be sent

to the clearing service. Codes "pacs.008" and

"pacs.004" are used in the files generated by the

clearing service.

3.6 [0..1] ├─ <OrgnlInstrId> Original instruction identifier X

3.7 [1..1] ├─ <OrgnlEndToEndId>

│

Original identifierassigned by the

debtor

X

3.8 [1..1] ├─ <OrgnlTxId>

│

Original message identifier X If pacs.004 is returned, the value <RtrId> from the

message to be returned.

3.10 [1..1] ├─ <OrgnlIntrBk

│ SttlmAmt>

Amount of the original message X

3.11 [1..1] ├─ <RtrdIntrBk

│ SttlmAmt>

Returned interbank settlement amount X See the format notes.

3.13 [0..1] ├─ <RtrdInstdAmt>

│

Returned instructed amount before

deduction of charges

X Must be used if 3.17 is used; allowed only in a reply to

the cancellation request.

3.16 [0..1] ├─ <ChrgBr> Charge bearer X Only code "SLEV" is allowed.

3.17 [1..1] ├┬ <ChrgsInf>

││

Charges information Only allowed in messages responding to a SEPA

payment cancellation request.

3.18 [1..1] │├─ <Amt> Charged amount X

3.19 [1..1] │└┬ <Pty> Party deducting charges

6.1.0 [1..1] │ └┬ <FinInstnId>

24

6.1.1 [1..1] │ └─ <BIC> BIC X

3.20 [0..1] ├┬ <InstgAgt>

││

Instructing agent Used in the files generated by the clearing service. Not

allowed in the files to be sent to the clearing service.

6.1.0 [1..1] │└┬ <FinInstnId>


3.22 [1..1] ├┬ <RtrRsnInf> Return reason information

3.23 [1..1] │├┬ <Orgtr> Party originating the return

9.1.0 {Or ││├─ <Nm>

│││

Name of the party originating the

return where it is a customer

X Cannot be used at the same time as 9.1.12.

9.1.12 Or} ││└┬ <Id>

││ │

Party originating the return where it is

an agent

Cannot be used at the same time as 9.1.0.

9.1.13 [1..1] ││ └┬ <OrgId>

9.1.14 [1..1] ││ └─ <BICOrBEI>

││

The BIC of the party originating the

return

X

3.24 [1..1] │├┬ <Rsn> Return reason

3.25 [1..1] ││└─ <Cd> Return reason code X Only the listed codes are allowed (Table 6).

3.27 [0..1] │└─ <AddtlInf>

│

│

│

Additional information X Only allowed in messages responding to a SEPA

payment cancellation request. In this case it is

mandatory and shall be filled in with a reference to the

cancellation request message.

3.28 [1..1] └┬ <OrgnlTxRef>

│

Information on the original message


3.39 [1..1] ├┬ <SttlmInf>

3.40 [1..1] │└─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

3.51 [1..1] ├┬ <PmtTpInf>

3.54 [1..1] │├┬ <SvcLvl> Service level

3.55 [1..1] ││└─ <Cd> Code X Only code "SEPA" is allowed.

3.57 [0..1] │├┬ <LclInstrm>

│││


information

Only used if bilaterally agreed between the debtor

agent and the creditor agent.

3.58 {Or ││├─ <Cd>

│││

X Only ISO 20022 codes are allowed (Table 1). Cannot

be used at the same time as 3.59.

3.59 Or} ││└─ <Prtry> X Cannot be used at the same time as 3.58.

3.61 [0..1] │└┬ <CtgyPurp> Category purpose

3.62 {Or │ ├─ <Cd>

│ │

X Only ISO 20022 codes are allowed (Table 2). Cannot

be used at the same time as 3.63.

25

3.63 Or} │ └─ <Prtry> X Cannot be used at the same time as 3.62.

3.84 [1..1] ├┬ <RmtInf> Remittance information

3.85 {Or │├─ <Ustrd> Unstructured X Cannot be used at the same time as 3.86.

3.86 Or} │└┬ <Strd>

│ │

│ │

Structured Cannot be used at the same time as 3.85. Only one

element occurrence is allowed with a maximum of

140 characters.

3.106 [1..1] │ └┬ <CdtrRefInf> Creditor reference information

3.107 [1..1] │ ├┬ <Tp> Creditor reference information type Only allowed to use with 3.112.

3.108 [1..1] │ │├┬ <CdOrPrtry>

3.109 [1..1] │ ││└─ <Cd>

│ ││


type code


3.111 [0..1] │ │└─ <Issr> Issuer X Issuer of creditor reference information type.

3.112 [1..1] │ └─ <Ref> Reference assigned by the creditor X Only allowed to use with 3.107.

3.116 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

9.1.0 [0..1] │├─ <Nm> Name X





9.1.16 [1..1] │ │ ├─ <Id> Identifier X


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││

Scheme name code X Only ISO 20022 codes are allowed (Table 3). Cannot

be used at the same time as 9.1.19.





│ ││ Birth>

Date and place of birth Cannot be used at the same time as 9.1.27.




9.1.26 [1..1] │ │└─ <CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are allowed.


9.1.28 [1..1] │ ├─ <Id> Identifier X


26

9.1.30 {Or │ │├─ <Cd>

│ ││





3.117 [1..1] ├┬ <Dbtr> Debtor

9.1.0 [1..1] │├─ <Nm> Debtor name X


9.1.10 [0..1] ││├─ <Ctry> Country X Only ISO 3166 Alpha-2 codes are allowed.

9.1.11 [0..2] ││└─ <AdrLine> Address line X No more than two occurrences of the element are

allowed.



9.1.14 {Or │ │├─ <BICOrBEI> BIC or BEI X


9.1.16 [1..1] │ │ ├─ <Id> Identifier X Cannot be used at the same time as 9.1.14.


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







9.1.28 [1..1] │ ├─ <Id> Identifier X


9.1.30 {Or │ │├─ <Cd>

│ ││





3.118 [1..1] ├┬ <DbtrAcct> Debtor account Mandatory.


27

1.1.1 [1..1] │ └─ <IBAN> IBAN X

3.119 [1..1] ├┬ <DbtrAgt> Debtor agent Only BIC is allowed.


6.1.1 [1..1] │ └─ <BIC> BIC X

3.121 [1..1] ├┬ <CdtrAgt> Creditor agent Only BIC is allowed.


6.1.1 [1..1] │ └─ <BIC> BIC X

3.123 [1..1] ├┬ <Cdtr> Creditor




9.1.11 [0..2] ││└─ <AdrLine>

││

Address line X No more than two occurrences of the element are

allowed.

9.1.12 [0..1] │└┬ <Id> Creditor identification




9.1.16 [1..1] │ │ ├─ <Id> Identifier X


9.1.18 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







9.1.28 [1..1] │ ├─ <Id> Identifier X


9.1.30 {Or │ │├─ <Cd>

│ ││




28


3.124 [1..1] ├┬ <CdtrAcct> Creditor account Mandatory.

1.1.0 [1..1] │└┬ <Id> Creditor account identification

1.1.1 [1..1] │ └─ <IBAN> IBAN X

3.125 [0..1] └┬ <UltmtCdtr> Ultimate creditor

5.1.0 [0..1] ├─ <Nm> Name X

9.1.12 [0..1] └┬ <Id> Ultimate creditor identification

9.1.13 {Or ├┬ <OrgId> Organisation identification Cannot be used at the same time as 9.1.21.

9.1.14 {Or │├─ <BICOrBEI> BIC or BEI X Cannot be used at the same time as 9.1.15.

9.1.15 Or} │└┬ <Othr> Other type of identification Cannot be used at the same time as 9.1.14.

9.1.16 [1..1] │ ├─ <Id> Identifier X


9.1.18 {Or │ │├─ <Cd>

│ ││





9.1.21 Or} └┬ <PrvtId> Natural person identification Cannot be used at the same time as 9.1.13.

9.1.22 {Or ├┬ <DtAndPlcOf

││ Birth>


9.1.23 [1..1] │├─ <BirthDt> Date of birth X

9.1.24 [0..1] │├─ <PrvcOfBirth> Province of birth X

9.1.25 [1..1] │├─ <CityOfBirth> City of birth X

9.1.26 [1..1] │└─ <CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are allowed.

9.1.27 Or} └┬ <Othr> Other type of identification Cannot be used at the same time as 9.1.22.

9.1.28 [1..1] ├─ <Id> Identifier X

9.1.29 [0..1] ├┬ <SchmeNm> Scheme name

9.1.30 {Or │├─ <Cd>

││



9.1.31 Or} │└─ <Prtry> Scheme name X Cannot be used at the same time as 9.1.30.

9.1.32 [0..1] └─ <Issr> Issuer of identifier X

5.3. Status message

A status message shall be generated by the clearing service in accordance with ISO 20022 pacs.002.001.03 message rules and included into

the VE or QE type files. The status message shall be sent to a participant to inform it of the acceptance or rejection of its submitted message.

If the submitted PE or IE type file contains more than one message bulk, the status message is generated for each bulk.

29

5.3.1. Bulk header

ISO

number


1.0 [1..1] ├┬ <GrpHdr>

││

Status message bulk information

1.1 [1..1] │├─ <MsgId>

││

Status message bulk identifier X

1.2 [1..1] │└─ <CreDtTm> Date and time of bulk creation X

5.3.2. Payment status message structure

ISO

number


2.0 [1..1] ├┬ <OrgnlGrpInfAndSts>

2.1 [1..1] │├─ <OrgnlMsgId>

││

Message identifier of the original bulk X

2.2 [1..1] │├─ <OrgnlMsgNmId>

││

Type of messages in the original bulk X Only codes "pacs.008", "pacs.004", "camt.056",

"camt.029", "pacs.028", "camt.027" or "camt.087" are

used.

2.4 [1..1] │├─ <OrgnlNbOfTxs>

││

Number of messages in the original

bulk X

2.5 [1..1] │├─ <OrgnlCtrlSum>

││

Total amount of messages in the

original bulk X If 2.2 contains "camt.029", "pacs.028", "camt.027" or

"camt.087", "0" (zero) shall be used.

2.6 [1..1] │├─ <GrpSts>

││

Bulk status X "RJCT" (rejected), "PART" (partly accepted) and

"ACCP" (accepted).

2.7 [1..1] │├┬ <StsRsnInf> Status reason information

2.8 [1..1] ││├┬ < Orgtr> Status originator

9.1.12 [1..1] │││└┬ <Id>

9.1.13 [1..1] │││ └┬ <OrgId>

9.1.14 [1..1] │││ └─ <BICOrBEI> Status originator BIC X BIC of Latvijas Banka (LACBLV2XXXX).

2.9 [1..1] ││└┬ <Rsn> Reason for the bulk status

2.10 {Or ││ ├─ <Cd>

││ │

Reason for the status (ISO20022 error

code) X Only code "ED05" (settlement failed) is allowed.

Cannot be used at the same time as 2.11.

2.11 Or} ││ └─ <Prtry>

││

Reason for the status (clearing service

error code). X Only listed codes are used (Table 15). Cannot be used

at the same time as 2.10.

30

2.13 [0..1] │├┬ <NbOfTxsPerSts>

│││

Information on the accepted messages

in the bulk

Only to be used, if 2.6 contains the code "PART".

2.14 [1..1] ││├─ <DtldNbOfTxs>

│││

Number of accepted messages in the

bulk X

2.15 [1..1] ││├─ <DtldSts> Message status X Only code "ACCP" is allowed.

2.16 [1..1] ││└─ <DtldCtrlSum>

││

Amount of accepted messages in the

bulk X

2.13 [0..1] │└┬ <NbOfTxsPerSts>

│ │

Information on the rejected messages

in the bulk

Only to be used, if 2.6 contains the code "PART".

2.14 [1..1] │ ├─ <DtldNbOfTxs>

│ │

Number of rejected messages in the

bulk X

2.15 [1..1] │ ├─ <DtldSts> Message status X Only code "RJCT" is allowed.

2.16 [1..1] │ └─ <DtldCtrlSum>

│

Amount of rejected messages in the

bulk X

3.0 [0..n] └┬ <TxInfAndSts> Only to be used, if 2.6 contains the code "PART".

3.1 [1..1] ├─ <StsId>

│

Identifier of the message generated by

the clearing service X



│


debtor X

3.4 [1..1] ├─ <OrgnlTxId> Original message identifier X Identifier origin specific for each message type

(pacs.008 – <TxId>, pacs.004 – <RtrId>, camt.056 –

<CxlId>, camt.029.001.03 – <CxlStsId>,

camt.029.001.08 – <RslvdCase>/<Id>, pacs.028 –

<StsReqId>, camt.027- <Case><Id> , camt.087 –

<Case><Id>).

3.5 [1..1] ├─ <TxSts> Message status X Only code "RJCT" is used.

3.6 [1..1] ├┬ <StsRsnInf> Status reason information

3.7 [1..1] │├┬ <Orgtr> Status originator

9.1.12 [1..1] ││└┬ <Id>

9.1.13 [1..1] ││ └┬ <OrgId>

9.1.14 [1..1] ││ └─ <BICorBEI> Status originator BIC X BIC of Latvijas Banka (LACBLV2XXXX).

3.8 [1..1] │└┬ <Rsn> Reason for the status

3.9 {Or │ ├─ <Cd>

│ │

Reason for the status (ISO20022 error

code) X Only listed codes are allowed (Table 16). Cannot be

used at the same time as 3.10.

31

3.10 Or} │ └─ <Prtry>

│


error code) X Only listed codes are allowed (Table 17). Cannot be


3.20 [0..1] └┬ <OrgnlTxRef> Information on the original message

3.21 [1..1] ├─ <IntrBkSttlmAmt>

Amount X If 2.2 contains "camt.029", "pacs.028", "camt.027" or



3.109 [1..1] ├┬ <DbtrAgt> Debtor agent Debtor agent of the original message.

6.1.0 [1..1] │└┬ <FinInstnId>

6.1.1 [1..1] │ └─ <BIC> X

3.113 [1..1] └┬ <CdtrAgt> Creditor agent Creditor agent of the original message.

6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> X

5.4. Moved payment notification message

A moved payment notification message shall be generated by the clearing service in accordance with ISO 20022 pacs.002.001.03 message

rules. Only selected fields of the message are used to generate this message. The format of such message is not regulated by SEPA.

A moved payment notification message is sent to inform a participant that the SEPA credit transfer message or SEPA payment return message

submitted by it is moved to the next clearing cycle.

5.4.1. Bulk header

ISO

number


1.0 [1..1] ├┬ <GrpHdr>

││

Bulk information on moved payment

notification messages

1.1 [1..1] │├─ <MsgId>

││

Bulk identifier of moved payment

notification message X


32

5.4.2. Moved payment notification message structure

ISO

number




2.2 [1..1] │├─ <OrgnlMsgNmId> Type of messages in the original bulk X Only codes "pacs.008" and "pacs.004" are used.


││


bulk X


││


original bulk X

2.6 [1..1] │├─ <GrpSts> Bulk status X Only code "PDNG" is used.


2.8 [1..1] ││├┬ <Orgtr> Status originator

9.1.12 [1..1] │││└┬ <Id>

9.1.13 [1..1] │││ └┬ <OrgId>

9.1.14 [1..1] │││ └─ <BICOrBEI> Status originator BIC X BIC of Latvijas Banka (LACBLV2XXXX).


2.11 [1..1] ││ └─ <Prtry>

││

Reason for the bulk status (clearing

service error code). X Only listed codes are used (Table 18).


2.14 [1..1] │ ├─ <DtldNbOfTxs>

│ │

Number of messages moved to the

next clearing cycle X

2.15 [1..1] │ ├─ <DtldSts> Message status X Only code "PDNG" is used.

2.16 [1..1] │ └─ <DtldCtrlSum>

│

Amount of messages to the next

clearing cycle X

3.0 [0..n] └┬ <TxInfAndSts> Moved message information

3.1 [1..1] ├─ <StsId>

│


the clearing service X



│

Original identification assigned by the

debtor X


(pacs.008-<TxId>, pacs.004-<RtrId>).

3.5 [1..1] ├─ <TxSts> Message status X Only code "PDNG" is used.


33

3.7 [1..1] │├┬ <Orgtr> Status originator

9.1.12 [1..1] ││└┬ <Id>

9.1.13 [1..1] ││ └┬ <OrgId>

9.1.14 [1..1] ││ └─ <BICorBEI> Status originator BIC X


3.10 [1..1] │ └─ <Prtry>

│


error code) X Only listed codes are used (Table 18).


3.21 [1..1] ├─ <IntrBkSttlmAmt> Amount X


3.109 [1..1] └┬ <DbtrAgt> Debtor agent Debtor agent of the original message.

6.1.0 [1..1] ├┬ <FinInstnId>

6.1.1 [1..1] │└─ <BIC> X


6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> X

5.5. Excluded payment rejection message

An excluded payment rejection message shall be generated by the clearing service in accordance with ISO 20022 pacs.002.001.03 message

rules. Only selected fields of the message are used to generate this message. The format of such message is not regulated by SEPA. The

message shall be included in the UE type file.

An excluded payment rejection message shall be sent to inform a clearing service participant that the previously accepted SEPA credit transfer

message or SEPA payment return message submitted by the participant has been rejected as a result of a clearing cycle recalculation or due

to the exclusion of a participant or entity reachable via STEP2 from the clearing.

5.5.1. Bulk header

ISO

number


1.0 [1..1] ├┬ <GrpHdr> Bulk information

1.1 [1..1] │├─ <MsgId> Bulk identifier X


34

5.5.2. Excluded payment rejection message structure

ISO

number





││

Type of messages in the original bulk X Only codes "pacs.008", "pacs.004", "camt.056",

"camt.029", "pacs.028", "camt.027" or "camt.087" are

allowed.


││


bulk

X


││


original bulk

X If 2.2 contains "camt.029", "pacs.028", "camt.027" or


2.6 [1..1] │├─ <GrpSts> Bulk status X "RJCT" (rejected), "PART" (partly accepted).



9.1.12 [1..1] │││└┬ <Id>

9.1.13 [1..1] │││ └┬ <OrgId>

9.1.14 [1..1] │││ └─ <BICOrBEI> Status originator BIC X BIC of Latvijas Banka (LACBLV2XXXX)


2.11 [1..1] ││ └─ <Prtry>

││

Reason for the bulk status (clearing

service error code).

X Only listed codes are used (Table 19).


2.14 [1..1] │ ├─ <DtldNbOfTxs>

│ │


bulk

X

2.15 [1..1] │ ├─ <DtldSts> Message status X Only code "RJCT" is used.

2.16 [1..1] │ └─ <DtldCtrlSum>

│


bulk

X

3.0 [0..n] └┬ <TxInfAndSts>

3.1 [1..1] ├─ <StsId>

│


the clearing service

X



│


debtor

X


(pacs.008 – <TxId>, pacs.004 – <RtrId>, camt.056 –

35

<CxlId>, camt.029 – <CxlStsId>, pacs.028 –

<StsReqId>, camt.027 – <Case><Id> , camt.087 –

<Case><Id>).



3.7 [1..1] │├┬ <StsOrgtr> Status originator

9.1.12 [1..1] ││└┬ <Id>

9.1.13 [1..1] ││ └┬ <OrgId>

9.1.14 [1..1] ││ └─ <BICorBEI> Status originator BIC X BIC of Latvijas Banka (LACBLV2XXXX).


3.10 [1..1] │ └─ <Prtry>

│


error code)

X Only listed codes are used (Table 19).


3.21 [1..1] ├─ <IntrBkSttlmAmt> Amount X If 2.2 contains "camt.029", "pacs.028", "camt.027" or



3.109 [1..1] ├┬ <DbtrAgt> Debtor agent Debtor agent of the original payment.

6.1.0 [1..1] │└┬ <FinInstnId>

6.1.1 [1..1] │ └─ <BIC> X

3.113 [1..1] └┬ <CdtrAgt> Creditor agent Creditor agent of the original payment.

6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> X

5.6. Information message

The information message shall be generated by the clearing service in accordance with ISO 20022 pacs.002.001.03 message rules. Only

selected fields of the message are used to generate this message. The format of such message is not regulated by SEPA. The message shall

be included in the ME type file. The information message is sent to inform a participant that the previously accepted SEPA payment

cancellation request message, SEPA resolution of investigation (negative response to the cancellation request) message, status request

message, SEPA claim of non-receipt message, SEPA claim for value date correction message or SEPA resolution of investigation (response

to the investigation request) message submitted by the participant and addressed to a participant of another system cannot be delivered to the

addressee since the acceptance of the above message has been rejected by STEP2 or other SEPA payment system.

36

5.6.1. Bulk header

ISO

number


1.0 [1..1] ├┬ <GrpHdr> Bulk information

1.1 [1..1] │├─ <MsgId> Bulk identifier X


5.6.2. Information message structure

ISO

number





││

Type of messages in the original bulk X Only codes "camt.056", "camt.029",

"pacs.028","camt.027" or "camt.087" are used.


││


bulk

X

2.6 [1..1] │├─ <GrpSts> Bulk status X "RJCT" (rejected), "PART" (partly accepted).



9.1.12 [1..1] │││└┬ <Id>

9.1.13 [1..1] │││ └┬ <OrgId>

9.1.14 [1..1] │││ └─ <BICOrBEI>

│││

Status originator BIC X BIC of STEP2 or another SEPA payment system.


2.11 [1..1] ││ └─ <Prtry>

││

Reason code for the bulk status

(clearing service error code)

X Only code "XT99" is used.


2.14 [1..1] │ ├─ <DtldNbOfTxs>

│ │


bulk

X

2.15 [1..1] │ ├─ <DtldSts> Message status X Only code "RJCT" is used.

2.16 [1..1] │ └─ <DtldCtrlSum>

│


bulk

X

3.0 [0..n] └┬ <TxInfAndSts>

37

3.1 [1..1] ├─ <StsId>

│


the clearing service

X

3.4 [1..1] ├─ <OrgnlTxId>

│

│

│

Original message identifier X Identifier origin specific for each message type

(camt.056 – <CxlId>,camt.029.001.03 –

<CxlStsId>, camt.029.001.08 -

<RslvdCase>/<Id>, pacs.028 – <StsReqId>,

camt.027- <Case><Id> , camt.087-<Case><Id>).



3.7 [1..1] │├┬ <StsOrgtr> Status originator

9.1.12 [1..1] ││└┬ <Id>

9.1.13 [1..1] ││ └┬ <OrgId>

9.1.14 [1..1] ││ └─ <BICorBEI> Status originator BIC X BIC of STEP2 or another SEPA payment system.


3.10 [1..1] │ └─ <Prtry>

│

Reason code for the status (clearing

service error code)

X Only code "XT99" is used.


3.21 [1..1] ├─ <IntrBkSttlmAmt> Amount X


3.109 [1..1] ├┬ <DbtrAgt> Debtor agent Debtor agent of the original message.

6.1.0 [1..1] │└┬ <FinInstnId>

6.1.1 [1..1] │ └─ <BIC> X


6.1.0 [1..1] └┬ <FinInstnId>

6.1.1 [1..1] └─ <BIC> X

5.7. SEPA payment cancellation request message

A SEPA payment cancellation request message shall be generated in accordance with ISO 20022 camt.056.001.01 message rules and included

into the PE type file. A SEPA payment cancellation request message shall be sent to inform a participant about a request to return a previously

settled SEPA credit transfer, indicating the relevant details in the message.

38

5.7.1. Bulk header

ISO

number


1.0 [1..1] └┬ <Assgnmt>

1.1 [1..1] ├─ <Id>

│

SEPA payment cancellation request

message bulk identifier

X

1.2 [1..1] ├┬ <Assgnr>

││

││

││

Instructing agent of SEPA payment

cancellation request message bulk

The files to be sent to the clearing service shall

contain the BIC of the bulk sender; the files

generated by the clearing service the BIC of

Latvijas Banka (LACBLV2XXXX) is indicated.

1.4 [1..1] │└┬ <Agt>

2.1.0 [1..1] │ └┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X

1.5 [1..1] ├┬ <Assgne>

││

││

││


message bulk recipient


contain the BIC of Latvijas Banka

(LACBLV2XXXX); the files received from the

clearing indicate the BIC of the bulk recipient.

1.7 [1..1] │└┬ <Agt>

2.1.0 [1..1] │ └┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X

1.8 [1..1] └─ <CreDtTm> Date and time of bulk creation X

5.7.2. Control data

ISO

number


3.0 [1..1] └┬ <CtrlData>

3.1 [1..1] └─ <NbOfTxs> Total number of payment cancellations X

5.7.3. SEPA payment cancellation request message structure

ISO

number


4.0 [1..1] └┬ <Undrlyg>

│

Copy of the message to be requested

for cancellation

At least one message must be present.

39

4.21 [1..n] └┬ <TxInf>

│

Message information Copy of the message to be requested for

cancellation.

4.22 [1..1] ├─ <CxlId>

│


message identifier

X

4.29 [1..1] ├┬ <OrgnlGrpInf>

││

Information on the original bulk

4.30 [1..1] │├─ <OrgnlMsgId>

││

Message identifier of the original bulk X

4.31 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original bulk X Only code "pacs.008" is allowed.

4.33 [0..1] ├─ <OrgnlInstrId>

│

Original instruction identifier X


│


debtor

X

4.35 [1..1] ├─ <OrgnlTxId> Original message identifier X

4.37 [1..1] ├─<OrgnlIntrBk

│ SttlmAmt>


4.38 [1..1] ├─<OrgnlIntrBk

│ SttlmDt>

Value date of the original message X

4.39 [0..1] ├┬ <Assgnr>

││

││

││

Instructing agent of SEPA payment

cancellation request message

Not allowed to be used in the files to be sent to the

clearing service. The files generated by the clearing

service indicate the entity submitting this

instruction to the clearing service.

2.1.0 [1..1] │└┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X

4.41 [1..1] ├┬ <CxlRsnInf>

││

Cancellation request reason

information

4.42 [1..1] │├┬ <Orgtr>

│││

Party originating the request for

cancellation

5.1.0 {Or ││├─ <Nm>

│││

│││

Name of the party originating the

request for cancellation where its is a

customer

X Cannot be used at the same time as 5.1.12. Must be

indicated if 4.44 contains value "CUST" or 4.45

contains values "AM09" or "AC03".

5.1.12 Or} ││└┬ <Id>

││ │

Party originating the request for

cancellationwhere it is a debtor agent


5.1.13 [1..1] ││ └┬ <OrgId>

5.1.14 [1..1] ││ └─ <BICOrBEI>

││

The BIC of the party originating the

request for cancellation

X

40

4.43 [1..1] │├┬ <Rsn>

│││

Cancellation request reason

information

4.44 {Or ││├─ <Cd>

│││

│││

Cancellation reason ISO code X Only codes "DUPL" (duplicate payment) or

"CUST" (debtor initiated cancellation) are allowed.


4.45 Or} ││└─ <Prtry>

││

Cancellation reason proprietary code X Only listed codes are allowed (Table 7). Cannot be


4.46 [0..1] │└─ <AddtlInf>

│

Additional Information X Only allowed when 4.44 contains value "CUST" or

4.45 contains value "FRAD", "AM09" or "AC03".


6.1.52 [1..1] ├┬ <SttlmInf>

6.1.53 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

6.1.68 [1..1] │└┬ <ClrSys>

6.1.70 [1..1] │ └─ <Prtry>

│

Proprietary identification of the

clearing system

X Only code "EKS" is allowed.

6.1.233 [1..1] ├┬ <PmtTpInf>

6.1.236 [1..1] │├┬ <SvcLvl>

6.1.237 [1..1] ││└─ <Cd> Service level code X Only code "SEPA" is allowed.

6.1.239 [0..1] │├┬ <LclInstrm>

│││


information

6.1.240 {Or ││├─ <Cd>

│││

X Only ISO 20022 codes are allowed (Table 1).


6.1.241 Or} ││└─ <Prtry> X Cannot be used at the same time as 6.1.240.

6.1.243 [0..1] │└┬ <CtgyPurp> Category purpose

6.1.244 {Or │ ├─ <Cd>

│ │



6.1.245 Or} │ └─ <Prtry> X Cannot be used at the same time as 6.1.244.

6.1.467 [0..1] ├┬ <RmtInf> Remittance information

6.1.468 {Or │├─ <Ustrd> Unstructured X Cannot be used at the same time as 6.1.469.

6.1.469 Or} │└┬ <Strd>

│ │

│ │

Structured Cannot be used at the same time as 6.1.468. Only

one element occurrence is allowed with a

maximum of 140 characters.

6.1.489 [0..1] │ └┬ <CdtrRefInf> Creditor reference information

6.1.490 [1..1] │ ├┬ <Tp> Creditor reference information type When used, 6.1.495 must be present.

6.1.491 [1..1] │ │├┬ <CdOrPrtry>

41

6.1.492 [1..1] │ ││└─ <Cd>

│ ││


code


6.1.494 [0..1] │ │└─ <Issr>

│ │


information type

X

6.1.495 [1..1] │ └─ <Ref> Reference assigned by the creditor X When used, 6.1.490 must be present.

6.1.583 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

6.1.584 [0..1] │├─ <Nm> Name X





6.1.600 [1..1] │ │ ├─ <Id> Identifier X


6.1.602 {Or │ │ │├─ <Cd>

│ │ ││

Scheme name code X Only ISO 20022 codes are allowed (Table 3).






│ ││ Birth>







6.1.612 [1..1] │ ├─ <Id> Identifier X


6.1.614 {Or │ │├─ <Cd>

│ ││





6.1.626 [1..1] ├┬ <Dbtr> Debtor


6.1.628 [0..1] │├┬ <PstlAdr> Address


42

6.1.638 [0..2] ││└─ <AdrLine>

││


allowed.





6.1.643 [1..1] │ │ ├─ <Id> Identifier X


6.1.645 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







6.1.655 [1..1] │ ├─ <Id> Identifier X


6.1.657 {Or │ │├─ <Cd>

│ ││





6.1.669 [1..1] ├┬ <DbtrAcct> Debtor account Mandatory.


6.1.671 [1..1] │ └─ <IBAN> IBAN X

6.1.683 [1..1] ├┬ <DbtrAgt> Debtor agent Only BIC is allowed.


6.1.685 [1..1] │ └─ <BIC>

│

BIC X The specified BIC shall be reachable according to

the routing table.

6.1.737 [1..1] ├┬ <CdtrAgt> Creditor agent Only BIC is allowed.


43

6.1.739 [1..1] │ └─ <BIC>

│


the routing table.

6.1.791 [1..1] ├┬ <Cdtr> Creditor


6.1.793 [0..1] │├┬ <PstlAdr> Address


6.1.803 [0..2] ││└─ <AdrLine>

││


allowed.





6.1.808 [1..1] │ │ ├─ <Id> Identifier X


6.1.810 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







6.1.820 [1..1] │ ├─ <Id> Identifier X


6.1.822 {Or │ │├─ <Cd>

│ ││





6.1.834 [1..1] ├┬ <CdtrAcct> Creditor account Mandatory.


6.1.836 [1..1] │ └─ <IBAN> IBAN X

6.1.848 [0..1] └┬ <UltmtCdtr> Ultimate creditor

44

6.1.849 [0..1] ├─ <Nm> Name X





6.1.865 [1..1] │ ├─ <Id> Identifier X


6.1.867 {Or │ │├─ <Cd>

│ ││







││ Birth>







9.1.28 [1..1] ├─ <Id> Identifier X


9.1.30 {Or │├─ <Cd>

││





5.8. SEPA resolution of investigation (negative response to the cancellation request) message

A SEPA resolution of investigation (negative response to the cancellation request) message shall be generated in accordance with ISO 20022

camt.029.001.03 message rules and included into the PE type file. SEPA resolution of investigation (negative response to the cancellation

request) message shall be sent to inform a participant that the requested return of the SEPA credit transfer is not possible.

45

5.8.1. Bulk header

ISO

number


1.0 [1..1] └┬ <Assgnmt>

1.1 [1..1] ├─ <Id>

│

SEPA resolution of investigation

(negative response to the cancellation

request) message bulk identifier

X

1.2 [1..1] ├┬ <Assgnr>

││

││

││

Instructing agent of SEPA resolution

of investigation (negative response to

the cancellation request) message bulk


contain the BIC of the bulk sender; the files

generated by the clearing service contain the BIC

of Latvijas Banka (LACBLV2XXXX).

1.4 [1..1] │└┬ <Agt>

2.1.0 [1..1] │ └┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X

1.5 [1..1] ├┬ <Assgne>

││

││

││

││



request) message bulk recipient



(LACBLV2XXXX); the files generated by the

clearing service contain the BIC of the bulk

recipient.

1.7 [1..1] │└┬ <Agt>

2.1.0 [1..1] │ └┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X

1.8 [1..1] └─ <CreDtTm> Date and time of bulk creation X

5.8.2. Status data

ISO

number


3.0 [1..1] └┬ <Sts>

3.1 [1..1] └─ <Conf> Resolution of investigation status code X Only code "RJCR" is allowed.

46

5.8.3. SEPA resolution of investigation (negative response to the cancellation request) message structure

ISO

number


4.0 [1..1] └┬ <CxlDtls>

│



request) message information

At least one message must be present.

4.72 [1..n] └┬ <TxInfAndSts> Message information

4.73 [1..1] ├─ <CxlStsId>

│



request) message identifier

X

4.80 [1..1] ├┬ <OrgnlGrpInf> Information on the original bulk


4.82 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original bulk X Only code "pacs.008" is allowed.



│


debtor

X

4.86 [1..1] ├─ <OrgnlTxId> Original message identifier X

4.88 [1..1] ├─ <TxCxlSts> Message cancellation status X Only code "RJCR" is allowed.

4.89 [1..1] ├┬ <CxlStsRsnInf> Cancellation reason information

4.90 [1..1] │├┬ <Orgtr> Cancellation request originator

5.1.0 {Or ││├─ <Nm>

│││

│││

Where the originator is a debtor, the

name of the debtor originating the

cancellation request

X Cannot be used at the same time as 5.1.12.

5.1.12 Or} ││└┬ <Id>

││ │

││ │

Where the originator is a debtor agent,

identifier of the debtor agent

originating the cancellation request


5.1.13 [1..1] ││ └┬ <OrgId>

5.1.14 [1..1] ││ └─ <BICOrBEI>

││

BIC of the cancellation request

originator

X

4.91 [1..1] │├┬ <Rsn> Cancellation reason information

4.92 {Or ││├─ <Cd>

│││

Cancellation reason code X Only ISO 20022 codes are allowed (Table 8).


4.93 Or} ││└─ <Prtry>

││

X Only the listed codes are allowed (Table 9).


47

4.94 [0..2] │└─ <AddtlInf>

│

│

Additional information X Only allowed to be used where 4.92 is "LEGL" or

4.93 is "ARDT", "AM04" or "NOAS", to further

specify the reason.

4.101 [0..1] ├┬ <Assgnr>

││

││

││

││


of investigation (negative response to

the cancellation request) message

Not allowed to be used in the files to be sent to the

clearing service. The files generated by the

clearing service indicate the entity originating the

SEPA resolution of investigation (negative

response to the cancellation request) message to

the clearing service (where such information is

available).

4.103 [1..1] │└┬ <Agt>

2.1.0 [1..1] │ └┬ <FinInstnId>

2.1.1 [1..1] │ └─ <BIC> BIC X


6.1.0 [1..1] ├─ <IntrBkSttlmAmt> Amount of the original message X

6.1.6 [1..1] ├─ <IntrBkSttlmDt> Value date of the original message X

6.1.52 [1..1] ├┬ <SttlmInf>

6.1.53 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

6.1.68 [0..1] │└┬ <ClrSys>

6.1.70 [1..1] │ └─ <Prtry> Clearing system proprietary code X Only code "EKS" is allowed.

6.1.233 [1..1] ├┬ <PmtTpInf>

6.1.236 [1..1] │├┬ <SvcLvl>

6.1.237 [1..1] ││└─ <Cd> Service code X Only code "SEPA" is allowed.

6.1.239 [0..1] │├┬ <LclInstrm>

│││


information

6.1.240 {Or ││├─ <Cd>

│││



6.1.241 Or} ││└─ <Prtry> X Cannot be used at the same time as 6.1.240.

6.1.243 [0..1] │└┬ <CtgyPurp> Category purpose

6.1.244 {Or │ ├─ <Cd>

│ │



6.1.245 Or} │ └─ <Prtry> X Cannot be used at the same time as 6.1.244.

6.1.467 [0..1] ├┬ <RmtInf> Remittance information

6.1.468 {Or │├─ <Ustrd> Unstructured X Cannot be used at the same time as 6.1.469.

48

6.1.469 Or} │└┬ <Strd>

│ │

│ │

Structured Cannot be used at the same time as 6.1.468. Only

one element occurrence is allowed with a

maximum of 140 characters.

6.1.489 [0..1] │ └┬ <CdtrRefInf> Creditor reference information

6.1.490 [1..1] │ ├┬ <Tp> Creditor reference information type When used, 6.1.495 must be present.

6.1.491 [1..1] │ │├┬ <CdOrPrtry>

6.1.492 [1..1] │ ││└─ <Cd>

│ ││


code


6.1.494 [0..1] │ │└─ <Issr>

│ │


information type

X

6.1.495 [1..1] │ └─ <Ref> Reference assigned by the creditor X When used, 6.1.490 must be present.

6.1.583 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

6.1.584 [0..1] │├─ <Nm> Name X





6.1.600 [1..1] │ │ ├─ <Id> Identifier X


6.1.602 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







6.1.612 [1..1] │ ├─ <Id> Identifier X


6.1.614 {Or │ │├─ <Cd>

│ ││




49


6.1.626 [1..1] ├┬ <Dbtr> Debtor


6.1.628 [0..1] │├┬ <PstlAdr> Address


6.1.638 [0..2] ││└─ <AdrLine> Address line X Only two occurrences of the element are allowed.





6.1.643 [1..1] │ │ ├─ <Id> Identifier X


6.1.645 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>







6.1.655 [1..1] │ ├─ <Id> Identifier X


6.1.657 {Or │ │├─ <Cd>

│ ││





6.1.669 [1..1] ├┬ <DbtrAcct> Debtor account Mandatory.


6.1.671 [1..1] │ └─ <IBAN> IBAN X

6.1.683 [1..1] ├┬ <DbtrAgt> Debtor agent Only BIC is allowed.


50

6.1.685 [1..1] │ └─ <BIC>

│


the routing table.

6.1.737 [1..1] ├┬ <CdtrAgt> Creditor agent Only BIC is allowed.


6.1.739 [1..1] │ └─ <BIC>

│


the routing table.

6.1.791 [1..1] ├┬ <Cdtr> Creditor


6.1.793 [0..1] │├┬ <PstlAdr> Address


6.1.803 [0..2] ││└─ <AdrLine>

││


allowed.





6.1.808 [1..1] │ │ ├─ <Id> Identifier X


6.1.810 {Or │ │ │├─ <Cd>

│ │ ││







│ ││ Birth>





6.1.818 [1..1] │ │└─ <CtryOfBirth>

│ │



6.1.820 [1..1] │ ├─ <Id> Identifier X


6.1.822 {Or │ │├─ <Cd>

│ ││




51


6.1.834 [1..1] ├┬ <CdtrAcct> Creditor account Mandatory.


6.1.836 [1..1] │ └─ <IBAN> IBAN X

6.1.848 [0..1] └┬ <UltmtCdtr> Ultimate creditor

6.1.849 [0..1] ├─ <Nm> Name X





6.1.865 [1..1] │ ├─ <Id> Identifier X


6.1.867 {Or │ │├─ <Cd>

│ ││

│ ││







││ Birth>







9.1.28 [1..1] ├─ <Id> Identifier X


9.1.30 {Or │├─ <Cd>

││





52

5.9. Status request message

A status request message shall be generated in accordance with ISO 20022 pacs.028.001.01 message rules and included into the PE, IE or

OE type file. Status request message shall be sent to inquire about the status of a SEPA payment cancellation request, SEPA claim of non-

receipt or SEPA claim for value date correction, where no response has been received in due time.

5.9.1. Bulk header

ISO

number


9.4.1 [1..1] ├┬ <GrpHdr> Bulk information

9.4.1.1 [1..1] │├─ <MsgId> Bulk identifier X

9.4.1.2 [1..1] │├─ <CreDtTm>

││

Date and time of bulk creation X

9.4.1.3 [0..1] │├┬ <InstgAgt>

│││

│││

Bulk sender Must be indicated in the files to be sent to the

clearing service. Is not used in files generated by


10.1.7.1.1 [1..1] ││└┬ <FinInstnId>

10.1.7.4.1 [1..1] ││ └─ <BICFI> The BIC of the bulk sender X

9.4.1.4 [0..1] │└┬ <InstdAgt>

│ │

│ │

Bulk recipient Used in the files generated by the clearing

service. Not allowed in the files to be sent to the

clearing service.

10.1.7.1.1 [1..1] │ └┬ <FinInstnId>

│ │

10.1.7.4.1 [1..1] │ └─ <BICFI> The BIC of the bulk recipient X

5.9.2. Status request message structure

ISO number Usag

e

Element Description Link Notes

9.4.2 [1..1] ├┬ <OrgnlGrpInf> Information on the original bulk

9.4.2.1 [1..1] │├─ <OrgnlMsgId> Message identifier of the original bulk X

9.4.2.2 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original bulk X Only code "camt.056", "camt.027" or

"camt.087" is allowed.

9.4.3 [1..1] └┬ <TxInf> Message information

9.4.3.1 [1..1] ├─ <StsReqId> Status request message identifier X

53

│

9.4.3.3 [1..1] ├─ <OrgnlInstrId> │

│

Original SEPA payment cancellation

request message identifier

X Identifier origin specific for each message type

(camt.056 – <CxlId>, camt.027 - <Case><Id>,

camt.087 - <Case><Id>).

9.4.3.4 [1..1] ├─ <OrgnlEndToEndId> │


debtor

X

9.4.3.5 [1..1] ├─ <OrgnlTxId> Original message identifier X

9.4.3.10 [1..1] └┬ <OrgnlTxRef> Information on the original message

9.4.3.10.1 [0..1] ├─ <IntrBkSttlmAmt> Amount of the original message X

9.4.3.10.3 [1..1] ├─ <IntrBkSttlmDt> Date of the original message X

9.4.3.10.7 [1..1] ├┬ <SttlmInf>

10.1.15.2.1 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

10.1.15.2.3 [1..1] │└┬ <ClrSys>

10.1.15.2.3.2 [1..1] │ └─ <Prtry> Clearing system proprietary code X Only code "EKS" is allowed.

9.4.3.10.8 [1..1] ├┬ <PmtTpInf> Payment type information Mandatory in each message.

10.1.11.2.3 [1..1] │├┬ <SvcLvl> Service level Mandatory.

10.1.11.2.3.1 [1..1] ││└─ <Cd> Code X Only code "SEPA" is allowed.

10.1.11.2.4 [0..1] │├┬ <LclInstrm> │││


information

Only used if bilaterally agreed between the

debtor agent and the creditor agent.

10.1.11.2.4.1 {Or ││├─ <Cd>

│││

│││


Cannot be used at the same time

as 10.1.11.2.4.2.

10.1.11.2.4.2 Or} ││└─ <Prtry> ││

X Cannot be used at the same time

as 10.1.11.2.4.1.

10.1.11.2.6 [0..1] │└┬ <CtgyPurp> Category purpose

10.1.11.2.6.1 {Or │ ├─ <Cd>

│ │

│ │



as 10.1.11.2.6.2.

10.1.11.2.6.2 Or} │ └─ <Prtry> │

X Cannot be used at the same time

as 10.1.11.2.6.1.

9.4.3.10.11 [0..1] ├┬ <RmtInf> Remittance information

9.4.3.10.11.1 {Or │├─ <Ustrd>

││

Unstructured X Cannot be used at the same time

as 9.4.3.10.11.2.

9.4.3.10.11.2 Or} │└┬ <Strd> │ │

│ │

Structured Cannot be used at the same time

as 9.4.3.10.11.1. Only one element occurrence

is allowed with a maximum of 140 characters.

9.4.3.10.11.2.3 [0..1] │ └┬ <CdtrRefInf> Creditor reference information

54

10.1.6.1.1 [1..1] │ ├┬ <Tp> Creditor reference information type Allowed to use only with 10.1.6.1.2.

10.1.6.1.1.1 [1..1] │ │├┬ <CdOrPrtry>

10.1.6.1.1.1.1 [1..1] │ ││└─ <Cd> │ ││


code


10.1.6.1.1.1.2 [0..1] │ │└─ <Issr> │ │


information type

X

10.1.6.1.2 [1..1] │ └─ <Ref> Reference assigned by the creditor X Allowed to use only with 10.1.6.1.1.

9.4.3.10.12 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

10.1.9.1.1 [0..1] │├─ <Nm> Ultimate debtor's name X

10.1.9.1.2 [0..1] │├┬ <PstlAdr> Address

10.1.13.1.9 [0..1] ││├─ <Ctry> │││

Country X Only ISO 3166 Alpha-2 codes are allowed.

10.1.13.1.10 [0..2] ││└─ <AdrLine> Address line X

10.1.9.1.3 [0..1] │└┬ <Id> Ultimate debtor identification

10.1.10.1.1 {Or │ ├┬ <OrgId> Organisation identification Cannot be used at the same time as 10.1.10.1.2.

10.1.9.2.1 [0..1] │ │├─ <AnyBIC> BIC or BEI X

10.1.9.2.2 [0..1] │ │└┬ <Othr> Other type of identification

10.1.9.2.2.1 [1..1] │ │ ├─ <Id> Identifier X

10.1.9.2.2.2 [0..1] │ │ ├┬ <SchmeNm> Scheme name

10.1.9.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



as 10.1.9.2.2.2.2.

10.1.9.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │

Scheme name X Cannot be used at the same time

as 10.1.9.2.2.2.1.

10.1.9.2.2.3 [0..1] │ │ └─ <Issr> Issuer of identifier X

10.1.10.1.2 Or} │ └┬ <PrvtId> Natural person identification Cannot be used at the same time as 10.1.10.1.1.

10.1.12.2.1 {Or │ ├┬ <DtAndPlcOf

│ ││ Birth>

Date and place of birth Cannot be used at the same time as 10.1.12.2.2.

10.1.12.1.1 [1..1] │ │├─ <BirthDt> Date of birth X

10.1.12.1.2 [0..1] │ │├─ <PrvcOfBirth> Province of birth X

10.1.12.1.3 [1..1] │ │├─ <CityOfBirth> City of birth X

10.1.12.1.4 [1..1] │ │└─ <CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are allowed.

10.1.12.2.2 Or} │ └┬ <Othr> Other type of identification Cannot be used at the same time as 10.1.12.2.1.

10.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X

10.1.12.2.2.2 [0..1] │ ├┬ <SchmeNm> Scheme name

55

10.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



as 10.1.12.2.2.2.2.

10.1.12.2.2.2.2 Or} │ │└─ <Prtry> │ │


as 10.1.12.2.2.2.1.

10.1.12.2.2.3 [0..1] │ └─ <Issr> Issuer of identifier X

9.4.3.10.13 [1..1] ├┬ <Dbtr> Debtor

10.1.9.1.1 [1..1] │├─ <Nm> Debtor name X

10.1.9.1.2 [0..1] │├┬ <PstlAdr> Address

10.1.13.1.9 [0..1] ││├─ <Ctry> Country X Only ISO 3166 Alpha-2 codes are allowed.

10.1.13.1.10 [0..2] ││└─ <AdrLine> Address line X

10.1.9.1.3 [0..1] │└┬ <Id> Debtor identification




10.1.9.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


10.1.9.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



as 10.1.9.2.2.2.2.

10.1.9.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


as 10.1.9.2.2.2.1.



10.1.12.2.1 {Or │ ├┬ <DtAndPlcOf

│ ││ Birth>







10.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


10.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



as 10.1.12.2.2.2.2.

56

10.1.12.2.2.2.2 Or} │ │└─ <Prtry> │ │


as 10.1.12.2.2.2.1.


9.4.3.10.14 [1..1] ├┬ <DbtrAcct> Debtor account

10.1.1.1.1 [1..1] │└┬ <Id> Debtor account identification

10.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

9.4.3.10.15 [1..1] ├┬ <DbtrAgt> Debtor agent

10.1.7.1.1 [1..1] │└┬ <FinInstnId> Financial institution identification

10.1.7.4.1 [1..1] │ └─ <BICFI> BIC X Only BIC is allowed.

9.4.3.10.17 [1..1] ├┬ <CdtrAgt> Creditor agent


10.1.7.4.1 [1..1] │ └─ <BICFI> BIC X Only BIC is allowed.

9.4.3.10.19 [1..1] ├┬ <Cdtr> Creditor

10.1.9.1.1 [1..1] │├─ <Nm> Creditor name X Mandatory.

10.1.9.1.2 [0..1] │├┬ <PstlAdr> Address

10.1.13.1.9 [0..1] ││├─ <Ctry> Country X Only ISO 3166 Alpha-2 codes are allowed.

10.1.13.1.10 [0..2] ││└─ <AdrLine> ││

Address line X No more than two occurrences of the element

are allowed.

10.1.9.1.3 [0..1] │└┬ <Id> Creditor identification




10.1.9.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


10.1.9.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



as 10.1.9.2.2.2.2.

10.1.9.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


as 10.1.9.2.2.2.1.



10.1.12.2.1 {Or │ ├┬ <DtAndPlcOf

│ ││ Birth>



10.1.12.1.2 [0..1] │ │├─<PrvcOfBirth> Province of birth X

10.1.12.1.3 [1..1] │ │├─<CityOfBirth> City of birth X

57

10.1.12.1.4 [1..1] │ │└─<CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are allowed.


10.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


10.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



as 10.1.12.2.2.2.2.

10.1.12.2.2.2.2 Or} │ │└─ <Prtry> │ │


as 10.1.12.2.2.2.1.


9.4.3.10.20 [1..1] ├┬ <CdtrAcct> Creditor account

10.1.1.1.1 [1..1] │└┬ <Id> Creditor account identification

10.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

9.4.3.10.21 [0..1] └┬ <UltmtCdtr> Ultimate creditor

10.1.9.1.1 [0..1] ├─ <Nm> Ultimate creditor's name X

10.1.9.1.2 [0..1] ├┬ <PstlAdr> Address

10.1.13.1.9 [0..1] │├─ <Ctry> Country X

10.1.13.1.10 [0..2] │└─ <AdrLine> Address line X

10.1.9.1.3 [0..1] └┬ <Id> Ultimate creditor identification

10.1.10.1.1 {Or ├┬ <OrgId> Organisation identification Cannot be used at the same time as 10.1.10.1.2.

10.1.9.2.1 [0..1] │├─ <AnyBIC> BIC or BEI X

10.1.9.2.2 [0..1] │└┬ <Othr> Other type of identification

10.1.9.2.2.1 [1..1] │ ├─ <Id> Identifier X


10.1.9.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



as 10.1.9.2.2.2.2.

10.1.9.2.2.2.2 Or} │ │└─ <Prtry>

│ │


as 10.1.9.2.2.2.1.


10.1.10.1.2 Or} └┬ <PrvtId> Natural person identification Cannot be used at the same time as 10.1.10.1.1.

10.1.12.2.1 {Or ├┬ <DtAndPlcOf

││ Birth>


10.1.12.1.1 [1..1] │├─ <BirthDt> Date of birth X

10.1.12.1.2 [0..1] │├─<PrvcOfBirth> Province of birth X

10.1.12.1.3 [1..1] │├─<CityOfBirth> City of birth X

58

10.1.12.1.4 [1..1] │└─<CtryOfBirth> Country of birth X Only ISO 3166 Alpha-2 codes are allowed.

10.1.12.2.2 Or} └┬ <Othr> Other type of identification Cannot be used at the same time as 10.1.12.2.1.

10.1.12.2.2.1 [1..1] ├─ <Id> Identifier X

10.1.12.2.2.2 [0..1] ├┬ <SchmeNm> Scheme name

10.1.12.2.2.2.1 {Or │├─ <Cd>

││

││



as 10.1.12.2.2.2.2.

10.1.12.2.2.2.2 Or} │└─ <Prtry> │


as 10.1.12.2.2.2.1.

10.1.12.2.2.3 [0..1] └─ <Issr> Issuer of identifier X

5.10. SEPA resolution of investigation (response to the investigation request) message

SEPA resolution of investigation (response to the investigation request) message shall be generated in accordance with ISO 20022

camt.029.001.08 message rules and included in the IE or OE type files. SEPA resolution of investigation (response to the investigation

request) message shall be sent to inform about the results of investigation conducted in accordance with the SEPA claim of non-receipt

message or SEPA claim for value date correction message.

5.10.1. SEPA resolution of investigation (response to the investigation request) message structure

ISO

number

Usage Element Description Notes

[1..1] └┬ <RsltnOfInvstgtn> SEPA resolution of investigation

(response to the investigation request)

message

5.4.1 [1..1] ├─ <Assgnmt> SEPA resolution of investigation


message bulk information

5.4.2 [1..1] ├─ <RslvdCase> Information on the original

investigation request message

5.4.3 [1..1] ├─ <Sts> Information on the results of the

investigation

5.4.5 [0..1] ├─ <ModDtls> Details of the underlying message

being modified

59

5.4.6 [0..1] ├─ <ClmNonRctDtls> Details of the underlying message for

which a SEPA claim of non-receipt has

been initiated

5.4.9 [0..1] └─ <RsltnRltdInf> Resolution related information

5.10.2. Bulk header

ISO

number


5.4.1 [1..1] └┬ <Assgnmt>

19.1.9.13.1 [1..1] ├─ <Id> │




X

19.1.9.13.2 [1..1] ├┬ <Assgnr> ││

││

││


of investigation (response to the

investigation request) message bulk


contain the BIC of the file sender; the files

generated by the clearing service contain the

BIC of Latvijas Banka (LACBLV2XXXX).

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.9.13.3 [1..1] ├┬ <Assgne> ││

││

││

││






(LACBLV2XXXX); the files generated by the

clearing service contain the BIC of the file

recipient.

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.9.13.4 [1..1] └─ <CreDtTm> Date and time when the bulk was

created

X

60

5.10.3. Structure of the information on the original investigation request message

ISO

number


5.4.2 [1..1] └┬ <RslvdCase>

19.1.9.15.1 [1..1] ├─ <Id> Original investigation message

identifier

X

19.1.9.15.2 [1..1] └┬ <Cretr> Debtor agent of the initial payment

message

19.1.12.3.2 [1..1] └┬ <Agt>

19.1.7.1.1 [1..1] └┬ <FinInstnId>

19.1.7.4.1 [1..1] └─ <BICFI> BIC X

5.10.4. Structure of the information on the results of the investigation

ISO

number


5.4.3 [1..1] └┬ <Sts> Status

5.4.3.1 [1..1] └─ <Conf> Resolution of investigation status code X Only the listed codes are allowed (Table 10).

5.10.5. Structure of the details of the underlying message being modified

ISO number Usage Element Description Notes

5.4.5 [1..1] └┬ <ModDtls>

5.4.5.1 [1..1] ├─ <ModStsId> Modification status identifier X

5.4.5.3 [1..1] ├┬ <OrgnlGrpInf> Information on the original bulk

19.1.10.2.1 [1..1] │├─ <OrgnlMsgId> Message identifier of the original

bulk

X

19.1.10.2.2 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original

bulk

X Only code "pacs.008" is allowed.

5.4.5.5 [0..1] ├─ <OrgnlInstrId> │

Original instruction identifier X Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

5.4.5.6 [0..1] ├─ <OrgnlEndToEndId> │

│

Original identifier assigned by the

debtor

X Mandatory if value of 5.4.3.1 <Conf> is

"ACNR", "RJVA", "CVAA", "ACVA",

61

"MODI". Cannot be used if value of 5.4.3.1

<Conf> is "RJNR".

5.4.5.7 [0..1] ├─ <OrgnlTxId> │

Original message identifier X Mandatory

5.4.5.15 [1..1] └┬ <OrgnlTxRef> Information on the original

message

19.1.10.1.1 [0..1] ├─ <IntrBkSttlmAmt> │

Amount of the original message X Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.10.1.3 [0..1] ├─ <IntrBkSttlmDt> │

Value date of the original message X Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.10.1.7 [0..1] ├┬ <SttlmInf> ││

Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.19.2.1 [1..1] │├─ <SttlmMtd> ││

Settlement method X Only code "CLRG" is allowed.

19.1.19.2.3 [1..1] │└┬ <ClrSys>


19.1.10.1.8 [0..1] ├┬ <PmtTpInf> ││

││

││

Payment type information Cannot be used if 5.4.3.1 <Conf> has value

"RJNR".

19.1.14.1.3 [1..1] │├┬ <SvcLvl>

19.1.14.1.3.1 [1..1] ││└─ <Cd> Service Level Code X Only the code "SEPA" is allowed.

19.1.14.1.4 [0..1] │├┬ <LclInstrm> │││

Local Instrument Only used if bilaterally agreed between the

debtor agent and the creditor agent.

19.1.14.1.4.1 {Or ││├─ <Cd>

│││

│││

Service code X Only ISO 20022 codes are allowed (Table 1).

Cannot be used at the same time as

19.1.14.1.4.2.

19.1.14.1.4.2 Or} ││└─ <Prtry>

││

User community specific

instrument information

X Cannot be used at the same time as

19.1.14.1.4.1.


19.1.14.1.6.1 {Or │ ├─ <Cd>

│ │

│ │



19.1.14.1.6.2.

19.1.14.1.6.2 Or} │ └─ <Prtry>

│


19.1.14.1.6.1.

62

19.1.10.1.11 [0..1] ├┬ <RmtInf> ││

Remittance Information Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.10.10.1 {Or │├─ <Ustrd>

││

Unstructured X Cannot be used at the same time as

19.1.10.10.2.

19.1.10.10.2 Or} │└┬ <Strd>

│ │

│ │

│ │

│ │

│ │

Structured Cannot be used at the same time as

19.1.10.10.1. Only one occurrence of the

element is allowed with maximum 140

characters.

19.1.16.1.3 [0..1] │ └┬ <CdtrRefInf> Creditor reference information

19.1.6.1.1 [1..1] │ ├┬ <Tp> │ ││

Creditor reference information

type

Allowed to use only with 19.1.6.1.2.

19.1.6.1.1.1 [0..1] │ │├┬ <CdOrPrtry>

19.1.6.1.1.1.1 [0..1] │ ││└─ <Cd> │ │

Creditor reference information

type code


19.1.6.1.1.2 [0..1] │ │└─ <Issr> │ │


information type

X

19.1.6.1.2 [0..1] │ └─ <Ref> Reference assigned by the creditor X Allowed to use only with 19.1.6.1.1.

19.1.10.1.12 [0..1] ├┬ <UltmtDbtr> ││

Ultimate debtor Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Name X

19.1.11.3.3 [0..1] │ └┬ <Id> Ultimate debtor identification

19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││

Organisation identification Cannot be used at the same time as 19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │

Other type of identification

19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │

Scheme name X Cannot be used at the same time as

19.1.11.2.2.2.1.

63



19.1.12.2.1 [0..1] │ ├┬ <DtAndPlcOf │ ││ Birth>

Date and place of birth





19.1.12.2.2 [0..1] │ └┬ <Othr> Other type of identification

19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││

Scheme name code X Only ISO 20022 codes are allowed (Table 4.).


19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.13 [0..1] ├┬ <Dbtr> ││

Debtor Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Debtor name X

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address

19.1.17.1.9 [0..1] │ │├─ <Ctry> Country X Only ISO 3166 Alpha-2 codes are allowed.

19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │


are allowed.

19.1.11.3.3 [0..1] │ └┬ <Id> Debtor identification


19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


64

19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │

Natural person identification Cannot be used at the same time as 19.1.12.4.1.








19.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.14 [0..1] ├┬ <DbtrAcct> ││

Debtor account Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.1.1.1 [1..1] │└┬ <Id> Debtor account identification

19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

19.1.10.1.15 [1..1] ├┬ <DbtrAgt> ││

Debtor agent Only BIC is allowed. Mandatory if value of

5.4.3.1 <Conf> is "RJNR".


19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X BIC should be available in a routing table.

19.1.10.1.17 [1..1] ├┬ <CdtrAgt> ││

Creditor agent Only BIC is allowed. Mandatory if value

5.4.3.1 <Conf> is "RJNR".


19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X BIC should be available in a routing table.

65

19.1.10.1.19 [0..1] ├┬ <Cdtr> ││

Creditor Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Creditor name X Mandatory

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address


19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │

Address line X Only two occurrences of the element are

allowed.

19.1.11.3.3 [0..1] │ └┬ <Id> Creditor identification


19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.










19.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


66

19.1.10.1.20 [0..1] ├┬ <CdtrAcct> ││

Creditor account Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".


19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

19.1.10.1.21 [0..1] ├┬ <UltmtCdtr> ││

Ultimate creditor Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Name X Mandatory

19.1.11.3.3 [0..1] │ └┬ <Id> Ultimate creditor identification


19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.










19.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


67

19.1.10.1.22 [0..1] └┬ <Purp> │

Payment purpose Cannot be used if value of 5.4.3.1 <Conf> is

"RJNR".

19.1.10.11.1 [1..1] └─ <Cd> Payment purpose ISO code X

5.10.6. Structure of the details of the underlying message for which a SEPA claim of non-receipt has been initiated


5.4.6 [0..1] └┬ <ClmNonRctDtls> │

Allowed to use if value of 5.4.3.1 <Conf> is

"RJNR" or "ACNR".

5.4.6.1 {Or ├┬ <Accptd>

││

││

SEPA claim of non-receipt message is

accepted

Cannot be used at the same time as 5.4.6.2.

Mandatory if value of 5.4.3.1 <Conf> is

"ACNR".

5.4.6.1.1 [1..1] │├─ <DtPrcd> ││

Date when the original payment

message was processed

X

5.4.6.1.2 │└┬ <OrgnlNxtAgt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

5.4.6.2 Or} └┬ <Rjctd>

│

│

SEPA claim of non-receipt message is

rejected

Cannot be used at the same time as 5.4.6.1.


"RJNR".

5.4.6.2.1 [1..1] └─ <Cd> Rejection code X Only listed codes are allowed (Table 11).

5.10.7. Resolution related information structre


5.4.5.10 [0..1] └┬ <RsltnRltdInf> │

│

│


"ACVA" or "MODI". Cannot be used if value

of 5.4.3.1 <Conf> is "RJNR", "RJVA" or

"CVAA".

19.1.9.7.2 [0..1] ├─ <IntrBkSttlmDt> │

│

New value date applied to the payment

message

X Mandatory if value of 5.4.3.1 <Conf> is

"ACVA" or "MODI". Cannot be used if value

of 5.4.3.1 <Conf> is "ACNR".

19.1.9.7.4 [0..1] ├┬ <Compstn> ││

││

Compensation Mandatory if value of 5.4.3.1 <Conf> is

"ACVA". May be used if value of 5.4.3.1

<Conf> is "MODI".

68

19.1.9.6.1 [1..1] │├─ <Amt> Compensation amount X

19.1.9.6.2 [1..1] │├┬ <DbtrAgt> Debtor agent

19.1.7.1.1 [1..1] ││└┬ <FinInstnId> Financial institution identification

19.1.7.4.1 [1..1] ││ ├─ <BICFI> BIC X

[0..1] ││ └┬ <Othr> Other type of identification

[1..1] ││ └─<Id> ││

Account number in IBAN format for

crediting the compensation amount

19.1.9.6.3 [1..1] │├┬ <CdtrAgt> Creditor agent

19.1.7.1.1 [1..1] ││└┬ <FinInstnId> Financial institution identification

19.1.7.4.1 [1..1] ││ └─ <BICFI> BIC X

19.1.9.6.4 [1..1] │└┬ <Rsn> Reason

19.1.9.6.4.1 [1..1] │ └─ <Cd> Reason code X Only code "VADA" is allowed.

19.1.9.7.5 [0..1] └┬ <Chrgs> │

Charges requested for the processing of

investigation request

Allowed if value of 5.4.3.1 <Conf> is

"ACNR", "ACVA" vai "MODI".

19.1.4.1.1 [1..1] ├─ <Amt> Amount X

19.1.4.1.2 [1..1] └┬ <Agt>

19.1.7.1.1 [1..1] └┬ <FinInstnId>

19.1.7.4.1 [1..1] ├─ <BICFI> BIC X

[0..1] └┬ <Othr> Other type of identification

[1..1] └─<Id> Account number in IBAN format for

crediting the charges amount

5.11. SEPA claim of non-receipt message

SEPA claim of non-receipt message shall be generated in accordance with ISO 20022 camt.027.001.06 message rules and included into the

IE or OE files. SEPA claim of non-receipt message is sent by the debtor agent with the purpose to investigate if and when the SEPA credit

transfer has been credited to the beneficiary's account.

5.11.1. SEPA claim of non-receipt message structure

ISO

number


[1..1] └┬ <ClmNonRct> SEPA claim of non-receipt message

3.4.1 [1..1] ├─ <Assgnmt> SEPA claim of non-receipt message

bulk information

69

3.4.2 [1..1] ├─ <Case> Details of the SEPA claim of non-

receipt request

3.4.3 [1..1] ├─ <Undrly> Details of the underlying payment

message

3.4.5 [0..1] └─ <InstrForAssgne> Instructions for the recipient

5.11.2. Bulk header

ISO

number


3.4.1 [1..1] └┬ <Assgnmt>

19.1.9.13.1 [1..1] ├─ <Id> SEPA claim of non-receipt message

bulk identifier

X

19.1.9.13.2 [1..1] ├┬ <Assgnr>

││

││

││

││

Instructing agent of SEPA claim of

non-receipt message bulk

The files to be sent to the clearing service

shall contain the BIC of the bulk sender; the

files generated by the clearing service contain

the BIC of Latvijas Banka

(LACBLV2XXXX).

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.9.13.3 [1..1] ├┬ <Assgne>

││

││

││

││

SEPA claim of non-receipt message

bulk recipient

The files to be sent to the clearing service

shall contain the BIC of Latvijas Banka

(LACBLV2XXXX); the files generated by

the clearing service contain the BIC of the

bulk recipient.

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X


created

X

70

5.11.3. Structure of the details of the SEPA claim of non-receipt request

ISO

number


3.4.2 [1..1] └┬ <Case>

19.1.9.15.1 [1..1] ├─ <Id> SEPA claim of non-receipt message

identifier

X


message

19.1.12.3.2 [1..1] └┬ <Agt>

19.1.7.1.1 [1..1] └┬ <FinInstnId>

19.1.7.4.1 [1..1] └─ <BICFI> BIC X

5.11.4. Structure of the details of the underlying payment message

ISO number Usag

e

Element Description Notes

3.4.3 [1..1] └┬ <Undrlyg>

19.1.9.11.2 [1..1] └┬ <IntrBk>

19.1.9.12.1 [1..1] ├┬ <OrgnlGrpInf> ││

Information on the original bulk

19.1.9.12.1.1 [1..1] │├─ <OrgnlMsgId> Message identifier of the original

bulk

X

19.1.9.12.1.2 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original

bulk


19.1.9.12.2 [0..1] ├─ <OrgnlInstrId> Original instruction identifier X

19.1.9.12.3 [1..1] ├─ <OrgnlEndToEndId> │

Original identifier assigned by the

debtor

X

19.1.9.12.4 [1..1] ├─ <OrgnlTxId> Original message identifier X

19.1.9.12.5 [1..1] ├─ <OrgnlIntrBk │ SttlmAmt>


19.1.9.12.6 [1..1] ├─ <OrgnlIntr │ BkSttlmDt>


19.1.9.12.7 [1..1] └┬ <OrgnlTxRef> Information on the original message

19.1.10.1.7 [0..1] ├┬ <SttlmInf>

19.1.19.2.1 [1..1] │├─ <SttlmMtd> Settlement method X Only code "CLRG" is allowed.

71

││

19.1.19.2.3 [1..1] │└┬ <ClrSys>


19.1.10.1.8 [0..1] ├┬ <PmtTpInf>

19.1.14.1.3 [1..1] │├┬ <SvcLvl>

19.1.14.1.3.1 [1..1] ││└─ <Cd> Service Level Code X Only code "SEPA" is allowed.

19.1.14.1.4 [0..1] │├┬ <LclInstrm> │││

Local Instrument

19.1.14.1.4.1 {Or ││├─ <Cd>

│││

│││

Service code X Only ISO 20022 codes are allowed


as 19.1.14.1.4.2.

19.1.14.1.4.2 Or} ││└─ <Prtry>

││


information


19.1.14.1.4.1.


19.1.14.1.6.1 {Or │ ├─ <Cd>

│ │

│ │



as 19.1.14.1.6.2.

19.1.14.1.6.2 Or} │ └─ <Prtry>

│


19.1.14.1.6.1.

19.1.10.1.11 [0..1] ├┬ <RmtInf> Remittance Information

[1..1] │├─ <Ustrd> ││


19.1.10.10.2.

19.1.10.10.2 [1..1] │└┬ <Strd> │ │

│ │

│ │




characters.


19.1.6.1.1 [1..1] │ ├┬ <Tp> Creditor reference information type Allowed to use with 19.1.6.1.2.

19.1.6.1.1.1 [1..1] │ │├┬ <CdOrPrtry>

19.1.6.1.1.1.1 [1..1] │ ││└─ <Cd> │ │


code


19.1.6.1.1.2 [0..1] │ │└─ <Issr> │ │


information type

X

19.1.6.1.2 [1..1] │ └─ <Ref> Reference assigned by the creditor X Allowed to use with 19.1.6.1.1.

19.1.10.1.12 ├┬ <UltmtDbtr> Ultimate debtor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Name X

72


19.1.12.4.1 {Or │ ├┬ <OrgId> Organisation identification Allowed to use with 19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││ │ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │

Natural person identification Cannot be used at the same time as

19.1.12.4.1.








19.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.13 [0..1] ├┬ <Dbtr> Debtor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Debtor name X

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address


73

19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │


are allowed.


19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││

Organisation identification Cannot be used at the same time as

19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.








19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.



19.1.1.1.1 [1..1] │└┬ <Id> Identification

19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

74

19.1.10.1.15 [1..1] ├┬ <DbtrAgt> Debtor Agent

19.1.7.1.1 [1..1] │└┬ <FinInstnId> Financial Institution Identification

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X



19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.10.1.19 [0..1] ├┬ <Cdtr> Creditor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Creditor name X

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address


19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │


allowed.


19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││


19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.







75


19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.




19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

├┬ <UltmtCdtr> Ultimate creditor

19.1.12.3.1 [1..1] │└┬ <Pty> Party



19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││


19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.





76




19.1.12.2.2.1 [1..1] │ ├─ <Id> Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.22 [0..1] └┬ <Purp> Payment purpose


5.11.5. Structure of the instructions for the assignee


1.0 [1..1] └┬ <InstrForAssgne>

1.1 [1..1] ├─ <Cd> Instruction code X Only code "INQR" is allowed.

1.2 [1..1] └─ <InstrInf> Additional details for the recepient X

5.12. SEPA claim for value date correction message

SEPA claim for value date correction message shall be generated in accordance with ISO 20022 camt.087.001.05 message rules and included

in the IE or OE files. SEPA claim for value date correction message is sent by the debtor agent to request to change the value date of the

settled SEPA credit transfer.

5.12.1. SEPA claim for value date correction message structure


[1..1] └┬ <ReqToModfyPmt> SEPA claim for value date

correction message

18.4.1 [1..1] ├─ <Assgnmt> SEPA claim for value date

correction message bulk information

77

18.4.2 [1..1] ├─ <Case> Details of SEPA claim for value date

correction message

18.4.3 [1..1] ├─ <Undrly> Details of the underlying payment

message

18.4.4 [1..1] ├─ <Mod> Change request information

18.4.5 [0..1] └─ <InstrForAssgne> Instructions for the recipient

5.12.2. Bulk header


18.4.1 [1..1] └┬ <Assgnmt>

19.1.9.13.1 [1..1] ├─ <Id> SEPA claim for value date correction


X

19.1.9.13.2 [1..1] ├┬ <Assgnr>

││

││

││

Instructing agent of SEPA claim for

value date correction message bulk

Files sent to the clearing service shall

contain the sending bank's BIC, files

received from the clearing service shall

contain BIC of the EKS (Latvijas Banka).

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.9.13.3 [1..1] ├┬ <Assgne>

││

││

││

SEPA claim for value date correction


Files sent to the clearing service shall

contain BIC of the EKS (Latvijas Banka),

files received from the clearing service shall

contain the beneficiary bank's BIC.

19.1.12.3.2 [1..1] │└┬ <Agt>

19.1.7.1.1 [1..1] │ └┬ <FinInstnId>

19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X


created

X

5.12.3. Structure of details of SEPA claim for value date correction message


18.4.2 [1..1] └┬ <Case>

19.1.9.15.1 [1..1] ├─ <Id> SEPA claim for value date

correction message identifier

X

78


message

19.1.12.3.2 [1..1] └┬ <Agt>

19.1.7.1.1 [1..1] └┬ <FinInstnId>

19.1.7.4.1 [1..1] └─ <BICFI> BIC X

5.12.4. Structure of details of the underlying payment message


18.4.3 [1..1] └┬ <Undrlyg>

19.1.9.11.2 [1..1] └┬ <IntrBk>

19.1.9.12.1 [1..1] ├┬ <OrgnlGrpInf> Information on the original bulk

19.1.9.12.1.1 [1..1] │├─ <OrgnlMsgId> Message identifier of the original

bulk

X

19.1.9.12.1.2 [1..1] │└─ <OrgnlMsgNmId> Type of messages in the original

bulk


19.1.9.12.2 [0..1] ├─ <OrgnlInstrId> Original instruction identifier X

19.1.9.12.3 [1..1] ├─ <OrgnlEndToEndId> Original identifier assigned by the

debtor

X

19.1.9.12.4 [1..1] ├─ <OrgnlTxId> Original message identifier X

19.1.9.12.5 [1..1] ├─ <OrgnlIntrBkSttlm │ Amt>


19.1.9.12.6 [1..1] ├─ <OrgnlIntrBkSttlm │ Dt>


19.1.9.12.7 [1..1] └┬ <OrgnlTxRef> Information on the original message

19.1.10.1.7 [0..1] ├┬ <SttlmInf>

19.1.19.2.1 [1..1] │├─ <SttlmMtd> ││

Settlement method X Only code "CLRG" is allowed.

19.1.19.2.3 [1..1] │└┬ <ClrSys>

19.1.19.2.3.2 [1..1] │ └─ <Prtry> │

Clearing system proprietary code X Only code "EKS" is allowed.

19.1.10.1.8 [0..1] ├┬ <PmtTpInf>

19.1.14.1.3 [1..1] │├┬ <SvcLvl>

19.1.14.1.3.1 [1..1] ││└─ <Cd> Service Level Code X Only code "SEPA" is allowed.

19.1.14.1.4 [0..1] │├┬ <LclInstrm> │││

Local Instrument

79

19.1.14.1.4.1 {Or ││├─ <Cd>

│││

│││

Service code X Only ISO 20022 codes are allowed


as 19.1.14.1.4.2.

19.1.14.1.4.2 Or} ││└─ <Prtry>

││

User community specific

instrument information


19.1.14.1.4.1.

19.1.14.1.6 [0..1] │└┬ <CtgyPurp> Category Purpose

19.1.14.1.6.1 {Or │ ├─ <Cd>

│ │

│ │



as 19.1.14.1.6.2.

19.1.14.1.6.2 Or} │ └─ <Prtry>

│


19.1.14.1.6.1.

19.1.10.1.11 [0..1] ├┬ <RmtInf> Remittance Information

19.1.10.10.1 [1..1] │├─ <Ustrd> ││


19.1.10.10.2.

19.1.10.10.2 [1..1] │└┬ <Strd> │ │

│ │

│ │

│ │

│ │




characters.


19.1.6.1.1 [1..1] │ ├┬ <Tp> │ ││

Creditor reference information type Allowed to use with 19.1.6.1.2.

19.1.6.1.1.1 [1..1] │ │├┬ <CdOrPrtry>

19.1.6.1.1.1.1 [1..1] │ ││└─ <Cd> │ ││


code


19.1.6.1.1.2 [0..1] │ │└─ <Issr> │ │


information type

X

19.1.6.1.2 [1..1] │ └─ <Ref> │

Reference assigned by the creditor X Allowed to use with 19.1.6.1.1.

19.1.10.1.12 [0..1] ├┬ <UltmtDbtr> Ultimate debtor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Name X


19.1.12.4.1 {Or │ ├┬ <OrgId> Organisation identification Allowed to use with 19.1.12.4.2.



80

│ │ │

19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.

19.1.11.2.2.3 [0..1] │ │ └─ <Issr> │ │

Issuer of identifier X

19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.






19.1.12.1.4 [1..1] │ │└─ <CtryOfBirth> │ │



19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.13 [0..1] ├┬ <Dbtr> Debtor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Debtor name X

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address

19.1.17.1.9 [0..1] │ │├─ <Ctry> │ ││

Country X Only ISO 3166 Alpha-2 codes are allowed.

81

19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │


are allowed.


19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││


19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.

19.1.11.2.2.3 [0..1] │ │ └─ <Issr> │ │

Issuer of identifier X

19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.






19.1.12.1.4 [1..1] │ │└─ <CtryOfBirth> │ │



19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


82


19.1.1.1.1 [1..1] │└┬ <Id> Identification

19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

19.1.10.1.15 [1..1] ├┬ <DbtrAgt> Debtor Agent


19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X



19.1.7.4.1 [1..1] │ └─ <BICFI> BIC X

19.1.10.1.19 [0..1] ├┬ <Cdtr> Creditor

19.1.12.3.1 [1..1] │└┬ <Pty> Party

19.1.11.3.1 [0..1] │ ├─ <Nm> Creditor name X

19.1.11.3.2 [0..1] │ ├┬ <PstlAdr> Address


19.1.17.1.10 [0..2] │ │└─ <AdrLine> │ │


allowed.


19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││


19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <AnyBIC> BIC X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.




83



19.1.12.1.4 [1..1] │ │└─ <CtryOfBirth> │ │



19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.



19.1.1.1.1 [1..1] │└┬ <Id> │ │

Creditor account identification

19.1.2.1.1 [1..1] │ └─ <IBAN> IBAN X

19.1.10.1.21 [0..1] ├┬ <UltmtCdtr> Ultimate creditor

19.1.12.3.1 [1..1] │└┬ <Pty> Party



19.1.12.4.1 {Or │ ├┬ <OrgId>

│ ││


19.1.12.4.2.

19.1.11.2.1 [0..1] │ │├─ <BICOrBEI> BIC or BEI X

19.1.11.2.2 [0..1] │ │└┬ <Othr> │ │ │


19.1.11.2.2.1 [1..1] │ │ ├─ <Id> │ │ │

Identifier X


19.1.11.2.2.2.1 {Or │ │ │├─ <Cd>

│ │ ││

│ │ ││



19.1.11.2.2.2.2.

19.1.11.2.2.2.2 Or} │ │ │└─ <Prtry>

│ │ │


19.1.11.2.2.2.1.


84

19.1.12.4.2 Or} │ └┬ <PrvtId>

│ │


19.1.12.4.1.






19.1.12.1.4 [1..1] │ │└─ <CtryOfBirth> │ │



19.1.12.2.2.1 [1..1] │ ├─ <Id> │ │

Identifier X


19.1.12.2.2.2.1 {Or │ │├─ <Cd>

│ ││

│ ││



19.1.12.2.2.2.2.

19.1.12.2.2.2.2 Or} │ │└─ <Prtry>

│ │


19.1.12.2.2.2.1.


19.1.10.1.22 [0..1] └┬ <Purp> Payment purpose


5.12.5. Change request information structure


18.4.4 [1..1] └┬ <Mod> Modification

18.4.4.7 [1..1] └─ <IntrBkSttlmDt> Value Date X

5.12.6. Structure of instructions for the assignee


18.4.5 [0..1] └┬ <InstrForAssgne> Instruction For Assignee

19.1.13.3.1 [1..1] ├─ <Cd> Code X Only code "INQR" is allowed.

19.1.13.3.2 [1..1] └─ <InstrInf> Instruction Information X

85

5.13. Sets of codes allowed to be used

5.13.1. Local instruments ISO codes

Table 1

ISO 20022 ExternalLocalInstrument1Code

Available at https://www.iso20022.org/external_code_list.page "External Code Sets

spreadsheet" sheet 7-LocalInstrument.

5.13.2. Payment purpose category ISO codes

Table 2

ISO 20022 ExternalCategoryPurpose1Code

Available at

https://www.iso20022.org/external_code_list.page "External Code Sets spreadsheet"

sheet 4-CategoryPurpose.

5.13.3. Organisation identification type codes

Table 3

ISO 20022 ExternalOrganisationIdentification1Code

Available at


sheet 9-OrganisationIdentification.

5.13.4. Person identification codes

Table 4

ISO 20022 ExternalPersonIdentification1Code

Available at


sheet 10-PersonIdentification.

Where a natural person is identified by way of its ID number, the appropriate natural

person's identification type code shall be "NIDN".

5.13.5. Payment purpose ISO codes

Table 5

ISO 20022 ExternalPurpose1Code

Available at


sheet 11-Purpose.

https://www.iso20022.org/external_code_list.page





86

5.13.6. Message return reason codes

Table 6 No. Code Explanation

1. AC01 Incorrect account number format or account number does not exist.

2. AC04 The account is closed.

3. AC06 The account is blocked.

4. AG01 Crediting funds to such an account type is not allowed.

5. AG02 The bank operation code indicated in the message does not correspond to the

creditor.

6. AM05 Duplicate message

7. BE04 The creditor's address necessary to execute the payment is missing or is

incorrect.

8. CNOR Creditor agent is not registered under this BIC in the CSM

9. FOCR The payment returned as per SEPA payment cancellation request.

10. MD07 Ultimate creditor has deceased.

11. MS02 No reason for return was provided by the ultimate creditor.

12. MS03 No reason for return was provided by the agent.

13. RC01 The BIC indicated in the message is inconsistent with the format or does not

exist.

14. RR01 Debtor account indication or unique identification necessary to meet regulatory

requirements is incomplete or missing.

15. RR02 Debtor name or address does not meet regulatory requirements.

16. RR03 Creditor name or address does not meet regulatory requirements.

17. RR04 Other non-compliance with regulatory requirements.

5.13.7. Cancellation reason codes of the clearing service


1. TECH Erroneous payment due to technical issues.

2. FRAD Fraudulent originated payment..

3. AC03 Wrong IBAN.

4. AM09 Wrong amount.

5.13.8. ISO codes for resolution of investigation reason


1. CUST Beneficiary’s Refusal.

2. LEGL Legal restrictions.

5.13.9. Clearing service codes for resolution of investigation reason


1. AC04 Account is closed.

2. AM04 Insufficient funds on the account.

3. NOAS No response from beneficiary.

4. NOOR The original payment message has not been received.

5. ARDT The message has already been returned.

87

5.13.10. Resolution of investigation (response to the investigation request) status codes


1. ACNR SEPA claim of non-receipt is accepted. Payment has been credited to the

beneficiary's account.

2. RJNR SEPA claim of non-receipt is rejected.

3. ACVA SEPA claim for value date correction is accepted. Value date will be corrected

as per the request.

4. RJVA SEPA claim for value date correction is rejected, value date of the payment

message does not match criteria set in the SEPA Credit Transfer Scheme

Rulebook.

5. CVAA SEPA claim for value date correction is rejected, the payment has been credited

to the beneficiary's account on the value date indicated in the payment message.

6. MODI SEPA claim for value date correction is executed.

5.13.11. Response to the SEPA claim of non-receipt codes


1. NOOR No original transaction received

2. RNPR Original transaction received but not processable

3. ARJT Already rejected transaction

4. ARDT Already returned transaction

5. RR04 Regulatory reason

5.14. Formats of message data fields

Data formats

ISO element <AddtlInf>

ISO element name Additional Information

ISO No Message type

3.27 pacs.004.001.02

4.46 camt.056.001.01

4.94 camt.029.001.03

Data type Max105Text

Format maxLength: 105

minLength: 1

ISO element <Adrline>

ISO element name Address Line ISO No Message type

9.1.11 pacs.008.001.02

9.1.11 pacs.004.001.02

6.1.638 camt.056.001.01

6.1.803 camt.056.001.01

6.1.638 camt.029.001.03

6.1.803 camt.029.001.03

10.1.13.1.10 pacs.028.001.01

19.1.17.1.10 camt.029.001.08

19.1.17.1.10 camt.027.001.06

19.1.17.1.10 camt.087.001.05

Data type Max70Text


minLength: 1

88

ISO element <AnyBIC>

ISO element name Any BIC

ISO No Message type

10.1.9.2.1 pacs.028.001.01

19.1.11.2.1 camt.029.001.08

19.1.11.2.1 camt.027.001.06

19.1.11.2.1 camt.087.001.05

Data type BICIdentifier

Format [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

ISO element <Amt>

ISO element name Amount ISO No Message type

3.18 pacs.004.001.02

19.1.9.6.1 camt.029.001.08

19.1.4.1.1 camt.029.001.08

Data type CurrencyAndAmount

Format fractionDigits: 2

minInclusive: 0.01

maxInclusive: 999999999.99

totalDigits: 18

CurrencyCode

[A-Z]{3,3}

Notes Only currency code "EUR" is allowed.

The amount must be 0.01 or more, and it must not exceed 999 999 999.99.

No more than two digits after the decimal point.

ISO element <BIC>

ISO element name BIC

ISO No Message type

6.1.1 pacs.008.001.02

6.1.1 pacs.004.001.02

6.1.1 pacs.002.001.03

2.1.1 camt.056.001.01

6.1.685 camt.056.001.01

6.1.739 camt.056.001.01

2.1.1 camt.029.001.03

6.1.685 camt.056.001.01

6.1.739 camt.056.001.01



ISO element <BICFI>

ISO element name BICFI

ISO No Message type

10.1.7.4.1 pacs.028.001.01

19.1.7.4.1 camt.029.001.08

19.1.7.4.1 camt.027.001.06



89

ISO element <BICOrBEI>

ISO element name BIC Or BEI

ISO No Message type

9.1.14 pacs.008.001.02

9.1.14 pacs.004.001.02

9.1.14 camt.002.001.03

5.1.14 camt.056.001.01

6.1.598 camt.056.001.01

6.1.806 camt.056.001.01

6.1.863 camt.056.001.01

5.1.14 camt.029.001.03

6.1.598 camt.029.001.03

6.1.641 camt.029.001.03

6.1.806 camt.029.001.03

6.1.863 camt.029.001.08

19.1.11.2.1 camt.087.001.05

10.1.9.2.1 pacs.028.001.01

Data type AnyBICIdentifier

Format A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1}

ISO element <BirthDt>

ISO element name BirthDate

ISO No Message type

9.1.23 pacs.008.001.02

9.1.23 pacs.004.001.02

6.1.607 camt.056.001.01

6.1.650 camt.056.001.01

6.1.815 camt.056.001.01

6.1.872 camt.056.001.01

6.1.607 camt.029.001.03

6.1.650 camt.029.001.03

6.1.815 camt.029.001.03

6.1.872 camt.029.001.03

19.1.12.1.1 camt.029.001.08

19.1.12.1.1 camt.027.001.06

19.1.12.1.1 camt.087.001.05

10.1.12.1.1 pacs.028.001.01

Data type ISODate

ISO element <Cd> (<CdOrPrtry>)

ISO element name Code

ISO No Message type

2.100 pacs.008.001.02

3.109 pacs.004.001.02

6.1.492 camt.056.001.01

6.1.492 camt.029.001.03

19.1.6.1.1.1.1 camt.029.001.08

19.1.6.1.1.1.1 camt.027.001.06

19.1.6.1.1.1.1 camt.087.001.05

10.1.6.1.1.1.1 pacs.028.001.01

Data type Code

Notes Only code "SCOR" is allowed.

90

ISO element <Cd> (<ClmNonRctDtls>)


ISO No Message type

5.4.6.2.1 pacs.029.001.08

Data type Code

Notes Only the listed codes are allowed (Table 11).

ISO element <Cd> (<CtgyPurp>)


ISO No Message type

2.16 pacs.008.001.02

3.62 pacs.004.001.02

6.1.244 camt.056.001.01

6.1.244 camt.029.001.03

19.1.14.1.6.1 camt.029.001.08

19.1.14.1.6.1 camt.027.001.06

19.1.14.1.6.1 camt.087.001.05

10.1.11.2.6.1 pacs.028.001.01

Data type Code

Notes Only the listed codes are allowed (see "Notes" in the message structure table).

ISO element <Cd> (<InstrForAssgne>)


ISO No Message type

1.1 camt.027.001.06

Data type Code

Notes

ISO element <Cd> (<LclInstrm>)


ISO No Message type

2.13 pacs.008.001.02

3.58 pacs.004.001.02

6.1.240 camt.056.001.01

6.1.240 camt.029.001.03

19.1.14.1.4.1 camt.029.001.08

Data type ExternalLocalInstrument1Code


minLength: 1

Notes Only ISO 20022 codes are allowed (Table 1).

ISO element <Cd> (<Purp>)


ISO No Message type

2.65 pacs.008.001.02

19.1.10.11.1 camt.029.001.08

19.1.10.11.1 camt.027.001.06

19.1.10.11.1 camt.087.001.05

Data type Code

Notes Only ISO 20022 codes are allowed (Table 5). Cannot be used at the same

time as 2.54.

91

ISO element <Cd> (<Rsn>)


ISO No Message type

2.10 pacs.002.001.03

3.9 pacs.002.001.03

Data type Code

Notes Only the listed codes are allowed (see "Notes" in the message structure

table).



ISO No Message type

3.25 pacs.004.001.02

Data type Code




ISO No Message type

4.44 camt.056.001.01

Data type Code

Notes Only code "DUPL" is allowed.



ISO No Message type

4.92 camt.029.001.03

Data type Code




ISO No Message type

19.1.9.6.4.1 camt.029.001.08

Data type Code

Notes Only code "VADA" is allowed.

92

ISO element <Cd> (<SchmeNm>)


ISO No Message type

9.1.18 pacs.008.001.02

9.1.18 pacs.004.001.02

6.1.602 camt.056.001.01

6.1.645 camt.056.001.01

6.1.810 camt.056.001.01

6.1.867 camt.056.001.01

6.1.602 camt.029.001.03

6.1.645 camt.029.001.03

6.1.810 camt.029.001.03

6.1.867 camt.029.001.03

19.1.11.2.2.2.1 camt.029.001.08

19.1.11.2.2.2.1 camt.027.001.06

19.1.11.2.2.2.1 camt.087.001.05

10.1.9.2.2.2.1 pacs.028.001.01

Data type Code


ISO element <Cd> (<SvcLvl>)


ISO No Message type

2.10 pacs.008.001.02

3.55 pacs.004.001.02

6.1.237 camt.056.001.01

6.1.237 camt.029.001.03

19.1.14.1.3.1 camt.029.001.08

19.1.14.1.3.1 camt.027.001.06

19.1.14.1.3.1 camt.087.001.05

10.1.11.2.3.1 pacs.028.001.01

Data type Code

Notes Only code "SEPA" is allowed.

ISO element <Cd> (<UltmtDbtr>/<PrvtId>)


ISO No Message type

9.1.30 pacs.008.001.02

9.1.30 pacs.004.001.02

6.1.614 camt.056.001.01

6.1.657 camt.056.001.01

6.1.822 camt.056.001.01

6.1.879 camt.056.001.01

6.1.614 camt.029.001.03

6.1.657 camt.029.001.03

6.1.822 camt.029.001.03

6.1.879 camt.029.001.03

19.1.12.2.2.2.1 camt.029.001.08

19.1.12.2.2.2.1 camt.027.001.06

19.1.12.2.2.2.1 camt.087.001.05

10.1.12.2.2.2.1 pacs.028.001.01

Data type Code


93

ISO element <ChrgBr>

ISO element name Charge Bearer

ISO No Message type

2.33 pacs.008.001.02

3.16 pacs.004.001.02

Data type Code

Notes Only code "SLEV" is allowed (Settlement failed).

ISO element <CityOfBirth>

ISO element name City Of Birth

ISO No Message type

9.1.25 pacs.008.001.02

9.1.25 pacs.004.001.02

6.1.609 camt.056.001.01

6.1.652 camt.056.001.01

6.1.817 camt.056.001.01

6.1.874 camt.056.001.01

6.1.609 camt.029.001.03

6.1.652 camt.029.001.03

6.1.817 camt.029.001.03

6.1.874 camt.029.001.03

19.1.12.1.3 camt.029.001.08

19.1.12.1.3 camt.027.001.06

19.1.12.1.3 camt.087.001.05

10.1.12.1.3 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <Conf>

ISO element name Confirmation ISO No Message type

3.1 camt.029.001.03

5.4.3.1 camt.029.001.08

Data type Code

ISO element <CreDtTm>

ISO element name Creation Date Time

ISO No Message type

1.2 pacs.008.001.02

1.2 pacs.004.001.02

1.2 pacs.002.001.03

1.8 camt.056.001.01

1.8 camt.029.001.03

19.1.9.13.4 camt.029.001.08

19.1.9.13.4 camt.027.001.06

19.1.9.13.4 camt.087.001.05

9.4.1.2 pacs.028.001.01

Data type ISODateTime

94

ISO element <Ctry>

ISO element name Country

ISO No Message type

9.1.10 pacs.008.001.02

9.1.10 pacs.004.001.02

6.1.637 camt.056.001.01

6.1.802 camt.056.001.01

6.1.637 camt.029.001.03

6.1.802 camt.029.001.03

19.1.17.1.9 camt.029.001.08

19.1.17.1.9 camt.027.001.06

19.1.17.1.9 camt.087.001.05

10.1.13.1.9 pacs.028.001.01

Data type CountryCode

Format [A-Z]{2,2}

ISO element <CtryOfBirth>

ISO element name Country Of Birth

ISO No Message type

9.1.26 pacs.008.001.02

9.1.26 pacs.004.001.02

6.1.610 camt.056.001.01

6.1.653 camt.056.001.01

6.1.818 camt.056.001.01

6.1.875 camt.056.001.01

6.1.610 camt.029.001.03

6.1.653 camt.029.001.03

6.1.818 camt.029.001.03

6.1.875 camt.029.001.03

19.1.12.1.4 camt.029.001.08

19.1.12.1.4 camt.027.001.06

19.1.12.1.4 camt.087.001.05

10.1.12.1.4 pacs.028.001.01

Data type CountryCode

Format [A-Z]{2,2}

ISO element <CxlId>

ISO element name Cancellation Identification

ISO No Message type

4.22 camt.056.001.01



minLength: 1

ISO element <CxlStsId>

ISO element name Cancellation Status Identification

ISO No Message type

4.73 camt.029.001.03

Data type Max35Text


minLength: 1

Space is not allowed.

95

ISO element <DtldCtrlSum>

ISO element name Detailed Control Sum

ISO No Message type

2.16 pacs.002.001.03



minInclusive: 0

totalDigits: 18

CurrencyCode

[A-Z]{3,3}


The amount must be 0.01 or more, and it must not exceed

999 999 999 999 999.99.


ISO element <DtldNbOfTxs>

ISO element name Detailed Number Of Transactions

ISO No Message type

2.14 pacs.002.001.03

Data type Max15NumericText

Format [0-9]{1,15}

ISO element <DtldSts>

ISO element name Detailed Status

ISO No Message type

2.15 pacs.002.001.03

Data type Code

Notes Only the listed codes are allowed (see "Notes" in the message structure table).

ISO element <DtPrcd>

ISO element name Date Processed

ISO No Message type

5.4.6.1.1 camt.029.001.08


ISO element <EndToEndId>

ISO element name End To End Identification

ISO No Message type

2.3 pacs.008.001.02

Data type Max35Text


minLength: 1

ISO element <GrpSts>

ISO element name Group Status

ISO No Message type

2.6 pacs.002.001.03

Data type Code

96

ISO element <IBAN>

ISO element name IBAN

ISO No Message type

1.1.1 pacs.008.001.02

1.1.1 pacs.004.001.02

6.1.671 camt.056.001.01

6.1.836 camt.056.001.01

6.1.671 camt.029.001.03

6.1.836 camt.029.001.03

19.1.2.1.1 camt.029.001.08

19.1.2.1.1 camt.027.001.06

19.1.2.1.1 camt.087.001.05

10.1.2.1.1 pacs.028.001.01

Data type IBAN2007Identifier

Format [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}

ISO element <Id> (<Assgnmt>)

ISO element name Identification ISO No Message type

1.1 camt.056.001.01

1.1 camt.029.001.03

Data type Max35Text


minLength: 1


ISO element <Id> (<RslvdCase>;<Case>)

ISO element name Identification ISO No Message type

19.1.9.15.1 camt.029.001.08

19.1.9.15.1 camt.027.001.06

19.1.9.15.1 camt.087.001.05

Data type Max35Text


minLength: 1


ISO element <Id> (<UltmtDbtr>/<OrgId>)

ISO element name Identification

ISO No Message type

9.1.16 pacs.008.001.02

9.1.16 pacs.004.001.02

6.1.600 camt.056.001.01

6.1.643 camt.056.001.01

6.1.808 camt.056.001.01

6.1.865 camt.056.001.01

6.1.600 camt.029.001.03

6.1.643 camt.029.001.03

6.1.808 camt.029.001.03

6.1.865 camt.029.001.03

19.1.11.2.2.1 camt.029.001.08

19.1.11.2.2.1 camt.027.001.06

19.1.11.2.2.1 camt.087.001.05

10.1.9.2.2.1 pacs.028.001.01

Data type Max35Text


minLength: 1

97

ISO element <Id> (<UltmtDbtr>/<PrvtId>)

ISO element name Identification

ISO No Message type

9.1.28 pacs.008.001.02

9.1.28 pacs.004.001.02

6.1.612 camt.056.001.01

6.1.655 camt.056.001.01

6.1.820 camt.056.001.01

6.1.877 camt.056.001.01

6.1.612 camt.029.001.03

6.1.655 camt.029.001.03

6.1.820 camt.029.001.03

6.1.877 camt.029.001.03

19.1.12.2.2.1 camt.029.001.08

19.1.12.2.2.1 camt.027.001.06

19.1.12.2.2.1 camt.087.001.05

10.1.12.2.2.1 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <InstrId>

ISO element name Instruction Identification

ISO No Message type

2.2 pacs.008.001.02

Data type Max35Text


minLength: 1


ISO element <InstrInf>

ISO element name Instruction Information

ISO No Message type

1.2 camt.027.001.06



minLength: 1


98

ISO element <IntrBkSttlmAmt>

ISO element name Interbank Settlement Amount ISO No Message type

2.18 pacs.008.001.02

3.21 pacs.002.001.03

6.1.0 camt.029.001.03

19.1.10.1.1 camt.029.001.08

9.4.3.10.1 pacs.028.001.01



minInclusive: 0.01


totalDigits: 18

CurrencyCode

[A-Z]{3,3}


The amount must be 0.01 or more, and it must not exceed

999 999 999 999 999.99.


ISO element <IntrBkSttlmDt>

ISO element name Interbank Settlement Date

ISO No Message type

1.7 pacs.008.001.02

1.11 pacs.004.001.02

3.35 pacs.004.001.02

3.27 pacs.002.001.03

6.1.6 camt.029.001.03

19.1.10.1.3 camt.029.001.08

19.1.9.7.2 camt.029.001.08

19.1.9.13.4 camt.027.001.06

18.4.4.7 camt.087.001.05

9.4.3.10.3 pacs.028.001.01


ISO element <Issr> (<CdtrRefInf>)

ISO element name Issuer

ISO No Message type

2.102 pacs.008.001.02

3.111 pacs.004.001.02

6.1.494 camt.056.001.01

6.1.494 camt.029.001.03

19.1.6.1.1.2 camt.029.001.08

19.1.6.1.1.2 camt.027.001.06

19.1.6.1.1.2 camt.087.001.05

10.1.6.1.1.1.2 pacs.028.001.01

Data type Max35Text


minLength: 1

99

ISO element <Issr> (<OrgId>)


ISO No Message type

9.1.20 pacs.008.001.02

9.1.20 pacs.004.001.02

6.1.604 camt.056.001.01

6.1.647 camt.056.001.01

6.1.812 camt.056.001.01

6.1.869 camt.056.001.01

6.1.604 camt.029.001.03

6.1.647 camt.029.001.03

6.1.812 camt.029.001.03

6.1.869 camt.029.001.03

19.1.11.2.2.3 camt.029.001.08

19.1.11.2.2.3 camt.027.001.06

19.1.11.2.2.3 camt.087.001.05

10.1.9.2.2.3 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <Issr> (<UltmtDbtr>/<PrvtId>)


ISO No Message type

9.1.32 pacs.008.001.02

9.1.32 pacs.004.001.02

6.1.616 camt.056.001.01

6.1.659 camt.056.001.01

6.1.824 camt.056.001.01

6.1.881 camt.056.001.01

6.1.616 camt.029.001.03

6.1.659 camt.029.001.03

6.1.824 camt.029.001.03

6.1.881 camt.029.001.03

19.1.12.2.2.3 camt.029.001.08

19.1.12.2.2.3 camt.027.001.06

19.1.12.2.2.3 camt.087.001.05

10.1.12.2.2.3 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <MsgId> ISO element name Message Identification

ISO No 1 Message type

1.1 pacs.008

1.1 pacs.004

1.1 pacs.002

9.4.1.1 pacs.028

Data type3 Max35Text

Format3 maxLength: 35

minLength: 1


100

ISO element <NbOfTxs>

ISO element name Number Of Transactions

ISO No Message type

1.4 pacs.008.001.02

1.7 pacs.004.001.02

1.8 camt.056.001.01


Format [0-9]{1,15}

ISO element <Nm>

ISO element name Name

ISO No Message type

9.1.0 pacs.008.001.02

9.1.0 pacs.004.001.02

6.1.584 camt.056.001.01

6.1.627 camt.056.001.01

6.1.792 camt.056.001.01

6.1.849 camt.056.001.01

6.1.584 camt.029.001.03

6.1.627 camt.029.001.03

6.1.792 camt.029.001.03

6.1.849 camt.029.001.03

19.1.11.3.1 camt.029.001.08

19.1.11.3.1 camt.027.001.06

19.1.11.3.1 camt.087.001.05

10.1.9.1.1 pacs.028.001.01

Data type Max70Text


minLength: 1

ISO element <OrgnlCtrlSum>

ISO element name Original Control Sum

ISO No Message type

2.5 pacs.002.001.03



minInclusive: 0

totalDigits: 18

CurrencyCode

[A-Z]{3,3}




101

ISO element <OrgnlEndToEndId>

ISO element name Original End To End Identification

ISO No Message type

3.7 pacs.004.001.02

3.3 camt.002.001.03

4.34 camt.056.001.01

4.85 camt.029.001.03

5.4.5.6 camt.029.001.08

19.1.9.12.3 camt.027.001.06

19.1.9.12.3 camt.087.001.05

9.4.3.3 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <OrgnlInstrId>

ISO element name Original Instruction Identification

ISO No Message type

3.6 pacs.004.001.02

3.2 camt.002.001.03

4.33 camt.056.001.01

4.84 camt.029.001.03

5.4.5.5 camt.029.001.08

5.4.5.5 camt.027.001.06

5.4.5.5 camt.087.001.05

9.4.3.3 pacs.028.001.01

Data type Max35Text


minLength: 1


ISO element <OrgnlIntrBkSttlmAmt>

ISO element name Original Interbank Settlement Amount ISO No Message type

3.10 pacs.004.001.02

4.37 camt.056.001.01

4.100 camt.029.001.03



minInclusive: 0.01


totalDigits: 18

CurrencyCode

[A-Z]{3,3}



ISO element <OrgnlIntrBkSttlmDt>

ISO element name Original Interbank Settlement Date

ISO No Message type

4.38 camt.056.001.01


102

ISO element <OrgnlMsgId>

ISO element name Original Message Identification

ISO No Message type

3.3 pacs.004.001.02

2.1 pacs.002.001.03

4.30 camt.056.001.01

4.81 camt.029.001.03

19.1.10.2.1 camt.029.001.08

19.1.9.12.1.1 camt.027.001.06

19.1.9.12.1.1 camt.087.001.05

9.4.2.1 pacs.028.001.01

Data type Max35Text


minLength: 1


ISO element <OrgnlMsgNmId>

ISO element name Original Message Name Identification

ISO No Message type

3.4 pacs.004.001.02

2.2 pacs.002.001.03

4.31 camt.056.001.01

4.82 camt.029.001.03

19.1.10.2.2 camt.029.001.08

19.1.9.12.1.2 camt.027.001.06

19.1.9.12.1.2 camt.087.001.05

9.4.2.2 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <OrgnlNbOfTxs>

ISO element name Original Number Of Transactions

ISO No Message type

2.4 pacs.002.001.03


Format [0-9]{1,15}

ISO element <OrgnlTxId>

ISO element name Original Transaction Identification

ISO No Message type

3.8 pacs.004.001.02

3.4 camt.002.001.03

4.35 camt.056.001.01

4.86 camt.029.001.03

5.4.5.7 camt.029.001.08

19.1.9.12.4 camt.027.001.06

19.1.9.12.4 camt.087.001.05

9.4.3.5 pacs.028.001.01

Data type Max35Text


minLength: 1


103

ISO element <Prtry> (<ClrSys>)

ISO element name Proprietary

ISO No Message type

1.13 pacs.008.001.02

1.17 pacs.004.001.02

6.1.70 camt.056.001.01

6.1.70 camt.029.001.03

19.1.19.2.3.2 camt.029.001.08

19.1.19.2.3.2 camt.027.001.06

19.1.19.2.3.2 camt.087.001.05

10.1.15.2.3.2 pacs.028.001.01

Data type Code

Notes Only code "EKS" is allowed.

ISO element <Prtry> (<CtgyPurp>)


ISO No Message type

2.17 pacs.008.001.02

3.63 pacs.004.001.02

6.1.245 camt.056.001.01

6.1.245 camt.029.001.03

19.1.14.1.6.2 camt.029.001.08

19.1.14.1.6.2 camt.027.001.06

19.1.14.1.6.2 camt.087.001.05

10.1.11.2.6.2 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <Prtry> (<LclInstrm>)


ISO No Message type

2.14 pacs.008.001.02

3.59 pacs.004.001.02

6.1.241 camt.056.001.01

6.1.241 camt.029.001.03

19.1.14.1.4.2 camt.029.001.08

10.1.11.2.4.2 pacs.028.001.01

Data type Max35Text


minLength: 1

Notes

ISO element <Prtry> (<Rsn>)


ISO No Message type

2.11 pacs.002.001.03

Data type Code

Notes Only codes listed in the notes of the respective message element are allowed.

104

ISO element <Prtry> (<SchmeNm>) ISO element name Proprietary ISO No Message type

9.1.19 pacs.008.001.02

9.1.19 pacs.004.001.02

6.1.603 camt.056.001.01

6.1.646 camt.056.001.01

6.1.811 camt.056.001.01

6.1.868 camt.056.001.01

6.1.603 camt.029.001.03

6.1.646 camt.029.001.03

6.1.811 camt.029.001.03

6.1.868 camt.029.001.03

19.1.11.2.2.2.2 camt.029.001.08

19.1.11.2.2.2.2 camt.027.001.06

19.1.11.2.2.2.2 camt.087.001.05

10.1.9.2.2.2.2 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <Prtry> (<UltmtDbtr>/<PrvtId>)


ISO No Message type

9.1.31 pacs.008.001.02

9.1.31 pacs.004.001.02

6.1.615 camt.056.001.01

6.1.658 camt.056.001.01

6.1.823 camt.056.001.01

6.1.880 camt.056.001.01

6.1.615 camt.029.001.03

6.1.658 camt.029.001.03

6.1.823 camt.029.001.03

6.1.880 camt.029.001.03

19.1.12.2.2.2.2 camt.029.001.08

19.1.12.2.2.2.2 camt.027.001.06

19.1.12.2.2.2.2 camt.087.001.05

10.1.12.2.2.2.2 pacs.028.001.01

Data type Max35Text


minLength: 1



ISO No Message type

4.93 camt.029.001.03

Data type Max35Text


minLength: 1

Notes Only listed codes are allowed (Table 9).

105



ISO No Message type

4.45 camt.056.001.01

Data type Max35Text


minLength: 1

ISO element <PrvcOfBirth>

ISO element name Province Of Birth

ISO No Message type

9.1.24 pacs.008.001.02

9.1.24 pacs.004.001.02

6.1.608 camt.056.001.01

6.1.651 camt.056.001.01

6.1.816 camt.056.001.01

6.1.873 camt.056.001.01

6.1.608 camt.029.001.03

6.1.651 camt.029.001.03

6.1.816 camt.029.001.03

6.1.873 camt.029.001.03

19.1.12.1.1 camt.029.001.08

19.1.12.1.1 camt.027.001.06

19.1.12.1.1 camt.087.001.05

10.1.12.1.1 pacs.028.001.01

Data type Max35Text


minLength: 1

ISO element <Ref>

ISO element name Reference

ISO No Message type

2.103 pacs.008.001.02

3.112 pacs.004.001.02

6.1.495 camt.056.001.01

6.1.495 camt.029.001.03

19.1.6.1.1.2 camt.029.001.08

19.1.6.1.1.2 camt.027.001.06

19.1.6.1.1.2 camt.087.001.05

Data type Max35Text


minLength: 1

106

ISO element <RtrdInstdAmt>

ISO element name Returned Instructed Amount ISO No Message type

3.5 pacs.004.001.02



minInclusive: 0.01


totalDigits: 18

CurrencyCode

[A-Z]{3,3}




Must be present along with 3.17. Contains the amount to be returned before

the deduction of charges. Only allowed to be used where the message is a

reply to a SEPA payment cancellation request message.

ISO element <RtrdIntrBkSttlmAmt>

ISO element name Returned Interbank Settlement Amount ISO No Message type

3.5 pacs.004.001.02



minInclusive: 0.01


totalDigits: 18

CurrencyCode

[A-Z]{3,3}




Where the message is a response to an instant SEPA payment cancellation

request message, then <RtrdIntrBkSttlmAmt>=<OrgnlIntrBkSttlmAmt>-

<ChrgsInf><Amt>.

Where the message is not a response to an instant SEPA payment

cancellation request message, then <RtrdIntrBkSttlmAmt>=<OrgnlIntrBkSttlmAmt>.

ISO element <RtrId>

ISO element name Return Identification

ISO No Message type

3.1 pacs.004.001.02

Data type Max35Text


minLength: 1


ISO element <StsId>

ISO element name Status Identification

ISO No Message type

3.1 pacs.002.001.03

Data type Max35Text


minLength: 1


107

ISO element <StsReqId>

ISO element name Status Request Identification

ISO No Message type

3.1 pacs.028.001.01

Data type Max35Text


minLength: 1


ISO element <SttlmMtd>

ISO element name Settlement Method

ISO No Message type

1.9 pacs.008.001.02

1.13 pacs.004.001.02

3.40 pacs.004.001.02

6.1.53 camt.056.001.01

6.1.53 camt.029.001.03

19.1.19.2.1 camt.029.001.08

19.1.19.2.1 camt.027.001.06

19.1.19.2.1 camt.087.001.05

9.4.3.10.3 pacs.028.001.01

Data type Code

Notes Only code "CLRG" is allowed.

ISO element <TtlIntrBkSttlmAmt>

ISO element name Total Interbank Settlement Amount ISO No Message type

1.6 pacs.008.001.02

Data type ActiveCurrencyAndAmount


minInclusive: 0.01

maxInclusive: 999999999999999.99

totalDigits: 18

CurrencyCode "EUR"

ISO element <TtlRtrdIntrBkSttlmAmt>

ISO element name Total Returned Interbank Settlement Amount ISO No Message type

1.10 pacs.004.001.02

Data type ActiveCurrencyAndAmount


minInclusive: 0.01

maxInclusive: 999999999999999.99

totalDigits: 18

CurrencyCode "EUR"

ISO element <TxCxlSts>

ISO element name Transaction Cancellation Status

ISO No Message type

4.73 camt.029.001.03

Data type Code

Notes Only the listed codes are allowed (see "Notes" in the message structure

table).

108

ISO element <TxId>

ISO element name Transaction Identification

ISO No Message type

2.4 pacs.002.001.03

Data type Max35Text


minLength: 1


ISO element <TxSts> ISO element name Transaction Status ISO No Message type

3.5 pacs.002.001.03

Data type Code

Notes Only the codes listed in the Notes of the respective message element are

allowed.

ISO element <Ustrd>

ISO element name Unstructured

ISO No Message type

2.76 pacs.008.001.02

3.85 pacs.004.001.02

6.1.468 camt.056.001.01

6.1.468 camt.029.001.03

19.1.10.10.1 camt.029.001.08

19.1.10.10.1 camt.027.001.06

19.1.10.10.1 camt.087.001.05

9.4.3.10.11.1 pacs.028.001.01



minLength: 1

6. File and message validation

6.1. File validation

When accepting a file, the clearing service shall perform the following validation checks:

Table 12 No. Name of the

validation check

Description Error

code

1. File name Is the file name generated in line with the provisions of

Section 4 herein?

–

1.1 File type Does the file name contain the allowed file type

(Section 4)?

C01

1.2 Date Does the date, expressed as the number of days from the

beginning of the year, correspond to the value date with

which payments are accepted by the clearing service?

C02

1.3 Sequence number Does the file sequence number correspond to the format

specified in Section 4 herein?

C03

1.4 File extension Does the file extension correspond to the cryptographic

package used?

C04

1.5 File name length Does the file name length correspond to the one defined in

Section 4 herein?

C05

1.6 File name uniqueness Is the name of the file received from the file sender on the

respective value date unique?

C06

109

1.7 Number of messages

per file

Has the maximum number of messages allowed per file not

been exceeded?

C16

2. File authenticity Is the file received from the file sender authentic, based on

the cryptographic package used?

–

2.1 Status of the file

sender

Has the file sender concluded an agreement with Latvijas

Banka on electronic settlement in the clearing service?

C08

2.2 File sender account Has the file sender's settlement account with Latvijas

Banka not been closed?

C08

2.3 Information

authenticity

Does the file contain a valid digital signature of the person

authorised by the file sender whose operation has not been

suspended in the clearing service?

C10

2.4 Place of file origin Is the file received from the file sender signed with the

digital signature of the person authorised by the same

entity?

C11

2.5 Validity period of the

key

Does the file contain the digital signature of the authorised

person of the sending bank whose validity period of the

key has not expired?

C12

2.6 Name of the signed

file

Is the file name without extension, prior to its digital

signing, the same as the received and encrypted file name

without extension?

C14

2.7 Number of the signed

files

Does the digitally signed and encrypted file not contain

several files?

C15

3. XML schema

validation

Does the file comply with the XML schema? R10

4. File header Is the file header generated in line with the general rules for

generating the corresponding file header? If errors are

found as a result of the validation checks stated in this

item, the file shall not be accepted for clearing.

–

4.1 File type Does the header contain the allowed file type? R07

4.2 File sender Is the file sender identified by the correct BIC in the

header?

R11

4.3 File recipient Is the file recipient identified by the correct BIC in the

header?

R12

4.4 Test code Is the code of the test system or active system specified

correctly in the header?

R14

4.5 Number of bulks Does the bulk number in the file correspond to the number

indicated in the file header?

R18

If an error is identified in any of the listed validation checks, the entire file is rejected and

the VE type file or QE type file including the respective error code, is sent to the sender

of the file.

6.2. File rejection reason codes

Table 13 No. Code Description

1. A00 File entirely accepted.

2. A01 File partially accepted.

3. C01 File name contains an unauthorised file type.

4. C02 The date in the file name, expressed as the number of days from the beginning of

the year, is not the same as the value date with which the payments are accepted by


5. C03 File sequence number indicated in the file name is incorrect.

6. C04 File extension is not appropriate for the encryption package used.

7. C05 File name length does not correspond to the one defined in Paragraph 4.1 herein.

8. C06 Duplicated file name.

9. C08 The file was received from a sender not authorised to send files.

10. C10 The digital signature in the file received is erroneous, wrong or has the signature of

an authorised person revoked by the participant.

110

11. C11 The file received does not contain the digital signature of the person authorised by

the file sender.

12. C12 The file has been signed with an expired key.

13. C14 Prior to signing the file has had a different name than the digitally signed and

received file (apart from its extension).

14. C15 More than one file has been included in the digitally signed and sent file.

15. C16 The maximum number of messages allowed per file has been exceeded.

16. R07 Incorrect file type in the file header.

17. R10 Contents of the file does not meet the XML schema requirements.

18. R11 Invalid file sender BIC in the file header.

19. R12 Invalid file recipient BIC in the file header.

20. R14 Invalid test or production system's code in the file header.

21. R18 Invalid number of bulks is indicated in the file header.

22. R19 Insufficient liquidity for the payments of the participant who has an obligation to

provide a pre-deposit.

6.3. Bulk validation

Upon the receipt of a file, the clearing service performs the following validation checks

of the bulks included in the file:

Table 14 No. Name of the

validation check

Description Error

code

1. Number of

payments

Does the number of messages in the bulk not exceed the

allowed limit?

B02

2. Number of

payments in a

bulk

Does the message number in the bulk correspond to the number

indicated in the bulk header?

B03

3. Amount of

payments in a

bulk

Does the message amount in the bulk correspond to the amount

indicated in the bulk header?

B05

4. Number of bulks Does the number bulks in the file not exceed the allowed limit? B08

5. All messages

were rejected

Does the bulk contain messages? The bulk has been rejected

due to the rejection of all messages included in it.

B09

6. Bulk sender Is the file sender identified by the correct BIC? B10

7. Bulk recipient Is the file recipient identified by the correct BIC? B11

8. No payments in

the bulk

Does the bulk contain messages? B13

9. Bulk MsgId Is the bulk MsgId not duplicated within the settlement day? B14

10. Value date Is the date in the header the same as the date with which the

payments are accepted by the clearing service?

B15

11. System code Is the system code indicated correctly? B16

6.4. Bulk rejection reason codes


1. B00 The bulk is entirely accepted.

2. B01 The bulk is partially accepted.

3. B02 The maximum number of messages in the bulk has been exceeded.

4. B03 The message number in the bulk does not correspond to the number indicated in

the bulk header.

5. B05 The message amount in the bulk does not correspond to the amount indicated in

the bulk header.

6. B08 The maximum number of bulks in the file has been exceeded.

7. B09 The bulk has been rejected due to the rejection of all messages included in it.

8. B10 Invalid BIC of the bulk sender in the bulk header.

9. B11 The BIC of the bulk recipient shall not be indicated in the bulk header.

10. B12 Invalid <Assgnr> or <Assgne> values in the bulk header.

111

11. B13 Bulk settlement amount is zero.

12. B14 Duplicated message identifier in the bulk header .

13. B15 Incorrect value date.

14. B16 Incorrect clearing system proprietary code.

6.5. Message rejection reason ISO codes


1. AM01 Amount of the message is zero.

2. AM02 Amount of the message exceeds the maximum limit.

3. AM05 The message has been duplicated.

4. DT01 Incorrect value date.

5. ED05 Settlement failed.

6.6. Message rejection reason clearing service codes


1. XD19 An IBAN in the message has failed the ISO 13616 check (2 characters – country

code, 2 characters – check digits, n character – account number with the country

code-specific structure).

2. XT13 The message contains at least one unsupported XML element or it does not

contain at least one mandatory element.

3. XT27 The message contains at least one element with a BIC not included in the routing

table of the clearing service.

4. XT33 At least one XML element is is not in the requiredformat.

5. XT73 The country code is not an existing ISO or SEPA country code.

6. XT85 Messages cannot be sent to this recipient in the current clearing cycle.

7. XT99 The message has been rejected due to other reasons.

6.7. Movement reason clearing service codes


1. F02 The payment message has been moved to the next clearing cycle as a result of

recalculating the multilateral net positions.

Code F02 is followed by the BIC of the participant whose payment message has been

moved to the next clearing cycle due to insufficient funds.

6.8. Rejection reason clearing service codes for excluded message


1. U01 The file sender has been excluded from the clearing.

2. U02 The creditor agent has been excluded from the clearing.

3. U03 The payment message has been rejected as a result of recalculating the multilateral

net positions.

4. U04 Settlement in TARGET2 failed.

112

7. Clearing result file

7.1. TE type file structure

Following each clearing cycle, a TE type file containing the clearing result message shall

be sent to a participant for each its registered BIC. All payment message files included in

the clearing shall be indicated in the message. Each file is allocated one row consisting

of the following sub-fields:

Sub-field Format Explanation

1 4n Sequence number. Clearing result rows are numbered in ascending

sequence, starting with 1. Where a clearing result contains several

messages, the sequence number of each subsequent message follows that

of the previous message.

2 9x File name.

3 1a D – debit or C – credit.

4 6n pacs.008, camt.056, pacs.004 and camt.029 number of messages per file.

5 15d pacs.008 and pacs.004 amount of messages per file.

The last three rows summarise the clearing result (the last row is marked with an n).

Row n-2 "Debit turnover"


1 4n Sequence number.

2 /DRTOTAL/ /DRTOTAL/ denotes debit turnover.

3 D D – debit

4 6n Total number of submitted and accepted messages.

5 15d Amount of debit turnover messages.

Row n-1 "Credit turnover"



2 /CRTOTAL/ /CRTOTAL/ denotes credit turnover.

3 C C – credit.

4 6n Total number of messages sent to a participant with its registered BIC.

5 15d Amount of credit turnover messages.

Row n "Multilateral net position"



2 /TOTAL/ /TOTAL/ denotes the multilateral net position.

3 8n The value date of the multilateral net position settlement shall be stated

in the format YYYYMMDD.

4 1a D – debit or C – credit.

5 15d Amount of the multilateral net position.

7.2. Sample clearing result message

0001PE1740001D0000153000,00"CrLf"

0002PE1740002D0000225000,00"CrLf"

0003PE1740003D000007500,00"CrLf"

0004PE1740085C0000102500,00"CrLf"

0005PE1740086C000005500,00"CrLf"

0006PE1740087C000007700,00"CrLf"

0007/DRTOTAL/D0000448500,00"CrLf"

0008/CRTOTAL/C0000223700,00"CrLf"

0009/TOTAL/20000624D4800,00"CrLf"

113

8. Warning message

The warning message shall be included in a ME file.

8.1. Message contents

Field Name according to the

SWIFT standard

Type Name Format

20 Transaction Reference

Number

O Transaction reference number 16x

79 Narrative O Information for the message

recipient

35*50xl

8.2. Message field specification

Field 20 "Message reference number"

The warning message reference number assigned by the clearing service shall be

indicated in the field.

Field 79 "Information for the message recipient"

Information to the participant about the situation and its consequences.

9. Account statement

Where changes in the balance of the cover account have taken place on a TARGET2

holiday, Latvijas Banka shall send a cover account statement to the participant for each

its registered BIC separately at the end of the clearing service business day, reflecting the

changes in the balance on the cover account. The cover account statement shall be sent to

a participant using the respective registered BICin the form of encrypted and digitally

signed file generated in SWIFT MT950 message format, via the file exchange service.

The cover account statement shall be included in the KE file.

Contents of the account statement message

Field Name according to the SWIFT

standard

Type Name Format

20 Transaction Reference Number O Transaction reference

number

16x

25 Account Identification O Account identification 35x

28C Statement Number/Sequence

Number

O Account statement

number/sequence number

5n[/5n]

60a Opening Balance O Opening balance F or M

61 Statement Line N Statement line 6!n[4!n]2a[1!a]15d

1!a3!c16x[//16x]

[34x]

62a Closing Balance (Booked

Funds)

O Closing balance (booked

funds)

F or M

64 Closing Available Balance

(Available Funds)

N Closing balance (available

funds)

1!a6!n3!a15d

114

10. Information on direct and indirect participants of STEP2 system

Information on direct and indirect participants of STEP2 system shall be provided in two

files depending on the type of participation in STEP2. File name:

S202SCTLACBLV2XYYMMDDHHMMSSI00.T consists of the following elements:

No Position Symbols Description

1. 1-15 S202SCTLACBLV2X System and beneficiary

2. 16-27 YYMMDDHHMMSS Creation date and time

3. 28 I or D Routing table type (D for Direct

Participant or I for Reachable BIC);

4. 29-30 00 Increasing number. Increased when sent

repeatedly on the same day.

5. 31-32 .T The file type.

10.1. List of direct STEP2 participants

Line 1 of the list of direct STEP2 participants contains the value "SCT DIRECT

PARTICIPANT ROUTING TABLE". Lines 2–9 contain information about the table

contents. With Line 10, the table of STEP2 direct participants starts with the following

structure (columns are separated by a "Tab" symbol (hex 09)):

No. Column Format Description

1. BIC 8x 8 symbol BIC

2. Name 50x Name of the direct participant

3. Valid from 8n Valid from date (YYYYMMDD)

4. Valid till 8n Valid till date (YYYYMMDD)

5. Settlement BIC 11x Settlement BIC

6. Status 9x Status of the direct participant

7. Additional services 40x Specify the additional services the direct

participant uses

10.2. List of indirect STEP2 participants

Line 1 of the list of indirect STEP2 participants contains the value "SCT INDIRECT

PARTICIPANT ROUTING TABLE". Lines 2–9 contain information about the table

contents. With Line 10, the table of STEP2 direct participants starts with the following

structure (columns are separated by a "Tab" symbol (hex 09)):

No. Column Format Description

1. BIC 11x 11 symbol BIC

2. Name 50x Name of the indirect participant

3. Valid from 8n Valid from date (YYYYMMDD)

4. Valid till 8n Valid till date (YYYYMMDD)

5. BIC of the direct

participant

8x 8 symbol BIC

6. Settlement BIC of the

direct participant

11x 11 symbol BIC

7. Status 9x Status of the indirect participant

8. Additional services 40x Specify the additional services the indirect

participant uses

115

10.3. Status used in the list of participants

The "Status" column of the list of STEP2 participants may contain the following values:

No Status Description

1. ENABLED The Participant can send or receive any messages.

2. SUSPENDED The participant can no longer send or receive any message. Is a

temporary status used for emergency conditions.

3. CHANGED The participant is allowed to send and receive pacs.004 messages

4. DISABLED The Participant cannot send or receive message.

10.4. Additional services

The "Additional services"column may contain the following values:

No Payment

Type

Allowed

Value

Description

1. AO1 Acceptance Date AOS

2. AO3 Italian Transferability AOS

3. BPO Batch Processing Option

4. C00 Optional Settlement Cycle “00”

5. C01 Optional Settlement Cycle “01”

6. CAI CAI User Group

7. ERI Extended Remittance Information AOS

8. TEC The Direct Participant’s BIC is a Technical BIC

Chairman of the Board of Latvijas Banka Māris Kālis

Documents

Functional Specification of the Clearing Service of …..."20" – participant of STEP2 or another SEPA payment system. Where a message has been addressed to an entity with an 11-digit