Docstoc

EACHA2007-3.02 Interoperability_

Document Sample
EACHA2007-3.02 Interoperability_ Powered By Docstoc
					“Technical Interoperability Framework for
SEPA - Compliant Giro Payments Processing”

EACHA Taskforce Report v3.02




 Document Reference   :   EACHA2007-3.0 Interoperability

 Issue / date         :   Version 3.02 draft / January, 25 2008

 Produced by          :   EACHA Task Force Interoperability

 Authorised by        :   EACHA

 Circulation          :   Draft versions (v1.0x-v2.9x and v3.01-2) are limited to
                          Members of EACHA and Taskforce EACHA “Interoperability”.

                          The authorised version 3.0 will be made available to EPC and
                          ECB and subsequently brought into the public domain.
EACHA Interoperability Framework (v3.02)




Content



1     Document information .................................................................................................... 3
      1.1       About EACHA ............................................................................................ 3
      1.2       Purpose and Scope of Document ................................................................. 3

2     EACHA Technical Interoperability Framework v2 ............................................................ 4
      2.1       Interoperability supporting SEPA goals ......................................................... 4
      2.2       Why the need for “Interoperability”? ............................................................ 4
      2.3       Building Interoperability framework on EPC work ........................................... 5
      2.4       The EACHA Model ...................................................................................... 6

3     Annex I: Principles to protect “fiduciary” accounts in Inter-CSM settlement .................. 7
      3.1       Clearing and Settlement among Payment service providers Participating in
                Different CSMs .......................................................................................... 8
      3.2       Fiduciary account model ............................................................................. 8
      3.3       Shielding insolvency risks of fiduciary account holder ..................................... 9

4     Annex II: Reconciliation process .................................................................................. 10
      4.1       SEPA Credit Transfer .................................................................................10
      4.2       SEPA Direct Debit .....................................................................................15

5     Annex III: Routing provisions ...................................................................................... 22
      5.1       Routing provisions in SEPA ........................................................................22
      5.2       Routing provisions in SEPA ........................................................................24
      5.3       CSM reach table .......................................................................................24
      5.4       Using the CSM reach table .........................................................................24
      5.5       Managing the CSM reach table ...................................................................24
      5.6       Exchanging the CSM reach table.................................................................24
      5.7       Validity dates ...........................................................................................25
      5.8       Logical structure of the CSM table ..............................................................26
      5.9       Applications of the reach table messages.....................................................27
      5.10      Reach Table Definition: List of data Elements ...............................................31

6     Annex IV: SEPA Core Credit Transfer Messages EACHA guidelines ................................ 34
      6.1       Introduction .............................................................................................34
      6.2       Messages context and scope ......................................................................34
      6.3       Other issues ............................................................................................37
      6.4       Explanatory notes to the message descriptions ............................................38
      6.5       Message descriptions ................................................................................40

7     Annex IV: Bulking Mechanism .................................................................................... 145


8     Annex A : Participant list EACHA Task force on Interoperability ................................. 146


9     Annex B: Timescales ................................................................................................... 147


10    Annex C: Other Related Documents ............................................................................ 148




Page 2 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




1     Document information



1.1   About EACHA

      EACHA aims:

         to be a forum for the sharing of information amongst its members;

         to advance the views of its members on issues of general interest to the payment industry;

         to work on specific issues as and when they arise e.g. developing common standards for SEPA
          inter bank clearing and settlement activities.

      The association created in September 2006 is a not for profit organisation and will not perform any
      commercial or operational role in payments processing. Any commercial relationships will be
      outside the Association. Please refer to chapter 8 for the EACHA participant list of organisations
      contributing to this Technical Paper and for EACHA contact information.

      In January 2006 EACHA initiated an ad hoc task force to draft a technical paper on Interoperability
      in relation to giro payments processing in light of the SEPA challenges. The purpose of this „EACHA
      taskforce on interoperability‟ was to investigate interoperability and to define the guiding principles
      from a payments processing perspective of an open standard industry wide interoperability
      framework.

      Amendments and updates to the Interoperability Framework are the responsibility of the EACHA
      Plenary.



1.2   Purpose and Scope of Document

      EACHA‟s aim is to complement the SEPA standards by establishing an interoperability framework
      that adheres to SEPA goals for the product scheme and the market and available to be used by
      payment processors and payment service providers at least realising interoperability between
      infrastructures. The technical paper version 0.93 (as published in September 2006) was the first
      step. The EACHA framework document version 2.0 (as published in April 2007) described the
      different elements needed to realise interoperability,

      The EACHA framework document version 3.02 further elaborates on the open issues listed in
      version 2.0 needed to realise interoperability in order to allow every payment processor or
      institution willing, to implement these interoperability conventions and principles based on stable
      and authorized specifications. This document will provide a management summary on the
      backgrounds and the concepts introduced in version 2.0 to provide for interoperability for SEPA
      payments.

      This technical paper will reference the PSD terminology; parties will be addressed in their role as
      payment service providers or payment processor. This technical paper concentrates on the
      payment function rather than who is performing the specific function(s) or process(es), as many
      banks combine (parts of) both roles. Whenever in this document the term "bank" is used it
      references its role as payments service provider. Within the scope of this paper we therefore will
      refer to the payments processing function. A payment processor in the capacity of a Clearing and
      Settlement Mechanism (CSM) allows participating payment service providers or their branches to
      clear and settle payments made between them. This document will reference the use of the term
      CSM from the CSM framework.




      Page 3 of 148                                                         Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




2     EACHA Technical Interoperability Framework v2



2.1   Interoperability supporting SEPA goals

      The SEPA is emerging ever more clearly. We are witnessing the introduction of various essential
      architectural elements to complement the design of the SEPA:

      1 the PSD to harmonise the legal and regulatory environment within the SEPA;

      2 shared European governance and oversight by the National Banks;

      3 Target2 as common settlement platform effectively overcoming national boundaries for
        settlement purposes;

      4 the SCT/SDD rulebooks issued by the EPC in conjunction with the Implementation Guidelines
        providing common payment products;

      5 standardised (ISO20022) UNIFI messages introducing XML as main stream technology in
        payments leveraging IP related developments;

      6 “Interoperability” to allow any payment service provider or payment processor can use the
        same technical conventions to send to or receive payments from any other party Based on this
        ability.

      The introduction of these well defined architectural elements together is crucial to build our
      common SEPA for efficient payments between citizens, corporations and institutions where interior
      boundaries will have disappeared effectively. The new SEPA, once fully deployed, can be
      characterised as a scale free network were all can reach all because the architectural elements of
      SEPA are principally available equally to all.



2.2   Why the need for “Interoperability”?

      “Interoperability”, the ability to be systematically and consistently accessible to other payments
      service providers and processors, is essential if we are to create STP processing and open,
      competitive payments processing within SEPA at the same time:

         Technical interoperability is needed to reach SEPA objectives on STP processing

          Based on common interoperability, a seamless payment processing environment will be created
          at an operational level so that straight-through processing is maximised as to realise the SEPA
          scheme goals.

         Technical interoperability vital to create SEPA level playing field

          Interoperability will enable competition between payment processors, so that payment service
          providers can easily connect to or switch processing partners, or, if they desire to do so, to
          connect easily to other payments service providers directly. Technical interoperability will enable
          the payment processors to reach new markets. Interoperability will potentially create
          accessibility to and from all, thus realising a level playing field for all involved.

          Full interoperability will lead to the freedom for banks to change community, or to join several
          communities, all based on the same interoperability basics. Processors will compete based on
          the volumes they attract and on the services they provide. Some of them will specialise to
          attract business. Combined with low switching cost as a result of shared Interoperability, the
          market will constantly arbitrage inefficiencies and barriers.




      Page 4 of 148                                                             Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




      EACHA believes that interoperability is a key component of SEPA infrastructure in a competitive
      market which does not impede infrastructural consolidation.



2.3   Building Interoperability framework on EPC work

      The standards defined in the European Payment Council (EPC) Scheme Rulebooks and
      Implementation Guidelines, in the UNIFI message sets and the PEACH/CSM framework lay the
      foundation for interoperability. To reach the broad spectrum of goals for the SEPA, EACHA believes
      that additional operational and technical conventions for technical interoperability are needed.

      EACHA explicitly recognises the EPC‟s role in defining the SEPA payment schemes and the business
      interoperability that they ensure. EACHA seeks to standardise the technical procedures necessary
      for the technical interoperability of CSMs.

      EACHA proposes to create the basis for interoperability through an open and freely usable
      framework based on technical accessibility to the advantage of all involved in payments processing,
      based on a given set of technical standards guidelines and conventions.

      The EACHA framework on interoperability aims to promote the following shared goals:

         A harmonised implementation of SEPA and end-to-end payment processing at the level of
          payment infrastructure

         Competitive choices for payment processors and for banks

         Market-led rationalisation to boost efficiency and quality

      Banks and CSMs are diverse in their architectures, process flows and business rules. EACHA seeks
      a flexible approach to interoperability for SEPA stakeholders for they do not have uniform needs.
      To this end, specific conventions are needed in addition to SEPA scheme rules.

      For banks, interoperability will create a seamless payment processing environment on an
      operational level so that straight-through processing is maximised as to realise the SEPA goals. It
      promotes competitive choices for banks as well as creating operational flexibility and resilience by
      avoiding a single point of failure in the SEPA market.

      For payment processors, interoperability will help reduce the fragmentation of market
      infrastructures during and after the transition to SEPA. By partially harmonising CSM practices,
      interoperability will improve competition. Instead of avoiding market consolidation, Interoperability
      will actually be one of the enablers of market consolidation. Interoperability will lead to a better
      competition in the market, as unnecessarily protective boundaries will be removed.;
      Interoperability will not be compulsory and some CSMs may provide reach to others.

      The core SEPA Direct Debit and SEPA Credit Transfer schemes are the focus for the framework,
      with a priority to supporting the current core and basic SEPA payment schemes from 28.1.2008.
      The framework permits the exchange of SEPA payments within an AOS community.

      The framework will set the minimal specifications of the technical elements needed to secure
      interoperability. It therefore restricts the interoperability elements to those which are strictly
      necessary to realise SEPA goals, whilst allowing market forces to act freely.

      Whenever possible, this framework reuses existing open standards and – whenever this is not
      possible – widely accepted international procedures to avoid the fragmentation of standards. No
      restrictions are placed on the use of the framework or the standards underlying it.

      EACHA will maintain and issue new versions of this framework in line with changes to the EPC
      rulebooks and the related technical standards.




      Page 5 of 148                                                          Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




2.4   The EACHA Model

      The EACHA Model consists of a number of technical elements which together will enable any of the
      possible ways of exchanging a payment between two payment service provider. This allows a
      sending payment service provider to choose the appropriate mechanism to reach the receiving
      payment service provider from any of the mechanisms it has available.

      The interoperability rules and options are consistent with SEPA schemes and existing CSM legal and
      operational arrangements. No additional financial or legal risks need to be assumed by CSMs and
      no significant investments in IT development or connectivity are envisaged.

       SEPA Standard typology


                                                            Intra Community                Receiving
              Sending                               CSM 1


                                               Direct exchange
        Bank A                                                                                         Bank B


                                               Inter Community
                              CSM 2                                      CSM 3


      The framework can be used in ALL prevalent payment chain topologies: e.g. bilateral bank to bank,
      bank to CSM for intra CSM payments and bank to CSM for inter CSM payments. The framework can
      be used between any two parties in any of these payment chains. In principle it supports any
      length of payments chain based on the ability to “daisy chain” the parties (i.e. the message flows)
      involved. (See Annex IV SEPA Core Credit Transfer Messages EACHA guidelines)

      Payments service providers as well as CSMs will often have multiple options to reach the recipient
      payment service provider. To allow payment service providers to reach SEPA scheme Payment
      service providers in efficient processing chains routing provisions have been detailed resulting in
      standardised CSM reach tables to facilitate individual Payment service providers to easily compare
      reach options from various reach methods. (See Annex III Routing provisions)

      To facilitate an STP exchange of the payments, with clarity about the usage of and checks on each
      of the fields EACHA create a detailed message definition on the basis of the UNIFI XML-messages
      and the EPC Implementation Guidelines. These detailed definitions are accompanied by a message
      flow, displaying the ways in which these message definitions can be used between two parties
      exchanging payments. (See Annex IV SEPA Core Credit Transfer Messages EACHA guidelines)

      Embedded in the EACHA model the fiduciary cq bridging account concept is introduced (See Annex
      I Principles to protect “fiduciary” accounts in Inter-CSM settlement) to enable settlement in any
      possible method of exchange. At the same moment independent reconciliation possibilities are
      created while settling payments via target 2. (See annex II reconciliation process)




      Page 6 of 148                                                           Doc ref: EACHA 2007-3.02 Interoperability
    EACHA Interoperability Framework (v3.02)




3   Annex I: Principles to protect “fiduciary” accounts in Inter-CSM settlement


    The concept is that payments flowing between two CSMs go through two clearing and settlement
    cycles, one cycle in CSM1 and one in CSM2. Settlement will use TARGET2 [T2] Payment Module
    [PM] accounts and will always take place in TARGET2 using the settlement capabilities of the
    Ancillary System Interface. i.e.

    Cycle I: initiated by CSM1, funds are debited from the accounts of sending payment service
    providers and credited to a T2 PM account. On successful completion of settlement the payment
    messages are sent from CSM1 to CSM2.

    Cycle II: initiated by CSM2, the funds are debited from the T2 PM account and distributed to the
    beneficiary payment service providers connected to CSM2. On successful completion of settlement,
    CSM2 sends the payment messages to the beneficiary payment service providers.

    This approach means that in the period between the first settlement cycle and the second, the
    funds have passed from the control of the payment service providers connected to CSM1 and are
    held in a TARGET2 PM account. The intention is that funds will only be held in the PM account intra
    day. Overnight balances are not envisaged.

    There are two slightly different accounting procedures envisaged which are described further in
    section 5 of this document.

    The following diagram illustrates this generic model.

         Target2 used to Debit Bank 1              Target2 used to Debit PM
         and Credit PM account                   Account and Credit PM Bank 2


                    Funds               PM Account                    Funds
                                        In Target 2



             Cycle I: Sending                         Cycle II: Receiving



         Bank 1                 CSM 1                  CSM 2                    Bank 2
        Remitting Payment                 Payment                Payment      Receiving
                     messages             messages               messages




    Settlement, credit and liquidity risk for the receiving CSM and its participants and the sending CSM
    and its participants will be mitigated as follows:

       To eliminate settlement risk, a “settlement before output” model will be used, such that
        messages are only ever forwarded to CSM2 by CSM1 when the first settlement cycle has been
        successfully completed.

       The inter-CSM payments settled in the T2 CSM account represent the gross credit position of
        the community of the receiving participants vis-à-vis the community of the sending participants.
        This feature allows an “easy” resending of the inter-CSM payments not settled on the receiving
        payment service providers accounts back to the sending CSM, in case the receiving CSM
        settlement procedures failed for any reason. There will be no unwinding of inter-CSM
        multilateral balances as only gross credit positions are dealt with. CSMs need to have
        appropriate measures in place to avoid overnight balances on the T2 CSM account.




    Page 7 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




         The CSM account must be protected and limited to ensure that it is only used for the specific
          purpose of inter CSM settlements and to protect against insolvency. Such a limitation should
          ensure – inter alia - that the T2 CSM account performs a purely technical function within the
          inter-CSM payments settlement procedure and that the inter-CSM payments are settled in the
          T2 CSM account in the interest of the community of the CSM participants and “legally”
          segregated/dedicated for the benefit of the receiving CSM participants concerned. Currently
          TARGET2 is not expected to provide technical and legal restrictions to the use of funds in a PM
          account by its holder. EACHA is working with European central banks to define an appropriate
          legal structure.

         In the end, it is worth noting that inter-CSM payments - once settled in the T2 CSM account of
          the receiving CSM - are “legally” final according to the settlement finality rules applicable to the
          sending CSM/TARGET2 system, and therefore the receiving CSM (and its participants) are
          protected against possible insolvencies on the sending side. Protection against insolvencies on
          the receiving side will depend on the settlement finality rules applicable to the receiving
          CSM/TARGET2 system and also will have to be dealt with using a fiduciary contract solution.



3.1   Clearing and Settlement among Payment service providers Participating in
      Different CSMs

      TARGET2 will offer several solutions for settling ancillary system transactions, beyond the
      boundaries of a single national central bank. From a technical point of view the six settlement
      procedures supported by the Single Shared Platform (SSP) of TARGET2 for the settlement of
      ancillary systems (through the so-called Ancillary System Interface - ASI) will enable each CSM on
      behalf of its clients to directly debit or credit accounts at NCBs other then the NCB which is
      responsible for the oversight of the CSM.

      EACHA will use TARGET2 as the settlement mechanism for settlement.

      Settlement among Payment service providers participating in different CSMs

      Within the generic 2 cycle model already described in section 4 of this document, EACHA
      recognises that there are two approaches to the use of PM accounts in terms of the ownership of
      the accounts i.e.

         Fiduciary account model: in this model the PM account used to hold funds between cycles 1 and
          2 is in the name of CSM2 [although the funds will be owned by the Payment service providers
          connected to CSM2].

         Liquidity bridge model: in this model the PM account is owned by a commercial Payment service
          provider that is a settlement bank in CSM2



3.2   Fiduciary account model

      According to the “Communication on TARGET2” released by the ECB, CSMs will be eligible to be
      direct participants in TARGET2 as “organisations providing clearing or settlement services subject
      to oversight by a competent authority” and, therefore, will be allowed to hold settlement accounts
      in the Payment Module (PM) of the Single Shared Platform (SSP). In the fiduciary account model,
      such accounts (hereinafter referred to as T2 CSM accounts) would be used to hold intra day funds
      solely for the purposes of settling transactions that have to be transmitted to participants of other
      CSMs.

      Where one CSM is sending payments to another CSM, the T2 CSM fiduciary account used will
      always be in the name of the receiving CSM. Accordingly, the sending CSM needs to be able to hold
      such a PM account and be able to credit such an account in its settlement [i.e. in cycle 1].




      Page 8 of 148                                                          Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




3.3   Shielding insolvency risks of fiduciary account holder

      The principle risk of a settlement account used as fiduciary account to support inter CSM payments
      is the risk of insolvency of the account holder. All other risks are mitigated by above principles. The
      legal construction, which has to be set up in national law between the CSM and the NCB overseeing
      the facility, is to prevent, in case of insolvency, that balances are drawn into the insolvency and
      that proper and timely unwinding can take place to the owners of these balances.




      Page 9 of 148                                                         Doc ref: EACHA 2007-3.02 Interoperability
                                EACHA Interoperability Framework (v3.02)




                    4           Annex II: Reconciliation process


                                The scope of the EACHA reconciliation proposal is focused on the reconciliation between two CSM‟s
                                exchanging transactions. It can be easily extended however to the CSM to bank domain. As the
                                specific element being added for reconciliation purposes (end-to-end-id/reconciliation-id) is for
                                reconciling between two parties exchanging, the contents of these elements should be removed
                                again before forwarding the message to the next party. If there is again a reconciliation need on
                                this next step the same structure can be used again.



                    4.1         SEPA Credit Transfer
stm Credit Transfer Fid-Fid     For SEPA Credit Transfer two separate flows will need to be reconciled for Credit Transfers, the
           Banks Debit Side                          Settlement Agent Credit                   will be separately defined.
                                normal Credit Transfer and the (TARGET2) Transfer Return. EachBanks Credit Side
                                         CSM1                                   CSM2

                 «1» CTBatch [pacs.008.001]



                 4.1.1          Normal Credit Transfer
              Initial

stm Credit Transfer Fid-Fid
                                               part
                                The specificCTBatch of the process where reconciliation is necessary is pictured below:
                                      Validate



           Banks Debit Side                     CSM1                      Settlement Agent (TARGET2)                    CSM2                    Banks Credit Side
                «2» StatusReport [pacs.002.001]
                 «1» CTBatch [pacs.008.001]



                                            Prepare Settlement
              Initial
                                            Validate CTBatch

                                                                    «3» Pre Settlement [?]
                         «3» Pre Settlement [?]
                                                                  «4» SettlementRequest [ASTransferInitiation]
                 «2» StatusReport [pacs.002.001] Settlement
                                          Initiate


                                                                              Perform Settlement
                                            Prepare Settlement

                                                                                        «5»
                                      «5» Debit Advice [MT900]                       Credit Advice [MT910]
                                                                «3» Pre Settlement [?]
                         «3» Pre Settlement [?]
                                                     «6» SettlementConfirmation [ASInitiationStatus]
                                                              «4» SettlementRequest [ASTransferInitiation]
                                          Initiate settled CT's
                                         Send theSettlement


                                                                             Perform Settlement
                        «7b» Settled CT's [pacs.002.001]            «7a» CT Batch [pacs.008.001]

                                                                                            «5»
            Reconcilliation           «5» Debit Advice [MT900]                           Credit Advice [MT910]
                                                                                                                  Reconcilliation +
                                                       «6» SettlementConfirmation [ASInitiationStatus]
                                                                                                                  Validate CTBatch
                                           Send the settled CT's



                                                     «7a» normally have 2
                                The second CSM will CTStatusReport [pacs.002.001] (and a maximum of 3) incoming flows which were initiated by
               ExitPoint                                «8»
                      «7b» Settled CT's [pacs.002.001]
                                                            Batch [pacs.008.001]

                                the first CSM for settlement and transfer of the Credit Transfers.
                                           ExitPoint
            Reconcilliation
                                                                                                                 Prepare Settlement
                                                                                                                  Reconcilliation +
                                                                                                                  Validate CTBatch



                                                                                                                           «9» Pre Settlement [?]
               ExitPoint                                              «8» StatusReport [pacs.002.001]
                                                              «10» SettlementRequest [ASTransferInitiation]
                                                                                                                  Initiate Settlement
                                                  ExitPoint


                                                                                Perform Settlement               Prepare Settlement




                                                                                                                         «9» Pre Settlement [?]
                                                                                                     «11» Credit Advice [MT910]

                                                                                        «11» Debit Advice
                                                              «10» SettlementRequest [ASTransferInitiation] [MT900]
                                                                                                               Initiate Settlement

                                                                                                                      ExitPoint
                                                                                                                 Send the settled CT's
                                                                            Perform Settlement
                                                           «12» SettlementConfirmation [ASInitiationStatus]


                                                                     «13b» Status Settled [pacs.002.001]
                                                                                                   «11» Credit Advice [MT910]
                                                                                                             «13a»
                                                     ExitPoint                          «11» Debit Advice [MT900] CT Batch [pacs.008.001]
                                                                                                                                                  Reconcilliation +
                                                                                                                                                  Process CTBatch
                                Page 10 of 148                                                                                                                  Doc ref: EACHA 2007-3.02 Interoperability
                                                                                                                      ExitPoint
                                                                                                                 Send the settled CT's
                                                           «12» SettlementConfirmation [ASInitiationStatus]
EACHA Interoperability Framework (v3.02)




In the Settlement Request the first CSM will put a specific settlement reference number and will of
course specify the settlement amount. Leaving out the not relevant parts, this would result in a
following example Settlement Request:


      <pain.998.001.01>
        <PrtryDt>
          <Tp>ASTransferInitiation</Tp>
          <SspPrtryDt>
            <GrpHdr>
              …
              <InitgPty>
                <FI>
                   <BIC>CSM1CC2LXXX</BIC>
                </FI>
              </InitgPty>
            </GrpHdr>
            <PmtInf>
              <ReqExctnDt>2008-01-02</ReqdExctnDt>
              <FrstAgt>
                <BIC>CSM1CC2LTEC</BIC>
              </FrstAgt>
              <PmtTx>
                <PmtId>
                   <InstrId>ABC1234</InstrId>
                   <EndToEndId>RECONREF001</EndToEndId>
                </PmtId>
                <Amt>
                   <InstAmt>300.00</InstAmt>
                </Amt>
                <FnlAgt>
                   <BIC>CSM2CC2LFID</BIC>
                </FnlAgt>
                …
              <PmtTx>
            <PmtInf>
            …
          </SspPrtryDt>
        </PrtryDt>
      </pain.998.001.01>


In this case CSM2 makes use of the Fiduciary account.

If successfully executed the above stated part of the ASTransferInitiation will result in the following
MT910 to the beneficiary in TARGET2. In this case it will be send to the Fiduciary BIC code of
CSM2. This is under the assumption that the second CSM has requested these optional MT910
messages to be send.


      :20:AS02100240012345
      :21:RECONREF001
      :25:CSM2CC2LFID
      :32A:080102EUR300,00
      :52:CSM1CC2LXXX




Page 11 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




This then needs to be able to be connected to the pacs.008 which will be send after a successful
settlement. This is depicted below in an extract of this message:


      <pacs.008.001.01>
        <GrpHdr>
          …
          <IntrBkSttlmDt>2008-01-02</IntBkSttlmDt>
          …
        </GrpHdr>
        <CdtTrfTxInf>
          …
          <IntrBkSttlmAmt Ccy=”EUR”>300</IntrBkSttlmAmt>
          …
          <InstrForNxtAgt>
            <InstrInf>/STTLMREF/RECONREF001</InstrInf>
          </InstrForNxtAgt>
          …
        </CdtTrfTxInf>
      </pacs.008.001.01>


As a result the second CSM can now reconcile the receive pacs.008 with the received MT910.

All the amounts of the settlements done with reference „RECONREF001‟ from initiating CSM
„CSM1CC2LXXX‟ on Settlement Date „080102‟ need to be added up and need to match to the sum
of the amount of all the transactions received in a pacs.008 from the Swift sender „CSM1CC2L‟ with
reference (in instruction for next agent field) „RECONREF001‟ and settlement date „2008-01-02‟.

In case the optional functionality of a pre settlement advice is used, the second CSM can firstly
reconcile this pre settlement advice with the received Credit advice in the MT910. This way it can
be ensured the predicted and intended amount ended up on the settlement account. This means
that the amount in field 32A of the Credit advice should equal the amount specified in the pre
settlement advice and that the related reference in field 21 of the Credit advice should match the
end-to-end id specified in the pre settlement advice.




Page 12 of 148                                                      Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




4.1.2   Credit Transfer Return

        The flows for a Credit Transfer Return are much like the flows of a normal Credit Transfer, with the
        exception of the messages used, where the pacs.008 is replaced by the pacs.004. Looking at the
        previous Credit Transfer example the resulting messages for the Return would be as follows:

        In the Settlement Request the second CSM will put a specific settlement reference number and will
        of course specify the settlement amount. Leaving out the not relevant parts, this would result in a
        following example Settlement Request:


              <pain.998.001.01>
                <PrtryDt>
                  <Tp>ASTransferInitiation</Tp>
                  <SspPrtryDt>
                    <GrpHdr>
                      …
                      <InitgPty>
                        <FI>
                          <BIC>CSM2CC2LXXX</BIC>

              </FI>
                      </InitgPty>
                    </GrpHdr>
                    <PmtInf>
                      <ReqExctnDt>2008-01-03</ReqdExctnDt>
                      <FrstAgt>
                        <BIC>CSM2CC2LTEC</BIC>
                      </FrstAgt>
                      <PmtTx>
                        <PmtId>
                           <InstrId>ABC1234</InstrId>
                           <EndToEndId>CSM2RECREF0001</EndToEndId>
                        </PmtId>
                        <Amt>
                           <InstAmt>300.00</InstAmt>
                        </Amt>
                        <FnlAgt>
                           <BIC>BANKCC2LBRI</BIC>
                        </FnlAgt>
                        …
                      <PmtTx>
                    <PmtInf>
                    …
                  </SspPrtryDt>
                </PrtryDt>
              </pain.998.001.01>


        In this case CSM1 makes use of a liquidity bridge bank.




        Page 13 of 148                                                      Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




If successfully executed the above stated part of the ASTransferInitiation will result in the following
MT910 to the beneficiary in TARGET2. In this case it will be send to the Liquidity Bridging bank BIC
code of the Bridge bank of CSM1. This is under the assumption that this bank has requested these
optional MT910 messages to be send.


      :20:AS02100240012345
      :21:CSM2RECREF0001
      :25:BANKCC2LBRI
      :32A:080103EUR300,00
      :52:CSM2CC2LXXX


This then needs to be able to be connected to the pacs.004 which will be send after a successful
settlement. This is depicted below in an extract of this message:


      <pacs.004.001.01>
        <GrpHdr>
          …
          <IntrBkSttlmDt>2008-01-03<IntBkSttlmDt>
          …
        </GrpHdr>
        <TxInf>
          …
          <RtrdIntrBkSttlmAmt Ccy=”EUR”>300</RtrdIntrBkSttlmAmt>
          …
          <RtrRsnInf>
            …

      <AddtlRtrRsnInf>/STTLMREF/CSM2RECREF0001</AddtlRtrRsnInf>
          </RtrRsnInf>
          …
        </TxInf>
      </pacs.004.001.01>


As a result the first CSM can now reconcile the receive pacs.004 with the received MT910
(forwarded by the liquidity bridge bank).

All the amounts of the settlements done with reference „CSM2RECREF0001‟ from initiating CSM
„CSM2CC2LXXX‟ on Settlement Date „080103‟ need to be added up and need to match to the sum
of the amount of all the transactions received in a pacs.004 from the Swift sender „CSM2CC2L‟ with
reference (in Additional Return Reason Information) „CSM2RECREF0001‟ and settlement date
„2008-01-03‟.

In case the optional functionality of a pre settlement advice is used, the first CSM can firstly
reconcile this pre settlement advice with the received Credit advice in the MT910. This way it can
be ensured the predicted and intended amount ended up on the settlement account. This means
that the amount in field 32A of the Credit advice should equal the amount specified in the pre
settlement advice and that the related reference in field 21 of the Credit advice should match the
end-to-end id specified in the pre settlement advice.




Page 14 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
                                                 ExitPoint       «4a» StatusReport [pacs.002.001]


                                                                          «4b» Rejects [pacs.002.001]
                                           Forw ard Rej ect
                                     EACHA
                      «4b» rejects [pacs.002.001]   Interoperability Framework (v3.02)DD Batch
                                                                                 Forw ard



                                                                                                                       «5» DD Batch [pacs.003.001]
                                                                                                                                               Validate/Process
                                                                                                                                                   DD Batch

                                                                                                                Forw ard
                          4.2        SEPA Direct Debit                                                        Rej ect/Refusal
                                                                                                                                    «6»Reject/Refusal [pacs.002.001]


                                     SEPA Direct Debit consists of several flows, which can be reconciled. The Normal Direct Debit Flow,
                                                                                               «7» StatusReport [pacs.002.001]
                                                         Direct Debit Flow,
                                     the Return/Refund «8» Reject/Refusal [pacs.002.001] the Reversal Direct Debit Flow. Each will be separately
                                           Forw ard
                                         Rej ect/Refusal
                                     defined.
                  «10»Reject/Refusal [pacs.002.001]
                                                                 «9» StatusReport [pacs.002.001]

                       4.2.1         Normal Direct Debit                                                   ExitPoint


                                     The specific part of the process where reconciliation is necessary is pictured below:
                                                                             Wait until Day D /
Direct Debit Fid-Fid
                                                                                                             Prepare Settlement
      Banks Credit Side                          CSM1                 Settlement Agent (TARGET-2)                  CSM2                         Banks Debit Side


                  «1» DD Batch [pacs.003.001]                              «11» Pre settlement [?]                         «11»Pre settlement [?]


                                                                                                             Initiate Settlement
            Initial
                                         Validate DD Batch

                                                                                                «12» SettlementRequest [ASTransferInitiation]
                                                                           Perform Settlement

       «2a» StatusReport [pacs.002.001]
                                                             «13»
                      «2b» Rejects [pacs.002.001]
                                                             Credit Advice [MT910]                   «13» Debit Advice [MT900]

                                         Forw ard DD Batch                     «14» SettlementConfirmation [ASInitiationStatus]
                                                                                                             Send Settled DD's
                                                               «3» DD Batch [pacs.003.001]
                                                                                                             Validate DD Batch

                                                                      «15» DD Status [pacs.002.001]                     «15» DD Status [pacs.002.001]
                                                 ExitPoint       «4a» StatusReport [pacs.002.001]

                                          Reconcilliation /
                                         Prepare Settlement               «4b» Rejects [pacs.002.001]                                               Reconcilliation
                                           Forw ard Rej ect
                      «4b» rejects [pacs.002.001]                                                            Forw ard DD Batch

                                     CSM 1 will normally have 2 (and a maximum of 3) incoming flows which were initiated by the CSM
                        «16»Pre settlement [?]


                                     2 for settlement and confirmation of the Direct Debits.
                                        Initiate Settlement
                                                                                «5» DD Batch [pacs.003.001]
                                                                                                            ExitPoint                          Validate/Process
                                             «17» SettlementRequest [ASTransferInitiation]                                                         DD Batch
                                                                     Perform Settlement
                                                                                                                Forw ard
                                                                                                              Rej ect/Refusal
                                                                                                                                    «6»Reject/Refusal [pacs.002.001]

                                  «18» Credit Advice [MT910]
                                                    «18» Debit Advice [MT900]
                                               Forw ard              «8» Reject/Refusal [pacs.002.001]                   «7» StatusReport [pacs.002.001]
                                           Rej ect/Refusal
                                            ExitPoint
                                         Send Settled DD's
                                                                 «19»SettlementConfirmation [ASInitiationStatus]
                  «20»Reject/Refusal [pacs.002.001]
                  «10»DD Status [pacs.002.001]
                                                                 «9» StatusReport [pacs.002.001]


                                                                                                           ExitPoint
        Reconcilliation

                                                                                                              Wait until Day D /
                                                                                                             Prepare Settlement


           ExitPoint
                                                                           «11» Pre settlement [?]                         «11»Pre settlement [?]


                                                                                                             Initiate Settlement


                                                                                                «12» SettlementRequest [ASTransferInitiation]
                                                                           Perform Settlement


                                                             «13»
                                                             Credit Advice [MT910]                   «13» Debit Advice [MT900]

                                                                               «14» SettlementConfirmation [ASInitiationStatus]
                                                                                                             Send Settled DD's




                                                                      «15» DD Status [pacs.002.001]                     «15» DD Status [pacs.002.001]



                                          Reconcilliation /
                                         Prepare Settlement                                                                                         Reconcilliation


                        «16»Pre settlement [?]

                                         Initiate Settlement
                                                                                                                                                       ExitPoint
                                             «17» SettlementRequest [ASTransferInitiation]
                                                                     Perform Settlement



                                    Page Advice [MT910]
                                  «18» Credit 15 of 148                                                                                                               Doc ref: EACHA 2007-3.02 Interoperability
                                                     «18» Debit Advice [MT900]

                                            ExitPoint
EACHA Interoperability Framework (v3.02)




In the Settlement Request CSM 2 will put a specific settlement reference number and will of course
specify the settlement amount. Leaving out the not relevant parts, this would result in a following
example Settlement Request:


      <pain.998.001.01>
        <PrtryDt>
          <Tp>ASTransferInitiation</Tp>
          <SspPrtryDt>
            <GrpHdr>
              …
              <InitgPty>
                <FI>
                   <BIC>CSM2CC2LXXX</BIC>
                </FI>
              </InitgPty>
            </GrpHdr>
            <PmtInf>
              <ReqExctnDt>2009-11-06</ReqdExctnDt>
              <FrstAgt>
                <BIC>CSM2CC2LTEC</BIC>
              </FrstAgt>
              <PmtTx>
                <PmtId>
                   <InstrId>ABC1234</InstrId>
                   <EndToEndId>RECONREF001</EndToEndId>
                </PmtId>
                <Amt>
                   <InstAmt>300.00</InstAmt>
                </Amt>
                <FnlAgt>
                   <BIC>CSM1CC2LFID</BIC>
                </FnlAgt>
                …
              <PmtTx>
            <PmtInf>
            …
          </SspPrtryDt>
        </PrtryDt>
      </pain.998.001.01>


In this case CSM1 makes use of the Fiduciary account.



If successfully executed the above stated part of the ASTransferInitiation will result in the following
MT910 to the beneficiary in TARGET2. In this case it will be send to the Fiduciary BIC code of
CSM1. This is under the assumption that CSM 1 has requested these optional MT910 messages to
be send.


      :20:AS02100240012345
      :21:RECONREF001
      :25:CSM1CC2LFID
      :32A:091106EUR300,00
      :52:CSM2CC2LXXX




Page 16 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




        This then needs to be able to be connected to the pacs.002 which will be send after a successful
        settlement in order to confirm the settlement of the original Direct Debits back to CSM 1. This is
        depicted below in an extract of this message:


              <pacs.002.001.02>
                <GrpHdr>
                  …
                  …
                </GrpHdr>
                <OrgnlGrpInfAndSts>
                  …
                  <OrgnlMsgId>Identification of the original
              pacs.003</OrgnlMsgId>
                  <OrgnlMsgNmId>‘pacs.003.001.01’</OrgnlMsgNmId>
                  …
                  <GrpSts>ACSC</GrpSts>(Can also be status ‘PART’)
                  <StsRsnInf>
                    …
                    <AddtlStsRsnInf>/INTRBKSTTLMDT/2009-11-
              06</AddtlStsRsnInf>

              <AddtlStsRsnInf>/TTLINTRBKSTTLMAMT/EUR300</AddtlStsRsnInf>
                    <AddtlStsRsnInf>/STTLMREF/RECONREF001</AddtlStsRsnInf>
                  </StsRsnInf>
                  …
                </OrgnlGrpInfAndSts>
                <TxInfAndSts>
                  …
                  <TxSts>ACSC</TxSts>
                  …
                  …
                </TxInfAndSts>
              </pacs.002.001.02>


        As a result CSM 1 can now reconcile the receive pacs.002 with the received MT910.

        All the amounts of the settlements done with reference „RECONREF001‟ from initiating CSM
        „CSM2CC2LXXX‟ on Settlement Date „091106‟ need to be added up and need to match to the sum
        of the amount of all the transactions received in a pacs.002 from the Swift sender „CSM2CC2L‟ with
        reference (in instruction for next agent field) „RECONREF001‟ and settlement date „2009-11-06‟.

        In case the optional functionality of a pre settlement advice is used, CSM 1 can firstly reconcile this
        pre settlement advice with the received Credit advice in the MT910. This way it can be ensured the
        predicted and intended amount ended up on the settlement account. This means that the amount
        in field 32A of the Credit advice should equal the amount specified in the pre settlement advice and
        that the related reference in field 21 of the Credit advice should match the end-to-end id specified
        in the pre settlement advice.


