This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

Size: px
Start display at page:

Download "This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version."

Transcription

1 The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA credit transfers via the RPS ( SCT/BCT/SCL technical specifications ) Version 3.0 valid from 20 November 2017 Notes on the English translation This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version. SCT technical specifications SCT/SCL, version 3.0 Page 1 of 37

2 Contents Contents Introduction Duplication checks and cross-referencing checks Duplication checks in the Duplication checks in other CSMs Cross-referencing checks by other CSMs Daily reconciliation report for credit transfers (DRC) DRC header DRC (pacs.008) credit transfer bulks sent body DRC (pacs.004) return bulks sent body DRC (camt.056) payment cancellation requests sent body DRC (camt.029) resolutions of investigation (ROIs) sent body DRC (pacs.008) credit transfer bulks received body DRC (pacs.004) return bulks received body DRC (camt.056) payment cancellation requests received body DRC (camt.029) resolutions of investigation (ROIs) received body DRC trailer XML file header Input credit file (ICF) header Credit validation file (CVF) header Settled credit file (SCF) header Bilateral credit file (BCF) header XML interbank messages SEPA credit transfer interbank payment SEPA credit transfer interbank credit transfer reject SCL SEPA credit transfer interbank return credit transfer SEPA credit transfer interbank payment cancellation request SEPA credit transfer interbank resolution of investigation Use of the instructing agent and instructed agent Error codes/rejection reason codes Error codes/rejection reason codes used in the SCT service Error codes/reject reason codes used in the BCT service Character set Notes on format/status, special features of XML Explanatory notes on the format of XML file headers and the daily reconciliation report Completing amount fields in line with the schema Use of filling characters in the amount fields Use of white spaces in XML fields, in this case the collapsing procedure space declaration Compression procedures FileAct EBICS environment TARGET2 referencing SCT technical specifications SCT/SCL, version 3.0 Page 2 of 37

3 Changes/additions to the technical specifications compared with version 2.7 Section Location Changes/additions 3 DRC Change to the numbering of processing cycles in the 7 Use of the instructing/instructed agent Amendment to the description 13 TARGET2 referencing Changes in the structure of the booking references SCT technical specifications SCT/SCL, version 3.0 Page 3 of 37

4 1 Introduction All items to be processed between the and direct participants are exchanged in the form of physical files. The formats of the individual files and bulks (logical files contained in files) are specified in the corresponding sections of this document. If the XML format and syntax rules defined in the XSD schema files are not observed, a file rejection message is generated by the. With regard to outgoing files, the data formats provided meet the specifications of this document. In both its SCT and BCT services, the supports SEPA credit transfers in XML format in accordance with ISO and the EPC specifications. Checking rules that go beyond schema validations are described in the following sections. Message type pacs scl used in the CVF does not form part of the EPC specifications. It is a rejection message which the sends to the submitter in the event of an error to inform them about rejected bulks or individual transactions (at the validation or settlement stage). SCT technical specifications SCT/SCL, version 3.0 Page 4 of 37

5 2 Duplication checks and cross-referencing checks 2.1 Duplication checks in the Participants in the RPS are advised to unambiguously reference each individual transaction every business day. Ensuring that payments are unambiguous helps to avoid duplicate payments and makes it easier to classify and trace specific payments. The carries out duplication checks in the SCT service at file, bulk and individual transaction level and in the BCT service at file level. These cover the following criteria, from which an unambiguous key can be derived. Service Reference number Identification of the party that allocated the reference Interbank settlement date (determined by the processing window used in the SEPA- Clearer) or processing day in the The table below shows the duplication criteria applying at file, bulk and individual transaction levels. Files ICF bulks Origin Service Reference number ICF/BCF SCT/ File reference file header BCT ICF group header or assignment SCT If a file is rejected, it must always be given a new file reference before it is resubmitted. Message ID or identification It is necessary to ensure that the <Msgld> remains unambiguous for both pacs message types (pacs.008 and pacs.004) and to safeguard the <Id> of the two camt types (camt.056 and camt.029 (see explanatory note on <MsgId> and <Id>). BIC Sending institution Instructing agent - Date Interbank settlement date Credit transfer pacs.008 SCT Transaction ID Debtor agent Interbank settlement date Return pacs.004 SCT Return ID Original creditor Interbank settlement date agent Payment cancellation camt.056 SCT Cancellation ID Original debtor agent SCL processing day request Resolution of investigation camt.029 SCT Cancellation Status ID Original creditor agent SCL processing day SCT technical specifications SCT/SCL, version 3.0 Page 5 of 37

6 2.2 Duplication checks in other CSMs The Deutsche Bundesbank routes SEPA credit transfers which cannot be processed in the via other CSMs. To avoid rejections by other CSMs on account of other duplication checks, the references entered in the following message elements should be kept unambiguous for an extended period of time (at least three months) by, for example, applying a time stamp. Message identification (bulk level; pacs.008 and pacs.004) Identification (bulk level; camt.056 and camt.029) Transaction ID (individual transaction level; pacs.008) Return ID (individual transaction level; pacs.004) Cancellation ID (individual transaction level; camt.056) Cancellation status ID (individual transaction level; camt.029) The individual participant is responsible for any rejections by other CSMs owing to duplicate submissions arising from that participant's non-compliance with the aforementioned rules for completing fields. Furthermore, that participant shall be liable for any resulting damages, breaches of return deadlines defined in the rulebook etc. 2.3 Cross-referencing checks by other CSMs Among other activities, the routes R-transactions to other CSMs. Where applicable, other CSMs may subject these R-transactions to cross-referencing checks on the basis of references entered in the individual message elements and entries contained in other message elements of the original transaction as listed under the previous sub-item (eg the original interbank settlement date or the original interbank settlement amount), the aim being to establish whether the original transaction was also processed using this other CSM. If the details contained in the R-transaction regarding the original transaction do not exactly match the data relating to the original transaction or if the original transaction has the wrong status, this may result in the R-transaction being rejected by the other CSM. SCT technical specifications SCT/SCL, version 3.0 Page 6 of 37

7 3 Daily reconciliation report for credit transfers (DRC) Summary of the SCT bulks submitted to and delivered from the 's SCT service, a copy of which is made available to each SEPA- Clearer participant in EBCDIC format every business day at the end of that day's processing schedule. The DRC is not in XML format. The DRC files delivered by the in ASCII format using the EBICS communication infrastructure do not incorporate any special characters for the line feed at the end of the data record. 3.1 DRC header Status Field name Format Content Item M Record type 4x HDRC 0 M Service identifier 3x SCT 4 M File type 3x DRC 7 M Sending institution 4!a2!a2!c s BIC (production: MARKDEFF; test: MARKDEF0) 10 M Sender s file reference 16!x s reference 18 M Date and time 6!n6!n YYMMDDHHMMSS 34 M Test code 1x Either T (test) or P (production), depending on the processing environment 46 M Receiving institution 4!a2!a2!c3!c Originator s BIC/clearing institution s BIC (not communication partner) 47 M Business date 6!n business day 58 SCT technical specifications SCT/SCL, version 3.0 Page 7 of 37

8 3.2 DRC (pacs.008) credit transfer bulks sent body Submissions of original SEPA credit transfers to the s SCT service by participants Status Field name Format Content Item M Record type 4x DTSB 0 M Bulk reference 35x <MsgId> in group header 4 M Number credit transfers processed 8n Number of processed transactions in a bulk 39 M Number credit transfers rejected 8n Number of records rejected in a bulk 47 M Value credit transfers processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: 0.00 M Value credit transfers rejected 18d Total value of records rejected in a bulk. If an entire bulk is rejected, total value of all transactions contained in the bulk M Processing cycle number 2n Processing cycle A 90 denotes processing after the first submission window A 91 denotes processing after the second submission window A 92 denotes processing after the third submission window A 95 denotes processing after the fourth submission window A 96 denotes processing after the fifth submission window A 99 denotes processing after the sixth submission window SCT technical specifications SCT/SCL, version 3.0 Page 8 of 37

9 3.3 DRC (pacs.004) return bulks sent body Submissions of returns to the s SCT service by participants Status Field name Format Content Item M Record type 4x DRSB 0 M Bulk reference 35x <MsgId> in group header 4 M Number returns processed 8n Number of processed transactions in a bulk 39 M Number returns rejected 8n Number of records rejected in a bulk 47 M Value returns processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value returns rejected 18d Total value of records rejected in a bulk. If an entire bulk is rejected, total 73 value of all transactions contained in the bulk M Processing cycle number 2n Processing cycle A 90 denotes processing after the first submission window A 91 denotes processing after the second submission window A 92 denotes processing after the third submission window A 95 denotes processing after the fourth submission window A 96 denotes processing after the fifth submission window A 99 denotes processing after the sixth submission window 91 SCT technical specifications SCT/SCL, version 3.0 Page 9 of 37

10 3.4 DRC (camt.056) payment cancellation requests sent body Submissions of payment cancellation requests (PCRs) to the s SCT service by participants Status Field name Format Content Item M Record type 4x DCSB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number PCRs processed 8n Number of processed transactions in a bulk 39 M Number PCRs rejected 8n Number of records rejected in a bulk 47 M Value PCRs processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value PCRs rejected 18d Total value of records rejected in a bulk. If an entire bulk is rejected, total 73 value of all transactions contained in the bulk M Processing cycle number 2n Processing cycle A 90 denotes processing after the first submission window A 91 denotes processing after the second submission window A 92 denotes processing after the third submission window A 95 denotes processing after the fourth submission window A 96 denotes processing after the fifth submission window A 99 denotes processing after the sixth submission window 91 SCT technical specifications SCT/SCL, version 3.0 Page 10 of 37

11 3.5 DRC (camt.029) resolutions of investigation (ROIs) sent body Submissions of resolutions of investigation (ROIs) to the s SCT service by participants Status Field name Format Content Item M Record type 4x DRIB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number ROIs processed 8n Number of processed transactions in a bulk 39 M Number ROIs rejected 8n Number of records rejected in a bulk 47 M Value ROIs processed 18d Total value of processed transactions in a bulk. If an entire bulk is rejected: M Value ROIs rejected 18d Total value of records rejected in a bulk. If an entire bulk is rejected, total 73 value of all transactions contained in the bulk M Processing cycle number 2n Processing cycle A 90 denotes processing after the first submission window A 91 denotes processing after the second submission window A 92 denotes processing after the third submission window A 95 denotes processing after the fourth submission window A 96 denotes processing after the fifth submission window A 99 denotes processing after the sixth submission window 91 SCT technical specifications SCT/SCL, version 3.0 Page 11 of 37

12 3.6 DRC (pacs.008) credit transfer bulks received body Deliveries of original SEPA credit transfers from the s SCT service to participants Status Field name Format Content Item M Record type 4x DTRB 0 M Bulk reference 35x <MsgId> in group header 4 M Number credit transfers received 8n Number of delivered transactions in a bulk 39 M Value credit transfers received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 2n Processing cycle A 90 denotes deliveries made from the first delivery window A 91 denotes deliveries made from the second delivery window A 92 denotes deliveries made from the third delivery window A 95 denotes deliveries made from the fourth delivery window A 96 denotes deliveries made from the fifth delivery window A 97 denotes deliveries made from the sixth delivery window A 98 denotes deliveries made from the seventh delivery window A 99 denotes deliveries made from the eighth delivery window 65 SCT technical specifications SCT/SCL, version 3.0 Page 12 of 37

13 3.7 DRC (pacs.004) return bulks received body Deliveries of returns from the s SCT service to participants Status Field name Format Content Item M Record type 4x DRCB 0 M Bulk reference 35x <MsgId> in group header 4 M Number returns received 8n Number of delivered transactions in a bulk 39 M Value returns received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 2n Processing cycle A 90 denotes deliveries made from the first delivery window A 91 denotes deliveries made from the second delivery window A 92 denotes deliveries made from the third delivery window A 95 denotes deliveries made from the fourth delivery window A 96 denotes deliveries made from the fifth delivery window A 97 denotes deliveries made from the sixth delivery window A 98 denotes deliveries made from the seventh delivery window A 99 denotes deliveries made from the eighth delivery window 65 SCT technical specifications SCT/SCL, version 3.0 Page 13 of 37

14 3.8 DRC (camt.056) payment cancellation requests received body Deliveries of payment cancellation requests (PCRs) from the s SCT service to participants Status Field name Format Content Item M Record type 4x DRRB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number PCRs received 8n Number of delivered transactions in a bulk 39 M Value PCRs received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 2n Processing cycle A 90 denotes deliveries made from the first delivery window A 91 denotes deliveries made from the second delivery window A 92 denotes deliveries made from the third delivery window A 95 denotes deliveries made from the fourth delivery window A 96 denotes deliveries made from the fifth delivery window A 97 denotes deliveries made from the sixth delivery window A 98 denotes deliveries made from the seventh delivery window A 99 denotes deliveries made from the eighth delivery window 65 SCT technical specifications SCT/SCL, version 3.0 Page 14 of 37

15 3.9 DRC (camt.029) resolutions of investigation (ROIs) received body Deliveries of resolutions of investigation (ROIs) from the s SCT service to participants Status Field name Format Content Item M Record type 4x DROB 0 M Bulk reference 35x <Id> belonging to assignment 4 M Number ROIs received 8n Number of delivered transactions in a bulk 39 M Value ROIs received 18d Total value of delivered transactions in a bulk 47 M Processing cycle number 2n Processing cycle A 90 denotes deliveries made from the first delivery window A 91 denotes deliveries made from the second delivery window A 92 denotes deliveries made from the third delivery window A 95 denotes deliveries made from the fourth delivery window A 96 denotes deliveries made from the fifth delivery window A 97 denotes deliveries made from the sixth delivery window A 98 denotes deliveries made from the seventh delivery window A 99 denotes deliveries made from the eighth delivery window 3.10 DRC trailer Status Field name Format Content Item M Record type 4x TDRC 0 M Total number records 6n Number of DRC bodies 4 65 SCT technical specifications SCT/SCL, version 3.0 Page 15 of 37

16 4 XML file header 4.1 Input credit file (ICF) header (BBkICFBlkCdtTrf) see annex Credit validation file (CVF) header (BBkCVFBlkCdtTrf) see annex Settled credit file (SCF) header (BBkSCFBlkCdtTrf) see annex Bilateral credit file (BCF) header (BBkBCFBlkCdtTrf) see annex 4 SCT technical specifications SCT/SCL, version 3.0 Page 16 of 37

17 5 XML interbank messages 5.1 SEPA credit transfer interbank payment (pacs ) see annex SEPA credit transfer interbank credit transfer reject SCL (pacs sclsct) see annex SEPA credit transfer interbank return credit transfer (pacs sct) see annex SEPA credit transfer interbank payment cancellation request (interbank recall of a credit transfer) (camt sct) see annex SEPA credit transfer interbank resolution of investigation (interbank negative response to a request to recall a credit transfer) (camt ) see annex 9 SCT technical specifications SCT/SCL, version 3.0 Page 17 of 37

18 6 Use of the instructing agent and instructed agent The following section provides an overview of how the instructing agent, the instructed agent and the receiving institution and sending institution are to be specified at the different message levels (file, bulk or individual transaction level). The InstructedAgentRule and the InstructingAgentRule must be observed in accordance with the ISO standard. The latter rule encompasses an exclusion principle, which clearly states that the instructing agent may be specified only in the group header or at individual transaction level. This principle also applies to the instructed agent. The following information is not intended to depict all the data elements that can or must contain a BIC in a SEPA direct debit message but rather to identify the key actors involved in payment processing using the. Brief overview of key individual agents Sending institution <SndgInst> in the file header: should contain the BIC of the file sender (communication partner). A file delivered to the may contain bulks from one or more instructing agents. The BIC of the sending institution can deviate from that of the instructing agent and need not be listed in the SCL Directory. This is, for example, the case for technical service providers who themselves are not participants in the. A file sent by the contains exactly one bulk. MARKDEFF (in the test: MARKDEF0 ) is entered as the sending institution. Receiving institution <RcvgInst> in the file header: should contain the BIC of the file recipient (communication partner). A file sent by the contains exactly one bulk for an instructed agent. The BIC of the receiving institution can deviate from that of the instructed agent and need not be listed in the SCL Directory. This is, for example, the case for technical service providers who themselves are not participants in the. In a file delivered to the MARKDEFF (in the test: MARKDEF0 ) must be specified as the receiving institution. Instructing agent <InstgAgt> in the group header 1 : should contain the BIC of the submitter of a bulk submitted to the. This BIC can, but need not necessarily, be listed in the SCL Directory. The countervalue of the submitted bulk is settled using the technical sub-account on the TARGET2 SSP specified by the submitter for the purpose of effecting financial settlement via the during the corresponding SDD/SCC settlement cycle. The BIC of the instructing agent in the group header can deviate from that of the payment service provider at the individual transaction level. 1 In the case of submissions, this applies equally to the assigner behind the assignment of the message type camt.056. SCT technical specifications SCT/SCL, version 3.0 Page 18 of 37

19 In the files delivered by the, the field instructing agent in the group header is left blank. Instructed agent <InstdAgt> in the group header: 2 In the files delivered by the SEPA- Clearer, the field instructed agent contains the BIC of the participant whose technical sub-account is used on the TARGET2 Single Shared Platform for the purpose of effecting financial settlement during the corresponding SDD/SCC settlement cycle. This BIC can, but need not necessarily, be listed in the SCL Directory. The BIC of the instructed agent can deviate from that of the debtor/creditor agent at the individual transaction level. In the case of submissions to the, this field must be left blank. Instructing agent <InstgAgt> at the individual transaction level: 3 should contain the BIC of the original submitter to the of the bulk in which the transaction was contained upon its submission to the. Upon delivery of the transaction, this BIC is entered at individual transaction level by the and can, but need not necessarily, be listed in the SCL Directory. The BIC of the instructing agent can deviate from that of the debtor/creditor agent at the individual transaction level. In the case of submissions to the, this field must be left blank. Instructed agent <InstdAgt> at the individual transaction level: 4 this field is not supported at individual transaction level, nor is it a component of the schema files. Debtor agent BIC <DbtrAgt> at the individual transaction level: should contain the BIC of the payer's payment service provider (debtor bank). It is essential that this BIC is listed in the SCL Directory as it is the key criterion for routing the payment in the SCT service. Creditor agent BIC <CdtrAgt> at the individual transaction level: should contain the BIC of the payee's payment service provider (creditor bank). This BIC must be listed in the SCL Directory. 2 In the case of deliveries, this applies equally to the assignee behind the assignment of the message type camt In the case of deliveries, this applies equally to the assigner at the individual transaction level of the message type camt In the case of deliveries, this applies equally to the assignee at the individual transaction level of the message type camt.056. SCT technical specifications SCT/SCL, version 3.0 Page 19 of 37

20 Sample entry for the maximum number of different BICs in an SCT input credit file: File header: Bulk header: Individual transaction level: SCT technical specifications SCT/SCL, version 3.0 Page 20 of 37

21 7 Error codes/rejection reason codes This section contains tables showing the error and rejection codes which payment service providers may use when submitting R-transactions or on the basis of which the can reject and return erroneous files, bulks and transactions to the submitter. In individual cases, rejections may occur in the context of a payment being forwarded to another CSM as a result of deviating plausibility checks even if the payment was processed without error in the. Corresponding notifications of rejections by other CSMs are included in the message descriptions (see section 5). 7.1 Error codes/rejection reason codes used in the SCT service Error codes used in connection with the structural check of an input credit file (ICF) by the The errors described below result in the entire file being rejected by means of CVF (exception: A01) Error code A01 R02 R04 R07 R09 R10 R11 R12 R13 R14 R18 R19 R20 R21 R98 ICF was partially rejected. Nature of error The file name designation does not conform with the rules (code currently not in use). The sender s BIC in the file name does not conform with the rules (code currently not in use). SWIFTNet FileAct request type does not conform with the rules. ICF was completely rejected as it does not conform with the rules for other reasons (eg character set data deviate from UTF-8). File does not correspond to the schema and therefore cannot be processed. Sender's BIC (<SndgInst>) is incorrect. Recipient's BIC (<RcvgInst>) is incorrect. ICF is a duplicate. Error in test code (<TstCode>). Number of credit transfer bulks contained in the ICF does not match the figure given in the file header. Number of payment cancellation request bulks contained in the ICF does not match the figure given in the file header. Number of return bulks contained in the ICF does not match the figure given in the file header. Number of resolution of investigation bulks contained in the ICF does not match the figure given in the file header. File rejected as prefixes used at group header or individual transaction level (code currently not in use). SCT technical specifications SCT/SCL, version 3.0 Page 21 of 37

22 Error code R99 S01 Nature of error File rejected for other reasons (code currently not in use). File rejected as maximum permissible number of bulks in a file was exceeded. SCT technical specifications SCT/SCL, version 3.0 Page 22 of 37

23 Error codes used in connection with the structural check of a bulk by the The errors described below result in the entire bulk being rejected by means of CVF (exception: B01) Error code Nature of error e pacs.002scl AM04 Bulk was rejected due to insufficient funds. ISO X B01 Bulk was partially rejected. PRTRY X B02 Maximum permissible number of transactions contained in a bulk was exceeded. PRTRY X B03 Number of transactions contained in a bulk does not match the figure given in the group header. PRTRY X B05 B09 B10 Total value in the field <TtlIntrBkSttlnAmt> or <TtlRtrdIntrBkSttlmAmt> does not match the sum of the transactions in the bulk. Entire bulk was rejected as all transactions contained in it were rejected. The specific reasons for rejecting each transaction are stated accordingly. Entire bulk was rejected either because the instructing agent has to be included in the ICF group header or the specified instructing agent is not authorised to make submissions for the submitted payment type. PRTRY PRTRY PRTRY B11 Entire bulk was rejected as the instructed agent must not be included in the ICF group header. PRTRY X B12 Entire bulk was rejected as the assigner was not authorised to make submissions or the assignee data were incorrect. PRTRY B14 Entire bulk was rejected as the <MsgId> or <Id> appears in duplicate. PRTRY X B15 B23 B40 B98 Entire bulk was rejected as the date in the field <IntrBkSttlmDt> or <OrgnlIntrBkSttlmDt> falls outside the permitted time period. Rejection of individual transactions owing to another CSM's bulk rejection to. The individual transactions are each rejected with the error code B23. Entire bulk was rejected as it contains more than 999 erroneous transactions. Specific reasons for rejection are only stated for the validated, erroneous individual transactions. Entire bulk was rejected as the <MsgId> (GrpHdr) or <Id> (Assgnmt) does not conform with the format rules. PRTRY PRTRY PRTRY PRTRY X X X X X X X X SCT technical specifications SCT/SCL, version 3.0 Page 23 of 37

24 Error code Nature of error e pacs.002scl B99 Bulk was rejected for other reasons. PRTRY X SCT technical specifications SCT/SCL, version 3.0 Page 24 of 37

25 Individual transaction-related error codes ( and other CSMs) or rejection codes (banks) specific to the individual transaction: Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, 2017, version 1.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 AC01 IncorrectAccountNumber Account identifier invalid (ie invalid IBAN or account number does not exist) See description on left Banks/ SEPA- Clearer ISO X X AC04 ClosedAccountNumber Account closed See description on left Banks ISO X X AC06 BlockedAccount Account blocked, reason not specified See description on left Banks ISO X AG01 TransactionForbidden Credit transfer forbidden on this type of account (eg savings account) AG02 InvalidBankOperationCode Operation/transaction code incorrect, invalid file format Usage rule: To be used for incorrect operation/ transaction code See description on left Banks ISO X AM02 Not Allowed Amount ---- Incorrect amount Other CSMs/ SEPA- Clearer AM04 InsufficientFunds Insufficient funds on the account Banks ISO X ISO X See description on left Banks ISO X X AM05 Duplication Duplicate payment See description on left Banks/other CSMs/ SEPA- ISO X X SCT technical specifications SCT/SCL, version 3.0 Page 25 of 37

26 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, 2017, version 1.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 ARDT ---- The transaction has already been returned Clearer See description on left Banks PRTRY X BE04 MissingCreditorAddress Account address invalid Payee's address missing or incorrect Banks ISO X CANC The original transaction (pacs.008) was cancelled by another CSM through a credit transfer recall (camt.056) Other CSMs PRTRY X CUST RequestedByCustomer Beneficiary refusal Refused by payee Banks ISO X DUPL DuplicatePayment Duplicate sending See description on left Banks ISO X DT01 InvalidDateRange ---- Date falls outside the time period permitted by other CSMs or the 's time corridor ED05 SettlementFailed ---- Unsuccessful settlement in the STEP2 SCT service Other CSMs/ SEPA- Clearer Other CSMs/ SEPA- Clearer ISO X X ISO X FOCR FollowingCancellation Request Positive answer to the recall Designation for a return on the basis of a recall request Banks ISO X FRAD ---- Fraudulent originated credit transfer Payment effected fraudulently Banks PRTRY X LEGL LegalDecision Legal reason Rejection on legal grounds Banks ISO X SCT technical specifications SCT/SCL, version 3.0 Page 26 of 37

27 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, 2017, version 1.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 MD07 EndCustomerDeceased Beneficiary deceased See description on left Banks ISO X MS02 MS03 NotSpecifiedReason CustomerGenerated NotSpecifiedReason AgentGenerated By order of the beneficiary Reason not specified NOAS NoAnswerFromCustomer No response from beneficiary NOOR NoOriginalTransaction Received Original credit transfer never received Reason for return not specified by customer Reason for return not specified by payment service provider PY Transaction cannot be processed as the payer s and/or the payee s payment service provider(s) is/are not registered as direct or indirect participant(s) in the STEP2 SCT service Banks ISO X Banks ISO X Payee fails to respond Banks PRTRY X See description on left Banks PRTRY X X Other CSMs/ SEPA- Clearer PRTRY X RC01 BankIdentifierIncorrect Bank identifier incorrect, eg invalid BIC See description on left Banks ISO X RR01 MissingDebtorAccountOr Identification Regulatory reason See description on left Banks ISO X RR02 RR03 MissingDebtorOr Address MissingCreditorOr Address Regulatory reason See description on left Banks ISO X Regulatory reason See description on left Banks ISO X RR04 Regulatory reason Regulatory reason See description on left Banks ISO X SCT technical specifications SCT/SCL, version 3.0 Page 27 of 37

28 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, 2017, version 1.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 TECH ---- Technical problems resulting in erroneous credit transfer Payment effected erroneously due to technical problems XD Issued if the country code is a valid ISO or SEPA country code but the (country-specific) structure of the IBAN or the check digits is incorrect XT The transaction contains at least one unsupported field At least one mandatory field is missing from the transaction The invalid XML field is indicated by the error code (if a code exists) XT The content of at least one XML element is not in the format required. The invalid XML field is indicated by the error code. XT The two characters forming the country code do not constitute a valid ISO or SEPA country code XT Invalid underlying original transaction Further check required Banks PRTRY X SEPA- Clearer SEPA- Clearer XT The transaction contains at least one element with a BIC that is not SEPAreachable SEPA- Clearer SEPA- Clearer SEPA- Clearer PRTRY X PRTRY X PRTRY X PRTRY X PRTRY X Other CSMs PRTRY X SCT technical specifications SCT/SCL, version 3.0 Page 28 of 37

29 Code ISO designation SEPA Core reason (pursuant to the EPC s SCT Implementation Guidelines, 2017, version 1.0) Nature of error Initiator e pacs.002scl pacs.004 camt.056 camt.029 XT Invalid status of underlying original transaction No further action required XT The originally instructed amount <OrgnlIntrBkSttlmAmt> was not found or does not match the original transaction amount XT Deadline expired for requesting the recall of a SEPA credit transfer XT Rejection of a credit transfer recall (camt.056) due to cross-referencing XT Credit transfer rejected for other reasons (code currently not in use). Other CSMs PRTRY X Other CSMs PRTRY X Other CSMs PRTRY X Other CSMs PRTRY X SEPA- Clearer PRTRY SCT technical specifications SCT/SCL, version 3.0 Page 29 of 37

30 7.2 Error codes/reject reason codes used in the BCT service Error codes used in connection with the structural check of a bilateral credit file (BCF) by the The errors described below result in the entire file being rejected by means of CVF Error code R07 R09 R10 R11 R12 R13 R14 R97 RIF RIA RID RFR Nature of error SWIFTNet FileAct request type does not conform with the rules. BCF was completely rejected as it does not conform with the rules for other reasons (eg character set data deviate from UTF-8). File does not correspond to the schema and therefore cannot be processed. Sender's BIC (<SndgInst>) is incorrect. Recipient's BIC (<RcvgInst>) is incorrect. BCF is duplicated. Error in test code (<TstCode>). File rejected due to the absence of a bilateral agreement. File rejected due to insufficient funds. Entire file was rejected either because the instructing agent has to be included in the BCF file header or the specified instructing agent is not authorised to make submissions for the submitted payment type. Entire file was rejected as the date in the field <IntrBkSttlmDt> falls outside the permitted time period. Entire file was rejected as the <FileRef> (file header) does not conform with the format rules. SCT technical specifications SCT/SCL, version 3.0 Page 30 of 37

31 8 Character set The supports the full UTF-8 character set. Pursuant to the SEPA rulebooks, PSPs must be able to support the following Latin character set commonly used in international communication. a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( ). + Space However, it can be agreed on a bilateral or multilateral basis to support one or more UTF-8 character sets in addition to the Latin character set (eg the Greek character set). This applies above all to message elements containing the purpose of payment, name and address of the payer (creditor) and payee (debtor). Unless prevented by the schema parameters, the therefore delivers data records featuring UTF-8 characters not contained in the Latin character set to the recipient in unchanged format. Checks by the (1) When files are submitted (ICFs), the checks whether their prologue contains the following information in line with the usage rules applying to the UTF-8 character set. <?xml version= 1.0 encoding= UTF-8 > If any other character set is entered, the entire file is rejected using the error code R09. (2) No character set checks beyond those covering compliance with the UTF-8 character set are carried out by the. SCT technical specifications SCT/SCL, version 3.0 Page 31 of 37

32 9 Notes on format/status, special features of XML 9.1 Explanatory notes on the format of XML file headers and the daily reconciliation report Format Description a c Alpha, capital letters Alphanumeric, letters: capital letters d Decimal including decimal point and two decimal places n x Numeric Characters in accordance with Latin character set, in some cases restricted by XSD schema file (see also section entitled Character set ) 3!a Precisely three alpha characters ISODate ISODateTime YYYY-MM-DD YYYY-MM-DDThh:mm:ss Status M O Mandatory field Optional field 9.2 Completing amount fields in line with the schema Sample entry Processing in the SEPA- Clearer One decimal place No decimal places No decimal point and no decimal places Submitted files containing amounts with a comma and/or more than two decimal places do not conform to the schema and are therefore rejected using error code R10. Amounts may not be smaller than 0.01 and must not exceed Use of filling characters in the amount fields The XML parser accepts characters that function as fillers in an XML context. These may be entered in the amount fields in an XML environment, however their use may result in SCT technical specifications SCT/SCL, version 3.0 Page 32 of 37

33 processing problems for the receiving/processing institution. We therefore advise against using such filling characters. The fillers listed below are recognised by the XML parser and routed/processed as follows by the SCL. 1. Leading zeros before the decimal point and trailing zeros after the decimal point The ignores the redundant zeros and delivers the amount with the first and the last significant characters to the SCL participant. Example: Submission to the SCL: <IntrBkSttlmAmt Ccy= EUR > </IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy= EUR >1.01<IntrBkSttlmAmt> 2. Spaces in the amount field The ignores the redundant spaces and delivers the amount with the first and the last significant characters to the SCL participant. Example: Submission to the SCL: <IntrBkSttlmAmt Ccy= EUR > 2.02 </IntrBkSttlmAmt> Delivery by the SCL: <IntrBkSttlmAmt Ccy= EUR >2.02</IntrBkSttlmAmt> 9.4 Use of white spaces in XML fields, in this case the collapsing procedure White spaces form part of the standard XML environment. They are also permitted for the decimal data type, which is set as standard for the amount field. Neither the ISO standard nor the EPC s Implementation Guidelines make provisions for any restrictions to this arrangement. As a rule, white spaces can be processed by XML parsers. However, problems can occur, eg when customised solutions have been programmed or the XML data records have been converted to different formats for further processing. We therefore advise against using spaces in the tags, as this may result in processing problems for the receiving/processing institution. CSMs have stipulated the following format rules for a variety of string -derived fields in their schema files. In the description, the white spaces facet was set to collapse in the schema files. Detailed information on the procedure used in XML parsing can be found in the document W3C Recommendation 28 October 2004, XML Schema Part 2: Datatypes SCT technical specifications SCT/SCL, version 3.0 Page 33 of 37

34 Second Edition, the contents of which can be called up using the internet link provided below. For reasons of interoperability, this collapsing procedure was integrated into the SEPA- Clearer s schema files with the same level of effect, meaning that, overall, and wherever necessary both submissions to and deliveries from the undergo the above procedure as part of the XML parsing process. 9.5 space declaration Message instances (ie messages exchanged between PSPs and the ) must contain the name space declaration at bulk level. This declaration thereafter applies to all tags contained in the message; individual tags therefore need not be identified with the prefix sw. SCL participants must take care to adhere to the stipulated entries/declaration (see also sample files). Prefix data at bulk and individual transaction level result in the entire file being rejected using the error code R98 (implementation at a later expansion stage only). SCL delivery messages to PSPs are likewise sent without a prefix at tag level. Sample message instance: <SCLSCT:pacs xmlns= urn:iso:std:iso:20022:tech:xsd:sct:pacs > <GrpHdr> <MsgId>AAAAAAAAAAABCD123</MsgId> 10 Compression procedures 10.1 FileAct 5 Files may be transmitted in either direction in compressed or uncompressed format as desired by the customer. To this end, the following compression procedures may be used. FLAM 6 (which uses the ADC compression mode as it offers the highest compression factor) ZIP GZIP 10.2 EBICS environment 7 In EBICS, the ZIP compression procedure must be supported when transmitting files in either direction. 5 See the procedural rules on communication via SWIFTNet FileAct for the Deutsche Bundesbank's Retail Payment System (RPS) and the RPS (SCL). 6 FLAM (Frankenstein-Limes-Access-Method) is a registered trademark of limes datentechnik gmbh, Friedrichsdorf, Germany. 7 See the Deutsche Bundesbank s procedural rules on communication via EBICS with deposit-taking credit institutions and other account holders with a bank sort code. SCT technical specifications SCT/SCL, version 3.0 Page 34 of 37

35 11 TARGET2 referencing TARGET2 issues settlement information (MT 900/MT 910) and electronic account statements (MT 940/MT 950) for all accounts held under its auspices. The aforementioned message types contain settlement references which serve to identify the SEPA credit transfers that are exchanged using the. 1 Current order (ie liquidity transfer) automatically generated by the from the PM account to the relevant sub-account in the amount of the sum total of the settlementrelated SEPA credit transfers arising from all ICFs and BCFs submitted in a specific submission window. Structure of the settlement reference in field 21 of MT 900/MT 910 and field 61, sub-field 7 of MT 940/MT 950: SCL Format Content System 1-character alphabetical S () AS action 2-character alphabetical C (current order) + No of cycles Date 2-character, numeric TT (processing day) Sequence number 2-character, numeric Number of the relevant sub-account Serial number 9-character, numeric Unambiguous serial number within the preceding reference information In addition, field 72 of MT 900/MT 910 supports the codeword ASINF followed by the information given below. SCL Format Content Current order 3-character, constant CUO (current order) Processing cycle 2-character, numeric Phase 90 to 99 Settlement cycle 2-character, alphabetical First character: I, O or X I = Input (settlement of bulks submitted to the SCL) O = Output (settlement of bulks delivered from the SCL) X = Error (settlement of rejected transactions) Second character: A, B, C or D A = SCT service B = SDD service C = SCC service D = BCT service In MT 940/MT 950, the information <MARKDEFFEDE>HHMMSS is additionally incorporated into field 61, sub-field 9. SCT technical specifications SCT/SCL, version 3.0 Page 35 of 37

36 2 Settlement of submitted and delivered SCT bulks and BCFs on the sub-account during the relevant SCT/BCT settlement cycles of a settlement procedure. Structure of the settlement reference in field 21 of MT 900/MT 910 and field 61, sub-field 7 of MT 940/MT 950: SCL Format Content System 1-character, alphanumeric S () AS action 2-character, alphabetical First character: I, O or X I = Input (settlement of bulks submitted to the SCL) O = Output (settlement of bulks delivered from the SCL) X = Error (settlement of rejected transactions) Second character: A, B, C or D A = SCT service B = SDD service C = SCC service D = BCT service Current date 2-character, numeric Day of the current month File ID 6-character, numeric Internal file ID Bulk ID 3-character, numeric Bulk within the file Serial number 2-character, numeric Serial number In addition, field 72 of MT 900/MT 910 supports the codeword ASINF followed by the information given below. SCL Format Content Bulk ID 35-character, alphanumeric Message identification (<MsgID>) in group header of the settled SCT bulk File reference (<FileRef>) in file header of the settled BCF Settlement date 6-character, numeric DDMMYY Instructing or instructed agent 11-character, alphanumeric BIC in group header of settled SCT bulk or file header of settled BCF: Submitted bulks: instructing agent Delivered bulks: instructed agent In MT 940/MT 950, the information <MARKDEFFEDE>HHMMSS is additionally incorporated into field 61, sub-field 9. SCT technical specifications SCT/SCL, version 3.0 Page 36 of 37

37 3 Return transfer of entire funds from the sub-account to the corresponding PM account after completion of all settlements in a settlement procedure (SCT/BCT and SDD/SCC settlement cycles) automatically initiated by the. When retransferring the (entire amount of) liquidity from the sub-account to the PM account, references are likewise assigned (note to such effect in field 21 of MT 900/MT 910 as well as in field 61, sub-field 7 of MT 940/MT 950). In this case, however, these are merely internal references assigned by the application when communicating with the TARGET2 platform. Hence, reconciliation with the underlying transactions is not possible. SCT technical specifications SCT/SCL, version 3.0 Page 37 of 37

38 Input Credit File (ICF) Header BBkICFBlkCdtTrf XML-File-Header Input Credit File (ICF) Header Use Submission of pacs.008, pacs.004, camt.056 and camt.029-bulks to the Parsing errors result in the file being rejected with the error code R10. The schema file BBkICFBlkCdtTrf specifies the ICF. SCT annex 1 of appendix SCT/SCL technical specifications BBkICFBlkCdtTrf page 1 of 1

39 BBkICFBlkCdtTrf Message structure Status Element/Attribut Format Content Checks SCL BBkICFBlkCdtTrf BBkICFBlkCdtTrf 1..1 SndgInst 1..1 RcvgInst 1..1 FileRef BBkICFBlkCdtTrf +SndgInst BBkICFBlkCdtTrf +RcvgInst BBkICFBlkCdtTrf +FileRef 1..1 SrvcID 1..1 TstCode BBkICFBlkCdtTrf +SrvcID BBkICFBlkCdtTrf +TstCode Pattern Sending Institution sw8:bicidentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Receiving Institution BBkICF:RcvgInstBICIdentifier Acceptable Codes MARKDEF0 MARKDEFF File Reference BBkICF:Max16Text Pattern [0-9A-Z]{16,16} Service Identifier BBkICF:SrvcID Acceptable Codes SCT Test Code BBkICF:TestCodee Acceptable Codes P T Sending Institution s 11-digit BIC (communication partner) 's BIC (production: MARKDEFF; test: MARKDEF0) Sender s file reference, must be unique on operating day SCT Either T (test) or P (production), depending on the processing environment Communication partner s authorisation to submit verified against the BIC in the group header error code: R11 Part of the duplication check error code: R13 Check as to whether this element is allocated with the BIC of the error code: R12 Part of the duplication check error code: R13 Error code: R14 BBkICFBlkCdtTrf; SCL SCT; 2017 page 1 of 2

40 BBkICFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 Fe 1..1 FDtTm BBkICFBlkCdtTrf +Fe BBkICFBlkCdtTrf +FDtTm 1..1 NumCTBlk BBkICFBlkCdtTrf +NumCTBlk 1..1 NumPCRBlk BBkICFBlkCdtTrf +NumPCRBlk 1..1 NumRFRBlk BBkICFBlkCdtTrf +NumRFRBlk 1..1 NumROIBlk BBkICFBlkCdtTrf +NumROIBlk File e BBkICF:Fe Acceptable Codes ICF File Date and Time sw8:isodatetime Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Total Number of pacs.008 Bulks BBkICF:Max8NumericText Pattern [0-9]{1,8} Total Number of camt.056 Bulks BBkICF:Max8NumericText Pattern [0-9]{1,8} Total Number of pacs.004 Bulks BBkICF:Max8NumericText Pattern [0-9]{1,8} Total Number of camt.029 Bulks BBkICF:Max8NumericText Pattern [0-9]{1,8} ICF File creation date and time Total number of Credit Transfer bulks in ICF Total number of payment cancellation request bulks in ICF. Total number of return bulks in ICF Total number of the resolution of investigation bulks in ICF Number of bulks within the file is not consistent with the number given. error code: R18 Maximum of 999 bulks per file is permitted error code: S01 Number of bulks within the file is not consistent with the number given error code: R19 Maximum of 999 bulks per file is permitted error code: S01 Number of bulks within the file is not consistent with the number given error code: R20 Maximum of 999 bulks per file is permitted error code: S01 Number of bulks within the file is not consistent with the number given error code: R21 Maximum of 999 bulks per file is permitted error code: S01 BBkICFBlkCdtTrf; SCL SCT; 2017 page 2 of 2

41 Credit Validation File (CVF) Header BBkCVFBlkCdtTrf XML-File-Header Credit Validation File (CVF) Header Use File, bulk and individual transaction rejections of ICF by the. Parsing errors lead to the entire ICF that was submitted being rejected with the error code R10; this is entered into the field File reject reason of the CVF header. In the case of bulk and individual transaction rejections, the pacs sclsct is added to the CVF header. File rejection of BCF by the The CVF header is used for technical and functional errors and when there are insufficient funds. The CVF Header plus pacs sclsct is also used to provide notification of the cancellation of a SEPA credit transfer recalled via camt sct before being settled at another clearing house. The schema BBkCVFBlkCdtTrf specifies the CVF. SCT annex 2 of appendix SCT/BCT/SCL technical specifications BBkCVFBlkCdtTrf page 1 of 1

42 BBkCVFBlkCdtTrf Message structure Status Element/Attribut Format Content Checks SCL BBkCVFBlkCdtTrf BBkCVFBlkCdtTrf 1..1 SndgInst 1..1 RcvgInst 1..1 SrvcId 1..1 TstCode 1..1 Fe 1..1 FileRef BBkCVFBlkCdtTrf +SndgInst BBkCVFBlkCdtTrf +RcvgInst BBkCVFBlkCdtTrf +SrvcId BBkCVFBlkCdtTrf +TstCode BBkCVFBlkCdtTrf +Fe BBkCVFBlkCdtTrf +FileRef Sending Institution BBkCVF:SndgInstBICIdentifier Acceptable Codes MARKDEF0 MARKDEFF Receiving Institution sw5:bicidentifier Pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Service Identifier BBkCVF:SrvcID Acceptable Codes BCT SCT Test Code BBkCVF:TestCodee Acceptable Codes P T File e BBkCVF:FTpe Acceptable Codes CVF File Reference BBkCVF:Max16Text Length Pattern [0-9A-Z]{16,16} 's BIC (production: MARKDEFF; test: MARKDEF0) Recipient s 11-digit BIC (communication partner) "SCT" for rejections of ICF (File-, Bulk- or Tx- rejection) "BCT" for rejections of BCF (File-Rejection) Either T (test) or P (production), depending on the processing environment CVF s reference BBkCVFBlkCdtTrf; SCL SCT; 2017 page 1 of 2

43 BBkCVFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 FileDtTm BBkCVFBlkCdtTrf +FileDtTm 0..1 OrigFRef BBkCVFBlkCdtTrf +OrigFRef 1..1 OrigF 0..1 OrigDtTm BBkCVFBlkCdtTrf +OrigF BBkCVFBlkCdtTrf +OrigDtTm 1..1 FileRjctRsn BBkCVFBlkCdtTrf +FileRjctRsn 1..1 FileBusDt BBkCVFBlkCdtTrf +FileBusDt 1..1 FileCycleNo BBkCVFBlkCdtTrf +FileCycleNo File Date and Time sw5:isodatetime Original File Reference BBkCVF:Max16Text Length Pattern [0-9A-Z]{16,16} Original File BBkCVF:Max32Text Length Original Date And Time sw5:isodatetime File Reject Reason BBkCVF:Text3 File Business Date sw5:isodate File Cycle Number BBkCVF:Max2NumericText Pattern [0-9]{2,2} File creation date and time Given only when ascertainable from original file SWIFT FileAct: original ICF file name; without the constant SCL_ EBICS: Internal by the generated reference. Allows no conclusion about the submitted file. Only when ascertainable Reason for rejection/partial rejection of file Operating day on which the file was created by the Processing phase during which the file was created by the BBkCVFBlkCdtTrf; SCL SCT; 2017 page 2 of 2

44 Settled Credit File (SCF) Header BBkSCFBlkCdtTrf XML-File-Header Settled Credit File (SCF) Header Use Delivery of pacs.004, pacs.008, camt.056 and camt.029-bulks by the to a participant. Each file contains exactly one bulk. The schema file BBkSCFBlkCdtTrf specifies the SCF. SCT annex 3 of appendix SCT/SCL technical specifications BBkSCFBlkCdtTrf page 1 of 1

45 BBkSCFBlkCdtTrf Message structure Status Element/Attribut Format Content Checks SCL BBkSCFBlkCdtTrf BBkSCFBlkCdtTrf 1..1 SndgInst 1..1 RcvgInst 1..1 SrvcId 1..1 TstCode 1..1 Fe 1..1 FileRef BBkSCFBlkCdtTrf +SndgInst BBkSCFBlkCdtTrf +RcvgInst BBkSCFBlkCdtTrf +SrvcId BBkSCFBlkCdtTrf +TstCode BBkSCFBlkCdtTrf +Fe BBkSCFBlkCdtTrf +FileRef 1..1 RoutingInd BBkSCFBlkCdtTrf +RoutingInd Sending Institution BBkSCF:SndgInstBICIdentifier Acceptable Codes MARKDEF0 MARKDEFF Receiving Institution sw8:bicidentifier Pattern [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Service Identifier BBkSCF:SrvcID Acceptable Codes SCT Test Code BBkSCF:TestCodee Acceptable Codes P T File e BBkSCF:FTpe Acceptable Codes SCF File Reference BBkSCF:Max16Text Length Pattern [0-9A-Z]{16,16} Routing Indicator BBkSCF:RoutingInd The 's BIC (production: MARKDEFF; test: MARKDEF0) Recipient s 11-digit BIC (communication partner) SCT Either T (test) or P (production) depending on the processing environment SCF s reference ALL BBkSCFBlkCdtTrf; SCL SCT; 2017 page 1 of 2

46 BBkSCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 FileBusDt BBkSCFBlkCdtTrf +FileBusDt 1..1 FileCycleNo BBkSCFBlkCdtTrf +FileCycleNo Acceptable Codes ALL DIR IND RET File Business Date sw8:isodate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} File Cycle Number BBkSCF:Max2NumericText Pattern [0-9]{2,2} Business day on which the file was created by the Processing phase during which the file was created by the BBkSCFBlkCdtTrf; SCL SCT; 2017 page 2 of 2

47 Bilateral Input Credit File (BCF) Header BBkBCFBlkCdtTrf XML-File-Header Bilateral Credit File (BCF) Header Use Submission of BCT files to the Delivery of BCT files by the Parsing errors result in the file being rejected with the error code R10 The schema file BBkBCFBlkCdtTrf specifies the BCF SCT annex 4 of appendix SCT/BCT/SCL technical specifications BBkBCFBlkCdtTrf page 1 von 1

48 BBkBCFBlkCdtTrf Message structure Status Element/Attribut Format Content Checks SCL BBkBCFBlkCdtTrf BBkBCFBlkCdtTrf 1..1 SndgInst BBkBCFBlkCdtTrf +SndgInst Pattern Sending Institution sw8:bicidentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} For submissions to the : Sender s 11-digit BIC Communication partner s authorisation to submit verified against the BIC of the Instructing Agent on file level. error code: R11 Part of the duplication check error code: R13 For deliveries from the : 1..1 RcvgInst BBkBCFBlkCdtTrf +RcvgInst Pattern Receiving Institution sw8:bicidentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} 's BIC (production: MARKDEFF; test: MARKDEF0) For submissions to the : Check as to whether this element is allocated with the BIC of the error code: R12 For deliveries from the SEPAClearer: Communication partner s 11-digit BIC 1..1 InstgAgt 1..1 FinInstnId BBkBCFBlkCdtTrf +InstgAgt BBkBCFBlkCdtTrf +InstgAgt ++FinInstnId Instructing Agent sw8: SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification sw8: SCLSCTFinancialInstitutionIdentification7 BBkBCFBlkCdtTrf; SCL SCT; 2017 page 1 of 6

