Bank to Customer Reject Credit Transfer Dataset. pain format

Size: px
Start display at page:

Download "Bank to Customer Reject Credit Transfer Dataset. pain format"

Transcription

1 Bank to Customer Reject Credit Transfer Dataset pain format Verzija Status / izmjene Datum Autor 1.0 Prva inicijalna verzija Razrada formata poruke Razrada formata poruke reject od CSM-a Razrada formata poruke return poruke Razrada formata poruke reject od banke, reject od CSM, return Promjena naziva Remittance Information Dopuna formata sa svim podelementima i usuglašavanje oko kontrola i opisa polja Implementacija novih pravila po verziji Implementation Guidelines 8.0 Razrada formata za non SEPA plaćanja Dodan kod XK za Kosovo uz ISO code Anamarija Manojlović Gordana Bolanča Željka Gašparić Operativna grupa Operativna grupa Operativna grupa (polje 3.41 i 3.68 Operativna grupa Operativna grupa kolovoz, rujan, listopad i studeni 2014 siječanj veljača Operativna grupa Operativna grupa Operativna grupa Operativna grupa

2 Bank to Customer Reject Credit Transfer Dataset (based on DS-03) Pažnja: ovaj Vodič za implementaciju daje preporuke za korištenje XML poruke i nije obavezan. Ovaj Vodič za implementaciju nije dovoljan za cjelokupnu implementaciju ove poruke i zahtijeva dodatne informacije koje se odnose na dogovor između korisnika (klijenta) i PPU korisnika. Rulebook (Pravilnik) ovo ne propisuje Upotreba Customer Payment Status Report (pain ) Kod RJCT mora se upotrebljavati na nivou poruke, grupe ili transakcije radi prijenosa instrukcije (poruke) CT Odbijanja (Credit Transfer Reject) između banaka i KPU-a. Poruke se odnose na skupna ili pojedinačna plaćanja. Opaska: Izbor atributa u AT-R1 određuje se iz Message Name,, the Original Message Name Identification, pain and Group Status or Transaction Status. Opaska: Atribut AT-R4 -The Settlement Date for the Return se ne upotrebljava u porukama Odbijanja (reject instructions). Opaska: Elementi poruke unutar Original Transaction Reference se temelje na DS-01 ili DS-02 atributima. Opaska: U slučaju nemogućnosti upisa poruke pain u sustav PPU-a (npr pogrešan message root, nečitljivost poruke,...) PPU neće moći kreirati poruku pain.002 već klijenta o tome obavijestiti na dogovoreni način. Poruka pain.002 koristi se samo za odbijene (Reject) transakcije, dok se informacija o transakcijama povrata (Returna) klijentu dostavlja kroz camt.poruku.

3 CustomerPaymentStatusReport se sastoji od tri djela: A. Zaglavlje ili vodeći slog (Group Header) Skup podataka koji je obavezan i pojavljuje se jedanput u poruci. Sadrži informacije kao što su Identifikacijska oznaka poruke (MessageIdentification), Datum i vrijeme kreiranja (CreationDateAndTime). B. Informacije i status izvorne poruke (Original Group Information and Status) razina poruke Skup podataka koji je obavezan i pojavljuje se jedanput u poruci. Sadrži informacije kao što su Identifikacijska oznaka izvorne poruke (OriginalMessageIdentification), Naziv izvorne poruke (OriginalMessageNameIdentification), Status grupe/poruke (GroupStatus). Informacije o statusu odbijanja (Reject) na razini poruke daje se samo ako se odbija cijela poruka pain i tada sadrži razlog odbijanja. C. Informacije i status izvorne Informacije o plaćanju (Original Payment Information And Status) razina grupe naloga/pojedinačnog naloga Skup podataka koji je opcionalan i koji se ponavlja. Sadrži podatke iz originalne grupe naloga ili pojedinačnog naloga iz poruke pain Informacija o statusu odbijanja (Reject) daje se na razini grupe naloga ili pojedinačnog naloga ako se odbije cijela grupa naloga ili pojedinačni nalog (nalozi) iz grupe naloga i tada sadrži razlog odbijanja. Sadrži informacije koje se odnose (referencije) na originalnu instrukciju (npr. Izvorni jedinstveni identifikator platitelja- OriginalEndToEndIdentification), informacije koje se odnose na Izvješće o plaćanju (CustomerPaymentStatusReport (npr. Informacija o razlogu statusa - StatusReasonInformation). Skup podataka Informacije i status izvornog plaćanja (OriginalPaymentInformationAndStatus) mogu također sadržavati određene podatke iz originalne instrukcije. Struktura poruke pain

4 Group Header Zaglavlje ili vodeći slog Original Group Information and Status Informacije i status izvorne poruke Original Payment Information and Status Informacije i status grupe naloga/pojedinačnog naloga Original Payment Information and Status Original Payment Information and Status Informacije i status grupe naloga/pojedinačnog naloga Informacije i status grupe naloga/pojedinačnog naloga

5 Bank to Customer Reject Credit Transfer Dataset DS-03 pain Index Pravilo Mult ISO ime elementa Message Element Message root Oznaka poruke labela <CstmrPmtStsRpt> ra zi n a ISO format elementa SEPA Core zahtjevi Upotreba/značenje elementa TheCustomerPaymentStatu sreport message is sent by an instructed agent to the payment initiator. It is used to informed this party about the positive or negative status of an instruction (eighter single, group or file). It is also used to report on a pending instruction. Reject od banke platitelja Reject od CSM-a Return Poruka o statusu naloga koju šalje PPU platitelja inicijatoru plaćanja. Koristi se za informiranje o izvršenom ili odbijenom pojedinčanom nalogu, grupi naloga ili cijeloj poruici. Koristi se i za informiranje o nalozima na čekanju. Sadrži elemente iz CustomerPaymentStatusR eportv03 Index Pravilo Multi GroupHeader Zaglavlje ili vodeći slog ra zi n a ISO format elementa SEPA Core zahtjevi Upotreba/značenje elementa Reject od banke platitelja Reject od CSM-a Return Group Header + Zaglavlje ili vodeći 1 Set of characteristics shared by all individual transactions included in the status report message.

6 slog <GrpHdr> Set podataka koji se odnosi na sve pojedinačne transakcije u poruci o statusu naloga. naslov GroupHeader36 Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message Message Identification ++ Identifikacijska oznaka poruke <MsgId> 2 Max35Text maxlength: 35 Usage: The instructing party has to make sure that 'MessageIdentification' is unique per instructed party for a pre-agreed period. Jedinstveni identifikator poruke u okviru istoga datuma nastanka poruke i pošiljatelja poruke. ++ Creation Date Time Banka dodjeljuje samostalno radi identifikacije R poruke (pain.002) Date and time at which the message was created Datum i vrijeme kreiranja 2 ISODateTime Datum i vrijeme kreiranja poruke pain.002. <CreDtTm>

7 Debtor Agent ++ PPU platitelja <DbtrAgt> 2 (AT-06 BIC code of the Originator Bank) AT-06 BIC Banke platitelja Financial institution servicing an account for the debtor. PPU koji vodi račun platitelja. BIC banke platitelja. +++ Financial Institution Identification BranchAndFinancialInstituti onidentificat +++ Oznaka PPU platitelja 3 Obavezan podatak. <FinInstnId> ++++ BIC ++++ BIC <BIC> 4 BICIdentifier [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} (AT-06 BIC code of the Originator Bank) Index Pravilo Multi 2.0 Original Group Information and Status Informacije i status izvorne poruke + Original Group Information And Status ra zi n a 1 ISO format elementa SEPA Core zahtjevi Upotreba/značenje elementa Original group information concerning the group of transactions, to which the status report message Reject od banke platitelja Reject od CSM-a Return

8 + Informacije i status izvorne poruke <OrgnlGrpInfAndSts> refers to. OriginalGroupInformation2 0 Rule(s): StatusReasonInformationR ule If GroupStatus is present and is different from RJCT or PDNG then StatusReasonInformation/ AdditionalInformation must be absent. Guideline(s): NumberOfTransactionPerS tatusguideline OriginalGroupInformationA ndstatus/numberoftransa ctionsperstatus should only be present if GroupStatus equals 'PART'. Informacije o izvornoj grupi plaćanja na koje se odnosi poruka o statusu naloga za plaćanje. Ako je popunjeno polje GroupStatus (Status grupe / poruke 2.6) i različito od RJCT ili PDNG tada se ne popunjava polje Informacija o razlogu statusa / Dodatne informacije 2.12) naslov

9 ++ Original Message Identification Point to point reference, as assigned by the original instructing party, to unambiguously identify the original message Identifikacijska oznaka izvorne poruke <OrgnlMsgId> 2 Max35Text maxlength: 35 Jedinstveni identifikator poruke dodijeljen od strane izvornog inicijatora plaćanja radi identificiranja plaćanja. ++ Original Message Name Identification podatak iz polja 1.1. iz pain.001 Specifies the original message name identifier to which the message refers Naziv izvorne poruke <OrgnlMsgNmId> ++ Original Number of Transactions ++ Broj naloga izvorne poruke 2 2 Max35Text maxlength: 35 Max15 Numeric Text [0-9]{1,15} Određuje naziv izvorne poruke na koju se ova poruka statusa odnosi. "pain Number of individual transactions contained in the original message. Broj pojedinačnih transakcija u izvornoj poruci. 2.5 <OrgnlNbOfTxs> ++ Original Control Sum ++ Ukupni iznos izvorne poruke 2 DecimalNumb er fractiondigits: 17 totaldigits: 18 podatak iz polja 1.4 iz pain.001 Total of all individual amounts included in the original message, irrespective of currencies. Zbroj pojedinačnih iznosa iz izvorne poruke, bez obzira

10 <OrgnlCtrlSum> na valutu. (AT-R1 Type of R Massage) podatak iz polja 1.5 (ako je popunjen u poruci pain.001) Specifies the status of a group of transactions [0..n] ++ Group Status ++ Status poruke <GrpSts> ++ Status Reason Information ++Informacija o razlogu statusa <StsRsnInf> 2 Code 2 Usage Rule: ''Group Status'', ''Payment Information Status'' or ''Transaction Status'' must be present with the code ''RJCT'' Pravilo: ''Group Status''(Status grupe poruke 2.6), ''Payment Information Status (Status informacije o plaćanj -3.4) ili ''Transaction Status'' (Status transakcije 3.16) moraju biti popunjeni s kodom ''RJCT'' Usage Rule: Status Reason Information must be present in Original Group Information And Status, Original Payment Information and Status or Specificira status poruke. TransactionGroupStatus3C ode Pravilo upotrebe: popunjava se kod RJCT RJCT payment inititaiton or individual transaction has been rejected. Upotrebaljva se samo ako se odbija cijela poruka. Cijela poruka pain.001 se odbija ako je u pain.001 Zaglavlje (Group Header) suštinski neispravno odnosno ako se javi greška na jednom od opisanih polja u pain.001 (MsgId nije jedinstven, kontrolni zbroj ne odgovara zbroju svih transakcija.) Set of elements used to provide detailed information on the status reason. StatusReasonInformation8 Rule(s): StatusReasonRule If Reason/Code is equal to NARR, then AddititionalInformation must Koristi se samo kada se odbija cijela poruka pain001 Ne navodimo pojedinačne transakcije Ne koristi se Ne koristi se

11 Originator +++ Pošiljatelj statusa <Orgtr> 3 Transaction Information and Status. Pravilo: ''Status Reason Information'' mora biti popunjeno u ''Original Group Information And Status'' (2.0), ''Original Payment Information and Status'' (3.0) ili ''Transaction Information and Status'' (3.12) (AT-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 a CSM when it has no BIC. Usage Rule: Name is limited to 70 characters in length. be present. Set podataka koji osiguravaju detaljne informacije o razlogu statusa. Ako je Reason/Code NARR, tada treba biti popunjeno i polje Additional Information (Dodatne informacije 2.12) Naslov Party that issues the status. Strana koja dodijeljuje status. PartyIdentification32 Popunajva se BIC banke platitelja. Ne koristi se Ne koristi se (AT-R2 Identifikacija strane koja je odbacuje plaćanje) BIC banke ili CSM pošiljatelja, ili ''Name'' ako CSM

12 ++++ Identification nema BIC. ''Name'' je ograničen na 70 mjesta. Ne koristi se Ne koristi se ++++ Identifikacija <Id> Organisation Identification Ne koristi se Ne koristi se +++++Oznaka organizacije 5 <OrgId > BICOrBEI BIC ili BEI <BICOrBEI> +++ Reason +++ Razlog statusa <Rsn> 6 3 AnyBICIdentifi er [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} (AT-R3 Reason Code for Non- Acceptance) AT-R3 Razlog u obliku koda za neprihvaćanje Specifies the reason for the status report. StatusReason6Choice Specificira razlog za izvješće o statusu iz AT-R3 Naslov Ne koristi se Ne koristi se Ne koristi se Ne koristi se Code ++++ Kod 4 Code maxlength: 4 See Message Element Specifications below. Reason for the status, as published in an external reason code list. ExternalStatusReason1Cod Koristi se samo za greške iz Zaglavlja iz poruke pain.001. Ako banka popuni Ne koristi se Ne koristi se

13 <Cd> Razlog statusa AT-R3. Kod NARR obavezno se popunjava polje 2.12 Further details on the status reason [0..n] +++ Additional Information +++ Dodatne informacije <AddtlInf> 3 Max105Text maxlength: 105 Usage: Additional information can be used for several purposes such as the reporting of repaired information. Dodatne informacije o razlogu statusa. Index Pravilo Multi Original Payment Information and Status Informacije i status izvorne Informacije o plaćanju + Original Payment Information And Status ra zi n a ISO format elementa SEPA Core zahtjevi R6 Obavezno se popunjava ako je u polju 2.10 upisan kod NARR. Upotreba/značenje elementa Information concerning the original payment information, to which the status report message refers. Reject od banke platitelja Reject od CSM-a Return 3.0 [0..n] + Informacije i status izvorne Informacije o plaćanju 1 OriginalPaymentInformatio n1 <OrgnlPmtInfAndSts> Informacije o izvornom plaćanju na koje se odnosi izvješće o statusu.

14 naslov Rule(s): PaymentInformationStatus AcceptedRule If OriginalPaymentInformatio nandstatus/paymentinform ationstatus is present and is equal to ACTC, ACCP, ACSP, ACSC or ACWC, then TransactionInformationAnd Status/TransactionStatus must be different from RJCT. Ako je polje PaymentInformationStatus (Status informacije o plaćanju 3.4) popunjeno s ACTC, ACCP, ACSP, ACSC ili ACWC, tada polje TransactionStatus (Status transakcije 3.16) ne smije biti RJCT. Ne odnosi se na RJCT. PaymentInformationStatus PendingRule If OriginalPaymentInformatio nandstatus/paymentinform ationstatus is present and is equal to PDNG, then TransactionInformationAnd Status/TransactionStatus must be different from RJCT. Ako je polje

15 PaymentInformationStatus (Status informacije o plaćanju 3.4.) popunjeno s PDNG, tada polje TransactionStatus (Status transakcije 3.16) ne smije biti RJCT. PaymentInformationStatus ReceivedRule If OriginalPaymentInformatio nandstatus/paymentinform ationstatus is present and is equal to RCVD, then TransactionInformationAnd Status/TransactionStatus is not allowed. Ako je polje PaymentInformationStatus (Status informacije o plaćanju 3.4.) popunjeno s RVCD, tada polje TransactionStatus (Status transakcije 3.16) ne smije biti popunjeno. Neće se koristiti RCVD PaymentInformationStatus RejectedRule If OriginalPaymentInformatio nandstatus/paymentinform ationstatus is present and is equal to RJCT, then TransactionInformationAnd Status/TransactionStatus, if present, must be equal to RJCT.

16 ++ Original Payment Information Identification Max35Text Ako je polje PaymentInformationStatus (Status informacije o plaćanju 3.4.) popunjeno s RJCT, tada polje TransactionStatus (Status transakcije 3.16) mora biti popunjeno s RJCT. Unique identification, as assigned by the original sending party, to unambiguously identify the original payment information group Izvorna idenifikacijska oznaka plaćanja <OrgnlPmtInfId> ++ Original Number of Transactions ++ Broj transakcija izvorne grupe n aloga <OrgnlNbOfTxs> ++ Original Control Sum ++ Izvorni kontrolni zbroj iznosa <OrgnlCtrlSum> maxlength: 35 Max15Numeri ctext [0-9]{1,15} DecimalNumb er fractiondigits: 17 totaldigits: 18 Jedinstvena oznaka dodijeljena od strane izvornog pošiljatelja, radi jednoznačnog identificiranja grupe naloga. Podatak iz polja 2.1 iz pain.001 Number of individual transactions contained in the original payment information group. Broj pojedinačnih transakcija iz izvorne grupe naloga. podatak iz polja 2.4 iz pain.001 Total of all individual amounts included in the original payment information group, irrespective of currencies. Zbroj pojedinačnih iznosa koje sadrži izvorna grupa Koristi se samo kada odbijamo cijelu grupu unutar jedne poruke i u tom slučaju ne navodimo pojedinačne transakcije tj navode se podaci do 3.13 polja) Koristi se samo kada odbijamo cijelu grupu unutar jedne poruke i u tom slučaju ne navodimo pojedinačne Ne koristi se. Ne koristi se. Ne koristi se. Ne koristi se.

17 [0..n] ++ Payment Information Status ++ Status informacije o plaćanju <PmtInfSts> ++ Status Reason Information ++ Razlog statusa <StsRsnInf> 2 2 Code maxlength: 4 (AT-R1 Type of R- message) Usage Rule: Group Status, Payment Information Status or Transaction Status must be present with the code RJCT. AT-R1 Vrsta R poruke Group Status (Status grupe / poruke 2.6), Payment Information Status (Status informacije o plaćanju - 3.4) ili Transaction Status (Status transakcije 3.16) mora biti popunjen s RJCT. Usage Rule: Status Reason Information must be present in Original Group Information And Status, Original Payment Information Status or Transaction Information and Status. naloga bez obzira na valutu plaćanja. podatak iz polja 2.5 iz pain.001 Specifies the status of the payment information group. Specificira status grupe naloga. TransactionGroupStatus3C ode RJCT payment inititaiton or individual transaction has been rejected. Set of elements used to provide detailed information on the status reason. StatusReasonInformation8 Rule(s): StatusReasonRule If Reason/Code is equal to NARR, then AddititionalInformation must be present. Set podataka koji transakcije - (tj navode se podaci do 3.13 polja) Koristi se samo kada odbijamo cijelu grupu unutar jedne poruke i u tom slučaju ne navodimo pojedinačne transakcije - (tj navode se podaci do 3.13 polja) Ne koristi se. Ne koristi se Ne koristi se. Ne koristi se

18 Originator +++ Pošiljatelj <Orgtr> 3 Polje Status Reason Information (Razlog statusa 3.5) mora biti popunjeno u Original Group Information And Status (Informacije i status izvorne poruke/grupe plaćanja - 2.0) ili Transaction Information and Status (Informacija i status transakcije ) (AT-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 a CSM when it has no BIC. Usage Rule: Name is limited to 70 characters in length. AT-R2 Identifikacija strane koja je inicirala odbacivanje. osiguravaju detaljnu informaciju o razlogu statusa. Ako je Reason/Code NARR, tada treba biti popunjeno polje AddititionalInformation (Dodatne informacije ) Naslov Party that issues the status. Strana koja dodjeljuje status PartyIdentification32 BIC banke platitelja. Ne koristi se Ne koristi se. BIC banke ili CSM pošiljatelja ili ''Name'' (Naziv) ako

19 CSM nema BIC Identification ''Name'' (Naziv) je ograničen na 70 mjesta. Ne koristi se Ne koristi se ++++ Identifikacija 4 <Id> Organisation Identification Ne koristi se Ne koristi se +++++Oznaka organizacije <OrgId > BICOrBEI BIC ili BEI <BICOrBEI> +++ Reason +++ Razlog statusa <Rsn> ++++ Code ++++Kod <Cd> AnyBICIdentifi er [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} Code maxlength: 4 (AT-R3 Reason Code for Non- Acceptance) AT-R3 Razlog u obliku koda za neprihvaćanje See Message Element Specifications below. Specifies the reason for the status. StatusReason6Choice Specificira razlog za izvješće o statusu. naslov Reason for the status, as published in an external reason code list. ExternalStatusReason1Cod Razlog statusa sukladno listi external reason code. Ne koristi se Ne koristi se

20 3.10 [0..n] +++ Additional Information +++ Dodatne informacije <AddtlInf> 3 Max105Text maxlength: 105 Further details on the status reason. Usage: Additional information can be used for several purposes such as the reporting of repaired information. Dodatne informacije o razlogu statusa (3.15) [0..n] ++ Transaction Information and Status ++ Informacija i status naloga <TxInfAndSts> 2 Obavezno se popunjava ako je u polju 3.8 upisan kod NARR. Set of elements used to provide information on the original transactions to which the status report message refers. PaymentTransactionInform ation25 Set podataka koje osiguravaju informaciju o izvornom nalogu na koju se odnosi izvještaj o statusu (3.16) +++ Status Identification +++ Identifikator statusa <StsId> 3 Max35Text maxlength: 35 (AT-R5 Specific reference of the bank that initiated the reject) (AT-R5 jedinstvena referenca banke koja je inicirala odbacivanje) naslov Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the reported status. Usage: The instructing party is the party sending the status message and not the party that sent the original instruction that is being reported on. PPU platitelja popunajva identifikator stausa za nalog koji se odbija - ovo samostalno određuje 3.1 (StsId) iz pacs (RtrId)) iz pacs.004

21 Jedinstvena oznaka, koju je dodijelio inicijator poruke za primatelja, radi jednoznačnog identificiranja statusa (3.17) +++ Original Instruction Identification +++ Izvorna identifikacijska oznaka naloga referencija <OrgnlInstrId> 3 Max35Text maxlength: 35 Inicijator poruke (Instructing party) je strana koja šalje poruku o statusu (PPU), a ne strana (KPU) koja je poslala izvornu poruku/plaćanje o kojoj se šalje izvještaj. Ako odbijamo cijelu poruku pain.001 ili cijelu grupu naloga iz poruke pain.001 ne popunjava se polje 3.13 (jer u tom slučaju sustav nije ni došao do same transakcije) Unique identification, as assigned by the original instructing party for the original instructed party, to unambiguously identify the original instruction. Jedinstveni identifikator (referencija) kojeg dodjeljuje inicijator PPU platitelja radi identificiranja naloga (3.18) +++ Original End-to- End Identification +++ Izvorni jedinstveni identifikator platitelja 3 Max35Text maxlength: 35 (AT-41 Originator s reference of the credit transfer transaction) podatak iz polja 2.65 iz pain.001. ako je popunjeno Unique identification, as assigned by the original initiating party, to unambiguously identify the original transaction.

22 <OrgnlEndToEndId> Jedinstveni identifikator kojeg je odredio platitelj radi praćenja transakcije (3.19) 3.17 (3.20) [0..n] +++ Transaction Status +++ Status naloga <TxSts> +++ Status Reason Information +++ Informacija o razlogu statusa <StsRsnInf> 3 3 Code maxlength: 4 (AT-R1 Type of R- message) Usage Rule: Group Status, Payment Information Status or Transaction Status must be present with the code RJCT. (AT-R1 Vrsta R poruke) Pravilo: Ako je kod ''RJCT'', moraju biti popunjenja polja ''Group status''(2.6), Payment Information Status (3.4) ili Transaction Status (3.16) Usage Rule: Status Reason Information must be present in Original Group Information And Status, Original Payment Information Status or Transaction Information and podatak iz polja 2.66 iz poruke pain Specifies the status of a transaction, in a coded form. TransactionIndividualStatus 3Code Specificira status transakcije u obliku koda. RJCT RJCT payment inititaiton or individual transaction has been rejected. Set of elements used to provide detailed information on the status reason. StatusReasonInformation8 Set podataka koji osiguravaju detaljnu informaciju o razlogu statusa.

23 3.18 (3.21) ++++ Originator ++++ Pošiljatelj <Orgtr> 4 Status. Pravilo: Polje Status Reason Information mora biti popunjeno u Original Group Information And Status,(2.0), Original Payment Information Status (3.0) ili Transaction Information and Status (3.12). (AT-R2 Identification of the Type of Party that initiated the reject) Usage Rule: Name is limited to 70 characters in length. Usage Rule: Limited to BIC to identify the bank or CSM originating the status or Name to indicate a CSM when it has no BIC. Naslov Party that issues the status. PartyIdentification32 Strana koja određuje status. BIC banke platitelja naziv CSM ili BIC CSM-a. BIC PPU primatelja (AT-R2 Identifikator strane koja je inicirala odbacivanje) Name 5 max140ext ''Name'' je ograničen na 70 mjesta. Usage Rule: Name is limited to Name by which a party is known and which is usually Ne koristi se. naziv CSM ako Ne koristi se.

24 +++++ Naziv pošiljatelja <Nm> Identification Identifikacija <Id> Organisation Identification Oznaka organizacije 5 6 maxlength: characters in length. used to identified that party Naziv pošiljatelja. Unique and unambiguous identification of a party. Jedinstvena i neoporeciva identifikacija pošiljatelja. Unique and unamibiguous way to identifiey an organisation CSM nema BIC (NKS ) 3.19 (3.22) <OrgId > BICOrBEI BIC ili BEI <BICOrBEI> ++++ Reason ++++ Razlog statusa <Rsn> 7 4 AnyBICIdentifi er [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} AT-R3 Reason Code for Non- Acceptance Specifies the reason for the status report. StatusReason6Choice Specificira razlog za izvješće o statusu. BIC banke platitelja BIC CSM, ako CSM ima BIC. BIC PPU primatelja 3.20 (3.23) 3.22 (3.25) [0..n] Code Kod <Cd> ++++ Additional Information 4 5 Code maxlength: 4 Max105Text maxlength: See Message Element Specifications below. naslov Reason for the status, as published in an external reason code list. ExternalStatusReason1Cod Razlog statusa sukladno listi external reason code. Further details on the status reason. Usage: Additional Popunjava banka platitelja Prenosi se kod popunjen od CSM-a Prenosi se ako je nešto popunjeno od CSM-a Prenosi se kod popunjen od banke primatelja Prenosi se ako je nešto popunjeno od

25 ++++ Dodatne informacije <AddtIInf> 105 information can be used for several purpose such as the reporting of repaired information. banke primatelja Koristi se za dodatno pojašnjenje razloga odbijanja naloga Koristi svaka banka prema svojim internim pravilima (3.32) +++ Original Transaction Reference +++ Referenca izvorne transakcije <OrgnlTxRef> 3 (An exact copy of all attributes of the received DS-02 or DS-01 which is being rejected) Kopija podataka zaprimljenih u DS- 02 ili DS-01 koji se odbacuju. 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. Podaci pod Original Transaction Reference Obavezno se popunjava ako je u polju 3.20 upisan kod NARR. Set of key elements used to identify the original transaction that is being referred to. OriginalTransactionReferen ce13 Set podatka koji se koriste za identifikaciju izvorog naloga iz poruke pain.001 na koju se odnosi ova poruka naslov

26 3.29 (3.34) ++++ Amount ++++ Iznos <Amt> Instructed Amount Iznos <InstdAmt> 4 5 AmountandCu rrancy ActiveOrHistori ccurrencyand Amount ActiveOrHistori ccurrencyand Amount fractiondigits: 5 mininclusive: 0 totaldigits: 18 ActiveOrHistori ccurrencycod (Referenca izvorne transakcije ) mora biti popunjena s istim podacima kao i izvorna poruka/plaćanje/tra nsakcije, a kako je određeno slijedećim elementima. AT-04 Amount of the credit transfer in Euro) AT-04 Iznos kreditnog transfera u eurima (AT-04 Amount of the Credit Transfer in Euro) Usage Rule: Only EUR is allowed. Usage Rule: Amount must be 0.01 or more and or less. Format Rule: The fractional part has a maximum of two digits. Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. AmountType3Choice Iznos sredstava kojeg platitelj prenosi primatelju, prije oduzimanja naknade, izražen u valuti koju je odredio platitelj. Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. This data type must be used with the following XML Attribute: Currency (Ccy) which is typed by ActiveOrHistoricCurrencyC ode The number of fractional digits (or minor unit of currency) must comply with podatak iz 2.76 iz pain.001 podatak iz 2.77 iz pain.001 podatak iz 3.19 iz pacs.002 podatak iz 3.10 iz pacs.004