4.2.2   Direct Debit Return/Refund

        The flows for a Direct Debit Return/Refund are much like the flows of a normal Direct Debit, with
        the exception of the messages used, where the pacs.003 is replaced by the pacs.004. For
        reconciliation purposes however in both cases the pacs.002 is used, as the pacs.003 and pacs.004
        need to be exchanged before settlement takes place. Looking at the previous Direct Debit example
        the resulting messages for the Return would be as follows:




        Page 17 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




In the Settlement Request CSM 1 will put a specific settlement reference number and will of course
specify the settlement amount. Leaving out the not relevant parts, this would result in a following
example Settlement Request:


      <pain.998.001.01>
        <PrtryDt>
          <Tp>ASTransferInitiation</Tp>
          <SspPrtryDt>
            <GrpHdr>
              …
              <InitgPty>
                <FI>
                   <BIC>CSM1CC2LXXX</BIC>
                </FI>
              </InitgPty>
            </GrpHdr>
            <PmtInf>
              <ReqExctnDt>2009-11-08</ReqdExctnDt>
              <FrstAgt>
                <BIC>CSM1CC2LTEC</BIC>
              </FrstAgt>
              <PmtTx>
                <PmtId>
                   <InstrId>ABC1234</InstrId>
                   <EndToEndId>CSM1RECREF0001</EndToEndId>
                </PmtId>
                <Amt>
                   <InstAmt>300.00</InstAmt>
                </Amt>
                <FnlAgt>
                   <BIC>BANKCC2LBRI</BIC>
                </FnlAgt>
                …
              <PmtTx>
            <PmtInf>
            …
          </SspPrtryDt>
        </PrtryDt>
      </pain.998.001.01>


In this case CSM2 makes use of a liquidity bridge bank.

If successfully executed the above stated part of the ASTransferInitiation will result in the following
MT910 to the beneficiary in TARGET2. In this case it will be send to the Liquidity Bridging bank BIC
code of the Bridge bank of CSM2. This is under the assumption that this bank has requested these
optional MT910 messages to be send.


      :20:AS02100240012345
      :21:CSM1RECREF0001
      :25:BANKCC2LBRI
      :32A:091108EUR300,00
      :52:CSM1CC2LXXX




Page 18 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




This then needs to be able to be connected to the pacs.002 which will be send after a successful
settlement. This is depicted below in an extract of this message:


      <pacs.002.001.02>
        <GrpHdr>
          …
          …
        </GrpHdr>
        <OrgnlGrpInfAndSts>
          …
          <OrgnlMsgId>Identification of the original
      pacs.004</OrgnlMsgId>
          <OrgnlMsgNmId>‘pacs.004.001.01’</OrgnlMsgNmId>
          …
          <GrpSts>ACSC</GrpSts>(Can also be status ‘PART’)
          <StsRsnInf>
            …
            <AddtlStsRsnInf>/INTRBKSTTLMDT/2009-11-
      08</AddtlStsRsnInf>

      <AddtlStsRsnInf>/TTLINTRBKSTTLMAMT/EUR300</AddtlStsRsnInf>

      <AddtlStsRsnInf>/STTLMREF/CSM1RECREF0001</AddtlStsRsnInf>
          </StsRsnInf>
          …
        </OrgnlGrpInfAndSts>
        <TxInfAndSts>
          …
          <TxSts>ACSC</TxSts>
          …
          …
        </TxInfAndSts>
      </pacs.002.001.02>


As a result CSM 2 can now reconcile the receive pacs.002 with the received MT910 (forwarded by
the liquidity bridge bank).

All the amounts of the settlements done with reference „CSM1RECREF0001‟ from initiating CSM
„CSM1CC2LXXX‟ on Settlement Date „091108‟ need to be added up and need to match to the sum
of the amount of all the transactions received in a pacs.002 from the Swift sender „CSM1CC2L‟ with
reference (in Additional Return Reason Information) „CSM1RECREF0001‟ and settlement date
„2009-11-08‟.

In case the optional functionality of a pre settlement advice is used, CSM 2 can firstly reconcile this
pre settlement advice with the received Credit advice in the MT910. This way it can be ensured the
predicted and intended amount ended up on the settlement account. This means that the amount
in field 32A of the Credit advice should equal the amount specified in the pre settlement advice and
that the related reference in field 21 of the Credit advice should match the end-to-end id specified
in the pre settlement advice.




Page 19 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




4.2.3   Direct Debit Reversal

        The flows for a Direct Debit Reversal are much like the flows of a normal Credit Transfer, where the
        messages only need to be send to the other CSM after settlement has taken place.

        In the Settlement Request CSM 1 will put a specific settlement reference number and will of course
        specify the settlement amount. Leaving out the not relevant parts, this would result in a following
        example Settlement Request:


              <pain.998.001.01>
                <PrtryDt>
                  <Tp>ASTransferInitiation</Tp>
                  <SspPrtryDt>
                    <GrpHdr>
                      …
                      <InitgPty>
                        <FI>
                           <BIC>CSM1CC2LXXX</BIC>
                        </FI>
                      </InitgPty>
                    </GrpHdr>
                    <PmtInf>
                      <ReqExctnDt>2009-11-07</ReqdExctnDt>
                      <FrstAgt>
                        <BIC>CSM1CC2LTEC</BIC>
                      </FrstAgt>
                      <PmtTx>
                        <PmtId>
                           <InstrId>ABC1234</InstrId>
                           <EndToEndId>CSM1RECREF0001</EndToEndId>
                        </PmtId>
                        <Amt>
                           <InstAmt>300.00</InstAmt>
                        </Amt>
                        <FnlAgt>
                           <BIC>BANKCC2LBRI</BIC>
                        </FnlAgt>
                        …
                      <PmtTx>
                    <PmtInf>
                    …
                  </SspPrtryDt>
                </PrtryDt>
              </pain.998.001.01>


        In this case CSM2 makes use of a liquidity bridge bank.

        If successfully executed the above stated part of the ASTransferInitiation will result in the following
        MT910 to the beneficiary in TARGET2. In this case it will be send to the Liquidity Bridging bank BIC
        code of the Bridge bank of CSM2. This is under the assumption that this bank has requested these
        optional MT910 messages to be send.


              :20:AS02100240012345
              :21:CSM1RECREF0001
              :25:BANKCC2LBRI
              :32A:091107EUR300,00
              :52:CSM1CC2LXXX




        Page 20 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




This then needs to be able to be connected to the pacs.007 which will be send after a successful
settlement. This is depicted below in an extract of this message:


      <pacs.007.001.01>
        <GrpHdr>
          …
          <TtlRvsdIntrBkSttlmAmt
      Ccy=”EUR”>300</TtlRvsdIntrBkSttlmAmt>
          <IntrBkSttlmDt>2009-11-07</IntBkSttlmDt>
          …
        </GrpHdr>
        <OrgnlGrpInf>
          …
          <OrgnlMsgId>Identification of the original
      pacs.003</OrgnlMsgId>
          <OrgnlMsgNmId>‘pacs.003.001.01’</OrgnlMsgNmId>
          …
          <RvslRsnInf>
            …

      <AddtlStsRsnInf>/STTLMREF/CSM1RECREF0001</AddtlStsRsnInf>
          </RvslRsnInf>
          …
        </OrgnlGrpInf>
        <TxInf>
          …
        </TxInf>
      </pacs.007.001.01>


As a result CSM 2 can now reconcile the received pacs.007 with the received MT910 (forwarded by
the liquidity bridge bank).

All the amounts of the settlements done with reference „CSM1RECREF0001‟ from initiating CSM
„CSM1CC2LXXX‟ on Settlement Date „091108‟ need to be added up and need to match to the sum
of the amount of all the transactions received in a pacs.007 from the Swift sender „CSM1CC2L‟ with
reference (in Additional Return Reason Information) „CSM1RECREF0001‟ and settlement date
„2009-11-08‟.

In case the optional functionality of a pre settlement advice is used, CSM 2 can firstly reconcile this
pre settlement advice with the received Credit advice in the MT910. This way it can be ensured the
predicted and intended amount ended up on the settlement account. This means that the amount
in field 32A of the Credit advice should equal the amount specified in the pre settlement advice and
that the related reference in field 21 of the Credit advice should match the end-to-end id specified
in the pre settlement advice.




Page 21 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




 5      Annex III: Routing provisions



 5.1    Routing provisions in SEPA

        With the introduction of SEPA, different routes for transactions are possible; these are described in
        the top half of the following diagram. The bottom half shows an example of the mix of routing
        options that will exist in the real life implementations of SEPA.
        SEPA Standard typology for swift routing table


                                                               Intra Community                   Receiving
               Sending                                CSM 1


                                                  Direct exchange
          Bank A                                                                                              Bank B


                                                  Inter Community
                                 CSM 2                                       CSM 3


               Information CSM reach tables                      Information Swift routing table
         Real life mix of business models


               Sending                                 CSM 1                                      Receiving



           Bank A        CSM 3/ Processing bank                        CSM 4/ Processing bank                 Bank B




                                CSM 2
                                                                              CSM 3




                                                      CSM 4




5.1.1   Participants' choice

        A payment service provider needs at least one CSM to be able to remit to and receive payments
        from payment service providers it does not enjoy bilateral arrangements with. The CSM framework
        states that each Scheme Participant shall ensure that it establishes access to a sufficient number of
        CSMs so as to create the required options for making and receiving payments and thereby creating
        reachability. It is up to the responsibility of a payment service provider to select the CSM(s) that
        provide adequate reach. A payment service provider also has the discretion to differentiate
        between CSMs over business attributes. As a consequence a participant can remit and receive
        payments to and from more than one CSM.


5.1.2   CSM choice

        Offering reach to their community is essential for CSMs. CSMs can choose to cooperate with one or
        more CSM‟s as to facilitate routing of payments to the receiver payment service provider‟s
        reachability point if outside their own community. CSMs can have other CSMs to act as a
        Reachability point for them: e.g. CSM1 agrees to act as Reachability point for CSM 2 for payments
        remitted to it from outside CSM2's community.




        Page 22 of 148                                                                          Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




5.1.3   Routing provisions

        As a consequence of both participants' choices and CSM choices it will be often possible in the SEPA
        for a remitting payment service provider to reach receiving payment service providers through
        multiple routes. To enable remitters and receivers to find each other with the opportunity to
        optimise the actual routing of messages "routing provisions" have to be made.

        The routing provisions are part of interoperability catering for efficient and competitive payments
        processing, it is not in it self meant to provide full reach to all for it does not cater for the
        contractual arrangements needed to exchange payments between agents in the value chain.


5.1.4   Two purposes, two tables

        From a remitting perspective in principle all payment service providers - or CSM(s) on their behalf -
        need to be able to know where it can reach a receiving payment service provider. Payment service
        providers will have to provide the appropriate information as to make known to the market in
        general how it wants to be reached (perspective of receiving payments service providers). The
        reachability directory (e.g. the SWIFT SEPA routing database) could be extended to contain all
        the necessary and up to date information where a payment service provider can be reached
        containing the product, technical and business attributes needed for routing purposes. The
        reachability directory should contain reachability information from all payment service providers.

        The reachability point information should be considered part of the technical level, independent of
        competitive interest at the business level. This data has to be made available to all market
        participants. The reachability table does not contain any routing information as such but only
        reflects the reachability end point information of a payments service provider or CSM.

        A remitting payment service provider has to know the reach available via the CSM(s) it has
        contractual relations with (perspective of payments service providers). A CSM will publish a CSM
        reach table with a list of payments service providers and the reachability related business and
        technical attributes within its reach (direct and if applicable indirect via inter CSM reachability
        arrangements with other CSM‟s). The remainder of this document will focus on the CSM reach
        table.

        The advantages of segregating the two purposes over two tables:

        1 The tables will be maintained by the parties directly influenced by the table content (receiver for
          reachability information, CSM‟s for CSM tables serving their own community)

        2 The remitting payment service provider can optimise the routing of its payments, while the
          receiving payment service provider can optimise, independently of the remitters routing, their
          reachability point of preference.

        3 The reachability table remains part of the technical level, the CSM table is part of the business
          level.

        NB This remainder of this chapter is nearly identical to the routing provisions chapter from the
        "Technical Interoperability Framework for SEPA - Compliant Giro Payments Processing” - EACHA
        Taskforce Report v2.0" document. It serves as the basis for the mechanisms described in this
        document.




        Page 23 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




5.2   Routing provisions in SEPA

      The CSM framework states that each Scheme Participant shall ensure that it establishes access to a
      sufficient number of CSMs so as to create the required options for making and receiving payments.
      In other words, it must be reachable. Consequently clearing payments presupposes knowing which
      payments service providers are reachable through which CSM.

      CSMs need an operationally robust mechanism, which takes into account inter-CSM connection
      routing possibilities. The EPC will maintain a directory of payments service providers that have
      signed the Adherence Agreements; however, this will not be the full solution as required by CSMs.
      This document describe the complete EACHA solution.



5.3   CSM reach table

      According to the CSM framework a Scheme Participant selecting a CSM must establish that the
      receiving Scheme Participant is addressable (directly or indirectly) through that mechanism. CSMs
      will have to provide a list of all payment service providers that they can reach to participating
      payments service providers. In order to fulfil their obligations, CSMs that interoperate with other
      CSMs will have to exchange this information with each other as well.

      Harmonisation of the table structure benefits CSMs as they will not have to implement different
      solutions with each partner CSM for determining routing information.

      The CSM reach table structure and CSM table (XML formatted) message should be standardised via
      ISO 20022 methodology and be incorporated in the UNIFI message set. In the meantime, EACHA
      will use interim standards.

      The data will cover all payment service providers reachable by the CSM and the relevant technical
      and business attributes specified below.



5.4   Using the CSM reach table

      The remitter can instruct its contracted CSM to route the message through another CSM. This is
      limited to the inter CSM arrangements available to this CSM. If the remitter has not requested any
      preference, the CSM will have the discretion to choose one of the possible paths among those
      available in order to reach the receiver participant.



5.5   Managing the CSM reach table

      Each CSM will maintain it‟s own CSM table for the SEPA CT and DD compliant payment service
      providers it can reach direct and if applicable indirectly via inter CSM arrangements.

      Each CSM holds the complete reach table of the participants he has an agreement with and holds
      the “shared data” of all the participants that are customer of those CSMs he has an agreement
      with.



5.6   Exchanging the CSM reach table

      Each CSM remits the information and related updates on its own connected payment service
      providers to all the other CSM with which it has an interoperability agreement.

      While the structure to do this with is standard, any CSMs using the standard would agree bilaterally
      whether to provide other CSMs with the full content of their reach tables or only a specific set of
      BICS to which they will be giving reach to the other CSM.




      Page 24 of 148                                                      Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




      At a bilaterally agreed time and frequency, the CSMs exchange updates to their own reach tables
      pertaining to their customers (creation, cancellation, variation). They must also agree on a time to
      activate such changes.

      Each CSM has to be able to supply, on request of a counterparty CSM, a full and up-to-date version
      of its CSM reach table, including all route entries that have a start date in the future.

      The CSM reach table updates will be exchanged on the basis of common agreed standards.
      Participating CSMs may extend the functionality of the updates on a bilateral basis.

      The CSM reach table updates will be exchanged by means of a File Transfer System bilaterally
      agreed between the parties.

      In order to simplify the CSM reach table updating process the exchanged physical file should
      contain all the updates pertaining the periodic cycle of updating.

      The main CSM-ID in each entry (if provided) should be the CSM-ID of the CSM remitting the
      information. This enables the receiving CSMs to easily integrate the contents of the CSM reach
      tables it receives in their own CSM reach table, because it makes the reach information in each
      entry completely self-contained. This format can be used irrespective of whether the two parties
      are two CSMs, two payment service providers, or one of each.



5.7   Validity dates

      Due to the length of processing periods for payments made under the SEPA schemes, (maximum 3
      days for the CT and 14 days for the DD), routing table updates could occur while a payment is
      being processed. A participant remitting a payment should properly set and route it considering the
      settlement date of the payment and the CSM table information valid at the moment of the
      settlement date: Validity date in the CSM table = Exchange date. The implication is that the
      CSM table should manage the “current” valid information as well as the “future” valid information.

      The R-message should be routed depending on the CSM table valid at the moment of the original
      settlement date unless it is no longer possible for the remitter participant to remit the message
      through the original path.




      Page 25 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




5.8   Logical structure of the CSM table

      The “physical file” is the file physically sent to the counterparty over the network and file can
      contain one or more logical files. The data will be formatted in a “logical file” composed by:

         one header record

         one or more detail records containing the single evidence of updates

      Logical files are homogenous per scheme- product (e.g. in one logical file the CT updates, in one
      other the DD updates) and can contain creation, cancellation and variations.

      Data               Description                          Format       Sha Notes
                                                                           red
                                                                           data
      Participant code   Identification of payment service BIC             Y
                         provider that can be reached      code
      Participant name                                                     Y

      Participant                                                          Y
      address
      Scheme Product     Specific product for which this                   Y
                         entry is applicable
      Scheme Product     Version of the scheme supported                   Y   Can be multiple
      version
      CSMid              Identification of the CSM            Bic          Y
                         providing the remitting option       code (?)
                         for this reach
      Preferred CSM      It indicates if the CSM is the                    Y
      indicator          preferred CSM at the receiving
                         side
      Start date         starting validity date from which                 Y
                         the information is considered
                         valid
      End date           Last date the information is still                Y   Can be empty
                         considered valid
      AOS                Additional optional services                      Y
                         supported
      Cut-off time       Time at which the latest
                         payments for this destination
                         BIC can be remitted
      PriceIndicator     Price or price markup for this       Currency +   Y   optional
                         destination BIC                      Amount




      Page 26 of 148                                                           Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




 5.9    Applications of the reach table messages

        This paragraph describes the intended uses of the EACHA reach table messages, including the
        principles of the self organising routing mechanism between CSMs.

        Three different uses of the same message structure are described, including the differences
        between how the tables can be filled depending on which usage it is intended for.


5.9.1   Different uses of the routing table

        The different uses of the table are explained using a standard example configuration. In this
        diagram, CSM1 is the CSM the examples are explained for. CSM1 has two payments service
        providers that are connected directly, Payments service provider1 and Payments service provider2.
        This CSM is connected to two other CSMs, CMS2 and CSM3. CSM2 has two directly connected
        payments service providers, which are Payments service provider3 and Payments service
        provider4.


                                                                Information
                                                                  Service               Directory
                                                                Provider(s)



                                                          Route Table usage 3:
                                                   Communicate connected participants
                                                 of a CSM to information service providers



                                                                                         Route Table usage 2:
                             Route Table usage 2:
                   CSM2                                           CSM1                Communicate available reach      CSM3
                          Communicate available reach
                                                                                          to connected CSMs
                              to connected CSMs



                                                          Route Table usage 1:
                                                        Communicate offered reach
                                                           to connected banks




           Bank3          Bank4                         Bank1                 Bank2




        The routing table as defined in this document has 3 different purposes:

        1 communicating a CSMs complete reach to its customers (payments service providers)

        2 communicating reach between CSMs to establish possible routes for transactions

        3 communicating the direct reach of a CSM to information service providers for incorporation in a
          directory

        In all 3 cases, the definition (structure) of the table is the same, the content (the actual entries and
        their data elements) may be (and probably usually will be) different. PrivateData, as defined in the
        table, is always intended for internal use by the CSM and is never sent out in the table for usage 1,
        2 or 3.

        For each of the different uses, a brief description of the usage and the consequences for the
        content of the routing table is given in the next sections.




        Page 27 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




5.9.2   Usage 1 : communicating reach to customers

        When communicating its reach to its (sending) customers, a CSM will create a table according to
        the standard format. The contents of this table will be made up of entries for all participants the
        CSM can offer reach to, both directly and indirectly, including reach through for example another
        CSM. It is up to the CSM how many entries are given for the same participant. If the CSM has two
        different routes to a participant, with for example different supported AOSs and cutoff times, the
        CSM can choose to send these options as separate entries to its customer, or send the customer a
        consolidated version, showing a combined set of AOSs and one cutoff time for a certain participant.
        The amount of information the customer needs, depends on who decides upon the routing to be
        used for a transaction, the CSM or the sending payments service provider itself. Therefore, the
        CSM needs to dynamically generate these tables for its customers, based on its internal routing
        database.


5.9.3   Usage 2 : communicating available reach to connected CSMs

        Every CSM that is interlinked with another CSM using EACHA standards, will communicate the
        reach it offers to its connected CSMs using the ReachTable format defined in this document.

        CSM will normally fill this table with at least their own connected participants. It is every CSM's
        choice (possibly depending on its contracts with its linked CSMs) what indirect reach (that is,
        participants that can be reached through another CSM) it wants to offer to every CSM.

        In the example diagram, CSM1 must decide wether or not it can offer reach to payments service
        providers 3 and 4 (reachable through CSM2, with which it is linked) to CSM3. Depending on this
        decision, the reach to the indirectly reachable payments service providers is added to the
        ReachTable it sends to CSM3, or it is left out of the table. This also means that the reach table that
        is sent to the connected CSMs can be different for every CSM. This self-organising mechanism
        between CSMs is described in more detail in the next chapter.

        By combining its own connected participants, the received ReachTables and its reach through other
        channels (e.g. CSMs that do not adhere to EACHA standards for interoperability), a CSM can build
        an internal table with the reach it has to offer to customers.


5.9.4   Usage 3 : communicating connected participants to information service providers

        Once interoperable links between CSMs have developed sufficiently, it may become useful to create
        a “reachability directory” to take advantage of the multiple routes available to CSMs and payments
        service providers for routing payments. Analogous to the reach table documenting which payments
        service providers are reachable via a given CSM, the reachability directory would document the
        reachability end point information available for reaching a given payments service provider.

        The nature of the information held in such a reachability directory may overlap partially with the
        information held in the BIC/IBAN directory from information service providers such as SWIFT.
        Extending the BIC/IBAN directory may therefore to be practical for the purpose of creating general
        routing provisions. This may be discussed with SWIFT and other information service providers if the
        need for such a directory becomes evident. NB At present SWIFT is working on the "SWIFT SEPA
        routing table" for this purpose.

        To allow information service providers to maintain a central directory of participants, and the CSMs
        they are connected to, CSMs will send only their own connected participants in a ReachTable. The
        information that will be provided in the standard table format will be the minimum information that
        is needed to convey where participants can be reached. No information on inter-CSM routing, cost
        or quality of service (QoS) will be provided for this purpose.




        Page 28 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




        NB1 It is up to the individual CSM, based on the arrangements made with their community of
        payments service providers to provide the information to SWIFT and/or other information service
        providers

        NB2 The reachability directory is not essential for the CSMs to realise interoperability, but it does
        explain to payments service providers and CSMs what routes are available to them and the
        preferences that a receiving payments service provider might have.


5.9.5   Self Organising Routing Mechanism for interlinked CSM's

        A working routing mechanism that operates by self-organisation (there is no central coordination or
        centrally managed directory, every CSM determines its reach and possible routes by combining all
        received routing tables from other CMSs into a consolidated internal table with its own participants)
        needs to have strictly defined messages (where not only the type but also the meaning of the data
        elements has to be strictly defined) and well-defined algorithms for working with this table. When
        these two definitions are established and implemented by everyone, every CSM can be sure that
        the routing tables it receives from other CSMs have a specified meaning, and are derived in the
        same way.

        The self-organising mechanism works on the basis of ReachTables being sent between CSM's. By
        combining these tables, every CSM knows what inter-CSM reach it has to participants of other
        CSMs (and through which CSM).

        By combining this with its own connected participants, and the reach it has through other channels
        (e.g. CSMs that do not adhere to EACHA standards), a CSM has a complete list of the routes it has
        to all reachable participants.


5.9.6   Processing of ReachTables by CSMs

        This chapter describes the steps that should be performed by a CSM using the ReachTables. This
        description assumes an internal CSM routing table is being maintained as a result of all the reach
        information that is received.


5.9.7   Preparing outgoing table for customers

           Take internal routing table, consisting of all participants connected to CSM itself, combined with
            the processed ReachTables from other CSMs, and the reach through other options.

           If necessary for customer, consolidate multiple entries for one participant to one entry according
            to guidelines defined by the CSM itself

           For every remaining entry, set conditions to customer e.g. cutoff, supported AOSs, etc.

           Remove private data elements from ReachEntry elements

           Add GroupHeader (GrpHdr) with correct information (creation date & time amongst others)




        Page 29 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




5.9.8   Preparing outgoing table for other CSMs

           Take internal routing table, consisting of participants connected to CSM itself, and the processed
            ReachEntries from other CSMs, if these can be offered to other CSMs (may depend on
            contractual conditions, or business choices).

           For every remaining entry, set conditions to CSM e.g. cutoff, supported AOSs, etc.

           Remove private data elements from ReachEntry elements

           Add GroupHeader (GrpHdr) with correct information (creation date & time amongst others)


5.9.9   Preparing outgoing table for SWIFT

           Take internal routing table, select only participants connected to CSM itself

           Fill minimum necessary attributes (cut-off times,…)

           Remove private data elements from ReachEntry elements

           Add GroupHeader (GrpHdr) with correct information (creation date & time amongst others)


5.9.10 Distributing reach tables to other CSMs

        At an agreed cut off time, the CSMs exchange updates to their own reach tables pertaining to their
        customers (creation, cancellation, variation). They must also agree on a time to activate such
        changes. The CSM reach table updates will be exchanged on the basis of common agreed
        standards. Participating CSMs may extend the functionality of the updates on a bilateral basis. In
        order to simplify the CSM reach table updating process the exchanged physical file should contain
        all the updates pertaining the periodic cycle of updating.

        The CSM reach table updates will be exchanged by means of a File Transfer System bilaterally
        agreed between the parties.

        Each CSM has to be able to supply, on request of a counterparty CSM, a full and up-to-date version
        of its CSM reach table, including all scheduled updates.

        In the normal situation, only updates are distributed between CSMs. In case of problems (an
        update cannot be processed or a CSM might not have received a certain update), the normal
        procedure should be to first request a full table update, if there are then still problems then
        escalate to solve this problem.

        There should be a way of signalling errors or other problems in processing a received table to the
        sending party of the routing table, this is not yet defined. A confirmation reply to this table
        (containing details of any errors) would be a possible mechanism to tackle this. It is proposed to
        find a solution for this during the proper ISO standardisation of routing messages, and solve this
        problem by using the telephone in case of problems while using the temporary EACHA solution
        described in this document.




        Page 30 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
       EACHA Interoperability Framework (v3.02)




5.9.11 Processing received tables from other CSMs

          Check for structural integrity, if there are XML structure problems, do not process the table.

          Check if the table is a full table or an update.

          If the table is a full table, remove all entries for this CSM, and add all entries from this table.

          Process differently according to ReachEntry status:

          Existing (normally, an 'existing' entry would only occur when a full table update is requested)

              Find the original entry for this route in the internal routing table
              If found, check if identical. If not identical, replace with values received in full table.
              If not found, it is up to the CSM to add a ReachEntry for this route to its internal table. This
               should be free for the CSM to decide. If the CSM doesn‟t add this route, he may still get
               updates on this same element from the other CSM.

          New

              Find all routes to the participant in this entry in the internal table
              As an optional element: Check if the received ReachEntry to this participant is 'better' in any
               way, only then add it to the internal consolidated table. Some CSMs might want to decide
               this on the fly, during the processing rather than when working with the tables

          Changed

              Find the original entry for this route in the internal routing table
              Update the information

          Deleted

              Find the original entry for this route in the internal routing table

          Delete this route entry


5.9.12 Using consolidated table

       How to use a consolidated (internal) routing table is up to the CSM. There are no firm rules on how
       to determine routing; this table only provides information on possible routes. Which elements from
       this table are sent to other outside parties (e.g. customers) is completely left at the CSM's
       discretion.



 5.10 Reach Table Definition: List of data Elements

       In this paragraph, the actual reach table is defined and described. This definition uses existing data
       elements from ISO200222 where possible, to stay as close to ISO20022 (UNIFI) as possible. This
       is, however, not an ISO20022 message, as it is not defined by ISO. This definition is an
       intermediate EACHA format to be used until there is an ISO20022 message for the exchange of
       routing or reach information.

       For every ReachEntry, the table contains shared data (to be shared with CSM and customers), and
       private data (for use within the CSM only).

       For every data element in the routing table message, the following is defined:

          Index : numbering of the element for reference purposes

          Mult : the multiplicity of the element, i.e. how often can it occur within its parent element

          ISO: Y if is this an element already defined in the ISO20022 repository, N otherwise




       Page 31 of 148                                                           Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




   Explanation: describes the business meaning of the data element, but sometimes
    also contains usage rules for the element.

Index Mult       Element            ISO     Explanation
1.0     [1..1] +GrpHdr              N       Header
                                            Type : GroupHeader
1.1     [1..1] ++MsgId              Y       Usage rule : only 'ReachTable' is allowed
                                            Type : Max35Text
1.2     [1..1] ++CreDtTm            Y       Creation Date & Time for this file
                                            Type : ISODateTime
1.3     [1..1] ++PtyId              Y       This identifies the party (CSM) sending the table,
                                            providing reach.
                                            Type : PartyIdentificationChoice1
1.4     {Or    +++BICOrBEI          Y       BIC for CSM
        [1..1]                              Type : AnyBICIdentifier
                                            (See ISO for definition of subelements)
1.5     Or    +++ PrtryId           Y       Proprietary ID of CSM
        [1…1]                               Type : GenericIdentification1
                                            (See ISO for definition of subelements)
1.6     Or}    +++ NmAndAdr         Y       Name and Address of CSM
        [1..1]                              Type : NameAndAddress2
                                            Usage rule : Not to be used
                                            (See ISO for definition of subelements)
1.9     [1..1] ++FullTable          N       1 (or true) to indicate if a full table is being
                                            provided or 0 (or false) to indicate if a table update
                                            is being provided.
                                            Type: xs:boolean
2.0     [1..n] +RchEntry            N       A ReachEntry is present for every participant that
                                            can be reached through this CSM
                                            Type : ReachEntry
2.1     [1..1] ++Status             N       Status of this reach entry.
                                            Usage rule : only „existing‟ 'new' or 'changed‟ or
                                            'deleted' is allowed.
                                            For full table, only 'existing' is allowed.
                                            Type : Max16Text
2.2     [1..1] ++Validity           N       Period of validity of this reach entry.
                                            Type : DateTimePeriod
2.3     [1..1] +++FromDtTm          Y       Valid from: date & time
                                            Default from start of day (00:00:00 CET)
                                            Type: ISODateTime
2.4     [0..1] +++ToDtTm            Y       Valid to : date & time
                                            Default until end of day (00:00:00 CET)
                                            Type: ISODateTime
2.5     [1..1] ++Participant        N       The identification of the participant of this
                                            ReachEntry. This is a final destination for
                                            transactions that can be reached, for CT this is the
                                            Creditor Agent.
                                            Type : FinancialInstitutionIdentification




Page 32 of 148                                                      Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




Index Mult       Element         ISO       Explanation
2.7    [1..1] +++BIC             Y         Type : AnyBICIdentifier
2.8    [1..1] +++NmAndAddr       Y         Type : NameAndAddress2
                                           (See ISO for definition of subelements)
2.15   [1..1] ++Product          N         Type : ProductIdentifier
2.16   [1..1] +++ProductName     N         Usage rule : only 'SCT' or 'SDD' is allowed
                                           Type : Max16Text
2.17   [1..1] +++Vrsn            Y         Version of Rulebook of the product that is
                                           supported
                                           Type : xs:decimal
2.18   [0..1] ++CSM              N         Identifies the CSM that provides this reach
                                           Usage rule : Repeat CSM info from <GrpHdr>
                                           Type : CSMIdentifier
2.19   [1..1] +++PtyId           Y         Type : PartyIdentificationChoice1
2.21   {Or    ++++BICOrBEI       Y         BIC for CSM
       [1..1]                              Type : AnyBICIdentifier
2.22   Or    ++++PrtryId         Y         Proprietary ID of CSM
       [1…1]                               Type : GenericIdentification1
                                           (See ISO for definition of elements)
2.23   Or}    ++++NmAndAdr       Y         Name and Address of CSM
       [1..1]                              Type : NameAndAddress2
                                           Usage rule : Not to be used
                                           (See ISO for definition of elements)
2.26   [1..1] +++PreferredIndicat N        Contains 1= true or 0= false
              or                           Indicates if this CSM offers a route to the preferred
                                           CSM at the receiving side.
                                           Type : xs:boolean
2.27   [1..1] ++CutOff           N         Type : CutOffType
2.28   [1..1] +++Time            N         The time at which the latest payments for this
                                           destination BIC can be remitted
                                           Type : ISOTime
2.30   [1..1] +++RelDays         N         Number of days relative to exchange day (>=0)
                                           Type : xs:nonNegativeInteger
2.31   [0..1] +++SupportedAos    N         A list of (to be determined) Additional Optional
                                           Services supported by (this route to) the
                                           participant.
                                           Type : AosList
2.32   [1..n] ++++AOSId          N         Identifies an AOS. Requires unique IDs for AOSs,
                                           at least within the CSM.
                                           Type : xs:decimal
2.33   [0..1] ++PriceIndicator   Y         Indicates a price or price markup on the reach to
                                           this destination.
                                           Type : CurrencyAndAmount




Page 33 of 148                                                     Doc ref: EACHA 2007-3.02 Interoperability
      EACHA Interoperability Framework (v3.02)




6     Annex IV: SEPA Core Credit Transfer Messages EACHA guidelines


      VERSION 1.0 23 JULY 2007

      This Annex defines the UNIFI ISO 20022 XML messages that CSMs will exchange with each other
      and with banks for the processing of SEPA Core Credit Transfers.

      Paragraph 6.6 summarises the various messages.



6.1   Introduction

      This document defines the ISO 20022 XML messages that CSMs will exchange for SEPA Core Credit
      Transfer processing. SEPA Core processing comprises the basic services for processing, clearing
      and settlement of incoming and outgoing Credit Transfers, compliant with the SEPA CT Rulebook.

      The messages in this document are based on the Implementation Guidelines: the EPC document
      'SEPA Credit Transfer Scheme Implementation Guidelines‟ Version 2.3 Approved, issued 19 June
      2007. Columns 1 to 4 in the message descriptions below have been copied from the
      Implementation Guidelines.

      In the Implementation Guidelines, and in this EACHA document at hand, the SEPA Core message
      elements have been marked yellow, the AOS-related message elements are white. SEPA Core
      processing means the processing and forwarding of the yellow elements, not the white ones. There
      may be parties in the payment chain that support only SEPA Core, so sending parties should be
      aware that only the yellow elements may reach the (ultimate) receiving party.



6.2   Messages context and scope

      This chapter shows the various messages, their context and scope.

      Figure 1. Simplified flow for Credit Transfer

                                                                                                                             Everything in blue is out of
                                                                                                                             the scope of this document
                                                                           TARGET-2


                                                    17                                                            17




                                                                 17   17              17          17

                  Bank 1                                                                                                                        Bank 2
                (debit side)                                                                                                                 (credit side)

                                      1                                                                                             3
                       10
                                  5       4                                  2                                                          8

                             15                                              6                                                          11
                                                                             7
                        16                                   CSM 1               9                     CSM 2                                 12
                                                                                 13
                                                                                 14

      Credit Transfer                                                            Credit Transfer Return
      1 Bank – CSM Credit Transfer (pacs.008.001.01)                             8 Bank – CSM CT Return (pacs.004.001.01)
      2 Inter CSM Credit Transfer (pacs.008.001.01)                              9 Inter CSM CT Return (pacs.004.001.01)
      3 CSM – Bank Credit Transfer (pacs.008.001.01)                             10 CSM – Bank CT Return (pacs.004.001.01)
      4 CSM – Bank CT Reject (pacs.002.001.02)                                   11 CSM – Bank CT Return Reject (pacs.002.001.02)
      5 CSM – Bank CT Positive Status report (pacs.002.001.02)                   12 CSM – Bank CT Return Positive Status Report (pacs.002.001.02)
      6 Inter CSM CT Reject (pacs.002.001.02)                                    13 Inter CSM CT Return Reject (pacs.002.001.02)
      7 Inter CSM CT Positive Status Report (pacs.002.001.02)                    14 Inter CSM CT Return Positive Status Report (pacs.002.001.02)
                                                                                 Credit Transfer Cancellation
                                                                                 15 Bank – CSM Cancellation (pacs.006.001.01)
                                                                                 16 CSM – Bank Cancellation Reject (pacs.002.001.02)
                                                                                 17 Settlement messages



      For Bank 1 and Bank 2 it makes no difference whether there are 1, 2 or more CSMs in the chain.




      Page 34 of 148                                                                                           Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




Figure 2 shows the scenario with only one CSM. The messages are the same as in Figure 1.
Evidently, the inter CSM messages are absent.

For this scenario the terms 'CSM 1' and 'CSM 2' in the message descriptions can be replaced with
'CSM'.

Figure 2. Simplified flow for Credit Transfer

                                                                                                              Everything in blue is out of
                                                                                                              the scope of this document
                                                           TARGET-2


                                                17                                                 17




                                                           17         17

            Bank 1                                                                                                             Bank 2
          (debit side)                                                                                                      (credit side)


                                            1                                                           3
                                           4                                                             8
                                           5
                                                                                                        11
                                           10
                                           15                   CSM
                                                                                                        12
                                           16


Credit Transfer                                                   Credit Transfer Return
1 Bank – CSM Credit Transfer (pacs.008.001.01)                    8 Bank – CSM CT Return (pacs.004.001.01)
2 Inter CSM Credit Transfer (pacs.008.001.01)                     9 Inter CSM CT Return (pacs.004.001.01)
3 CSM – Bank Credit Transfer (pacs.008.001.01)                    10 CSM – Bank CT Return (pacs.004.001.01)
4 CSM – Bank CT Reject (pacs.002.001.02)                          11 CSM – Bank CT Return Reject (pacs.002.001.02)
5 CSM – Bank CT Positive Status report (pacs.002.001.02)          12 CSM – Bank CT Return Positive Status Report (pacs.002.001.02)
6 Inter CSM CT Reject (pacs.002.001.02)                           13 Inter CSM CT Return Reject (pacs.002.001.02)
7 Inter CSM CT Positive Status Report (pacs.002.001.02)           14 Inter CSM CT Return Positive Status Report (pacs.002.001.02)
                                                                  Credit Transfer Cancellation
                                                                  15 Bank – CSM Cancellation (pacs.006.001.01)
                                                                  16 CSM – Bank Cancellation Reject (pacs.002.001.02)
                                                                  17 Settlement messages




This document describes the following messages:

1.       Bank - CSM Credit Transfer (pacs.008.001.01) (= CT)
         The CT transports the payment instruction from the bank to the CSM.

2.       Inter CSM Credit Transfer (pacs.008.001.01)
         The CT transports the payment instruction from one CSM to the next CSM in the chain.

3.       CSM - Bank Credit Transfer (pacs.008.001.01)
         The CT transports the payment, after clearing and settlement, from the CSM to the bank.

4.       CSM - Bank CT Reject (pacs.002.001.02)
         The CT Reject is used when a credit transfer is not accepted for normal execution, before
         interbank settlement.

5.       CSM - Bank CT Positive Status Report (pacs.002.001.02)
         The CT Positive Status Report is used to inform the bank about the successful receipt and
         validation or the successful settlement of the Credit Transfer. The bank can use it to
         reconcile the Credit Transfer with settlement messages from TARGET-2.
         This message is not part of the SEPA CT Rulebook, it is an optional service.

6.       Inter CSM CT Reject (pacs.002.001.02)
         The CT Reject is used when a credit transfer is not accepted for normal execution because of
         technical reasons.




Page 35 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




7.    Inter CSM CT Positive Status Report (pacs.002.001.02)
      The CT Positive Status Report is used to inform the CSM about the successful receipt and
      validation or the successful settlement of the Credit Transfer. This message is not part of the
      SEPA CT Rulebook, it is an optional service.

8.    Bank - CSM CT Return (pacs.004.001.01)
      The CT Return is used when a credit transfer is diverted from normal execution after
      interbank settlement. It is sent by the bank to the CSM for a credit transfer that cannot be
      executed for valid reasons such as wrong account number or account closed with the
      consequence that the creditor account cannot be credited on the basis of the information
      contained in the original credit transfer message.

9.    Inter CSM CT Return (pacs.004.001.01)
      The inter CSM CT Return is used when a credit transfer is diverted from normal execution
      after interbank settlement. It is sent by a CSM to the next CSM in the chain for a credit
      transfer that cannot be executed for valid reasons such as wrong account number or account
      closed with the consequence that the creditor account cannot be credited on the basis of the
      information contained in the original credit transfer message.

10.   CSM - Bank CT Return (pacs.004.001.01)
      The CT Return is used to transport the CT Return, after clearing and settlement, from the
      CSM to the bank.

11.   CSM - Bank CT Return Reject (pacs.002.001.02)
      The CT Return Reject is used when a CT Return is not accepted for normal execution.

12.   CSM - Bank CT Return Positive Status Report (pacs.002.001.02)
      The CT Return Positive Status Report is used to inform the bank about the successful receipt
      and validation or the successful settlement of the CT Return. The bank can use it to reconcile
      the CT Return with settlement messages from TARGET-2. This message is not part of the
      SEPA CT Rulebook, it is an optional service.

13.   Inter CSM CT Return Reject (pacs.002.001.02)
      The Inter CSM CT Return Reject is used when a CT Return is not accepted for normal
      execution because of technical reasons.

14.   Inter CSM CT Return Positive Status Report (pacs.002.001.02)
      The CT Return Positive Status Report is used to inform the CSM about the successful receipt
      and validation or the successful settlement of the CT Return. This message is not part of the
      SEPA CT Rulebook, it is an optional service.

15.   Bank - CSM CT Cancellation (pacs.006.001.01)
      The CT Cancellation is used to cancel a Credit Transfer before settlement. This message is
      not part of the SEPA CT Rulebook, it is an optional service.

16.   CSM - Bank CT Cancellation reject (pacs.002.001.02)
      Not yet described, to be added in a next version of this document.

All the above messages cater for both bulk transactions and single transactions.




Page 36 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




 6.3    Other issues


6.3.1   Instructing Agent and Instructed Agent

        In this document the following basic assumptions have been made:

           An 'agent' is always a bank. A CSM can not be Instructing Agent or Instructed Agent.

           A 'party' can have any role in the payment chain. A CSM can be a party. A CSM can be an
            instructing party or an instructed party, but not Instructing Agent or Instructed Agent.

        In a message from a bank to a CSM Instructing Agent contains the (BIC of the) sending bank.
        Instructing Agent is forwarded in the chain, for example:

           an Instructing Agent in a CT from Bank 1 to CSM 1 is forwarded to CSM 2 and Bank 2;

           an Instructing Agent in a CT Return from Bank 2 to CSM 2 is forwarded to CSM 1 and Bank 1.

        In a message from a bank to a CSM Instructed Agent is not allowed and not forwarded in the
        chain. The CSMs don't need Instructed Agent for their processing (routing, clearing, settlement
        etcetera). In a message from a CSM to a bank Instructed Agent contains the (BIC of the) receiving
        bank.


6.3.2   Positive Status Report

        As mentioned in the previous chapter, the Positive Status Report message (inter CSM and CSM–
        Bank) is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA Core
        message.

        It is a pacs.002.001.02. The (major) differences with the Reject message (also a pacs.002.001.02,
        but SEPA Core) are marked in bold in the Positive Status Report message descriptions below.
        Where possible, the Reject SEPA Core Requirements have been followed. These requirements are
        shown (although striked out) in the Positive Status Report message descriptions for background
        information.

        The Positive Status Report conflicts with the ISO 20022 specifications on two points:

           element 2.14 Additional Status Reason Information should not be present if 2.8 Group Status =
            „ACSC‟ or „PART‟, see the ISO StatusReasonInformationRule;

           if the elements 2.16 Detailed Number Of Transactions and 2.17 Detailed Status are present,
            then the transactions (3.0) should also be present, see the ISO description of element 2.15.

        Despite these conflicts, the Positive Status Report passes the ISO pacs.002.001.02 xsd schema.


6.3.3   Settlement reference

        Note that the Credit Transfer and the CT Return each contain a white (not yellow!) message
        element, from CSM to CSM and from CSM to Bank:

           element 2.49 Instruction For Next Agent in the Credit Transfer;

           element 3.24 Additional Return Reason Information in the CT Return.

        Both these elements contain the settlement reference (alphanumeric, max. 16 positions).
        Settlement reference is also provided in the settlement messages from TARGET-2. It enables the
        receiving CSM/bank to relate the transaction to the settlement in TARGET-2. It is meant for the
        receiving CSM/bank, it should not be forwarded onwards.




        Page 37 of 148                                                        Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




6.3.4   Conversion of reason codes

        R-transactions that third parties send to a CSM may contain (AOS) reason codes that are not
        allowed in Core messages. The CSM converts such codes into codes that are allowed in Core
        messages before forwarding the R-transactions to CSMs/banks that wish to receive only Core
        messages. See the message descriptions for the details.