49 BBkBCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 BIC BBkBCFBlkCdtTrf +InstgAgt ++FinInstnId +++BIC Pattern BIC sw8:bicidentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Sender s BIC Allocation of the BIC of the BCT-participant which is linked with the TARGET2 sub-account assigned for settlement (<TtlIntrBkSttlmAmt>) with the. The field must be assigned in the file. The submitter must be entitled for the BCT Service. Error code: RIA For submissions to the SEPAClearer: 1..1 InstdAgt 1..1 FinInstnId BBkBCFBlkCdtTrf +InstdAgt BBkBCFBlkCdtTrf +InstdAgt ++FinInstnId 1..1 BIC BBkBCFBlkCdtTrf +InstdAgt ++FinInstnId +++BIC Pattern Instructed Agent sw8: SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification sw8: SCLSCTFinancialInstitutionIdentification7 BIC sw8:bicidentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Check if there is a existing agreement between the submitting and the addressed (field <InstdAgt>) BCT participant Error Code: R97 Allocation of the BIC of the receiving BCT-participant which is linked with the TARGET2 sub-account assigned for settlement (<TtlIntrBkSttlmAmt>) with the. BBkBCFBlkCdtTrf; SCL SCT; 2017 page: 2 of 6

50 BBkBCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 FileRef 1..1 SrvcID 1..1 TstCode 1..1 Fe 1..1 FDtTm BBkBCFBlkCdtTrf +FileRef BBkBCFBlkCdtTrf +SrvcID BBkBCFBlkCdtTrf +TstCode BBkBCFBlkCdtTrf +Fe BBkBCFBlkCdtTrf +FDtTm 1..1 IntrBkSttlmDt BBkBCFBlkCdtTrf +IntrBkSttlmDt Pattern File Reference BBkBCT:Max16Text [0-9A-Z]{16,16} Service Identifier BBkBCT:SrvcID Acceptable Codes BCT Test Code BBkBCT:TestCodee Acceptable Codes P T File e BBkBCT:Fe Acceptable Codes BCF File Date and Time sw8:isodatetime Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Interbank Settlement Date sw8:isodate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} BCT Either T (test) or P (production), depending on the processing environment Error code: R14 BCF File creation date and time Part of the duplication check Error code: R13 The first 8 or 11 characters of the FileRef must match the BIC of <InstgAgt> in BCF. The rest of the field can be freely defined. Error code: RFR Settlement date (Booking date) of the collection For submissions in the submission window with the cut-off the current operating day of the must be given. For submissions in the submission window with the cut-off after 16.00, the next operating day of the must be given. Error Code: RID BBkBCFBlkCdtTrf; SCL SCT; 2017 page: 3 of 6

51 BBkBCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 1..1 TtlIntrBkSttlmAmt Total Interbank Settlement Amount sw8:sclsctcurrencyandamount_2 BBkBCFBlkCdtTrf FractionDigits 2 +TtlIntrBkSttlmAmt TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy sw8:sclsctcurrencycode Use required Acceptable Codes EUR 1..1 TtlNbOfTxs Total Number of Transactions sw8:max15numerictext BBkBCFBlkCdtTrf Pattern [0-9]{1,15} +TtlNbOfTxs 0..1 CTBlk BBkBCFBlkCdtTrf +CTBlk 0..1 NbOfBlk BBkBCFBlkCdtTrf +CTBlk ++NbOfBlk 0..1 NbOfTxs BBkBCFBlkCdtTrf +CTBlk ++NbOfTxs 0..1 IntrBkSttlmAmt The total amount of single transactions Total number of Credit Transfers in the file Credit Transfer Bulk Optional element group for balancing informations Number of Bulks BBkBCT:Max8NumericText Pattern [0-9]{1,8} Number of Transactions sw8:max15numerictext Pattern [0-9]{1,15} Interbank Settlement Amount sw8:sclsctcurrencyandamount_2 BBkBCFBlkCdtTrf FractionDigits 2 +CTBlk TotalDigits 18 ++IntrBkSttlmAmt Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy sw8:sclsctcurrencycode Use required Acceptable Codes EUR 0..1 PCRBlk BBkBCFBlkCdtTrf +PCRBlk 0..1 NbOfBlk BBkBCFBlkCdtTrf +PCRBlk ++NbOfBlk Number of bulks in the file Total number of payment in the bulks Total amount of the bulks Payment Cancellation Request Bulk Optional element group for balancing informations Number of Bulks BBkBCT:Max8NumericText Pattern [0-9]{1,8} Total number of bulks in the file Amount must be at least 0.01 and no more than (Schema validation) Amount must be at least 0.01 and no more than (Schema validation) BBkBCFBlkCdtTrf; SCL SCT; 2017 page: 4 of 6