27 e [A-Z]{3,3} ISO Note: The decimal separator is a dot. The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged. CurrencyCode Obavezan podatak. Iznos kojeg platitelj duguje primatelju, a prije odbijanja troškova, iskazano u valuti određenoj od strane inicijatora plaćanja. Ovaj podatak se koristi s XML atributom Currency (Ccy) koji je označen u ActiveOrHistoricCurrencyC ode Napomena: kao decimalni separator koristi se točka. The Currency Code treba biti registriran. Važeći ili već povijesni kodovi se registriraju po ISO 4217, sadrže tri slova i ne smiju biti opozvani na dan kada

28 se razmjenjuje poruka koja sadrži određenu valutu. Obavezno za popunjavanje, prema pravilima SEPE SEPA nalog: Iznos mora bti u rasponu od 0.01 do Dozvoljeno je najviše 11 znamenki cijeli broj 9 znamenki + 2 znamenke decimale, ne računajući decimalnu točku (3.41) 3.35 (3.55) ++++ Requested Execution Date ++++ Traženi datum izvršenja <ReqdExctnDt> ++++ Payment Type Information 4 4 ISODate AT-07 Requested execution date of the instruction) AT-07 traženi datum izvršenja plaćanja AT-40 Identification code of the HRK nalog i non SEPA nalog: Iznos mora bti u rasponu od 0.01 do Dozvoljeno je najviše 14 znamenki cijeli broj 12 znamenki + 2 znamenke decimale, ne računajući decimalnu točku Date at which the initiating party requests the clearing agent to process the payment. Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date when the cheque must be generated by the bank. Datum na koji platitelj traži da se sredstva proslijede primatelju plaćanja. Na ovaj datum se tereti račun platitelja. Set of elements used to further specify the type of podatak iz 2.15 iz pain.001 podatak iz 2.6 ili 2.67 iz pain.001 Ne prenosi se podatak iz 2.6 ili 2.67 iz pain.001 Ne prenosi se podatak iz 2.6 ili 2.67 iz pain.001