6.3.5   Checks on incoming messages

        The message descriptions below show the checks by the CSM on incoming messages. These checks
        are optional, not mandatory; every CSM is free to execute these checks or not. If executed then it
        should be done as described: check, error code, action. If not executed, the CSM must take into
        account that, when forwarding a message/transaction containing incorrect data, this
        message/transaction may be rejected by the receiving party.

        CSMs are free to make bilateral or multilateral agreements on which checks are to be executed by
        which parties.



 6.4    Explanatory notes to the message descriptions

        The message descriptions should be read in conjunction with the Implementation Guidelines and
        the ISO 20022 XML message standards (document 'UNIFI (ISO 20022) Message Definition Report,
        Payments Standards - Clearing and Settlement').

        Columns 1 to 4 in the message descriptions have been copied from the Implementation Guidelines.

        The first column shows the index number of the message element in the ISO 20022 message
        standard, for reference purposes.

        The second column shows whether the message element is mandatory or optional and how many
        times it occurs (multiplicity).

        Note that if a higher level message element is mandatory and its lower level message elements
        (components) are optional, then at least one lower level message element must be present.

        An example:

        [1..1] + Group

        [0..1] ++ Sub Group 1

        [0..1] ++ Sub Group 2

        In this example at least 'Sub Group 1' or 'Sub Group 2' must be present.

        And, reversely, if a lower level message element is mandatory but its higher level message
        element is optional, then the lower level message element must be present if and only if the higher
        level message element is present.

        [0..1] + Group

        [1..1] ++ Sub Group 1

        In this example 'Sub Group 1' must be present, but only if 'Group' is present.

        In the third column the message element is given, and its level is indicated by 1 or more '+' signs.

        The fourth, 'SEPA Core Requirements' column, shows the SEPA Usage rules, Format rules, values
        and corresponding Rulebook attributes.

        The fifth column shows comments and additional specifications.




        Page 38 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




The sixth column shows the checks done by the CSM (on ISO rules, SEPA rules and additional
specifications) that are not covered by the ISO xsd schema.

The seventh and eighth columns show the error codes that the CSM assigns and the actions it
takes.

These checks are optional, not mandatory, see „Checks on incoming messages‟.

Also, CSMs are free to develop their own xsd schemas and to incorporate the checks from the
„Checks‟ column into their xsd schemas, as long as the working of the checks remains the same.




Page 39 of 148                                                    Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




 6.5     Message descriptions


6.5.1    Bank - CSM Credit Transfer (pacs.008.001.01)

         From Bank 1 to CSM 1

         If the message does not conform to the ISO xsd schema the whole message will be rejected with
         Error Code 'MD03'.



 Index   Mult.    Message element      SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                       Requirements              ditional specifications

 1.0     [1..1]   +Group Header

 1.1     [1..1]   ++ Message                                     Assigned by Bank 1,       The combination of     MD03         reject the
                  Identification                                 must be unique over       Instructing Agent and (duplicate)   message
                                                                 time for this message     Message Identification
                                                                 type (CT).                must be unique, for
                                                                                           this message type
                                                                                           (CT).

 1.2     [1..1]   ++ Creation Date                               The date and time the Must be a valid date       MD03         reject the
                  Time                                           message has been      and time                                message
                                                                 created

 1.3     [0..1]   ++ Batch Booking                               Only used for additio-
                                                                 nal optional services

 1.4     [1..1]   ++ Number Of                                   A maximum of 100000 Must be  100000             MD03         reject the
                  Transactions                                   transactions per                                              message
                                                                 message.
                                                                                     Must equal the               MD03         reject the
                                                                                     number of                                 message
                                                                                     transactions in the
                                                                                     message

 1.5     [0..1]   ++ Control Sum                                 Only used for additio-
                                                                 nal optional services

 1.6     [0..1]   ++ Total Interbank   Mandatory                                           Must equal the sum of MD03          reject the
                  Settlement Amount    Usage rule:                                         all occurrences of                  message
                                       Only „EUR‟ is allowed.                              Credit Transfer Trans-
                                                                                           action Information /
                                       Usage rule:
                                                                                           Interbank Settlement
                                       Amount must be 0.01
                                                                                           Amount
                                       or more and
                                       999999999999999.99                                  Currency Code must     MD03         reject the
                                       or less.                                            be "EUR"                            message
                                       Format rule:
                                       The fractional part has                             Amount must be ≥       MD03         reject the
                                       a maximum of two                                    0.01                                message
                                       digits.
                                                                                           Amount must be ≤   MD03             reject the
                                                                                           999999999999999.99                  message

                                                                                           Maximum 2 fraction     MD03         reject the
                                                                                           digits                              message

 1.7     [0..1]   ++ Interbank         Mandatory                 The requested             Must be present        MD03         reject the
                  Settlement Date      (AT-42 Settlement         Settlement Date.                                              message
                                       Date of the Credit        If it is a date in the
                                       Transfer)                 (near) past, CSM 1
                                                                 will execute as soon
                                                                 as possible.
                                                                 If it is not a Target
                                                                 day, CSM 1 will
                                                                 execute on the first
                                                                 Target day after this
                                                                 date.




         Page 40 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error Code   Action
                                         Requirements               ditional specifications

                                                                    (As an alternative        Must be a valid date     MD03         reject the
                                                                    CSM 1 may choose to                                             message
                                                                    reject a requested
                                                                    Settlement Date that      Must not be too far in   TM01         reject the
                                                                    is in the past and/or     the past:                             message
                                                                    not a Target day.)        current date - 2
                                                                                              Target days ≤
                                                                                              requested Settlement
                                                                                              Date

                                                                                              Must not be too far in   MD03         reject the
                                                                                              the future:                           message
                                                                                              requested Settlement
                                                                                              Date ≤ current date +
                                                                                              x Target days.
                                                                                              'x' is to be agreed
                                                                                              between Bank 1 and
                                                                                              CSM 1

1.8     [1..1]   ++ Settlement
                 Information

1.9     [1..1]   +++ Settlement          Usage rule:                Only the value 'CLRG'     Must contain the value MD03           reject the
                 Method                  Only CLRG, INGA and        is allowed.               'CLRG'.                               message
                                         INDA are allowed.

1.10    [0..1]   +++ Settlement          Usage rule:                Absent.               Must not be present          MD03         reject the
                 Account                 Only 'Identification' is   (ISO: If Settlement                                             message
                                         allowed.                   Method = 'CLRG', then
                                                                    Settlement Account is
                                                                    not allowed.)

1.11    [0..1]   +++ Clearing System                                Present.              Must be Present              MD03         reject the
                                                                    (ISO: If Settlement                                             message
                                                                    Method = 'CLRG', then
                                                                    Clearing System must
                                                                    be present.)
                                                                    Identifies Clearing
                                                                    System of CSM 1

1.12    {Or      ++++ Clearing                                      Used when Clearing        If present, it must    MD03           reject the
                 System Identification                              System Identification     contain the valid                     message
                                                                    exists for the Clearing   UNIFI code identifying
                                                                    System of CSM 1 in        CSM 1
                                                                    the UNIFI ISO 20022
                                                                    code list

1.13    Or}      ++++ Proprietary                                   Used when no             If present, it must       MD03         reject the
                                                                    Clearing System          contain the valid code                 message
                                                                    Identification exists    as specified by CSM 1
                                                                    for the Clearing
                                                                    System of CSM 1 in
                                                                    UNIFI ISO 20022 code
                                                                    list. Value is specified
                                                                    by CSM 1.

1.14    [0..1]   +++ Instructing                                    Absent. (ISO: If
                 Reimbursement Agent                                Settlement Method =
                                                                    'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.15    [0..1]   +++ Instructing                                    Absent. (ISO: If
                 Reimbursement Agent                                Settlement Method =
                 Account                                            'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)




        Page 41 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                        Requirements              ditional specifications

1.16    [0..1]   +++ Instructed Reim-                             Absent. (ISO: If
                 bursement Agent                                  Settlement Method =
                                                                  'CLRG', then Reim-
                                                                  bursement agents are
                                                                  not allowed.)

1.17    [0..1]   +++ Instructed Reim-                             Absent. (ISO: If
                 bursement Agent                                  Settlement Method =
                 Account                                          'CLRG', then Reim-
                                                                  bursement agents are
                                                                  not allowed.)

1.18    [0..1]   +++ Third Reim-                                  Absent. (ISO: If
                 bursement Agent                                  Settlement Method =
                                                                  'CLRG', then Reim-
                                                                  bursement agents are
                                                                  not allowed.)

1.19    [0..1]   +++ Third Reim-                                  Absent. (ISO: If
                 bursement Agent                                  Settlement Method =
                 Account                                          'CLRG', then Reim-
                                                                  bursement agents are
                                                                  not allowed.)

1.20    [0..1]   ++ Payment Type                                  Absent.                   Must be absent.        MD03         reject the
                 Information                                      Present at transaction                                        message
                                                                  level (2.2).

1.21    [0..1]   +++ Instruction
                 Priority

1.22    {Or      +++ Service Level      Usage rule:
                                        Service Level must be
                                        present at either in
                                        „Group Header‟ or in
                                        „Credit Transfer Trans-
                                        action Information‟, to
                                        specify “SEPA”.

1.23    {Or      ++++ Code              (AT-40 Identification
                                        code of the Scheme)
                                        Usage rule:
                                        Only „SEPA‟ is allowed.

1.24    Or}      ++++ Proprietary

1.25    Or}      +++ Clearing Channel

1.26    [0..1]   +++ Local Instrument

1.29    [0..1]   +++ Category
                 Purpose

1.30    [0..1]   ++ Instructing Agent   Usage rule:               Present.                Must be present        MD03           reject the
                                        Only BIC is allowed.      Contains the BIC of                                           message
                                                                  the agent that
                                                                  instructs the next      Must contain BIC       MD03           reject the
                                                                  party in the chain to                                         message
                                                                  carry out the (set of)
                                                                  instruction(s): Bank 1. Must contain a BIC     RC01           reject the
                                                                                          from the BIC-directory                message

1.31    [0..1]   ++ Instructed Agent    Usage rule:               Absent.                   Must be absent         MD03         reject the
                                        Only BIC is allowed.                                                                    message




2.0     [1..n]   +Credit Transfer
                 Transaction
                 Information

2.1     [1..1]   ++ Payment
                 Identification




        Page 42 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                   Error Code    Action
                                        Requirements              ditional specifications

2.1     [0..1]   +++ Instruction                                  Assigned by Bank 1,       The combination of       MD03          reject the
                 Identification                                   must be unique over       Instructing Agent and    (duplicate)   transaction
                                                                  time for this message     Instruction
                                                                  type (CT).                Identification must be
                                                                                            unique, for this
                                                                                            message type (CT).

2.1     [1..1]   +++ End to End         (AT-41 Originator‟s       Assigned by the
                 Identification         Reference to the          debtor, is passed on
                                        Credit Transfer)          unaltered.
                                        Usage rule:
                                        A customer reference
                                        that must be passed
                                        on in the end-to-end
                                        chain. In the event
                                        that no reference was
                                        given, „NOTPROVIDED‟
                                        must be used.

2.1     [1..1]   +++ Transaction        (AT-43 Originator         Assigned by the       The combination of           MD03          reject the
                 Identification         Bank‟s Reference)         Debtor Agent, must be Debtor Agent and             (duplicate)   transaction
                                        Usage rule:               unique over time.     Transaction
                                        Must contain a                                  Identification must be
                                        reference that is                               unique, for this
                                        meaningful to the                               message type (CT).
                                        Originator‟s Bank and
                                        is unique over time.

2.2     [0..1]   ++ Payment Type                                  Present.
                 Information

2.3     [0..1]   +++ Instruction                                  Only used for additio-
                 Priority                                         nal optional services

2.4     {Or      +++ Service Level      Usage rule:             Present.
                                        „Service Level‟ must
                                        be present at either in
                                        „Group Header‟ or in
                                        „Credit Transfer Trans-
                                        action Information‟, to
                                        specify “SEPA”.

2.5     {Or      ++++ Code              (AT-40 Identification     Present.                  Must be present          MD03          reject the
                                        code of the Scheme)                                                                        transaction
                                        Usage rule:
                                                                                            Value must be "SEPA"     MD03          reject the
                                        Only „SEPA‟ is allowed.
                                                                                                                                   transaction

2.6     Or}      ++++ Proprietary

2.7     Or}      +++ Clearing Channel

2.8     [0..1]   +++ Local Instrument                             Only used for additio-
                                                                  nal optional services

2.11    [0..1]   +++ Category                                     Only used for additio-
                 Purpose                                          nal optional services

2.12    [1..1]   ++ Interbank           (AT-04 Amount of the                                Currency Code must       MD03          reject the
                 Settlement Amount      Credit Transfer in                                  be "EUR"                               transaction
                                        Euro)
                                                                                            Amount must be ≥         MD03          reject the
                                        Usage rule:
                                                                                            0.01                                   transaction
                                        Only „EUR‟ is allowed.
                                        Usage rule:                                         Amount must be ≤         MD03          reject the
                                        Amount must be 0.01                                 999999999.99                           transaction
                                        or more and
                                        999999999.99 or less.                               Maximum 2 fraction       MD03          reject the
                                        Format rule:                                        digits                                 transaction
                                        The fractional part has
                                        a maximum of two
                                        digits.




        Page 43 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                        Requirements              ditional specifications

2.13    [0..1]   ++ Interbank                                     Cannot be present
                 Settlement Date                                  because mandatory at
                                                                  group level

2.14    [0..1]   ++ Settlement Time                               Only used for additio-
                 Indication                                       nal optional services

2.17    [0..1]   ++ Settlement Time                               Only used for additio-
                 Request                                          nal optional services

2.19    [0..1]   ++ Acceptance Date                               Only used for additio-
                 and Time                                         nal optional services

2.20    [0..1]   ++ Pooling                                       Only used for additio-
                 Adjustment Date                                  nal optional services

2.21    [0..1]   ++ Instructed Amount                             Only used for additio-
                                                                  nal optional services

2.22    [0..1]   ++ Exchange Rate                                 Only used for additio-
                                                                  nal optional services

2.23    [1..1]   ++ Charge Bearer       Usage rule:                                         Code must be "SLEV"    MD03         reject the
                                        Only „SLEV‟ is allowed.                                                                 transaction

2.24    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

2.25    [0..1]   ++ Previous                                      Only used for additio-
                 Instructing Agent                                nal optional services

2.26    [0..1]   ++ Previous                                      Only used for additio-
                 Instructing Agent                                nal optional services
                 Account

2.27    [0..1]   ++ Instructing Agent   Usage rule:               Absent.                   Must be absent         MD03         reject the
                                        Only BIC is allowed.      (Present at group                                             transaction
                                                                  level: 1.30)

2.28    [0..1]   ++ Instructed Agent    Usage rule:               Absent.                   Must be absent         MD03         reject the
                                        Only BIC is allowed.                                                                    transaction

2.29    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 1                                          nal optional services

2.30    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 1 Account                                  nal optional services

2.31    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 2                                          nal optional services

2.32    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 2 Account                                  nal optional services

2.33    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 3                                          nal optional services

2.34    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 3 Account                                  nal optional services

2.35    [0..1]   ++ Ultimate Debtor     (AT-08 Originator       Will be considered for
                                        Reference Party)        inclusion in a future
                                        Usage rule:             version as AT-08
                                        Only „Name „or „Identi- Originator Reference
                                        fication‟ is allowed.   Party

2.35    [0..1]   +++ Name                                         Idem

2.35    [0..1]   +++ Postal Address                               Idem




        Page 44 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                       Requirements             ditional specifications

2.35    [0..1]   +++ Identification    Format rule:             Idem
                                       Either „Organisation
                                       Identification‟ or one
                                       occurrence of „Private
                                       Identification‟ may be
                                       present.

2.35    {Or      ++++ Organisation                              Idem
                 Identification

2.35    Or}      ++++ Private          Usage rule:              Idem
                 Identification        Only one occurrence
                                       of „Private
                                       Identification‟ is
                                       allowed.

2.35    [0..1]   +++ Country of                                 Idem
                 Residence

2.36    [0..1]   ++ Initiating Party                            Only used for additio-
                                                                nal optional services

2.37    [1..1]   ++ Debtor

2.37    [0..1]   +++ Name              Mandatory                                          Debtor name must be      MD03         reject the
                                       (AT-02 Name of the                                 present                               transaction
                                       Originator)

2.37    [0..1]   +++ Postal Address    (AT-03 Address of the
                                       Originator)

2.37    [0..5]   ++++ Address Line     Format rule:                                       If present, a            MD03         reject the
                                       Only two occurrences                               maximum of two                        transaction
                                       of „Address Line‟ are                              occurrences 'Address
                                       allowed.                                           Line' is allowed

2.37    [1..1]   ++++ Country                                                             Must be an ISO 3166      MD03         reject the
                                                                                          Alpha-2 code                          transaction

2.37    [0..1]   +++ Identification    (AT-10 Originator‟s
                                       Identification Code)
                                       Format rule:
                                       Either „Organisation
                                       Identification‟ or one
                                       occurrence of „Private
                                       Identification‟ may be
                                       present.

2.37    {Or      ++++ Organisation                              If present, every ISO
                 Identification                                 option is allowed.

2.37    Or}      ++++ Private          Usage rule:                                        If present, only one     MD03         reject the
                 Identification        Only one occurrence                                occurrence of 'Private                transaction
                                       of „Private Identifi-                              Identification' is
                                       cation‟ is allowed.                                allowed

2.37    [0..1]   +++ Country of                                 Only used for additio-
                 Residence                                      nal optional services

2.38    [0..1]   ++ Debtor Account     Mandatory                                          Must be present          MD03         reject the
                                       (AT-01 Account                                                                           transaction
                                       Number of the
                                                                                          Must contain an IBAN     MD03         reject the
                                       Originator)
                                                                                                                                transaction
                                       Usage rule:
                                       Only IBAN is allowed.                              Characters 1 and 2       AC01         reject the
                                                                                          (country code) must                   transaction
                                                                                          be an ISO 3166
                                                                                          Alpha-2 code and
                                                                                          must represent a
                                                                                          SEPA country.




        Page 45 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                       Requirements             ditional specifications

                                                                                          Characters 3 and 4    AC01            reject the
                                                                                          (IBAN check digits)                   transaction
                                                                                          are checked using ISO
                                                                                          7064

2.39    [1..1]   ++ Debtor Agent       (AT-06 BIC of the                                  Must contain BIC         MD03         reject the
                                       Originator Bank)                                                                         transaction
                                       Usage rule:
                                                                                          Must contain a BIC     RC01           reject the
                                       Only BIC is allowed.
                                                                                          from the BIC-directory                transaction

2.40    [0..1]   ++ Debtor Agent                                Only used for additio-
                 Account                                        nal optional services

2.41    [1..1]   ++ Creditor Agent     (AT-23 BIC of the                                  Must contain BIC         MD03         reject the
                                       Beneficiary Bank)                                                                        transaction
                                       Usage rule:
                                                                                          Must contain a BIC     RC01           reject the
                                       Only BIC is allowed.
                                                                                          from the BIC-directory                transaction

                                                                                          Creditor Agent must     MD03          reject the
                                                                                          be a participant reach-               transaction
                                                                                          able by or via CSM 1

2.42    [0..1]   ++ Creditor Agent                              Only used for additio-
                 Account                                        nal optional services

2.43    [1..1]   ++ Creditor

2.43    [0..1]   +++ Name              Mandatory                                          Must be present          MD03         reject the
                                       (AT-21 Name of the                                                                       transaction
                                       Beneficiary)

2.43    [0..1]   +++ Postal Address    (AT-22 Address of the
                                       Beneficiary)

2.43    [0..5]   ++++ Address Line     Format rule:                                       If present, a            MD03         reject the
                                       Only two occurrences                               maximum of two                        transaction
                                       of „Address Line‟ are                              occurrences 'Address
                                       allowed.                                           Line' is allowed

2.43    [1..1]   ++++ Country                                                             Must be an ISO 3166      MD03         reject the
                                                                                          Alpha-2 code                          transaction

2.43    [0..1]   +++ Identification    (AT-24 Beneficiary
                                       Identification Code)
                                       Format rule:
                                       Either „Organisation
                                       Identification‟ or one
                                       occurrence of „Private
                                       Identification‟ may be
                                       present.

2.43    {Or      ++++ Organisation                              If present, every ISO
                 Identification                                 option is allowed.

2.43    Or}      ++++ Private          Usage rule:                                        If present, only one     MD03         reject the
                 Identification        Only one occurrence                                occurrence of 'Private                transaction
                                       of „Private Identifi-                              Identification' is
                                       cation‟ is allowed.                                allowed

2.43    [0..1]   +++ Country of                                 Only used for additio-
                 Residence                                      nal optional services

2.44    [0..1]   ++ Creditor Account   Mandatory                                          Must be present          MD03         reject the
                                       (AT-20 Account of the                                                                    transaction
                                       Beneficiary)
                                       Usage rule:
                                       Only IBAN is allowed.

                                                                                          Must contain an IBAN     MD03         reject the
                                                                                                                                transaction




        Page 46 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                   Error Code   Action
                                        Requirements              ditional specifications

                                                                                            Characters 1 and 2       AC01         reject the
                                                                                            (country code) must                   transaction
                                                                                            be an ISO 3166
                                                                                            Alpha-2 code and
                                                                                            must represent a
                                                                                            SEPA country.

                                                                                            Characters 3 and 4    AC01            reject the
                                                                                            (IBAN check digits)                   transaction
                                                                                            are checked using ISO
                                                                                            7064

2.45    [0..1]   ++ Ultimate Creditor   (AT-28 Beneficiary        Will be considered for
                                        Reference Party)          inclusion in a future
                                        Usage rule:               version as AT-28
                                        Only „Name‟ or „Iden-     Beneficiary Reference
                                        tification‟ is allowed.   Party

2.45    [0..1]   +++ Name                                         Idem

2.45    [0..1]   +++ Postal Address                               Idem

2.45    [0..1]   +++ Identification     Format rule:              Idem
                                        Either „Organisation
                                        Identification‟ or one
                                        occurrence of „Private
                                        Identification‟ may be
                                        present.

2.45    {Or      ++++ Organisation                                Idem
                 Identification

2.45    Or}      ++++ Private           Usage rule:               Idem
                 Identification         Only one occurrence
                                        of „Private
                                        Identification‟ is
                                        allowed.

2.45    [0..1]   +++ Country of                                   Idem
                 Residence

2.46    [0..n]   ++ Instruction for                               Only used for additio-
                 Creditor Agent                                   nal optional services

2.49    [0..n]   ++ Instruction for                               Only used for additio-
                 Next Agent                                       nal optional services

2.52    [0..1]   ++ Purpose                                       Only used for additio-
                                                                  nal optional services

2.55    [0..10 ++ Regulatory                                      Only used for additio-
        ]      Reporting                                          nal optional services

2.64    [0..10 ++ Related                                         Only used for additio-
        ]      Remittance                                         nal optional services
               Information

2.71    [0..1]   ++ Remittance          (AT-05 Remittance                                   Either 'Structured' or   MD03         reject the
                 Information            Information)                                        'Unstructured' may be                 transaction
                                        Usage rule:                                         present.
                                        Either „Structured‟ or
                                        „Unstructured‟ may be
                                        present.




        Page 47 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core               Comments and ad-          Checks                  Error Code   Action
                                         Requirements            ditional specifications

2.72    [0..n]   +++ Unstructured        Usage rule:                                       Only one occurrence is MD03          reject the
                                         „Unstructured‟ may                                allowed.                             transaction
                                         carry structured
                                         remittance infor-
                                         mation, as agreed
                                         between Originator
                                         and the Beneficiary.
                                         Usage rule:
                                         Only one occurrence
                                         of „Unstructured‟ is
                                         allowed.

2.73    [0..n]   +++ Structured          Format rule:                                      Only one occurrence is MD03          reject the
                                         „Structured‟ can be                               allowed.                             transaction
                                         used; provided the
                                         tags and data do not
                                         exceed 140 characters
                                         in length.
                                         Usage rule:
                                         Only one occurrence
                                         of „Structured‟ is
                                         allowed.

                                                                                           The length, including   MD03         reject the
                                                                                           tags, must be 140                    transaction
                                                                                           characters or less.

2.74    [0..1]   ++++ Referred
                 Document Information

2.80    [0..1]   ++++ Referred
                 Document Related
                 Date

2.81    [0..n]   ++++ Referred
                 Document Amount

2.87    [0..1]   ++++ Creditor
                 Reference Information

2.93    [0..1]   ++++ Invoicer

2.94    [0..1]   ++++ Invoicee

2.95    [0..1]   ++++ Additional
                 Remittance
                 Information




        Page 48 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.2    Inter CSM Credit Transfer (pacs.008.001.01)

         From CSM 1 to CSM 2

         If the message does not conform to the ISO xsd schema the whole message will be rejected with
         Error Code 'MD03'.



 Index   Mult.    Message element      SEPA Core                 Comments and ad-          Checks                  Error Code    Action
                                       Requirements              ditional specifications

 1.0     [1..1]   +Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 1,        Must be unique, for     MS03          return the
                  Identification                                 must be unique over       the instructing party   (duplicate)   message
                                                                 time for this message     (CSM 1)
                                                                 type (CT).

 1.2     [1..1]   ++ Creation Date                               The date and time the Must be a valid date        MD03          reject the
                  Time                                           message is created    and time                                  message

 1.3     [0..1]   ++ Batch Booking                               Only used for additio-
                                                                 nal optional services

 1.4     [1..1]   ++ Number Of                                   A maximum of 100000 Must be  100000              MD03          reject the
                  Transactions                                   transactions per                                                message
                                                                 message.

                                                                                           Must equal the          MD03          reject the
                                                                                           number of                             message
                                                                                           transactions in the
                                                                                           message

 1.5     [0..1]   ++ Control Sum                                 Only used for additio-
                                                                 nal optional services

 1.6     [0..1]   ++ Total Interbank   Mandatory                                           Must equal the sum of MD03            reject the
                  Settlement Amount    Usage rule:                                         all occurrences of                    message
                                       Only „EUR‟ is allowed.                              Credit Transfer
                                                                                           Transaction
                                       Usage rule:
                                                                                           Information /
                                       Amount must be 0.01
                                                                                           Interbank Settlement
                                       or more and
                                                                                           Amount
                                       999999999999999.99
                                       or less.                                            Currency Code must      MD03          reject the
                                       Format rule:                                        be "EUR"                              message
                                       The fractional part has
                                       a maximum of two                                    Amount must be ≥        MD03          reject the
                                       digits.                                             0.01                                  message

                                                                                           Amount must be ≤   MD03               reject the
                                                                                           999999999999999.99                    message

                                                                                           Maximum 2 fraction      MD03          reject the
                                                                                           digits                                message

 1.7     [0..1]   ++ Interbank         Mandatory                 Date on which CSM 1       Must be present         MD03          reject the
                  Settlement Date      (AT-42 Settlement         has settled these                                               message
                                       Date of the Credit        transactions.
                                       Transfer)

                                                                                           Must be a valid date    MD03          reject the
                                                                                                                                 message

                                                                                           Must not be in the      MD03          reject the
                                                                                           future                                message

                                                                                           Must be current        TM01           reject the
                                                                                           Target day or 1 Target                message
                                                                                           day in the past

 1.8     [1..1]   ++ Settlement
                  Information




         Page 49 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                  Error Code   Action
                                         Requirements               ditional specifications

1.9     [1..1]   +++ Settlement          Usage rule:                In Inter CSM only the     Must contain the value MD03          reject the
                 Method                  Only CLRG, INGA and        value 'CLRG' is           'CLRG'.                              message
                                         INDA are allowed.          allowed.

1.10    [0..1]   +++ Settlement          Usage rule:                Absent. (ISO: If          Must not be present     MD03         reject the
                 Account                 Only 'Identification' is   Settlement Method =                                            message
                                         allowed.                   'CLRG', then
                                                                    Settlement Account is
                                                                    not allowed.)

1.11    [0..1]   +++ Clearing System                                Present.                  Must be Present         MD03         reject the
                                                                    (ISO: If Settlement                                            message
                                                                    Method = 'CLRG', then
                                                                    Clearing System must
                                                                    be present.)
                                                                    Identifies Clearing
                                                                    System of CSM 2

1.12    {Or      ++++ Clearing                                      Used when Clearing        If present, it must    MD03          reject the
                 System Identification                              System Identification     contain the valid                    message
                                                                    exists for the Clearing   UNIFI code identifying
                                                                    System of CSM 2 in        CSM 2
                                                                    the UNIFI ISO 20022
                                                                    code list

1.13    Or}      ++++ Proprietary                                   Used when no             If present, it must      MD03         reject the
                                                                    Clearing System          contain the valid code                message
                                                                    Identification exists    as specified by CSM 2
                                                                    for the Clearing
                                                                    System of CSM 2 in
                                                                    UNIFI ISO 20022 code
                                                                    list. Value is specified
                                                                    by CSM 2.

1.14    [0..1]   +++ Instructing                                    Absent. (ISO: If
                 Reimbursement Agent                                Settlement Method =
                                                                    'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.15    [0..1]   +++ Instructing                                    Absent. (ISO: If
                 Reimbursement Agent                                Settlement Method =
                 Account                                            'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.16    [0..1]   +++ Instructed Reim-                               Absent. (ISO: If
                 bursement Agent                                    Settlement Method =
                                                                    'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.17    [0..1]   +++ Instructed Reim-                               Absent. (ISO: If
                 bursement Agent                                    Settlement Method =
                 Account                                            'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.18    [0..1]   +++ Third Reim-                                    Absent. (ISO: If
                 bursement Agent                                    Settlement Method =
                                                                    'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)

1.19    [0..1]   +++ Third Reim-                                    Absent. (ISO: If
                 bursement Agent                                    Settlement Method =
                 Account                                            'CLRG', then Reim-
                                                                    bursement agents are
                                                                    not allowed.)




        Page 50 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code    Action
                                        Requirements              ditional specifications

1.20    [0..1]   ++ Payment Type                                  Absent.                   Must be absent.        MD03          reject the
                 Information                                      Present at transaction                                         message
                                                                  level (2.2).

1.21    [0..1]   +++ Instruction
                 Priority

1.22    {Or      +++ Service Level      Usage rule:
                                        Service Level must be
                                        present at either in
                                        „Group Header‟ or in
                                        „Credit Transfer Trans-
                                        action Information‟, to
                                        specify “SEPA”.

1.23    {Or      ++++ Code              (AT-40 Identification
                                        code of the Scheme)
                                        Usage rule:
                                        Only „SEPA‟ is allowed.

1.24    Or}      ++++ Proprietary

1.25    Or}      +++ Clearing Channel

1.26    [0..1]   +++ Local Instrument

1.29    [0..1]   +++ Category
                 Purpose

1.30    [0..1]   ++ Instructing Agent   Usage rule:               Mandatory, either at      Must be present in      MD03         reject the
                                        Only BIC is allowed.      Group level or at         either the Group                     message
                                                                  Transaction level, but    Header or the Credit
                                                                  not at both levels.       Transfer Transaction
                                                                  (Most obvious is at       Information, but not in
                                                                  transaction level.)       both.
                                                                  Contains the
                                                                  Instructing Agent as
                                                                  received by CSM 1.

                                                                                            If present, must       MD03          reject the
                                                                                            contain BIC                          message

                                                                                            If present with BIC,   RC01          return the
                                                                                            must contain a BIC                   message
                                                                                            from the BIC-directory

1.31    [0..1]   ++ Instructed Agent    Usage rule:               Not used.                 Must be absent         MD03          reject the
                                        Only BIC is allowed.                                                                     message




2.0     [1..n]   +Credit Transfer
                 Transaction
                 Information

2.1     [1..1]   ++ Payment
                 Identification

2.1     [0..1]   +++ Instruction                                  Assigned by the           Must be unique for the MS03          return the
                 Identification                                   sending party: CSM 1      instructing party      (duplicate)   transaction
                                                                                            (CSM 1)




        Page 51 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code    Action
                                        Requirements              ditional specifications

2.1     [1..1]   +++ End to End         (AT-41 Originator‟s       Assigned by the
                 Identification         Reference to the          debtor, is passed on
                                        Credit Transfer)          unaltered.
                                        Usage rule:
                                        A customer reference
                                        that must be passed
                                        on in the end-to-end
                                        chain. In the event
                                        that no reference was
                                        given, „NOTPROVIDED‟
                                        must be used.

2.1     [1..1]   +++ Transaction        (AT-43 Originator         Assigned by the       The combination of         MS03          return the
                 Identification         Bank‟s Reference)         Debtor Agent, must be Debtor Agent and           (duplicate)   transaction
                                        Usage rule:               unique over time.     Transaction
                                        Must contain a                                  Identification must be
                                        reference that is                               unique, for this
                                        meaningful to the                               message type (CT).
                                        Originator‟s Bank and
                                        is unique over time.

2.2     [0..1]   ++ Payment Type                                  Present.
                 Information

2.3     [0..1]   +++ Instruction                                  Only used for additio-
                 Priority                                         nal optional services

2.4     {Or      +++ Service Level      Usage rule:             Present.
                                        „Service Level‟ must
                                        be present at either in
                                        „Group Header‟ or in
                                        „Credit Transfer
                                        Transaction Infor-
                                        mation‟, to specify
                                        “SEPA”.

2.5     {Or      ++++ Code              (AT-40 Identification     Present.                  Must be present        MD03          reject the
                                        code of the Scheme)                                                                      transaction
                                        Usage rule:
                                        Only „SEPA‟ is allowed.

                                                                                            Value must be "SEPA"   MD03          reject the
                                                                                                                                 transaction

2.6     Or}      ++++ Proprietary

2.7     Or}      +++ Clearing Channel

2.8     [0..1]   +++ Local Instrument                             Only used for additio-
                                                                  nal optional services

2.11    [0..1]   +++ Category                                     Only used for additio-
                 Purpose                                          nal optional services

2.12    [1..1]   ++ Interbank           (AT-04 Amount of the                                Currency Code must     MD03          reject the
                 Settlement Amount      Credit Transfer in                                  be "EUR"                             transaction
                                        Euro)
                                        Usage rule:
                                        Only „EUR‟ is allowed.
                                        Usage rule:
                                        Amount must be 0.01
                                        or more and
                                        999999999.99 or less.
                                        Format rule:
                                        The fractional part has
                                        a maximum of two
                                        digits.

                                                                                            Amount must be ≥       MD03          reject the
                                                                                            0.01                                 transaction




        Page 52 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                        Requirements              ditional specifications

                                                                                            Amount must be ≤       MD03         reject the
                                                                                            999999999.99                        transaction

                                                                                            Maximum 2 fraction     MD03         reject the
                                                                                            digits                              transaction

2.13    [0..1]   ++ Interbank                                     Cannot be present
                 Settlement Date                                  because mandatory on
                                                                  grouplevel

2.14    [0..1]   ++ Settlement Time                               Only used for additio-
                 Indication                                       nal optional services

2.17    [0..1]   ++ Settlement Time                               Only used for additio-
                 Request                                          nal optional services

2.19    [0..1]   ++ Acceptance Date                               Only used for additio-
                 and Time                                         nal optional services

2.20    [0..1]   ++ Pooling                                       Only used for additio-
                 Adjustment Date                                  nal optional services

2.21    [0..1]   ++ Instructed Amount                             Only used for additio-
                                                                  nal optional services

2.22    [0..1]   ++ Exchange Rate                                 Only used for additio-
                                                                  nal optional services

2.23    [1..1]   ++ Charge Bearer       Usage rule:                                         Code must be "SLEV"    MD03         reject the
                                        Only „SLEV‟ is allowed.                                                                 transaction

2.24    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

2.25    [0..1]   ++ Previous                                      Only used for additio-
                 Instructing Agent                                nal optional services

2.26    [0..1]   ++ Previous Instruc-                             Only used for additio-
                 ting Agent Account                               nal optional services

2.27    [0..1]   ++ Instructing Agent   Usage rule:               Mandatory, either at      Must be present in      MD03        reject the
                                        Only BIC is allowed.      Group level or at         either the Group                    message
                                                                  Transaction level, but    Header or the Credit
                                                                  not at both levels.       Transfer Transaction
                                                                  (Most obvious is at       Information, but not in
                                                                  transaction level.)       both.
                                                                  Contains the
                                                                  Instructing Agent as
                                                                  received by CSM 1.

                                                                                            If present, must       MD03         reject the
                                                                                            contain BIC                         transaction

                                                                                            If present with BIC,   RC01         return the
                                                                                            must contain a BIC                  transaction
                                                                                            from the BIC-directory

2.28    [0..1]   ++ Instructed Agent    Usage rule:               Not used.                 Must be absent         MD03         reject the
                                        Only BIC is allowed.                                                                    transaction

2.29    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 1                                          nal optional services

2.30    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 1 Account                                  nal optional services

2.31    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 2                                          nal optional services

2.32    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 2 Account                                  nal optional services

2.33    [0..1]   ++ Intermediary                                  Only used for additio-
                 Agent 3                                          nal optional services




        Page 53 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                       Requirements             ditional specifications

2.34    [0..1]   ++ Intermediary                                Only used for additio-
                 Agent 3 Account                                nal optional services

2.35    [0..1]   ++ Ultimate Debtor    (AT-08 Originator       Will be considered for
                                       Reference Party)        inclusion in a future
                                       Usage rule:             version as AT-08
                                       Only „Name „or „Identi- Originator Reference
                                       fication‟ is allowed.   Party

2.35    [0..1]   +++ Name                                       Idem

2.35    [0..1]   +++ Postal Address                             Idem

2.35    [0..1]   +++ Identification    Format rule:             Idem
                                       Either „Organisation
                                       Identification‟ or one
                                       occurrence of „Private
                                       Identification‟ may be
                                       present.

2.35    {Or      ++++ Organisation                              Idem
                 Identification

2.35    Or}      ++++ Private          Usage rule:              Idem
                 Identification        Only one occurrence
                                       of „Private Identifi-
                                       cation‟ is allowed.

2.35    [0..1]   +++ Country of                                 Idem
                 Residence

2.36    [0..1]   ++ Initiating Party                            Only used for additio-
                                                                nal optional services

2.37    [1..1]   ++ Debtor

2.37    [0..1]   +++ Name              Mandatory                                          Debtor name must be      MD03         reject the
                                       (AT-02 Name of the                                 present                               transaction
                                       Originator)

2.37    [0..1]   +++ Postal Address    (AT-03 Address of the
                                       Originator)

2.37    [0..5]   ++++ Address Line     Format rule:                                       If present, a            MD03         reject the
                                       Only two occurrences                               maximum of two                        transaction
                                       of „Address Line‟ are                              occurrences 'Address
                                       allowed.                                           Line' is allowed

2.37    [1..1]   ++++ Country                                                             Must be an ISO 3166      MD03         reject the
                                                                                          Alpha-2 code                          transaction

2.37    [0..1]   +++ Identification    (AT-10 Originator‟s
                                       Identification Code)
                                       Format rule:
                                       Either „Organisation
                                       Identification‟ or one
                                       occurrence of „Private
                                       Identification‟ may be
                                       present.

2.37    {Or      ++++ Organisation                              If present, every ISO
                 Identification                                 option is allowed

2.37    Or}      ++++ Private          Usage rule:                                        If present, only one     MD03         reject the
                 Identification        Only one occurrence                                occurrence of 'Private                transaction
                                       of „Private Identifi-                              Identification' is
                                       cation‟ is allowed.                                allowed

2.37    [0..1]   +++ Country of                                 Only used for additio-
                 Residence                                      nal optional services




        Page 54 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element      SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                      Requirements             ditional specifications

2.38    [0..1]   ++ Debtor Account    Mandatory                                          Must be present        MD03         reject the
                                      (AT-01 Account Num-                                                                    transaction
                                      ber of the Originator)
                                      Usage rule:
                                      Only IBAN is allowed.

                                                                                         Must contain an IBAN   MD03         reject the
                                                                                                                             transaction

                                                                                         Characters 1 and 2     AC01         reject the
                                                                                         (country code) must                 transaction
                                                                                         be an ISO 3166
                                                                                         Alpha-2 code and
                                                                                         must represent a
                                                                                         SEPA country.

                                                                                         Characters 3 and 4    AC01          reject the
                                                                                         (IBAN check digits)                 transaction
                                                                                         are checked using ISO
                                                                                         7064

2.39    [1..1]   ++ Debtor Agent      (AT-06 BIC of the                                  Must contain BIC       MD03         reject the
                                      Originator Bank)                                                                       transaction
                                      Usage rule:
                                      Only BIC is allowed.

                                                                                         Must contain a BIC     RC01         return the
                                                                                         from the BIC-directory              transaction

2.40    [0..1]   ++ Debtor Agent                               Only used for additio-
                 Account                                       nal optional services

2.41    [1..1]   ++ Creditor Agent    (AT-23 BIC of the                                  Creditor Agent must    MS03         return the
                                      Beneficiary Bank)                                  be a participant                    transaction
                                      Usage rule:                                        reachable by CSM 2
                                      Only BIC is allowed.

                                                                                         Must contain a BIC     RC01         return the
                                                                                         from the BIC-directory              transaction

                                                                                         Must contain BIC       MD03         reject the
                                                                                                                             transaction

2.42    [0..1]   ++ Creditor Agent                             Only used for additio-
                 Account                                       nal optional services

2.43    [1..1]   ++ Creditor

2.43    [0..1]   +++ Name             Mandatory                                          Must be present        MD03         reject the
                                      (AT-21 Name of the                                                                     transaction
                                      Beneficiary)

2.43    [0..1]   +++ Postal Address   (AT-22 Address of the
                                      Beneficiary)

2.43    [0..5]   ++++ Address Line    Format rule:                                       If present, a          MD03         reject the
                                      Only two occurrences                               maximum of two                      transaction
                                      of „Address Line‟ are                              occurrences 'Address
                                      allowed.                                           Line' is allowed

2.43    [1..1]   ++++ Country                                                            Must be an ISO 3166    MD03         reject the
                                                                                         Alpha-2 code                        transaction

2.43    [0..1]   +++ Identification   (AT-24 Beneficiary
                                      Identification Code)
                                      Format rule:
                                      Either „Organisation
                                      Identification‟ or one
                                      occurrence of „Private
                                      Identification‟ may be
                                      present.




        Page 55 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                        Requirements             ditional specifications

2.43    {Or      ++++ Organisation                               If present, every ISO
                 Identification                                  option is allowed

2.43    Or}      ++++ Private           Usage rule:                                        If present, only one     MD03         reject the
                 Identification         Only one occurrence                                occurrence of 'Private                transaction
                                        of „Private                                        Identification' is
                                        Identification‟ is                                 allowed
                                        allowed.

2.43    [0..1]   +++ Country of                                  Only used for additio-
                 Residence                                       nal optional services

2.44    [0..1]   ++ Creditor Account    Mandatory                                          Must be present          MD03         reject the
                                        (AT-20 Account of the                                                                    transaction
                                        Beneficiary)
                                        Usage rule:
                                        Only IBAN is allowed.

                                                                                           Must contain an IBAN     MD03         reject the
                                                                                                                                 transaction

                                                                                           Characters 1 and 2       AC01         reject the
                                                                                           (country code) must                   transaction
                                                                                           be an ISO 3166
                                                                                           Alpha-2 code and
                                                                                           must represent a
                                                                                           SEPA country.

                                                                                           Characters 3 and 4    AC01            reject the
                                                                                           (IBAN check digits)                   transaction
                                                                                           are checked using ISO
                                                                                           7064

2.45    [0..1]   ++ Ultimate Creditor   (AT-28 Beneficiary       Will be considered for
                                        Reference Party)         inclusion in a future
                                        Usage rule:              version as AT-28
                                        Only „Name‟ or           Beneficiary Reference
                                        „Identification‟ is      Party
                                        allowed.

2.45    [0..1]   +++ Name                                        Idem

2.45    [0..1]   +++ Postal Address                              Idem

2.45    [0..1]   +++ Identification     Format rule:             Idem
                                        Either „Organisation
                                        Identification‟ or one
                                        occurrence of „Private
                                        Identification‟ may be
                                        present.

2.45    {Or      ++++ Organisation                               Idem
                 Identification

2.45    Or}      ++++ Private           Usage rule:              Idem
                 Identification         Only one occurrence
                                        of „Private
                                        Identification‟ is
                                        allowed.

2.45    [0..1]   +++ Country of                                  Idem
                 Residence

2.46    [0..n]   ++ Instruction for                              Only used for additio-
                 Creditor Agent                                  nal optional services

2.49    [0..n]   ++ Instruction for                              Used to provide the   Must be present and    MD03               reject the
                 Next Agent                                      settlement reference, contain the settlement                    transaction
                                                                 assigned by CSM 1, to reference.




        Page 56 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                         Requirements             ditional specifications

                                                                  CSM 2. Contains a         Settlement reference     MD03         reject the
                                                                  codeword followed by      must not be more                      transaction
                                                                  the reference itself:     than 16 positions.
                                                                  /STTLMREF/<ref max.
                                                                  16 positions>

2.52    [0..1]   ++ Purpose                                       Only used for additio-
                                                                  nal optional services

2.55    [0..10 ++ Regulatory                                      Only used for additio-
        ]      Reporting                                          nal optional services

2.64    [0..10 ++ Related                                         Only used for additio-
        ]      Remittance                                         nal optional services
               Information

2.71    [0..1]   ++ Remittance           (AT-05 Remittance                                  Either 'Structured' or   MD03         reject the
                 Information             Information)                                       'Unstructured' is                     transaction
                                         Usage rule:                                        present.
                                         Either „Structured‟ or
                                         „Unstructured‟ may be
                                         present.

2.72    [0..n]   +++ Unstructured        Usage rule:                                        Only one occurrence is MD03           reject the
                                         „Unstructured‟ may                                 allowed.                              transaction
                                         carry structured
                                         remittance
                                         information, as agreed
                                         between Originator
                                         and the Beneficiary.
                                         Usage rule:
                                         Only one occurrence
                                         of „Unstructured‟ is
                                         allowed.

2.73    [0..n]   +++ Structured          Format rule:                                       Only one occurrence is MD03           reject the
                                         „Structured‟ can be                                allowed.                              transaction
                                         used; provided the
                                         tags and data do not
                                         exceed 140 characters
                                         in length.
                                         Usage rule:
                                         Only one occurrence
                                         of „Structured‟ is
                                         allowed.

                                                                                            The length, including    MD03         reject the
                                                                                            tags, must be 140                     transaction
                                                                                            characters or less.

2.74    [0..1]   ++++ Referred
                 Document Information

2.80    [0..1]   ++++ Referred
                 Document Related
                 Date

2.81    [0..n]   ++++ Referred
                 Document Amount

2.87    [0..1]   ++++ Creditor
                 Reference Information

2.93    [0..1]   ++++ Invoicer

2.94    [0..1]   ++++ Invoicee

2.95    [0..1]   ++++ Additional
                 Remittance
                 Information




        Page 57 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.3    CSM - Bank Credit Transfer (pacs.008.001.01)

         From CSM 2 to Bank 2



 Index   Mult.    Message element       SEPA Core                  Comments and ad-          Checks                 Error Code   Action
                                        Requirements               ditional specifications

 1.0     [1..1]   +Group Header

 1.1     [1..1]   ++ Message                                       Assigned by CSM 2,
                  Identification                                   must be unique over
                                                                   time for this message
                                                                   type (CT).

 1.2     [1..1]   ++ Creation Date                                 The date and time the
                  Time                                             message has been
                                                                   created

 1.3     [0..1]   ++ Batch Booking                                 Only used for additio-
                                                                   nal optional services

 1.4     [1..1]   ++ Number Of                                     A maximum of 100000
                  Transactions                                     transactions per
                                                                   message.

 1.5     [0..1]   ++ Control Sum                                   Only used for additio-
                                                                   nal optional services

 1.6     [0..1]   ++ Total Interbank    Mandatory                  Present, equals the
                  Settlement Amount     Usage rule:                sum of all occurrences
                                        Only „EUR‟ is allowed.     of Credit Transfer
                                                                   Transaction
                                        Usage rule:
                                                                   Information /
                                        Amount must be 0.01
                                                                   Interbank Settlement
                                        or more and
                                                                   Amount.
                                        999999999999999.99
                                        or less.
                                        Format rule:
                                        The fractional part has
                                        a maximum of two
                                        digits.

 1.7     [0..1]   ++ Interbank          Mandatory                  Present. date on which
                  Settlement Date       (AT-42 Settlement          CSM 2 has settled
                                        Date of the Credit         these transactions.
                                        Transfer)                  This may not be the
                                                                   same date as the
                                                                   requested settlement
                                                                   date in the CT from
                                                                   Bank 1 to CSM 1.

 1.8     [1..1]   ++ Settlement
                  Information

 1.9     [1..1]   +++ Settlement        Usage rule:                Only the value 'CLRG'
                  Method                Only CLRG, INGA and        is allowed.
                                        INDA are allowed.

 1.10    [0..1]   +++ Settlement        Usage rule:                Absent. (ISO: If
                  Account               Only 'Identification' is   Settlement Method =
                                        allowed.                   'CLRG', then
                                                                   Settlement Account is
                                                                   not allowed.)

 1.11    [0..1]   +++ Clearing System                              Present. (ISO: If
                                                                   Settlement Method =
                                                                   'CLRG', then Clearing
                                                                   System must be
                                                                   present.)
                                                                   Identifies Clearing
                                                                   System of CSM 2




         Page 58 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-           Checks                 Error Code   Action
                                         Requirements              ditional specifications

1.12    {Or      ++++ Clearing                                     Used when Clearing
                 System Identification                             System Identification
                                                                   exists for the Clearing
                                                                   System of CSM 2 in
                                                                   the UNIFI ISO 20022
                                                                   code list

1.13    Or}      ++++ Proprietary                                  Used when no
                                                                   Clearing System
                                                                   Identification exists
                                                                   for the Clearing
                                                                   System of CSM 2 in
                                                                   UNIFI ISO 20022 code
                                                                   list. Value is specified
                                                                   by CSM 2.

1.14    [0..1]   +++ Instructing                                   Absent. (ISO: If
                 Reimbursement Agent                               Settlement Method =
                                                                   'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.15    [0..1]   +++ Instructing                                   Absent. (ISO: If
                 Reimbursement Agent                               Settlement Method =
                 Account                                           'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.16    [0..1]   +++ Instructed Reim-                              Absent. (ISO: If
                 bursement Agent                                   Settlement Method =
                                                                   'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.17    [0..1]   +++ Instructed Reim-                              Absent. (ISO: If
                 bursement Agent                                   Settlement Method =
                 Account                                           'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.18    [0..1]   +++ Third Reim-                                   Absent. (ISO: If
                 bursement Agent                                   Settlement Method =
                                                                   'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.19    [0..1]   +++ Third Reim-                                   Absent. (ISO: If
                 bursement Agent                                   Settlement Method =
                 Account                                           'CLRG', then Reim-
                                                                   bursement agents are
                                                                   not allowed.)

1.20    [0..1]   ++ Payment Type                                   Absent.
                 Information                                       Present at transaction
                                                                   level (2.2).

1.21    [0..1]   +++ Instruction
                 Priority

1.22    {Or      +++ Service Level       Usage rule:
                                         Service Level must be
                                         present at either in
                                         „Group Header‟ or in
                                         „Credit Transfer Trans-
                                         action Information‟, to
                                         specify “SEPA”.

1.23    {Or      ++++ Code               (AT-40 Identification
                                         code of the Scheme)
                                         Usage rule:
                                         Only „SEPA‟ is allowed.

1.24    Or}      ++++ Proprietary




        Page 59 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                        Requirements            ditional specifications

1.25    Or}      +++ Clearing Channel

1.26    [0..1]   +++ Local Instrument

1.29    [0..1]   +++ Category
                 Purpose

1.30    [0..1]   ++ Instructing Agent   Usage rule:             Present, either at
                                        Only BIC is allowed.    Group level or at
                                                                Transaction level, but
                                                                not at both levels.
                                                                (Most obvious is at
                                                                transaction level.)
                                                                Contains the BIC of
                                                                the agent that
                                                                instructs the next
                                                                party in the chain to
                                                                carry out the (set of)
                                                                instruction(s): Bank 1.

1.31    [0..1]   ++ Instructed Agent    Usage rule:             Present.
                                        Only BIC is allowed.    Contains the BIC of
                                                                Bank 2.




2.0     [1..n]   +Credit Transfer
                 Transaction
                 Information

2.1     [1..1]   ++ Payment
                 Identification

2.1     [0..1]   +++ Instruction                                If present, assigned
                 Identification                                 by CSM 2, must be
                                                                unique over time for
                                                                this message type
                                                                (CT).

2.1     [1..1]   +++ End to End         (AT-41 Originator‟s     Assigned by the
                 Identification         Reference to the        debtor, is passed on
                                        Credit Transfer)        unaltered.
                                        Usage rule:
                                        A customer reference
                                        that must be passed
                                        on in the end-to-end
                                        chain. In the event
                                        that no reference was
                                        given, „NOTPROVIDED‟
                                        must be used.

2.1     [1..1]   +++ Transaction        (AT-43 Originator       Assigned by the
                 Identification         Bank‟s Reference)       Debtor Agent, must be
                                        Usage rule:             unique over time. Is
                                        Must contain a          passed on unaltered.
                                        reference that is
                                        meaningful to the
                                        Originator‟s Bank and
                                        is unique over time.

2.2     [0..1]   ++ Payment Type                                Present.
                 Information

2.3     [0..1]   +++ Instruction                                Only used for additio-
                 Priority                                       nal optional services




        Page 60 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                        Requirements              ditional specifications

2.4     {Or      +++ Service Level      Usage rule:             Present.
                                        „Service Level‟ must
                                        be present at either in
                                        „Group Header‟ or in
                                        „Credit Transfer Trans-
                                        action Information‟, to
                                        specify “SEPA”.

2.5     {Or      ++++ Code              (AT-40 Identification     Present. Contains the
                                        code of the Scheme)       value 'SEPA'.
                                        Usage rule:
                                        Only „SEPA‟ is allowed.

2.6     Or}      ++++ Proprietary

2.7     Or}      +++ Clearing Channel

2.8     [0..1]   +++ Local Instrument                             Only used for additio-
                                                                  nal optional services

2.11    [0..1]   +++ Category                                     Only used for additio-
                 Purpose                                          nal optional services

2.12    [1..1]   ++ Interbank           (AT-04 Amount of the
                 Settlement Amount      Credit Transfer in
                                        Euro)
                                        Usage rule:
                                        Only „EUR‟ is allowed.
                                        Usage rule:
                                        Amount must be 0.01
                                        or more and
                                        999999999.99 or less.
                                        Format rule:
                                        The fractional part has
                                        a maximum of two
                                        digits.

2.13    [0..1]   ++ Interbank                                     Cannot be present
                 Settlement Date                                  because mandatory on
                                                                  group level

2.14    [0..1]   ++ Settlement Time                               Only used for additio-
                 Indication                                       nal optional services

2.17    [0..1]   ++ Settlement Time                               Only used for additio-
                 Request                                          nal optional services

2.19    [0..1]   ++ Acceptance Date                               Only used for additio-
                 and Time                                         nal optional services

2.20    [0..1]   ++ Pooling                                       Only used for additio-
                 Adjustment Date                                  nal optional services

2.21    [0..1]   ++ Instructed Amount                             Only used for additio-
                                                                  nal optional services

2.22    [0..1]   ++ Exchange Rate                                 Only used for additio-
                                                                  nal optional services

2.23    [1..1]   ++ Charge Bearer       Usage rule:             Contains the value
                                        Only „SLEV‟ is allowed. 'SLEV'

2.24    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

2.25    [0..1]   ++ Previous                                      Only used for additio-
                 Instructing Agent                                nal optional services

2.26    [0..1]   ++ Previous                                      Only used for additio-
                 Instructing Agent                                nal optional services
                 Account




        Page 61 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                        Requirements             ditional specifications

2.27    [0..1]   ++ Instructing Agent   Usage rule:              Present, either at
                                        Only BIC is allowed.     Group level or at
                                                                 Transaction level, but
                                                                 not at both levels.
                                                                 (Most obvious is at
                                                                 transaction level.)
                                                                 Contains the BIC of
                                                                 the agent that
                                                                 instructs the next
                                                                 party in the chain to
                                                                 carry out the (set of)
                                                                 instruction(s): Bank 1.

2.28    [0..1]   ++ Instructed Agent    Usage rule:              Absent.
                                        Only BIC is allowed.

2.29    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 1                                         nal optional services

2.30    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 1 Account                                 nal optional services

2.31    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 2                                         nal optional services

2.32    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 2 Account                                 nal optional services

2.33    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 3                                         nal optional services

2.34    [0..1]   ++ Intermediary                                 Only used for additio-
                 Agent 3 Account                                 nal optional services

2.35    [0..1]   ++ Ultimate Debtor     (AT-08 Originator        Will be considered for
                                        Reference Party)         inclusion in a future
                                        Usage rule:              version as AT-08
                                        Only „Name „or           Originator Reference
                                        „Identification‟ is      Party
                                        allowed.

2.35    [0..1]   +++ Name                                        Idem

2.35    [0..1]   +++ Postal Address                              Idem

2.35    [0..1]   +++ Identification     Format rule:             Idem
                                        Either „Organisation
                                        Identification‟ or one
                                        occurrence of „Private
                                        Identification‟ may be
                                        present.

2.35    {Or      ++++ Organisation                               Idem
                 Identification

2.35    Or}      ++++ Private           Usage rule:              Idem
                 Identification         Only one occurrence
                                        of „Private
                                        Identification‟ is
                                        allowed.

2.35    [0..1]   +++ Country of                                  Idem
                 Residence

2.36    [0..1]   ++ Initiating Party                             Only used for additio-
                                                                 nal optional services

2.37    [1..1]   ++ Debtor

2.37    [0..1]   +++ Name               Mandatory
                                        (AT-02 Name of the
                                        Originator)




        Page 62 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element      SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                      Requirements             ditional specifications

2.37    [0..1]   +++ Postal Address   (AT-03 Address of the
                                      Originator)

2.37    [0..5]   ++++ Address Line    Format rule:
                                      Only two occurrences
                                      of „Address Line‟ are
                                      allowed.

2.37    [1..1]   ++++ Country

2.37    [0..1]   +++ Identification   (AT-10 Originator‟s
                                      Identification Code)
                                      Format rule:
                                      Either „Organisation
                                      Identification‟ or one
                                      occurrence of „Private
                                      Identification‟ may be
                                      present.

2.37    {Or      ++++ Organisation                             If present, every ISO
                 Identification                                option may occur.

2.37    Or}      ++++ Private         Usage rule:
                 Identification       Only one occurrence
                                      of „Private
                                      Identification‟ is
                                      allowed.

2.37    [0..1]   +++ Country of                                Only used for additio-
                 Residence                                     nal optional services

2.38    [0..1]   ++ Debtor Account    Mandatory
                                      (AT-01 Account
                                      Number of the
                                      Originator)
                                      Usage rule:
                                      Only IBAN is allowed.

2.39    [1..1]   ++ Debtor Agent      (AT-06 BIC of the
                                      Originator Bank)
                                      Usage rule:
                                      Only BIC is allowed.

2.40    [0..1]   ++ Debtor Agent                               Only used for additio-
                 Account                                       nal optional services

2.41    [1..1]   ++ Creditor Agent    (AT-23 BIC of the
                                      Beneficiary Bank)
                                      Usage rule:
                                      Only BIC is allowed.

2.42    [0..1]   ++ Creditor Agent                             Only used for additio-
                 Account                                       nal optional services

2.43    [1..1]   ++ Creditor

2.43    [0..1]   +++ Name             Mandatory
                                      (AT-21 Name of the
                                      Beneficiary)

2.43    [0..1]   +++ Postal Address   (AT-22 Address of the
                                      Beneficiary)


2.43    [0..5]   ++++ Address Line    Format rule:
                                      Only two occurrences
                                      of „Address Line‟ are
                                      allowed.

2.43    [1..1]   ++++ Country




        Page 63 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                        Requirements             ditional specifications

2.43    [0..1]   +++ Identification     (AT-24 Beneficiary
                                        Identification Code)
                                        Format rule:
                                        Either „Organisation
                                        Identification‟ or one
                                        occurrence of „Private
                                        Identification‟ may be
                                        present.

2.43    {Or      ++++ Organisation                               If present, every ISO
                 Identification                                  option may occur.

2.43    Or}      ++++ Private           Usage rule:
                 Identification         Only one occurrence
                                        of „Private
                                        Identification‟ is
                                        allowed.

2.43    [0..1]   +++ Country of                                  Only used for additio-
                 Residence                                       nal optional services

2.44    [0..1]   ++ Creditor Account    Mandatory
                                        (AT-20 Account of the
                                        Beneficiary)
                                        Usage rule:
                                        Only IBAN is allowed.

2.45    [0..1]   ++ Ultimate Creditor   (AT-28 Beneficiary       Will be considered for
                                        Reference Party)         inclusion in a future
                                        Usage rule:              version as AT-28
                                        Only „Name‟ or           Beneficiary Reference
                                        „Identification‟ is      Party
                                        allowed.

2.45    [0..1]   +++ Name                                        Idem

2.45    [0..1]   +++ Postal Address                              Idem

2.45    [0..1]   +++ Identification     Format rule:             Idem
                                        Either „Organisation
                                        Identification‟ or one
                                        occurrence of „Private
                                        Identification‟ may be
                                        present.

2.45    {Or      ++++ Organisation                               Idem
                 Identification

2.45    Or}      ++++ Private           Usage rule:              Idem
                 Identification         Only one occurrence
                                        of „Private
                                        Identification‟ is
                                        allowed.

2.45    [0..1]   +++ Country of                                  Idem
                 Residence

2.46    [0..n]   ++ Instruction for                              Only used for additio-
                 Creditor Agent                                  nal optional services

2.49    [0..n]   ++ Instruction for                              Used to provide the
                 Next Agent                                      settlement reference,
                                                                 assigned by CSM 2, to
                                                                 Bank 2. Contains a
                                                                 codeword followed by
                                                                 the reference itself:
                                                                 /STTLMREF/<ref max.
                                                                 16 positions>

2.52    [0..1]   ++ Purpose                                      Only used for additio-
                                                                 nal optional services




        Page 64 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                         Requirements              ditional specifications

2.55    [0..10 ++ Regulatory                                       Only used for additio-
        ]      Reporting                                           nal optional services

2.64    [0..10 ++ Related                                          Only used for additio-
        ]      Remittance                                          nal optional services
               Information

2.71    [0..1]   ++ Remittance           (AT-05 Remittance         If present, copied
                 Information             Information)              from the previous CT
                                         Usage rule:               message. Provided by
                                         Either „Structured‟ or    Bank 1.
                                         „Unstructured‟, but not
                                         both, may be present.

2.72    [0..n]   +++ Unstructured        Usage rule:
                                         „Unstructured‟ may
                                         carry structured
                                         remittance
                                         information, as agreed
                                         between Originator
                                         and the Beneficiary.
                                         Usage rule:
                                         Only one occurrence
                                         of
                                         „Unstructured‟ is
                                         allowed.

2.73    [0..n]   +++ Structured          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.

2.74    [0..1]   ++++ Referred
                 Document Information

2.80    [0..1]   ++++ Referred
                 Document Related
                 Date

2.81    [0..n]   ++++ Referred
                 Document Amount

2.87    [0..1]   ++++ Creditor
                 Reference Information

2.93    [0..1]   ++++ Invoicer

2.94    [0..1]   ++++ Invoicee

2.95    [0..1]   ++++ Additional
                 Remittance
                 Information




        Page 65 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.4    CSM - Bank CT Reject (pacs.002.001.02)

         From CSM 1 to Bank 1.

         If the message does not conform to the ISO xsd schema then contact CSM 1.



 Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                 Error Code   Action
                                          Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 1,
                  Identification                                 must be unique over
                                                                 time for this message
                                                                 type (CT Reject).

 1.2     [1..1]   ++ Creation Date                               The date and time the
                  Time                                           message has been
                                                                 created

 1.3     [0..1]   ++ Initiating Party                            Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                            Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                                Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                              Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent    Usage rule:            Absent.
                                          Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent     Usage rule:            Present, contains the
                                          Only BIC is allowed.   BIC of Bank 1




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                            Message Identification
                  Identification                                 of the original Credit
                                                                 Transfer message as
                                                                 sent by Bank 1

 2.2     Or}      ++ Network File Name                           If no Original Message
                                                                 Identification is
                                                                 available then
                                                                 Network File Name is
                                                                 filled.

 2.3     [1..1]   ++ Original Message                            Message name of the
                  Name Identification                            original Credit
                                                                 Transfer message:
                                                                 'pacs.008.001.01'.

 2.4     [0..1]   ++ Original Creation                           Only used for additio-
                  Date and Time                                  nal optional services

 2.5     [0..1]   ++ File Originator                             Only used for additio-
                                                                 nal optional services

 2.6     [0..1]   ++ Original Number of                          Only used for additio-
                  Transactions                                   nal optional services

 2.7     [0..1]   ++ Original Control                            Only used for additio-
                  Sum                                            nal optional services




         Page 66 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

2.8     [0..1]   ++ Group Status         (R1 Type of R            Present, value =
                                         Message)                 'RJCT' or 'PART'.
                                         Usage rule:            RJCT means that the
                                         Only 'RJCT' and 'PART' whole original Credit
                                         are allowed.           Transfer message is
                                                                rejected. The rejected
                                                                transactions can be
                                                                present or absent
                                                                (0..n Transaction
                                                                Information And
                                                                Status).
                                                                  PART means that
                                                                  some transactions of
                                                                  the original Credit
                                                                  Transfer message are
                                                                  rejected. The rejected
                                                                  transactions follow in
                                                                  Transaction
                                                                  Information And
                                                                  Status (1..n).

2.9     [0..n]   ++ Status Reason        Usage rule:              Exactly one
                 Information             Only one occurrence      occurrence is present,
                                         of 'Status Reason        either in Original
                                         Information' is          Group Information
                                         allowed.                 and Status or in every
                                         Usage rule:              Transaction
                                         'Status Reason           Information and
                                         Information' must be     Status.
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in
                                         'Transaction
                                         Information and
                                         Status'.

2.10    [0..1]   +++ Status Originator Mandatory                  BIC or Name of
                                         (R2 Identification of    CSM 1.
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the Bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

2.11    [0..1]   +++ Status Reason       Mandatory                Either Code or
                                         (R3 Reason Code for      Proprietary is present
                                         Non-Acceptance)

2.12    {Or      ++++ Code               Possible values are:     If present, contains
                                         (reject) AC01, AG02,     one of the approved
                                         MD03, MS03, RC01         SEPA Credit Transfer
                                         and TM01.                reject reasons (AC01,
                                                                  AG02, MD03, MS03
                                                                  RC01 and TM01).

2.13    Or}      ++++ Proprietary        Usage rule:              If present, contains
                                         To be used to specify    one of the approved
                                         the regulatory reason,   SEPA Credit Transfer
                                         using „RR01‟.            reject reasons (RR01).

2.14    [0..n]   +++ Additional Status                            Only used for additio-
                 Reason Information                               nal optional services

2.15    [0..n]   ++ Number of Trans-                              Only used for additio-
                 actions Per Status                               nal optional services




        Page 67 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                       Requirements              ditional specifications




3.0     [0..n]   + Transaction
                 Information and
                 Status

3.1     [0..1]   ++ Status             Mandatory                 Assigned by CSM 1,
                 Identification        (R5 Specific reference    must be unique over
                                       of the bank that          time for this message
                                       initiated the reject)     type (CT Reject).

3.2     [0..1]   ++ Original Payment                             Only used for additio-
                 Information                                     nal optional services
                 Identification

3.3     [0..1]   ++ Original           Usage rule:               If present, copied
                 Instruction           Mandatory if provided     from the original
                 Identification        in the original           transaction.
                                       instruction.

3.4     [0..1]   ++ Original End To    Mandatory                 Copied from the
                 End Identification                              original transaction.

3.5     [0..1]   ++ Original           Mandatory                 Copied from the
                 Transaction           Usage rule:               original transaction.
                 Identification        Must contain a
                                       reference that is
                                       unique over time.

3.6     [0..1]   ++ Transaction Status (R1 Type of R             Present, value =
                                       message)                  „RJCT‟
                                       Usage rule:
                                       Only 'RJCT' is allowed.

3.7     [0..n]   ++ Status Reason      Usage rule:               Exactly one
                 Information           Only one occurrence       occurrence is present,
                                       of 'Status Reason         either in Original
                                       Information' is           Group Information
                                       allowed.                  and Status or in every
                                       Usage rule:               Transaction Infor-
                                       'Status Reason Infor-     mation and Status.
                                       mation' must be
                                       present either in
                                       'Original Group Infor-
                                       mation and Status' or
                                       in 'Transaction Infor-
                                       mation and Status'.

3.8     [0..1]   +++ Status Originator Mandatory                 BIC or Name of
                                       (R2 Identification of     CSM 1.
                                       the Type of Party that
                                       initiated the reject)
                                       Usage rule:
                                       Limited to BIC to
                                       identify the bank or
                                       CSM originating the
                                       status or „Name‟ to
                                       indicate the CSM when
                                       it has no BIC.

3.9     [0..1]   +++ Status Reason     Mandatory                 Either Code or
                                       (R3 Reason Code for       Proprietary is present
                                       Non-Acceptance)

3.10    {Or      ++++ Code             Possible values are:      If present, contains
                                       (reject) AC01, AG02,      one of the approved
                                       MD03, MS03, RC01          SEPA Credit Transfer
                                       and TM01.                 reject reasons (AC01,
                                                                 AG02, MD03, MS03
                                                                 RC01 and TM01).




        Page 68 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                 Error Code   Action
                                         Requirements               ditional specifications

3.11    Or}      ++++ Proprietary        Usage rule:                If present, contains
                                         To be used to specify      one of the approved
                                         the regulatory reason,     SEPA Credit Transfer
                                         using the code „RR01‟.     reject reasons (RR01).

3.12    [0..n]   +++ Additional Status                              Only used for additio-
                 Reason Information                                 nal optional services

3.13    [0..n]   ++ Charges                                         Only used for additio-
                 Information                                        nal optional services

3.14    [0..1]   ++ Acceptance Date                                 Only used for additio-
                 Time                                               nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:                Absent.
                                         Only BIC is allowed.

3.16    [0..1]   ++ Instructed Agent     Usage rule:                Absent.
                                         Only BIC is allowed.

3.17    [0..1]   ++ Original           Mandatory                    All following data, if
                 Transaction Reference (An exact copy of all        present, has been
                                       attributes of the            copied from the
                                       received DS-02 which         original Credit
                                       is being returned)           Transfer message.
                                         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.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the
                 Settlement Amount       credit transfer in Euro)

3.19    [0..1]   +++ Amount                                         Only used for additio-
                                                                    nal optional services

3.24    [0..1]   +++ Interbank           (AT-42 Settlement
                 Settlement Date         Date of the credit
                                         transfer)

3.25    {Or      +++ Requested                                      Only used for additio-
                 Execution Date                                     nal optional services

3.26    Or}      +++ Requested                                      Only used for additio-
                 Collection Date                                    nal optional services

3.27    [0..1]   +++ Creditor Scheme                                Only used for additio-
                 Information                                        nal optional services

3.28    [0..1]   +++ Settlement
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                 Only used for additio-
                                                                    nal optional services

3.71    [0..1]   +++ Remittance          (AT-05 Remittance
                 Information             information)

3.96    [0..1]   +++ Ultimate Debtor     (AT-08 Originator          Will be considered for
                                         Reference Party)           inclusion in a future
                                                                    version as AT-08
                                                                    Originator Reference
                                                                    Party




        Page 69 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                       Requirements            ditional specifications

3.97    [0..1]   +++ Debtor            (AT-02 Name of the
                                       Originator)
                                       (AT-03 Address of the
                                       Originator)
                                       (AT-10 Originator
                                       identification code)

3.98    [0..1]   +++ Debtor Account    (AT-01 IBAN of the
                                       Originator)

3.99    [0..1]   +++ Debtor Agent      (AT-06 BIC code of
                                       the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                              Only used for additio-
                 Account                                       nal optional services

3.101   [0..1]   +++ Creditor Agent    (AT-23 BIC code of
                                       the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                            Only used for additio-
                 Account                                       nal optional services

3.103   [0..1]   +++ Creditor          (AT-21 Name of the
                                       Beneficiary)
                                       (AT-22 Address of the
                                       Beneficiary
                                       (AT-24 Beneficiary
                                       identification code)

3.104   [0..1]   +++ Creditor Account (AT-20 IBAN of the
                                      Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary      Will be considered for
                                       Reference Party)        inclusion in a future
                                                               version as AT-28
                                                               Beneficiary Reference
                                                               Party




        Page 70 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.5    CSM - Bank CT Positive Status Report (pacs.002.001.02)

         From CSM 1 to Bank 1.

         This message is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA
         Core message.

         If the message does not conform to the ISO xsd schema the whole message will be rejected, the
         required action is to contact CSM 1.



 Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                 Error Code   Action
                                          Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 1,
                  Identification                                 must be unique over
                                                                 time for this message
                                                                 type (CT Positive
                                                                 Status Report).

 1.2     [1..1]   ++ Creation Date                               The date and time the
                  Time                                           message has been
                                                                 created

 1.3     [0..1]   ++ Initiating Party                            Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                            Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                                Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                              Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent    Usage rule:            Absent.
                                          Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent     Usage rule:            Present, contains the
                                          Only BIC is allowed.   BIC of Bank 1.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                            Present, Message
                  Identification                                 Identification of the
                                                                 original Credit
                                                                 Transfer message as
                                                                 sent by Bank 1.

 2.2     Or}      ++ Network File Name                           Absent.

 2.3     [1..1]   ++ Original Message                            Value =
                  Name Identification                            'pacs.008.001.01'

 2.4     [0..1]   ++ Original Creation                           Only used for additio-
                  Date and Time                                  nal optional services

 2.5     [0..1]   ++ File Originator                             Only used for additio-
                                                                 nal optional services

 2.6     [0..1]   ++ Original Number of                          Optional. Number Of
                  Transactions                                   Transactions of the
                                                                 original Credit
                                                                 Transfer message.

 2.7     [0..1]   ++ Original Control                            Only used for additio-
                  Sum                                            nal optional services




         Page 71 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element      SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                      Requirements             ditional specifications

2.8     [0..1]   ++ Group Status      (R1 Type of R            Present.
                                      Message)                 Allowed values:
                                      Usage rule:            „ACTC‟, 'ACSC' and
                                      Only 'RJCT' and 'PART' 'PART'.
                                      are allowed.
                                                               ACTC means that the
                                                               original Credit
                                                               Transfer message has
                                                               been successfully
                                                               validated (ready for
                                                               further processing).
                                                               ACSC means that all
                                                               transactions of the
                                                               original Credit
                                                               Transfer message
                                                               have been settled.
                                                               PART means that part
                                                               of the transactions of
                                                               the original Credit
                                                               Transfer message
                                                               have been settled.
                                                               The validated (ACTC)
                                                               or settled
                                                               (ACSC/PART)
                                                               transactions can be
                                                               present or absent:
                                                               0..n Transaction
                                                               Information and
                                                               Status.

2.9     [0..n]   ++ Status Reason     Usage rule:              Exactly one
                 Information          Only one occurrence      occurrence is present.
                                      of 'Status Reason
                                      Information' is
                                      allowed.
                                      Usage rule:
                                      'Status Reason
                                      Information' must be
                                      present either in
                                      'Original Group
                                      Information and
                                      Status' or in
                                      'Transaction
                                      Information and
                                      Status'.

2.10    [0..1]   +++ Status Originator Mandatory               Present, the BIC or
                                      (R2 Identification of    Name of CSM 1.
                                      the Type of Party that
                                      initiated the reject)
                                      Usage rule:
                                      Limited to BIC to
                                      identify the Bank or
                                      CSM originating the
                                      status or „Name‟ to
                                      indicate the CSM when
                                      it has no BIC.

2.11    [0..1]   +++ Status Reason    Mandatory                Absent if Group Status
                                      (R3 Reason Code for      is „ACTC‟.
                                      Non-Acceptance)          Present if Group
                                                               Status is „ACSC‟ or
                                                               „PART‟.

2.12    {Or      ++++ Code            Possible values are:     Contains the code
                                      (reject) AC01, AG02,     'NARR' (= Narrative).
                                      MD03, MS03, RC01
                                      and TM01.




        Page 72 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

2.13    Or}      ++++ Proprietary        Usage rule:            Absent.
                                         To be used to specify
                                         the regulatory reason,
                                         using „RR01‟.

2.14    [0..n]   +++ Additional Status                            If Group Status is
                 Reason Information                               „ACSC‟ or „PART‟,
                                                                  three occurrences are
                                                                  present, for
                                                                  settlement date,
                                                                  settled amount and
                                                                  settlement reference:
                                                                  1./INTRBKSTTLMDT/
                                                                  YYYY-MM-DD
                                                                  2./TTLINTRBKSTTLM
                                                                  AMT/<alpha-3
                                                                  currency
                                                                  code><amount>
                                                                  3./STTLMREF/<ref
                                                                  max. 16 positions>
                                                                  Note that the
                                                                  presence of
                                                                  Additional Status
                                                                  Reason Information
                                                                  is against ISO's
                                                                  StatusReason-
                                                                  nformationRule.

2.15    [0..n]   ++ Number of                                     One occurrence is
                 Transactions Per                                 present if Group
                 Status                                           Status is 'PART'.

2.16    [1..1]   +++ Detailed Number                              Contains the number
                 Of Transactions                                  of settled
                                                                  transactions.
                                                                  Note that the settled
                                                                  transactions
                                                                  themselves (3.0) may
                                                                  be absent, which is
                                                                  not fully in line with
                                                                  ISO.

2.17    [1..1]   +++ Detailed Status                              Contains code 'ACSC'
                                                                  (= settled).

2.18    [0..1]   +++ Detailed Control
                 Sum




3.0     [0..n]   + Transaction                                    The validated/settled
                 Information and                                  transactions can be
                 Status                                           present or absent.

3.1     [0..1]   ++ Status               Mandatory                Present, Assigned by
                 Identification          (R5 Specific reference   CSM 1, must be
                                         of the bank that         unique over time for
                                         initiated the reject)    this message type (CT
                                                                  Positive Status
                                                                  Report).

3.2     [0..1]   ++ Original Payment                              Only used for additio-
                 Information                                      nal optional services
                 Identification

3.3     [0..1]   ++ Original             Usage rule:              Instruction
                 Instruction             Mandatory if provided    Identification of the
                 Identification          in the original          original transaction as
                                         instruction.             sent by Bank 1.




        Page 73 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

3.4     [0..1]   ++ Original End To      Mandatory                Present, End To End
                 End Identification                               Identification of the
                                                                  original transaction as
                                                                  sent by Bank 1.

3.5     [0..1]   ++ Original             Mandatory                Present, Transaction
                 Transaction             Usage rule:              Identification of the
                 Identification          Must contain a           original transaction as
                                         reference that is        sent by Bank 1.
                                         unique over time.

3.6     [0..1]   ++ Transaction Status (R1 Type of R              Present.
                                       message)                   The value is
                                         Usage rule:             - „ACTC‟ if Group
                                         Only 'RJCT' is allowed.   Status is „ACTC‟;
                                                                  - „ACSC‟ if Group
                                                                    Status is „ACSC‟ or
                                                                    „PART‟.

3.7     [0..n]   ++ Status Reason        Usage rule:              Absent.
                 Information             Only one occurrence
                                         of 'Status Reason
                                         Information' is
                                         allowed.
                                         Usage rule:
                                         'Status Reason
                                         Information' must be
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in
                                         'Transaction
                                         Information and
                                         Status'.

3.8     [0..1]   +++ Status Originator Mandatory
                                         (R2 Identification of
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

3.9     [0..1]   +++ Status Reason       Mandatory
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:
                                         (reject) AC01, AG02,
                                         MD03, MS03, RC01
                                         and TM01.

3.11    Or}      ++++ Proprietary        Usage rule:
                                         To be used to specify
                                         the regulatory reason,
                                         using the code „RR01‟.

3.12    [0..n]   +++ Additional Status
                 Reason Information

3.13    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.14    [0..1]   ++ Acceptance Date                               Only used for additio-
                 Time                                             nal optional services




        Page 74 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                 Error Code   Action
                                         Requirements               ditional specifications

3.15    [0..1]   ++ Instructing Agent    Usage rule:                Absent.
                                         Only BIC is allowed.


3.16    [0..1]   ++ Instructed Agent     Usage rule:                Absent.
                                         Only BIC is allowed.


3.17    [0..1]   ++ Original             Mandatory                  Optional.
                 Transaction Reference   (An exact copy of all      If present, all
                                         attributes of the          following data has
                                         received DS-02 which       been copied from the
                                         is being returned)         original Credit
                                         Usage rule:                Transfer message.
                                         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.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the
                 Settlement Amount       credit transfer in Euro)

3.19    [0..1]   +++ Amount                                         Only used for additio-
                                                                    nal optional services

3.24    [0..1]   +++ Interbank           (AT-42 Settlement
                 Settlement Date         Date of the credit
                                         transfer)

3.25    {Or      +++ Requested                                      Only used for additio-
                 Execution Date                                     nal optional services

3.26    Or}      +++ Requested                                      Only used for additio-
                 Collection Date                                    nal optional services

3.27    [0..1]   +++ Creditor Scheme                                Only used for additio-
                 Information                                        nal optional services

3.28    [0..1]   +++ Settlement
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                 Only used for additio-
                                                                    nal optional services

3.71    [0..1]   +++ Remittance          (AT-05 Remittance
                 Information             information)

3.96    [0..1]   +++ Ultimate Debtor     (AT-08 Originator          Will be considered for
                                         Reference Party)           inclusion in a future
                                                                    version as AT-08
                                                                    Originator Reference
                                                                    Party

3.97    [0..1]   +++ Debtor              (AT-02 Name of the
                                         Originator)
                                         (AT-03 Address of the
                                         Originator)
                                         (AT-10 Originator
                                         identification code)

3.98    [0..1]   +++ Debtor Account      (AT-01 IBAN of the
                                         Originator)




        Page 75 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                        Requirements            ditional specifications

3.99    [0..1]   +++ Debtor Agent       (AT-06 BIC code of
                                        the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                               Only used for additio-
                 Account                                        nal optional services

3.101   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.103   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.104   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary       Will be considered for
                                       Reference Party)         inclusion in a future
                                                                version as AT-28
                                                                Beneficiary Reference
                                                                Party




        Page 76 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.6    Inter CSM CT Reject (pacs.002.001.02)

         From CSM 2 to CSM 1

         (Only for technical rejects, e.g. message cannot be read, or does not comply with the agreed
         format, specifically in relation to pacs.008).

         If the message does not conform to the ISO xsd schema then contact CSM 2.



 Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                    Error Code   Action
                                          Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 2,        Must be unique, for                    contact CSM 2
                  Identification                                 must be unique over       the combination of
                                                                 time for this message     sending party (CSM 2)
                                                                 type (CT Reject).         and Message
                                                                                           Identification for this
                                                                                           message type (CT
                                                                                           Reject).

 1.2     [1..1]   ++ Creation Date                               The date and time the Must be a valid date                       contact CSM 2
                  Time                                           message has been      and time
                                                                 created

 1.3     [0..1]   ++ Initiating Party                            Not applicable to pacs

 1.4     [0..1]   ++ Forwarding Agent                            Not applicable to pacs

 1.5     [0..1]   ++ Debtor Agent                                Not applicable to pacs

 1.6     [0..1]   ++ Creditor Agent                              Not applicable to pacs

 1.7     [0..1]   ++ Instructing Agent    Usage rule:            Absent.                   Must be absent                         contact CSM 2
                                          Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent     Usage rule:            Absent.                   Must be absent                         contact CSM 2
                                          Only BIC is allowed.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                            Message identification    If present, must                       contact CSM 2
                  Identification                                 of the original           match with the
                                                                 message as sent by        corresponding value in
                                                                 CSM 1                     the original Credit
                                                                                           Transfer

 2.2     Or}      ++ Network File Name                           If no Original Message    If present, must                       contact CSM 2
                                                                 Identification is         match with a network
                                                                 available then            file name of a sent
                                                                 Network File Name is      file.
                                                                 filled.

                                                                                           If present then                        contact CSM 2
                                                                                           Transaction
                                                                                           Information And
                                                                                           Status may not be
                                                                                           present.

 2.3     [1..1]   ++ Original Message                                                      Must equal                             contact CSM 2
                  Name Identification                                                      'pacs.008.001.01'

 2.4     [0..1]   ++ Original Creation                           Only used for additio-
                  Date and Time                                  nal optional services

 2.5     [0..1]   ++ File Originator                             Only used for additio-
                                                                 nal optional services

 2.6     [0..1]   ++ Original Number of                          Only used for additio-
                  Transactions                                   nal optional services




         Page 77 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                       Requirements             ditional specifications

2.7     [0..1]   ++ Original Control                            Only used for additio-
                 Sum                                            nal optional services

2.8     [0..1]   ++ Group Status       (R1 Type of R            Value = „RJCT‟ or         Value must be either                  In case no
                                       Message)                 „PART‟.                   'RJCT' or 'PART'                      other usage of
                                       Usage rule:            RJCT means that the                                               pacs.002.001.
                                       Only 'RJCT' and 'PART' whole original                                                    02 is agreed
                                       are allowed.           message is rejected.                                              contact CSM 2
                                                              The rejected
                                                              transactions are
                                                              present or absent
                                                              (0..n Transaction
                                                              Information And
                                                              Status).
                                                                PART means that
                                                                some transactions of
                                                                the original message
                                                                are rejected. The
                                                                rejected transactions
                                                                follow in Transaction
                                                                Information And
                                                                Status (1..n).

                                                                                          If value = 'PART', at                 contact CSM 2
                                                                                          least one Transaction
                                                                                          Information and
                                                                                          Status must be
                                                                                          present

                                                                                          Must be present                       contact CSM 2

2.9     [0..n]   ++ Status Reason      Usage rule:                                        Must be present in                    contact CSM 2
                 Information           Only one occurrence                                either the Original
                                       of 'Status Reason                                  Group Information
                                       Information' is                                    and Status or the
                                       allowed.                                           Transaction
                                       Usage rule:                                        Information and
                                       'Status Reason                                     Status.
                                       Information' must be
                                       present either in
                                       'Original Group Infor-
                                       mation and Status' or
                                       in 'Transaction
                                       Information and
                                       Status'.

                                                                                          If present, only one                  contact CSM 2
                                                                                          occurrence of 'Status
                                                                                          Reason Information' is
                                                                                          allowed

2.10    [0..1]   +++ Status Originator Mandatory                BIC or Name of            Must be present                       contact CSM 2
                                       (R2 Identification of    CSM 2.
                                       the Type of Party that
                                       initiated the reject)
                                       Usage rule:
                                       Limited to BIC to
                                       identify the Bank or
                                       CSM originating the
                                       status or „Name‟ to
                                       indicate the CSM when
                                       it has no BIC.

                                                                                          Either BIC or Name                    contact CSM 2
                                                                                          must be present

                                                                                          If present with BIC,                  contact CSM 2
                                                                                          must contain a BIC
                                                                                          from the BIC-directory

2.11    [0..1]   +++ Status Reason     Mandatory                                          Must be present                       contact CSM 2
                                       (R3 Reason Code for
                                       Non-Acceptance)




        Page 78 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                   Error Code   Action
                                         Requirements              ditional specifications

2.12    {Or      ++++ Code               Possible values are:                                If present, must be                   contact CSM 2
                                         (reject) AC01, AG02,                                one of the approved
                                         MD03, MS03, RC01                                    SEPA Credit Transfer
                                         and TM01.                                           reject reasons (AC01,
                                                                                             AG02, MD03, MS03,
                                                                                             RC01 and TM01)

2.13    Or}      ++++ Proprietary        Usage rule:                                         If present, must be                   contact CSM 2
                                         To be used to specify                               one of the approved
                                         the regulatory reason,                              SEPA Credit Transfer
                                         using „RR01‟.                                       reject reasons (RR01)

2.14    [0..n]   +++ Additional Status                             Only used for additio-
                 Reason Information                                nal optional services

2.15    [0..n]   ++ Number of Trans-                               Only used for additio-
                 actions Per Status                                nal optional services




3.0     [0..n]   + Transaction                                                               If Group Status =                     contact CSM 2
                 Information and                                                             'PART', at least one
                 Status                                                                      Transaction
                                                                                             Information and
                                                                                             Status must be
                                                                                             present

                                                                                             If present, then
                                                                                             Network File Name
                                                                                             may not be present.

3.1     [0..1]   ++ Status               Mandatory                 Assigned by CSM 2,        The combination of                    contact CSM 2
                 Identification          (R5 Specific reference    must be unique over       Status Originator
                                         of the bank that          time for this message     (2.10 or 3.8) and
                                         initiated the reject)     type (CT Reject).         Status Identification
                                                                                             must be unique, for
                                                                                             this message type (CT
                                                                                             Reject).

                                                                                             Must be present                       contact CSM 2

3.2     [0..1]   ++ Original Payment                               Only used for additio-
                 Information                                       nal optional services
                 Identification

3.3     [0..1]   ++ Original             Usage rule:               If present, copied        If present, must                      contact CSM 2
                 Instruction             Mandatory if provided     from the original         match with the
                 Identification          in the original           transaction as sent by    corresponding value in
                                         instruction.              CSM 1                     the original Credit
                                                                                             Transfer

3.4     [0..1]   ++ Original End To      Mandatory                 Copied from the           Must match with the                   contact CSM 2
                 End Identification                                original transaction as   corresponding value in
                                                                   sent by CSM 1             the original Credit
                                                                                             Transfer

                                                                                             Must be present                       contact CSM 2

3.5     [0..1]   ++ Original             Mandatory                 Copied from the           Must match with the                   contact CSM 2
                 Transaction             Usage rule:               original transaction as   corresponding value in
                 Identification          Must contain a            sent by CSM 1             the original Credit
                                         reference that is                                   Transfer
                                         unique over time.

                                                                                             Must be present                       contact CSM 2

3.6     [0..1]   ++ Transaction Status (R1 Type of R               Value = „RJCT‟            Must equal 'RJCT'                     contact CSM 2
                                       message)
                                         Usage rule:
                                         Only 'RJCT' is allowed.




        Page 79 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                         Requirements             ditional specifications

3.7     [0..n]   ++ Status Reason        Usage rule:                                        Must be present in                    contact CSM 2
                 Information             Only one occurrence                                either the Original
                                         of 'Status Reason                                  Group Information
                                         Information' is                                    and Status or the
                                         allowed.                                           Transaction
                                         Usage rule:                                        Information and
                                         'Status Reason                                     Status.
                                         Information' must be
                                         present either in
                                         'Original Group Infor-
                                         mation and Status' or
                                         in 'Transaction Infor-
                                         mation and Status'.

                                                                                            If present, only one                  contact CSM 2
                                                                                            occurrence of 'Status
                                                                                            Reason Information' is
                                                                                            allowed

3.8     [0..1]   +++ Status Originator Mandatory                  BIC or Name of            Must be present                       contact CSM 2
                                         (R2 Identification of    CSM 2.
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

                                                                                            Either BIC or Name                    contact CSM 2
                                                                                            must be present

                                                                                            If present with BIC,                  contact CSM 2
                                                                                            must contain a BIC
                                                                                            from the BIC-directory

3.9     [0..1]   +++ Status Reason       Mandatory
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:                               If present must be one                contact CSM 2
                                         (reject) AC01, AG02,                               of the approved SEPA
                                         MD03, MS03, RC01                                   Credit Transfer reject
                                         and TM01.                                          reasons (AC01, AG02,
                                                                                            MD03, MS03, RC01
                                                                                            and TM01)

3.11    Or}      ++++ Proprietary        Usage rule:                                        If present must be one                contact CSM 2
                                         To be used to specify                              of the approved SEPA
                                         the regulatory reason,                             Credit Transfer reject
                                         using the code „RR01‟.                             reasons (RR01)

3.12    [0..n]   +++ Additional Status                            Only used for additio-
                 Reason Information                               nal optional services

3.13    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.14    [0..1]   ++ Acceptance Date                               Only used for additio-
                 Time                                             nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:              Absent                    Must be absent                        contact CSM 2
                                         Only BIC is allowed.

3.16    [0..1]   ++ Instructed Agent     Usage rule:              Absent                    Must be absent                        contact CSM 2
                                         Only BIC is allowed.




        Page 80 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error Code   Action
                                         Requirements               ditional specifications

3.17    [0..1]   ++ Original             Mandatory                                            Must be present                       contact CSM 2
                 Transaction Reference   (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.

                                                                                              All mandatory                         contact CSM 2
                                                                                              elements of the
                                                                                              original Credit
                                                                                              Transfer must be
                                                                                              present

                                                                                              All elements supplied                 contact CSM 2
                                                                                              must match with the
                                                                                              corresponding value in
                                                                                              the original Credit
                                                                                              Transfer.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the
                 Settlement Amount       credit transfer in Euro)

3.19    [0..1]   +++ Amount                                         Only used for additio-
                                                                    nal optional services

3.24    [0..1]   +++ Interbank           (AT-42 Settlement
                 Settlement Date         Date of the credit
                                         transfer)

3.25    {Or      +++ Requested                                      Only used for additio-
                 Execution Date                                     nal optional services

3.26    Or}      +++ Requested                                      Only used for additio-
                 Collection Date                                    nal optional services

3.27    [0..1]   +++ Creditor Scheme                                Only used for additio-
                 Information                                        nal optional services

3.28    [0..1]   +++ Settlement
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                 Only used for additio-
                                                                    nal optional services

3.71    [0..1]   +++ Remittance          (AT-05 Remittance
                 Information             information)

3.96    [0..1]   +++ Ultimate Debtor     (AT-08 Originator          Will be considered for
                                         Reference Party)           inclusion in a future
                                                                    version as AT-08
                                                                    Originator Reference
                                                                    Party

3.97    [0..1]   +++ Debtor              (AT-02 Name of the
                                         Originator)
                                         (AT-03 Address of the
                                         Originator)
                                         (AT-10 Originator
                                         identification code)

3.98    [0..1]   +++ Debtor Account      (AT-01 IBAN of the
                                         Originator)




        Page 81 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                        Requirements            ditional specifications

3.99    [0..1]   +++ Debtor Agent       (AT-06 BIC code of
                                        the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                               Only used for additio-
                 Account                                        nal optional services

3.101   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.103   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.104   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary       Will be considered for
                                       Reference Party)         inclusion in a future
                                                                version as AT-28
                                                                Beneficiary Reference
                                                                Party




        Page 82 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.7    Inter CSM CT Positive Status Report (pacs.002.001.02)

         From CSM 2 to CSM 1.

         This message is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA
         Core message.

         If the message does not conform to the ISO xsd schema the whole message will be rejected, the
         required action is to contact CSM 2.



 Index   Mult.    Message element        SEPA Core              Comments and ad-          Checks                    Error Code   Action
                                         Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                    Assigned by CSM 2,        Must be unique, for                    contact CSM 2
                  Identification                                must be unique over       the combination of
                                                                time for this message     sending party (CSM 2)
                                                                type (CT Positive         and Message
                                                                Status Report).           Identification for this
                                                                                          message type (CT
                                                                                          Positive Status
                                                                                          Report).

 1.2     [1..1]   ++ Creation Date                              The date and time the Must be a valid date                       contact CSM 2
                  Time                                          message has been      and time
                                                                created

 1.3     [0..1]   ++ Initiating Party                           Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                           Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                               Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                             Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent   Usage rule:            Absent.                   Must be absent                         contact CSM 2
                                         Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent    Usage rule:            Absent.                   Must be absent                         contact CSM 2
                                         Only BIC is allowed.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                           Present, Message          Must be present                        contact CSM 2
                  Identification                                Identification of the
                                                                original Credit
                                                                Transfer message as
                                                                sent by CSM 1.

                                                                                          Must match with the                    contact CSM 2
                                                                                          corresponding value in
                                                                                          the original Credit
                                                                                          Transfer

 2.2     Or}      ++ Network File Name                          Absent.

 2.3     [1..1]   ++ Original Message                           Value =                   Must equal                             contact CSM 2
                  Name Identification                           'pacs.008.001.01'         'pacs.008.001.01'

 2.4     [0..1]   ++ Original Creation                          Only used for additio-
                  Date and Time                                 nal optional services

 2.5     [0..1]   ++ File Originator                            Only used for additio-
                                                                nal optional services




         Page 83 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                         Requirements             ditional specifications

2.6     [0..1]   ++ Original Number of                            Optional.                 If present, must                      contact CSM 2
                 Transactions                                     Number Of                 match with the
                                                                  Transactions of the       corresponding value in
                                                                  original Credit           the original Credit
                                                                  Transfer message.         Transfer

2.7     [0..1]   ++ Original Control                              Only used for additio-
                 Sum                                              nal optional services

2.8     [0..1]   ++ Group Status         (R1 Type of R            Present.                  Must be present.                      contact CSM 2
                                         Message)                 Allowed values:
                                         Usage rule:            „ACTC‟, 'ACSC' and
                                         Only 'RJCT' and 'PART' 'PART'.
                                         are allowed.
                                                                  ACTC means that the
                                                                  original Credit
                                                                  Transfer message has
                                                                  been successfully
                                                                  validated (ready for
                                                                  further processing).
                                                                  ACSC means that all
                                                                  transactions of the
                                                                  original Credit
                                                                  Transfer message
                                                                  have been settled.
                                                                  PART means that part
                                                                  of the transactions of
                                                                  the original Credit
                                                                  Transfer message
                                                                  have been settled.
                                                                  The validated (ACTC)
                                                                  or settled
                                                                  (ACSC/PART)
                                                                  transactions can be
                                                                  present or absent:
                                                                  0..n Transaction
                                                                  Information and
                                                                  Status.

                                                                                            Must equal „ACTC‟,                    contact CSM 2
                                                                                            'ACSC' or 'PART'

2.9     [0..n]   ++ Status Reason        Usage rule:              Exactly one               Exactly one                           contact CSM 2
                 Information             Only one occurrence      occurrence is present.    occurrence must be
                                         of 'Status Reason                                  present.
                                         Information' is
                                         allowed.
                                         Usage rule:
                                         'Status Reason
                                         Information' must be
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in
                                         'Transaction
                                         Information and
                                         Status'.

2.10    [0..1]   +++ Status Originator Mandatory                  Present, the BIC or       Either BIC or Name                    contact CSM 2
                                         (R2 Identification of    name of CSM 2.            must be present
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the Bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.




        Page 84 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                   Error Code   Action
                                         Requirements           ditional specifications

                                                                                          If present with BIC,                  contact CSM 2
                                                                                          must contain a BIC
                                                                                          from the BIC-directory

2.11    [0..1]   +++ Status Reason       Mandatory              Absent if Group Status
                                         (R3 Reason Code for    is „ACTC‟.
                                         Non-Acceptance)        Present if Group
                                                                Status is „ACSC‟ or
                                                                „PART‟.

2.12    {Or      ++++ Code               Possible values are:   Contains the code         Must be present if                    contact CSM 2
                                         (reject) AC01, AG02,   'NARR' (= Narrative). Group Status is „ACSC‟
                                         MD03, MS03, RC01                                 or „PART‟.
                                         and TM01.

                                                                                          If present, must                      contact CSM 2
                                                                                          contain the value
                                                                                          „NARR‟

2.13    Or}      ++++ Proprietary        Usage rule:            Absent.
                                         To be used to specify
                                         the regulatory reason,
                                         using „RR01‟.

2.14    [0..n]   +++ Additional Status                          If Group Status is        Settlement date must                  contact CSM 2
                 Reason Information                             „ACSC‟ or „PART‟, two     be present if Group
                                                                occurrences are           Status is „ACSC‟ or
                                                                present, for              „PART‟.
                                                                settlement date and
                                                                settled amount:
                                                                1./INTRBKSTTLMDT/
                                                                YYYY-MM-DD
                                                                2./TTLINTRBKSTTLM
                                                                AMT/<alpha-3
                                                                currency
                                                                code><amount>
                                                                Note that the
                                                                presence of
                                                                Additional Status
                                                                Reason Information
                                                                is against ISO's
                                                                StatusReason-
                                                                InformationRule.

                                                                                          Settlement date must                  contact CSM 2
                                                                                          be a valid date

                                                                                          Settled amount must                   contact CSM 2
                                                                                          be present if Group
                                                                                          Status is „ACSC‟ or
                                                                                          „PART‟.

                                                                                          Currency code must                    contact CSM 2
                                                                                          be "EUR"

                                                                                          Amount must be ≥                      contact CSM 2
                                                                                          0.01

                                                                                          Amount must be ≤                      contact CSM 2
                                                                                          999999999999999.99

                                                                                          Maximum 2 fraction                    contact CSM 2
                                                                                          digits

2.15    [0..n]   ++ Number of                                   One occurrence is         One occurrence must                   contact CSM 2
                 Transactions Per                               present if Group          be present if Group
                 Status                                         Status is 'PART'.         Status is „PART‟




        Page 85 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                        Requirements             ditional specifications

2.16    [1..1]   +++ Detailed Number                             Contains the number
                 Of Transactions                                 of settled
                                                                 transactions.
                                                                 Note that the settled
                                                                 transactions them-
                                                                 selves (3.0) may be
                                                                 absent, which is not
                                                                 fully in line with ISO.

2.17    [1..1]   +++ Detailed Status                             Contains code 'ACSC'      Must contain the value                contact CSM 2
                                                                 (= settled).              „ACSC‟

2.18    [0..1]   +++ Detailed Control
                 Sum




3.0     [0..n]   + Transaction                                   The validated/settled
                 Information and                                 transactions can be
                 Status                                          present or absent.

3.1     [0..1]   ++ Status              Mandatory                Present. Assigned by  Must be present                           contact CSM 2
                 Identification         (R5 Specific reference   CSM 2, must be
                                        of the bank that         unique over time for
                                        initiated the reject)    this message type (CT
                                                                 Positive Status
                                                                 Report).

                                                                                           The combination of                    contact CSM 2
                                                                                           Status Originator
                                                                                           (2.10) and Status
                                                                                           Identification must be
                                                                                           unique

3.2     [0..1]   ++ Original Payment                             Only used for additio-
                 Information                                     nal optional services
                 Identification

3.3     [0..1]   ++ Original            Usage rule:              Instruction               If present, must                      contact CSM 2
                 Instruction            Mandatory if provided    Identification of the     match with the
                 Identification         in the original          original transaction as   corresponding value in
                                        instruction.             sent by CSM 1             the original Credit
                                                                                           Transfer

3.4     [0..1]   ++ Original End To     Mandatory                Present, End To End       Must be present                       contact CSM 2
                 End Identification                              Identification of the
                                                                 original transaction as
                                                                 sent by CSM 1

                                                                                           Must match with the                   contact CSM 2
                                                                                           corresponding value in
                                                                                           the original Credit
                                                                                           Transfer

3.5     [0..1]   ++ Original            Mandatory                Present, Transaction      Must be present                       contact CSM 2
                 Transaction            Usage rule:              Identification of the
                 Identification         Must contain a           original transaction as
                                        reference that is        sent by CSM 1
                                        unique over time.

                                                                                           Must match with the                   contact CSM 2
                                                                                           corresponding value in
                                                                                           the original Credit
                                                                                           Transfer




        Page 86 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                  Error Code   Action
                                         Requirements             ditional specifications

3.6     [0..1]   ++ Transaction Status (R1 Type of R              Present.                  Must be present                      contact CSM 2
                                       message)                   The value is
                                         Usage rule:             - „ACTC‟ if Group
                                         Only 'RJCT' is allowed.   Status is „ACTC‟;
                                                                  - „ACSC‟ if Group
                                                                    Status is „ACSC‟ or
                                                                    „PART‟.

                                                                                            Must equal                           contact CSM 2
                                                                                            - „ACTC‟ if Group
                                                                                              Status is „ACTC‟;
                                                                                            - „ACSC‟ if Group
                                                                                              Status is „ACSC‟ or
                                                                                              „PART‟.

3.7     [0..n]   ++ Status Reason        Usage rule:              Absent.                   Must be absent                       contact CSM 2
                 Information             Only one occurrence
                                         of 'Status Reason
                                         Information' is
                                         allowed.
                                         Usage rule:
                                         'Status Reason
                                         Information' must be
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in 'Trans-
                                         action Information and
                                         Status'.

3.8     [0..1]   +++ Status Originator Mandatory
                                         (R2 Identification of
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

3.9     [0..1]   +++ Status Reason       Mandatory
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:
                                         (reject) AC01, AG02,
                                         MD03, MS03, RC01
                                         and TM01.

3.11    Or}      ++++ Proprietary        Usage rule:
                                         To be used to specify
                                         the regulatory reason,
                                         using the code „RR01‟.

3.12    [0..n]   +++ Additional Status
                 Reason Information

3.13    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.14    [0..1]   ++ Acceptance Date                               Only used for additio-
                 Time                                             nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:              Absent.                   Must be absent                       contact CSM 2
                                         Only BIC is allowed.

3.16    [0..1]   ++ Instructed Agent     Usage rule:              Absent.                   Must be absent                       contact CSM 2
                                         Only BIC is allowed.




        Page 87 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error Code   Action
                                         Requirements               ditional specifications

3.17    [0..1]   ++ Original             Mandatory                  Optional.                 If present, all                       contact CSM 2
                 Transaction Reference   (An exact copy of all      If present, all           mandatory elements
                                         attributes of the          following data has        of the original Credit
                                         received DS-02 which       been copied from the      Transfer must be
                                         is being returned)         original Credit           present
                                         Usage rule:                Transfer message.
                                         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.

                                                                                              All elements supplied                 contact CSM 2
                                                                                              must match with the
                                                                                              corresponding value in
                                                                                              the original Credit
                                                                                              Transfer.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the
                 Settlement Amount       credit transfer in Euro)

3.19    [0..1]   +++ Amount                                         Only used for additio-
                                                                    nal optional services

3.24    [0..1]   +++ Interbank           (AT-42 Settlement
                 Settlement Date         Date of the credit
                                         transfer)

3.25    {Or      +++ Requested                                      Only used for additio-
                 Execution Date                                     nal optional services

3.26    Or}      +++ Requested                                      Only used for additio-
                 Collection Date                                    nal optional services

3.27    [0..1]   +++ Creditor Scheme                                Only used for additio-
                 Information                                        nal optional services

3.28    [0..1]   +++ Settlement
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                 Only used for additio-
                                                                    nal optional services

3.71    [0..1]   +++ Remittance          (AT-05 Remittance
                 Information             information)

3.96    [0..1]   +++ Ultimate Debtor     (AT-08 Originator          Will be considered for
                                         Reference Party)           inclusion in a future
                                                                    version as AT-08
                                                                    Originator Reference
                                                                    Party

3.97    [0..1]   +++ Debtor              (AT-02 Name of the
                                         Originator)
                                         (AT-03 Address of the
                                         Originator)
                                         (AT-10 Originator
                                         identification code)

3.98    [0..1]   +++ Debtor Account      (AT-01 IBAN of the
                                         Originator)

3.99    [0..1]   +++ Debtor Agent        (AT-06 BIC code of
                                         the Originator Bank)




        Page 88 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                        Requirements            ditional specifications

3.100   [0..1]   +++ Debtor Agent                               Only used for additio-
                 Account                                        nal optional services

3.101   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.103   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.104   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary       Will be considered for
                                       Reference Party)         inclusion in a future
                                                                version as AT-28
                                                                Beneficiary Reference
                                                                Party




        Page 89 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.8    Bank - CSM CT Return (pacs.004.001.01)

         From Bank 2 to CSM 2.

         If the message does not conform to the ISO xsd schema the whole message will be rejected with
         Error Code 'MD03'.



 Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                 Error code    Action
                                         Requirements              ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                       Assigned by Bank 2,       The combination of     MD03          reject the
                  Identification                                   must be unique over       Instructing Agent      (duplicate)   message
                                                                   time for this message     (Bank 2) and Message
                                                                   type (CT Return).         Identification must be
                                                                                             unique, for this
                                                                                             message type (CT
                                                                                             Return).

 1.2     [1..1]   ++ Creation Date                                 The date and time the Must be a valid date       MD03          reject the
                  Time                                             message has been      and time                                 message
                                                                   created

 1.3     [0..2]   ++ Authorisation                                 Only used for additio-
                                                                   nal optional services

 1.4     [0..1]   ++ Batch Booking                                 Only used for additio-
                                                                   nal optional services

 1.5     [1..1]   ++ Number Of                                     A maximum of 100000 Must be  100000             MD03          reject the
                  Transactions                                     transactions per                                               message
                                                                   message.

                                                                                             Must equal the         MD03          reject the
                                                                                             number of                            message
                                                                                             transactions in the
                                                                                             message

 1.6     [0..1]   ++ Control Sum                                   Only used for additio-
                                                                   nal optional services

 1.7     [0..1]   ++ Group Return                                  Only used for additio-
                                                                   nal optional services

 1.8     [0..1]   ++ Total Returned      Mandatory                 ISO: must equal the       Must equal the sum of MD03           reject the
                  Interbank Settlement   Usage rule:               sum of all occurrences    all occurrences of                   message
                  Amount                 Only „EUR‟ is allowed.    of Transaction            Transaction
                                                                   Information /             Information /
                                         Usage rule:
                                                                   Returned Interbank        Returned Interbank
                                         Amount must be 0.01
                                                                   Settlement Amount         Settlement Amount
                                         or more and
                                                                   when present
                                         999999999999999.99
                                         or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

                                                                                             Currency Code must     MD03          reject the
                                                                                             be "EUR"                             message

                                                                                             Amount must be ≥       MD03          reject the
                                                                                             0.01                                 message

                                                                                             Amount must be ≤       MD03          reject the
                                                                                             999999999999999.99                   message

                                                                                             Maximum 2 fraction     MD03          reject the
                                                                                             digits                               message




         Page 90 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error code   Action
                                         Requirements               ditional specifications