52 BBkBCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 0..1 NbOfTxs BBkBCFBlkCdtTrf +PCRBlk ++NbOfTxs 0..1 IntrBkSttlmAmt Number of Transactions sw8:max15numerictext Pattern [0-9]{1,15} Interbank Settlement Amount sw8:sclsctcurrencyandamount_2 BBkBCFBlkCdtTrf FractionDigits 2 +PCRBlk TotalDigits 18 ++IntrBkSttlmAmt Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy sw8:sclsctcurrencycode Use required Acceptable Codes EUR 0..1 RFRBlk BBkBCFBlkCdtTrf +RFRBlk 0..1 NbOfBlk BBkBCFBlkCdtTrf +RFRBlk ++NbOfBlk 0..1 NbOfTxs BBkBCFBlkCdtTrf +RFRBlk ++NbOfTxs 0..1 IntrBkSttlmAmt Total number of single transactions in the bulk Total amount of the bulks Return Bulk Optional element group for balancing informations Number of Bulks BBkBCT:Max8NumericText Pattern [0-9]{1,8} Number of Transactions sw8:max15numerictext Pattern [0-9]{1,15} Interbank Settlement Amount sw8:sclsctcurrencyandamount_2 BBkBCFBlkCdtTrf FractionDigits 2 +RFRBlk TotalDigits 18 ++IntrBkSttlmAmt Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy sw8:sclsctcurrencycode Use required Acceptable Codes EUR 0..1 ROIBlk BBkBCFBlkCdtTrf +ROIBlk 0..1 NbOfBlk BBkBCFBlkCdtTrf +ROIBlk ++NbOfBlk Total number of bulks in the file Total number of payment in the bulks Total amount of the bulks Result of Investigation Bulk Optional element group for balancing informations Number of Bulks BBkBCT:Max8NumericText Pattern [0-9]{1,8} Total number of bulks in the file Amount must be at least 0.01 and no more than (Schema validation) Amount must be at least 0.01 and no more than (Schema validation) BBkBCFBlkCdtTrf; SCL SCT; 2017 page: 5 of 6

53 BBkBCFBlkCdtTrf Status Element/Attribut Format Content Checks SCL 0..1 NbOfTxs BBkBCFBlkCdtTrf +ROIBlk ++NbOfTxs 0..1 IntrBkSttlmAmt Number of Transactions sw8:max15numerictext Pattern [0-9]{1,15} Interbank Settlement Amount sw8:sclsctcurrencyandamount_2 BBkBCFBlkCdtTrf FractionDigits 2 +ROIBlk TotalDigits 18 ++IntrBkSttlmAmt Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy sw8:sclsctcurrencycode Use required Acceptable Codes EUR Total number of payment in the bulks Total amount of the bulks Amount must be at least 0.01 and no more than (Schema validation) BBkBCFBlkCdtTrf; SCL SCT; 2017 page: 6 of 6

54 SCT Interbank Payment Dataset (DS-02) pacs Memo SEPA Credit Transfer Interbank Payment Dataset (DS-02) SCT annex 5 of appendix SCT/SCL technical specifications pacs page 1 of 2

55 SCT Interbank Payment Dataset (DS-02) pacs Use of bank-to-bank credit transfer (pacs ) This message is used to transport a payment instruction from the payer s payment service provider to the payee s payment service provider. The message caters for bulk and single payment instructions. ISO message structure A bank-to-bank credit transfer message contains a single group header one or more Credit transfer transaction information sequences, each of which contains a credit transfer instruction as defined in DS-02. Group header The group header contains information required to process the entire message. SCT annex 5 of appendix SCT/SCL technical specifications pacs page 2 of 2

56 pacs Message structure Contents and checks 1..1 FIToFICustomerCreditTransferV GrpHdr +GrpHdr 1..1 MsgId +GrpHdr ++MsgId Pattern Group Header SCLSCTGroupHeader33 Message Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Contains general processing information which applies to each individual payment. Bulk reference number. Part of the duplication check (unique daily reference). Error code: B CreDtTm +GrpHdr ++CreDtTm 1..1 NbOfTxs +GrpHdr ++NbOfTxs Pattern Creation Date Time ISODateTime [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Number Of Transactions Max15NumericText Pattern [0-9]{1,15} The first 8 or 11 characters of Msgld must match the BIC of InstgAgt in the ICF. The rest of the field can be freely defined. Error code: B98 Bulk creation date and time. Total number of single transactions in the bulk. Must not exceed 100,000 (maximum parameter of data records in the bulk). Error code: B02 Total number of datasets must be equal to the actual number of individual data records in the bulk. Error code: B03 pacs ; SCL SCT; 2017 page 1 of 37

57 pacs Contents and checks 1..1 TtlIntrBkSttlmAmt +GrpHdr ++TtlIntrBkSttlmAmt Total Interbank Settlement Amount SCLSCTCurrencyAndAmount_2 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Mandatory Usage Rule: Only 'EUR' is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Total number of single transactions in the bulk. Integer value up to 15 characters allowed. Maximum number of decimal places allowed is two. (Schema validation) Currency designation is always EUR. (Schema validation) The total amount given must equal the sum of the single transactions in the bulk. Error code: B05 required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 IntrBkSttlmDt Interbank Settlement Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} +GrpHdr ++IntrBkSttlmDt Mandatory (AT-42 Settlement Date of the Credit Transfer) Amount must be at least 0.01 and no more than (Schema validation) Settlement date of the bulk. For submissions in the submission windows with the cut-off 8.00, 10.00, 11.00, and the current operating day of the must be given. For submissions in the submission window with the cut-off 20.00, the next operating day of the must be given. Error code: B15 <IntrBkSttlmDt> is part of the duplication check at bulk level (unique daily reference) and individual transaction level. pacs ; SCL SCT; 2017 page 2 of 37

58 pacs Contents and checks 1..1 SttlmInf +GrpHdr ++SttlmInf 1..1 SttlmMtd 1..1 ClrSys +GrpHdr ++SttlmInf +++SttlmMtd +GrpHdr ++SttlmInf +++ClrSys 1..1 Prtry 0..1 InstgAgt +GrpHdr ++SttlmInf +++ClrSys ++++Prtry +GrpHdr ++InstgAgt 1..1 FinInstnId +GrpHdr ++InstgAgt +++FinInstnId Settlement Information SCLSCTSettlementInformation13 Settlement Method SCLSCTSettlementMethod1Code Acceptable Codes CLRG Clearing System SCLSCTClearingSystemIdentification3Choic e Pattern Proprietary SCLSCTId7_2 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Acceptable Codes SCL Instructing Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 Usage Rule: Only CLRG, INGA and INDA are allowed. Usage Rule: Only BIC is allowed. Information on the settlement mechanism. Only the code CLRG is allowed. (Schema validation) Code for the clearing system. For the, only the value SCL is admissible. (Schema validation) pacs ; SCL SCT; 2017 page 3 of 37

59 pacs Contents and checks 1..1 BIC +GrpHdr ++InstgAgt +++FinInstnId ++++BIC Pattern BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Only to be used for submissions to the. Allocation of the BIC of the SCL participant which is linked with the TARGET2 sub-account assigned for settlement with the. Part of duplication check (unique daily reference) Part of the duplication check (unique daily reference). BIC must be contained in the Input Credit File (ICF) and be eligible for submitting payments of this type InstdAgt +GrpHdr ++InstdAgt 1..1 FinInstnId +GrpHdr ++InstdAgt +++FinInstnId 1..1 BIC 1..n +GrpHdr ++InstdAgt +++FinInstnId ++++BIC CdtTrfTxInf Pattern Instructed Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Credit Transfer Transaction Information CreditTransferTransactionInformation11 Usage Rule: Only BIC is allowed. Error code: B10 Only used for deliveries from the (SCF). Allocation of the BIC of the SCL participant which is linked with the TARGET2 sub-account assigned for settlement with the. Error code: B11 pacs ; SCL SCT; 2017 page 4 of 37

60 pacs Contents and checks 1..1 PmtId ++PmtId 0..1 InstrId ++PmtId +++InstrId 1..1 EndToEndId 1..1 TxId ++PmtId +++EndToEndId ++PmtId +++TxId 1..1 PmtTpInf ++PmtTpInf 1..1 SvcLvl ++PmtTpInf +++SvcLvl Payment Identification extension (SCLSCTPaymentIdentification3) Instruction Identification SCLSCTId7 Pattern ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} End to End Identification Transaction Identification SCLSCTId7 Pattern ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Payment e Information SCLSCTPaymenteInformation21 Service Level SCLSCTServiceLevel8Choice (AT-41 Originator's Reference to the Credit Transfer) Usage Rule: A customer reference that must be passed on in the endto-end chain. In the event that no reference was given, 'NOTPROVIDED' must be used. (AT-43 Originator Bank's Reference) Usage Rule: Must contain a reference that is meaningful to the Originator's Bank and is unique over time. Usage Rule: "Payment e Information" must be present in either "Group Header" or "Credit Transaction Information". Mandatory Reference number of the instructing agent ( own ref ). Point-to-point reference. Payer s reference. If the end-to-end ID is not given, 'NOTPROVIDED must be entered. There is no provision for a check using the. Reference of the remitting payment service provider. Transaction ID is part of the duplication check at single record level. Error code: AM05 Only intended at single record level in the. Only intended at single record level in the. pacs ; SCL SCT; 2017 page 5 of 37

61 pacs Contents and checks 1..1 Cd 0..1 LclInstrm ++PmtTpInf +++SvcLvl ++++Cd ++PmtTpInf +++LclInstrm 1..1 Cd ++PmtTpInf +++LclInstrm ++++Cd 1..1 Prtry ++PmtTpInf +++LclInstrm ++++Prtry 0..1 CtgyPurp ++PmtTpInf +++CtgyPurp Code SCLSCTExternalServiceLevel1Code Acceptable Codes SEPA Local Instrument SCLSCTLocalInstrument2Choice Code ExternalLocalInstrument1Code Pattern Proprietary SCLSCTId8 ([A-Za-z0-9] [+ \? / \- : \( \) \., ' \s]){1,35} Category Purpose CategoryPurpose1Choice (AT-40 Identification code of the scheme) Usage Rule: Only "SEPA" is allowed. Usage Rule: Only used if bilaterally agreed between the Debtor Bank and the Creditor Bank. (AT-45 Category purpose of the Credit Transfer) Usage Rule: Depending on the agreement between the Originator and the Originator Bank, "Category Purpose" may be forwarded to the Beneficiary Bank. In the, only the code SEPA is admissible. (Schema validation) <Cd> and <Prtry> (see below) cannot be used simultaneously. No entry is required for submissions to the SCL, whereas for deliveries from the SLC an entry may be made in the field. There is no validation by the SCL. <Cd> (see above) and <Prtry> cannot be used simultaneously. No entry is required for submissions to the SCL, whereas for deliveries from the SCL an entry may be made in the field. There is no validation by the SCL. No plausibility check if <Purp> and<ctgy purp> fields both contain entries, ie SCL ignores conflicting entries. pacs ; SCL SCT; 2017 page 6 of 37

62 pacs Contents and checks 1..1 Cd 1..1 Prtry ++PmtTpInf +++CtgyPurp ++++Cd ++PmtTpInf +++CtgyPurp ++++Prtry 1..1 IntrBkSttlmAmt ++IntrBkSttlmAmt Code ExternalCategoryPurpose1Code Length Proprietary Interbank Settlement Amount SCLSCTCurrencyAndAmount_3 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} (AT-04 Amount of the Credit Transfer in Euro) Usage Rule: Only 'EUR' is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Category purpose. <Cd> and <Prtry> (see below) cannot be used simultaneously. Field may be completed in accordance with the external code list (ISO 20022) to specify the purpose of a transaction. There is no validation by the SCL. A maximum of four characters may be entered. No entry is required for submissions to the SCL, whereas for deliveries from the SCL an entry may be made in the field. Category purpose. <Cd> and <Prtry> (see above) cannot be used simultaneously. No entry is required for submissions to the SCL, whereas for deliveries from the SCL an entry may be made in the field. There is no validation by the SCL. The amount of the relevant transfer. The currency designation must be EUR. (Schema validation) A maximum of two decimal places may be used (Schema validation) Must not exceed permitted maximum amount ( ) and must be greater than (Schema validation) pacs ; SCL SCT; 2017 page 7 of 37

63 pacs Contents and checks required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 ChrgBr Charge Bearer ++ChrgBr SCLSCTChargeBearere1Code Acceptable Codes SLEV 0..1 InstgAgt Instructing Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 ++InstgAgt 1..1 FinInstnId Financial Institution Identification ++InstgAgt +++FinInstnId 1..1 BIC ++InstgAgt +++FinInstnId ++++BIC Pattern SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Usage Rule: Only 'SLEV' is allowed. Usage Rule: Only BIC is allowed. Only SLEV is allowed. (Schema validation) Original submitter of the credit transfer. Only used in the Settled Credit File (SCF). Original submitter of the bulk that contained the credit transfer when submitted to the. Only used in the Settled Credit File (SCF), may not be included in the Input Credit File (ICF) of the SCL participant. Error code: XT13 pacs ; SCL SCT; 2017 page 8 of 37

64 pacs Contents and checks 0..1 UltmtDbtr ++UltmtDbtr 0..1 Nm 0..1 Id ++UltmtDbtr +++Nm ++UltmtDbtr +++Id 1..1 OrgId ++UltmtDbtr +++Id ++++OrgId 1..1 BICOrBEI ++UltmtDbtr +++Id ++++OrgId +++++BICOrBEI Max70Text Length Pattern Ultimate Debtor SCLSCTPartyIdentification321 Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} (AT-08 of the Originator Reference Party) Usage Rule: "" is limited to 70 characters in length. (AT-09 Identification code of the Originator Reference Party) Usage Rule: Either "BICOrBEI" or one occurrence of "Other" is allowed. Ultimate debtor of the ultimate debtor. Either Organisation Id or one occurrence of Private identification admissible. (Schema validation) The Organisation Id of the ultimate debtor. Either BICOrBEI or Othr admissible. pacs ; SCL SCT; 2017 page 9 of 37

65 pacs Contents and checks 1..1 Othr ++UltmtDbtr +++Id ++++OrgId +++++Othr 1..1 Id ++UltmtDbtr +++Id ++++OrgId +++++Othr 0..1 SchmeNm ++UltmtDbtr +++Id ++++OrgId +++++Othr SchmeNm 1..1 Cd ++UltmtDbtr +++Id ++++OrgId +++++Othr SchmeNm Cd Identification Other GenericOrganisationIdentification1 Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length The Organisation Id of the ultimate debtor. Either BICOrBEI or Othr admissible. pacs ; SCL SCT; 2017 page 10 of 37

66 pacs Contents and checks 1..1 Prtry ++UltmtDbtr +++Id ++++OrgId +++++Othr SchmeNm Prtry 0..1 Issr ++UltmtDbtr +++Id ++++OrgId +++++Othr Issr 1..1 PrvtId ++UltmtDbtr +++Id ++++PrvtId 1..1 DtAndPlcOfBirth ++UltmtDbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth 1..1 BirthDt Proprietary Issuer Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Usage Rule: Either "Date and The Private Id of the ultimate debtor. Place of Birth" or one occurrence of Either Organisation Id or one occurrence of "Other" is allowed. Private Id admissible. (Schema validation). pacs ; SCL SCT; 2017 page 11 of 37

67 pacs Contents and checks ++UltmtDbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++UltmtDbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth ++UltmtDbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++UltmtDbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CtryOfBirth Province of Birth City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} pacs ; SCL SCT; 2017 page 12 of 37

68 pacs Contents and checks 1..1 Othr 1..1 Id ++UltmtDbtr +++Id ++++PrvtId +++++Othr ++UltmtDbtr +++Id ++++PrvtId +++++Othr 0..1 SchmeNm ++UltmtDbtr +++Id ++++PrvtId +++++Othr SchmeNm 1..1 Cd ++UltmtDbtr +++Id ++++PrvtId +++++Othr SchmeNm Cd Other GenericPersonIdentification1 Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length pacs ; SCL SCT; 2017 page 13 of 37

69 pacs Contents and checks 1..1 Prtry ++UltmtDbtr +++Id ++++PrvtId +++++Othr SchmeNm Prtry 0..1 Issr ++UltmtDbtr +++Id ++++PrvtId +++++Othr Issr 1..1 Dbtr ++Dbtr 1..1 Nm ++Dbtr +++Nm 0..1 PstlAdr ++Dbtr +++PstlAdr Proprietary Issuer Debtor SCLSCTPartyIdentification322 Max70Text Length Postal Address SCLSCTPostalAddress6 Mandatory (AT-02 of the Orignator) Usage Rule: is limited to 70 characters in length. (AT-03 Address of the Originator) Payer of the payer. Address of the payer. pacs ; SCL SCT; 2017 page 14 of 37

70 pacs Contents and checks 0..1 Ctry ++Dbtr +++PstlAdr ++++Ctry 0..2 AdrLine 0..1 Id ++Dbtr +++PstlAdr ++++AdrLine ++Dbtr +++Id 1..1 OrgId ++Dbtr +++Id ++++OrgId 1..1 BICOrBEI ++Dbtr +++Id ++++OrgId +++++BICOrBEI Pattern Country CountryCode [A-Z]{2,2} Address Line Max70Text Length Pattern Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Usage Rule: Only two occurrences of 'Address Line' are allowed. (AT-10 Originator's Identification Code). Usage Rule: Either BIC or BEI or one occurrence of Other is allowed. Country of payer according to address given. Must be an acceptable country code in accordance with ISO 3166 Error code: XT73 Address of the payer. "Address line may not occur more than twice. (Schema validation) Identification of the payer. Either Organisation Id or one occurrence of Private Id admissible (schema validation). May not be specified simultaneously with Id/PrvtId (see below). (Schema validation) All ISO options are allowed. The Organisation Id of the payer. Either <BICOrBEI> or <Othr> admissible. May not be specified simultaneously with <Id><PrvtId> (see below). (Schema validation) All ISO options are allowed. pacs ; SCL SCT; 2017 page 15 of 37

71 pacs Contents and checks 1..1 Othr 1..1 Id ++Dbtr +++Id ++++OrgId +++++Othr ++Dbtr +++Id ++++OrgId +++++Othr 0..1 SchmeNm ++Dbtr +++Id ++++OrgId +++++Othr SchmeNm 1..1 Cd ++Dbtr +++Id ++++OrgId +++++Othr SchmeNm Cd Identification Other GenericOrganisationIdentification1 Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length The Organisation Id of the payer. Either <BICOrBEI> or <Othr> admissible. pacs ; SCL SCT; 2017 page 16 of 37

72 pacs Contents and checks 1..1 Prtry ++Dbtr +++Id ++++OrgId +++++Othr SchmeNm Prtry 0..1 Issr ++Dbtr +++Id ++++OrgId +++++Othr Issr 1..1 PrvtId ++Dbtr +++Id ++++PrvtId 1..1 DtAndPlcOfBirth ++Dbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth Proprietary Issuer Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth Usage Rule: Either "Date and May not be specified simultaneously with Place of Birth" or one occurrence of <Id><OrgId> (see above). "Other" is allowed. (Schema validation) pacs ; SCL SCT; 2017 page 17 of 37

73 pacs Contents and checks 1..1 BirthDt ++Dbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++Dbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth ++Dbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++Dbtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CtryOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} pacs ; SCL SCT; 2017 page 18 of 37

74 pacs Contents and checks 1..1 Othr 1..1 Id ++Dbtr +++Id ++++PrvtId +++++Othr ++Dbtr +++Id ++++PrvtId +++++Othr 0..1 SchmeNm ++Dbtr +++Id ++++PrvtId +++++Othr SchmeNm 1..1 Cd ++Dbtr +++Id ++++PrvtId +++++Othr SchmeNm Cd Other GenericPersonIdentification1 Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length pacs ; SCL SCT; 2017 page 19 of 37

75 pacs Contents and checks 1..1 Prtry ++Dbtr +++Id ++++PrvtId +++++Othr SchmeNm Prtry 0..1 Issr ++Dbtr +++Id ++++PrvtId +++++Othr Issr 1..1 DbtrAcct 1..1 Id ++DbtrAcct ++DbtrAcct +++Id 1..1 IBAN ++DbtrAcct +++Id ++++IBAN Proprietary Issuer Debtor Account SCLSCTCashAccount161 Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier Pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Mandatory (AT-01 Account Number of the Originator) Usage Rule: Only IBAN is allowed. IBAN of the payer. IBAN of the payer. Check in accordance with ISO Error code: XD19 Check of the first two characters that they correspond to a valid ISO or SEPA country code. Error code: XT73 pacs ; SCL SCT; 2017 page 20 of 37

76 pacs Contents and checks 1..1 DbtrAgt ++DbtrAgt 1..1 FinInstnId ++DbtrAgt +++FinInstnId 1..1 BIC ++DbtrAgt +++FinInstnId ++++BIC Pattern Debtor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} (AT-06 BIC of the Originator Bank) Usage Rule: Only BIC is allowed. BIC of the Originator Bank BIC of the Originator Bank Validity check of BIC against SCL-Directory. Error code: XT27 General addressability check: BIC must be addressable within the. Error code: PY01 Check only if credit transfer is forwarded from the to EBA CLEARING: BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service. Error code: PY01 The debtor agent BIC is part of the duplication check at single record level Error code: AM05 pacs ; SCL SCT; 2017 page 21 of 37

77 pacs Contents and checks 1..1 CdtrAgt ++CdtrAgt 1..1 FinInstnId ++CdtrAgt +++FinInstnId 1..1 BIC 1..1 Cdtr ++CdtrAgt +++FinInstnId ++++BIC ++Cdtr Pattern Creditor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creditor SCLSCTPartyIdentification322 (AT-23 BIC of the Beneficiary Bank) Usage Rule: Only BIC is allowed. BIC of the Beneficiary Bank BIC of the Beneficiary Bank Validity check of BIC against SCL-Directory. Error code: XT27 Check only if credit transfer is forwarded from the to EBA CLEARING: BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service. Error code: PY01 Creditor pacs ; SCL SCT; 2017 page 22 of 37

78 pacs Contents and checks 1..1 Nm ++Cdtr +++Nm 0..1 PstlAdr ++Cdtr +++PstlAdr 0..1 Ctry ++Cdtr +++PstlAdr ++++Ctry 0..2 AdrLine 0..1 Id ++Cdtr +++PstlAdr ++++AdrLine ++Cdtr +++Id Max70Text Length Postal Address SCLSCTPostalAddress6 Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Identification SCLSCTParty6Choice Mandatory (AT-21 of the Beneficiary) Usage Rule: "" is limited to 70 characters in length. (AT-22 Address of the Beneficiary) Usage Rule: Only two occurrences of 'Address Line' are allowed. (AT-24 Beneficiary Identification Code) of creditor Address of the creditor. Country of creditor according to the address given. Must be a valid country code according to ISO3166. Error code: XT73. Address of the creditor. "Address line may not occur more than twice (Schema validation). Identification of the creditor. pacs ; SCL SCT; 2017 page 23 of 37

79 pacs Contents and checks 1..1 OrgId ++Cdtr +++Id ++++OrgId Organisation Identification SCLSCTOrganisationIdentification41 Usage Rule: Either BIC or BEI or one occurrence of Other is allowed. The Organisation Id of the beneficiary. Either <BICOrBEI> or <Othr> admissible May not be specified simultaneously with <Id><PrvtId> (see below). (Schema validation) All ISO options are allowed BICOrBEI ++Cdtr +++Id ++++OrgId +++++BICOrBEI 1..1 Othr 1..1 Id ++Cdtr +++Id ++++OrgId +++++Othr ++Cdtr +++Id ++++OrgId +++++Othr Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 pacs ; SCL SCT; 2017 page 24 of 37

80 pacs Contents and checks 0..1 SchmeNm ++Cdtr +++Id ++++OrgId +++++Othr SchmeNm 1..1 Cd ++Cdtr +++Id ++++OrgId +++++Othr SchmeNm Cd 1..1 Prtry ++Cdtr +++Id ++++OrgId +++++Othr SchmeNm Prtry 0..1 Issr ++Cdtr +++Id ++++OrgId +++++Othr Issr Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary Issuer pacs ; SCL SCT; 2017 page 25 of 37

81 pacs Contents and checks 1..1 PrvtId ++Cdtr +++Id ++++PrvtId 1..1 DtAndPlcOfBirth ++Cdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth 1..1 BirthDt ++Cdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++Cdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth PrvcOfBirth Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth Usage Rule: Either Date and Place of Birth or one occurrence of Other is allowed. May not be specified simultaneously with <Id><OrgId> (see above). (Schema validation) All ISO options are allowed. pacs ; SCL SCT; 2017 page 26 of 37

82 pacs Contents and checks 1..1 CityOfBirth ++Cdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++Cdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CtryOfBirth 1..1 Othr 1..1 Id ++Cdtr +++Id ++++PrvtId +++++Othr ++Cdtr +++Id ++++PrvtId +++++Othr City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification pacs ; SCL SCT; 2017 page 27 of 37

83 pacs Contents and checks 0..1 SchmeNm ++Cdtr +++Id ++++PrvtId +++++Othr SchmeNm 1..1 Cd ++Cdtr +++Id ++++PrvtId +++++Othr SchmeNm Cd 1..1 Prtry ++Cdtr +++Id ++++PrvtId +++++Othr SchmeNm Prtry Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary pacs ; SCL SCT; 2017 page 28 of 37

84 pacs Contents and checks 0..1 Issr ++Cdtr +++Id ++++PrvtId +++++Othr Issr 1..1 CdtrAcct 1..1 Id ++CdtrAcct ++CdtrAcct +++Id 1..1 IBAN 0..1 UltmtCdtr ++CdtrAcct +++Id ++++IBAN ++UltmtCdtr 0..1 Nm Issuer Pattern Max70Text Length Creditor Account SCLSCTCashAccount161 Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Ultimate Creditor SCLSCTPartyIdentification321 Mandatory (AT-20 Account of the Beneficiary) Usage Rule: Only IBAN is allowed. (AT-28 of the Beneficiary Reference Party) Usage Rule: "" is limited to 70 characters in length. IBAN of the creditor. IBAN of the creditor. Check in accordance with ISO Error code XD19 Check as to whether the first two characters match a valid ISO code or SEPA country code. Error code XT73 Ultimate creditor of ultimate creditor. pacs ; SCL SCT; 2017 page 29 of 37

85 pacs Contents and checks 0..1 Id ++UltmtCdtr +++Nm ++UltmtCdtr +++Id 1..1 OrgId ++UltmtCdtr +++Id ++++OrgId 1..1 BICOrBEI ++UltmtCdtr +++Id ++++OrgId +++++BICOrBEI 1..1 Othr 1..1 Id ++UltmtCdtr +++Id ++++OrgId +++++Othr ++UltmtCdtr +++Id ++++OrgId +++++Othr WhiteSpace Pattern collapse Identification SCLSCTParty6Choice Identification Organisation Identification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 (AT-29 Identification code of the Beneficiary Reference Party) Usage Rule: Either "BIC or BEI" or one occurrence of "Other" is allowed. Either Organisation Id or one occurence of the Private Identification admissibe (Schema validation). The Organisation Id of the ultimate creditor. Either <BICOrBEI> or <Othr> admissible. pacs ; SCL SCT; 2017 page 30 of 37