29 ++++ Informacije o vrsti plaćanja <PmtTpInf> Service Level Razina usluge 5 Scheme (AT-40 Identifikacijski kod) AT-45 Category purpose of the Credit Transfer (AT-45 Kategorija namjene kreditnog transfera) transaction. Podaci koji detaljnije opisuju vrstu transakcije. PaymentTypeInformation22 Agreement under which or rules under which the transaction should be processed. ako je popunjeno. ako je popunjeno. ako je popunjeno. <SvcLvl> Code Kod <Cd> 6 maxlength: 4 AT-40 Identification code of the Scheme) Dogovor ili pravila po kojima će se obraditi transakcija. Specifies a pre-agreed service or level of service between the parties, as published in an external service level code list. 2.9 ili 2.70 iz poruke pain ili 2.70 iz poruke pain ili 2.70 iz poruke pain Category Purpose Kategorija namjene <CtgyPurp> 5 (AT-45 Category purpose of the Credit Transfer) U Specifies the high level purpose of the instruction based on a set of predefined categories. Usage: This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain. kod kategorije namjene (AT-45) iz polja 2.14 ili 2.75 iz poruke pain.001 kod kategorije namjene (AT-45) iz polja 2.14 ili 2.75 iz poruke pain.001 kod kategorije namjene (AT-45) iz polja 2.14 ili 2.75 iz poruke pain.001 Označava svrhu plaćanja koja se temelji na unaprijed definiranim kategorijama, a prema šifarniku