1.9     [0..1]   ++ Interbank            Mandatory                  The requested             Must be present          MD03         reject the
                 Settlement Date         (AT-R4 Settlement          Settlement Date.                                                message
                                         Date for the Return)       If it is a date in the
                                                                    (near) past, CSM 2
                                                                    will execute as soon
                                                                    as possible.
                                                                    If it is not a Target
                                                                    day, CSM 2 will
                                                                    execute on the first
                                                                    Target day after this
                                                                    date.


                                                                    (As an alternative        Must be a valid date     MD03         reject the
                                                                    CSM 2 may choose to                                             message
                                                                    reject a requested
                                                                    Settlement Date that
                                                                    is in the past and/or
                                                                    not a Target day.)

                                                                                              Must not be too far in   TM01         reject the
                                                                                              the past:                             message
                                                                                              current date – 3
                                                                                              Target days ≤
                                                                                              requested Settlement
                                                                                              Date

                                                                                              Must not be too far in   MD03         reject the
                                                                                              the future:                           message
                                                                                              requested Settlement
                                                                                              Date ≤ current date +
                                                                                              3 Target days

1.10    [1..1]   ++ Settlement
                 Information

1.11    [1..1]   +++ Settlement          Usage rule:                Only the value 'CLRG'     Must contain the value MD03           reject the
                 Method                  Only CLRG, INGA and        is allowed.               'CLRG'.                               message
                                         INDA are allowed.