86 pacs Contents and checks 0..1 SchmeNm ++UltmtCdtr +++Id ++++OrgId +++++Othr SchmeNm 1..1 Cd ++UltmtCdtr +++Id ++++OrgId +++++Othr SchmeNm Cd 1..1 Prtry ++UltmtCdtr +++Id ++++OrgId +++++Othr SchmeNm Prtry 0..1 Issr ++UltmtCdtr +++Id ++++OrgId +++++Othr Issr Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary Issuer pacs ; SCL SCT; 2017 page 31 of 37

87 pacs Contents and checks 1..1 PrvtId ++UltmtCdtr +++Id ++++PrvtId 1..1 DtAndPlcOfBirth ++UltmtCdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth 1..1 BirthDt ++UltmtCdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++UltmtCdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth PrvcOfBirth Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth Usage Rule: Either "Date and The Private Id of the ultimate creditor. Either Place of Birth" or one occurrence of Organisation Id or oneoccurence of the Private "Other" is allowed. Identification admissible (Schema validation). pacs ; SCL SCT; 2017 page 32 of 37

88 pacs Contents and checks 1..1 CityOfBirth ++UltmtCdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++UltmtCdtr +++Id ++++PrvtId +++++DtAndPlcOfBirth CtryOfBirth 1..1 Othr 1..1 Id ++UltmtCdtr +++Id ++++PrvtId +++++Othr ++UltmtCdtr +++Id ++++PrvtId +++++Othr City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification pacs ; SCL SCT; 2017 page 33 of 37

89 pacs Contents and checks 0..1 SchmeNm ++UltmtCdtr +++Id ++++PrvtId +++++Othr SchmeNm 1..1 Cd ++UltmtCdtr +++Id ++++PrvtId +++++Othr SchmeNm Cd 1..1 Prtry ++UltmtCdtr +++Id ++++PrvtId +++++Othr SchmeNm Prtry 0..1 Issr ++UltmtCdtr +++Id ++++PrvtId +++++Othr Issr Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary Issuer pacs ; SCL SCT; 2017 page 34 of 37

90 pacs Contents and checks 0..1 Purp ++Purp 1..1 Cd 0..1 RmtInf ++Purp +++Cd ++RmtInf 1..1 Ustrd ++RmtInf +++Ustrd Purpose Purpose2Choice Code ExternalPurpose1Code Length Remittance Information SCLSCTRemittanceInformation5 Unstructured Max140Text Length (AT-44 Purpose of the Credit Transfer) (AT-05 Remittance Information) Usage Rule: Either 'Structured' or 'Unstructured', may be present. Purpose of the CreditTransfer. No plausibility check if <Purp> and<ctgypurp> fields both contain entries, ie SCL ignores conflicting entries. Purpose of transaction. Field may be completed in accordance with the external code list (ISO 20022). There is no validation by the SCL. A maximum of four characters may be entered. No entry is required for submissions to the SCL, whereas for deliveries from the SLC an entry may be made in the field. Structured or unstructured remittance information. (Schema validation) Usage Rule: 'Unstructured' may Unstructured remittance information. carry structured remittance information, as agreed between the Either structured or unstructured remittance Originator and the Beneficiary. information can be used. Usage Rule: Only one occurrence (Schema validation). of 'Unstructured' is allowed. Field may not occur more than once pacs ; SCL SCT; 2017 page 35 of 37

91 pacs Contents and checks 1..1 Strd ++RmtInf +++Strd Structured SCLSCTStructuredRemittanceInformation7 Format Rule: Structured can be Structured remittance information. used, provided the tags and the data within the Structured Either structured or unstructured remittance element do not exceed 140 information can be used. (Schema validation). characters in length. Field may not occur more than once and the data Usage Rule: within the Structured element may not be more Only one occurrence of Structured than 140 characters in length. Only information is allowed within the <Strd> element is counted. The elements including the contents within the tag <Strd> are also counted. Error code: XT CdtrRefInf ++RmtInf +++Strd ++++CdtrRefInf 1..1 Tp ++RmtInf +++Strd ++++CdtrRefInf +++++Tp 1..1 CdOrPrtry ++RmtInf +++Strd ++++CdtrRefInf +++++Tp CdOrPrtry Creditor Reference Information SCLSCTCreditorReferenceInformation2 e SCLSCTCreditorReferencee2 Code or Proprietary SCLSCTCreditorReferencee1Choice Usage Rule: When present, the Debtor Bank is not obliged to validate the reference information. Usage Rule: When used both "e" and "Reference" must be present. All ISO field options are allowed. pacs ; SCL SCT; 2017 page 36 of 37

92 pacs Contents and checks 1..1 Cd 0..1 Issr ++RmtInf +++Strd ++++CdtrRefInf +++++Tp CdOrPrtry Cd ++RmtInf +++Strd ++++CdtrRefInf +++++Tp Issr 1..1 Ref ++RmtInf +++Strd ++++CdtrRefInf +++++Ref Code SCLSCTe3Code Acceptable Codes SCOR Issuer Reference Usage Rule: Only "SCOR" is allowed. Creditor reference. If <CdtrRefInf> is used, it is necessary to complete Tp and Ref. Only code SCOR may be entered (Schema validation). Usage Rule: If a Creditor Reference The creditor reference. If CdtrRefInf is used, Tp contains a check digit, the receiving and Ref must be completed. It is possibe to bank is not required to validate this. specify a structured creditor reference. Usage Rule: If the receiving bank This reference is to be structured in accordance validates the check digit and if this with ISO validation fails, the bank may (RFnnaaaaaaaaaaaaaaaaaaaaa); maximum continue its processing and send length of 25 characters. the transaction to the next party in There is no validation by the SCL. the chain. Usage Rule: RF Creditor Reference may be used (ISO 11649). pacs ; SCL SCT; 2017 page 37 of 37

93 SCT Interbank Credit Transfer Reject Dataset (DS-03) pacs sclsct Memo SEPA Credit Transfer Interbank Credit Transfer Reject Dataset (DS-03) SCT annex 6 of appendix SCT/SCL technical specifications pacs sclsct page 1 of 2

94 SCT Interbank Credit Transfer Reject Dataset (DS-03) pacs sclsct Use of the interbank credit transfer reject dataset (pacs sclsct) This message is a rejection message from the in the event of an error to notify the SCL participant about rejected credit transfers or return ( R ) messages (at the validation stage). Submitted bulks which are not covered are rejected with the error code AM04 (insufficient funds). The message caters for bulk and single reject instructions. Main difference between pacs.002scl and Implementation Guideline compliant pacs.002 message: 1. Along with the relevant ISO and SEPA error codes, in the status reason/proprietary field, error codes specific to the SEPA- Clearer (SCL) (see separate list of error codes) are also used by the SCL. 2. The group header does not contain an instructing agent or instructed agent. 3. Within the original transaction reference, no exact copy is returned; only the following information is given. <IntrBkSttlmAmt> the amount of the original transaction <IntrBkSttlmDt> the original interbank settlement date <CdtrAgt><FinInstnId><BIC> the original creditor agent 4. The number of transactions per status for the payments rejected by the is provided in the original group information and status sequence (only negative acknowledgement). Group header The group header contains information required to process the entire message. SCT annex 6 of appendix SCT/SCL technical specifications pacs sclsct page 2 of 2

95 pacs sclsct Message structure Contents and checks 1..1 FIToFIPmtStsRptSCL +FIToFIPmtStsRptSCL 1..1 GrpHdr +FIToFIPmtStsRptSCL ++GrpHdr 1..1 MsgId +FIToFIPmtStsRptSCL ++GrpHdr +++MsgId 1..1 CreDtTm +FIToFIPmtStsRptSCL ++GrpHdr +++CreDtTm 1..1 OrgnlGrpInfAndSts +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts 1..1 OrgnlMsgId +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++OrgnlMsgId FIToFIPaymentStatusReportV03 Group Header SCLSCTGroupHeader37 Message Identification SCLSCTId7 Pattern ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Creation Date Time ISODateTime Original Group Information And Status OriginalGroupInformation20 Original Message Identification Contains general processing information which applies to all payment.s file reference. Bulk creation date and time in the. Contains general information from the original group header which is relevant for all payments. The <MsgId> of original bulk. pacs sclsct; SCL SCT; 2017 page 1 of 10

96 pacs sclsct Contents and checks 1..1 OrgnlMsgNmId +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++OrgnlMsgNmId 1..1 OrgnlNbOfTxs +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++OrgnlNbOfTxs 1..1 OrgnlCtrlSum +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++OrgnlCtrlSum 1..1 GrpSts 1..1 StsRsnInf +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++GrpSts +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf Original Message Identification _Codes Acceptable Codes camt.029 camt.056 pacs.004 pacs.008 Original Number of Transactions Max15NumericText Pattern [0-9]{1,15} Original Control Sum SCLSCTCurrencyAndAmount_Simplee FractionDigits 2 TotalDigits 18 Inclusive 0.. Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Group Status SCLSCTTransactionGroupStatus3Code Acceptable Codes PART RJCT Status Reason Information SCLSCTStatusReasonInformation8 Message type of the rejected original bulk. Total number of received individual payments from the original bulk. Total amount from the original bulk in euro. RJCT: displayed by if the bulk is completely rejected. (Also applies for rejection due to insufficient funds) PART: displayed by if the bulk is partially rejected. pacs sclsct; SCL SCT; 2017 page 2 of 10

97 pacs sclsct Contents and checks 1..1 Orgtr 1..1 Id +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Orgtr +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Orgtr +++++Id 1..1 OrgId +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Orgtr +++++Id OrgId 1..1 BICOrBEI +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Orgtr +++++Id OrgId BICOrBEI Pattern Originator SCLSCTId5 Identification SCLSCTParty3Choice Organisation Identification SCLSCTOrganisationIdentification4 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Originator of the reject. The BIC of the (production: MARKDEFF, test: MARKDEF0) initiating the reject. pacs sclsct; SCL SCT; 2017 page 3 of 10

98 pacs sclsct Contents and checks 1..1 Rsn +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Rsn 1..1 Cd 1..1 Prtry +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Rsn +++++Cd +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++StsRsnInf ++++Rsn +++++Prtry 0..1 NbOfTxsPerSts +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++NbOfTxsPerSts 1..1 DtldNbOfTxs +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++NbOfTxsPerSts ++++DtldNbOfTxs Reason StatusReason6Choice Code SCLSCTExternalStatusReason1Code Acceptable Codes ED05 Proprietary Number of Transactions Per Status NumberOfTransactionsPerStatus3 Detailed Number Of Transactions Max15NumericText Pattern [0-9]{1,15} Not completed by SCL. Proprietary error code of the (see error codes in the technical specifications) Information on transactions rejected by the.(only completed in the case of a partial rejection) Number of transactions that were rejected. Only given when the Group Status contains the code PART. pacs sclsct; SCL SCT; 2017 page 4 of 10

99 pacs sclsct Contents and checks 1..1 DtldSts 1..1 DtldCtrlSum 0..n +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++NbOfTxsPerSts ++++DtldSts +FIToFIPmtStsRptSCL ++OrgnlGrpInfAndSts +++NbOfTxsPerSts ++++DtldCtrlSum TxInfAndSts +FIToFIPmtStsRptSCL AndSts 1..1 StsId +FIToFIPmtStsRptSCL AndSts +++StsId 0..1 OrgnlInstrId +FIToFIPmtStsRptSCL AndSts +++OrgnlInstrId Detailed Status SCLSCTTransactionIndividualStatus1Code Acceptable Codes RJCT Detailed Control Sum SCLSCTCurrencyAndAmount_Simplee FractionDigits 2 TotalDigits 18 Inclusive 0.. Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Pattern Pattern Transaction Information And Status PaymentTransactionInformation26 Status Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original Instruction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Status of transactions. Only given when the Group Status contains the code PART. Here only the code RJCT is possible. Total amount of the rejected transactions. Only given when the <GrpSts> contains the code PART Only completed in the case of a partial rejection. Reference number of the transaction, issued by the. The Original Instruction ID of the underlying transaction. Is only given here if it already existed in the original transaction. pacs sclsct; SCL SCT; 2017 page 5 of 10

100 pacs sclsct Contents and checks 1..1 OrgnlEndToEndId +FIToFIPmtStsRptSCL AndSts +++OrgnlEndToEndId 1..1 OrgnlTxId +FIToFIPmtStsRptSCL AndSts +++OrgnlTxId 1..1 TxSts 1..1 StsRsnInf +FIToFIPmtStsRptSCL AndSts +++TxSts +FIToFIPmtStsRptSCL AndSts +++StsRsnInf 1..1 Orgtr +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Orgtr Original End To End Identification Original Transaction Identification SCLSCTId7 Pattern ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Transaction Status TransactionIndividualStatus3Code Acceptable Codes RJCT Status Reason Information SCLSCTStatusReasonInformation9 Originator SCLSCTId5 The reference of originator (End to End Id) of the original transaction. Reference of the payment service provider (transaction Id) of the rejected transfer (for pacs.008 = <TxId>, for pacs.004 = <RtrId>, for camt.056 = <CxIId>, for camt.029 = <CxIStsId>) Status of the individual transaction. Only the code RJCT is allowed. Originator oft he reject pacs sclsct; SCL SCT; 2017 page 6 of 10

101 pacs sclsct Contents and checks 1..1 Id +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Orgtr +++++Id 1..1 OrgId +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Orgtr +++++Id OrgId 1..1 BICOrBEI +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Orgtr +++++Id OrgId BICOrBEI 1..1 Rsn +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Rsn Pattern Identification SCLSCTParty3Choice Organisation Identification SCLSCTOrganisationIdentification4 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Reason StatusReason7Choice The BIC of the (production: MARKDEFF, test: MARKDEF0) initiating the reject. pacs sclsct; SCL SCT; 2017 page 7 of 10

102 pacs sclsct Contents and checks 1..1 Cd 1..1 Prtry +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Rsn +++++Cd +FIToFIPmtStsRptSCL AndSts +++StsRsnInf ++++Rsn +++++Prtry 0..1 OrgnlTxRef +FIToFIPmtStsRptSCL AndSts 1..1 IntrBkSttlmAmt +FIToFIPmtStsRptSCL AndSts ++++IntrBkSttlmAmt Acceptable Codes AM01 AM02 AM05 DT01 ED05 Proprietary Code SCLSCTExternalStatusReason2Code Original Transaction Reference OriginalTransactionReference13 Interbank Settlement Amount SCLSCTCurrencyAndAmount FractionDigits 2 TotalDigits 18 Inclusive 0.. Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Not completed by the SCL. Error code of the if the individual transaction is rejected. ISO defined codes and proprietary codes possible. Field is formatted as follows in the event of certain errors: [Code] [space][erroneous XML tag] Parts of the original message : <IntrBkSttlmAmt>: the amount of the original message <IntrBkSttlmDt>: settlement date of the original message. <DbtrAgt>/<FinInstnId>/<BIC>: BIC of the originator bank of the original message. Amount of the original message (dependent on payment type). In pacs.008 = interbank settlement amount In pacs.004 = returned interbank settlement amount. In camt.056 = Original Interbank Settlement Amount In camt.029 = Interbank Settlement Amount pacs sclsct; SCL SCT; 2017 page 8 of 10

103 pacs sclsct required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 IntrBkSttlmDt Interbank Settlement Date +FIToFIPmtStsRptSCL AndSts ++++IntrBkSttlmDt ISODate 1..1 DbtrAgt Debtor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 +FIToFIPmtStsRptSCL AndSts ++++DbtrAgt 1..1 FinInstnId Financial Institution Identification +FIToFIPmtStsRptSCL AndSts ++++DbtrAgt +++++FinInstnId 1..1 BIC +FIToFIPmtStsRptSCL AndSts ++++DbtrAgt +++++FinInstnId BIC Pattern SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1}. Contents and checks The interbank settlement date of the original message. BIC of the originating payment service provider according to original message. pacs sclsct; SCL SCT; 2017 page 9 of 10

104 pacs sclsct Contents and checks 1..1 CdtrAgt +FIToFIPmtStsRptSCL AndSts ++++CdtrAgt 1..1 FinInstnId +FIToFIPmtStsRptSCL AndSts ++++CdtrAgt +++++FinInstnId 1..1 BIC +FIToFIPmtStsRptSCL AndSts ++++CdtrAgt +++++FinInstnId BIC Pattern Creditor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} BIC of the creditor agent according to the original message pacs sclsct; SCL SCT; 2017 page 10 of 10

105 SCT Interbank Return Credit Transfer Dataset (DS-03) pacs sct Memo SEPA Credit Transfer Interbank Return Credit Transfer Dataset (DS-03) SCT annex 7 of appendix SCT/SCL technical specifications pacs page 1 of 2

106 SCT Interbank Return Credit Transfer Dataset (DS-03) pacs sct Use of the interbank payment returns (pacs ) The message is used to transport credit transfer returns instruction between credit institutions, directly or through intermediaries. The message caters only for single return instructions. Notes Attribute R1 is implied by the message name 'pacs.004' and the original message name identification 'pacs.008'. Message elements under the original transaction reference sequence are based on DS-02 attributes. ISO message structure An interbank payment return message contains: a single group header one or more credit transfer transaction information sequences, each of which contains a credit transfer return instruction as defined in DS-03. Group header The group header contains information required to process the entire message. SCT annex 7 of appendix SCT/SCL technical specifications pacs page 1 of 2

107 pacs sct Message structure Contents and checks 1..1 PmtRtr PaymentReturnV GrpHdr ++GrpHdr 1..1 MsgId ++GrpHdr +++MsgId Pattern Group Header SCLSCTGroupHeader38 Message Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Contains general processing information which applies to the whole payment. Reference No of the bulk. Part of the duplication check (unique daily reference). Error code: B14 The first 8 or 11 characters of <Msgld> must match the BIC of the Instructing Agent in ICF. The rest of the field can be freely defined. Error code: B CreDtTm ++GrpHdr +++CreDtTm 1..1 NbOfTxs ++GrpHdr +++NbOfTxs Pattern Creation Date Time ISODateTime [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Number Of Transactions Max15NumericText Pattern [0-9]{1,15} Bulk creation date and time. Total number of single transactions in the bulk. Must not exceed 100,000 (maximum parameter of data records in the bulk). Error code: B02 Total number of data records must be equal to the actual number of individual data records in the bulk. Error code: B03 pacs sct; SCL SCT; 2017 page 1 of 54

108 pacs sct Contents and checks 1..1 TtlRtrdIntrBkSttlmAmt ++GrpHdr +++TtlRtrdIntrBkSttlmAmt Total Returned Interbank Settlement Amount SCLSCTCurrencyAndAmount_3 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Mandatory Usage Rule: Only 'EUR' is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Total number of single transactions in the bulk. Integer value up to 15 characters allowed. Maximum number of decimal places allowed remains two. (Schema validation) Currency designation is always EUR. (Schema validation) The total amount given must equal the sum of the single transactions in the bulk. Error code: B05 required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR Amount must be at least 0.01 but no more than (Schema validation) pacs sct; SCL SCT; 2017 page 2 of 54

109 pacs sct Contents and checks 1..1 IntrBkSttlmDt ++GrpHdr +++IntrBkSttlmDt Interbank Settlement Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Mandatory (AT-R4 Settlement Date for the Return) or (AT-R8 Settlement Date for the positive answer to a Recall) For submissions in the submission windows with the cut-off 8.00, 10.00, 11.00, and the current operating day of the must be given. For submissions in the submission window with the cut-off 20.00, the next operating day of the must be given. Error code: B SttlmInf ++GrpHdr +++SttlmInf 1..1 SttlmMtd 1..1 ClrSys ++GrpHdr +++SttlmInf ++++SttlmMtd ++GrpHdr +++SttlmInf ++++ClrSys Settlement Information SCLSCTSettlementInformation13 SettlementMethod SCLSCTSettlementMethod1Code Acceptable Codes CLRG Clearing System SCLSCTClearingSystemIdentification3Choic e Usage Rule: Only CLRG, INGA and IND are allowed. <IntrBkSttlmDt> is part of the duplication check at file level (unique daily reference) and single record level. Information on the settlement mechanism. Only the code CLRG is allowed. (Schema validation) pacs sct; SCL SCT; 2017 page 3 of 54

110 pacs sct Contents and checks 1..1 Prtry ++GrpHdr +++SttlmInf ++++ClrSys +++++Prtry 0..1 InstgAgt ++GrpHdr +++InstgAgt 1..1 FinInstnId ++GrpHdr +++InstgAgt ++++FinInstnId 1..1 BIC ++GrpHdr +++InstgAgt ++++FinInstnId +++++BIC Pattern Proprietary SCLSCTId7_2 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Acceptable Codes SCL Instructing Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Pattern Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Usage Rule: Only BIC is allowed. Code for the clearing system. For the, only the value SCL is admissible. (Schema validation). Only to be used for submissions to the (ICF). Allocation of the BIC of the SCL participant which is linked with the TARGET2 sub-account assigned for settlement with the. Part of duplication check (unique daily reference) BIC must be contained in the ICF and be eligible for submitting payments of this type (check based on the SCL-Directory). Error code: B10 pacs sct; SCL SCT; 2017 page 4 of 54

111 pacs sct Contents and checks 0..1 InstdAgt ++GrpHdr +++InstdAgt 1..1 FinInstnId ++GrpHdr +++InstdAgt ++++FinInstnId 1..1 BIC ++GrpHdr +++InstdAgt ++++FinInstnId +++++BIC Pattern Instructed Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Usage Rule: Only BIC is allowed. BIC code may only be contained in the Settled Credit File (SCF). Allocation of the BIC of the SCL participant which is linked with the TARGET2 sub-account assigned for settlement with the. Only to be used for deliveries from the. Error code: B11 pacs sct; SCL SCT; 2017 page 5 of 54

112 pacs sct Contents and checks 1..n TxInf 1..1 RtrId +++RtrId 1..1 OrgnlGrpInf +++OrgnlGrpInf 1..1 OrgnlMsgId +++OrgnlGrpInf ++++OrgnlMsgId 1..1 OrgnlMsgNmId +++OrgnlGrpInf ++++OrgnlMsgNmId Pattern Pattern Pattern Transaction Information SCLSCTPaymentTransactionInformation27 Return Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original Group Information SCLSCTOriginalGroupInformation3 Original Message Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original Message SCLSCTOrgnlMsgNmId pacs\.008[a-za-z0-9\.]{0,27} PACS\.008[A-Za-z0-9\.]{0,27} Mandatory Mandatory (AT-R5 Specific Reference of the Bank Initiating the Return) Usage Rule: Element Original Group Information must be present in either Original Group Information or in Transaction Information. maximum data records in the bulk Reference number of the transaction given by the bank initiating the return. Return Id is part of the duplication check at the single record level. Error code: AM05 Data which refer to the original bulk. of the original bulk. Usage rule: "pacs.008" or "PACS.008" to be entered, in each case with additional characters where applicable. Schema validation. The Original Instruction Id of the underlying bulk. Only given here if already specified in the original credit transfer. pacs sct; SCL SCT; 2017 page 6 of 54

113 pacs sct Contents and checks 0..1 OrgnlInstrId +++OrgnlInstrId 1..1 OrgnlEndToEndId +++OrgnlEndToEndId 1..1 OrgnlTxId +++OrgnlTxId 1..1 OrgnlIntrBkSttlmAmt +++OrgnlIntrBkSttlmAmt Pattern Original Instruction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original End To End Identification Pattern Original Transaction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original Interbank Settlement Amount SCLSCTCurrencyAndAmount_2 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Usage Rule: Mandatory if provided in the original instruction. Mandatory (AT-41 Originator's reference of the credit transfer transaction) Mandatory (AT-43 Originator Bank's reference of the credit transfer transaction) Usage Rule: Must contain a reference that is meaningful to the Originator's Bank and is unique over time. Mandatory (AT-04 Amount of the credit transfer in euro) Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. The Original Instruction Id of the underlying bulk. Only given here if already specified in the original credit transfer. The reference of the payer (end-to-end Id) of the original credit transfer. Reference of the originating payment service provider. Transaction Id (TxId) of the original pacs.008 message. Original amount of the original credit transfer. Only EUR is permitted as the currency designation. (Schema validation) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation) required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR Amount must be at least 0.01 but no more than (Schema validation) pacs sct; SCL SCT; 2017 page 7 of 54

114 pacs sct Contents and checks 1..1 RtrdIntrBkSttlmAmt +++RtrdIntrBkSttlmAmt Returned Interbank Settlement Amount SCLSCTCurrencyAndAmount_2 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 0..1 RtrdInstdAmt Returned Instructed Amount SCLSCTCurrencyAndAmount_2 FractionDigits 2 TotalDigits 18 Inclusive RtrdInstdAmt Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} (AT-04 Amount of the credit transfer in euro) or (AT-46 Amount of a positive answer to the Recall in euro) Usage Rule: If the return message is a positive answer to a Recall (ie, if Code under Return Reason Information specifies FOCR ), the amount must be equal to the Original Interbank Settlement Amount less the Amount under Charges Information. Usage Rule: If the return message is not a positive answer to a Recall (ie, if Code under Return Reason Information is different from FOCR ), the Amount must be the same as in Original Interbank Settlement Amount. Usage Rule: Only EUR is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Usage Rule: Only allowed in the case of a return in response to a cancellation request, ie, Reason in Return Reason Information specifies FOCR. Usage Rule: Only EUR is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Return amount of the credit transfer. Where the return constitutes a positive response to a recall ("FOCR"), the following applies: <OrgnlIntrBkSttlmAmt>./. <ChrgsInf/Amt> = <RtrdIntrBkSttlmAmt>. Error code: AM02 Where the return does not constitute a positive response to a recall, the following applies: <OrgnlIntrBkSttlmAmt> = <RtrdIntrBkSttlmAmt>. Error code: AM02 The curency designation "EUR" is permissible. (Schema validation) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation) Amount must be at least 0.01 but no more than (Schema validation) If use is made of the "Charges Information" element block, the element "Returned Instructed Amount" must be completed too due to an ISO stipulation. In any other cases the element block Is optional. Error code: XT13 If used although "FOCR" not present in <RtrRsnInf><Rsn><Cd>: Error code: XT13 pacs sct; SCL SCT; 2017 page 8 of 54

115 pacs sct Contents and checks required Attribute: Ccy SCLSCTCurrencyCode Use required 0..1 ChrgBr +++ChrgBr 0..1 ChrgsInf +++ChrgsInf Acceptable Codes EUR Charge Bearer SCLSCTChargeBearere1Code Acceptable Codes SLEV Charges Information SCLSCTChargesInformation5 Usage Rule: Only 'SLEV' is allowed. Usage Rule: Only allowed in case of a return in response to a cancellation request, ie, "Reason" in "Return Reason Information" specifies "FOCR". Usage Rule: Only one occurence is allowed. The curency designation "EUR" is permissible. (Schema validation) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation) Amount must be at least 0.01 but no more than (Schema validation) Only the entry "SLEV" is allowed (Schema validation). The element block "Charges Information" may only be used in the event of a positive response to a Payment Cancellation Request ("Rsn" contains the entry "FOCR") An ISO stipulation requires that in such cases the element "Returned Instructed Amount" has to be completed as well. Error code: XT13 pacs sct; SCL SCT; 2017 page 9 of 54