30 CategoryPurpose1Choice Code Kod <Cd> 6 Code ExternalCategoryPurpose1 Code 3.36 (3.68) ++++ Payment Method ++++ Metoda plaćanja <PmtMtd> 4 Code Specifies the means of payment that will be used to move the amount of money. PaymentMethod4Code Označava način plaćanja koji će se koristi za prijenos sredstava iz pain iz pain iz pain (3.88) ++++ Remittance Information ++++ Detalji plaćanja <RmtInf> +++++Unstructured Nestrukturirani <Ustrd> 4 5 Max140Text maxlength: 140 (AT-05 Remittance information) AT-05 IDetalji plaćanja) Usage rule: Only one occurrence of 'Unstructured' is allowed. Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system. RemittanceInformation5 Podaci koji omogućavaju povezivanje transakacije sa svrhom plaćanja, kao što su fakture dobavljača. Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commerical invoices in an accounts' receivable system, in an ustructured form. Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001

31 Pravilo upotrebe: Nestrukturirani detalji plaćanja mogu sadržavati strukturirane detalje plaćanja ako su ista ugovorena između platitelja i primatelja Structured +++++Strukturirana 5 Format Rule: 'Structure' can be used, provided the tags and the data within the 'Structured' element do not exceed 140 characters in length. Može se pojaviti samo jedanput. Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commerical invoices in an accounts' receivable system, in a structured form. Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 <Strd> Usage Rule: Only one occurrence of 'Structured' is allowed. Pravilo upotrebe: Strukturirani detalji plaćanja popunjavaju se do max 140 znakova Creditor Reference Information Referenca koju određuje primatelja plaćanja <CdtrRefInf> 6 Usage Rule: When present, the Debtor Bank is not obliged to validate the reference information. Usage Rule: When used both Creditor Reference Type and Creditor Reference must be present. StructuredRemittanceInfor mation7 Reference information provided by the creditor to allow the identification of the underlying documents. Informacija/referenca koju je kreirao primatelj radi identifikacije plaćanja. Sastoji se od elemenata iz CreditorReferenceInformati on2 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001

32 Type Vrsta reference 7 Specified the type of creditor reference. CreditorReferenceType2 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 <Tp> Code or Proprietary Kod ili vlastita oznaka 8 Coded or proprietary format creditor reference type. CreditorReferenceType1Ch oice Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 <CdOrPrtry> Code Kod 9 Code Usage Rule: Only SCOR is allowed. Type of creditor reference, in a coded form. DocumentType3Code Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 <Cd> Issuer Izdavatelj <Issr> 8 Max35Text maxlength: 35 Pravilo upotrebe: Upotrebljava se samo SCOR. Entity that assigns the credit reference type. Strana koja dodijeljuje vrstu reference primatelja. Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain Reference Referentna oznaka <Ref> 7 Max35Text maxlength: 35 Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. Usage: If available, the initiating party should provide this reference in the structured remittance information, to enable Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001 Popunjavaju se podaci iz polja iz pain.001