1.12    [0..1]   +++ Settlement          Usage rule:                Absent. (ISO: If          Must not be present      MD03         reject the
                 Account                 Only 'Identification' is   Settlement Method =                                             message
                                         allowed.                   'CLRG', then
                                                                    Settlement Account is
                                                                    not allowed.)

1.13    [0..1]   +++ Clearing System                                Present. (ISO: If         Must be Present          MD03         reject the
                                                                    Settlement Method =                                             message
                                                                    'CLRG', then Clearing
                                                                    System must be
                                                                    present.)
                                                                    Identifies Clearing
                                                                    System of CSM 2

1.14    {Or      ++++ Clearing                                      Used when Clearing        If present, it must    MD03           reject the
                 System Identification                              System Identification     contain the valid                     message
                                                                    exists for the Clearing   UNIFI code identifying
                                                                    System of CSM 2 in        CSM 2
                                                                    the UNIFI ISO 20022
                                                                    code list

1.15    Or}      ++++ Proprietary                                   Used when no             If present, it must       MD03         reject the
                                                                    Clearing System          contain the valid code                 message
                                                                    Identification exists    as specified by CSM 2
                                                                    for the Clearing
                                                                    System of CSM 2 in
                                                                    UNIFI ISO 20022 code
                                                                    list. Value is specified
                                                                    by CSM 2.




        Page 91 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core              Comments and ad-          Checks                 Error code   Action
                                        Requirements           ditional specifications

1.16    [0..1]   +++ Instructing                               Absent. (ISO: If
                 Reimbursement Agent                           Settlement Method =
                                                               'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.17    [0..1]   +++ Instructing                               Absent. (ISO: If
                 Reimbursement Agent                           Settlement Method =
                 Account                                       'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.18    [0..1]   +++ Instructed Reim-                          Absent. (ISO: If
                 bursement Agent                               Settlement Method =
                                                               'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.19    [0..1]   +++ Instructed Reim-                          Absent. (ISO: If
                 bursement Agent                               Settlement Method =
                 Account                                       'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.20    [0..1]   +++ Third Reim-                               Absent. (ISO: If
                 bursement Agent                               Settlement Method =
                                                               'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.21    [0..1]   +++ Third Reim-                               Absent. (ISO: If
                 bursement Agent                               Settlement Method =
                 Account                                       'CLRG', then Reim-
                                                               bursement agents are
                                                               not allowed.)

1.22    [0..1]   ++ Instructing Agent   Usage rule:            Mandatory. Contains     Must be present          MD03         reject the
                                        Only BIC is allowed.   the BIC of the agent                                          message
                                                               that instructs the next
                                                               party in the chain to
                                                               carry out the (set of)
                                                               instruction(s): Bank 2.

                                                                                         Must contain BIC       MD03         reject the
                                                                                                                             message

                                                                                         Must contain a BIC     RC01         reject the
                                                                                         from the BIC-directory              message

1.23    [0..1]   ++ Instructed Agent    Usage rule:            Absent.                   Must be absent         MD03         reject the
                                        Only BIC is allowed.                                                                 message




2.0     [0..1]   + Original Group                                                        Must be present either MD03         reject the
                 Information                                                             at message level or at              message
                                                                                         transaction level, but
                                                                                         not at both levels.

2.1     [1..1]   ++ Original Message                           Message Identification    Must match with the    MD03         reject the
                 Identification                                of the original Credit    corresponding value in              message
                                                               Transfer message as       the original Credit
                                                               sent by CSM 2.            Transfer.

2.2     [1..1]   ++ Original Message                                                     Must equal             MD03         reject the
                 Name Identification                                                     „pacs.008.001.01‟.                  message

2.3     [0..1]   ++ Original Creation                          Only used for additio-
                 Date and Time                                 nal optional services

2.4     [0..n]   ++ Return Reason                              Only used for additio-
                 Information                                   nal optional services




        Page 92 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                   Error code    Action
                                         Requirements              ditional specifications

2.5     [0..1]   +++ Return                                        Only used for additio-
                 Originator                                        nal optional services

2.6     [0..1]   +++ Return Reason                                 Only used for additio-
                                                                   nal optional services

2.9     [0..n]   +++ Additional Return                             Only used for additio-
                 Reason Information                                nal optional services




3.0     [0..n]   + Transaction           Mandatory                 For Returns always        At least one             MD03          reject the
                 Information                                       the full original         Transaction                            message
                                                                   transaction details       Information must be
                                                                   must be provided (no      present
                                                                   group returns
                                                                   possible).

3.1     [0..1]   ++ Return               Mandatory              Unique identification        The combination of       MD03          reject the
                 Identification          (R5 Specific Reference assigned by the bank         Return Originator        (duplicate)   transaction
                                         of the Bank Initiating that initiated the           (3.20) and Return
                                         the Return)            Return: Bank 2 or a          Identification must be
                                                                previous bank that           unique, for this
                                                                submits via Bank 2.          message type (CT
                                                                Must be forwarded to         Return).
                                                                Bank 1.

                                                                                             Must be present          MD03          reject the
                                                                                                                                    transaction

3.2     [0..1]   ++ Original Group                                                           Must be present either MD03            reject the
                 Information                                                                 at message level or at                 message
                                                                                             transaction level, but
                                                                                             not at both levels.

3.3     [1..1]   +++ Original Message                              Message Identification    Must match with the    MD03            reject the
                 Identification                                    of the original Credit    corresponding value in                 transaction
                                                                   Transfer message as       the original Credit
                                                                   sent by CSM 2.            Transfer.

3.4     [1..1]   +++ Original Message                                                        Must equal               MD03          reject the
                 Name Identification                                                         „pacs.008.001.01‟.                     transaction

3.5     [0..1]   +++ Original Creation                             Only used for additio-
                 Date and Time                                     nal optional services

3.6     [0..1]   ++ Original             Usage rule:               Instruction               Must match with the    MD03            reject the
                 Instruction             Mandatory if provided     Identification of the     corresponding value in                 transaction
                 Identification          in the original           original transaction as   the original Credit
                                         instruction.              sent by CSM 2.            Transfer.

3.7     [0..1]   ++ Original End To      Mandatory                                           Must match with the    MD03            reject the
                 End Identification      (AT-41 Originator‟s                                 corresponding value in                 transaction
                                         reference of the credit                             the original Credit
                                         transfer transaction)                               Transfer.

                                                                                             Must be present          MD03          reject the
                                                                                                                                    transaction

3.8     [0..1]   ++ Original             Mandatory                                           Must match with the    MD03            reject the
                 Transaction             (AT-43 Originator                                   corresponding value in                 transaction
                 Identification          Bank‟s reference of                                 the original Credit
                                         the credit transfer                                 Transfer.
                                         transaction)
                                         Usage rule:
                                         Must contain a
                                         reference that is
                                         meaningful to the
                                         Originator‟s Bank and
                                         is unique over time.




        Page 93 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                 Error code   Action
                                         Requirements               ditional specifications

                                                                                              Must be present        MD03         reject the
                                                                                                                                  transaction

3.9     [0..1]   ++ Original Interbank   Mandatory                                            Must match with the    MD03         reject the
                 Settlement Amount       (AT-04 Amount of the                                 corresponding value in              transaction
                                         credit transfer in euro)                             the original Credit
                                                                                              Transfer.
                                         Usage rule:
                                         Amount must be 0.01
                                         or more and
                                         999999999.99 or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

                                                                                              Must be present        MD03         reject the
                                                                                                                                  transaction

3.10    [1..1]   ++ Returned             Usage rule:                                          Must be equal to       MD03         reject the
                 Interbank Settlement    Only „EUR‟ is allowed.                               Original Interbank                  transaction
                 Amount                  Usage rule:                                          Settlement Amount
                                         Amount must be 0.01                                  (3.9).
                                         or more and
                                         999999999.99 or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

3.11    [0..1]   ++ Interbank                                       Only used for additio-
                 Settlement Date                                    nal optional services

3.12    [0..1]   ++ Returned                                        Only used for additio-
                 Instructed Amount                                  nal optional services

3.13    [0..1]   ++ Exchange Rate                                   Only used for additio-
                                                                    nal optional services

3.14    [0..1]   ++ Compensation                                    Only used for additio-
                 Amount                                             nal optional services

3.15    [0..1]   ++ Charge Bearer        Usage rule:                                          If present, must       MD03         reject the
                                         Only 'SLEV' is allowed.                              contain the value                   transaction
                                                                                              'SLEV'

3.16    [0..n]   ++ Charges                                         Only used for additio-
                 Information                                        nal optional services

3.17    [0..1]   ++ Instructing Agent    Usage rule:                Absent.                   Must be absent         MD03         reject the
                                         Only BIC is allowed.       (Present at group                                             transaction
                                                                    level: 1.22)

3.18    [0..1]   ++ Instructed Agent     Usage rule:                Absent.                   Must be absent         MD03         reject the
                                         Only BIC is allowed.                                                                     transaction

3.19    [0..n]   ++ Return Reason        Mandatory                                            Must contain exactly   MD03         reject the
                 Information             Usage rule:                                          one occurrence.                     transaction
                                         Only one occurrence
                                         of 'Return Reason
                                         Information' is
                                         allowed.




        Page 94 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                 Error code   Action
                                         Requirements               ditional specifications

3.20    [0..1]   +++ Return              Mandatory                  BIC of the bank that      The combination of    MD03          reject the
                 Originator              (R2 Identification of      initiated the Return:     Return Originator and (duplicate)   transaction
                                         the type of party          Bank 2 or a previous      Return Identification
                                         initiating the R-          bank that submits via     must be unique, for
                                         message)                   Bank 2. Must be           this message type (CT
                                                                    forwarded to Bank 1.      Return).
                                         Usage rule:
                                         Limited to BIC for an
                                         Agent or „Name‟ for a
                                         non-financial
                                         institution.

                                                                                              Must be present        MD03         reject the
                                                                                                                                  transaction

                                                                                              Must contain BIC       MD03         reject the
                                                                                                                                  transaction

                                                                                              Must contain a BIC     RC01         reject the
                                                                                              from the BIC-directory              transaction

3.21    [0..1]   +++ Return Reason       Mandatory                  Either Code or            Must be present        MD03         reject the
                                         (R3 Reason Code for        Proprietary must be                                           transaction
                                         Non-Acceptance)            present

3.22    {Or      ++++ Code               Possible values are:                                 If present, must be   MD03          reject the
                                         (return) AC01, AC04,                                 one of the approved                 transaction
                                         AC06, AG01, BE04,                                    SEPA Credit Transfer
                                         MD07, MS02 and                                       return reasons (AC01,
                                         MS03.                                                AC04, AC06, AG01,
                                                                                              BE04, MD07, MS02
                                                                                              and MS03)

3.23    Or}      ++++ Proprietary        Usage rule:                                          If present, must be   MD03          reject the
                                         To be used to specify                                one of the approved                 transaction
                                         the regulatory reason,                               SEPA Credit Transfer
                                         using the code „RR01‟.                               return reasons (RR01)

3.24    [0..n]   +++ Additional Return                              Only used for additio-
                 Reason Information                                 nal optional services

3.25    [0..1]   ++ Original             Mandatory                                            Must be present        MD03         reject the
                 Transaction Reference   (An exact copy of all                                                                    transaction
                                         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.

                                                                                              All mandatory          MD03         reject the
                                                                                              elements of the                     transaction
                                                                                              original Credit
                                                                                              Transfer must be
                                                                                              present

                                                                                              All elements supplied  MD03         reject the
                                                                                              must match with the                 transaction
                                                                                              corresponding value in
                                                                                              the original Credit
                                                                                              Transfer.

3.26    [0..1]   +++ Interbank                                      Only used for additio-
                 Settlement Amount                                  nal optional services




        Page 95 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error code   Action
                                        Requirements            ditional specifications

3.27    [0..1]   +++ Amount                                     Only used for additio-
                                                                nal optional services

3.32    [0..1]   +++ Interbank          (AT-42 Settlement                                 A maximum of 3         TM01         reject the
                 Settlement Date        Date of the credit                                Target days in the                  transaction
                                        transfer)                                         past and not more
                                                                                          than 3 Target days
                                                                                          older than the
                                                                                          Interbank Settlement
                                                                                          Date of the Return
                                                                                          (see 1.9).

3.33    {Or      +++ Requested                                  Only used for additio-
                 Execution Date                                 nal optional services

3.34    Or}      +++ Requested                                  Not used.
                 Collection Date

3.35    [0..1]   +++ Creditor Scheme                            Not used.
                 Identification

3.36    [0..1]   +++ Settlement
                 Information

3.48    [0..1]   +++ Payment Type       (AT-40 Identification
                 Information            code of the Scheme)

3.59    [0..1]   +++ Payment Method                             Only used for additio-
                                                                nal optional services

3.60    [0..1]   +++ Mandate Related                            Not used.
                 Information

3.79    [0..1]   +++ Remittance         (AT-05 Remittance
                 Information            information)

3.104   [0..1]   +++ Ultimate Debtor    (AT-08 Originator       Will be considered for
                                        Reference Party)        inclusion in a future
                                                                version as AT-08
                                                                Originator Reference
                                                                Party

3.105   [0..1]   +++ Debtor             (AT-02 Name of the
                                        Originator)
                                        (AT-03 Address of the
                                        Originator)
                                        (AT-10 Originator
                                        identification code)

3.106   [0..1]   +++ Debtor Account     (AT-01 IBAN of the
                                        Originator)

3.107   [0..1]   +++ Debtor Agent       (AT-06 BIC code of
                                        the Originator Bank

3.108   [0..1]   +++ Debtor Agent                               Only used for additio-
                 Account                                        nal optional services

3.109   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.110   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.111   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.112   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)




        Page 96 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core            Comments and ad-          Checks                 Error code   Action
                                       Requirements         ditional specifications

3.113   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary   Will be considered for
                                       Reference Party)     inclusion in a future
                                                            version as AT-28
                                                            Beneficiary Reference
                                                            Party




        Page 97 of 148                                                                         Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.9    Inter CSM CT Return (pacs.004.001.01)

         From CSM 2 to CSM 1.

         If the message does not conform to the ISO xsd schema the whole message will be rejected with
         Error Code 'MD03'.



 Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                  Error code   Action
                                         Requirements              ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                       Assigned by CSM 2,        Must be unique, for                  contact CSM 2
                  Identification                                   must be unique over       the instructing party
                                                                   time for this message     (CSM 2)
                                                                   type (CT Return).

 1.2     [1..1]   ++ Creation Date                                 The date and time the Must be a valid date        MD03         reject the
                  Time                                             message has been      and time                                 message
                                                                   created

 1.3     [0..2]   ++ Authorisation                                 Only used for additio-
                                                                   nal optional services

 1.4     [0..1]   ++ Batch Booking                                 Only used for additio-
                                                                   nal optional services

 1.5     [1..1]   ++ Number Of                                     A maximum of 100000 Must be  100000              MD03         reject the
                  Transactions                                     transactions per                                               message
                                                                   message.

                                                                                             Must equal the          MD03         reject the
                                                                                             number of                            message
                                                                                             transactions in the
                                                                                             message

 1.6     [0..1]   ++ Control Sum                                   Only used for additio-
                                                                   nal optional services

 1.7     [0..1]   ++ Group Return                                  Only used for additio-
                                                                   nal optional services

 1.8     [0..1]   ++ Total Returned      Mandatory                 ISO: must equal the       Must equal the sum of MD03           reject the
                  Interbank Settlement   Usage rule:               sum of all occurrences    all occurrences of                   message
                  Amount                 Only „EUR‟ is allowed.    of Transaction            Transaction
                                                                   Information /             Information /
                                         Usage rule:
                                                                   Returned Interbank        Returned Interbank
                                         Amount must be 0.01
                                                                   Settlement Amount         Settlement Amount
                                         or more and
                                                                   when present
                                         999999999999999.99
                                         or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

                                                                                             Currency Code must      MD03         reject the
                                                                                             be "EUR"                             message

                                                                                             Amount must be ≥        MD03         reject the
                                                                                             0.01                                 message

                                                                                             Amount must be ≤        MD03         reject the
                                                                                             999999999999999.99                   message

                                                                                             Maximum 2 fraction      MD03         reject the
                                                                                             digits                               message

 1.9     [0..1]   ++ Interbank           Mandatory                 Date on which CSM 2       Must be a valid date    MD03         reject the
                  Settlement Date        (AT-R4 Settlement         has settled these                                              message
                                         Date for the Return)      transactions.

                                                                                             Must not be in the      MD03         reject the
                                                                                             future                               message




         Page 98 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                  Error code   Action
                                         Requirements               ditional specifications

                                                                                              Must be current        TM01          reject the
                                                                                              Target day or 1 Target               message
                                                                                              day in the past

1.10    [1..1]   ++ Settlement
                 Information

1.11    [1..1]   +++ Settlement          Usage rule:                In Inter CSM only the     Must contain the value MD03          reject the
                 Method                  Only CLRG, INGA and        value 'CLRG' is           'CLRG'.                              message
                                         INDA are allowed.          allowed.

1.12    [0..1]   +++ Settlement          Usage rule:                Absent. (ISO: If          Must not be present     MD03         reject the
                 Account                 Only 'Identification' is   Settlement Method =                                            message
                                         allowed.                   'CLRG', then
                                                                    Settlement Account is
                                                                    not allowed.)

1.13    [0..1]   +++ Clearing System                                Present. (ISO: If         Must be Present         MD03         reject the
                                                                    Settlement Method =                                            message
                                                                    'CLRG', then Clearing
                                                                    System must be
                                                                    present.)
                                                                    Identifies Clearing
                                                                    System of CSM 1

1.14    {Or      ++++ Clearing                                      Clearing System           If present, it must    MD03          reject the
                 System Identification                              Identification is used    contain the valid                    message
                                                                    when Clearing System      UNIFI code identifying
                                                                    Identification exists     CSM 1
                                                                    for the Clearing
                                                                    System of CSM 1 in
                                                                    the UNIFI ISO 20022
                                                                    code list

1.15    Or}      ++++ Proprietary                                   Used when no             If present, it must      MD03         reject the
                                                                    Clearing System          contain the valid code                message
                                                                    Identification exists    as specified by CSM 1
                                                                    for the Clearing
                                                                    System of CSM 1 in
                                                                    UNIFI ISO 20022 code
                                                                    list. Value is specified
                                                                    by CSM 1.

1.16    [0..1]   +++ Instructing                                    Only used for additio-
                 Reimbursement Agent                                nal optional services

1.17    [0..1]   +++ Instructing                                    Only used for additio-
                 Reimbursement Agent                                nal optional services
                 Account

1.18    [0..1]   +++ Instructed Reim-                               Only used for additio-
                 bursement Agent                                    nal optional services

1.19    [0..1]   +++ Instructed Reim-                               Only used for additio-
                 bursement Agent                                    nal optional services
                 Account

1.20    [0..1]   +++ Third Reim-                                    Only used for additio-
                 bursement Agent                                    nal optional services

1.21    [0..1]   +++ Third Reimbur-                                 Only used for additio-
                 sement Agent Account                               nal optional services




        Page 99 of 148                                                                                 Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                   Error code   Action
                                         Requirements           ditional specifications

1.22    [0..1]   ++ Instructing Agent    Usage rule:            If CSM 2 receives an      May be present in       MD03          reject the
                                         Only BIC is allowed.   Instructing Agent in      either the Group                      message
                                                                an incoming Return,       Header or the
                                                                then she forwards it to   Transaction
                                                                CSM 1. If CSM 2           Information, but not in
                                                                herself initiates the     both
                                                                Return, then
                                                                Instructing Agent is
                                                                absent.
                                                                If present, then either
                                                                at group level or
                                                                (most obvious) at
                                                                transaction level.

                                                                                          If present, must         MD03         reject the
                                                                                          contain BIC                           message

                                                                                          If present with BIC,                  contact CSM 2
                                                                                          must contain a BIC
                                                                                          from the BIC-directory

1.23    [0..1]   ++ Instructed Agent     Usage rule:            Not used.                 Must be absent           MD03         reject the
                                         Only BIC is allowed.                                                                   message




2.0     [0..1]   + Original Group                                                         Must be present either MD03           reject the
                 Information                                                              at message level or at                message
                                                                                          transaction level, but
                                                                                          not at both levels.

2.1     [1..1]   ++ Original Message                            Message Identification    Must match with the                   contact CSM 2
                 Identification                                 of the original           corresponding value in
                                                                message as sent by        the original Credit
                                                                CSM 1.                    Transfer.

2.2     [1..1]   ++ Original Message                                                      Must equal               MD03         reject the
                 Name Identification                                                      „pacs.008.001.01‟.                    message

2.3     [0..1]   ++ Original Creation                           Only used for additio-
                 Date and Time                                  nal optional services

2.4     [0..n]   ++ Return Reason                               Only used for additio-
                 Information                                    nal optional services

2.5     [0..1]   +++ Return                                     Only used for additio-
                 Originator                                     nal optional services

2.6     [0..1]   +++ Return Reason                              Only used for additio-
                                                                nal optional services

2.9     [0..n]   +++ Additional Return                          Only used for additio-
                 Reason Information                             nal optional services




3.0     [0..n]   + Transaction           Mandatory              For Returns always        At least one             MD03         reject the
                 Information                                    the full original         Transaction                           message
                                                                transaction details       Information must be
                                                                must be provided (no      present
                                                                group returns
                                                                possible).

3.1     [0..1]   ++ Return               Mandatory              Unique identification     The combination of                    contact CSM 2
                 Identification          (R5 Specific Reference assigned by the bank      Return Originator
                                         of the Bank Initiating or CSM that initiated     (3.20) and Return
                                         the Return)            the Return. Must be       Identification must be
                                                                forwarded to Bank 1       unique, for this
                                                                (bank on the debit        message type (CT
                                                                side).                    Return).




        Page 100 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error code   Action
                                         Requirements               ditional specifications

                                                                                              Must be present          MD03         reject the
                                                                                                                                    transaction

3.2     [0..1]   ++ Original Group                                                            Must be present either MD03           reject the
                 Information                                                                  at message level or at                message
                                                                                              transaction level, but
                                                                                              not at both levels.

3.3     [1..1]   +++ Original Message                               Message Identification    Must match with the                   contact CSM 2
                 Identification                                     of the original           corresponding value in
                                                                    message as sent by        the original Credit
                                                                    CSM 1.                    Transfer.

3.4     [1..1]   +++ Original Message                                                         Must equal               MD03         reject the
                 Name Identification                                                          „pacs.008.001.01‟.                    transaction

3.5     [0..1]   +++ Original Creation                              Only used for additio-
                 Date and Time                                      nal optional services

3.6     [0..1]   ++ Original             Usage rule:                Instruction               Must match with the                   contact CSM 2
                 Instruction             Mandatory if provided      identification of the     corresponding value in
                 Identification          in the original            original transaction as   the original Credit
                                         instruction.               sent by CSM 1.            Transfer.

3.7     [0..1]   ++ Original End To      Mandatory                                            Must be present          MD03         reject the
                 End Identification      (AT-41 Originator‟s                                                                        transaction
                                         reference of the credit
                                         transfer transaction)

                                                                                              Must match with the                   contact CSM 2
                                                                                              corresponding value in
                                                                                              the original Credit
                                                                                              Transfer.

3.8     [0..1]   ++ Original             Mandatory                                            Must match with the                   contact CSM 2
                 Transaction             (AT-43 Originator                                    corresponding value in
                 Identification          Bank‟s reference of                                  the original Credit
                                         the credit transfer                                  Transfer.
                                         transaction)
                                         Usage rule:
                                         Must contain a
                                         reference that is
                                         meaningful to the
                                         Originator‟s Bank and
                                         is unique over time.

                                                                                              Must be present          MD03         reject the
                                                                                                                                    transaction

3.9     [0..1]   ++ Original Interbank   Mandatory                                            Must match with the                   contact CSM 2
                 Settlement Amount       (AT-04 Amount of the                                 corresponding value in
                                         credit transfer in euro)                             the original Credit
                                                                                              Transfer.
                                         Usage rule:
                                         Amount must be 0.01
                                         or more and
                                         999999999.99 or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

                                                                                              Must be present          MD03         reject the
                                                                                                                                    transaction




        Page 101 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                 Comments and ad-          Checks                   Error code   Action
                                        Requirements              ditional specifications

3.10    [1..1]   ++ Returned            Usage rule:                                         Must be equal to         MD03         reject the
                 Interbank Settlement   Only „EUR‟ is allowed.                              Original Interbank                    transaction
                 Amount                 Usage rule:                                         Settlement Amount.
                                        Amount must be 0.01
                                        or more and
                                        999999999.99 or less.
                                        Format rule:
                                        The fractional part has
                                        a maximum of two
                                        digits.

3.11    [0..1]   ++ Interbank                                     Only used for additio-
                 Settlement Date                                  nal optional services

3.12    [0..1]   ++ Returned                                      Only used for additio-
                 Instructed Amount                                nal optional services

3.13    [0..1]   ++ Exchange Rate                                 Only used for additio-
                                                                  nal optional services

3.14    [0..1]   ++ Compensation                                  Only used for additio-
                 Amount                                           nal optional services

3.15    [0..1]   ++ Charge Bearer       Usage rule:                                         If present, must         MD03         reject the
                                        Only 'SLEV' is allowed.                             contain the value                     transaction
                                                                                            'SLEV'

3.16    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.17    [0..1]   ++ Instructing Agent   Usage rule:               If CSM 2 receives an      May be present in       MD03          reject the
                                        Only BIC is allowed.      Instructing Agent in      either the Group                      message
                                                                  an incoming Return,       Header or the
                                                                  then she forwards it to   Transaction
                                                                  CSM 1. If CSM 2           Information, but not in
                                                                  herself initiates the     both
                                                                  Return, then
                                                                  Instructing Agent is
                                                                  absent.
                                                                  If present, then either
                                                                  at group level or
                                                                  (most obvious) at
                                                                  transaction level.

                                                                                            If present, must         MD03         reject the
                                                                                            contain BIC                           transaction

                                                                                            If present with BIC,                  contact CSM 2
                                                                                            must contain a BIC
                                                                                            from the BIC-directory

3.18    [0..1]   ++ Instructed Agent    Usage rule:               Not used.                 Must be absent           MD03         reject the
                                        Only BIC is allowed.                                                                      transaction

3.19    [0..n]   ++ Return Reason       Mandatory                                           Must contain exactly     MD03         reject the
                 Information            Usage rule:                                         one occurrence.                       transaction
                                        Only one occurrence
                                        of 'Return Reason
                                        Information' is
                                        allowed.

3.20    [0..1]   +++ Return             Mandatory                 BIC of the bank or        The combination of                    contact CSM 2
                 Originator             (R2 Identification of     CSM that initiated the    Return Originator and
                                        the type of party         Return. Must be           Return Identification
                                        initiating the R-         forwarded to the          must be unique.
                                        message)                  Bank 1 (bank on the
                                                                  debit side).
                                        Usage rule:
                                        Limited to BIC for an
                                        Agent or „Name‟ for a
                                        non-financial
                                        institution.




        Page 102 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                   Error code   Action
                                         Requirements               ditional specifications

                                                                                              Must be present          MD03         reject the
                                                                                                                                    transaction

                                                                                              Either BIC or Name       MD03         reject the
                                                                                              must be present                       transaction

                                                                                              If present with BIC,                  contact CSM 2
                                                                                              must contain a BIC
                                                                                              from the BIC-directory

3.21    [0..1]   +++ Return Reason       Mandatory                  Either Code or            Must be present          MD03         reject the
                                         (R3 Reason Code for        Proprietary must be                                             transaction
                                         Non-Acceptance)            present

3.22    {Or      ++++ Code               Possible values are:                                 If present, must be   MD03            reject the
                                         (return) AC01, AC04,                                 one of the approved                   transaction
                                         AC06, AG01, BE04,                                    SEPA Credit Transfer
                                         MD07, MS02 and                                       return reasons (AC01,
                                         MS03.                                                AC04, AC06, AG01,
                                                                                              BE04, MD07, MS02
                                                                                              and MS03)

3.23    Or}      ++++ Proprietary        Usage rule:                                          If present, must be   MD03            reject the
                                         To be used to specify                                one of the approved                   transaction
                                         the regulatory reason,                               SEPA Credit Transfer
                                         using the code „RR01‟.                               return reasons (RR01)

3.24    [0..n]   +++ Additional Return                              Used to provide the   Must be present and    MD03               reject the
                 Reason Information                                 settlement reference, contain the settlement                    transaction
                                                                    assigned by CSM 2, to reference.
                                                                    CSM 1. Contains a
                                                                    codeword followed by
                                                                    the reference itself:
                                                                    /STTLMREF/<ref max.
                                                                    16 positions>

                                                                                              Settlement reference     MD03         reject the
                                                                                              must not be more                      transaction
                                                                                              than 16 positions

3.25    [0..1]   ++ Original             Mandatory                                            Must be present          MD03         reject the
                 Transaction Reference   (An exact copy of all                                                                      transaction
                                         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.

                                                                                              All mandatory ele-       MD03         reject the
                                                                                              ments of the original                 transaction
                                                                                              Credit Transfer must
                                                                                              be present

                                                                                              All elements supplied  MD03           reject the
                                                                                              must match with the                   transaction or
                                                                                              corresponding value in                contact CSM 2
                                                                                              the original Credit
                                                                                              Transfer.

3.26    [0..1]   +++ Interbank                                      Only used for additio-
                 Settlement Amount                                  nal optional services




        Page 103 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                   Error code   Action
                                        Requirements            ditional specifications

3.27    [0..1]   +++ Amount                                     Only used for additio-
                                                                nal optional services

3.32    [0..1]   +++ Interbank          (AT-42 Settlement                                 A maximum of 3 Tar-                   contact CSM 2
                 Settlement Date        Date of the credit                                get days in the past
                                        transfer)                                         and not more than 3
                                                                                          Target days older than
                                                                                          the Interbank
                                                                                          Settlement Date of the
                                                                                          Return (see 1.9).

3.33    {Or      +++ Requested                                  Only used for additio-
                 Execution Date                                 nal optional services

3.34    Or}      +++ Requested                                  Not used.
                 Collection Date

3.35    [0..1]   +++ Creditor Scheme                            Not used.
                 Identification

3.36    [0..1]   +++ Settlement
                 Information

3.48    [0..1]   +++ Payment Type       (AT-40 Identification
                 Information            code of the Scheme)

3.59    [0..1]   +++ Payment Method                             Only used for additio-
                                                                nal optional services

3.60    [0..1]   +++ Mandate Related                            Not used.
                 Information

3.79    [0..1]   +++ Remittance         (AT-05 Remittance
                 Information            information)

3.104   [0..1]   +++ Ultimate Debtor    (AT-08 Originator       Will be considered for
                                        Reference Party)        inclusion in a future
                                                                version as AT-08
                                                                Originator Reference
                                                                Party

3.105   [0..1]   +++ Debtor             (AT-02 Name of the
                                        Originator)
                                        (AT-03 Address of the
                                        Originator)
                                        (AT-10 Originator
                                        identification code)

3.106   [0..1]   +++ Debtor Account     (AT-01 IBAN of the
                                        Originator)

3.107   [0..1]   +++ Debtor Agent       (AT-06 BIC code of
                                        the Originator Bank

3.108   [0..1]   +++ Debtor Agent                               Only used for additio-
                 Account                                        nal optional services

3.109   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.110   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.111   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.112   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)




        Page 104 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core            Comments and ad-          Checks                 Error code   Action
                                       Requirements         ditional specifications

3.113   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary   Will be considered for
                                       Reference Party)     inclusion in a future
                                                            version as AT-28
                                                            Beneficiary Reference
                                                            Party




        Page 105 of 148                                                                        Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.10 CSM - Bank CT Return (pacs.004.001.01)

         From CSM 1 to Bank 1.


 Index   Mult.    Message element        SEPA Core                  Comments and ad-          Checks                 Error code   Action
                                         Requirements               ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                        Assigned by CSM 1,
                  Identification                                    must be unique over
                                                                    time for this message
                                                                    type (CT Return).

 1.2     [1..1]   ++ Creation Date                                  The date and time the
                  Time                                              message has been
                                                                    created

 1.3     [0..2]   ++ Authorisation                                  Only used for additio-
                                                                    nal optional services

 1.4     [0..1]   ++ Batch Booking                                  Only used for additio-
                                                                    nal optional services

 1.5     [1..1]   ++ Number Of                                      A maximum of 100000
                  Transactions                                      transactions per
                                                                    message.

 1.6     [0..1]   ++ Control Sum                                    Only used for additio-
                                                                    nal optional services

 1.7     [0..1]   ++ Group Return                                   Only used for additio-
                                                                    nal optional services

 1.8     [0..1]   ++ Total Returned      Mandatory                  Equals the sum of all
                  Interbank Settlement   Usage rule:                occurrences of
                  Amount                 Only „EUR‟ is allowed.     Transaction
                                                                    Information /
                                         Usage rule:
                                                                    Returned Interbank
                                         Amount must be 0.01
                                                                    Settlement Amount
                                         or more and
                                         999999999999999.99
                                         or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

 1.9     [0..1]   ++ Interbank           Mandatory                  Date on which CSM 1
                  Settlement Date        (AT-R4 Settlement          has settled these
                                         Date for the Return)       transactions.
                                                                    This may not be the
                                                                    same date as the
                                                                    requested settlement
                                                                    date in the CT Return
                                                                    from Bank 2 to CSM 2.

 1.10    [1..1]   ++ Settlement
                  Information

 1.11    [1..1]   +++ Settlement         Usage rule:                Only the value 'CLRG'
                  Method                 Only CLRG, INGA and        is allowed.
                                         INDA are allowed.

 1.12    [0..1]   +++ Settlement         Usage rule:                Absent. (ISO: If
                  Account                Only 'Identification' is   Settlement Method =
                                         allowed.                   'CLRG', then
                                                                    Settlement Account is
                                                                    not allowed.)




         Page 106 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core      Comments and ad-           Checks                 Error code   Action
                                         Requirements   ditional specifications

1.13    [0..1]   +++ Clearing System                    Present. (ISO: If
                                                        Settlement Method =
                                                        'CLRG', then Clearing
                                                        System must be
                                                        present.)
                                                        Identifies Clearing
                                                        System of CSM 1

1.14    {Or      ++++ Clearing                          Used when Clearing
                 System Identification                  System Identification
                                                        exists for the Clearing
                                                        System of CSM 1 in
                                                        the UNIFI ISO 20022
                                                        code list

1.15    Or}      ++++ Proprietary                       Used when no
                                                        Clearing System
                                                        Identification exists
                                                        for the Clearing
                                                        System of CSM 1 in
                                                        UNIFI ISO 20022 code
                                                        list. Value is specified
                                                        by CSM 1.