116 pacs sct Contents and checks 1..1 Amt +++ChrgsInf ++++Amt Amount SCLSCTCurrencyAndAmount_2 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 Pty Party SCLSCTBranchAndFinancialInstitutionIdentifi cation4 +++ChrgsInf ++++Pty 1..1 FinInstnId Financial Institution Identification +++ChrgsInf ++++Pty +++++FinInstnId 1..1 BIC +++ChrgsInf ++++Pty +++++FinInstnId BIC Pattern SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} (AT-47 Fee for the positive answer to the Recall in euro) Usage Rule: Only "EUR" is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. (AT-23 BIC of the Creditor Bank). Usage Rule: Only BIC is allowed The curency designation "EUR" is permissible. (Schema validation) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation) Amount must be at least 0.01 but no more than (Schema validation) pacs sct; SCL SCT; 2017 page 10 of 54

117 pacs sct Contents and checks 0..1 InstgAgt +++InstgAgt 1..1 FinInstnId +++InstgAgt ++++FinInstnId 1..1 BIC +++InstgAgt ++++FinInstnId +++++BIC 1..1 RtrRsnInf +++RtrRsnInf 1..1 Orgtr +++RtrRsnInf ++++Orgtr Pattern Instructing Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Return Reason Information SCLSCTReturnReasonInformation9 Originator SCLSCTId5 Usage Rule: Only BIC is allowed. Mandatory Usage Rule: Only one occurrence of 'Return Reason Information' is allowed. Mandatory (AT-R2 Identification of the type of party initiating the R- message) Usage Rule: Limited to BIC for an Agent or for a non-financial institution. Usage Rule: is limited to 70 characters in length. Original instructing agent of the bulk. May only be entered in the SCF of the, may not be included in the ICF (submitted by the SCL participant). Error code: XT13 Data of the party which initiated the message pacs.004. Only the BIC or the name (only for non-financial institutions) may be given. (Schema validation) pacs sct; SCL SCT; 2017 page 11 of 54

118 pacs sct Contents and checks 1..1 Nm 1..1 Id +++RtrRsnInf ++++Orgtr +++++Nm +++RtrRsnInf ++++Orgtr +++++Id 1..1 OrgId +++RtrRsnInf ++++Orgtr +++++Id OrgId 1..1 BICOrBEI +++RtrRsnInf ++++Orgtr +++++Id OrgId BICOrBEI Max70Text Length Pattern Identification SCLSCTParty3Choice Organisation Identification SCLSCTOrganisationIdentification3 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} of the party which initiated the return. BIC of the party which initiated the return. pacs sct; SCL SCT; 2017 page 12 of 54

119 pacs sct Contents and checks 1..1 Rsn +++RtrRsnInf ++++Rsn 1..1 Cd 0..1 AddtlInf +++RtrRsnInf ++++Rsn +++++Cd +++RtrRsnInf ++++AddtlInf Reason ReturnReason5Choice Code ExternalReturnReason1Code Acceptable Codes AC01 AC04 AC06 AG01 AG02 AM05 BE04 FOCR MD07 MS02 MS03 RC01 RR01 RR02 RR03 RR04 Additional Information Max105Text Length Mandatory (AT-R3 Reason Code for Non-Acceptance of the credit transfer) Usage Rule: If the message is used for a positive answer to a Recall, only FOCR is allowed. See Message Element Specifications below. (AT-R7 Specific Reference of the bank initiating the recall) Usage Rule: Only allowed when FOCR is present in Reason. In this case, it is mandatory and only one occurrence is allowed. Return reason. If the message Is used to transfer back an amount that was requested using message type camt , it is only admissible to enter "FOCR" (no technical validation occurs). All acceptable return codes in accordance with the EPC Implementation Guidelines. (Schema validation) Use of <AddtlInf> only allowed if "FOCR" is given as the reason for return. If completed, although "Rsn" is not equivalent to "FOCR": Error code: XT33 pacs sct; SCL SCT; 2017 page 13 of 54

120 pacs sct Contents and checks 1..1 OrgnlTxRef 1..1 IntrBkSttlmDt ++++IntrBkSttlmDt 1..1 SttlmInf ++++SttlmInf Original Transaction Reference SCLSCTOriginalTransactionReference13 Interbank Settlement Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Settlement Information SCLSCTSettlementInformation131 Mandatory (An exact copy of all attributes of the received DS-02 which is being returned) Usage Rule: The message elements under 'Original Transaction Reference' must be populated with the same value as the message elements of the original instruction as defined within the following elements. (AT-42 Settlement Date of the credit transfer) Copy of the returned original message pacs sct; SCL SCT; 2017 page 14 of 54

121 pacs sct Contents and checks 1..1 SttlmMtd 1..1 PmtTpInf ++++SttlmInf +++++SttlmMtd ++++PmtTpInf 1..1 SvcLvl ++++PmtTpInf +++++SvcLvl 1..1 Cd ++++PmtTpInf +++++SvcLvl Cd Settlement Method SCLSCTSettlementMethod1Code Acceptable Codes CLRG Payment e Information SCLSCTPaymenteInformation22 Acceptable Codes SEPA ServiceLevel SCLSCTServiceLevel8Choice Code SCLSCTExternalServiceLevel1Code (AT-40 Identification code of the Scheme) (AT-45 Category Purpose of the Credit Transfer) Information about the settlement mechanism. Only the code "CLRG" is allowed (Schema validation). SEPA constant (Schema validation) pacs sct; SCL SCT; 2017 page 15 of 54

122 pacs sct Contents and checks 0..1 LclInstrm ++++PmtTpInf +++++LclInstrm 1..1 Cd ++++PmtTpInf +++++LclInstrm Cd 1..1 Prtry ++++PmtTpInf +++++LclInstrm Prtry 0..1 CtgyPurp ++++PmtTpInf +++++CtgyPurp Local Instrument SCLSCTLocalInstrument2Choice Code ExternalLocalInstrument1Code Pattern Proprietary SCLSCTId8 ([A-Za-z0-9] [+ \? / \- : \( \) \., ' \s]){1,35} Category Purpose CategoryPurpose1Choice (AT-45 Category purpose of the Credit Transfer) Allocation according to the returned original message Allocation according to the returned original message Encrypted remittance information. pacs sct; SCL SCT; 2017 page 16 of 54

123 pacs sct Contents and checks 1..1 Cd ++++PmtTpInf +++++CtgyPurp Cd 1..1 Prtry ++++PmtTpInf +++++CtgyPurp Prtry 0..1 RmtInf ++++RmtInf 1..1 Ustrd ++++RmtInf +++++Ustrd Code ExternalCategoryPurpose1Code Length Proprietary Remittance Information SCLSCTRemittanceInformation5 Unstructured Max140Text Length (AT-05 Remittance Information) Usage Rule: 'Unstructured' may carry structured remittance information, as agreed between the Originator and the Beneficiary. Usage Rule: Only one occurrence of 'Unstructured' is allowed. Allocation according to the returned original message Allocation according to the returned original message Structured or unstructured remittance information. (Schema validation) Unstructured remittance information. Allocation according to the returned original message pacs sct; SCL SCT; 2017 page 17 of 54

124 pacs sct Contents and checks 1..1 Strd ++++RmtInf +++++Strd 0..1 CdtrRefInf ++++RmtInf +++++Strd CdtrRefInf 1..1 Tp ++++RmtInf +++++Strd CdtrRefInf Tp 1..1 CdOrPrtry ++++RmtInf +++++Strd CdtrRefInf Tp CdOrPrtry Structured SCLSCTStructuredRemittanceInformation7 Creditor Reference Information SCLSCTCreditorReferenceInformation2 e SCLSCTCreditorReferencee2 Code or Proprietary SCLSCTCreditorReferencee1Choice Format Rule: 'Structured' can be used, provided the tags and data do not exceed 140 characters in length. Usage Rule: Only one occurrence of 'Structured' is allowed. Structured remittance information Allocation according to the returned original message pacs sct; SCL SCT; 2017 page 18 of 54

125 pacs sct Contents and checks 1..1 Cd 0..1 Issr ++++RmtInf +++++Strd CdtrRefInf Tp CdOrPrtry Cd ++++RmtInf +++++Strd CdtrRefInf Tp Issr 1..1 Ref ++++RmtInf +++++Strd CdtrRefInf Ref Code SCLSCTe3Code Acceptable Codes SCOR Issuer Reference Only the code "SCOR" is allowed. (Schema validation). Allocation according to the returned original message Allocation according to the returned original message pacs sct; SCL SCT; 2017 page 19 of 54

126 pacs sct Contents and checks 0..1 UltmtDbtr ++++UltmtDbtr 0..1 Nm 0..1 Id ++++UltmtDbtr +++++Nm ++++UltmtDbtr +++++Id 1..1 OrgId ++++UltmtDbtr +++++Id OrgId Ultimate Debtor SCLSCTPartyIdentification321 Max70Text Length Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 (AT-08 of the Originator Reference Party) (AT-09 Identification code of the Originator Reference Party) of the ultimate payer. pacs sct; SCL SCT; 2017 page 20 of 54

127 pacs sct Contents and checks 1..1 BICOrBEI ++++UltmtDbtr +++++Id OrgId BICOrBEI 1..1 Othr 1..1 Id ++++UltmtDbtr +++++Id OrgId Othr ++++UltmtDbtr +++++Id OrgId Othr ++ Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 pacs sct; SCL SCT; 2017 page 21 of 54

128 pacs sct Contents and checks 0..1 SchmeNm ++++UltmtDbtr +++++Id OrgId Othr SchmeNm 1..1 Cd ++++UltmtDbtr +++++Id OrgId Othr SchmeNm Cd 1..1 Prtry ++++UltmtDbtr +++++Id OrgId Othr SchmeNm Prtry Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary pacs sct; SCL SCT; 2017 page 22 of 54

129 pacs sct Contents and checks 0..1 Issr ++++UltmtDbtr +++++Id OrgId Othr Issr 1..1 PrvtId ++++UltmtDbtr +++++Id PrvtId 1..1 DtAndPlcOfBirth ++++UltmtDbtr +++++Id PrvtId DtAndPlcOfBirth Issuer Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth pacs sct; SCL SCT; 2017 page 23 of 54

130 pacs sct Contents and checks 1..1 BirthDt ++++UltmtDbtr +++++Id PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++++UltmtDbtr +++++Id PrvtId DtAndPlcOfBirth PrvcOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth pacs sct; SCL SCT; 2017 page 24 of 54

131 pacs sct Contents and checks 1..1 CityOfBirth ++++UltmtDbtr +++++Id PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++++UltmtDbtr +++++Id PrvtId DtAndPlcOfBirth CtryOfBirth 1..1 Othr ++++UltmtDbtr +++++Id PrvtId Othr City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 pacs sct; SCL SCT; 2017 page 25 of 54

132 pacs sct Contents and checks 1..1 Id ++++UltmtDbtr +++++Id PrvtId Othr SchmeNm ++++UltmtDbtr +++++Id PrvtId Othr SchmeNm 1..1 Cd ++++UltmtDbtr +++++Id PrvtId Othr SchmeNm Cd Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length pacs sct; SCL SCT; 2017 page 26 of 54

133 pacs sct Contents and checks 1..1 Prtry ++++UltmtDbtr +++++Id PrvtId Othr SchmeNm Prtry 0..1 Issr ++++UltmtDbtr +++++Id PrvtId Othr Issr 1..1 Dbtr ++++Dbtr Proprietary Issuer Debtor SCLSCTPartyIdentification322 (AT-02 of the Originator) (AT-03 Address of the Originator) (AT-10 Originator identification code) pacs sct; SCL SCT; 2017 page 27 of 54

134 pacs sct Contents and checks 1..1 Nm ++++Dbtr +++++Nm 0..1 PstlAdr ++++Dbtr +++++PstlAdr 0..1 Ctry ++++Dbtr +++++PstlAdr Ctry 0..2 AdrLine ++++Dbtr +++++PstlAdr AdrLine Max70Text Length Postal Address SCLSCTPostalAddress6 Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Mandatory (AT-02 of the Originator) (AT-03 Address of the Originator) of the payer. Address of the payer. pacs sct; SCL SCT; 2017 page 28 of 54

135 pacs sct Contents and checks 0..1 Id ++++Dbtr +++++Id 1..1 OrgId ++++Dbtr +++++Id OrgId 1..1 BICOrBEI ++++Dbtr +++++Id OrgId BICOrBEI 1..1 Othr ++++Dbtr +++++Id OrgId Othr Pattern Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 (AT-10 Originator's Identification Code) Format Rule: Either 'Organisation Identification' or one occurrence of 'Private Identification' may be present. Identification code of the payer. (Originator Identification Code). May not be given simultaneously with the <Id><PrvtId> (see below). (Schema validation) All ISO options are allowed. pacs sct; SCL SCT; 2017 page 29 of 54

136 pacs sct Contents and checks 1..1 Id ++++Dbtr +++++Id OrgId Othr SchmeNm ++++Dbtr +++++Id OrgId Othr SchmeNm 1..1 Cd ++++Dbtr +++++Id OrgId Othr SchmeNm Cd Identification Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length pacs sct; SCL SCT; 2017 page 30 of 54

137 pacs sct Contents and checks 1..1 Prtry ++++Dbtr +++++Id OrgId Othr SchmeNm Prtry 0..1 Issr ++++Dbtr +++++Id OrgId Othr Issr 1..1 PrvtId ++++Dbtr +++++Id PrvtId Proprietary Issuer Private Identification SCLSCTPersonIdentification51 pacs sct; SCL SCT; 2017 page 31 of 54

138 pacs sct Contents and checks 1..1 DtAndPlcOfBirth ++++Dbtr +++++Id PrvtId DtAndPlcOfBirth 1..1 BirthDt ++++Dbtr +++++Id PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++++Dbtr +++++Id PrvtId DtAndPlcOfBirth PrvcOfBirth Date and Place of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth pacs sct; SCL SCT; 2017 page 32 of 54

139 pacs sct Contents and checks 1..1 CityOfBirth ++++Dbtr +++++Id PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++++Dbtr +++++Id PrvtId DtAndPlcOfBirth CtryOfBirth 1..1 Othr ++++Dbtr +++++Id PrvtId Othr City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 pacs sct; SCL SCT; 2017 page 33 of 54

140 pacs sct Contents and checks 1..1 Id ++++Dbtr +++++Id PrvtId Othr SchmeNm ++++Dbtr +++++Id PrvtId Othr SchmeNm Identification Scheme PersonIdentificationScheme1Choice pacs sct; SCL SCT; 2017 page 34 of 54

141 pacs sct Contents and checks 1..1 Cd ++++Dbtr +++++Id PrvtId Othr SchmeNm Cd 1..1 Prtry ++++Dbtr +++++Id PrvtId Othr SchmeNm Prtry 0..1 Issr ++++Dbtr +++++Id PrvtId Othr Issr Code ExternalPersonIdentification1Code Length Proprietary Issuer pacs sct; SCL SCT; 2017 page 35 of 54

142 pacs sct Contents and checks 1..1 DbtrAcct 1..1 Id ++++DbtrAcct ++++DbtrAcct +++++Id 1..1 IBAN ++++DbtrAcct +++++Id IBAN 1..1 DbtrAgt ++++DbtrAgt Pattern Debtor Account SCLSCTCashAccount161 Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Debtor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 (AT-01 IBAN of the Originator) (AT-06 BIC code of the Originator Bank) IBAN of the payer. BIC of the remitting payment service provider according to the original message. pacs sct; SCL SCT; 2017 page 36 of 54

143 pacs sct Contents and checks 1..1 FinInstnId ++++DbtrAgt +++++FinInstnId 1..1 BIC ++++DbtrAgt +++++FinInstnId BIC 1..1 CdtrAgt ++++CdtrAgt 1..1 FinInstnId ++++CdtrAgt +++++FinInstnId Pattern Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creditor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 (AT-23 BIC code of the Beneficiary Bank) Validity of the BIC according to the SCL-Directory. Error code: XT27 Check only if credit transfer is forwarded from the to STEP2: BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service. Error code: PY01 BIC of the creditor s payment service provider according to the original message. pacs sct; SCL SCT; 2017 page 37 of 54

144 pacs sct Contents and checks 1..1 BIC ++++CdtrAgt +++++FinInstnId BIC 1..1 Cdtr ++++Cdtr 1..1 Nm ++++Cdtr +++++Nm 0..1 PstlAdr ++++Cdtr +++++PstlAdr Pattern Max70Text Length BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creditor SCLSCTPartyIdentification322 Postal Address SCLSCTPostalAddress6 (AT-21 of the Beneficiary) (AT-22 Address of the Beneficiary (AT-24 Beneficiary identification code) Mandatory (AT-21 of the Beneficiary) (AT-22 Address of the Beneficiary) Validity of the BIC according to the SCL-Directory. Error code: XT27 Credit agent BIC is part of the duplication check at the single record level. Error code: AM05 of the creditor. Address of the creditor. pacs sct; SCL SCT; 2017 page 38 of 54

145 pacs sct Contents and checks 0..1 Ctry ++++Cdtr +++++PstlAdr Ctry 0..2 AdrLine 0..1 Id ++++Cdtr +++++PstlAdr AdrLine ++++Cdtr +++++Id 1..1 OrgId ++++Cdtr +++++Id OrgId Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 Format Rule: Only two occurrences of 'Address Line' are allowed. (AT-24 Beneficiary Identification Code) Format Rule: Either 'Organisation Identification' or one occurrence of 'Private Identification' may be present. Identification code of the creditor. May not be given simultaneously with <Id><PrvID> (see below). (Schema validation) All ISO options are allowed. pacs sct; SCL SCT; 2017 page 39 of 54

146 pacs sct Contents and checks 1..1 BICOrBEI ++++Cdtr +++++Id OrgId BICOrBEI 1..1 Othr 1..1 Id ++++Cdtr +++++Id OrgId Othr ++++Cdtr +++++Id OrgId Othr ++ Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 pacs sct; SCL SCT; 2017 page 40 of 54

147 pacs sct Contents and checks 0..1 SchmeNm ++++Cdtr +++++Id OrgId Othr SchmeNm 1..1 Cd ++++Cdtr +++++Id OrgId Othr SchmeNm Cd 1..1 Prtry ++++Cdtr +++++Id OrgId Othr SchmeNm Prtry Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary pacs sct; SCL SCT; 2017 page 41 of 54

148 pacs sct Contents and checks 0..1 Issr ++++Cdtr +++++Id OrgId Othr Issr 1..1 PrvtId ++++Cdtr +++++Id PrvtId 1..1 DtAndPlcOfBirth ++++Cdtr +++++Id PrvtId DtAndPlcOfBirth Issuer Private Identification SCLSCTPersonIdentification51 Date and Place of Birth DateAndPlaceOfBirth pacs sct; SCL SCT; 2017 page 42 of 54

149 pacs sct Contents and checks 1..1 BirthDt ++++Cdtr +++++Id PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++++Cdtr +++++Id PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth ++++Cdtr +++++Id PrvtId DtAndPlcOfBirth CityOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth City of Birth pacs sct; SCL SCT; 2017 page 43 of 54

150 pacs sct Contents and checks 1..1 CtryOfBirth ++++Cdtr +++++Id PrvtId DtAndPlcOfBirth CtryOfBirth 1..1 Othr 1..1 Id ++++Cdtr +++++Id PrvtId Othr ++++Cdtr +++++Id PrvtId Othr ++ Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification pacs sct; SCL SCT; 2017 page 44 of 54

151 pacs sct Contents and checks 0..1 SchmeNm ++++Cdtr +++++Id PrvtId Othr SchmeNm 1..1 Cd ++++Cdtr +++++Id PrvtId Othr SchmeNm Cd 1..1 Prtry ++++Cdtr +++++Id PrvtId Othr SchmeNm Prtry Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary pacs sct; SCL SCT; 2017 page 45 of 54

152 pacs sct Contents and checks 0..1 Issr ++++Cdtr +++++Id PrvtId Othr Issr 1..1 CdtrAcct 1..1 Id ++++CdtrAcct ++++CdtrAcct +++++Id 1..1 IBAN ++++CdtrAcct +++++Id IBAN Issuer Creditor Account SCLSCTCashAccount161 Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier Pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} (AT-20 IBAN of the Beneficiary) IBAN of the creditor pacs sct; SCL SCT; 2017 page 46 of 54

153 pacs sct Contents and checks 0..1 UltmtCdtr ++++UltmtCdtr 0..1 Nm 0..1 Id ++++UltmtCdtr +++++Nm ++++UltmtCdtr +++++Id 1..1 OrgId ++++UltmtCdtr +++++Id OrgId Ultimate Creditor SCLSCTPartyIdentification321 Max70Text Length Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 (AT-28 of the Beneficiary Reference Party) (AT-29 Identification code of the Beneficiary Reference Party) of the ultimate creditor. pacs sct; SCL SCT; 2017 page 47 of 54

154 pacs sct Contents and checks 1..1 BICOrBEI ++++UltmtCdtr +++++Id OrgId BICOrBEI 1..1 Othr 1..1 Id ++++UltmtCdtr +++++Id OrgId Othr ++++UltmtCdtr +++++Id OrgId Othr ++ Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 pacs sct; SCL SCT; 2017 page 48 of 54

155 pacs sct Contents and checks 0..1 SchmeNm ++++UltmtCdtr +++++Id OrgId Othr SchmeNm 1..1 Cd ++++UltmtCdtr +++++Id OrgId Othr SchmeNm Cd Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length pacs sct; SCL SCT; 2017 page 49 of 54

156 pacs sct Contents and checks 1..1 Prtry ++++UltmtCdtr +++++Id OrgId Othr SchmeNm Prtry 0..1 Issr ++++UltmtCdtr +++++Id OrgId Othr Issr 1..1 PrvtId ++++UltmtCdtr +++++Id PrvtId Proprietary Issuer Private Identification SCLSCTPersonIdentification51 pacs sct; SCL SCT; 2017 page 50 of 54

157 pacs sct Contents and checks 1..1 DtAndPlcOfBirth ++++UltmtCdtr +++++Id PrvtId DtAndPlcOfBirth 1..1 BirthDt ++++UltmtCdtr +++++Id PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth ++++UltmtCdtr +++++Id PrvtId DtAndPlcOfBirth PrvcOfBirth Date and Place of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province of Birth pacs sct; SCL SCT; 2017 page 51 of 54

158 pacs sct Contents and checks 1..1 CityOfBirth ++++UltmtCdtr +++++Id PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth ++++UltmtCdtr +++++Id PrvtId DtAndPlcOfBirth CtryOfBirth 1..1 Othr ++++UltmtCdtr +++++Id PrvtId Othr City of Birth Country of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 pacs sct; SCL SCT; 2017 page 52 of 54

159 pacs sct Contents and checks 1..1 Id ++++UltmtCdtr +++++Id PrvtId Othr SchmeNm ++++UltmtCdtr +++++Id PrvtId Othr SchmeNm 1..1 Cd ++++UltmtCdtr +++++Id PrvtId Othr SchmeNm Cd Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length pacs sct; SCL SCT; 2017 page 53 of 54

160 pacs sct Contents and checks 1..1 Prtry ++++UltmtCdtr +++++Id PrvtId Othr SchmeNm Prtry 0..1 Issr ++++UltmtCdtr +++++Id PrvtId Othr Issr Proprietary Issuer pacs sct; SCL SCT; 2017 page 54 of 54

161 SCT Interbank Recall of Credit Transfer Dataset (DS-05) camt sct Memo SEPA Credit Transfer Interbank Recall of Credit Transfer Dataset (DS-05) SCT annex 8 of appendix SCT/SCL technical specifications - camt page 1 of 2

162 SCT Interbank Recall of Credit Transfer Dataset (DS-05) camt sct Use of Interbank Recall of Credit Transfer Dataset (camt ) This message is used in the SCT service to recall individual credit transfers from the recipient following settlement. It is not possible to recall an entire bulk payment. Pursuant to the rulebook, the recall can be effected up to 10 business days after settlement. This deadline is not validated in the. The recall itself is not relevant for settlement and serves solely to inform the beneficiary who then has ten further business days to actively respond to the camt in one of two ways: The beneficiary transfers the amount where applicable minus the processing fee of the <Creditor Agent> (<Charges Information>) and specifying the <Reason Code> FOCR (Following Cancellation Request) to the originator of the cancellation request by means of a bookkeeping-relevant return (pacs ) or The beneficiary instructs the <Creditor Agent> to send a return message or negative message (Resolution of Investigation, camt ), stating why the requested return transfer will not take place using a <Reason Code>. This message is not relevant for settlement. The carries out a duplication check but does not cross reference checking. For example, no check is made as to whether the original payment was processed on the given date in the or whether a recall has already been submitted. Furthermore, it is not checked whether a recall has already been answered The message is a component of the Input Credit File (ICF) on the submitter side and a component of the Settled Credit File (SCF) on the delivery side. ISO message structure A Interbank Recall of Credit Transfer Dataset contains: a single assignment (in pacs messages: Group Header) a Control Data an Underlying containing one or more transaction information sequences, each of which contains the transaction data of the individual underlying transfer (pacs ). Group header The assignment contains information required to process the entire message. SCT annex 8 of appendix SCT/SCL technical specifications - camt page 2 of 2

163 camt sct Message structure Content and checks 1..1 FIToFIPmtCxlReq 1..1 Assgnmt ++Assgnmt 1..1 Id 1..1 Assgnr 1..1 Agt ++Assgnmt +++Id ++Assgnmt +++Assgnr ++Assgnmt +++Assgnr ++++Agt Pattern Payment Cancellation Request SCLSCTFIToFIPaymentCancellationRequest V01 Assignment SCLSCTCaseAssignment2 Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Assigner SCLSCTParty7Choice Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Instructing Party Usage Rule: Limited to BIC to identify a bank or CSM or to indicate the CSM when it has no BIC. Usage Rule: is limited to 70 characters in length. The assignment contains information which is relevant for the entire message. Identification of the bulk. Part of duplication check (unique daily reference). Error code: B14 The first 8 or 11 characters of Id must match the BIC of the Assigner in ICF. The rest of the field can be freely defined. Error code: B98 camt sct; SCL SCT; 2017 page 1 of 51

164 camt sct Content and checks 1..1 FinInstnId ++Assgnmt +++Assgnr ++++Agt +++++FinInstnId 1..1 BIC ++Assgnmt +++Assgnr ++++Agt +++++FinInstnId BIC 1..1 Assgne 1..1 Agt ++Assgnmt +++Assgne ++Assgnmt +++Assgne ++++Agt Pattern Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Assignee SCLSCTParty7Choice Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Instructed Party Usage Rule: Limited to BIC to identify a bank or CSM or to indicate the CSM when it has no BIC. Usage Rule: is limited to 70 characters in length. ICF: To be completed with the BIC of the submitter. BIC has been authorised to make submissions (Check against the SCL-Directory). Error code: B12 SCF: For deliveries from the SCL "MARKDEFF". camt sct; SCL SCT; 2017 page 2 of 51

165 camt sct Content and checks 1..1 FinInstnId ++Assgnmt +++Assgne ++++Agt +++++FinInstnId 1..1 BIC ++Assgnmt +++Assgne ++++Agt +++++FinInstnId BIC 1..1 CreDtTm ++Assgnmt +++CreDtTm 1..1 CtrlData ++CtrlData 1..1 NbOfTxs ++CtrlData +++NbOfTxs Pattern Pattern Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creation Date Time ISODateTime [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Control Data ControlData1 NumberOfTransactions Max15NumericText Pattern [0-9]{1,15} ICF: To be completed with MARKDEFF for submission to the SCL. Error code: B12 SCF: To be completed with the BIC of the of the creditor for delivery from the SCL. Total number of single transactions in the bulk. Must not exceed 100,000 (maximum parameter of data records in the file). Error code: B02 Total number of data records must be equal to the actual number of individual data records in the file. Error code: B03 camt sct; SCL SCT; 2017 page 3 of 51

166 camt sct Content and checks 1..1 Undrlyg 1..n TxInf CxlId CxlId 1..1 OrgnlGrpInf OrgnlGrpInf 1..1 OrgnlMsgId OrgnlGrpInf +++++OrgnlMsgId Pattern Pattern Underlying SCLSCTUnderlyingTransaction2 TransactionInformation SCLSCTPaymentTransactionInformation31 CancellationIdentification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} OriginalGroupInformation SCLSCTOriginalGroupInformation3 Original Message Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Mandatory Mandatory (AT-R7 Specific reference of the bank initiating the Recall) Usage Rule: This element must be transported up to the Creditor Agent. Mandatory Data of the underlying original transaction(s) being cancelled Reference of the payment service provider requesting the cancellation. Cancellation Id is part of the duplication check at single record level. Error code: AM05 Message Id (<MsgId>) of original bulk. camt sct; SCL SCT; 2017 page 4 of 51

167 camt sct Content and checks 1..1 OrgnlMsgNmId OrgnlGrpInf +++++OrgnlMsgNmId 0..1 OrgnlInstrId OrgnlInstrId 1..1 OrgnlEndToEndId OrgnlEndToEndId 1..1 OrgnlTxId OrgnlTxId 1..1 OrgnlIntrBkSttlmAmt OrgnlIntrBkSttlmAmt Pattern Pattern Original Message Identification SCLSCTOrgnlMsgNmId pacs\.008[a-za-z0-9\.]{0,27} PACS\.008[A-Za-z0-9\.]{0,27} Original Instruction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original End To End Identification Pattern Original Transaction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original Interbank Settlement Amount SCLSCTCurrencyAndAmount FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} Usage Rule: Only pacs is allowed. Mandatory (AT-41 Originator s reference of the credit transfer transaction) Mandatory (AT-43 Originator Bank s reference of the credit transfer transaction) Mandatory (AT-04 Amount of the Credit Transfer in Euro) Usage Rule: Only 'EUR' is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Message Id of original payment. To be completed with pacs.008 or PACS.008, where necessary further characters in accordance with schema validation permitted Instruction Id of original payment Only given if already specified in the original credit transfer. End to End Id of original payment Originator Bank s reference.transaction Id (<TxId>) of original payment Original payment amount. Only EUR is permitted as the currency designation. (Schema validation)) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation). Amount must be at least 0.01 but no more than (Schema validation) camt sct; SCL SCT; 2017 page 5 of 51