33 reconciliation by the creditor upaon receipt of the amount of money (3.120) [0..3] Additional Remittance Information Dodatni detalji plaćanja <AddtlRmtInf> ++++ Ultimate Debtor ++++ Stvarni dužnik <UltmtDbtr> Name Naziv stvarnog dužnika Max140Text maxlength: 140 max140text maxlength: 140 (AT-08 Name of the Originator Reference Party) (AT-09 Identification code of the Originator Reference Party) Text AT-08 Name of the Originator Reference Party) Usage Rule: If the business context requires the use of a creditor reference or a payment remit identification, and only one identifier can be passed through the end-to-end chain, the creditor's reference or payment remittance identification should be quoted in the end-to-end transaction identification. Additional information, in free text form, to complement the structured remittance information. Detalji plaćanja u tekstualnoj formi koji dopunjuju strukturirane detalje plaćanja. na max 140 mjesta, jedno ponavljanje. Ultimate party that owes an amount of money to the (ultimate) creditor. PartyIdentification32 Stvarni dužnik koji duguje određeni iznos novca (krajnjem) korisniku. (The name of a person in relation to whom an Originator makes a payment The Originator Reference Popunjavaju se podaci iz polja iz pain ili 2.82 iz pain.001 ako je popunjeno ili 2.83 iz pain.001 ako je popunjeno Popunjavaju se podaci iz polja iz pain ili 2.82 iz pain.001 ako je popunjeno ili 2.83 iz pain.001 ako je popunjeno Popunjavaju se podaci iz polja iz pain ili 2.82 iz pain.001 ako je popunjeno ili 2.83 iz pain.001 ako je popunjeno

34 <Nm> Identification Identifikacija 5 Name is limited to 70 characters in length. (AT-09 Identification code of the Originator Reference Party) Party is a person on behalf of or in connection with whom the Originator purports to make a payment Reference in any payment instruction to an Originator Reference Party does not imply that such party is an Originator or otherwise a payer, or is contractually obliged or entitled in connection with any payment obligation. The identification code of the Originator Reference Party. A code supplied by the Originator and to be delivered unaltered to the Beneficiary ili 2.85 iz pain.001 ako je popunjeno 2.55 ili 2.85 iz pain.001 ako je popunjeno 2.55 ili 2.85 iz pain.001 ako je popunjeno <Id> Unique and umambiguous identification of a party. {Or {Or Organisation Identification Oznaka organizacije <OrgId> BICOrBEI BIC ili BEI <BICOrBEI> 6 7 AnyBICIdentifi er [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} Sastoji se od elemenata iz Party6Choice Unique and unamibiguous way to identifiey an organisation. Pravilo upotrebe: Upisuje se ili BIC/BEi ili Other ili 2.86 iz pain.001 ako je popunjeno 2.56 ili 2.86 iz pain.001 ako je popunjeno 2.56 ili 2.86 iz pain.001 ako je popunjeno

35 Or} Other Ostalo <Othr> Identification 7 Max35Text Identifikacija 8 maxlength: 35 <Id> Scheme Name Naziv Sheme 8 OrganisationIdentificationS chemename1choice elements {Or Or} <SchmeNm> Code Kod <Cd> Proprietary Vlastita oznaka 9 9 Code maxlength: 4 minlength:1 Max35Text maxlength: 35 ExternalOrganisationIdentifi cation1code <Prtry> Issuer Max35Text Izdavatelj <Issr> 8 maxlength: 35 minlength:1. Or} Private Identification 6 Unique and unamibiguous identification of a person eg. passport ili 2.87 iz 2.57 ili 2.87 iz 2.57 ili 2.87 iz

36 Privatna identifikacija <PrvtId> Date and Place of Birth Pravilo upotrebe: Upisuje se ili datum i mjesto rođenja ili Other. pain.001 ako je popunjeno pain.001 ako je popunjeno pain.001 ako je popunjeno {Or Datum i mjesto rođenja 7 <DtAndPlcOfBirth> Birth Date ISODate Datum rođenja 8 <BirthDt> ProvinceOf Birth Županija rođenja 8 Max35Text maxlength: 35 <PrvcOfBirth> City of Birth Grad rođenja 8 Max35Text maxlength: 35 <CityOfBirth> Country of Birth Država 8 Code [A-Z]{2,2} CountryCode a iznimno se koristi i dvoslovni kod XK za Kosovo

37 rođenja <CtryOfBirth> Other Or} Ostalo 7 <Othr> Identification Identifikacija 8 Max35Text maxlength: 35 <Id> Scheme Name Naziv Sheme 8 <SchmeNm> Code Code {Or Kod <Cd> 9 maxlength: 4 Or} Proprietary Vlastita oznaka 9 Max35Text maxlength: 35

38 <Prtry> Issuer Max35Text Ne koristi se Izdavatelj <Issr> 8 maxlength: 35. (AT-02 Name of the Originator) AT-02 Naziv platitelja Party that owes an amount of money to the (ultimate) creditor. PartyIdentification32 Popunjavaju se podaci z polja 2.17 iz pain.001 Popunjavaju se podaci z polja 2.17 iz pain.001 Popunjavaju se podaci z polja 2.17 iz pain (3.121) ++++ Debtor ++++ Platitelj <Dbtr> 4 (AT-03 Address of the Originator) AT-03 Adresa platitelja (AT-10 Originator identification code) Name Naziv platitelja <Nm> Postal Address Adresa 5 5 Text AT-10 Identifikacijska oznaka platitelja Mandatory (AT-02 Name of the Originator) Usage Rule: Name is limited to 70 characters in length. AT-03 Address of the Originator) Name by which a party is known and which is usually used to identified that party Naziv platitelja. Navedeni podatak je ograničen na 70 znakova. Information that locates and identifies a specific address, as defined by postal services 2.18 iz pain iz pain iz pain iz pain iz pain iz pain.001

39 platitelja Adresa platitelja. <PstlAdr> Country Država 6 CountryCode [A-Z]{2,2} Sastaoji se od elemenata iz PostalAddress6 Dvoslovna oznaka države prema ISO 3166 standardu a iznimno se koristi i dvoslovni kod XK za Kosovo iz pain iz pain iz pain.001 <Ctry> Address Line Max70Text maxlength: 70 Usage Rule: Only two occurrences are allowed Information that locates and identifies a specific address, as defined by postal services, presented in free format text iz pain iz pain iz pain.001 [0..2] Adresna linija <AdrLine> 6 Dozvoljene su samo popunjene dvije adresne linije, u svakom retku po 70 znakova Identification Identifikacija 5 AT-10 Originator Identification Code U 1. redak - adresa i kućni broj, a u 2. redak naziv mjesta/grada. A code supplied by the Originator and to be delivered unaltered to the Beneficiary 2.30 iz pain iz pain iz pain.001 <Id> Sastoji se od elemenata iz Party6Choice {Or Organisation Identification Oznaka organizacije 6 Usage Rule: Either BIC or BEI or one occurrence of Other is allowed Unique and unamibiguous way to identifiey an organisation. Pravilo upotrebe: Upisuje se ili BIC/BEI ili Other 2.31 iz pain iz pain iz pain.001

40 <OrgId> {Or Or} BICOrBEI BIC ili BEI <BICOrBEI> Other Ostalo 7 7 AnyBICIdentifi er [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} GenericOrganisationIdentifi cation1 element(s) <Othr> Identification Identifikacija 8 Max35Text maxlength: 35 <Id> Scheme Name Naziv Sheme 8 OrganisationIdentificationS chemename1choice elements <SchmeNm> {Or Code Kod <Cd> 9 Code maxlength: 4 ExternalOrganisationIdentifi cation1code Or} Proprietary Vlastita 9 Max35Text maxlength: 35

41 oznaka <Prtry> Issuer Max35Text Izdavatelj <Issr> 8 maxlength: 35 Or} Private Identification Privatna identifikacija <PrvtId> Date and Place of Birth 6 Usage Rule: Either Date and Place of Birth or one occurrence of Other is allowed. Unique and unamibiguous identification of a person eg. passport. Pravilo upotrebe: Upisuje se ili datum i mjesto rođenja ili Other. PersonIdentification iz pain iz pain iz pain.001 {Or Datum i mjesto rođenja 7 <DtAndPlcOfBirth> Birth Date ISODate Datum rođenja 8 <BirthDt> ProvinceOf Birth Županija rođenja 8 Max35Text maxlength: 35

42 <PrvcOfBirth> City of Birth Grad rođenja 8 Max35Text maxlength: 35 <CityOfBirth> Country of Birth Država rođenja <CtryOfBirth> 8 Code [A-Z]{2,2} CountryCode Dvoslovna oznaka države prema ISO 3166 standardu a iznimno se koristi i dvoslovni kod XK za Kosovo. Or} Other Ostalo 7 GenericPersonIdentification 1 element(s) <Othr> Identification Identifikacija <Id> 8 Max35Text maxlength: Scheme Name Naziv Sheme 8 PersonIdentificationSchem ename1choice