1.16    [0..1]   +++ Instructing                        Absent. (ISO: If
                 Reimbursement Agent                    Settlement Method =
                                                        'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)

1.17    [0..1]   +++ Instructing                        Absent. (ISO: If
                 Reimbursement Agent                    Settlement Method =
                 Account                                'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)

1.18    [0..1]   +++ Instructed Reim-                   Absent. (ISO: If
                 bursement Agent                        Settlement Method =
                                                        'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)

1.19    [0..1]   +++ Instructed Reim-                   Absent. (ISO: If
                 bursement Agent                        Settlement Method =
                 Account                                'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)

1.20    [0..1]   +++ Third Reim-                        Absent. (ISO: If
                 bursement Agent                        Settlement Method =
                                                        'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)

1.21    [0..1]   +++ Third Reim-                        Absent. (ISO: If
                 bursement Agent                        Settlement Method =
                 Account                                'CLRG', then Reim-
                                                        bursement agents are
                                                        not allowed.)




        Page 107 of 148                                                                     Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                 Error code   Action
                                         Requirements           ditional specifications

1.22    [0..1]   ++ Instructing Agent    Usage rule:            Is present if the
                                         Only BIC is allowed.   Return was initiated
                                                                by a bank. Is absent if
                                                                the Return was
                                                                initiated by a CSM.
                                                                May be present in
                                                                either the Group
                                                                Header or (most
                                                                obvious) the Trans-
                                                                action Information,
                                                                but not in both.
                                                                If present, contains a
                                                                BIC.

1.23    [0..1]   ++ Instructed Agent     Usage rule:            Present. Contains the
                                         Only BIC is allowed.   BIC of Bank 1.




2.0     [0..1]   + Original Group                               Is present either at
                 Information                                    message level or at
                                                                transaction level, but
                                                                not at both levels.

2.1     [1..1]   ++ Original Message                            Message Identification
                 Identification                                 of the original CT
                                                                message (as sent by
                                                                Bank 1).

2.2     [1..1]   ++ Original Message                            Message name of the
                 Name Identification                            original CT message:
                                                                „pacs.008.001.01‟.

2.3     [0..1]   ++ Original Creation                           Only used for additio-
                 Date and Time                                  nal optional services

2.4     [0..n]   ++ Return Reason                               Only used for additio-
                 Information                                    nal optional services

2.5     [0..1]   +++ Return                                     Only used for additio-
                 Originator                                     nal optional services

2.6     [0..1]   +++ Return Reason                              Only used for additio-
                                                                nal optional services

2.9     [0..n]   +++ Additional Return                          Only used for additio-
                 Reason Information                             nal optional services




3.0     [0..n]   + Transaction           Mandatory              At least one Tran-
                 Information                                    saction Information is
                                                                present.

3.1     [0..1]   ++ Return               Mandatory              Unique identification
                 Identification          (R5 Specific Reference assigned by the bank
                                         of the Bank Initiating or CSM that initiated
                                         the Return)            the Return. Is
                                                                forwarded to Bank 1.

3.2     [0..1]   ++ Original Group                              Is present either at
                 Information                                    message level or at
                                                                transaction level, but
                                                                not at both levels.

3.3     [1..1]   +++ Original Message                           Message Identification
                 Identification                                 of the original CT
                                                                message (as sent by
                                                                Bank 1).




        Page 108 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                 Error code   Action
                                         Requirements              ditional specifications

3.4     [1..1]   +++ Original Message                              Message name of the
                 Name Identification                               original CT message:
                                                                   „pacs.008.001.01‟.

3.5     [0..1]   +++ Original Creation                             Only used for additio-
                 Date and Time                                     nal optional services

3.6     [0..1]   ++ Original             Usage rule:               If present, copied
                 Instruction             Mandatory if provided     from the original
                 Identification          in the original           transaction.
                                         instruction.

3.7     [0..1]   ++ Original End To      Mandatory               Copied from the
                 End Identification      (AT-41 Originator‟s     original transaction.
                                         reference of the credit
                                         transfer transaction)

3.8     [0..1]   ++ Original             Mandatory                 Copied from the
                 Transaction             (AT-43 Originator         original transaction.
                 Identification          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.

3.9     [0..1]   ++ Original Interbank   Mandatory                Copied from the
                 Settlement Amount       (AT-04 Amount of the original transaction.
                                         credit transfer in euro)
                                         Usage rule:
                                         Amount must be 0.01
                                         or more and
                                         999999999.99 or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

3.10    [1..1]   ++ Returned             Usage rule:               Equal to the Original
                 Interbank Settlement    Only „EUR‟ is allowed.    Interbank Settlement
                 Amount                  Usage rule:               Amount (3.9).
                                         Amount must be 0.01
                                         or more and
                                         999999999.99 or less.
                                         Format rule:
                                         The fractional part has
                                         a maximum of two
                                         digits.

3.11    [0..1]   ++ Interbank                                      Only used for additio-
                 Settlement Date                                   nal optional services

3.12    [0..1]   ++ Returned                                       Only used for additio-
                 Instructed Amount                                 nal optional services

3.13    [0..1]   ++ Exchange Rate                                  Only used for additio-
                                                                   nal optional services

3.14    [0..1]   ++ Compensation                                   Only used for additio-
                 Amount                                            nal optional services

3.15    [0..1]   ++ Charge Bearer        Usage rule:             If present, contains
                                         Only 'SLEV' is allowed. the value 'SLEV'

3.16    [0..n]   ++ Charges                                        Only used for additio-
                 Information                                       nal optional services




        Page 109 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error code   Action
                                         Requirements             ditional specifications

3.17    [0..1]   ++ Instructing Agent    Usage rule:              Is present if the
                                         Only BIC is allowed.     Return was initiated
                                                                  by a bank. Is absent if
                                                                  the Return was
                                                                  initiated by a CSM.
                                                                  May be present in
                                                                  either the Group
                                                                  Header or (most
                                                                  obvious) the
                                                                  Transaction
                                                                  Information, but not in
                                                                  both.
                                                                  If present, contains a
                                                                  BIC.

3.18    [0..1]   ++ Instructed Agent     Usage rule:              Absent.
                                         Only BIC is allowed.

3.19    [0..n]   ++ Return Reason        Mandatory                Exactly one
                 Information             Usage rule:              occurrence is present.
                                         Only one occurrence
                                         of 'Return Reason
                                         Information' is
                                         allowed.

3.20    [0..1]   +++ Return              Mandatory                BIC of the bank or
                 Originator              (R2 Identification of    CSM that initiated the
                                         the type of party        Return. Is forwarded
                                         initiating the R-        to Bank 1.
                                         message)
                                         Usage rule:
                                         Limited to BIC for an
                                         Agent or „Name‟ for a
                                         non-financial
                                         institution.

3.21    [0..1]   +++ Return Reason       Mandatory                Either Code or
                                         (R3 Reason Code for      Proprietary is present
                                         Non-Acceptance)

3.22    {Or      ++++ Code               Possible values are:     If present, contains
                                         (return) AC01, AC04,     one of the approved
                                         AC06, AG01, BE04,        SEPA Credit Transfer
                                         MD07, MS02 and           return reasons (AC01,
                                         MS03.                    AC04, AC06, AG01,
                                                                  BE04, MD07, MS02
                                                                  and MS03)

3.23    Or}      ++++ Proprietary        Usage rule:              If present, contains
                                         To be used to specify    one of the approved
                                         the regulatory reason,   SEPA Credit Transfer
                                         using the code „RR01‟.   return reasons (RR01)

3.24    [0..n]   +++ Additional Return                            Used to provide the
                 Reason Information                               settlement reference,
                                                                  assigned by CSM 1, to
                                                                  Bank 1. Contains a
                                                                  codeword followed by
                                                                  the reference itself:
                                                                  /STTLMREF/<ref max.
                                                                  16 positions>




        Page 110 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                  Comments and ad-          Checks                 Error code   Action
                                         Requirements               ditional specifications

3.25    [0..1]   ++ Original             Mandatory                  All following data, if
                 Transaction Reference   (An exact copy of all      present, has been
                                         attributes of the          copied from the
                                         received DS-02 which       original Credit
                                         is being returned)         Transfer message.
                                         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.

3.26    [0..1]   +++ Interbank                                      Only used for additio-
                 Settlement Amount                                  nal optional services

3.27    [0..1]   +++ Amount                                         Only used for additio-
                                                                    nal optional services

3.32    [0..1]   +++ Interbank           (AT-42 Settlement
                 Settlement Date         Date of the credit
                                         transfer)

3.33    {Or      +++ Requested                                      Only used for additio-
                 Execution Date                                     nal optional services

3.34    Or}      +++ Requested                                      Not used.
                 Collection Date

3.35    [0..1]   +++ Creditor Scheme                                Not used.
                 Identification

3.36    [0..1]   +++ Settlement
                 Information

3.48    [0..1]   +++ Payment Type        (AT-40 Identification
                 Information             code of the Scheme)

3.59    [0..1]   +++ Payment Method                                 Only used for additio-
                                                                    nal optional services

3.60    [0..1]   +++ Mandate Related                                Not used.
                 Information

3.79    [0..1]   +++ Remittance          (AT-05 Remittance
                 Information             information)

3.104   [0..1]   +++ Ultimate Debtor     (AT-08 Originator          Will be considered for
                                         Reference Party)           inclusion in a future
                                                                    version as AT-08
                                                                    Originator Reference
                                                                    Party

3.105   [0..1]   +++ Debtor              (AT-02 Name of the
                                         Originator)
                                         (AT-03 Address of the
                                         Originator)
                                         (AT-10 Originator
                                         identification code)

3.106   [0..1]   +++ Debtor Account      (AT-01 IBAN of the
                                         Originator)

3.107   [0..1]   +++ Debtor Agent        (AT-06 BIC code of
                                         the Originator Bank

3.108   [0..1]   +++ Debtor Agent                                   Only used for additio-
                 Account                                            nal optional services




        Page 111 of 148                                                                                Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error code   Action
                                        Requirements            ditional specifications

3.109   [0..1]   +++ Creditor Agent     (AT-23 BIC code of
                                        the Beneficiary Bank)

3.110   [0..1]   +++ Creditor Agent                             Only used for additio-
                 Account                                        nal optional services

3.111   [0..1]   +++ Creditor           (AT-21 Name of the
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.112   [0..1]   +++ Creditor Account   (AT-20 IBAN of the
                                        Beneficiary)

3.113   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary       Will be considered for
                                       Reference Party)         inclusion in a future
                                                                version as AT-28
                                                                Beneficiary Reference
                                                                Party




        Page 112 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.11 CSM - Bank CT Return Reject (pacs.002.001.02)

         From CSM 2 to Bank 2.

         The Reject of a CT Return is not part of the SEPA CT Rulebook. Note that Original Transaction
         Identification, Interbank Settlement Amount and Interbank Settlement Date relate to the CT
         Return, not to the original credit transfer transaction.

         If the message does not conform to the ISO xsd schema then contact CSM 2.



 Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                 Error Code   Action
                                          Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 2,
                  Identification                                 must be unique over
                                                                 time for this message
                                                                 type (CT Return
                                                                 Reject).

 1.2     [1..1]   ++ Creation Date                               The date and time the
                  Time                                           message has been
                                                                 created

 1.3     [0..1]   ++ Initiating Party                            Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                            Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                                Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                              Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent    Usage rule:            Absent.
                                          Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent     Usage rule:            Present, contains the
                                          Only BIC is allowed.   BIC of Bank 2




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                            Message Identification
                  Identification                                 of the original CT
                                                                 Return message as
                                                                 sent by Bank 2

 2.2     Or}      ++ Network File Name                           If no Original Message
                                                                 Identification is
                                                                 available then
                                                                 Network File Name is
                                                                 filled.

 2.3     [1..1]   ++ Original Message                            Message name of the
                  Name Identification                            original CT Return
                                                                 message:
                                                                 'pacs.004.001.01'.

 2.4     [0..1]   ++ Original Creation                           Only used for additio-
                  Date and Time                                  nal optional services

 2.5     [0..1]   ++ File Originator                             Only used for additio-
                                                                 nal optional services

 2.6     [0..1]   ++ Original Number of                          Only used for additio-
                  Transactions                                   nal optional services

 2.7     [0..1]   ++ Original Control                            Only used for additio-
                  Sum                                            nal optional services




         Page 113 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

2.8     [0..1]   ++ Group Status         (R1 Type of R            Present, value =
                                         Message)                 'RJCT' or 'PART'.
                                         Usage rule:            RJCT means that the
                                         Only 'RJCT' and 'PART' whole original CT
                                         are allowed.           Return message is
                                                                rejected. The rejected
                                                                transactions can be
                                                                present or absent
                                                                (0..n Transaction
                                                                Information And
                                                                Status).
                                                                  PART means that
                                                                  some transactions of
                                                                  the original CT Return
                                                                  message are rejected.
                                                                  The rejected
                                                                  transactions follow in
                                                                  Transaction
                                                                  Information And
                                                                  Status (1..n).

2.9     [0..n]   ++ Status Reason        Usage rule:              Exactly one
                 Information             Only one occurrence      occurrence is present,
                                         of 'Status Reason        either in Original
                                         Information' is          Group Information
                                         allowed.                 and Status or in every
                                         Usage rule:              Transaction
                                         'Status Reason           Information and
                                         Information' must be     Status.
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in
                                         'Transaction
                                         Information and
                                         Status'.

2.10    [0..1]   +++ Status Originator Mandatory                  BIC or Name of
                                         (R2 Identification of    CSM 2.
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the Bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

2.11    [0..1]   +++ Status Reason       Mandatory                Either Code or
                                         (R3 Reason Code for      Proprietary is present
                                         Non-Acceptance)

2.12    {Or      ++++ Code               Possible values are:     If present, contains
                                         (reject) AC01, AG02,     one of the approved
                                         MD03, MS03, RC01         SEPA Credit Transfer
                                         and TM01.                reject reasons (AC01,
                                                                  AG02, MD03, MS03
                                                                  RC01 and TM01).

2.13    Or}      ++++ Proprietary        Usage rule:              If present, contains
                                         To be used to specify    one of the approved
                                         the regulatory reason,   SEPA Credit Transfer
                                         using „RR01‟.            reject reasons (RR01).

2.14    [0..n]   +++ Additional Status                            Only used for additio-
                 Reason Information                               nal optional services

2.15    [0..n]   ++ Number of                                     Only used for additio-
                 Transactions Per                                 nal optional services
                 Status




        Page 114 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                       Requirements              ditional specifications




3.0     [0..n]   + Transaction
                 Information and
                 Status

3.1     [0..1]   ++ Status             Mandatory                 Assigned by CSM 2,
                 Identification        (R5 Specific reference    must be unique over
                                       of the bank that          time for this message
                                       initiated the reject)     type (CT Return
                                                                 Reject).

3.2     [0..1]   ++ Original Payment                             Only used for additio-
                 Information                                     nal optional services
                 Identification

3.3     [0..1]   ++ Original           Usage rule:               Absent.
                 Instruction           Mandatory if provided
                 Identification        in the original
                                       instruction.

3.4     [0..1]   ++ Original End To    Mandatory                 Present, Original End
                 End Identification                              To End Identification
                                                                 (3.7) of the original
                                                                 CT Return transaction.

3.5     [0..1]   ++ Original           Mandatory                 Present, Return
                 Transaction           Usage rule:               Identification (3.1) of
                 Identification        Must contain a            the original CT Return
                                       reference that is         transaction.
                                       unique over time.

3.6     [0..1]   ++ Transaction Status (R1 Type of R             Present, value =
                                       message)                  „RJCT‟
                                       Usage rule:
                                       Only 'RJCT' is allowed.

3.7     [0..n]   ++ Status Reason      Usage rule:               Exactly one
                 Information           Only one occurrence       occurrence is present,
                                       of 'Status Reason         either in Original
                                       Information' is           Group Information
                                       allowed.                  and Status or in every
                                       Usage rule:               Transaction
                                       'Status Reason            Information and
                                       Information' must be      Status.
                                       present either in
                                       'Original Group
                                       Information and
                                       Status' or in
                                       'Transaction
                                       Information and
                                       Status'.

3.8     [0..1]   +++ Status Originator Mandatory                 BIC or Name of
                                       (R2 Identification of     CSM 2.
                                       the Type of Party that
                                       initiated the reject)
                                       Usage rule:
                                       Limited to BIC to
                                       identify the bank or
                                       CSM originating the
                                       status or „Name‟ to
                                       indicate the CSM when
                                       it has no BIC.

3.9     [0..1]   +++ Status Reason     Mandatory                 Either Code or
                                       (R3 Reason Code for       Proprietary is present
                                       Non-Acceptance)




        Page 115 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                         Requirements              ditional specifications

3.10    {Or      ++++ Code               Possible values are:      If present, contains
                                         (reject) AC01, AG02,      one of the approved
                                         MD03, MS03, RC01          SEPA Credit Transfer
                                         and TM01.                 reject reasons (AC01,
                                                                   AG02, MD03, MS03
                                                                   RC01 and TM01).

3.11    Or}      ++++ Proprietary        Usage rule:               If present, contains
                                         To be used to specify     one of the approved
                                         the regulatory reason,    SEPA Credit Transfer
                                         using the code „RR01‟.    reject reasons (RR01).

3.12    [0..n]   +++ Additional Status                             Only used for additio-
                 Reason Information                                nal optional services

3.13    [0..n]   ++ Charges                                        Only used for additio-
                 Information                                       nal optional services

3.14    [0..1]   ++ Acceptance Date                                Only used for additio-
                 Time                                              nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:               Absent.
                                         Only BIC is allowed.

3.16    [0..1]   ++ Instructed Agent     Usage rule:               Absent.
                                         Only BIC is allowed.

3.17    [0..1]   ++ Original           Mandatory                   Present. The following
                 Transaction Reference (An exact copy of all       data has been copied
                                       attributes of the           from the original CT
                                       received DS-02 which        Return message.
                                       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 instruc-
                                         tion, as defined within
                                         the following
                                         elements.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the Returned Interbank
                 Settlement Amount       credit transfer in Euro) Settlement Amount
                                                                   (3.10 in CT Return)

3.19    [0..1]   +++ Amount                                        Absent

3.24    [0..1]   +++ Interbank           (AT-42 Settlement         Interbank Settlement
                 Settlement Date         Date of the credit        Date (1.9 in CT
                                         transfer)                 Return)

3.25    {Or      +++ Requested                                     Absent
                 Execution Date

3.26    Or}      +++ Requested                                     Absent
                 Collection Date

3.27    [0..1]   +++ Creditor Scheme                               Absent
                 Information

3.28    [0..1]   +++ Settlement                                    Absent
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification     Absent
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                Absent

3.71    [0..1]   +++ Remittance          (AT-05 Remittance         Absent
                 Information             information)




        Page 116 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                       Requirements            ditional specifications

3.96    [0..1]   +++ Ultimate Debtor   (AT-08 Originator       Absent
                                       Reference Party)

3.97    [0..1]   +++ Debtor            (AT-02 Name of the      Absent
                                       Originator)
                                       (AT-03 Address of the
                                       Originator)
                                       (AT-10 Originator
                                       identification code)

3.98    [0..1]   +++ Debtor Account    (AT-01 IBAN of the      Absent
                                       Originator)

3.99    [0..1]   +++ Debtor Agent      (AT-06 BIC code of      Absent
                                       the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                              Absent
                 Account

3.101   [0..1]   +++ Creditor Agent    (AT-23 BIC code of      Absent
                                       the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                            Absent
                 Account

3.103   [0..1]   +++ Creditor          (AT-21 Name of the      Absent
                                       Beneficiary)
                                       (AT-22 Address of the
                                       Beneficiary
                                       (AT-24 Beneficiary
                                       identification code)

3.104   [0..1]   +++ Creditor Account (AT-20 IBAN of the       Absent
                                      Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary      Absent
                                       Reference Party)




        Page 117 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.12 CSM - Bank CT Return Positive Status Report (pacs.002.001.02)

         From CSM 2 to Bank 2.

         This message is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA
         Core message.

         If the message does not conform to the ISO xsd schema the whole message will be rejected, the
         required action is to contact CSM 2.



 Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                 Error Code   Action
                                          Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                     Assigned by CSM 2,
                  Identification                                 must be unique over
                                                                 time for this message
                                                                 type (CT Return
                                                                 Positive Status
                                                                 Report).

 1.2     [1..1]   ++ Creation Date                               The date and time the
                  Time                                           message has been
                                                                 created

 1.3     [0..1]   ++ Initiating Party                            Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                            Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                                Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                              Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent    Usage rule:            Absent.
                                          Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent     Usage rule:            Present, contains the
                                          Only BIC is allowed.   BIC of Bank 2.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                            Present, Message
                  Identification                                 Identification of the
                                                                 original CT Return
                                                                 message as sent by
                                                                 Bank 2.

 2.2     Or}      ++ Network File Name                           Absent.

 2.3     [1..1]   ++ Original Message                            Value =
                  Name Identification                            'pacs.004.001.01'

 2.4     [0..1]   ++ Original Creation                           Only used for additio-
                  Date and Time                                  nal optional services

 2.5     [0..1]   ++ File Originator                             Only used for additio-
                                                                 nal optional services

 2.6     [0..1]   ++ Original Number of                          Optional.
                  Transactions                                   Number Of
                                                                 Transactions of the
                                                                 original CT Return
                                                                 message.

 2.7     [0..1]   ++ Original Control                            Only used for additio-
                  Sum                                            nal optional services




         Page 118 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element      SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                      Requirements             ditional specifications

2.8     [0..1]   ++ Group Status      (R1 Type of R            Present.
                                      Message)                 Allowed values:
                                      Usage rule:            „ACTC‟, 'ACSC' and
                                      Only 'RJCT' and 'PART' 'PART'.
                                      are allowed.
                                                               ACTC means that the
                                                               original CT Return
                                                               message has been
                                                               successfully validated
                                                               (ready for further
                                                               processing).
                                                               ACSC means that all
                                                               transactions of the
                                                               original CT Return
                                                               message have been
                                                               settled.
                                                               PART means that part
                                                               of the transactions of
                                                               the original CT Return
                                                               message have been
                                                               settled.
                                                               The validated (ACTC)
                                                               or settled
                                                               (ACSC/PART)
                                                               transactions can be
                                                               present or absent:
                                                               0..n Transaction
                                                               Information and
                                                               Status.

2.9     [0..n]   ++ Status Reason     Usage rule:              Exactly one
                 Information          Only one occurrence      occurrence is present.
                                      of 'Status Reason
                                      Information' is
                                      allowed.
                                      Usage rule:
                                      'Status Reason
                                      Information' must be
                                      present either in
                                      'Original Group
                                      Information and
                                      Status' or in
                                      'Transaction
                                      Information and
                                      Status'.

2.10    [0..1]   +++ Status Originator Mandatory               Present, the BIC or
                                      (R2 Identification of    Name of CSM 2.
                                      the Type of Party that
                                      initiated the reject)
                                      Usage rule:
                                      Limited to BIC to
                                      identify the Bank or
                                      CSM originating the
                                      status or „Name‟ to
                                      indicate the CSM when
                                      it has no BIC.

2.11    [0..1]   +++ Status Reason    Mandatory                Absent if Group Status
                                      (R3 Reason Code for      is „ACTC‟.
                                      Non-Acceptance)          Present if Group
                                                               Status is „ACSC‟ or
                                                               „PART‟.

2.12    {Or      ++++ Code            Possible values are:     Contains the code
                                      (reject) AC01, AG02,     'NARR' (= Narrative).
                                      MD03, MS03, RC01
                                      and TM01.




        Page 119 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

2.13    Or}      ++++ Proprietary        Usage rule:            Absent.
                                         To be used to specify
                                         the regulatory reason,
                                         using „RR01‟.

2.14    [0..n]   +++ Additional Status                            If Group Status is
                 Reason Information                               „ACSC‟ or „PART‟,
                                                                  three occurrences are
                                                                  present, for
                                                                  settlement date,
                                                                  settled amount and
                                                                  settlement reference:
                                                                  1./INTRBKSTTLMDT/
                                                                  YYYY-MM-DD
                                                                  2./TTLINTRBKSTTLM
                                                                  AMT/<alpha-3
                                                                  currency
                                                                  code><amount>
                                                                  3./STTLMREF/<ref
                                                                  max. 16 positions>
                                                                  Note that the
                                                                  presence of
                                                                  Additional Status
                                                                  Reason Information
                                                                  is against ISO's
                                                                  StatusReason-
                                                                  InformationRule.

2.15    [0..n]   ++ Number of                                     One occurrence is
                 Transactions Per                                 present if Group
                 Status                                           Status is 'PART'.

2.16    [1..1]   +++ Detailed Number                              Contains the number
                 Of Transactions                                  of settled
                                                                  transactions.
                                                                  Note that the settled
                                                                  transactions
                                                                  themselves (3.0) may
                                                                  be absent, which is
                                                                  not fully in line with
                                                                  ISO.

2.17    [1..1]   +++ Detailed Status                              Contains code 'ACSC'
                                                                  (= settled).

2.18    [0..1]   +++ Detailed Control
                 Sum




3.0     [0..n]   + Transaction                                    The validated/settled
                 Information and                                  transactions can be
                 Status                                           present or absent.

3.1     [0..1]   ++ Status               Mandatory                Present, Assigned by
                 Identification          (R5 Specific reference   CSM 2, must be
                                         of the bank that         unique over time for
                                         initiated the reject)    this message type (CT
                                                                  Return Positive Status
                                                                  Report).

3.2     [0..1]   ++ Original Payment                              Only used for additio-
                 Information                                      nal optional services
                 Identification

3.3     [0..1]   ++ Original             Usage rule:              Absent
                 Instruction             Mandatory if provided
                 Identification          in the original
                                         instruction.




        Page 120 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                 Error Code   Action
                                         Requirements             ditional specifications

3.4     [0..1]   ++ Original End To      Mandatory                Present.
                 End Identification                               Original End To End
                                                                  Identification (3.7) of
                                                                  the original CT Return
                                                                  transaction.

3.5     [0..1]   ++ Original             Mandatory                Present.
                 Transaction             Usage rule:              Return Identification
                 Identification          Must contain a           (3.1) of the original
                                         reference that is        CT Return transaction.
                                         unique over time.

3.6     [0..1]   ++ Transaction Status (R1 Type of R              Present.
                                       message)                   The value is
                                         Usage rule:             - „ACTC‟ if Group
                                         Only 'RJCT' is allowed.   Status is „ACTC‟;
                                                                  - „ACSC‟ if Group
                                                                    Status is „ACSC‟ or
                                                                    „PART‟.

3.7     [0..n]   ++ Status Reason        Usage rule:              Absent.
                 Information             Only one occurrence
                                         of 'Status Reason
                                         Information' is
                                         allowed.
                                         Usage rule:
                                         'Status Reason
                                         Information' must be
                                         present either in
                                         'Original Group
                                         Information and
                                         Status' or in
                                         'Transaction
                                         Information and
                                         Status'.

3.8     [0..1]   +++ Status Originator Mandatory
                                         (R2 Identification of
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

3.9     [0..1]   +++ Status Reason       Mandatory
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:
                                         (reject) AC01, AG02,
                                         MD03, MS03, RC01
                                         and TM01.

3.11    Or}      ++++ Proprietary        Usage rule:
                                         To be used to specify
                                         the regulatory reason,
                                         using the code „RR01‟.

3.12    [0..n]   +++ Additional Status
                 Reason Information

3.13    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.14    [0..1]   ++ Acceptance Date                               Only used for additio-
                 Time                                             nal optional services




        Page 121 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                 Error Code   Action
                                         Requirements              ditional specifications

3.15    [0..1]   ++ Instructing Agent    Usage rule:               Absent.
                                         Only BIC is allowed.


3.16    [0..1]   ++ Instructed Agent     Usage rule:               Absent.
                                         Only BIC is allowed.


3.17    [0..1]   ++ Original             Mandatory                 Optional.
                 Transaction Reference   (An exact copy of all     If present, the
                                         attributes of the         following data has
                                         received DS-02 which      been copied from the
                                         is being returned)        original CT Return
                                         Usage rule:               message.
                                         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.

3.18    [0..1]   +++ Interbank           (AT-04 Amount of the Returned Interbank
                 Settlement Amount       credit transfer in Euro) Settlement Amount
                                                                   (3.10 in CT Return)

3.19    [0..1]   +++ Amount                                        Absent

3.24    [0..1]   +++ Interbank           (AT-42 Settlement         Interbank Settlement
                 Settlement Date         Date of the credit        Date (1.9 in CT
                                         transfer)                 Return)

3.25    {Or      +++ Requested                                     Absent
                 Execution Date

3.26    Or}      +++ Requested                                     Absent
                 Collection Date

3.27    [0..1]   +++ Creditor Scheme                               Absent
                 Information

3.28    [0..1]   +++ Settlement                                    Absent
                 Information

3.40    [0..1]   +++ Payment Type        (AT-40 Identification     Absent
                 Information             code of the Scheme)

3.51    [0..1]   +++ Payment Method                                Absent

3.71    [0..1]   +++ Remittance          (AT-05 Remittance         Absent
                 Information             information)

3.96    [0..1]   +++ Ultimate Debtor     (AT-08 Originator         Absent
                                         Reference Party)

3.97    [0..1]   +++ Debtor              (AT-02 Name of the        Absent
                                         Originator)
                                         (AT-03 Address of the
                                         Originator)
                                         (AT-10 Originator
                                         identification code)

3.98    [0..1]   +++ Debtor Account      (AT-01 IBAN of the        Absent
                                         Originator)

3.99    [0..1]   +++ Debtor Agent        (AT-06 BIC code of        Absent
                                         the Originator Bank)




        Page 122 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                        Requirements            ditional specifications

3.100   [0..1]   +++ Debtor Agent                               Absent
                 Account

3.101   [0..1]   +++ Creditor Agent     (AT-23 BIC code of      Absent
                                        the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                             Absent
                 Account

3.103   [0..1]   +++ Creditor           (AT-21 Name of the      Absent
                                        Beneficiary)
                                        (AT-22 Address of the
                                        Beneficiary
                                        (AT-24 Beneficiary
                                        identification code)

3.104   [0..1]   +++ Creditor Account   (AT-20 IBAN of the      Absent
                                        Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary       Absent
                                       Reference Party)




        Page 123 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.13 Inter CSM CT Return Reject (pacs.002.001.02)

         From CSM 1 to CSM 2.

         The Reject of a CT Return is not part of the SEPA CT Rulebook. Note that Original Transaction
         Identification, Interbank Settlement Amount and Interbank Settlement Date relate to the CT
         Return, not to the original credit transfer transaction.

         If the message does not conform to the ISO xsd schema then contact CSM 1.



 Index   Mult.    Message element        SEPA Core              Comments and ad-           Checks                    Error Code   Action
                                         Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                    Assigned by CSM 1,         Must be unique, for                    contact CSM 1
                  Identification                                must be unique over        the combination of
                                                                time for this message      sending party (CSM 1)
                                                                type (CT Return            and Message
                                                                Reject).                   Identification for this
                                                                                           message type (CT
                                                                                           Return Reject).

 1.2     [1..1]   ++ Creation Date                              The date and time the Must be a valid date                        contact CSM 1
                  Time                                          message has been      and time
                                                                created

 1.3     [0..1]   ++ Initiating Party

 1.4     [0..1]   ++ Forwarding Agent

 1.5     [0..1]   ++ Debtor Agent

 1.6     [0..1]   ++ Creditor Agent

 1.7     [0..1]   ++ Instructing Agent   Usage rule:            Absent.                    Must be absent                         contact CSM 1
                                         Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent    Usage rule:            Absent.                    Must be absent                         contact CSM 1
                                         Only BIC is allowed.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                           Message identification     If present, must                       contact CSM 1
                  Identification                                of the original CT         match with the
                                                                Return message as          corresponding value in
                                                                sent by CSM 2              the original CT Return

 2.2     Or}      ++ Network File Name                          If no Original Message
                                                                Identification is avail-
                                                                able then Network File
                                                                Name is filled.

 2.3     [1..1]   ++ Original Message                           Contains                   Must equal                             contact CSM 1
                  Name Identification                           'pacs.004.001.01'          'pacs.004.001.01'

 2.4     [0..1]   ++ Original Creation                          Only used for additio-
                  Date and Time                                 nal optional services

 2.5     [0..1]   ++ File Originator                            Only used for additio-
                                                                nal optional services

 2.6     [0..1]   ++ Original Number                            Only used for additio-
                  of Transactions                               nal optional services

 2.7     [0..1]   ++ Original Control                           Only used for additio-
                  Sum                                           nal optional services




         Page 124 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element      SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                      Requirements             ditional specifications

2.8     [0..1]   ++ Group Status      (R1 Type of R            Present, value =          Must be present                       contact CSM 1
                                      Message)                 „RJCT‟ or „PART‟.
                                      Usage rule:            RJCT means that the
                                      Only 'RJCT' and 'PART' whole original
                                      are allowed.           message is rejected.
                                                             The rejected
                                                             transactions are
                                                             present or absent
                                                             (0..n Transaction
                                                             Information And
                                                             Status).
                                                               PART means that
                                                               some transactions of
                                                               the original message
                                                               are rejected. The
                                                               rejected transactions
                                                               follow in Transaction
                                                               Information And
                                                               Status (1..n).

                                                                                         Value must be either                  contact CSM 1
                                                                                         'RJCT' or 'PART'

                                                                                         If value = 'PART', at                 contact CSM 1
                                                                                         least one Transaction
                                                                                         Information and
                                                                                         Status must be
                                                                                         present

2.9     [0..n]   ++ Status Reason     Usage rule:                                        Must be present in                    contact CSM 1
                 Information          Only one occurrence                                either the Original
                                      of 'Status Reason                                  Group Information
                                      Information' is                                    and Status or the
                                      allowed.                                           Transaction
                                      Usage rule:                                        Information and
                                      'Status Reason                                     Status.
                                      Information' must be
                                      present either in
                                      'Original Group Infor-
                                      mation and Status' or
                                      in 'Transaction
                                      Information and
                                      Status'.

                                                                                         If present, only one                  contact CSM 1
                                                                                         occurrence of 'Status
                                                                                         Reason Information' is
                                                                                         allowed

2.10    [0..1]   +++ Status Originator Mandatory               BIC or Name of CSM 1 Either BIC or Name                         contact CSM 1
                                      (R2 Identification of                         must be present.
                                      the Type of Party that
                                      initiated the reject)
                                      Usage rule:
                                      Limited to BIC to
                                      identify the Bank
                                      or CSM originating the
                                      status or „Name‟ to
                                      indicate the CSM when
                                      it has no BIC.

                                                                                         If present with BIC,                  contact CSM 1
                                                                                         must contain a BIC
                                                                                         from the BIC-directory

2.11    [0..1]   +++ Status Reason    Mandatory                                          Must be present                       contact CSM 1
                                      (R3 Reason Code for
                                      Non-Acceptance)




        Page 125 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                         Requirements             ditional specifications

2.12    {Or      ++++ Code               Possible values are:                               If present, must be                   contact CSM 1
                                         (reject) AC01, AG02,                               one of the approved
                                         MD03, MS03, RC01                                   SEPA Credit Transfer
                                         and TM01.                                          reject reasons (AC01,
                                                                                            AG02, MD03, MS03,
                                                                                            RC01 and TM01)

2.13    Or}      ++++ Proprietary        Usage rule:                                        If present, must be                   contact CSM 1
                                         To be used to specify                              one of the approved
                                         the regulatory reason,                             SEPA Credit Transfer
                                         using „RR01‟.                                      reject reasons (RR01)

2.14    [0..n]   +++ Additional Status                            Only used for additio-
                 Reason Information                               nal optional services

2.15    [0..n]   ++ Number of                                     Only used for additio-
                 Transactions Per                                 nal optional services
                 Status




3.0     [0..n]   + Transaction                                                              If Group Status =                     contact CSM 1
                 Information and                                                            'PART', at least one
                 Status                                                                     Transaction
                                                                                            Information and
                                                                                            Status must be
                                                                                            present

3.1     [0..1]   ++ Status               Mandatory                Assigned by CSM 1,        Must be present                       contact CSM 1
                 Identification          (R5 Specific reference   must be unique over
                                         of the bank that         time for this message
                                         initiated the reject)    type (CT Return
                                                                  Reject).

                                                                                            The combination of                    contact CSM 1
                                                                                            Status Originator
                                                                                            (2.10 or 3.8) and
                                                                                            Status Identification
                                                                                            must be unique for
                                                                                            this message type (CT
                                                                                            Return Reject).

3.2     [0..1]   ++ Original Payment                              Only used for additio-
                 Information                                      nal optional services
                 Identification

3.3     [0..1]   ++ Original             Usage rule:              Absent.
                 Instruction             Mandatory if provided
                 Identification          in the original
                                         instruction.

3.4     [0..1]   ++ Original End To      Mandatory                Present, Original End  Must be present                          contact CSM 1
                 End Identification                               To End Identification
                                                                  (3.7) of the original
                                                                  CT Return transaction.

                                                                                            Must match with the                   contact CSM 1
                                                                                            corresponding value in
                                                                                            the original CT Return

3.5     [0..1]   ++ Original             Mandatory                Present, Return           Must be present                       contact CSM 1
                 Transaction             Usage rule:              Identification (3.1) of
                 Identification          Must contain a           the original CT Return
                                         reference that is        transaction.
                                         unique over time.

                                                                                            Must match with the                   contact CSM 1
                                                                                            corresponding value in
                                                                                            the original CT Return




        Page 126 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                 Comments and ad-          Checks                   Error Code   Action
                                         Requirements              ditional specifications

3.6     [0..1]   ++ Transaction Status (R1 Type of R               Value = „RJCT‟            Must be present                       contact CSM 1
                                       message)
                                         Usage rule:
                                         Only „RJCT‟ is allowed.

                                                                                             Must equal 'RJCT'                     contact CSM 1

3.7     [0..n]   ++ Status Reason        Usage rule:                                         Must be present in                    contact CSM 1
                 Information             Only one occurrence                                 either the Original
                                         of 'Status Reason                                   Group Information
                                         Information' is                                     and Status or the
                                         allowed.                                            Transaction
                                         Usage rule:                                         Information and
                                         'Status Reason Infor-                               Status.
                                         mation' must be
                                         present either in
                                         'Original Group Infor-
                                         mation and Status' or
                                         in 'Transaction Infor-
                                         mation and Status'.

                                                                                             If present, only one                  contact CSM 1
                                                                                             occurrence of 'Status
                                                                                             Reason Information' is
                                                                                             allowed

3.8     [0..1]   +++ Status Originator Mandatory                   BIC or Name of            Either BIC or Name                    contact CSM 1
                                         (R2 Identification of     CSM 1.                    must be present
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

                                                                                             If present with BIC,                  contact CSM 1
                                                                                             must contain a BIC
                                                                                             from the BIC-directory

3.9     [0..1]   +++ Status Reason       Mandatory                                           Must be present                       contact CSM 1
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:                                If present, must be                   contact CSM 1
                                         (reject) AC01, AG02,                                one of the approved
                                         MD03, MS03, RC01                                    SEPA Credit Transfer
                                         and TM01.                                           reject reasons (AC01,
                                                                                             AG02, MD03, MS03,
                                                                                             RC01 and TM01)

3.11    Or}      ++++ Proprietary        Usage rule:                                         If present, must be                   contact CSM 1
                                         To be used to specify                               one of the approved
                                         the regulatory reason,                              SEPA Credit Transfer
                                         using the code „RR01‟.                              reject reasons (RR01)

3.12    [0..n]   +++ Additional Status                             Only used for additio-
                 Reason Information                                nal optional services

3.13    [0..n]   ++ Charges                                        Only used for additio-
                 Information                                       nal optional services

3.14    [0..1]   ++ Acceptance Date                                Only used for additio-
                 Time                                              nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:               Absent                    Must be absent                        contact CSM 1
                                         Only BIC is allowed.




        Page 127 of 148                                                                               Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                 Comments and ad-          Checks                    Error Code   Action
                                       Requirements              ditional specifications

3.16    [0..1]   ++ Instructed Agent   Usage rule:               Absent                    Must be absent                         contact CSM 1
                                       Only BIC is allowed.


3.17    [0..1]   ++ Original           Mandatory                 Present.                                                         contact CSM 1
                 Transaction Reference (An exact copy of all     The following data has
                                       attributes of the         been copied from the
                                       received DS-02 which      original CT Return
                                       is being returned)        message.
                                       Usage rule:
                                       The message ele-
                                       ments under „Original
                                       Transaction Reference‟
                                       must be populated
                                       with the same value
                                       as the message ele-
                                       ments of the original
                                       instruction, as defined
                                       within the following
                                       elements.

3.18    [0..1]   +++ Interbank         (AT-04 Amount of the Returned Interbank             Must match with the                    contact CSM 1
                 Settlement Amount     credit transfer in Euro) Settlement Amount          corresponding value in
                                                                 (3.10 in CT Return)       the original CT Return.

3.19    [0..1]   +++ Amount                                      Absent.

3.24    [0..1]   +++ Interbank         (AT-42 Settlement         Interbank Settlement      Must match with the                    contact CSM 1
                 Settlement Date       Date of the credit        Date (1.9 in CT           corresponding value in
                                       transfer)                 Return)                   the original CT Return.

3.25    {Or      +++ Requested                                   Absent.
                 Execution Date

3.26    Or}      +++ Requested                                   Absent.
                 Collection Date

3.27    [0..1]   +++ Creditor Scheme                             Absent.
                 Information

3.28    [0..1]   +++ Settlement                                  Absent.
                 Information

3.40    [0..1]   +++ Payment Type      (AT-40 Identification     Absent.
                 Information           code of the Scheme)

3.51    [0..1]   +++ Payment Method                              Absent.

3.71    [0..1]   +++ Remittance        (AT-05 Remittance         Absent.
                 Information           information)

3.96    [0..1]   +++ Ultimate Debtor   (AT-08 Originator         Absent.
                                       Reference Party)

3.97    [0..1]   +++ Debtor            (AT-02 Name of the        Absent.
                                       Originator)
                                       (AT-03 Address of the
                                       Originator)
                                       (AT-10 Originator
                                       identification code)

3.98    [0..1]   +++ Debtor Account    (AT-01 IBAN of the        Absent.
                                       Originator)

3.99    [0..1]   +++ Debtor Agent      (AT-06 BIC code of        Absent.
                                       the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                                Absent.
                 Account

3.101   [0..1]   +++ Creditor Agent    (AT-23 BIC code of        Absent.
                                       the Beneficiary Bank)




        Page 128 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                       Requirements            ditional specifications

3.102   [0..1]   +++ Creditor Agent                            Absent.
                 Account

3.103   [0..1]   +++ Creditor          (AT-21 Name of the      Absent.
                                       Beneficiary)
                                       (AT-22 Address of the
                                       Beneficiary
                                       (AT-24 Beneficiary
                                       identification code)

3.104   [0..1]   +++ Creditor Account (AT-20 IBAN of the       Absent.
                                      Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary      Absent.
                                       Reference Party)




        Page 129 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.14 Inter CSM CT Return Positive Status Report (pacs.002.001.02)

         From CSM 1 to CSM 2.

         This message is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA
         Core message.

         If the message does not conform to the ISO xsd schema the whole message will be rejected, the
         required action is to contact CSM 1.



 Index   Mult.    Message element        SEPA Core              Comments and ad-          Checks                    Error Code   Action
                                         Requirements           ditional specifications

 1.0     [1..1]   + Group Header

 1.1     [1..1]   ++ Message                                    Assigned by CSM 1,        Must be unique, for                    contact CSM 1
                  Identification                                must be unique over       the combination of
                                                                time for this message     sending party (CSM 1)
                                                                type (CT Return           and Message
                                                                Positive Status           Identification for this
                                                                Report).                  message type (CT
                                                                                          Return Positive Status
                                                                                          Report).

 1.2     [1..1]   ++ Creation Date                              The date and time the Must be a valid date                       contact CSM 1
                  Time                                          message has been      and time
                                                                created

 1.3     [0..1]   ++ Initiating Party                           Not applicable to pacs.

 1.4     [0..1]   ++ Forwarding Agent                           Not applicable to pacs.

 1.5     [0..1]   ++ Debtor Agent                               Not applicable to pacs.

 1.6     [0..1]   ++ Creditor Agent                             Not applicable to pacs.

 1.7     [0..1]   ++ Instructing Agent   Usage rule:            Absent.                   Must be absent                         contact CSM 1
                                         Only BIC is allowed.

 1.8     [0..1]   ++ Instructed Agent    Usage rule:            Absent.                   Must be absent                         contact CSM 1
                                         Only BIC is allowed.




 2.0     [1..1]   + Original Group
                  Information and
                  Status

 2.1     {Or      ++ Original Message                           Present, Message          Must be present                        contact CSM 1
                  Identification                                Identification of the
                                                                original CT Return
                                                                message as sent by
                                                                CSM 2.

                                                                                          Must match with the                    contact CSM 1
                                                                                          corresponding value in
                                                                                          the original Credit
                                                                                          Transfer

 2.2     Or}      ++ Network File Name                          Absent.

 2.3     [1..1]   ++ Original Message                           Value =                   Must equal                             contact CSM 1
                  Name Identification                           'pacs.004.001.01'         'pacs.004.001.01'

 2.4     [0..1]   ++ Original Creation                          Only used for additio-
                  Date and Time                                 nal optional services

 2.5     [0..1]   ++ File Originator                            Only used for additio-
                                                                nal optional services




         Page 130 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                       Requirements             ditional specifications

2.6     [0..1]   ++ Original Number                             Optional. Number Of       If present, must                      contact CSM 1
                 of Transactions                                Transactions of the       match with the
                                                                original CT Return        corresponding value in
                                                                message.                  the original CT Return

2.7     [0..1]   ++ Original Control                            Only used for additio-
                 Sum                                            nal optional services

2.8     [0..1]   ++ Group Status       (R1 Type of R            Present                   Must be present.                      contact CSM 1
                                       Message)                 Allowed values:
                                       Usage rule:            „ACTC‟, 'ACSC' and
                                       Only 'RJCT' and 'PART' 'PART'.
                                       are allowed.
                                                                ACTC means that the
                                                                original CT Return
                                                                message has been
                                                                successfully validated
                                                                (ready for further
                                                                processing).
                                                                ACSC means that all
                                                                transactions of the
                                                                original CT Return
                                                                message have been
                                                                settled.
                                                                PART means that part
                                                                of the transactions of
                                                                the original CT Return
                                                                message have been
                                                                settled.
                                                                The validated (ACTC)
                                                                or settled
                                                                (ACSC/PART)
                                                                transactions can be
                                                                present or absent:
                                                                0..n Transaction
                                                                Information and
                                                                Status.

                                                                                          Must equal „ACTC‟,                    contact CSM 1
                                                                                          'ACSC' or 'PART'

2.9     [0..n]   ++ Status Reason      Usage rule:              Exactly one               Exactly one                           contact CSM 1
                 Information           Only one occurrence      occurrence is present.    occurrence must be
                                       of 'Status Reason                                  present.
                                       Information' is
                                       allowed.
                                       Usage rule:
                                       'Status Reason
                                       Information' must be
                                       present either in
                                       'Original Group
                                       Information and
                                       Status' or in
                                       'Transaction
                                       Information and
                                       Status'.

2.10    [0..1]   +++ Status Originator Mandatory                Present, the BIC or       Either BIC or Name                    contact CSM 1
                                       (R2 Identification of    name of CSM 1.            must be present
                                       the Type of Party that
                                       initiated the reject)
                                       Usage rule:
                                       Limited to BIC to
                                       identify the Bankor
                                       CSM originating the
                                       status or „Name‟ to
                                       indicate the CSM when
                                       it has no BIC.




        Page 131 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core              Comments and ad-          Checks                   Error Code   Action
                                         Requirements           ditional specifications

                                                                                          If present with BIC,                  contact CSM 1
                                                                                          must contain a BIC
                                                                                          from the BIC-directory

2.11    [0..1]   +++ Status Reason       Mandatory              Absent if Group Status
                                         (R3 Reason Code for    is „ACTC‟.
                                         Non-Acceptance)        Present if Group
                                                                Status is „ACSC‟ or
                                                                „PART‟.

2.12    {Or      ++++ Code               Possible values are:   Contains the code         Must be present if                    contact CSM 1
                                         (reject) AC01, AG02,   'NARR' (= Narrative). Group Status is „ACSC‟
                                         MD03, MS03, RC01                                 or „PART‟.
                                         and TM01.

                                                                                          If present, must                      contact CSM 1
                                                                                          contain the value
                                                                                          „NARR‟

2.13    Or}      ++++ Proprietary        Usage rule:            Absent.
                                         To be used to specify
                                         the regulatory reason,
                                         using „RR01‟.

2.14    [0..n]   +++ Additional Status                          If Group Status is        Settlement date must                  contact CSM 1
                 Reason Information                             „ACSC‟ or „PART‟, two     be present if Group
                                                                occurrences are           Status is „ACSC‟ or
                                                                present, for              „PART‟.
                                                                settlement date and
                                                                settled amount:
                                                                1./INTRBKSTTLMDT/
                                                                YYYY-MM-DD
                                                                2./TTLINTRBKSTTLM
                                                                AMT/<alpha-3
                                                                currency
                                                                code><amount>
                                                                Note that the
                                                                presence of
                                                                Additional Status
                                                                Reason Information
                                                                is against ISO's
                                                                StatusReason-
                                                                InformationRule.

                                                                                          Settlement date must                  contact CSM 1
                                                                                          be a valid date

                                                                                          Settled amount must                   contact CSM 1
                                                                                          be present if Group
                                                                                          Status is „ACSC‟ or
                                                                                          „PART‟.

                                                                                          Currency code must                    contact CSM 1
                                                                                          be "EUR"

                                                                                          Amount must be ≥                      contact CSM 1
                                                                                          0.01

                                                                                          Amount must be ≤                      contact CSM 1
                                                                                          999999999999999.99

                                                                                          Maximum 2 fraction                    contact CSM 1
                                                                                          digits

2.15    [0..n]   ++ Number of                                   One occurrence is         One occurrence must                   contact CSM 1
                 Transactions Per                               present if Group          be present if Group
                 Status                                         Status is 'PART'.         Status is „PART‟




        Page 132 of 148                                                                            Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core                Comments and ad-          Checks                   Error Code   Action
                                        Requirements             ditional specifications

2.16    [1..1]   +++ Detailed Number                             Contains the number
                 Of Transactions                                 of settled
                                                                 transactions.
                                                                 Note that the settled
                                                                 transactions them-
                                                                 selves (3.0) may be
                                                                 absent, which is not
                                                                 fully in line with ISO.

2.17    [1..1]   +++ Detailed Status                             Contains code 'ACSC'      Must contain the value                contact CSM 1
                                                                 (= settled).              „ACSC‟

2.18    [0..1]   +++ Detailed Control
                 Sum




3.0     [0..n]   + Transaction                                   The validated/settled
                 Information and                                 transactions can be
                 Status                                          present or absent.

3.1     [0..1]   ++ Status              Mandatory                Present. Assigned by   Must be present                          contact CSM 1
                 Identification         (R5 Specific reference   CSM 1, must be
                                        of the bank that         unique over time for
                                        initiated the reject)    this message type (CT
                                                                 Return Positive Status
                                                                 Report).

                                                                                           The combination of                    contact CSM 1
                                                                                           Status Originator
                                                                                           (2.10) and Status
                                                                                           Identification must be
                                                                                           unique

3.2     [0..1]   ++ Original Payment                             Only used for additio-
                 Information                                     nal optional services
                 Identification

3.3     [0..1]   ++ Original            Usage rule:              Absent
                 Instruction            Mandatory if provided
                 Identification         in the original
                                        instruction.

3.4     [0..1]   ++ Original End To     Mandatory                Present, Original End
                 End Identification                              To End Identification
                                                                 (3.7) of the original
                                                                 CT Return transaction.

3.5     [0..1]   ++ Original            Mandatory                Present, Return           Must be present                       contact CSM 1
                 Transaction            Usage rule:              Identification (3.1) of
                 Identification         Must contain a           the original CT Return
                                        reference that is        transaction.
                                        unique over time.

                                                                                           Must match with the                   contact CSM 1
                                                                                           corresponding value in
                                                                                           the original Credit
                                                                                           Transfer

3.6     [0..1]   ++ Transaction Status (R1 Type of R             Present.                  Must be present                       contact CSM 1
                                       message)                  The value is
                                        Usage rule:             - „ACTC‟ if Group
                                        Only 'RJCT' is allowed.   Status is „ACTC‟;
                                                                 - „ACSC‟ if Group
                                                                   Status is „ACSC‟ or
                                                                   „PART‟.




        Page 133 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core                Comments and ad-          Checks                  Error Code   Action
                                         Requirements             ditional specifications

                                                                                            Must equal                           contact CSM 1
                                                                                            - „ACTC‟ if Group
                                                                                              Status is „ACTC‟;
                                                                                            - „ACSC‟ if Group
                                                                                              Status is „ACSC‟ or
                                                                                              „PART‟.

3.7     [0..n]   ++ Status Reason        Usage rule:              Absent.                   Must be absent                       contact CSM 1
                 Information             Only one occurrence
                                         of 'Status Reason
                                         Information' is
                                         allowed.
                                         Usage rule:
                                         'Status Reason
                                         Information' must be
                                         present either in
                                         'Original Group Infor-
                                         mation and Status' or
                                         in 'Transaction Infor-
                                         mation and Status'.

3.8     [0..1]   +++ Status Originator Mandatory
                                         (R2 Identification of
                                         the Type of Party that
                                         initiated the reject)
                                         Usage rule:
                                         Limited to BIC to
                                         identify the bank or
                                         CSM originating the
                                         status or „Name‟ to
                                         indicate the CSM when
                                         it has no BIC.

3.9     [0..1]   +++ Status Reason       Mandatory
                                         (R3 Reason Code for
                                         Non-Acceptance)

3.10    {Or      ++++ Code               Possible values are:
                                         (reject) AC01, AG02,
                                         MD03, MS03, RC01
                                         and TM01.

3.11    Or}      ++++ Proprietary        Usage rule:
                                         To be used to specify
                                         the regulatory reason,
                                         using the code „RR01‟.

3.12    [0..n]   +++ Additional Status
                 Reason Information

3.13    [0..n]   ++ Charges                                       Only used for additio-
                 Information                                      nal optional services

3.14    [0..1]   ++ Acceptance Date                               Only used for additio-
                 Time                                             nal optional services

3.15    [0..1]   ++ Instructing Agent    Usage rule:              Absent.                   Must be absent                       contact CSM 1
                                         Only BIC is allowed.

3.16    [0..1]   ++ Instructed Agent     Usage rule:              Absent.                   Must be absent                       contact CSM 1
                                         Only BIC is allowed.




        Page 134 of 148                                                                              Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core                 Comments and ad-          Checks                    Error Code   Action
                                       Requirements              ditional specifications

3.17    [0..1]   ++ Original           Mandatory                 Optional.
                 Transaction Reference (An exact copy of all     If present, the
                                       attributes of the         following data has
                                       received DS-02 which      been copied from the
                                       is being returned)        original CT Return
                                       Usage rule:               message.
                                       The message ele-
                                       ments under „Original
                                       Transaction Reference‟
                                       must be populated
                                       with the same value
                                       as the message ele-
                                       ments of the original
                                       instruction, as defined
                                       within the following
                                       elements.

3.18    [0..1]   +++ Interbank         (AT-04 Amount of the Returned Interbank             Must match with the                    contact CSM 1
                 Settlement Amount     credit transfer in Euro) Settlement Amount          corresponding value in
                                                                 (3.10 in CT Return)       the original CT Return.

3.19    [0..1]   +++ Amount                                      Absent

3.24    [0..1]   +++ Interbank         (AT-42 Settlement         Interbank Settlement      Must match with the                    contact CSM 1
                 Settlement Date       Date of the credit        Date                      corresponding value in
                                       transfer)                 (1.9 in CT Return)        the original CT Return.

3.25    {Or      +++ Requested                                   Absent
                 Execution Date

3.26    Or}      +++ Requested                                   Absent
                 Collection Date

3.27    [0..1]   +++ Creditor Scheme                             Absent
                 Information

3.28    [0..1]   +++ Settlement                                  Absent
                 Information

3.40    [0..1]   +++ Payment Type      (AT-40 Identification     Absent
                 Information           code of the Scheme)

3.51    [0..1]   +++ Payment Method                              Absent

3.71    [0..1]   +++ Remittance        (AT-05 Remittance         Absent
                 Information           information)

3.96    [0..1]   +++ Ultimate Debtor   (AT-08 Originator         Absent
                                       Reference Party)

3.97    [0..1]   +++ Debtor            (AT-02 Name of the        Absent
                                       Originator)
                                       (AT-03 Address of the
                                       Originator)
                                       (AT-10 Originator
                                       identification code)

3.98    [0..1]   +++ Debtor Account    (AT-01 IBAN of the        Absent
                                       Originator)

3.99    [0..1]   +++ Debtor Agent      (AT-06 BIC code of        Absent
                                       the Originator Bank)

3.100   [0..1]   +++ Debtor Agent                                Absent
                 Account

3.101   [0..1]   +++ Creditor Agent    (AT-23 BIC code of        Absent
                                       the Beneficiary Bank)

3.102   [0..1]   +++ Creditor Agent                              Absent
                 Account




        Page 135 of 148                                                                             Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element       SEPA Core               Comments and ad-          Checks                 Error Code   Action
                                       Requirements            ditional specifications

3.103   [0..1]   +++ Creditor          (AT-21 Name of the      Absent
                                       Beneficiary)
                                       (AT-22 Address of the
                                       Beneficiary
                                       (AT-24 Beneficiary
                                       identification code)

3.104   [0..1]   +++ Creditor Account (AT-20 IBAN of the       Absent
                                      Beneficiary)

3.105   [0..1]   +++ Ultimate Creditor (AT-28 Beneficiary      Absent
                                       Reference Party)




        Page 136 of 148                                                                           Doc ref: EACHA 2007-3.02 Interoperability
         EACHA Interoperability Framework (v3.02)




6.5.15 Bank - CSM CT Cancellation (pacs.006.001.01)

         From Bank 1 to CSM 1.

         This message is not part of the SEPA CT Rulebook; it is an optional service message, not a SEPA
         Core message.

         If the message does not conform to the ISO xsd schema the whole message will be rejected with
         Error Code 'MD03'.



 Index   Mult.    Message element         SEPA Core      Comments and ad-          Checks                   Error Code   Action
                                          Requirements   ditional specifications

 1.0     [1..1]   +Group Header

 1.1     [1..1]   ++ Message                             Assigned by Bank 1,       The combination of     MD03           reject the
                  Identification                         must be unique over       Instructing Agent and (Duplicate)     message
                                                         time for this message     Message Identification
                                                         type (CT Cancellation)    must be unique for
                                                                                   this message type (CT
                                                                                   Cancellation)

 1.2     [1..1]   ++ Creation Date                       The date and time the Must be a valid date         MD03         reject the
                  Time                                   message has been      and time                                  message
                                                         created

 1.3     [1..1]   ++ Number Of                                                     Must Equal the           MD03         reject the
                  Transactions                                                     number of                             message
                                                                                   transactions in the
                                                                                   message

 1.4     [0..1]   ++ Control Sum                                                   Must be Equal to the     MD03         reject the
                                                                                   sum of all Interbank                  message
                                                                                   Settlement amounts
                                                                                   present at transaction
                                                                                   level

 1.5     [0..1]   ++ Group Cancellation

 1.6     [0..1]   ++ Initiating Party                    Not allowed in PACS

 1.7     [1..1]   ++ Forwarding Agent                    Not allowed in PACS

 1.8     [1..1]   ++ Debtor Agent                        Not allowed in PACS

 1.9     [0..1]   ++ Creditor Agent                      Not allowed in PACS

 1.10    [0..1]   ++ Instructing Agent                   Mandatory. Contains     Must be present            MD03         reject the
                                                         the BIC of the agent                                            message
                                                         that instructs the next
                                                         party in the chain to
                                                         carry out the (set of)
                                                         instruction(s): Bank 1.

                                                                                   If present, must         MD03         reject the
                                                                                   contain BIC                           message

                                                                                   If present with BIC,   RC01           reject the
                                                                                   must contain a BIC                    message
                                                                                   from the BIC-directory

 1.11    [0..1]   ++ Instructed Agent                    Absent.                   Must be absent           MD03         reject the
                                                                                                                         message




 2.0     [1..1]   +Original Group
                  Information

 2.1     [1..1]   ++ Original Message                    Message identification    Must match with the    MD03           reject the
                  Identification                         of the original Credit    corresponding value in                message
                                                         Transfer message as       the original Credit
                                                         received by CSM 1.        Transfer




         Page 137 of 148                                                                    Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element        SEPA Core      Comments and ad-          Checks                 Error Code   Action
                                        Requirements   ditional specifications

2.2     [1..1]   ++ Original Message                                             Must equal             MD03         reject the
                 Name Identification                                             „pacs.008.001.01‟.                  message

2.3     [0..1]   ++ Original Creation
                 Date Time

2.4     [0..n]   ++ Cancellation                                                 Cancellation Reason    MD03         reject the
                 Reason Information                                              Information must be                 message
                                                                                 present either at
                                                                                 Group Information or
                                                                                 at Transaction
                                                                                 Information

                                                                                 If present at Group    MD03         reject the
                                                                                 Information must                    message
                                                                                 contain only one
                                                                                 occurrence

2.5     [0..1]   +++ Cancellation                      All checks are            If present with BIC,   RC01         reject the
                 Originator                            conditional on            must contain a BIC                  message
                                                       Cancellation Reason       from the BIC-directory
                                                       Information to be
                                                       present at Group
                                                       Information level

                                                                                 Either BIC or Name     MD03         reject the
                                                                                 must be present                     message

                                                                                 Must be present        MD03         reject the
                                                                                                                     message

2.6     [0..1]   +++ Cancellation
                 Reason

2.7     {Or      ++++ Code

2.8     Or}      ++++ Proprietary

2.9     [0..n]   +++ Additional
                 Cancellation Reason
                 Information




3.0     [0..n]   + Transaction
                 Information

3.1     [0..1]   ++ Cancellation                                                 Must be present        MD03         reject the
                 Identification                                                                                      transaction

3.2     [0..1]   ++ Original Payment
                 Information
                 Identification

3.3     [0..1]   ++ Original                                                     Must match with the    MD03         reject the
                 Instruction                                                     corresponding value in              transaction
                 Identification                                                  the original Credit
                                                                                 Transfer

3.4     [0..1]   ++ Original End To                                              Must be present        MD03         reject the
                 End Identification                                                                                  transaction

                                                                                 Must match with the    MD03         reject the
                                                                                 corresponding value in              transaction
                                                                                 the original Credit
                                                                                 Transfer

3.5     [0..1]   ++ Original                                                     Must be present        MD03         reject the
                 Transaction                                                                                         transaction
                 Identification




        Page 138 of 148                                                                   Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element          SEPA Core      Comments and ad-          Checks                 Error Code   Action
                                          Requirements   ditional specifications

                                                                                   Must match with the    MD03         reject the
                                                                                   corresponding value in              transaction
                                                                                   the original Credit
                                                                                   Transfer

3.6     [0..1]   ++ Original Interbank                                             Must be present        MD03         reject the
                 Settlement Amount                                                                                     transaction

                                                                                   Must match with the    MD03         reject the
                                                                                   corresponding value in              transaction
                                                                                   the original Credit
                                                                                   Transfer

3.7     [0..1]   ++ Original Instructed
                 Amount

3.8     [0..1]   ++ Instructing Agent                    Absent.                   Must be absent         MD03         reject the
                                                         (Present at group                                             transaction
                                                         level: 1.10)

3.9     [0..1]   ++ Instructed Agent                     Absent.                   Must be absent         MD03         reject the
                                                                                                                       transaction

3.10    [0..n]   ++ Cancellation                                                   Cancellation Reason    MD03         reject the
                 Reason Information                                                Information must be                 message
                                                                                   present either at
                                                                                   Group Information or
                                                                                   at Transaction
                                                                                   Information

                                                                                   If present at          MD03         reject the
                                                                                   Transaction                         transaction
                                                                                   Information must
                                                                                   contain only one
                                                                                   occurrence

3.11    [0..1]   +++ Cancellation                        All checks are         If present with BIC,   RC01            reject the
                 Originator                              conditional on         must contain a BIC                     transaction
                                                         Cancellation Reason    from the BIC-directory
                                                         Information to be
                                                         present at Transaction
                                                         Information level

                                                                                   Either BIC or Name     MD03         reject the
                                                                                   must be present                     transaction

                                                                                   Must be present        MD03         reject the
                                                                                                                       transaction

3.12    [0..1]   +++ Cancellation
                 Reason

3.13    {Or      ++++ Code

3.14    Or}      ++++ Proprietary

3.15    [0..n]   +++ Additional
                 Cancellation Reason
                 Information

3.16    [0..1]   ++ Original                                                       All mandatory          MD03         reject the
                 Transaction Reference                                             elements of the                     transaction
                                                                                   original Credit
                                                                                   Transfer must be
                                                                                   present

                                                                                   Must be present        MD03         reject the
                                                                                                                       transaction

                                                                                   All elements supplied MD03          reject the
                                                                                   must match with the                 transaction
                                                                                   corresponding value in
                                                                                   the original Credit
                                                                                   Transfer




        Page 139 of 148                                                                     Doc ref: EACHA 2007-3.02 Interoperability
        EACHA Interoperability Framework (v3.02)




Index   Mult.    Message element         SEPA Core      Comments and ad-          Checks                  Error Code   Action
                                         Requirements   ditional specifications

3.17    [0..1]   +++ Interbank
                 Settlement Amount

3.18    [0..1]   +++ Amount

3.23    [0..1]   +++ Interbank                                                    The date cannot be in   TM01         reject the
                 Settlement Date                                                  the past                             transaction

                                                                                  The original Credit     TM01         reject the
                                                                                  Transfer must not be                 transaction
                                                                                  processed yet

3.24    {Or      +++ Requested
                 Execution Date

3.25    Or}      +++ Requested
                 Collection Date

3.26    [0..1]   +++ Creditor Scheme
                 Identification

3.27    [0..1]   +++ Settlement
                 Information

3.39    [0..1]   +++ Payment Type
                 Information

3.50    [0..1]   +++ Payment Method

3.51    [0..1]   +++ Mandate Related
                 Information

3.70    [0..1]   +++ Remittance
                 Information

3.95    [0..1]   +++ Ultimate Debtor

3.96    [0..1]   +++ Debtor

3.97    [0..1]   +++ Debtor Account

3.98    [0..1]   +++ Debtor Agent

3.99    [0..1]   +++ Debtor Agent
                 Account

3.100   [0..1]   +++ Creditor Agent

3.101   [0..1]   +++ Creditor Agent
                 Account

3.102   [0..1]   +++ Creditor

3.103   [0..1]   +++ Creditor Account

3.104   [0..1]   +++ Ultimate Creditor




        Page 140 of 148                                                                    Doc ref: EACHA 2007-3.02 Interoperability
       EACHA Interoperability Framework (v3.02)




6.5.16 Status Reason in pacs.002

       The table below shows the Status Reason codes allowed in SEPA Core+AOS messages. Only the
       shaded codes are allowed in a Core messages.



       Status Reason / Code

       Code     Name                          Definition
       AC01     IncorrectAccountNumber        Account identifier incorrect (i.e. invalid IBAN)
       AC04     ClosedAccountNumber           Account closed
       AC06     BlockedAccount                Account blocked
       AG01     TransactionForbidden          Transaction forbidden on this type of account (formerly
                                              NoAgreement).
       AG02     InvalidBankOperationCode      Operation/transaction code incorrect, invalid file format
                                              Usage rule:
                                              To be used for incorrect 'operation/transaction' code
       AM01     ZeroAmount                    Specified message amount is equal to zero.
       AM02     NotAllowedAmount              Specified transaction/message amount is greater than
                                              allowed maximum.
       AM03     NotAllowedCurrency            Specified message amount is in an non processable currency
                                              outside of existing agreement.
       AM04     InsufficientFunds             Insufficient funds
       AM05     Duplication                   Duplicate collection
       AM06     TooLowAmount                  Specified transaction amount is less than agreed minimum.
       AM07     BlockedAmount                 Amount specified in message has been blocked by
                                              regulatory authorities.
       AM09     WrongAmount                   Amount received is not the amount agreed or expected.
       AM10     InvalidControlSum             Sum of instructed amounts does not equal the control sum.
       BE01     InconsistentWith-             Identification of end customer is not consistent with
                EndCustomer                   associated account number. (formerly CreditorConsistency)
       BE04     MissingCreditorAddress        Specification of creditor's address, which is required for
                                              payment, is missing/not correct (formerly
                                              IncorrectCreditorAddress).
       BE05     UnrecognisedInitiatingParty   Party who initiated the message is not recognised by the
                                              end customer.
       BE06     UnknownEndCustomer            End customer specified is not known at associated
                                              Sort/National Bank Code or does no longer exist in the
                                              books.
       BE07     MissingDebtorAddress          Specification of debtor's address, which is required for
                                              payment, is missing/not correct.
       DT01     InvalidDate                   Invalid date (eg, wrong settlement date).
       ED01     CorrespondentBank-            Correspondent bank not possible.
                NotPossible
       ED03     BalanceInfoRequested          Balance of payments complementary info is requested.




       Page 141 of 148                                                     Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




Code      Name                          Definition
ED05      SettlementFailed              Settlement of the transaction has failed.
MD01      NoMandate                     No valid Mandate
                                        Account blocked for direct debit by the Debtor
MD02      MissingMandateInformation-    Mandate data missing or incorrect
          InMandate                     Account blocked for Direct Debit by the Debtor
MD03      InvalidFileFormatForOther-    Operation/transaction code incorrect, invalid file format
          ReasonthanGrouping-           Usage rule:
          Indicator                     to be used for invalid file format
MD04      InvalidFileFormatForOther-    File format incorrect in terms of grouping indicator.
          GroupingIndicator
MD06      RefundRequestBy-              Return of funds requested by end customer.
          EndCustomer
MD07      EndCustomer Deceased          End customer is deceased.
MS02      NotSpecifiedReason-           Reason has not been specified by end customer.
          CustomerGenerated
MS03      NotSpecifiedReason-           Reason not specified
          AgentGenerated
NARR      Narrative                     Reason is provided as narrative information in the additional
                                        reason information.
RC01      BankIdentifierIncorrect       Bank identifier incorrect (i.e. invalid BIC)
RF01      NotUniqueTransaction-         Transaction reference is not unique within the message.
          Reference
TM01      CutOffTime                    Associated message was received after agreed processing
                                        cut-off time.

When a CSM receives a Core+AOS CT Reject transaction that has to be forwarded in a Core
message, then conversion may be necessary:

   A Status Reason Code that is not allowed in a Core message is converted into code 'MS03'.

   A Status Reason Proprietary other than 'RR01', is converted into code 'MS03' in element Status
    Reason Code.

   Any Additional Status Reason Information elements are not forwarded.




Page 142 of 148                                                      Doc ref: EACHA 2007-3.02 Interoperability
       EACHA Interoperability Framework (v3.02)




6.5.17 Return Reason in pacs.004
       The table below shows the Return Reason codes allowed in SEPA Core+AOS messages.
       Only the shaded codes are allowed in a (CT) Core message.



       Return Reason / Code

       Code     Name                          Definition
       AC01     IncorrectAccountNumber        Account identifier incorrect (i.e. invalid IBAN or account
                                              number does not exist)
       AC04     ClosedAccountNumber           Account closed
       AC06     BlockedAccount                Account blocked, reason not specified
       AG01     TransactionForbidden          Credit transfer forbidden on this type of account (e.g.
                                              savings account)
       AG02     InvalidBankOperationCode      Operation/transaction code incorrect, invalid file format
                                              Usage rule:
                                              To be used for incorrect 'operation/transaction' code
       AM01     ZeroAmount                    Specified message amount is equal to zero.
       AM02     NotAllowedAmount              Specified transaction/message amount is greater than
                                              allowed maximum.
       AM03     NotAllowedCurrency            Specified message amount is in an non processable currency
                                              outside of existing agreement.
       AM04     InsufficientFunds             Insufficient funds
       AM05     Duplication                   Duplicate collection
       AM06     TooLowAmount                  Specified transaction amount is less than agreed minimum.
       AM07     BlockedAmount                 Amount specified in message has been blocked by
                                              regulatory authorities.
       AM09     WrongAmount                   Amount received is not the amount agreed or expected.
       AM10     InvalidControlSum             Sum of instructed amounts does not equal the control sum.
       BE01     InconsistentWith-             Identification of end customer is not consistent with
                EndCustomer                   associated account number. (formerly CreditorConsistency)
       BE04     MissingCreditorAddress        Account address invalid
       BE05     UnrecognisedInitiatingParty   Party who initiated the message is not recognised by the
                                              end customer.
       BE06     UnknownEndCustomer            End customer specified is not known at associated
                                              Sort/National Bank Code or does no longer exist in the
                                              books.
       BE07     MissingDebtorAddress          Specification of debtor's address, which is required for
                                              payment, is missing/not correct.
       DT01     InvalidDate                   Invalid date (eg, wrong settlement date).
       ED01     CorrespondentBank-            Correspondent bank not possible.
                NotPossible
       ED03     BalanceInfoRequested          Balance of payments complementary info is requested.
       ED05     SettlementFailed              Settlement of the transaction has failed.




       Page 143 of 148                                                    Doc ref: EACHA 2007-3.02 Interoperability
EACHA Interoperability Framework (v3.02)




Code      Name                          Definition
MD01      NoMandate                     No valid Mandate
                                        Account blocked for direct debit by the debtor
MD02      MissingMandateInformationIn Mandate related information data required by the scheme is
          Mandate                     missing
MD03      InvalidFileFormatForOther-    Operation/transaction code incorrect, invalid file format
          Reasonthan-                   Usage rule:
          GroupingIndicator             to be used for invalid file format
MD04      InvalidFileFormatForOther-    File format incorrect in terms of grouping indicator.
          GroupingIndicator
MD06      RefundRequestByEndCustom      Return of funds requested by end customer.
          er
MD07      EndCustomer Deceased          Beneficiary deceased
MS02      NotSpecifiedReason-           By order of the Beneficiary
          CustomerGenerated
MS03      NotSpecifiedReason-           Reason not specified
          AgentGenerated
NARR      Narrative                     Reason is provided as narrative information in the additional
                                        reason information.
RC01      BankIdentifierIncorrect       Bank identifier incorrect (i.e. invalid BIC)
RF01      NotUniqueTransaction-         Transaction reference is not unique within the message.
          Reference
TM01      CutOffTime                    Associated message was received after agreed processing
                                        cut-off time.



When a CSM receives a Core+AOS CT Return transaction that has to be forwarded in a Core
message, then conversion may be necessary:

   A Return Reason Code that is not allowed in a Core message is converted into code 'MS03'.

   A Return Reason Proprietary other than 'RR01', is converted into code 'MS03' in element Return
    Reason Code.

   Any Additional Return Reason Information elements are not forwarded.




Page 144 of 148                                                       Doc ref: EACHA 2007-3.02 Interoperability
    EACHA Interoperability Framework (v3.02)




7   Annex IV: Bulking Mechanism


    EACHA recognises that several different bulking mechanisms are being developed or have been
    developed. As part of technical interoperability EACHA also recognises that if a bulking mechanism
    is to be used, it should be part of the interoperability framework. Otherwise there may still be a
    considerable effort needed for connecting to a CSM or switching to another CSM. The current
    message specifications do not make use of a bulking mechanism, but instead single XML-messages
    are expected to be exchanged per file.
    As part of the ongoing development of the EACHA framework, in the future EACHA will be looking
    into the possibilities of a bulking mechanism and the different (standardised) solutions available.




    Page 145 of 148                                                    Doc ref: EACHA 2007-3.02 Interoperability
    EACHA Interoperability Framework (v3.02)




8   Annex A : Participant list EACHA Task force on Interoperability




    BBS, Norway                             Fina, Croatia                     SSB-SIA, Italia
    BdI, Italy                              Giro, Hungary                     SIBS, Portugal
    BGC, Sweden                             Iberpay, Spain                    SIC, Switzerland
    BS, Bulgaria                            Equens, Netherlands/Germany       STET, France
    Deutsche Bundesbank, Germany            KIR, Poland                       VocaLink, United Kingdom
    CEC, Belgium                            OE NB, Austria
    DIAS, Greece                            PBS, Denmark



    For information on this technical paper please contact:
    eacha@stet.eu




    Page 146 of 148                                                 Doc ref: EACHA 2007-3.02 Interoperability
    EACHA Interoperability Framework (v3.02)




9   Annex B: Timescales



    Date/Period           Milestone


    August 2006           EACHA Technical Paper on Interoperability v0.93 published to EPC


    End March 2007        Interoperability framework 2.0 published to stakeholders for consultation
                          i.e. Central Banks and European banking industry


    End May 2007          Feedback from industry consultation


    End June 2007         Version 2.1 of the framework issued including consultation feedback


    Q3 2007               Version 3.0/3.02 will include the results of work on outstanding issues


    28 January 2008       Start of SEPA




    Page 147 of 148                                                  Doc ref: EACHA 2007-3.02 Interoperability
     EACHA Interoperability Framework (v3.02)




10   Annex C: Other Related Documents


     Technical Paper: “Towards a Technical Interoperability Framework for SEPA - Compliant Giro
     Payments Processing” version v0.93; (EACHA, September 2006)

     EPC170/05 CSM framework version 1.0 March, 2006

     The EPC publications EPC016/06 “SEPA Direct Debit Scheme Rulebook” and EPC125/05 “SEPA
     Credit Transfer Scheme Rulebook version 2.2”, November 2006 and the respective SEPA Scheme
     Implementation Guidelines

     TOWARDS A SINGLE EURO PAYMENTS AREA – Objectives and Deadlines (4th Progress Report by
     ECB) 17 February 2006




     Page 148 of 148                                                   Doc ref: EACHA 2007-3.02 Interoperability

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:21
posted:7/3/2011
language:English
pages:148