168 camt sct Content and checks required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 OrgnlIntrBkSttlmDt Original Interbank Settlement Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} OrgnlIntrBkSttlmDt Mandatory (AT-42 Settlement Date of the Credit Transfer) Interbank settlement date of original payment must match date of the original transaction. If not, a transaction forwarded via other CSMs might be rejected using error code: XT74 A recall is permitted on the same day and after settlement. The ISD must indicate the current business day or a past date.error code: DT01 The current SCL <IntrBkSttlmDt> is assumed for the duplication check. Compliance with the permitted cancellation deadline of 10 business days following settlement of the original payment is not checked on either the submission or delivery sides in the SCL. Failure to meet the deadline of another CSM may result in a rejection Error code: XT86 camt sct; SCL SCT; 2017 page 6 of 51

169 camt sct Content and checks 0..1 Assgnr Assgnr 1..1 FinInstnId Assgnr +++++FinInstnId 1..1 BIC Assgnr +++++FinInstnId BIC 1..1 CxlRsnInf CxlRsnInf 1..1 Orgtr CxlRsnInf +++++Orgtr Pattern Assigner SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Cancellation Reason Information SCLSCTCancellationReasonInformation3 Originator SCLSCTId5 Mandatory Usage Rule: Only one occurrence is allowed. Mandatory (AT-R2 Identification of the type of party initiating the R- message) Usage Rule: Limited to BIC for an Agent or for a non-financial institution. Usage Rule: is limited to 70 characters in length. ICF: cannot be completed for submission. SCF: is completed upon delivery from the SCL. Original submitter of the bulk in which the recall was contained upon its submission to the. ICF cannot be completed for submission. Error code: XT13 SCF: to be completed, for delivery from the SCL Information regarding the reason for cancellation Institution requesting the recall. Either BIC or name (only for non financial institutions) (Schema validation) camt sct; SCL SCT; 2017 page 7 of 51

170 camt sct Content and checks 1..1 Nm CxlRsnInf +++++Orgtr Nm 1..1 Id CxlRsnInf +++++Orgtr 1..1 OrgId CxlRsnInf +++++Orgtr OrgId Max70Text Length Identification SCLSCTParty6Choice2 Organisation Identification SCLSCTOrganisationIdentification4 of the institution requesting the recall BIC of the institution requesting the recall. camt sct; SCL SCT; 2017 page 8 of 51

171 camt sct Content and checks 1..1 BICOrBEI CxlRsnInf +++++Orgtr OrgId BICOrBEI 1..1 Rsn CxlRsnInf +++++Rsn 1..1 Cd 1..1 Prtry CxlRsnInf +++++Rsn Cd CxlRsnInf +++++Rsn Prtry Pattern Acceptable Codes DUPL Proprietary BIC Or BEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Reason CancellationReason2Choice Code CancellationReason4Code Mandatory (AT-48 Recall reason code) See Message Element Specifications below See Message Element Specifications below Reason for the recall. ISO reason code for the recall (schema validation.) Reasons TECH and FRAD can be entered here (no ISO codes). No technical or schema validation. camt sct; SCL SCT; 2017 page 9 of 51

172 camt sct Content and checks 0..1 AddtlInf CxlRsnInf +++++AddtlInf 1..1 OrgnlTxRef 1..1 SttlmInf SttlmInf 1..1 SttlmMtd SttlmInf SttlmMtd Additional Information Max105Text Length Acceptable Codes CLRG Original Transaction Reference extension (SCLSCTOriginalTransactionReference13) Settlement Information SCLSCTSettlementInformation13 Settlement Method SCLSCTSettlementMethod1Code (AT-49 Additional Information to AT-48 The Recall reason code) Usage Rule: Only allowed when FRAD is used as a Recall reason code. Usage Rule: Only one occurrence is allowed Mandatory (an exact copy of all attributes of the initially sent DS-02 which is to be cancelled) Usage Rule: The message elements under Original Transaction Reference must be populated with the same value as the message elements of the original instruction as defined within the following elements. Additional information on the reason for the recall (AT-49) Only allowed, if CxlRsnInf><Rsn><Prtry> is "FRAD". Error code: XT13 Only CLRG is allowed (Schema validation) camt sct; SCL SCT; 2017 page 10 of 51

173 camt sct Content and checks 1..1 ClrSys SttlmInf ClrSys 1..1 Prtry 1..1 PmtTpInf SttlmInf ClrSys Prtry PmtTpInf 1..1 SvcLvl PmtTpInf SvcLvl Clearing System SCLSCTClearingSystemIdentification2Choic e Proprietary SCLSCT_SCL Acceptable Codes SCL Payment e Information SCLSCTPaymenteInformation22 Service Level SCLSCTServiceLevel8Choice (AT-40 Identification code of the Scheme) (AT-45 Category Purpose of the Credit Transfer) Identification of the clearing system. Only SCL is allowed (Schema validation). Payment type information camt sct; SCL SCT; 2017 page 11 of 51

174 camt sct Content and checks 1..1 Cd 0..1 LclInstrm PmtTpInf SvcLvl Cd PmtTpInf LclInstrm 1..1 Cd PmtTpInf LclInstrm Cd Code SCLSCTExternalServiceLevel1Code Acceptable Codes SEPA Local Instrument SCLSCTLocalInstrument2Choice Code ExternalLocalInstrument1Code Only SEPA is allowed (Schema validation). Entry according to original payment camt sct; SCL SCT; 2017 page 12 of 51

175 camt sct Content and checks 1..1 Prtry PmtTpInf LclInstrm Prtry 0..1 CtgyPurp PmtTpInf CtgyPurp 1..1 Cd PmtTpInf CtgyPurp Cd 1..1 Prtry PmtTpInf CtgyPurp Prtry Pattern Proprietary SCLSCTId8 ([A-Za-z0-9] [+ \? / \- : \( \) \., ' \s]){1,35} Category Purpose CategoryPurpose1Choice Code ExternalCategoryPurpose1Code Length Proprietary Entry according to original payment Encrypted remittance information Entry according to original payment Entry according to original payment camt sct; SCL SCT; 2017 page 13 of 51

176 camt sct Content and checks 0..1 RmtInf RmtInf 1..1 Ustrd RmtInf Ustrd 1..1 Strd RmtInf Strd 0..1 CdtrRefInf RmtInf Strd CdtrRefInf Remittance Information SCLSCTRemittanceInformation5 Unstructured Max140Text Length Structured SCLSCTStructuredRemittanceInformation7 Creditor Reference Information CreditorReferenceInformation2 (AT-05 Remittance Information) Unstructured or structured purpose of payment. Unstructured purpose of payment. Entry according to original payment Structured purpose of payment. Entry according to original payment Creditor reference information camt sct; SCL SCT; 2017 page 14 of 51

177 camt sct Content and checks 1..1 Tp RmtInf Strd CdtrRefInf Tp 1..1 CdOrPrtry RmtInf Strd CdtrRefInf Tp CdOrPrtry 1..1 Cd RmtInf Strd CdtrRefInf Tp CdOrPrtry Cd Acceptable Codes SCOR e CreditorReferencee2 Code Or Proprietary CreditorReferencee1Choice Code SCLSCTe3Code Code for the creditor reference. Only SCOR is allowed (Schema validation) camt sct; SCL SCT; 2017 page 15 of 51

178 camt sct Content and checks 0..1 Issr RmtInf Strd CdtrRefInf Tp Issr 1..1 Ref RmtInf Strd CdtrRefInf Ref 0..1 UltmtDbtr UltmtDbtr Issuer Reference Ultimate Debtor SCLSCTPartyIdentification33 (AT-08 of the Originator Reference Party) (AT-09 Identification Code of the Originator Reference Party) Entry according to original payment Entry according to original payment Ultimate debtor. All sub-elements from the original payment are supported. camt sct; SCL SCT; 2017 page 16 of 51

179 camt sct Content and checks 0..1 Nm UltmtDbtr Nm 0..1 Id UltmtDbtr 1..1 OrgId UltmtDbtr OrgId Max70Text Length Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 of the ultimate debtor. Identification of the ultimate debtor. camt sct; SCL SCT; 2017 page 17 of 51

180 camt sct Content and checks 0..1 BICOrBEI UltmtDbtr OrgId BICOrBEI 0..1 Othr UltmtDbtr OrgId Othr 1..1 Id UltmtDbtr OrgId Othr +++ Pattern Identification BIC Or BEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 camt sct; SCL SCT; 2017 page 18 of 51

181 camt sct Content and checks 0..1 SchmeNm UltmtDbtr OrgId Othr SchmeNm 1..1 Cd UltmtDbtr OrgId Othr SchmeNm Cd 1..1 Prtry UltmtDbtr OrgId Othr SchmeNm Prtry Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary camt sct; SCL SCT; 2017 page 19 of 51

182 camt sct Content and checks 0..1 Issr UltmtDbtr OrgId Othr Issr 1..1 PrvtId UltmtDbtr PrvtId 0..1 DtAndPlcOfBirth UltmtDbtr PrvtId DtAndPlcOfBirth Issuer Private Identification SCLSCTPersonIdentification5 Date And Place Of Birth DateAndPlaceOfBirth camt sct; SCL SCT; 2017 page 20 of 51

183 camt sct Content and checks 1..1 BirthDt UltmtDbtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth UltmtDbtr PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth UltmtDbtr PrvtId DtAndPlcOfBirth CityOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province Of Birth City Of Birth camt sct; SCL SCT; 2017 page 21 of 51

184 camt sct Content and checks 1..1 CtryOfBirth UltmtDbtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr UltmtDbtr PrvtId Othr 1..1 Id UltmtDbtr PrvtId Othr +++ Country Of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification camt sct; SCL SCT; 2017 page 22 of 51

185 camt sct Content and checks 0..1 SchmeNm UltmtDbtr PrvtId Othr SchmeNm 1..1 Cd UltmtDbtr PrvtId Othr SchmeNm Cd 1..1 Prtry UltmtDbtr PrvtId Othr SchmeNm Prtry Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary camt sct; SCL SCT; 2017 page 23 of 51

186 camt sct Content and checks 0..1 Issr UltmtDbtr PrvtId Othr Issr 1..1 Dbtr Dbtr 1..1 Nm Dbtr Nm 0..1 PstlAdr Dbtr PstlAdr Issuer Debtor SCLSCTPartyIdentification32 Max70Text Length Postal Address SCLSCTPostalAddress6 (AT-02 of the Originator - Mandatory) (AT-03 Address of the Originator) (AT-10 Originator s Identification Code) Debtor. All sub-elements from the original payment are supported of payer Postal address of payer camt sct; SCL SCT; 2017 page 24 of 51

187 camt sct Content and checks 0..1 Ctry Dbtr PstlAdr Ctry 0..2 AdrLine Dbtr PstlAdr AdrLine 0..1 Id Dbtr Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Identification SCLSCTParty6Choice camt sct; SCL SCT; 2017 page 25 of 51

188 camt sct Content and checks 1..1 OrgId Dbtr OrgId 0..1 BICOrBEI Dbtr OrgId BICOrBEI 0..1 Othr Dbtr OrgId Othr Pattern Organisation Identification SCLSCTOrganisationIdentification41 BIC Or BEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 camt sct; SCL SCT; 2017 page 26 of 51

189 camt sct Content and checks 1..1 Id Dbtr OrgId Othr SchmeNm Dbtr OrgId Othr SchmeNm 1..1 Cd Dbtr OrgId Othr SchmeNm Cd Identification Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length camt sct; SCL SCT; 2017 page 27 of 51

190 camt sct Content and checks 1..1 Prtry Dbtr OrgId Othr SchmeNm Prtry 0..1 Issr Dbtr OrgId Othr Issr 1..1 PrvtId Dbtr PrvtId Proprietary Issuer Private Identification SCLSCTPersonIdentification5 camt sct; SCL SCT; 2017 page 28 of 51

191 camt sct Content and checks 0..1 DtAndPlcOfBirth Dbtr PrvtId DtAndPlcOfBirth 1..1 BirthDt Dbtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth Dbtr PrvtId DtAndPlcOfBirth PrvcOfBirth Date And Place Of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province Of Birth camt sct; SCL SCT; 2017 page 29 of 51

192 camt sct Content and checks 1..1 CityOfBirth Dbtr PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth Dbtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr Dbtr PrvtId Othr City Of Birth Country Of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 camt sct; SCL SCT; 2017 page 30 of 51

193 camt sct Content and checks 1..1 Id Dbtr PrvtId Othr SchmeNm Dbtr PrvtId Othr SchmeNm 1..1 Cd Dbtr PrvtId Othr SchmeNm Cd Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length camt sct; SCL SCT; 2017 page 31 of 51

194 camt sct Content and checks 1..1 Prtry Dbtr PrvtId Othr SchmeNm Prtry 0..1 Issr Dbtr PrvtId Othr Issr 1..1 DbtrAcct DbtrAcct Proprietary Issuer Debtor Account SCLSCTCashAccount16 (AT-01 Account number of the Originator) Account of payer camt sct; SCL SCT; 2017 page 32 of 51

195 camt sct Content and checks 1..1 Id DbtrAcct 1..1 IBAN DbtrAcct IBAN 1..1 DbtrAgt DbtrAgt 1..1 FinInstnId DbtrAgt FinInstnId Pattern Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Debtor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 (AT-06 BIC of the Originator Bank) IBAN of payer Payment service provider of the payer camt sct; SCL SCT; 2017 page 33 of 51

196 camt sct Content and checks 1..1 BIC DbtrAgt FinInstnId BIC Pattern BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} BIC according to original payment. Validity of BIC using SCLdirectory. Error code: XT27. General addressability check: BIC must be addressable within the or via another CSM: Error code: PY01 Check only if credit transfer is forwarded from the to STEP2. BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service of the STEP2 SCT Service. Error code: PY CdtrAgt CdtrAgt 1..1 FinInstnId CdtrAgt FinInstnId Creditor Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 (AT-23 BIC of the Beneficiary Bank) The original debtor agent BIC is part of the duplication check at the single record level. Error code: AM05 Payment service provider of the creditor camt sct; SCL SCT; 2017 page 34 of 51

197 camt sct Content and checks 1..1 BIC CdtrAgt FinInstnId BIC 1..1 Cdtr Cdtr 1..1 Nm Cdtr Nm Pattern Max70Text Length BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creditor SCLSCTPartyIdentification32 (AT-21 of the Beneficiary Mandatory) (AT-22 Address of the Beneficiary) (AT-24 Beneficiary Identification Code) BIC according to original payment. Validity of BIC using SCL-Directory. Error code: XT27 Check only if credit transfer is forwarded from the to STEP2. BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service. Error code: PY01 Creditor. All sub-elements from the original payment are supported. of creditor camt sct; SCL SCT; 2017 page 35 of 51

198 camt sct Content and checks 0..1 PstlAdr Cdtr PstlAdr 0..1 Ctry Cdtr PstlAdr Ctry 0..2 AdrLine Cdtr PstlAdr AdrLine 0..1 Id Cdtr Postal Address SCLSCTPostalAddress6 Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Identification SCLSCTParty6Choice Address of creditor camt sct; SCL SCT; 2017 page 36 of 51

199 camt sct Content and checks 1..1 OrgId Cdtr OrgId 0..1 BICOrBEI Cdtr OrgId BICOrBEI 0..1 Othr Cdtr OrgId Othr Pattern OrganisationIdentification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 camt sct; SCL SCT; 2017 page 37 of 51

200 camt sct Content and checks 1..1 Id Cdtr OrgId Othr SchmeNm Cdtr OrgId Othr SchmeNm 1..1 Cd Cdtr OrgId Othr SchmeNm Cd Identification Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length camt sct; SCL SCT; 2017 page 38 of 51

201 camt sct Content and checks 1..1 Prtry Cdtr OrgId Othr SchmeNm Prtry 0..1 Issr Cdtr OrgId Othr Issr 1..1 PrvtId Cdtr PrvtId Proprietary Issuer PrivateIdentification SCLSCTPersonIdentification5 camt sct; SCL SCT; 2017 page 39 of 51

202 camt sct Content and checks 0..1 DtAndPlcOfBirth Cdtr PrvtId DtAndPlcOfBirth 1..1 BirthDt Cdtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth Cdtr PrvtId DtAndPlcOfBirth PrvcOfBirth DateAndPlaceOfBirth DateAndPlaceOfBirth BirthDate ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} ProvinceOfBirth camt sct; SCL SCT; 2017 page 40 of 51

203 camt sct Content and checks 1..1 CityOfBirth Cdtr PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth Cdtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr Cdtr PrvtId Othr CityOfBirth CountryOfBirth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 camt sct; SCL SCT; 2017 page 41 of 51

204 camt sct Content and checks 1..1 Id Cdtr PrvtId Othr SchmeNm Cdtr PrvtId Othr SchmeNm 1..1 Cd Cdtr PrvtId Othr SchmeNm Cd Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length camt sct; SCL SCT; 2017 page 42 of 51

205 camt sct Content and checks 1..1 Prtry Cdtr PrvtId Othr SchmeNm Prtry 0..1 Issr Cdtr PrvtId Othr Issr 1..1 CdtrAcct CdtrAcct Proprietary Issuer Creditor Account SCLSCTCashAccount16 (AT-20 Account of the Beneficiary) Account of the creditor camt sct; SCL SCT; 2017 page 43 of 51

206 camt sct Content and checks 1..1 Id CdtrAcct 1..1 IBAN CdtrAcct IBAN 0..1 UltmtCdtr UltmtCdtr 0..1 Nm UltmtCdtr Nm Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier Pattern [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Ultimate Creditor SCLSCTPartyIdentification33 Max70Text Length (AT-28 of the Beneficiary Reference Party) (AT-29 Identification Code of the Beneficiary Reference Party) IBAN of the creditor Ultimate creditor All sub-elements from the original payment are supported. of the ultimate creditor. camt sct; SCL SCT; 2017 page 44 of 51

207 camt sct Content and checks 0..1 Id UltmtCdtr 1..1 OrgId UltmtCdtr OrgId 0..1 BICOrBEI UltmtCdtr OrgId BICOrBEI Pattern Identification SCLSCTParty6Choice Organisation Identification SCLSCTOrganisationIdentification41 BIC Or BEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} camt sct; SCL SCT; 2017 page 45 of 51

208 camt sct Content and checks 0..1 Othr UltmtCdtr OrgId Othr 1..1 Id UltmtCdtr OrgId Othr SchmeNm UltmtCdtr OrgId Othr SchmeNm Identification Other GenericOrganisationIdentification1 Scheme OrganisationIdentificationScheme1Cho ice camt sct; SCL SCT; 2017 page 46 of 51

209 camt sct Content and checks 1..1 Cd UltmtCdtr OrgId Othr SchmeNm Cd 1..1 Prtry UltmtCdtr OrgId Othr SchmeNm Prtry 0..1 Issr UltmtCdtr OrgId Othr Issr Code ExternalOrganisationIdentification1Code Length Proprietary Issuer camt sct; SCL SCT; 2017 page 47 of 51

210 camt sct Content and checks 1..1 PrvtId UltmtCdtr PrvtId 0..1 DtAndPlcOfBirth UltmtCdtr PrvtId DtAndPlcOfBirth 1..1 BirthDt UltmtCdtr PrvtId DtAndPlcOfBirth BirthDt Private Identification SCLSCTPersonIdentification5 Date And Place Of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} camt sct; SCL SCT; 2017 page 48 of 51

211 camt sct Content and checks 0..1 PrvcOfBirth UltmtCdtr PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth UltmtCdtr PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth UltmtCdtr PrvtId DtAndPlcOfBirth CtryOfBirth Province Of Birth City Of Birth Country Of Birth CountryCode Pattern [A-Z]{2,2} camt sct; SCL SCT; 2017 page 49 of 51

212 camt sct Content and checks 0..1 Othr UltmtCdtr PrvtId Othr 1..1 Id UltmtCdtr PrvtId Othr SchmeNm UltmtCdtr PrvtId Othr SchmeNm Other GenericPersonIdentification1 Identification Scheme PersonIdentificationScheme1Choice camt sct; SCL SCT; 2017 page 50 of 51

213 camt sct Content and checks 1..1 Cd UltmtCdtr PrvtId Othr SchmeNm Cd 1..1 Prtry UltmtCdtr PrvtId Othr SchmeNm Prtry 0..1 Issr UltmtCdtr PrvtId Othr Issr Code ExternalPersonIdentification1Code Length Proprietary Issuer camt sct; SCL SCT; 2017 page 51 of 51

214 SCT Interbank Negative Answer to a Recall of a Credit Transfer Dataset (DS-06) camt Memo SEPA Credit Transfer Interbank Negative Answer to a Recall of a Credit Transfer Dataset (DS-06) SCT annex 9 of appendix SCT/SCL technical specifications - camt page 1 of 2

215 SCT Interbank Negative Answer to a Recall of a Credit Transfer Dataset (DS-06) camt Use of the Interbank Negative Answer to a Recall of a Credit Transfer Dataset (camt ) This message is used in the SCT service of the in order for the creditor to actively respond to the interbank Recall of Credit Transfer Dataset (camt ) after the funds have been credited. Pursuant to the rulebook, this response can take the form of a return or "negative" response within ten business days of receipt of the recall. This deadline is not validated in the or other CSM. If the creditor does not wish to return the recalled payment using a Return (pacs ), he has the option of communicating the reason for this to the party initiating the recall using message camt , stating a <Reason Code> (ISO code or proprietary code). The message camt is not bookkeeping-relevant and merely represents a negative information to the party requesting the recall. The carries out a duplication check but does not carry out a cross reference checking. This means, for example, that no check is made as to whether a negative response refers to a previously submitted recall or whether any reaction in the form of a negative response or return transfer has been made at all. The message is a component of the Input Credit File (ICF) on the submitter side and a component of the settled credit file (SCF) on the delivery side. ISO message structure A Interbank Negative Answer to a Recall of a Credit Transfer Dataset contains: a single Assignment (group header in pacs messages) a Status Cancellation Details containing one or more transaction information and status sequences, each of which contains the transaction details of the individual underlying transfer (pacs ) as well as a <Reason Code> for the non-acceptance of the recall. Group header The assignment contains information required to process the entire message. SCT annex 9 of appendix SCT/SCL technical specifications - camt page 2 of 2

216 camt Message structure Content and checks 1..1 RsltnOfInvstgtn 1..1 Assgnmt 1..1 Id 1..1 Assgnr 1..1 Agt ++Assgnmt ++Assgnmt +++Id ++Assgnmt +++Assgnr ++Assgnmt +++Assgnr ++++Agt Pattern Resolution Of Investigation SCLSCTResolutionOfInvestigationV03 Assignment CaseAssignment2 Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Assigner SCLSCTParty7Choice Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Instructing Party Usage Rule: Limited to BIC to identify a bank or CSM or to indicate the CSM when it has no BIC. Usage Rule: is limited to 70 characters in length. The assignment contains information which is relevant for the entire message. Reference Number of the bulk. Part of duplication check (unique daily reference). Error code: B14 The first 8 or 11 characters of Id must match the BIC of the Assigner in ICF. The rest of the field can be freely defined. Error code: B9 camt ; SCL SCT; 2017 page 1 of 51

217 camt Content and checks 1..1 FinInstnId ++Assgnmt +++Assgnr ++++Agt +++++FinInstnId 1..1 BIC ++Assgnmt +++Assgnr ++++Agt +++++FinInstnId BIC 1..1 Assgne 1..1 Agt ++Assgnmt +++Assgne ++Assgnmt +++Assgne ++++Agt Pattern FinancialInstitutionIdentification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Assignee SCLSCTParty7Choice Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Instructed Party Usage Rule: Limited to BIC to identify a bank or CSM or to indicate the CSM when it has no BIC. Usage Rule: is limited to 70 characters in length. ICF: To be completed with the BIC of the submitter. BIC has been authorised to make submissions (Check against the SCL-Directory). Error code: B12 SCF: For deliveries from the SCL "MARKDEFF".SCL.. camt ; SCL SCT; 2017 page 2 of 51