43 <SchmeNm> Code Code {Or Kod <Cd> 9 maxlength: 4 ExternalPersonIdentificatio n1 Or} Proprietary Vlastita oznaka 9 Max35Text maxlength: 35 <Prtry> Issuer Max35Text Izdavatelj <Issr> 8 maxlength: (3.122) ++++ Debtor Account ++++ Račun platitelja <DbtrAcct> Identification Identifikacija 4 5 (AT-01 IBAN of the Originator) AT-01 IBAN platitelja Usage Rule: Only IBAN is allowed. Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction. CashAccount16 Sastoji se od elemenata iz CashAccount iz pain iz pain iz pain iz pain iz pain iz pain.001 <Id> IBAN IBANIdentifier IBAN <IBAN> 6 [A-Z]{2,2}[0-9]{2,2}[0-9]{1,19}

44 +++++ Currency Valuta transakcijskog računa <Ccy> 5 ISO Code ActiveOrHistori ccurrencycod e [A-Z]{3,3} Identification of the currency in which the account is held. The Currency Code must be registered, or have already been registered. Valid active or historic currency codes are registered with the ISO 4217 Maintenance Agency, consist of three (3) contiguous letters, and may be or not be withdrawn on the day the message containing the Currency is exchanged iz pain iz pain iz pain (3.123) ++++ Debtor Agent ++++ PPP platitelja <DbtrAgt> Financial Institution Identification Oznaka PPU platitelja 4 5 AT-06 BIC code of the Originator Bank (if presented in DS- 01) AT-06 BIC kod banke platitelja (ako je popunjen u pain.001) Usage Rule: Either BIC or Other/Identification must be used. CurrencyCode Financial institution servicing an account for the debtor. PPU koja vodi račun platitelja BranchAndFinancialInstituti onidentificat 2.40 iz pain iz pain iz pain iz pain iz pain iz pain.001 <FinInstnId> BIC BIC 6 (AT-06 BIC code of the Originator Bank) 2.42 iz pain iz pain iz pain.001

45 <BIC> 3.44 (3.125) ++++ Creditor Agent ++++ PPP primatelja plaćanja <CdtrAgt> Financial Institution Identification 4 (AT-23 BIC code of the Beneficiary Bank if presented in DS-01) AT-23 BIC PPU primatelja (ako je popunjen u pain.001) Financial institution servicing an account for the creditor. PPU koji vodi račun primatelja BranchAndFinancialInstituti onidentificat Podatak iz polja 2.96 iz pain.001. Podatak iz polja 2.96 iz pain.001. Podatak iz polja 2.96 iz pain Oznaka PPU primatelja 5 <FinInstnId> BIC BICIdentifier BIC <BIC> Clearing System Member Identification 6 [A-Z]{6,6}[A- Z2-9][A-NP- Z0-9]([A-Z0-9]{3,3}){0,1} Identifikacijska oznaka sudionika klirinškog sustava 6 <ClrSysMmbId>

46 Member Identification Identifikacijska oznaka sudionika 7 Max35Text maxlength: 35 <MmbId> Name max140text Naziv PPU primatelja <Nm> 6 maxlength: Postal Address Adresa PPU primatelja 6 <PstlAdr> Country Država 7 countrycode [A-Z]{2,2} Iznimno se koristi i dvoslovni kod XK za Kosovo <Ctry> [0..2] Address Line Adresna linija 7 Max70Text maxlength: 70 Minlength: 1 <AdrLine> Creditor 4 (AT-21 Name of the Party to which an amount of money is due Podaci iz polja 2.98 iz pain 001. Podaci iz polja Podaci iz polja

47 (3.127) ++++ Primatelj plaćanja <Cdtr> Name Naziv primatelja plaćanja <Nm> 5 max140text maxlength: 140 Beneficiary) AT-21 Naziv primatelja plaćanja (AT-22 Address of the Beneficiary AT-22 Adresa primatelja plaćanja (AT-24 Beneficiary identification code) AT-24 Identifikacijska oznaka primatelja plaćanja Mandatory AT-21 Name of the Beneficiary) AT-21 Naziv primatelja plaćanja Primatelj sredstava. PartyIdentification32 naslov Name by which a party is known and which is usually used to identified that party Naziv platitelja. Navedeni podatak je ograničen na 70 znakova. Podaci iz polja 2.99 iz pain iz pain iz pain 001. Podaci iz polja 2.99 iz pain 001 Podaci iz polja 2.99 iz pain Postal Address Adresa primatelja 5 AT-22 Address of the Beneficiary AT-22 Adresa primatelja plaćanja Information that locates and identifies a specific address as defined by postal services Adresa platitelja. Podaci iz polja iz pain 001 Podaci iz polja iz pain 001 Podaci iz polja iz pain 001 <PstlAdr> Sastaoji se od elemenata iz PostalAddress Country Država <Ctry> 6 countrycode [A-Z]{2,2} Dvoslovna oznaka države prema ISO 3166 standardu a iznimno se koristi i dvoslovni kod XK za Kosovo. Podaci iz polja iz pain 001 Podaci iz polja iz pain 001 Podaci iz polja iz pain 001

XML message for Payment Initiation Implementation Guideline

XML message for Payment Initiation Implementation Guideline XML message for Payment Initiation Implementation Guideline Version 1.3 Version 1.3 Changes Updated 20160901 Customer Credit Transfer: Message element name is changed to Customer Credit Transfer Initiation

More information

pain ch-six cs-st; 1

pain ch-six cs-st; 1 Message Implementation Guideline Model: pain.002.001.03-ch-six-1.5. Version: 1 Issue date: November 2016 Author: Credit Suisse (Switzerland) Ltd. Message Overview... 2 Message Details... 5 Components...

More information

XML Message for Payment Status Report

XML Message for Payment Status Report XML Message for Payment Status Report Implementation Guidelines Version 1.1 Table of Contents Table of Contents... 2 1 Introduction... 5 1.1 Coverage... 6 1.2 Use of these Guidelines... 7 1.3 Character

More information

Orders in ISO format for issuance of transfers and cheques in euros

Orders in ISO format for issuance of transfers and cheques in euros Orders in ISO 20022 format for issuance of transfers and cheques in euros Series of banking standards and procedures Implementation Guide Adapted to version 1.0 RB 2017 SEPA Credit Transfer November 2017

More information

pain EPC; 1.0

pain EPC; 1.0 Message Implementation Guideline pain.008.001.02 - EPC; 1.0 Model: pain.008.001.02 - EPC Version: 1.0 Issue date: June 2015 Author: Credit Suisse Message Overview... 2 Message Details... 6 Components...

More information

SDD Bulk Payments XML File Format

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

More information

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 3

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 3 ISO 20022 CustomerPaymentStatusReport pain.002 version 3 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...

More information

XML message for Payment Initiation Implementation Guideline

XML message for Payment Initiation Implementation Guideline XML message for Payment Initiation Implementation Guideline Version 1.2 Version 1.2 Changes Updated 20130916 New column XML Tag added to the Customer Credit Transfer and Payment Status Report tables Version

More information

Orders in ISO format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies

Orders in ISO format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies Confidence, social commitment and quality Orders in ISO 20022 format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies February 2016 INDEX Page INTRODUCTION...

More information

Danish Inpayment Form 01, 04, 15, 71, 73, 75

Danish Inpayment Form 01, 04, 15, 71, 73, 75 Danish Inpayment Form 01, 04, 15, 71, 73, 75 Change log Version no. Date Change 0.1 15.07.2014 New design 0.2 29.10.2014 Remarks in English CGI rules added in Remarks Danish Clearing rules for addresses.

More information

SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES

SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES Doc: EPC315-10 26 January 2015 (Version 7.0 Approved) EPC SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information

Orders in ISO format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros

Orders in ISO format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros Confianza, compromiso social y calidad Orders in ISO 20022 format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros February 2018 CHANGE

More information

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 2

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 2 ISO 20022 CustomerPaymentStatusReport pain.002 version 2 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 26 January 2015 (Version 7.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out

More information

pain MandateInitiationRequestV03

pain MandateInitiationRequestV03 Corporate egateway Message Implementation Guideline MandateInitiationRequestV03 MIG version: 1.2 : 11-02-2017 2 of 14 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 4 4.

More information

pain MandateCancellationRequestV03

pain MandateCancellationRequestV03 Corporate egateway Message Implementation Guideline MandateCancellationRequestV03 MIG version: 1.2 : 01-10-2018 2 of 12 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3

More information

C2B - Customer to Bank Services

C2B - Customer to Bank Services SEPA Data Format (XML) Version: 02.02 Status: Final Go live date: 2016-02-01 Related Documents Reference Title Source EPC132-08 Implementation Guidelines SEPA CT C2B European Payments Council EPC130-08

More information

ISO XML message for Payment Initiation Implementation Guideline. Version 1.0 Estonia

ISO XML message for Payment Initiation Implementation Guideline. Version 1.0 Estonia ISO 20022 XML message for Payment Initiation Implementation Guideline Version 1.0 Estonia Approved by payment standards working group of Estonian Banking Association 31.01.2013 Table of contents Table

More information

Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) (28)

Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) (28) Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) 2015-11-17 1 (28) ver15.02.01 Introduction This document describes the usage on a set of ISO20022 messages.

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.5 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.4 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1

More information

Bank Connect. Customer Credit Transfer Pain Table of Contents

Bank Connect. Customer Credit Transfer Pain Table of Contents Bank Connect Customer Credit Transfer Pain 001.001.03 Table of Contents Introduction... 2 Scope... 2 Character set... 2 Change log... 3 Explanation on format usage... 5 1 Introduction This Danish Message

More information

XML Message for SEPA Direct Debit Initiation

XML Message for SEPA Direct Debit Initiation XML Message for SEPA Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 1.4 Table of Contents 1 Introduction... 4 1.1 SEPA Direct Debit definition... 5 1.2 Message

More information

Rules for the use of ISO standard data format in LUMINOR-TO-CUSTOMER statement

Rules for the use of ISO standard data format in LUMINOR-TO-CUSTOMER statement Rules for the use of ISO 20022 standard data format in LUMINOR-TO-CUSTOMER statement Version 1.4 September 2017 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Customer Direct Debit Initiation (pain.008) Version 2.6, with effect

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) ISO 20022 Payments for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Version 2.5.2 21.08.2017 General note Any suggestions or questions relating to this document should be addressed

More information

Version OUTGOING PAYMENTS SERVICE DESCRIPTION. Pain Pain

Version OUTGOING PAYMENTS SERVICE DESCRIPTION. Pain Pain Version 2.6 15.1.2018 OUTGOING PAYMENTS SERVICE DESCRIPTION Pain001.001.03 Pain002.001.03 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 30 November 2012 (Version 5.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information

ISO Customer Direct Debit Initiation

ISO Customer Direct Debit Initiation ISO 20022 Customer Direct Debit Initiation pain.008.001.02 Version 1.0.1 Publishing date 10 January 2017 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL INFORMATION...

More information

Rules for the use of ISO standard data format in DNB BANK-TO-CUSTOMER statement

Rules for the use of ISO standard data format in DNB BANK-TO-CUSTOMER statement Rules for the use of ISO 20022 standard data format in DNB BANK-TO-CUSTOMER statement Version 1.3 April 2016 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data exchange

More information

ISO XML messages for Customer Credit Transfer and Account Statement. Contents. Implementation Guideline

ISO XML messages for Customer Credit Transfer and Account Statement. Contents. Implementation Guideline ISO 20022 XML messages for Customer Credit Transfer and Account Statement Implementation Guideline Contents Introduction... 2 1. Message content of the Customer Credit Transfer... 3 2. Additional description

More information

pain CustomerDirectDebitInitiationV02

pain CustomerDirectDebitInitiationV02 Corporate egateway Message Implementation Guideline CustomerDirectDebitInitiationV02 MIG version: 1.2 : 01-10-2018 2 of 13 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Nordea usage of 20022

More information

ISO Message Implementation Guide for Payment Initiation

ISO Message Implementation Guide for Payment Initiation ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.7 Issue date: 12 January 2017 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 20022 Message Implementation Guidelines for payment initiation pain.001.001.03 CustomerCreditTransferInitiationV03 Version: 0.2 : Author: Luminor Bank AB 31/08/2015 2 of 17 Table of contents 1. Introduction...

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 1 November 2010 (Version 5.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the rules for implementing

More information

XML Message for European Direct Debit Initiation

XML Message for European Direct Debit Initiation XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 4.1a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 17 November 2011 (Version 4.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information

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

Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) Version 6.4 July 2013 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0

More information

ISO Customer-to-Bank messages usage guidelines

ISO Customer-to-Bank messages usage guidelines ISO 20022 Customer-to-Bank messages usage guidelines 1 Contents 1. Foreword... 3 2. Message description... 3 3. Message structure... 4 3.1. Message structure... 4 3.2. Character set... 5 3.3. Message pain.001.001.03...

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 1 November 2010 (Version 3.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the

More information

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part. Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC301-07 30 November 2012 (Version 5.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. 2017.11.27 Version 1.6 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of

More information

Format description CT-XML import

Format description CT-XML import Format description CT-XML import Rabo Cash Management Rabobank Format description CT-XML import 2 October 2017 Version 1.02 1 Contents 1 CT-XML import format... 3 1.1 CT-XML import format description...

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 3.2.a (see updates in annex 3) Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines... 6 1.3

More information

Code Name Definition Primjena. 2 AC02 InvalidDebtorAccountNumber Debtor account number invalid or missing Broj računa platitelja je neispravan.

Code Name Definition Primjena. 2 AC02 InvalidDebtorAccountNumber Debtor account number invalid or missing Broj računa platitelja je neispravan. ExternalStatusReason1Code Code Name Definition Primjena 1 AC01 IncorrectAccountNumber Account number is invalid or missing. SEPA: Account identifier incorrect (e.g. invalid IBAN) Broj računa je neispravan

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 October 2009 (Version 3.4 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Doc: EPC114-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing

More information

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part. Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit

More information

Mutual Fund Trailer Fee Payments Market Practice

Mutual Fund Trailer Fee Payments Market Practice Mutual Fund Trailer Fee Payments Market Practice ISITC Payments Working Group DISCLAIMER This market practice document has been developed by the International Securities Association for Institutional Trade

More information

XML message for Payment Initiation Implementation Guideline. Pain001. Version 1.0

XML message for Payment Initiation Implementation Guideline. Pain001. Version 1.0 XML message for Payment Initiation Implementation Guideline Pain001 Version 1.0 1 Version history Version Changes Date 1.0 First version 21.09.2015 1.1 ControlSum field is mandatory in GroupHeader and

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. Version 1.7 / 2018-04-13 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type

More information

XML Message for European Direct Debit Initiation

XML Message for European Direct Debit Initiation XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 3.0.a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be

More information

Danske Bank Baltic ISO XML messages for Payment Initiation and Cash Management Implementation Guideline. Pain001 Pain002 Camt052 Camt053 Camt054

Danske Bank Baltic ISO XML messages for Payment Initiation and Cash Management Implementation Guideline. Pain001 Pain002 Camt052 Camt053 Camt054 Danske Bank Baltic ISO 20022 XML messages for Payment Initiation and Cash Management Implementation Guideline Pain001 Pain002 Camt052 Camt053 Camt054 Version 1.0 1 Version history Version Changes Date

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. 2016.11.28 Version 1.5 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.0 XML message for Credit Transfer Initiation 2 Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines...

More information

CZECH REPUBLIC INSIDEBUSINESS PAYMENTS CZECH REPUBLIC ANNEX. File formats and validations. Contents

CZECH REPUBLIC INSIDEBUSINESS PAYMENTS CZECH REPUBLIC ANNEX. File formats and validations. Contents INSIDEBUSINESS PAYENTS CZECH REPUBLIC ANNEX File formats and validations Contents Validation of fields 2 CFD File Format 3 CFA File Format 5 Single credit transfer format T103 8 Single European Credit

More information

THE REPUBLIC OF CROATIA COPY 1 MINISTRY OF FINANCE-TAX ADMINISTRATION - for the claimant

THE REPUBLIC OF CROATIA COPY 1 MINISTRY OF FINANCE-TAX ADMINISTRATION - for the claimant R E P U B L I K A H R V A T S K A MINISTARSTVO FINANCIJA-POREZNA UPRAVA PRIMJERAK 1 - za podnositelja zahtjeva - THE REPUBLIC OF CROATIA COPY 1 MINISTRY OF FINANCE-TAX ADMINISTRATION - for the claimant

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines Swiss Recommendations for credit transfers pain.001.001.03.ch.02 - SR Version 1.5.1 US Version 1.0 July 2016 US Implementation Guidelines Swiss Recommendations for credit transfers

More information

Multi-Currency Bulk Payments XML File Format

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

More information

Multi-Currency Bulk Payments XML File Format

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

More information

Differences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct

Differences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct Differences BTL91and Generic Payment File RCM, RIB Pro, RDC and SWIFT FileAct Contents 1 GENERAL INFORMATION 3 2 INTRODUCTION 3 3 GENERAL DIFFERENCES 4 4 DESCRIPTION OF THE DIFFERENCES 6 APPENDIX: CHANGE

More information

SEPA Credit Transfer Instructions

SEPA Credit Transfer Instructions SEPA Credit Transfer Instructions STANDARD ISO 20022 pain.001.001.03 Guideline for SEPA Credit Transfer Instructions transmitted to Société Générale France Version: August 2015 ORDRE DE VIREMENT SEPA STANDARD

More information

ISO Credit Notification

ISO Credit Notification ISO 20022 Credit Notification camt.054 version 2 Version 1.0.0 Publishing date 30 November 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES... 4 2.1

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Page 2 of 16 Table of contents 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Service description Corporate Access Payables Appendix Denmark

Service description Corporate Access Payables Appendix Denmark Service description Corporate Access Payables Appendix Denmark Page 2 of 21 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Table of contents Page 2 of 13 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.5 : eference to equest for Transfer expected to be launched during Q4 2018

More information

PODALI O PODNOSITELJU ZAHTJEVA DAVATELJU LICENCE INFORMATION ON THE CLAIMANT LICENSOR:

PODALI O PODNOSITELJU ZAHTJEVA DAVATELJU LICENCE INFORMATION ON THE CLAIMANT LICENSOR: REPUBLIKA HRVATSKA MINISTARSTVO FINANCIJA - POREZNA UPRAVA THE REPUBLIC OF CROATIA MINISTRY OF FINANCE TAX ADMINISTRATIO PRIMJERAK I - za podnositelja zahtjeva - copy 1 - tor the daimant - ZAHTJEV ZA UMANJENJE

More information

Implementation guide. ISO Credit Notification camt.054 version 2

Implementation guide. ISO Credit Notification camt.054 version 2 Implementation guide ISO 20022 Credit Notification camt.054 version 2 Version 1.1.1 Publishing date 13 April 2018 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.6 : eference to Treasury payments expected to be launched during Q1 2019 2

More information

Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix

Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix pain.001 version 3 pain.002 version 3 pain.006 version 1 May 2013 Content 1. Background... 4 2. About Corporate Payments

More information

SWIFT for Corporates

SWIFT for Corporates SWIFTStandards MT Implementation Guide This document describes the rules users must follow when sending or receiving SWIFTStandards MT in SCORE (Standardised Corporate Environment). Cash Management Standards

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines CustomerCreditTransferInitiationV03 MIG version: 1.7 : 2 of 31 Table of contents 1. Introduction... 3 2. About Corporate Access Payables... 3

More information

Service description. Corporate Access Payables Appendix Finland

Service description. Corporate Access Payables Appendix Finland Service description Corporate Access Payables Appendix Finland Page 2 of 5 Table of contents APPENDIX FINLAND... 3 2 GENERAL OVERVIEW OF THE FINNISH PAYMENT INFRASTRUCTURE... 3 2. AVAILABLE PAYMENT TYPES...

More information

ISO Message Implementation Guide for Cash Management Reports

ISO Message Implementation Guide for Cash Management Reports ISO 20022 Message Implementation Guide for Cash Management Reports CAMT052 CAMT053 CAMT054 CAMT060 Version: 1.5 Issue date: 9 July 2015 Author: Swedbank Table of Contents 1. Introduction 2. Bank To Customer

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.3 : Note: Please refer to Change document 1.3 under Introduction chapter for

More information

Service description. Corporate Access Payables Appendix Denmark

Service description. Corporate Access Payables Appendix Denmark Service description Corporate Access Payables Appendix Denmark Page 2 of 19 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN)

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Version 6.0 - May 2012 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0 Group

More information

Service description Corporate Access Payables Appendix Finland

Service description Corporate Access Payables Appendix Finland Service description Corporate Access Payables Appendix Finland Page 2 of 2 Page 2 of 2 Table of contents APPENDIX FINLAND... 3 2 GENERAL OVERVIEW OF THE FINNISH PAYMENT INFRASTRUCTURE... 3 2. AVAILABLE

More information

Message Item XML Tag Occurrence Data Type / Code Message Item Definition T2S Mapping Use in T2S Business Rules SCOPE

Message Item XML Tag Occurrence Data Type / Code Message Item Definition T2S Mapping Use in T2S Business Rules SCOPE SecuritiesTransactionCancellat ionrequeststatusadvicev02 Document Document Last updated: 30/09/2013 SctiesTxCxlReqS tsadvc 1..1 SecuritiesTransactionCancella tionrequeststatusadvicev03 SCOPE An account

More information

ISO Cash Management

ISO Cash Management ISO 20022 Cash Management Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer (camt.053) Bank-to-Customer Debit/Credit Notification

More information

Corporate Payments Service. Example appendix - pain.001 version 3

Corporate Payments Service. Example appendix - pain.001 version 3 Corporate Payments Service Example appendix - pain.001 version 3 January 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 Message structure... 3 4 Example of the payment initiation

More information

KORISNIĈKA UPUTA za servis eblokade

KORISNIĈKA UPUTA za servis eblokade KORISNIĈKA UPUTA Zagreb, 2. listopad 2014. strana: 2/23 Pregled verzija dokumenta: Oznaka verzije Datum Opis promjene 1.0. 19.06.2013. Inicijalna korisnička uputa 2.0. 24.06.2013. Unaprjeđenje funkcionalnosti

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 2018 Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer (camt.053) Bank-to-Customer Debit/Credit Notification (camt.054) Version

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.1 : 02-01-2017 2 of 28 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

Version 8.0 final for Core rulebook 9.1 and B2B rulebook 7.1

Version 8.0 final for Core rulebook 9.1 and B2B rulebook 7.1 Nets Denmark A/S Lautrupbjerg 10 P.O. 500 DK-2750 Ballerup T + 45 44 68 44 68 F 45 44 86 09 30 www.nets.eu CVR-nr. 20016175 17 August 2016 SEPA Direct Debit Interface Description RBF/LP edition Version

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Changes in Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 Changes in version 1.3 since version 1.2 MIG version: 1.3 : 20-06-2016 Please refer

More information

Corporate Payments. Example appendix, pain.001 version 2. March 2018

Corporate Payments. Example appendix, pain.001 version 2. March 2018 Corporate Payments Example appendix, pain.001 version 2 March 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 The message structure... 3 4 Example of the payment initiation message...

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.3 : 2018.11.26 2 of 28 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description

camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification 28.06.2016 Format Description camt.053 Format Description Introduction... 3 Character set...

More information

[SLOVAK REPUBLIC] ANNEX. File formats and validations. Validation of fields 2. SKI File Format - Domestic payment 3. SKI File Format - Direct debit 5

[SLOVAK REPUBLIC] ANNEX. File formats and validations. Validation of fields 2. SKI File Format - Domestic payment 3. SKI File Format - Direct debit 5 ANNEX File formats and validations Validation of fields 2 SKI File Format - Domestic payment 3 SKI File Format - Direct debit 5 [SLVAK REPUBLIC] MT100 File Format 7 Single credit transfer format MT103

More information

Ime i prezime / naziv tvrtke Full name / business name: Pravni oblik Legal form:..

Ime i prezime / naziv tvrtke Full name / business name: Pravni oblik Legal form:.. R E P U B L I K A H R V A T S K A PRIMJERAK 1 MINISTARSTVO FINANCIJA-POREZNA UPRAVA - za podnositelja zahtjeva - THE REPUBLIC OF CROATIA COPY 1 MINISTRY OF FINANCE-TAX ADMINISTRATION - for the claimant

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Business Rules for Payments and Cash Management for Customer-Bank Messages Version 2.7, with effect from November 2018 Version 2.7 18.12.2017 General note Any suggestions

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Page 2 of 19 Table of contents 1 APPENDIX NORWAY 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE 3 2.1 AVAILABLE PAYMENT TYPES

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.2 : 2018.02.01 2 of 24 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

SEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE

SEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE EPC012-16 Version 1.0 05 April 2016 SEPA DIRECT DEBIT CORE RULEBOOK CHANGE REQUEST - PUBLIC CONSULTATION DOCUMENT COVER PAGE The Single Euro Payments Area (SEPA) payment schemes, as set out in the SEPA

More information

SEPA CREDIT TRANSFER RULEBOOK 2018 CHANGE REQUEST PUBLIC CONSULTATION DOCUMENT COVER PAGE

SEPA CREDIT TRANSFER RULEBOOK 2018 CHANGE REQUEST PUBLIC CONSULTATION DOCUMENT COVER PAGE EPC005-18 Version 1.0 13 March 2018 SEPA CREDIT TRANSFER RULEBOOK 2018 CHANGE REQUEST PUBLIC CONSULTATION DOCUMENT COVER PAGE The Single Euro Payments Area (SEPA) payment schemes, as set out in the SEPA

More information

SEPA INSTANT CRED IT TRANSFER (SCT INST) SCHEME RULEBOOK

SEPA INSTANT CRED IT TRANSFER (SCT INST) SCHEME RULEBOOK EPC 004-16 2017 Version 1.1 Issue date: 18 October 2017 Date effective: 21 November 2017 Time effective: 08:00:00.000 CET SEPA INSTANT CRED IT TRANSFER (SCT INST) SCHEME RULEBOOK Conseil Européen des Paiements

More information