218 camt Content and checks 1..1 FinInstnId ++Assgnmt +++Assgne ++++Agt +++++FinInstnId 1..1 BIC ++Assgnmt +++Assgne ++++Agt +++++FinInstnId BIC 1..1 CreDtTm ++Assgnmt +++CreDtTm 1..1 Sts ++Sts 1..1 Conf ++Sts +++Conf Pattern Pattern Acceptable Codes RJCR FinancialInstitutionIdentification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Creation Date Time ISODateTime [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2}[T][0-9]{2,2}: [0-9]{2,2}:[0-9]{2,2}[\S]* Status SCLSCTInvestigationStatus2Choice Usage Rule: Only Confirmation is allowed Confirmation Usage Rule: Only RJCR is allowed. SCLSCTInvestigationExecutionConfirmation3 Code ICF: To be completed with MARKDEFF for submissions to the SCL. Error code: B12 SCF: To be completed with the BIC of the creditor for delivery from the SCL. Status of the negative response (= rejection of cancellation request) Only RJCR is allowed (Schema validation) camt ; SCL SCT; 2017 page 3 of 51

219 camt Content and checks 1..1 CxlDtls 1..n TxInfAndSts +AndSts 1..1 CxlStsId +AndSts ++++CxlStsId 1..1 OrgnlGrpInf +AndSts ++++OrgnlGrpInf 1..1 OrgnlMsgId +AndSts ++++OrgnlGrpInf +++++OrgnlMsgId Pattern Pattern Cancellation Details SCLSCTUnderlyingTransaction3 TransactionInformationAndStatus SCLSCTPaymentTransactionInformation33 Cancellation Status Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} OriginalGroupInformation OriginalGroupInformation3 Original Message Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Mandatory Mandatory Mandatory Mandatory Remark: This element and its sub-elements refer to the original pacs message Detailed information regarding the negative response to the recall. Total number of single transactions in the bulk must not exceed 100,000 (maximum parameter of data records in the file). Error code: B02 Reference of the credit institution refusing the cancellation. Cancellation Status Id is part of the duplication check at single record level. Error code: AM05 The data of this element as well as its sub-elements refer to the information in the recall to be responded to (camt.056), which in turn refers to the original payment (pacs.008). Message Id (<MsgId>) of the original bulk containing the underlying transfer. camt ; SCL SCT; 2017 page 4 of 51

220 camt Content and checks 1..1 OrgnlMsgNmId +AndSts ++++OrgnlGrpInf +++++OrgnlMsgNmId 0..1 OrgnlInstrId +AndSts ++++OrgnlInstrId 1..1 OrgnlEndToEndId +AndSts ++++OrgnlEndToEndId 1..1 OrgnlTxId +AndSts ++++OrgnlTxId 1..1 TxCxlSts +AndSts ++++TxCxlSts Pattern Pattern Original Message Identification SCLSCTOrgnlMsgNmId pacs\.008[a-za-z0-9\.]{0,27} PACS\.008[A-Za-z0-9\.]{0,27} OriginalInstructionIdentification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Original End To End Identification Pattern Acceptable Codes RJCR Original Transaction Identification SCLSCTId7 ([A-Za-z0-9] [+ \? / \- : \( \) \., ']){1,35} Transaction Cancellation Status SCLSCTCancellationIndividualStatus1Code Usage Rule: Only pacs is allowed. Mandatory (AT-41 Originator s reference of the credit transfer transaction) Mandatory (AT-43 Originator Bank s reference of the credit transfer transaction) Usage Rule: Only RJCR is allowed Message type of the original bulk. May be completed with pacs.008 or PACS.008, where necessary with additional further characters in accordance with schema validation. The Original Instruction Id of the bulk containing the underlying transfer. Only given if it already existed in the original transfer. Original End to End Id of original payment Reference of the Debtor Bank. Transaction Id of original payment Only RJCR is allowed (Schema validation) camt ; SCL SCT; 2017 page 5 of 51

221 camt Content and checks 1..1 CxlStsRsnInf +AndSts ++++CxlStsRsnInf 1..1 Orgtr +AndSts ++++CxlStsRsnInf +++++Orgtr 1..1 Nm 1..1 Id +AndSts ++++CxlStsRsnInf +++++Orgtr Nm +AndSts ++++CxlStsRsnInf +++++Orgtr Max70Text Length Cancellation Status Reason Information Mandatory SCLSCTCancellationStatusReasonInformatio n1 Originator SCLSCTPartyIdentification321 Identification SCLSCTParty6Choice Mandatory (AT-R2 Identification of the type of party initiating the R- message) Usage Rule: Limited to BIC for an Agent or for a non-financial institution. Usage Rule: is limited to 70 characters in length. Reason for negative response Institution issuing the negative response. of the institution issuing the negative response ID of the institution issuing the negative response camt ; SCL SCT; 2017 page 6 of 51

222 camt Content and checks 1..1 OrgId +AndSts ++++CxlStsRsnInf +++++Orgtr OrgId 1..1 BICOrBEI +AndSts ++++CxlStsRsnInf +++++Orgtr OrgId BICOrBEI 1..1 Rsn +AndSts ++++CxlStsRsnInf +++++Rsn 1..1 Cd +AndSts ++++CxlStsRsnInf +++++Rsn Cd Pattern OrganisationIdentification SCLSCTOrganisationIdentification4 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Reason CancellationStatusReason1Choice Code PaymentCancellationRejection1Code Mandatory (AT-R6 Reason Code for non-acceptance of the Recall) See Message Element Specifications. Reason for negative response ISO codes for the rejection reason (Schema validation) camt ; SCL SCT; 2017 page 7 of 51

223 camt Content and checks 1..1 Prtry +AndSts ++++CxlStsRsnInf +++++Rsn Prtry 0..2 AddtlInf +AndSts ++++CxlStsRsnInf +++++AddtlInf 0..1 Assgnr +AndSts ++++Assgnr 1..1 Agt +AndSts ++++Assgnr +++++Agt Acceptable Codes CUST LEGL Proprietary Additional Information Max105Text Length Assigner SCLSCTParty7Choice Agent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 See Message Element Specifications below Usage Rule: To be used only when code is LEGL in order to precise the reason. Usage Rule: Only two occurrences are allowed Permitted codes: AC04, AM04, NOAS, NOOR. Until further notice the code ARDT may also be used to show that the payment has already been returned (= not a valid ISO code at present). No technical or schema validation. To be completed only when the reason code contains LEGL. Error code: XT13 camt ; SCL SCT; 2017 page 8 of 51

224 camt Content and checks 1..1 FinInstnId +AndSts ++++Assgnr +++++Agt FinInstnId 1..1 BIC +AndSts ++++Assgnr +++++Agt FinInstnId BIC 1..1 OrgnlTxRef +AndSts Pattern Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Original Transaction Reference SCLSCTOriginalTransactionReference13 Mandatory (an exact copy of all attributes of the initially sent DS-02 which is to be cancelled) Usage Rule: The yellow shaded message elements under Original Transaction Reference must be populated with the same value as the message elements of the original instruction as defined within the following elements. Original submitter of the bulk in which the negative answer was contained upon its submission to the. ICF: must not be completed for submission. Error code: XT13 SCF: for delivery from SCL camt ; SCL SCT; 2017 page 9 of 51

225 camt Content and checks 1..1 IntrBkSttlmAmt +AndSts +++++IntrBkSttlmAmt Interbank Settlement Amount SCLSCTCurrencyAndAmount_3 FractionDigits 2 TotalDigits 18 Inclusive Pattern [0-9]{0,15}([\.]([0-9]{0,2})){0,1} (AT-04 Amount of the Credit Transfer in Euro) Original amount of the original credit transfer. Only EUR is permitted as the currency designation. (Schema validation) A maximum of two decimal places is permitted in accordance with the convention for the euro. (Schema validation) required Attribute: Ccy SCLSCTCurrencyCode Use required Acceptable Codes EUR 1..1 IntrBkSttlmDt InterbankSettlementDate ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} +AndSts +++++IntrBkSttlmDt 1..1 SttlmInf SettlementInformation SCLSCTSettlementInformation13 +AndSts +++++SttlmInf (AT-42 Settlement Date of the Credit Transfer) Amount must be at least 0.01 but no more than (Schema validation) Entry according to original payment. camt ; SCL SCT; 2017 page 10 of 51

226 camt Content and checks 1..1 SttlmMtd 1..1 ClrSys +AndSts +++++SttlmInf SttlmMtd +AndSts +++++SttlmInf ClrSys 1..1 Prtry 1..1 PmtTpInf +AndSts +++++SttlmInf ClrSys Prtry +AndSts +++++PmtTpInf SettlementMethod SCLSCTSettlementMethod1Code Acceptable Codes CLRG SCLSCTClearingSystemIdentification1Choic e SCLSCT_SCL Acceptable Codes SCL Payment e Information SCLSCTPaymenteInformation22 (AT-40 Identification code of the Scheme) (AT-45 Category Purpose of the Credit Transfer) Only CLRG is allowed ( Schema validation) Only SCL is allowed (Schema validation) Payment type information camt ; SCL SCT; 2017 page 11 of 51

227 camt Content and checks 1..1 SvcLvl +AndSts +++++PmtTpInf SvcLvl 1..1 Cd 0..1 LclInstrm +AndSts +++++PmtTpInf SvcLvl Cd +AndSts +++++PmtTpInf LclInstrm 1..1 Cd +AndSts +++++PmtTpInf LclInstrm Cd ServiceLevel SCLSCTServiceLevel8Choice Code SCLSCTExternalServiceLevel1Code Acceptable Codes SEPA LocalInstrument SCLSCTLocalInstrument2Choice Code ExternalLocalInstrument1Code Only SEPA is allowed (Schema validation) Entry according to original payment camt ; SCL SCT; 2017 page 12 of 51

228 camt Content and checks 1..1 Prtry +AndSts +++++PmtTpInf LclInstrm Prtry 0..1 CtgyPurp +AndSts +++++PmtTpInf CtgyPurp 1..1 Cd +AndSts +++++PmtTpInf CtgyPurp Cd 1..1 Prtry +AndSts +++++PmtTpInf CtgyPurp Prtry Pattern Proprietary SCLSCTId8 ([A-Za-z0-9] [+ \? / \- : \( \) \., ' \s]){1,35} Category Purpose CategoryPurpose1Choice Code ExternalCategoryPurpose1Code Length Proprietary Entry according to original payment Encrypted remittance information Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 13 of 51

229 camt Content and checks 0..1 RmtInf +AndSts +++++RmtInf 1..1 Ustrd +AndSts +++++RmtInf Ustrd 1..1 Strd +AndSts +++++RmtInf Strd 0..1 CdtrRefInf +AndSts +++++RmtInf Strd CdtrRefInf Remittance Information SCLSCTRemittanceInformation5 Unstructured Max140Text Length Structured SCLSCTStructuredRemittanceInformation7 Creditor Reference Information CreditorReferenceInformation2 (AT-05 Remittance Information) Unstructured or structured remittance information Unstructured remittance information Entry according to original payment. Structured remittance information Entry according to original payment. Creditor reference. camt ; SCL SCT; 2017 page 14 of 51

230 camt Content and checks 1..1 Tp +AndSts +++++RmtInf Strd CdtrRefInf Tp 1..1 CdOrPrtry +AndSts +++++RmtInf Strd CdtrRefInf Tp CdOrPrtry 1..1 Cd +AndSts +++++RmtInf Strd CdtrRefInf Tp CdOrPrtry Cd Acceptable Codes SCOR e CreditorReferencee2 CodeOrProprietary CreditorReferencee1Choice Code SCLSCTe3Code Code for the creditor reference. Only SCOR is allowed (Schema validation) camt ; SCL SCT; 2017 page 15 of 51

231 camt Content and checks 0..1 Issr +AndSts +++++RmtInf Strd CdtrRefInf Tp Issr 1..1 Ref +AndSts +++++RmtInf Strd CdtrRefInf Ref 0..1 UltmtDbtr +AndSts +++++UltmtDbtr Issuer Reference UltimateDebtor SCLSCTPartyIdentification322 (AT-08 of the Originator Reference Party) (AT-09 Identification Code of the Originator Reference Party) Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 16 of 51

232 camt Content and checks 0..1 Nm 0..1 Id +AndSts +++++UltmtDbtr Nm +AndSts +++++UltmtDbtr 1..1 OrgId +AndSts +++++UltmtDbtr OrgId Max70Text Length Identification SCLSCTParty6Choice2 OrganisationIdentification SCLSCTOrganisationIdentification41 of the ultimate payer Identification of the ultimate payer camt ; SCL SCT; 2017 page 17 of 51

233 camt Content and checks 0..1 BICOrBEI +AndSts +++++UltmtDbtr OrgId BICOrBEI 0..1 Othr 1..1 Id +AndSts +++++UltmtDbtr OrgId Othr +AndSts +++++UltmtDbtr OrgId Othr +++ Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 18 of 51

234 camt Content and checks 0..1 SchmeNm +AndSts +++++UltmtDbtr OrgId Othr SchmeNm 1..1 Cd +AndSts +++++UltmtDbtr OrgId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++UltmtDbtr OrgId Othr SchmeNm Prtry Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 19 of 51

235 camt Content and checks 0..1 Issr +AndSts +++++UltmtDbtr OrgId Othr Issr 1..1 PrvtId +AndSts +++++UltmtDbtr PrvtId 0..1 DtAndPlcOfBirth +AndSts +++++UltmtDbtr PrvtId DtAndPlcOfBirth Issuer PrivateIdentification SCLSCTPersonIdentification5 DateAndPlaceOfBirth DateAndPlaceOfBirth Entry according to original payment. camt ; SCL SCT; 2017 page 20 of 51

236 camt Content and checks 1..1 BirthDt +AndSts +++++UltmtDbtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth +AndSts +++++UltmtDbtr PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth +AndSts +++++UltmtDbtr PrvtId DtAndPlcOfBirth CityOfBirth BirthDate ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} ProvinceOfBirth CityOfBirth Entry according to original payment. Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 21 of 51

237 camt Content and checks 1..1 CtryOfBirth +AndSts +++++UltmtDbtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr 1..1 Id +AndSts +++++UltmtDbtr PrvtId Othr +AndSts +++++UltmtDbtr PrvtId Othr +++ CountryOfBirth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 22 of 51

238 camt Content and checks 0..1 SchmeNm +AndSts +++++UltmtDbtr PrvtId Othr SchmeNm 1..1 Cd +AndSts +++++UltmtDbtr PrvtId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++UltmtDbtr PrvtId Othr SchmeNm Prtry Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 23 of 51

239 camt Content and checks 0..1 Issr +AndSts +++++UltmtDbtr PrvtId Othr Issr 1..1 Dbtr +AndSts +++++Dbtr 1..1 Nm +AndSts +++++Dbtr Nm 0..1 PstlAdr +AndSts +++++Dbtr PstlAdr Issuer Debtor SCLSCTPartyIdentification32 Max70Text Length PostalAddress SCLSCTPostalAddress6 (AT-02 of the Originator - Mandatory) (AT-03 Address of the Originator) (AT-10 Originator s Identification Code) Entry according to original payment. of payer Postal address of payer camt ; SCL SCT; 2017 page 24 of 51

240 camt Content and checks 0..1 Ctry +AndSts +++++Dbtr PstlAdr Ctry 0..2 AdrLine 0..1 Id +AndSts +++++Dbtr PstlAdr AdrLine +AndSts +++++Dbtr Country CountryCode Pattern [A-Z]{2,2} Address Line Max70Text Length Identification SCLSCTParty6Choice2 Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 25 of 51

241 camt Content and checks 1..1 OrgId +AndSts +++++Dbtr OrgId 0..1 BICOrBEI +AndSts +++++Dbtr OrgId BICOrBEI 0..1 Othr +AndSts +++++Dbtr OrgId Othr Pattern OrganisationIdentification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 Entry according to original payment camt ; SCL SCT; 2017 page 26 of 51

242 camt Content and checks 1..1 Id +AndSts +++++Dbtr OrgId Othr SchmeNm +AndSts +++++Dbtr OrgId Othr SchmeNm 1..1 Cd +AndSts +++++Dbtr OrgId Othr SchmeNm Cd Identification Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 27 of 51

243 camt Content and checks 1..1 Prtry +AndSts +++++Dbtr OrgId Othr SchmeNm Prtry 0..1 Issr +AndSts +++++Dbtr OrgId Othr Issr 1..1 PrvtId +AndSts +++++Dbtr PrvtId Proprietary Issuer Private Identification SCLSCTPersonIdentification5 Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 28 of 51

244 camt Content and checks 0..1 DtAndPlcOfBirth +AndSts +++++Dbtr PrvtId DtAndPlcOfBirth 1..1 BirthDt +AndSts +++++Dbtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth +AndSts +++++Dbtr PrvtId DtAndPlcOfBirth PrvcOfBirth Date And Place Of Birth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province Of Birth camt ; SCL SCT; 2017 page 29 of 51

245 camt Content and checks 1..1 CityOfBirth +AndSts +++++Dbtr PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth +AndSts +++++Dbtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr +AndSts +++++Dbtr PrvtId Othr City Of Birth Country Of Birth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 camt ; SCL SCT; 2017 page 30 of 51

246 camt Content and checks 1..1 Id +AndSts +++++Dbtr PrvtId Othr SchmeNm +AndSts +++++Dbtr PrvtId Othr SchmeNm 1..1 Cd +AndSts +++++Dbtr PrvtId Othr SchmeNm Cd Identification Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length camt ; SCL SCT; 2017 page 31 of 51

247 camt Content and checks 1..1 Prtry +AndSts +++++Dbtr PrvtId Othr SchmeNm Prtry 0..1 Issr +AndSts +++++Dbtr PrvtId Othr Issr 1..1 DbtrAcct +AndSts +++++DbtrAcct Proprietary Issuer DebtorAccount SCLSCTCashAccount16 (AT-01 Account number of the Originator) Payer s account camt ; SCL SCT; 2017 page 32 of 51

248 camt Content and checks 1..1 Id +AndSts +++++DbtrAcct 1..1 IBAN +AndSts +++++DbtrAcct IBAN 1..1 DbtrAgt +AndSts +++++DbtrAgt 1..1 FinInstnId +AndSts +++++DbtrAgt FinInstnId Pattern Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} DebtorAgent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 Financial Institution Identification SCLSCTFinancialInstitutionIdentification7 (AT-06 BIC of the Originator Bank) IBAN oft he debtor Debtor Bank camt ; SCL SCT; 2017 page 33 of 51

249 camt Content and checks 1..1 BIC +AndSts +++++DbtrAgt FinInstnId BIC Pattern BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Entry according to original payment Validity of BIC using SCL-Directory. Error code: XT27 Check only if credit transfer is forwarded from the to STEP2. BIC must be a registered direct participant or reachable BIC of the STEP2 SCT Service of the STEP2 SCT Service. Error code: PY CdtrAgt +AndSts +++++CdtrAgt 1..1 FinInstnId +AndSts +++++CdtrAgt FinInstnId 1..1 BIC +AndSts +++++CdtrAgt FinInstnId BIC Pattern CreditorAgent SCLSCTBranchAndFinancialInstitutionIdentifi cation4 FinancialInstitutionIdentification SCLSCTFinancialInstitutionIdentification7 BIC BICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} (AT-23 BIC of the Beneficiary Bank) Payment service provider of the creditor Entry according to original payment. The original creditor agent BIC is part of the duplication check at single record level. Error Code: AM05 camt ; SCL SCT; 2017 page 34 of 51

250 camt Content and checks 1..1 Cdtr +AndSts +++++Cdtr 1..1 Nm +AndSts +++++Cdtr Nm 0..1 PstlAdr +AndSts +++++Cdtr PstlAdr 0..1 Ctry +AndSts +++++Cdtr PstlAdr Ctry Creditor SCLSCTPartyIdentification32 Max70Text Length PostalAddress SCLSCTPostalAddress6 Country CountryCode Pattern [A-Z]{2,2} (AT-21 of the Beneficiary Mandatory) (AT-22 Address of the Beneficiary) (AT-24 Beneficiary Identification Code) Creditor. All sub-elements from the original payment are supported. of creditor. Address of creditor Entry according to original payment camt ; SCL SCT; 2017 page 35 of 51

251 camt Content and checks 0..2 AdrLine 0..1 Id +AndSts +++++Cdtr PstlAdr AdrLine +AndSts +++++Cdtr 1..1 OrgId +AndSts +++++Cdtr OrgId 0..1 BICOrBEI +AndSts +++++Cdtr OrgId BICOrBEI AddressLine Max70Text Length Pattern Identification SCLSCTParty6Choice2 OrganisationIdentification SCLSCTOrganisationIdentification41 BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 36 of 51

252 camt Content and checks 0..1 Othr 1..1 Id +AndSts +++++Cdtr OrgId Othr +AndSts +++++Cdtr OrgId Othr SchmeNm +AndSts +++++Cdtr OrgId Othr SchmeNm Identification Other GenericOrganisationIdentification1 Scheme OrganisationIdentificationScheme1Cho ice Entry according to original payment camt ; SCL SCT; 2017 page 37 of 51

253 camt Content and checks 1..1 Cd +AndSts +++++Cdtr OrgId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++Cdtr OrgId Othr SchmeNm Prtry 0..1 Issr +AndSts +++++Cdtr OrgId Othr Issr Code ExternalOrganisationIdentification1Code Length Proprietary Issuer Entry according to original payment Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 38 of 51

254 camt Content and checks 1..1 PrvtId +AndSts +++++Cdtr PrvtId 0..1 DtAndPlcOfBirth +AndSts +++++Cdtr PrvtId DtAndPlcOfBirth 1..1 BirthDt +AndSts +++++Cdtr PrvtId DtAndPlcOfBirth BirthDt Private Identification SCLSCTPersonIdentification5 DateAndPlaceOfBirth DateAndPlaceOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Entry according to original payment camt ; SCL SCT; 2017 page 39 of 51

255 camt Content and checks 0..1 PrvcOfBirth +AndSts +++++Cdtr PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth +AndSts +++++Cdtr PrvtId DtAndPlcOfBirth CityOfBirth 1..1 CtryOfBirth +AndSts +++++Cdtr PrvtId DtAndPlcOfBirth CtryOfBirth Province Of Birth City Of Birth Country Of Birth CountryCode Pattern [A-Z]{2,2} Entry according to original payment Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 40 of 51

256 camt Content and checks 0..1 Othr 1..1 Id +AndSts +++++Cdtr PrvtId Othr +AndSts +++++Cdtr PrvtId Othr SchmeNm +AndSts +++++Cdtr PrvtId Othr SchmeNm Other GenericPersonIdentification1 Identification Scheme PersonIdentificationScheme1Choice Entry according to original payment camt ; SCL SCT; 2017 page 41 of 51

257 camt Content and checks 1..1 Cd +AndSts +++++Cdtr PrvtId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++Cdtr PrvtId Othr SchmeNm Prtry 0..1 Issr +AndSts +++++Cdtr PrvtId Othr Issr Code ExternalPersonIdentification1Code Length Proprietary Issuer Entry according to original payment Entry according to original payment Entry according to original payment camt ; SCL SCT; 2017 page 42 of 51

258 camt Content and checks 1..1 CdtrAcct 1..1 Id +AndSts +++++CdtrAcct +AndSts +++++CdtrAcct 1..1 IBAN +AndSts +++++CdtrAcct IBAN Pattern Creditor Account SCLSCTCashAccount16 Identification SCLSCTAccountIdentification4Choice IBAN IBAN2007Identifier [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} (AT-20 Account of the Beneficiary) Account of the creditor IBAN of the creditor camt ; SCL SCT; 2017 page 43 of 51

259 camt Content and checks 0..1 UltmtCdtr +AndSts +++++UltmtCdtr 0..1 Nm 0..1 Id +AndSts +++++UltmtCdtr Nm +AndSts +++++UltmtCdtr 1..1 OrgId +AndSts +++++UltmtCdtr OrgId UltimateCreditor SCLSCTPartyIdentification322 Max70Text Length Identification SCLSCTParty6Choice2 OrganisationIdentification SCLSCTOrganisationIdentification41 (AT-28 of the Beneficiary Reference Party) (AT-29 Identification Code of the Beneficiary Reference Party) Ultimate creditor All sub-elements from the original payment are supported. of the ultimate creditor. camt ; SCL SCT; 2017 page 44 of 51

260 camt Content and checks 0..1 BICOrBEI +AndSts +++++UltmtCdtr OrgId BICOrBEI 0..1 Othr 1..1 Id +AndSts +++++UltmtCdtr OrgId Othr +AndSts +++++UltmtCdtr OrgId Othr +++ Pattern Identification BICOrBEI AnyBICIdentifier [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}) {0,1} Other GenericOrganisationIdentification1 Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 45 of 51

261 camt Content and checks 0..1 SchmeNm +AndSts +++++UltmtCdtr OrgId Othr SchmeNm 1..1 Cd +AndSts +++++UltmtCdtr OrgId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++UltmtCdtr OrgId Othr SchmeNm Prtry Scheme OrganisationIdentificationScheme1Cho ice Code ExternalOrganisationIdentification1Code Length Proprietary Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 46 of 51

262 camt Content and checks 0..1 Issr +AndSts +++++UltmtCdtr OrgId Othr Issr 1..1 PrvtId +AndSts +++++UltmtCdtr PrvtId 0..1 DtAndPlcOfBirth +AndSts +++++UltmtCdtr PrvtId DtAndPlcOfBirth Issuer Private Identification SCLSCTPersonIdentification5 Date And Place Of Birth DateAndPlaceOfBirth Entry according to original payment. camt ; SCL SCT; 2017 page 47 of 51

263 camt Content and checks 1..1 BirthDt +AndSts +++++UltmtCdtr PrvtId DtAndPlcOfBirth BirthDt 0..1 PrvcOfBirth +AndSts +++++UltmtCdtr PrvtId DtAndPlcOfBirth PrvcOfBirth 1..1 CityOfBirth +AndSts +++++UltmtCdtr PrvtId DtAndPlcOfBirth CityOfBirth Birth Date ISODate Pattern [0-9]{4,4}\-[0-9]{2,2}\-[0-9]{2,2} Province Of Birth City Of Birth Entry according to original payment. Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 48 of 51

264 camt Content and checks 1..1 CtryOfBirth +AndSts +++++UltmtCdtr PrvtId DtAndPlcOfBirth CtryOfBirth 0..1 Othr 1..1 Id +AndSts +++++UltmtCdtr PrvtId Othr +AndSts +++++UltmtCdtr PrvtId Othr +++ Country Of B irth CountryCode Pattern [A-Z]{2,2} Other GenericPersonIdentification1 Identification Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 49 of 51

265 camt Content and checks 0..1 SchmeNm +AndSts +++++UltmtCdtr PrvtId Othr SchmeNm 1..1 Cd +AndSts +++++UltmtCdtr PrvtId Othr SchmeNm Cd 1..1 Prtry +AndSts +++++UltmtCdtr PrvtId Othr SchmeNm Prtry Scheme PersonIdentificationScheme1Choice Code ExternalPersonIdentification1Code Length Proprietary Entry according to original payment. Entry according to original payment. camt ; SCL SCT; 2017 page 50 of 51

266 camt Content and checks 0..1 Issr +AndSts +++++UltmtCdtr PrvtId Othr Issr Issuer Entry according to original payment. camt ; SCL SCT; 2017 page 51 of 51

Version 3.0 valid from 20 November Notes on the English translation

Version 3.0 valid from 20 November Notes on the English translation The Deutsche Bundesbank s technical specifications for the clearing and settlement of interbank SEPA direct debits via the RPS (SCL) ( SDD/SCL technical specifications ) Version 3.0 valid from 20 November

More information

Version 3.0 valid from 20 November Notes on the English translation

Version 3.0 valid from 20 November Notes on the English translation The Deutsche Bundesbank s procedural rules for the clearing and settlement of SEPA credit transfers via the RPS SEPA-Clearer (Procedural rules for SEPA credit transfers) Version 3.0 valid from 20 November

More information

SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES Doc: EPC115_06 13 December 2006 (Version 2.2) OITS SG SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the

More information

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Doc: EPC114-06 13 December 2006 (Version 2.2) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct

More information

TECHNICAL SPECIFICATIONS FOR THE PROCESSING OF SEPA CREDIT TRANSFER ORDERS AND SEPA PAYMENT RETURN ORDERS

TECHNICAL SPECIFICATIONS FOR THE PROCESSING OF SEPA CREDIT TRANSFER ORDERS AND SEPA PAYMENT RETURN ORDERS Appendix 1.1 TECHNICAL SPECIFICATIONS FOR THE PROCESSING OF SEPA CREDIT TRANSFER ORDERS AND SEPA PAYMENT RETURN ORDERS 1 GENERAL PROVISIONS 1.1 Each participant shall pass a series of tests to prove its

More information

Notice on the routing directory for processing retail payments via the RPS SEPA-Clearer (SCL Directory Notice)

Notice on the routing directory for processing retail payments via the RPS SEPA-Clearer (SCL Directory Notice) Notice on the routing directory for processing retail payments via the RPS SEPA-Clearer (SCL Directory Notice) Version 2.5 valid from 21 November 2016 SCL Directory Notice, Version 2.5 Page 1 of 15 Version

More information

HCT INST SCHEME RULEBOOK V2.0

HCT INST SCHEME RULEBOOK V2.0 HCT INST SCHEME RULEBOOK V2.0 1054 Budapest, Vadász utca 31. Telefon: (1) 428-5600, (1) 269-2270 Fax: (1) 269-5458 www.giro.hu HCT INST SCHEME RULEBOOK V2.0 Issued by GIRO Zrt. GIRO Zrt. declares that

More information

The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules)

The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules) The Deutsche Bundesbank's procedural rules on communication via SWIFTNet FileAct (SWIFTNet FileAct procedural rules) Version 1.7 valid from 21 November 2016 Notes on the English translation This translation

More information

Single Shared Platform. User Detailed Functional Specifications - Optional Services - 2nd book Version May 2013

Single Shared Platform. User Detailed Functional Specifications - Optional Services - 2nd book Version May 2013 Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd book Version 7.01 31 May 2013 Table of Contents Table of Contents 11 Introduction 12 User Guide for optional modules

More information

TARGET Instant Payment Settlement User Requirements

TARGET Instant Payment Settlement User Requirements User s Status: FINAL Executive Summary Introduction The market consultation on the TARGET Instant Payment (TIPS) User s Document (URD) was initiated on 9 January 2017 and ran until 24 February 2017. Financial

More information

SEPA Credit Transfer Unpaid Report File Format

SEPA Credit Transfer Unpaid Report File Format SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland.

More information

EACHA Instant Payments Interoperability Framework

EACHA Instant Payments Interoperability Framework EACHA Instant Payments Interoperability Framework EACHA Framework version : 2017 V1.0 EACHA Framework approval date : 6 April 2017 Aligned to EPC Scheme Rulebook version : 2017 SCT Inst Rulebook version

More information

EACHA Instant Payments Interoperability Framework

EACHA Instant Payments Interoperability Framework EACHA Instant Payments Interoperability Framework EACHA Framework version : 2.0 EACHA Framework approval date : 29 November 2016 Aligned to EPC Scheme Rulebook version : SEPA Instant Credit Transfer Version

More information

Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd book

Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd book Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd book Version 12.0 23 March 2018 Table of Contents Table of Contents 11 Introduction... 1 12 User Guide for optional

More information

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Format description MT940 Structured version 1.0.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information 3 1.2

More information

Format Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

Format Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Format Description MT942 Structured version 1.0.1 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT942 STRUCTURED INTERIM TRANSACTION REPORT 3 1.1 General information

More information

Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN)

Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) 201 Version 1.0 - August 201 2 Table of content 1. Introduction 3 1.1 Related documents 1.2 Character Set 1.3 Change history 1.4 Summary

More information

Format Description MT940 Structured version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)

Format Description MT940 Structured version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) Format Description MT940 Structured version 1.0 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) January 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information

More information

Format Description MT940 Structured version 1.1. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)

Format Description MT940 Structured version 1.1. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) Format Description MT940 Structured version 1.1 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) May 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information

More information

Customer Documentation Message Status Report

Customer Documentation Message Status Report Customer Documentation Message Status Report Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT"). ANY USE OR REPRODUCTION OF

More information

Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd Book

Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd Book Single Shared Platform User Detailed Functional Specifications - Optional Services - 2nd Book Version 11.0 17 March 2017 Table of Contents Table of Contents 11 Introduction... 1 12 User Guide for optional

More information

SELF ASSESSMENT OF SEPA COMPLIANCE November, 2013

SELF ASSESSMENT OF SEPA COMPLIANCE November, 2013 SELF ASSESSMENT OF SEPA COMPLIANCE November, 2013 Bucharest, November 2013 This document constitutes the self-assessment of TRANSFOND`s system SENT against the Eurosystem s SEPA-compliance criteria. The

More information

Terms and Conditions for Remote Data Transmission

Terms and Conditions for Remote Data Transmission Terms and Conditions for Remote Data Transmission (As amended on 15 November 2013) 1. Scope of services (1) The Bank is available to its Customer (account holder) for remote transmission of data by electronic

More information

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

More information

RTGS Application. SWIFT Certified Application. Label Criteria 2018

RTGS Application. SWIFT Certified Application. Label Criteria 2018 Label Criteria 2018 This document explains the business criteria required to obtain the SWIFT Certified Application 2018 label for RTGS applications. 26 January 2018 Table of Contents Table of Contents

More information

TIPS CERTIFICATION TEST CASES

TIPS CERTIFICATION TEST CASES DG-MIP 31 August 2018 UPDATABLE CERTIFICATION TEST CASES Version: 1.0 Status: Final Date: 30/08/2018 Version: 1.00 Table of Contents 1. CERTIFICATION TEST APPROACH AND TEST CASES 3 1.1 APPROACH 3 1.2 Participant

More information

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 005 STANDARDS FOR THE EXCHANGE OF FINANCIAL DATA ON AFT FILES 2017 CANADIAN PAYMENTS ASSOCIATION 2017 ASSOCIATION CANADIENNE

More information

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure ISO 20022 Payments Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) and Customer Payment Status Report (pain.002)

More information

Format description SWIFT MT942

Format description SWIFT MT942 Format description SWIFT MT942 Rabo Cash Management Colophon Title Format description SWIFT MT942 Version, date 2.3, November 2014 On behalf of Zakelijke Klantkanalen Contact Rabobank Nederland Croeselaan

More information

Ulster Bank SEPA Direct Debit Origination Collection Processing Report CPR XML Guide

Ulster Bank SEPA Direct Debit Origination Collection Processing Report CPR XML Guide Ulster Bank SEPA Direct Debit Origination Collection Processing Report CPR XML Guide Version 1.2 May 2016 These documents are strictly for illustrative purposes. Customers should not rely solely on the

More information

ISO TRANSACTION REPORTING GUIDE. v 1.3

ISO TRANSACTION REPORTING GUIDE. v 1.3 ISO 20022 TRANSACTION REPORTING GUIDE v 1.3 4.10.2012 1 ISO 20022 Transaction Reporting Guide Table of contents 1 Introduction... 2 2 General... 2 3 Notification message structure... 3 3.1 Group Header

More information

paycom web User Manual

paycom web User Manual Submitting files and obtaining electronic approval via the Internet Version 1.3 06.10.2016 Base document Information No guarantee can be given for the information contained in this user manual, which is

More information

Annex 2 to the Agreement on Cooperation in the Area of Trade Finance & Cash Management Terms and Conditions for Remote Data Transmission

Annex 2 to the Agreement on Cooperation in the Area of Trade Finance & Cash Management Terms and Conditions for Remote Data Transmission Annex 2 to the Agreement on Cooperation in the Area of Trade Finance & Cash Management Terms and Conditions for Remote Data Transmission 1. Scope of services (1) The Bank is available to its Customer (account

More information

Administrative Guideline. SMPTE Metadata Registers Maintenance and Publication SMPTE AG 18:2017. Table of Contents

Administrative Guideline. SMPTE Metadata Registers Maintenance and Publication SMPTE AG 18:2017. Table of Contents SMPTE AG 18:2017 Administrative Guideline SMPTE Metadata Registers Maintenance and Publication Page 1 of 20 pages Table of Contents 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Definitions

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure ISO 20022 Payments Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) Version 1.1.1 07.08.2017 General note Any

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) Version 1.2, with effect from November

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines Swiss Payment Standards for domestic direct debit pain.008.001.02.ch.03 SPS Version 1.2 UBS Version 1.0 April 2018 UBS Implementation Guidelines Swiss Payment Standards for

More information

ING Format Description MT940 & MT942 Structured NL (V.4)

ING Format Description MT940 & MT942 Structured NL (V.4) ING Format MT940 & MT942 Structured NL (V.4) InsideBusiness Connect SwiftNet FIN SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 20-11-2013 First version 2.0 14-02-2014

More information

ING Format Description

ING Format Description ING Format Structured MT940 & MT942 (Version 4) Strategic InsideBusiness Connect InsideBusiness Payments CEE SwiftNet FIN SwiftNet FileAct Telelink@Isabel EBICS Document version history Version Date Changes

More information

Format Specification

Format Specification Format Specification ISO20022-pain.002.001.03 mbank SA 2017.01.02 Version 1.6 1. General Info...3 2. Short review of pain.002.001.03; format requirements; processing mechanism...3 3. Allowed characters

More information

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) Format description MT940 Structured version 1.1.1 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) November 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information

More information

Creating International Wire Transfer Payments Reference Guide

Creating International Wire Transfer Payments Reference Guide Creating International Wire Transfer Payments Reference Guide Table of Contents Creating and Working with International Wire Transfers 3 Overview 3 Creating a Freeform Payment or Template 3 Approving or

More information

Format Description CAMT and CAMT

Format Description CAMT and CAMT Format CAMT.052.001.02 and CAMT.053.001.02 InsideBusiness Connect SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 First version 2.0 14-02-2014 Updated - List of

More information

SWIFT Certified Applications RTGS. Technical validation Guide Version 1.1

SWIFT Certified Applications RTGS. Technical validation Guide Version 1.1 SWIFT Certified Applications RTGS Technical validation Guide 2018 Version 1.1 February 2018 Legal notices Copyright SWIFT 2018. All rights reserved. You may copy this publication within your organisation.

More information

TARGET Instant Payment Settlement

TARGET Instant Payment Settlement s V0.1.0 Author 4CB Version 0.1.0 Date 27/09/2017 All rights reserved. INTRODUCTION... 6 READER S GUIDE... 7 1. GENERAL FEATURES OF TIPS... 9 1.1. INTRODUCTION TO THE TIPS SERVICE... 9 1.2. ACCESS TO TIPS...

More information

Deutsche Postbank AG. Format Descriptions for Eurogiro Euro Settlement Service ESSP. ESSP Format Descriptions. Page 1.

Deutsche Postbank AG. Format Descriptions for Eurogiro Euro Settlement Service ESSP. ESSP Format Descriptions. Page 1. Deutsche Postbank AG Format Descriptions for Eurogiro Euro Settlement Service ESSP Version, Feb 2009 Deckblatt Format Description Page 1 Contents page Abbreviations... 3 MT202 Settlement Instruction...

More information

CSDs and Securities Market Infrastructures

CSDs and Securities Market Infrastructures Label Criteria 2017 This document explains the criteria required to obtain the SWIFT Certified Application - CSDs and Securities Market Infrastructures 2017 label for your business application. 27 January

More information

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation) SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) Version 1.8, with effect from

More information

Terms and Conditions for Remote Data Transmission

Terms and Conditions for Remote Data Transmission Terms and Conditions for Remote Data Transmission The following translation is provided for your convenience only. The original German text Bedingungen für Datenfernübertragung is binding in all respects.

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) Version 1.8, with effect from

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Version 1.6 25.07.2016 General note Any suggestions or questions relating to this document

More information

Access Online. Payment Upload

Access Online. Payment Upload Access Online Payment Upload ABN AMRO Bank N.V. 2017 All rights reserved. Apart from those exceptions stipulated in or by virtue of the 1912 Copyright Law, no part of this publication may be reproduced

More information

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) and Customer Payment Status Report

More information

BANKING CIRCLE WEB BULK UPLOAD

BANKING CIRCLE WEB BULK UPLOAD 18109 Training Manual - BULK UPLOAD_Layout 1 11/05/2016 10:06 Page 1 Freedom to BANKING CIRCLE WEB BULK UPLOAD SAXO PAYMENTS INTERNET BANKING WHAT IS A BULK PAYMENT? A bulk payment is defined as a payment

More information

SEPA Credit Transfer Conversion Service:

SEPA Credit Transfer Conversion Service: SEPA Credit Transfer Conversion Service: Standard 18 File Specification Winbits This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document

More information

Application of Key UCC 4A Concepts and Terms to the Real-Time Payment System

Application of Key UCC 4A Concepts and Terms to the Real-Time Payment System Application of Key UCC 4A Concepts and Terms to the Real-Time Payment System Note: Capitalized terms have the same meaning as provided in the RTP Rules, unless otherwise noted. UCC 4A Concept or Term Scope

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments for Customer-Bank Messages Credit Transfer (Payment Transactions) Version 1.7 29.05.2017 General note Any suggestions or questions relating to this document should be addressed to the

More information

INSTRUCTION Concerning the Operating Procedures for the Croatian Large Value Payment System

INSTRUCTION Concerning the Operating Procedures for the Croatian Large Value Payment System Pursuant to Article 18, paragraph (1) of the Decision on the rules of operation of the Croatian Large Value System (Official Gazette 55/2011), the Governor of the Croatian National Bank hereby issues the

More information

Sberbank Online User Guide

Sberbank Online User Guide Sberbank Online User Guide Contents 1. Introduction... 2 1.1 Available services... 2 1.2 Security... 2 2. First use... 3 2.1 Login... 3 2.2 Password change... 3 2.3 PIN change... 5 2.3 User profile...

More information

Frequently Asked Questions (FAQs) NACH Debit NATIONAL PAYMENTS CORPORATION OF INDIA

Frequently Asked Questions (FAQs) NACH Debit NATIONAL PAYMENTS CORPORATION OF INDIA Frequently Asked Questions (FAQs) NACH Debit NATIONAL PAYMENTS CORPORATION OF INDIA I. OVERVIEW OF NACH DEBIT 1. What is NACH? The National Payments Corporation of India (NPCI) offers to banks, financial

More information

Payment Integration Bulk Cashier s Order and Cheques Format Specifications

Payment Integration Bulk Cashier s Order and Cheques Format Specifications Payment Integration Bulk Cashier s Order and Cheques Format Specifications Prepared by: Group Transaction Banking, Product Management Electronic Delivery Channels Date: Nov 2017 Contents 1. Introduction...

More information

China Stock Connect Northbound Trading Investor ID Model System File Interface Specification

China Stock Connect Northbound Trading Investor ID Model System File Interface Specification China Stock Connect Northbound Trading Investor ID Model System File Interface Specification Version: 1.1 Prepared by: HKEX Date: 18 Apr 2018 Modification History Version Date Modified By Synopsis 1.0

More information

SR 2019 Business Highlights

SR 2019 Business Highlights This document provides summarised, high level, business information related to the changes made to FIN (MT) messages as part of Standards release 2019 (SR 2019). 16 November 2018 Table of Contents Table

More information

Interface with SIBS-AT2 Oracle FLEXCUBE Universal Banking Europe Cluster Release [October] [2013]

Interface with SIBS-AT2 Oracle FLEXCUBE Universal Banking Europe Cluster Release [October] [2013] Interface with SIBS- Oracle FLEXCUBE Universal Banking Europe Cluster Release 11.3.81.02.0 [October] [2013] Table of Contents Interface with SNCE 1. ABOUT THIS MANUAL... 1-1 1.1 INTRODUCTION... 1-1 1.2

More information

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation) SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information

More information

Corporates Cash Management

Corporates Cash Management SWIFT Certified Applications Corporates Cash Management Technical validation Guide 2017 Version 1.1 February 2017 Legal notices Copyright SWIFT 2017. All rights reserved. You may copy this publication

More information

Preface Entity Identifiers Directory Publication BIC Usage...7

Preface Entity Identifiers Directory Publication BIC Usage...7 This document provides specific guidelines for the use of BICs by SWIFT users, in particular as identifiers and addresses within the SWIFT messaging services. 25 August 2017 Table of Contents Table of

More information

Customer Documentation Request for Information Message (camt.026 & camt.028)

Customer Documentation Request for Information Message (camt.026 & camt.028) Customer Documentation Request for ormation Message (camt.026 & camt.028) Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT").

More information

Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029)

Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029) Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029) Version 2.2 April 2018 1 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT

More information

Seite 1 von 20

Seite 1 von 20 This English translation is provided for your convenience only. In the event of discrepancies the German original text shall prevail over the English translation. Version of October 2016 Version of July

More information

Direct Remittance User manual

Direct Remittance User manual Direct Remittance User manual Version 5.1 Dato 10.09.18 Page 1 of 24 Contents 1 Introducing Direct Remittance... 3 Brief overview of the service... 3 Why direct remittance?... 3 Benefits for companies...

More information

Autorec File Specification

Autorec File Specification www.aib.ie/sepa Autorec File Specification This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank, disseminate the

More information

Category 2 Financial Institution Transfers

Category 2 Financial Institution Transfers SWIFTStandards Category 2 Financial Institution Transfers November 2003 Standards Release 1 Legal Notices Legal Notices IMPORTANT NOTE: You may install and use this publication only if you have entered

More information

Rubric ECB-UNRESTRICTED. Q&A of the month ECB DG-MIP/MID. TIPS Contact Group. 8th Meeting on 4 July

Rubric ECB-UNRESTRICTED. Q&A of the month ECB DG-MIP/MID. TIPS Contact Group. 8th Meeting on 4 July Rubric ECB DG-MIP/MID Q&A of the month TIPS Contact Group 8th Meeting on 4 July 2018 We were wondering whether UDFS or XSD is leading specification in case these would contradict: for example, UDFS says

More information

OPERATING RULES FOR CLEARING OF INTERNATIONAL PAYMENTS

OPERATING RULES FOR CLEARING OF INTERNATIONAL PAYMENTS OPERATING RULES FOR CLEARING OF INTERNATIONAL PAYMENTS 1. Operating Rules for Clearing of International Payments (hereinafter: Rules) shall prescribe the procedure for performing clearing and settlement

More information

9 January February [Please provide your input]

9 January February [Please provide your input] Institution name Deliverable Name Version No. Document sent for review on Feedback by Deutsche Bundesbank TARGET Instant Payments Settlement User Requirements 0.1 9 January 2017 24 February 2017 [Please

More information

ISO CustomerPaymentStatusReport Confirmation of Receipt

ISO CustomerPaymentStatusReport Confirmation of Receipt ISO 20022 CustomerPaymentStatusReport Confirmation of Receipt pain.002 version 3 Version 1.0.1 Publishing date 21 December 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History...

More information

Wire & Internal Transfers

Wire & Internal Transfers Wire & Internal Transfers USER GUIDE Transfer funds easily and securely. Convenience. Transfer money between accounts at Union Bank and different banks domestically and internationally. Ease. Say goodbye

More information

SCT Bulk Payments XML File Format

SCT Bulk Payments XML File Format www.aib.ie/sepa SCT Bulk Payments XML File Format This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank, disseminate

More information

Universal Companion Document Industry Adoption of X

Universal Companion Document Industry Adoption of X Universal Companion Document Industry Adoption of X9.100-187 Version 1.3 April 1, 2014 Version 1.3 of the Universal Companion Document utilizes ANSI X9.100-187-2013 as the base standard. Document Revision

More information

Credit Transfer. PAIN XML File Structure V 1.2

Credit Transfer. PAIN XML File Structure V 1.2 Credit Transfer PAIN.001.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

Message flow and use of XML ISO20022 Messages Corporate egateway

Message flow and use of XML ISO20022 Messages Corporate egateway Message flow and use of XML ISO20022 Messages Corporate egateway Table of contents 1 PURPOSE OF THIS GUIDE... ERROR! BOOKMARK NOT DEFINED. 2 INTRODUCTION... ERROR! BOOKMARK NOT DEFINED. 2.1 THE XML ISO20022

More information

ECC Member Area User Guide

ECC Member Area User Guide ECC Member Area User Guide 24.07.2018 Leipzig Ref. 0009 Table of Contents 1. Introduction 4 2. Registration 5 3. Transactions 7 3.1 Report Subscription 7 3.1.1 Types of Reports 7 3.1.2 Scope of the Report

More information

Order your POSTCARD right away

Order your POSTCARD right away Order your POSTCARD right away Ordering the POSTCARD The benefits at a glance: The POSTCARD is entirely free of charge and can be used anywhere in Germany with delivery agents, at business post and bulk

More information

Error Handling Strategy. DCC Guidance Document

Error Handling Strategy. DCC Guidance Document Error DCC Guidance Document Date: June 2016 Classification: DCC Public Table of Contents 1 Introduction... 3 1.1 Purpose... 3 1.2 Scope... 3 1.3 General Provisions... 3 2 Error Management... 4 2.1 Error

More information

ISO migration related to the future RTGS service. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services

ISO migration related to the future RTGS service. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services ISO 20022 migration related to the future RTGS service 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services Development of working packages for Future RTGS Payment business Other business

More information

TARGET Instant Payment Settlement

TARGET Instant Payment Settlement TARGET Instant Payment Settlement Overview of the market feedback on the 1 st UDFS draft TIPS Contact Group #2 Frankfurt am Main, 07.11.2017 Summary 1. Overview of the market feedback on the UDFS 2. Main

More information

BL Real Time Server. The EBICS server system for SEPA Instant Credit Transfer. SEPA transfers in real-time

BL Real Time Server. The EBICS server system for SEPA Instant Credit Transfer. SEPA transfers in real-time BL Real Time Server The EBICS server system for SEPA Instant Credit Transfer SEPA transfers in real-time according to EPC SCT Inst Scheme Europe-wide instant payment Mastering tomorrow's challenges today:

More information

ISO20022 Messages types and flows in future RTGS services. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services

ISO20022 Messages types and flows in future RTGS services. 14 February 2017 Ad-hoc Workshop on messages for the Future RTGS Services ISO00 Messages types and flows in future RTGS s February 07 Ad-hoc Workshop on messages for the Future RTGS Services messages and message flow in TARGET (I) Background information for the RTGS s (today

More information

Credit Transfer. PAIN XML File Structure Version 1.2. Mandatory Fields Optional Fields Payment Information (Batch) / Transaction Level

Credit Transfer. PAIN XML File Structure Version 1.2. Mandatory Fields Optional Fields Payment Information (Batch) / Transaction Level Credit Transfer PAIN.001.001.03 XML File Structure V 1.3 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

Bankline Guide SEPA Direct Debit Origination

Bankline Guide SEPA Direct Debit Origination Bankline Guide SEPA Direct Debit Origination Table of Contents 1. Initial setup by the Bank.2 2. Processing timelines for SEPA Direct Debit Origination (DDO).2 3. Managing the SEPA Direct Debit Origination

More information

business online plus user guide

business online plus user guide business online plus user guide 1 2 Login : 03-09 Administration : 11-32 Accounts : 33-41 Transfers : 43-47 Beneficiaries : 49-54 Payments : 55-75 Statements : 77-79 Preferences : 81-83 Messages : 86-87

More information

INTRODUCTION TO THE ISO AFT USAGE GUIDELINES

INTRODUCTION TO THE ISO AFT USAGE GUIDELINES INTRODUCTION TO THE ISO 20022 AFT USAGE GUIDELINES INTRODUCTION 1.0 Scope This document outlines the specifications related to the formatting of CPA ISO 20022 Automated Funds Transfer (AFT) payment messages

More information

TERMS AND CONDITIONS OF USE

TERMS AND CONDITIONS OF USE TERMS AND CONDITIONS OF USE Managing SEPA Direct Debits and Mandates V 2.0 PURPOSE OF THIS DOCUMENT The purpose of this document is to define for Customers the Terms and Conditions of Use for the Direct-debits

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines DFÜ Agreement of Deutsche Kreditwirtschaft for Cash Management Reports camt.052.001.02 - DK Version 3.0 UBS Version 1.0 March 2017 Table of Contents 1. Cash Management Reports

More information

ISO Data Element Definitions

ISO Data Element Definitions SECTION 4 ISO 8583 1987 DATA ELEMENT DEFINITIONS Overview...4-1 Bit Maps...4-2 Annotation Conventions For Data Element s...4-3 General Representation...4-3 Length s...4-4 Field Content s...4-5 Conventions

More information

The Bank of Russia Standard FINANCIAL MESSAGES IN THE NPS

The Bank of Russia Standard FINANCIAL MESSAGES IN THE NPS The Bank of Russia Standard STO BR NPS-1.0-2017 FINANCIAL MESSAGES IN THE NPS GENERAL TERMS Introduction date: 2017-03-20 Official publication Moscow 2017 Preamble 1. ACCEPTED AND ENACTED by The Bank of

More information

BERMUDA REGULATORY AUTHORITY (NUMBERING PORTABILITY) GENERAL DETERMINATION 2014 BR 8 / 2014

BERMUDA REGULATORY AUTHORITY (NUMBERING PORTABILITY) GENERAL DETERMINATION 2014 BR 8 / 2014 QUO FA T A F U E R N T BERMUDA REGULATORY AUTHORITY (NUMBERING PORTABILITY) GENERAL BR 8 / 2014 The Regulatory Authority, in exercise of the power conferred by section 62 of the Regulatory Authority Act

More information

This product is the proprietary material of CheckCare Enterprises, LLC. And is not to be distributed or copyrighted without written permission from

This product is the proprietary material of CheckCare Enterprises, LLC. And is not to be distributed or copyrighted without written permission from CheckCare ACH Gateway Reference Secure Pay Edition This product is the proprietary material of CheckCare Enterprises, LLC. And is not to be distributed or copyrighted without written permission from CheckCare

More information