SEB GATEWAY Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės. v

Size: px
Start display at page:

Download "SEB GATEWAY Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės. v"

Transcription

1 SEB GATEWAY Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės v

2 Content Account Statement (camt Statement2) 3 Notification (camt Notification) 12 Payments (pain Custom credit Transfer Initiation) 21 Payment status report (pain Paymet Status Report) 29 Balance request (camt Balance/statement request) 36 Balance report (camt Balance) 38 SEB LT transaction types 40

3 Statement. (ISO 20022: camt Statement2) Index Or Message element <XML Tag> Mult Rules Type Field description LITAS-ESIS Remarks Message root <BkToCstmrStmt> [1..1] GroupHeader <GrpHdr> [1..1] Component (GroupHeader32) MessageIdentification <MsgId> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime Date & Time Header 2 & MessageRecipient <MsgRcpt> [0..1] Component (PartyIdentification32) +++Name <Nm> [0..1] Max140Text +++Identification <Id> [0..1] Component (Party6Choice) ++++OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) +++++BICOrBEI <BICOrBEI> [0..1] AnyBICIdentifier MessagePagination <MsgPgntn> [0..1] Component +++PageNumber <PgNb> [1..1] Max5NumericText +++LastPageIndicator <LastPgInd> [1..1] YesNoIndicator 2.0 +Statement <Stmt> [1..n] Component (AccountStatement2) Identification <Id> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime Date & Time Header 2 & FromToDate <FrToDt> [1..1] Category (DateTimePeriodDetails) +++FromDateTime <FrDtTm> [1..1] ISODateTime Start date +++ToDateTime <ToDtTm> [1..1] ISODateTime End date Account <Acct> [1..1] Component (CashAccount20) +++Identification <Id> [1..1] Component {Or ++++IBAN <IBAN> [1..1] IBAN2007Identifier Statement's account iban Header Currency <Ccy> [0..1] Code Statement's account currency Header Type <Tp> [0..1] Component (CashAccountType2) Usage: The account servicing institution has to make sure that MessageIdentification is unique per account owner for a pre-agreed period. ++++Code <Cd> [1..1] Code Used values: CACC - current account SVGS - deposit account If not provided will be treated as current account +++Owner <Ownr> [0..1] Component (PartyIdentification32) ++++Name <Nm> [0..1] Max140Text Client's name Header PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) +++++TownName <TwnNm> [0..1] Text Client's city Header Country <Ctry> [0..1] Country Code +++++AddressLine <AdrLine> [0..7] Max70Text Client's address Header Identification <Id> [0..1] Choice component (Party6Choice) {Or +++++OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) {{Or Other <Othr> [1..2] Component Identification SchemeName Code <Id> [1..1] Max35Text Owner's ID code Bank's CIF Header 12 Header 10 <Cd> [1..1] ExternalOrganisationIdentification1Code If CIF is entered, value has to be BANK If Customer s ID code is filled - COID Or} +++++PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) Other <Othr> [1..2] Component Identification SchemeName <Id> [1..1] Max35Text Owner's ID code Bank's CIF Header 12 Header 10 SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 3 of 41

4 {{Or Code <Cd> [1..1] ExternalOrganisationIdentification1Code If CIF is entered, value has to be BANK If Customer s ID code is filled - NIDN ++++ContactDetails <CtctDtls> [0..n] Component +++++Other <Othr> [0..1] Text Other information on payer Header Servicer <Svcr> [0..1] Component (BalanceType12) {Or ++++FinancialInstitutionIdentification <FinInstnId> [1..1] +++++BIC <BIC> [1..1] BICIdentifier +++++Name <Nm> [0..1] Max140Text Component (BranchAndFinancialInstitutionIdentification4) +++++PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) TownName <TwnNm> [0..1] Max35Text AddressLine <AdrLine> [0..7] Max70Text +++++Other <Othr> [0..1] Component (GenericFinancialIdentification1) Identification <Id> [0..1] Max35Text SchemeName Code BIC of payer credit institution Header 4 Only BIC is used Name of payer's credit institution Header 5 City of payer's credit institution Header 8 Address of payer's credit institution Id-code of payer's credit institution Header 7 Header 6 <Cd> [1..1] Code TXID is only allowed ++++BranchIdentification <BrnchId> [0..1] +++++Name <Nm> [0..1] Max140Text Component (BranchAndFinancialInstitutionIdentification4) Balance <Bal> [1..n] Component (CashBalance3) Type <Tp> [1..1] Component (BalanceType12) CodeOrProprietary <CdOrPrtry> [1..1] Choice component (BalanceType5Choice) 2.26 Branch of payer's credit institution +++++Code <Cd> [1..1] Code Type of balance Accepted values: CLBD - ClosingBooked OPBD - OpeningBooked CreditLine <CdtLine> [0..1] Component (CreditLine2) Included <Incl> [1..1] TrueFalseIndicator If not present, credit line is not included in the balance amount Amount <Amt> [0..1] ActiveOrHistoricCurrencyAndAmount Amount <Amt> [1..1] Amount Account balance (including currency) +++CreditDebitIndicator <CdtDbtInd> [1..1] Code C / D Body 7 Values: CRDT or DBIT Usage: A zero balance is considered to be a credit balance. Header Date <Dt> [1..1] Choice component (DateAndDateTimeChoice) {Or ++++Date <Dt> [1..1] ISODate Transaction execution (booking) date Or} ++++DateTime <DtTm> [1..1] ISODateTime Transaction execution (booking) date and time TransactionsSummary <TxsSummry> [0..1] Component (TotalTransactions2) Body 3 Body 3 & TotalEntries <TtlNtries> [0..1] Component (NumberAndSumOfTransactions2) NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Sum <Sum> [0..1] DecimalNumber CreditDebitIndicator <CdtDbtInd> [0..1] Code TotalCreditEntries <TtlCdtNtries> [0..1] Component (NumberAndSumOfTransactions1) SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 4 of 41

5 NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Number of credit entries Sum <Sum> [0..1] DecimalNumber TotalDebitEntries <TtlDbtNtries> [0..1] Component (NumberAndSumOfTransactions1) NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Number of debit entries Sum <Sum> [0..1] DecimalNumber Entry <Ntry> [0..n] Component (ReportEntry2) Usage: At least one reference must be provided to identify the entry and its underlying transaction(s). Mandatory in case statement contains at least one operation +++Amount <Amt> [1..1] Amount Amount and currency Body 5 Usage: <Amt Ccy="SEK"> </Amt> Does NOT Include charges CreditDebitIndicator <CdtDbtInd> [1..1] Code Values: CRDT or DBIT +++ReversalIndicator <RvslInd> [0..1] TrueFalseIndicator Usage: This element should only be present if the entry is the result of a reversal. If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry. If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry. +++Status <Sts> [1..1] Code SEPA allowed value "BOOK". BOOK - Booked +++BookingDate <BookgDt> [0..1] DateAndDateTimeChoice Usage: Booking date is the expected booking date, unless the status is booked, in which case it is the actual booking date. {Or ++++Date <Dt> [1..1] ISODate Or} ++++DateTime <DtTm> [1..1] ISODateTime +++ValueDate <ValDt> [0..1] DateAndDateTimeChoice Usage: If entry status is pending and value date is present, then the value date refers to an expected/requested value date. For entries subject to availability/float and for which availability information is provided, the value date must not be used. In this case the availability component identifies the number of availability days. {Or ++++Date <Dt> [1..1] ISODate BankTransactionCode <BkTxCd> [1..1] Component (BankTransactionCodeStructure4) Domain <Domn> [0..1] Component (BankTransactionCodeStructure5) Code <Cd> [1..1] ExternalBankTransactionDomain1Code Type of operation Body 2 See LT op. code sheet Family <Fmly> [1..1] Component (BankTransactionCodeStructure6) Code <Cd> [1..1] ExternalBankTransactionFamily1Code SubFamilyCode <SubFmlyCd> [1..1] ExternalBankTransactionSubFamily1Code EntryDetails <NtryDtls> [1..1] Component (EntryDetails1) TransactionDetails <TxDtls> [0..n] Component (EntryTransaction2) References <Refs> [0..1] Component (TransactionReferences2) AccountServicerReference <AcctSvcrRef> [0..1] Max35Text Operation row (identifier) Body InstructionIdentification <InstrId> [0..1] Max35Text User entered payment document number Body 10 User inputed payment number. Cannot be generated by the bank SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 5 of 41

6 EndToEndIdentification <EndToEndId> [0..1] Max35Text Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. Usage: In case there are technical limitations to pass on multiple references, the end-to-end identification must be passed on throughout the entire end-to-end chain TransactionIdentification <TxId> [0..1] Max35Text Transaction ID assigned by originator's bank Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre-agreed period AmountDetails <AmtDtls> [0..1] Component (AmountAndCurrencyExchange3) InstructedAmount <InstdAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Amount <Amt> [1..1] Amount Original amount (filled in case of FX) TransactionAmount <TxAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Amount <Amt> [1..1] Amount Amount and currency (in case of no FX) CurrencyExchange <CcyXchg> [0..1] Component (CurrencyExchange5) SourceCurrency <SrcCcy> [1..1] ActiveOrHistoricCurrencyCode TargetCurrency <TrgtCcy> [0..1] ActiveOrHistoricCurrencyCode UnitCurrency <UnitCcy> [0..1] ActiveOrHistoricCurrencyCode Body 8 & 9 Body 5 Usage: This component (on transaction level) should be used in case booking is for a single transaction and the original amount is different from the entry amount. It can also be used in case individual original amounts are provided in case of a batch or aggregate booking. Payment amount in EUR. Should be present if amount is different from entry amount Amount prior to charges. Used if the currency is the same as acc currency Used only in SWIFT and all debit cases Mandatory for SEPA. Payment amount in EUR Mandatory if AmountDetails is used ExchangeRate <XchgRate> [1..1] BaseOneRate Usage: ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency) CounterValueAmount <CntrValAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Usage: This can be either the counter amount quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges. No FX information - just output of resulting FX Amount <Amt> [1..1] Amount Equivalent (filled in case of FX) 6 Body CounterValue - equivalent in other currency. ProprietaryAmount - equivalent in national currency +++++ProprietaryAmount <PrtryAmt> [0..n] Component (AmountAndCurrencyExchangeDetails4) in case of SEPA EUR is used Type <Tp> [1..1] Max35Text allowed value - EQUIVALENT Amount <Amt> [1..1] Amount Equivalent CurrencyExchange <CcyXchg> [0..1] Component (CurrencyExchange5) SourceCurrency <SrcCcy> [1..1] ActiveOrHistoricCurrencyCode SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 6 of 41

7 TargetCurrency <TrgtCcy> [0..1] ActiveOrHistoricCurrencyCode UnitCurrency <UnitCcy> [0..1] ActiveOrHistoricCurrencyCode ExchangeRate <XchgRate> [1..1] BaseOneRate Usage: ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency) RelatedParties <RltdPties> [0..1] Component (TransactionParty2) Debtor <Dbtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Payer's name For credit: Body 18 For debit: Body PostalAddress <PstlAdr> [0..1] Choice component (PostalAddress6) Country <Ctry> [0..1] CountryCode AddressLine <AdrLine> [0..7] Max70Text Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) {{Or BICOrBEI According to SEPA recommendation payer's information should be entered here <BICOrBEI> [0..1] AnyBICIdentifier Payer's BIC or BEI code Used only in case of SEPA payment Other <Othr> [1..n] Component Identification SchemeName Code <Id> [1..1] Max35Text Payer's id-code Customer s code in beneficiary s IS Unique payer reference number (in case of SWIFT) For credit: Body 19 For debit: Header 12 Body 12 In case of debit payer's ID code might also be provided, although it's not availble in LITAS-ESIS <Cd> [1..1] ExternalOrganisationIdentification1Code If payer's ID code is entered, value has to be COID If Customer s code in beneficiary's IS is filled - CUST If Unique payer reference number is filled - BANK Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) BirthDate <BirthDt> [1..1] ISODate Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [1..n] Component For SEPA this element should be used only once Identification SchemeName <Id> [1..1] Max35Text Payer's id-code Customer s code in beneficiary s IS Unique payer reference number (in case of SWIFT) For credit: Body 19 Body 12 For debit: Header 12 Body 12 In case of debit payer's ID code might also be provided, although it's not availble in LITAS-ESIS SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 7 of 41

8 {{Or <Cd> [1..1] ExternalOrganisationIdentification1Code If payer's ID code is entered, value has to be NIDN If Customer s code in beneficiary's IS is filled - CUST If Unique payer reference number is filled - BANK Absence of this field means that payer's ID code is provided Code DebtorAccount <DbtrAcct> [0..1] Component (CashAccount16) Identification <Id> [1..1] Component {Or IBAN <IBAN> [1..1] IBAN2007Identifier Or} Other <Othr> [1..1] Component (GenericAccountIdentification1) Payer's account iban In case of credit: Body 17 In case of debit: Header Identification <Id> [1..1] Max34Text Beneficiary s account number In case of credit: Header 17 In case of debit: Body SchemeName <SchmeNm> [0..1] Component (AccountSchemeName1Choice) {Or Code <Cd> [1..1] ExternalAccountIdentification1Code Or} Proprietary <Prtry> [1..1] Max35Text UltimateDebtor <UltmtCdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Name of originator Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) Other <Othr> [0..n] Component Identification <Id> [1..1] Max35Text Id-code of originator Body SchemeName Or}} Proprietary <Prtry> [1..1] Max35Text Originator s account number Body 21 Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) Filled when CreditDebitIndicator is DBIT In other case debitor account = statement's account In case of SWIFT payment payer account is BBAN BirthDate <BirthDt> [1..1] DateTime Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [0..n] Component Identification <Id> [1..1] Max35Text Id-code of originator Body SchemeName Or}} Proprietary <Prtry> [1..1] Max35Text Originator s account number Body Creditor <Cdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Beneficiary s name In case of credit: Header 11 In case of debit: Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) Other <Othr> [1..2] Component For SEPA this element should be used only once SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 8 of 41

9 {{Or Identification SchemeName Code <Id> [1..1] Max35Text Beneficiary's id-code Customer s code in payer s information system In case of credit: Header 12 Body 20 In case of debit: Body 19 Body 20 <Cd> [1..1] ExternalOrganisationIdentification1Code If Customer s code in payer s information system is being used, value has to be CUST Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) {Or DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) BirthDate <BirthDt> [1..1] DateTime Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [1..2] Component Identification SchemeName Code <Id> [1..1] Max35Text Beneficiary's id-code or Customer s code in payer s information system In case of credit: Header 12 Body 20 In case of debit: Body 19 Body 20 <Cd> [1..1] ExternalOrganisationIdentification1Code If Customer s code in payer s information system is being used, value has to be CUST CreditorAccount <CdtrAcct> [0..1] Component (CashAccount16) Identification <Id> [1..1] Choice component (AccountIdentification4Choice) {Or IBAN <IBAN> [1..1] IBAN2007Identifier Beneficiary s account number In case of credit: Header 17 In case of debit: Body 17 Filled when CreditDebitIndicator is CRDT In other case creditor account = statement's account Or} Other <Othr> [1..1] Component (GenericAccountIdentification1) Identification <Id> [1..1] Max34Text Beneficiary s account number In case of credit: Header 17 In case of debit: Body 17 Used in case of SWIFT when IBAN is not used SchemeName <SchmeNm> [0..1] Component (AccountSchemeName1Choice) {Or Code <Cd> [1..1] ExternalAccountIdentification1Code In case of SWIFT payment beneficiary account is BBAN Or} Proprietary <Prtry> [1..1] Max35Text UltimateCreditor <UltmtCdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Name of beneficiary party Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) Or}} Other <Othr> [0..n] Component Identification <Id> [1..1] Max35Text Id-code of beneficiary party Body SchemeName Proprietary <Prtry> [1..1] Max35Text Beneficiary party s account number Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) Body 24 SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 9 of 41

10 Or}} BirthDate <BirthDt> [1..1] DateTime Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [0..n] Component Identification <Id> [1..1] Max35Text Id-code of beneficiary party Body SchemeName Proprietary <Prtry> [1..1] Max35Text Beneficiary party s account number RelatedAgents <RltdAgts> [0..1] Component (TransactionAgents2) DebtorAgent <DbtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> [1..1] BICIdentifier Name <Nm> [0..1] Max140Text Component (BranchAndFinancialInstitutionIdentification4) Component (BranchAndFinancialInstitutionIdentification4) PostalAddress <PstlAdr> [0..1] Component PostalAddress6) BIC of credit institution of account statement Name of credit institution of account statement Body 24 Header 4 Header 5 Filled when CreditDebitIndicator is DBIT According to LITAS-BIC Filled when CreditDebitIndicator is DBIT AddressLine <AdrLine> [0..7] Max70Text Address of credit institution Header 7 Filled when CreditDebitIndicator is DBIT CreditorAgent <CdtrAgt> [0..1] Component (BranchAndFinancialInstitutionIdentification4) FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> [1..1] BICIdentifier Name <Nm> [0..1] Max140Text Component (BranchAndFinancialInstitutionIdentification4) PostalAddress <PstlAdr> [0..1] Component PostalAddress6) AddressLine <AdrLine> [0..7] Max70Text BIC of counterparty's credit institution Name of counterparty's credit institution Address of counterparty's credit institution Body 15 Body 16 Filled when CreditDebitIndicator is CRDT Filled when CreditDebitIndicator is CRDT Filled when CreditDebitIndicator is CRDT IntermediaryAgent1 <IntrmyAgt1> [0..1] FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentification4) Component (BranchAndFinancialInstitutionIdentification4) BIC <BIC> [1..1] BICIdentifier BIC of correspondent bank Name <Nm> [0..1] Max140Text Name of correspondent bank PostalAddress <PstlAdr> [0..1] Component PostalAddress6) AddressLine <AdrLine> [0..7] Max70Text Purpose <Purp> [0..1] Choice component (Purpose2Choice) Address of correspondent bank {Or Code <Cd> [1..1] ExternalPurpose1Code Not yet used Or} ++++Proprietary <Prtry> [1..1] Max35Text RemittanceInformation <RmtInf> [0..1] Component (RemittanceInformation5) Unstructured <Ustrd> [0..n] Max140Text Payment description Body Structured <Strd> [0..n] Component (StructuredRemittanceInformation7) CreditorReferenceInformation <CdtrRefInf> [0..1] Component (CreditorReferenceInformation2) Type <CdtrRefTp> [0..1] Component (CreditorReferenceType2) Choice component Code or Propietary <CdOrPrtry> [0..1] (CreditorReferenceType1Choice) Used only in case of SEPA payment SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 10 of 41

11 2.259 {Or Code <Cd> [1..1] DocumentType3Code Issuer <Issr> [0..1] Max35Text Reference <Ref> [0..1] Max35Text Reference code Body RelatedDates <RltdDts> [0..1] Component (TransactionDates2) InterbankSettlementDate <IntrBkSttlmDt> [0..1] ISODateTime DISP DispatchAdvice FXDR ForeignExchangeDealReference PU PurchaseOrder RADM RemittanceAdviceMessage RPIN RelatedPaymentInstruction SC StructuredCommunicationReference SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 11 of 41

12 Notification (ISO camt Notification) Index Or Message element <XML Tag> Mult Rules Type Field description LITAS-ESIS Remarks <BkToCstmrDbtCdtN Message root tfctn> [1..1] GroupHeader <GrpHdr> [1..1] Component (GroupHeader32) MessageIdentification <MsgId> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime Date & Time Header 2 & 3 From header MessageRecipient <MsgRcpt> [0..1] Component (PartyIdentification32) +++Name <Nm> [0..1] Max140Text Identification <Id> [0..1] Component (Party6Choice) ++++OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) +++++BICOrBEI <BICOrBEI> [0..1] AnyBICIdentifier MessagePagination <<MsgPgntn>> [0..1] Component +++PageNumber <PgNb> [1..1] Max5NumericText +++LastPageIndicator <LastPgInd> [1..1] YesNoIndicator 2.0 +Notification <Ntfctn> [1..1] Component (OriginalGroupInformation20) Identification <Id> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime Date & Time Header 2 & FromToDate <FrToDt> [0..1] Category (DateTimePeriodDetails) +++FromDateTime <FrDtTm> [1..1] ISODateTime Start date +++ToDateTime <ToDtTm> [1..1] ISODateTime End date Account <Acct> [1..1] Component (CashAccount20) +++Identification <Id> [1..1] Component {Or ++++IBAN <IBAN> [1..1] IBAN2007Identifier ++++Currency <Ccy> [0..1] Code +++Owner <Ownr> [0..1] Component (PartyIdentification32) Notiffication's account iban Header 17 Notification's account currency Header Name <Nm> [0..1] Max140Text Client's name Header PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) +++++TownName <TwnNm> [0..1] Text Client's city Header Country <Ctry> [0..1] Country Code +++++AddressLine <AdrLine> [0..7] Max70Text Client's address Header Identification <Id> [0..1] Choice component (Party6Choice) {Or +++++OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) {{Or Other <Othr> [1..2] Component Identification SchemeName Code <Id> [1..1] Max35Text Owner's ID code Bank's CIF Header 12 Header 10 The account servicing institution has to make sure that MessageIdentification is unique per account owner for a pre-agreed period. <Cd> [1..1] ExternalOrganisationIdentification1Code If CIF is entered, value has to be BANK If Customer s ID code is filled - COID Or} +++++PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) Other <Othr> [1..2] Component Identification <Id> [1..1] Max35Text Owner's ID code Bank's CIF Header 12 Header 10 SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 12 of 41

13 {{Or SchemeName Code <Cd> [1..1] ExternalOrganisationIdentification1Code If CIF is entered, value has to be BANK If Customer s ID code is filled - NIDN ++++ContactDetails <CtctDtls> [0..n] Component +++++Other <Othr> [0..1] Text Other information on payer Header Servicer <Svcr> [0..1] Component (BalanceType12) ++++FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentification4) +++++BIC <BIC> [1..1] BICIdentifier +++++Name <Nm> [0..1] Max140Text +++++PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) TownName <TwnNm> [0..1] Max35Text AddressLine <AdrLine> [0..7] Max70Text +++++Other <Othr> [0..1] Component (GenericFinancialIdentification1) Identification <Id> [0..1] Max35Text BIC of payer credit institution Header 4 Name of payer's credit institution City of payer's credit institution Address of payer's credit institution Id-code of payer's credit institution Header 5 Header 8 Header 7 Header 6 Only BIC is used SchemeName {Or Code <Cd> [1..1] Code TXID is only allowed ++++BranchIdentification <BrnchId> [0..1] Component (BranchAndFinancialInstitutionIdentification4) +++++Name <Nm> [0..1] Max140Text TransactionsSummary <TxsSummry> [0..1] Component (TotalTransactions2) TotalEntries <TtlNtries> [0..1] Component (NumberAndSumOfTransactions2) NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Sum <Sum> [0..1] DecimalNumber CreditDebitIndicator <CdtDbtInd> [0..1] Code TotalCreditEntries <TtlCdtNtries> [0..1] Component (NumberAndSumOfTransactions1) Branch of payer's credit institution NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Number of credit entries Sum <Sum> [0..1] DecimalNumber TotalDebitEntries <TtlDbtNtries> [0..1] Component (NumberAndSumOfTransactions1) NumberOfEntries <NbOfNtries> [0..1] Max15NumericText Number of debit entries Sum <Sum> [0..1] DecimalNumber Entry <Ntry> [1..1] Component (ReportEntry2) Header 16 Usage: At least one reference must be provided to identify the entry and its underlying transaction(s). +++Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount Amount and currency Body 5 Usage: <Amt Ccy="SEK"> </Amt> Does NOT Include charges In case of deposit accrued interest is provided +++CreditDebitIndicator <CdtDbtInd> [1..1] Code C / D Body 7 Values: CRDT or DBIT Usage: A zero balance is considered to be a credit balance. SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 13 of 41

14 ReversalIndicator <RvslInd> [0..1] Indicator Usage: This element should only be present if the entry is the result of a reversal. If the CreditDebitIndicator is CRDT and ReversalIndicator is Yes, the original operation was a debit entry. If the CreditDebitIndicator is DBIT and ReversalIndicator is Yes, the original operation was a credit entry. +++Status <Sts> [1..1] Code Value: BOOK In case of accrued interest - INFO +++BookingDate <BookgDt> [1..1] DateAndDateTimeChoice Usage: Booking date is the expected booking date, unless the status is booked, in which case it is the actual booking date. ++++Date <Dt> [1..1] ISODate Transaction execution Body 3 {Or (booking) date ++++DateTime <DtTm> [1..1] ISODate Transaction execution Body 3 & 4 If time for operation is not available, zeros Or} (booking) date and time will be present BankTransactionCode <BkTxCd> [1..1] Component (BankTransactionCodeStructure4) Type of operation Body 2 See sheet LT/EE/LV op. codes sheet Domain <Domn> [0..1] Component (BankTransactionCodeStructure5) Code <Cd> [1..1] ExternalBankTransactionDomain1Code Family <Fmly> [1..1] Component (BankTransactionCodeStructure6) Code <Cd> [1..1] ExternalBankTransactionFamily1Code SubFamilyCode <SubFmlyCd> [1..1] ExternalBankTransactionSubFamily1Code Interest <Intrst> [0..n] Component (TransactionInterest2) Usage: This component is used on entry level in the case of batch or aggregate bookings. ++++Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount Accrued interest Body 10 Used in case of deposit account CreditDebitIndicator <CdtDbtInd> [1..1] Code Rate <Rate> [0..n] Component (Rate3) Type <Tp> [1..1] Choice component (RateType4Choice) {Or Percentage <Pctg> [1..1] PercentageRate Interest rate of deposit EntryDetails <NtryDtls> [1..1] Component (EntryDetails1) TransactionDetails <TxDtls> [0..n] Component (EntryTransaction2) References <Refs> [0..1] Component (TransactionReferences2) AccountServicerReference <AcctSvcrRef> [0..1] Max35Text Operation row (identifier) Body InstructionIdentification <InstrId> [0..1] Max35Text User entered payment document number Body 10 Cannot be generated by the bank EndToEndIdentification <EndToEndId> [0..1] Max35Text Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. Usage: In case there are technical limitations to pass on multiple references, the end-to-end identification must be passed on throughout the entire end-to-end chain. SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 14 of 41

15 TransactionIdentification <TxId> [0..1] Max35Text Transaction ID assigned by originator's bank Usage: The transaction identification can be used for reconciliation, tracking or to link tasks relating to the transaction on the interbank level. Usage: The instructing agent has to make sure that the transaction identification is unique for a pre-agreed period AmountDetails <AmtDtls> [0..1] Component (AmountAndCurrencyExchange3) +++++InstructedAmount <InstdAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount Original amount (filled in case of FX) CurrencyExchange <CcyXchg> [0..1] Component (CurrencyExchange5) +++++TransactionAmount <TxAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount Amount and currency (in case of no FX) CurrencyExchange <CcyXchg> [0..1] Component (CurrencyExchange5) SourceCurrency <SrcCcy> [1..1] ActiveOrHistoricCurrencyCode TargetCurrency <TrgtCcy> [0..1] ActiveOrHistoricCurrencyCode UnitCurrency <UnitCcy> [0..1] ActiveOrHistoricCurrencyCode ExchangeRate <XchgRate> [1..1] BaseOneRate +++++CounterValueAmount <CntrValAmt> [0..1] Component (AmountAndCurrencyExchangeDetails3) Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount Equivalent (filled in case of FX) +++++ProprietaryAmount <PrtryAmt> [0..n] Component (AmountAndCurrencyExchangeDetails4) Body 8 & 9 Body 5 Usage: This component (on transaction level) should be used in case booking is for a single transaction and the original amount is different from the entry amount. It can also be used in case individual original amounts are provided in case of a batch or aggregate booking. Used only in SWIFT and all debit cases Usage: This can be either the counter amount quoted in an FX deal, or the result of the currency information applied to an instructed amount, before deduction of charges 6 Body CounterValue - equivalent in other currency. ProprietaryAmount - equivalent in national currency In case of SEPA amount in EUR Type <Tp> [1..1] Max35Text Allowed value - EQUIVALENT Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount CurrencyExchange <CcyXchg> [0..1] Component (CurrencyExchange5) SourceCurrency <SrcCcy> [1..1] ActiveOrHistoricCurrencyCode TargetCurrency <TrgtCcy> [0..1] ActiveOrHistoricCurrencyCode UnitCurrency <UnitCcy> [0..1] ActiveOrHistoricCurrencyCode ExchangeRate <XchgRate> [1..1] BaseOneRate Usage: ExchangeRate expresses the ratio between UnitCurrency and QuotedCurrency (ExchangeRate = UnitCurrency/QuotedCurrency) RelatedParties <RltdPties> [0..1] Component (TransactionParty2) Debtor <Dbtr> [0..1] Component (PartyIdentification32) According to SEPA recommendation payer's information should be entered here SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 15 of 41

16 Name <Nm> [0..1] Max140Text Payer's name For credit: Body 18 For debit: Body PostalAddress <PstlAdr> [0..1] Choice component (PostalAddress6) Country <Ctry> [0..1] CountryCode AddressLine <AdrLine> [0..7] Max70Text Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) {{Or BICOrBEI <BICOrBEI> [0..1] AnyBICIdentifier Payer's BIC or BEI code Used in case of SEPA payment Other <Othr> [1..n] Component For SEPA this element should be used only once Identification SchemeName Code <Id> [1..1] Max35Text Payer's id-code Customer s code in beneficiary s IS Unique payer reference number (in case of SWIFT) For credit: Body 19 Body 20 For debit: Header 12 Body 20 <Cd> [1..1] ExternalOrganisationIdentification1Code If payer's ID code is entered, value has to be COID If Customer s code in beneficiary's IS is filled - CUST If Unique payer reference number is filled - BANK In case of SEPA payment the following values are usable: CUST CustomerNumber EMPL EmployerIdentificationNumber GS1G GS1GLNIdentifier DUNS Data Universal Numbering System BANK BankPartyIdentification COID CountryIdentificationCode TXID TaxIdentificationNumber Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) BirthDate <BirthDt> [1..1] ISODate Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [1..n] Component For SEPA this element should be used only once SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 16 of 41

17 {{Or Identification SchemeName Code <Id> [1..1] Max35Text Payer's id-code Customer s code in beneficiary s IS Unique payer reference number (in case of SWIFT) For credit: Body 19 Body 12 For debit: Header 12 Body 12 Payer's id-code Customer s code in beneficiary s IS Unique payer reference number (in case of SWIFT) In case of SEPA payment the following values are usable: ARNU AlienRegistrationNumber CCPT PassportNumber CUST CustomerIdentificationNumber DRLC DriversLicenseNumber EMPL EmployeeIdentificationNumber NIDN NationalIdentityNumber SOSE SocialSecurityNumber TXID TaxIdentificationNumber <Cd> [1..1] ExternalOrganisationIdentification1Code If payer's ID code is entered, value has to be NIDN If Customer s code in beneficiary's IS is filled - CUST If Unique payer reference number is filled - BANK Absence of this field means that payer's ID code is provided DebtorAccount <DbtrAcct> [0..1] Component (CashAccount16) Identification <Id> [1..1] Component {Or IBAN <IBAN> [1..1] IBAN2007Identifier Or} Other <Othr> [1..1] Component (GenericAccountIdentification1) Payer's account iban In case of credit: Body 17 In case of debit: Header Identification <Id> [1..1] Max34Text Payer's account iban In case of credit: Body 17 In case of debit: Header SchemeName <SchmeNm> [0..1] Component (AccountSchemeName1Choice) Filled when CreditDebitIndicator is DBIT In other case debitor account = notification's account In case of SWIFT when IBAN is not used {Or Code <Cd> [1..1] ExternalAccountIdentification1Code In case of WIFT payment payer account is BBAN Or} Proprietary <Prtry> [1..1] Max35Text UltimateDebtor <UltmtCdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Name of originator Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) Other <Othr> [0..1] Component Identification <Id> [1..1] Max35Text Id-code of originator Body SchemeName Or}} Proprietary <Prtry> [1..1] Max35Text Originator s account number Body 21 Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) Other <Othr> [0..1] Component Identification <Id> [1..1] Max35Text Id-code of originator Body 23 SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 17 of 41

18 SchemeName Or}} Proprietary <Prtry> [1..1] Max35Text Originator s account number Body Creditor <Cdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Beneficiary s name In case of credit: Header 11 In case of debit: Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) {{Or Other <Othr> [1..2] Component For SEPA this element should be used only once Identification SchemeName Code <Id> [1..1] Max35Text Beneficiary's id-code Customer s code in payer s information system In case of credit: Header 12 Body 20 In case of debit: Body 19 Body 20 <Cd> [1..1] ExternalOrganisationIdentification1Code In case of SEPA payment the following values are usable: CUST CustomerNumber EMPL EmployerIdentificationNumber GS1G GS1GLNIdentifier DUNS Data Universal Numbering System BANK BankPartyIdentification COID CountryIdentificationCode TXID TaxIdentificationNumber Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) DateAndPlaceOfBirth <DtAndPlcOfBirth> [0..1] Component (DateAndPlaceOfBirth) BirthDate <BirthDt> [1..1] DateTime Payer's birth date Used in case of SEPA payment CityOfBirth <CityOfBirth> [1..1] Max35Text Payer's city of birth Used in case of SEPA payment CountryOfBirth <CtryOfBirth> [1..1] CountryCode Payer's country of birth Used in case of SEPA payment Other <Othr> [1..2] Component For SEPA this element should be used only once {Or Identification SchemeName Code <Id> [1..1] Max35Text Beneficiary's id-code Customer s code in payer s information system In case of credit: Header 12 Body 20 In case of debit: Body 19 Body 20 <Cd> [1..1] ExternalOrganisationIdentification1Code In case of SEPA payment the following values are usable: ARNU AlienRegistrationNumber CCPT PassportNumber CUST CustomerIdentificationNumber DRLC DriversLicenseNumber EMPL EmployeeIdentificationNumber NIDN NationalIdentityNumber SOSE SocialSecurityNumber TXID TaxIdentificationNumber SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 18 of 41

19 CreditorAccount <CdtrAcct> [0..1] Component (CashAccount16) Identification <Id> [1..1] Choice component (AccountIdentification4Choice) {Or IBAN <IBAN> [1..1] IBAN2007Identifier Beneficiary s account number In case of credit: Header 17 In case of debit: Body 17 Or} Other <Othr> [1..1] Component (GenericAccountIdentification1) Identification <Id> [1..1] Max34Text Beneficiary s account number In case of credit: Header 17 In case of debit: Body SchemeName <SchmeNm> [0..1] Component (AccountSchemeName1Choice) Filled when CreditDebitIndicator is CRDT In other case creditor account = notification's account In case of SWIFT when IBAN is not used {Or Code <Cd> [1..1] ExternalAccountIdentification1Code In case beneficiary account is BBAN Or} Proprietary <Prtry> [1..1] Max35Text UltimateCreditor <UltmtCdtr> [0..1] Component (PartyIdentification32) Name <Nm> [0..1] Max140Text Name of beneficiary party Body Identification <Id> [0..1] Choice component (Party6Choice) {Or OrganisationIdentification <OrgId> [1..1] Component (OrganisationIdentification4) Other <Othr> [0..n] Component Identification <Id> [1..1] Max35Text Id-code of beneficiary party Body SchemeName Or}} <Prtry> [1..1] Max35Text Beneficiary party s account Proprietary number Or} PrivateIdentification <PrvtId> [1..1] Component (PersonIdentification5) Other <Othr> [0..n] Component Identification Body 24 <Id> [1..1] Max35Text Id-code of beneficiary party Body SchemeName Or}} <Prtry> [1..1] Max35Text Beneficiary party s account Proprietary number RelatedAgents <RltdAgts> [0..1] Component (TransactionAgents2) DebtorAgent <DbtrAgt> [0..1] Component (BranchAndFinancialInstitutionIdentification4) Body FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentification4) BIC <BIC> [1..1] BICIdentifier Name <Nm> [0..1] Max140Text PostalAddress <PstlAdr> [0..1] Component PostalAddress6) AddressLine <AdrLine> [0..7] Max70Text CreditorAgent <CdtrAgt> [0..1] Component (BranchAndFinancialInstitutionIdentification4) BIC of credit institution of account statement Name of credit institution of account statement Header 4 Header 5 Address of credit institution Header 7 Filled when CreditDebitIndicator is DBIT Filled when CreditDebitIndicator is DBIT Filled when CreditDebitIndicator is DBIT FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentification4) BIC <BIC> [1..1] BICIdentifier Name <Nm> [0..1] Max140Text PostalAddress <PstlAdr> [0..1] Component PostalAddress6) BIC of counterparty's credit institution Name of counterparty's credit institution Body 15 Body 16 Filled when CreditDebitIndicator is CRDT Filled when CreditDebitIndicator is CRDT SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 19 of 41

20 AddressLine <AdrLine> [0..7] Max70Text Purpose <Purp> [0..1] Choice component (Purpose2Choice) Address of counterparty's credit institution {Or Code <Cd> [1..1] Code Not yet used Or} ++++Proprietary <Prtry> [1..1] Max35Text RemittanceInformation <RmtInf> [0..1] Component (RemittanceInformation5) Unstructured <Ustrd> [0..n] Max140Text Payment description Body 14 Filled when CreditDebitIndicator is CRDT Usage: Purpose is used by the endcustomers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain Structured <Strd> [0..n] Component (StructuredRemittanceInformation7) Used only in case of SEPA payment CreditorReferenceInformation <CdtrRefInf> [0..1] Component (CreditorReferenceInformation2) Type <CdtrRefTp> [0..1] Component (CreditorReferenceType2) Code or Propietary <CdOrPrtry> [0..1] Choice component (CreditorReferenceType1Choice) {Or Code <Cd> [1..1] DocumentType3Code Issuer <Issr> [0..1] Max35Text Reference <Ref> [0..1] Max35Text Reference code Body RelatedDates <RltdDts> [0..1] Component (TransactionDates2) InterbankSettlementDate <IntrBkSttlmDt> [0..n] ISODateTime DISP DispatchAdvice FXDR ForeignExchangeDealRefer ence PU PurchaseOrder RADM RemittanceAdviceMessage RPIN RelatedPaymentInstruction SC StructuredCommunicationReference SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 20 of 41

21 Payments (ISO pain Custom credit Transfer Initiation) Index Or Message element <XML Tag> Mult Rules Type Message root <CstmrCdtTrfInitn> [1..1] GroupHeader <GrpHdr> [1..1] Component (GroupHeader32) MessageIdentification <MsgId> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime NumberOfTransactions <NbOfTxs> [1..1] Max15NumericText ControlSum <CtrlSum> [0..1] DecimalNumber InitiatingParty <InitgPty> [1..1] Component - (PartyIdentification32) +++Name <Nm> [0..1] Text Mokesis field # Taresis field # Domestic International SEPA Remarks 2 2 Date [C8] 6 Payer's name and surname / Name [C200] Date [C8] Payer's name and surname / Name Date Payer's name and surname / Name Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period. [1.1 MessageIdentification] and [2.29 InstructionIdentification] should be unique (new) for each subsequent attempt. Payment submission date and time Has to be checked against the amount of all CdtTrfTxInf instances in the message Usage: length of name if limited to 70 symbols ForwardingAgent <FwdgAgt> [0..1] Component (BranchAndFinancialInstitutionIdentification4) ++++FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentification4) ++++BIC <BIC> [0..1] BICIdentifier 2.0 +PaymentInformation <PmtInf> [1..n] Component (PaymentInstructionInformation3) PaymentInformationIdentification <PmtInfId> [1..1] Max35Text Unique Payment number Unique Payment number Unique Payment number The value of this element should be a 128 bit UUID number, represented as Base16 encoded string (i.e. without commonly used string formatting, containing - between blocks, as this type of representation would exceed 35 max characters limit). E.g. 6B29FC40CA471067B31D00DD010662DA Should be unique (new) for each subsequent attempt PaymentMethod <PmtMtd> [1..1] Code Usage: Only TRF is allowed Usage: if used and 'true" value is entered, all package is processed as one. If "false" is entered - each transaction must be processed separately. If not used, standard "client-bank" rule is applied. Default value is "false" BatchBooking <BtchBookg> [0..1] BatchBookingIndicator NumberOfTransactions <NbOfTxs> [0..1] Max15NumericText Has to be this checked against the amount of all CdtTrfTxInf instances in the PmtInf ControlSum <CtrlSum> [0..1] DecimalNumber Usage: if used, only usage on "Payment Information" level is recommended, and not on "Credit Transfer Transaction Information" level PaymentTypeInformation <PmtTpInf> [0..1] Component (PaymentTypeInformation19) ServiceLevel <SvcLvl> [0..1] Choice Component (ServiceLevel8Choice) 2.9 {Or ++++Code <Cd> [1..1] ExternalServiceLevel1Code CategoryPurpose <CtgyPurp> [0..1] Choice Component (CategoryPurpose1Choice) RequestedExecutionDate <ReqdExctnDt> [1..1] ISODate 4 4 Type of payment [N1] "NURG" = normal "URGP" - from discontinued, will be treated as "NURG" 3 3 Payment execution date [C8] Payment priority [N1] "NURG" = normal "URGP" = priority "SDVA" = extra urgent Payment execution date [C8] Payment priority [N1] value is "SEPA" only Payment execution date Specifies a pre-agreed service or level of service between the parties, Usage: see columns J-L for different payment types 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. 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 Debtor <Dbtr> [1..1] Component (PartyIdentification32) SEB Gateway: Duomenų apsikeitimo formato pagal ISO XML standarto pranešimus naudojimo taisyklės, v1.27 Page 21 of 41

camt BankToCustomerStatementV02

camt BankToCustomerStatementV02 Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.4 : 2018.11.26 2 of 10 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...

More information

camt BankToCustomerStatementV02

camt BankToCustomerStatementV02 Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.2 : 16-12-2013 2 of 7 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...

More information

XML message for Statement

XML message for Statement XML message for Statement Implementation Guidelines Version 2.0 Table of Contents 1. Introduction... 9 1.0. Scope... 9 1.1. General principles... 9 1.1.1. Contents of the message:... 9 1.1.2. Periodicity

More information

Swedbank AB (publ) Swedbank Sweden's MIG Credit and Debit Notification (CAMT.054)

Swedbank AB (publ) Swedbank Sweden's MIG Credit and Debit Notification (CAMT.054) Swedbank AB (publ) 2016-02-11 Swedbank Sweden's MIG Credit and Debit Notification (CAMT.054) Introduction This document describes the usage on a set of ISO20022 messages. The main target systems on the

More information

XML notification. Implementation Guidelines. Final Version 2.1 (changes in chapter 8.1)

XML notification. Implementation Guidelines. Final Version 2.1 (changes in chapter 8.1) XML notification Implementation Guidelines Final Version 2.1 (changes in chapter 8.1) Table of Contents 1 Introduction... 6 1.1 Scope... 6 1.2 General principles... 6 1.3 Use of these guidelines... 7 1.4

More information

pain CustomerDirectDebitInitiationV02 SEPA Direct Debit

pain CustomerDirectDebitInitiationV02 SEPA Direct Debit Message Implementation Guideline CustomerDirectDebitInitiationV02 SEPA Direct Debit MIG version: 1.0 : 27-02-2017 2017-02-27 2 of 18 Table of Contents 0. Document change history... 3 1. Introduction...

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 Corporate egateway Message Implementation Guideline camt.054.001.02 Debit Notification BankToCustomerDebitCreditNotificationV02 This Message Implementation Guide only includes description of Debit entries.

More information

Format Description CAMT and CAMT

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

More information

camt Account Statement Standard BankToCustomerStatementV02

camt Account Statement Standard BankToCustomerStatementV02 Corporate Access Account eporting Message Implementation Guidelines camt.053.001.02 Account Statement Standard BankToCustomerStatementV02 MIG version: 1.2 : This version is expected to be launched to the

More information

XML account report CAMT Service description April 2013

XML account report CAMT Service description April 2013 XML account report CAMT.052.001.02 Service description April 2013 Content 1 Purpose of the document... 2 2 Account report as an XML file... 2 2.1 Downloading of files... 2 3 Technical information... 2

More information

Usage rules of the SEB data exchange format based on ISO XML standard messages. Version 2.5 (effective from )

Usage rules of the SEB data exchange format based on ISO XML standard messages. Version 2.5 (effective from ) Usage rules of the SEB data exchange format based on ISO 20022 XML standard messages Version 2.5 (effective from 2017-11-19) Document version history Version Date Amendments 1.21 2013-09-19 Removed unused

More information

camt Account Statement BankToCustomerStatementV02

camt Account Statement BankToCustomerStatementV02 Corporate Access Account eporting Message Implementation Guidelines BankToCustomerStatementV02 MIG version: 1.00 : Corporate Access Account eporting version 1.0 2 of 10 Table of contents 1. Introduction...

More information

Record description XML File Transfer Foreign Payment Feedback camt

Record description XML File Transfer Foreign Payment Feedback camt Record description XML File Transfer Foreign Payment Feedback camt.054.001.02 15.11.2011 Page 2 of 14 Change date Version Changed 10.10.2011 1.0 7.12.2011 1.1 Added currency fields in 2.136 15.11.2012

More information

ING Format Description Transaction Details Camt InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS

ING Format Description Transaction Details Camt InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS ING Format Transaction Details Camt.054.001.02 InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS Document version history Version Date Changes 1.0 01-11-2016 First version 1.1 15-12-2016

More information

OP Corporate Bank plc Latvia Branch

OP Corporate Bank plc Latvia Branch OP Corporate Bank plc Latvia Branch Data exchange standard used in the Internet bank ISO 20022 September 2017 Content 1. Introduction... 3 2. Payment Initiation Message pain.001.001.03... 4 3. Account

More information

ING Format Description

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

More information

ISO XML message for Account Reports

ISO XML message for Account Reports ISO 20022 XML message for Account Reports Implementation Guideline Version 1.02 Estonia Version 1.02 Changes Updated 20131104 1. Introduction and message usage. Account Report (CAMT.052.001.02) can be

More information

pain CustomerPaymentReversalV02

pain CustomerPaymentReversalV02 Corporate egateway Message Implementation Guideline MIG version: 1.0 : 13-04-2015 2 of 7 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3 4. Services... 4 5. Use of references

More information

SEB MIG for ISO20022 camt.052, camt.053 and camt.054.

SEB MIG for ISO20022 camt.052, camt.053 and camt.054. SEB MIG for ISO20022 camt.052, camt.053 and camt.054. Version 1.0 Table of contents 1. Introduction... 3 2. Camt.053.001.02 Bank To Customer Statement... 4 3. Camt.052.001.02 Bank To Customer Account Report...

More information

SEB Estonia MIG for ISO20022 camt.053 and camt.054.

SEB Estonia MIG for ISO20022 camt.053 and camt.054. SEB Estonia MIG for ISO20022 camt.053 and camt.054. Version 1.01 Version 1.01 Changes Updated 20141031 1) Description of camt.052 is deleted. 2) Additional information is added to the field InstrId (in

More information

Format description Generic Payment File. Rabo Direct Connect & Rabo Internet banking (Professional)

Format description Generic Payment File. Rabo Direct Connect & Rabo Internet banking (Professional) Format description Generic Payment File Rabo Direct Connect & Rabo Internet banking (Professional) Contents 1 GENERAL... 3 1.1 GENERAL CHARACTERISTICS...3 1.2 STRUCTURE...3 1.2.1 Introduction...3 1.2.2

More information

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

Format Description CAMT.053 version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) Format Description CAMT.053 version 1.0 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) January 2018 Contents 1. CAMT.053 REPORTING EPORT FORMAT 3 1.1 CAMT.053 description 3

More information

OP-POHJOLA GROUP Customer instructions for XML account reporting of material obtained from the Web Services channel

OP-POHJOLA GROUP Customer instructions for XML account reporting of material obtained from the Web Services channel OP-POHJOLA GROUP Customer instructions for XML account reporting of material obtained from the Web Services channel Payment Transaction Services June 2014 OP-Services Ltd. All rights reserved. OP-SERVICES

More information

Format description XML SEPA DD. Rabo Direct Connect (RDC)

Format description XML SEPA DD. Rabo Direct Connect (RDC) Format description XML SEPA DD Rabo Direct Connect (RDC) Content 1 SEPA DD IMPORT FORMAT... 3 1.1 DESCRIPTION... 3 1.2 GENERAL CHARACTERISTICS... 3 1.3 SEPA DD STRUCTURE... 3 1.3.1 Introduction... 3 1.3.2

More information

XML message for Bank to Customer Statement (camt.053) Implementation Guidelines for the Netherlands

XML message for Bank to Customer Statement (camt.053) Implementation Guidelines for the Netherlands XML message for Bank to Customer Statement (camt.053) Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

More information

Format Description CAMT.052 version 1.0. Rabo Direct Connect, SWIFT FileAct en Rabo Internetbankieren (Professional)

Format Description CAMT.052 version 1.0. Rabo Direct Connect, SWIFT FileAct en Rabo Internetbankieren (Professional) Format Description CAMT.052 version 1.0 Rabo Direct Connect, SWIFT FileAct en Rabo Internetbankieren (Professional) Contents 1 CAMT.052 Exportformat 3 1.1 CAMT.052 description 3 1.2 CAMT.052 structure

More information

Credit Transfer. PAIN XML File Structure V 1.2

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

More information

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

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

More information

Format description CAMT.053 version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbanking (Professional)

Format description CAMT.053 version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbanking (Professional) Format description CAMT.053 version 1.0.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbanking (Professional) Contents 1. CAMT.053 REPORTING EPORT FORMAT 3 1.1 CAMT.053 description 3 1.2 CAMT.053

More information

ISO Cash Management

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

More information

SEPA Credit Transfer Unpaid Report File Format

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

More information

SCT Bulk Payments XML File Format

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

More information

ISO CustomerPaymentStatusReport Direct Debit

ISO CustomerPaymentStatusReport Direct Debit Implementation guide ISO 20022 CustomerPaymentStatusReport Direct Debit pain.002.001.03 Version 1.0.0 Publishing date 4 November 2013 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related

More information

ISO Message Implementation Guide for Payment Initiation pain

ISO Message Implementation Guide for Payment Initiation pain ISO 20022 Message Implementation Guide for Payment Initiation pain001.001.03 Credit Transfer PAIN.001.001.03 XML File Structure 1. Document Overview 1.1. Background 1.2. Document Purpose 2. The Character

More information

Document Overview. Credit Transfer PAIN XML File Structure. 1.1 Background. 1.2 Document Purpose. The Character Set.

Document Overview. Credit Transfer PAIN XML File Structure. 1.1 Background. 1.2 Document Purpose. The Character Set. ASOCIAȚIA ROMÂNĂ A BĂNCILOR Credit Transfer PAIN.001.001.03 XML File Structure Document Overview 1.1 Background 1.2 Document Purpose 2. 3. 4. 5. 6. 7. 8. 9. The Character Set Fields Types Usage Rules Unused

More information

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

More information

BankToCustomerDebitCreditNotificationV06_Debit

BankToCustomerDebitCreditNotificationV06_Debit BankToCustomerDebitCreditNotificationV06_Debit Bank to Corporate Messages Portfolio - Draft - January 31, 2017 This document describes a usage guideline restricting the base message MX camt.054.001.06.

More information

Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional)

Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional) Format description Generic Payment File version 1.8.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional) Contents 1 GENERAL... 3 1.1 GENERAL CHARACTERISTICS...3 1.2 STRUCTURE...3

More information

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

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

More information

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

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

More information

Message Usage Guideline

Message Usage Guideline Draft approved by the ISO 20022 RTPG Core Review Group Message Usage Guideline Modell: pacs.002.001.08 Version: 1.1 Issue Date: 19/07/2017 Author: ISO 20022 RTPG Core Review Group Contents History... 3

More information

Message Definition Report - Part 2

Message Definition Report - Part 2 ISO 20022 Stand-Alone Remittance Advice - Maintenance 2018-2019 Message Definition Report - Part 2 This document provides details of the Message Definitions for Stand-Alone Remittance Advice - Maintenance

More information

pain CustomerPaymentReversalV02 SEPA Direct Debit

pain CustomerPaymentReversalV02 SEPA Direct Debit Message Implementation Guideline CustomerPaymentReversalV02 SEPA Direct Debit MIG version: 1.0 : 23-04-2018 2 of 6 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3 4. Use

More information

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

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

More information

Message Definition Report

Message Definition Report Approved by the ISO 20022 RMG Message Definition Report Model: pacs.008.001.06 Version: 1.0 Issue Date: 15/04/2016 Author: ISO 20022 RTPG Contents History... 3 Introduction... 3 History Version Date Authors

More information

DRAFT for NO: camt Credit Notification BankToCustomerDebitCreditNotificationV02

DRAFT for NO: camt Credit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Account eporting Message Implementation Guidelines DAFT for NO: camt.054.001.02 redit Notification BankToustomerDebitreditNotificationV02 This Message Implementation Guide only includes

More information

SEPA Direct Debit. PAIN XML File Structure

SEPA Direct Debit. PAIN XML File Structure SEPA Direct Debit PAIN.008.001.02 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

UBS Implementation Guidelines

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

More information

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 Statement (camt.053) Bank-to-Customer Debit/Credit

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

Credit Suisse pain ch.02 - SIX v Swiss Recommendations for Credit Transfers Message Implementation Guidelines

Credit Suisse pain ch.02 - SIX v Swiss Recommendations for Credit Transfers Message Implementation Guidelines redit Suisse Version 2.0 Issue date: 25.01.2018 Ego vero valde afflictus sum redit Suisse pain.001.001.03.ch.02 - SIX v.1.7.2 Swiss Recommendations for redit Transfers Message Implementation Guidelines

More information

SEPA Direct Debit. PAIN XML File Structure

SEPA Direct Debit. PAIN XML File Structure SEPA Direct Debit PAIN.008.001.02 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

camt Account Statement Extended BankToCustomerStatementV02

camt Account Statement Extended BankToCustomerStatementV02 orporate Access Account eporting Message Implementation Guidelines camt.053.001.02 Account Statement Extended BankToustomerStatementV02 MIG version: 1.0 (DAFT) : This version is expected to be launched

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

Bank-to-Customer Cash Management Standards

Bank-to-Customer Cash Management Standards UNIFI (ISO 20022) Message Definition Report Bank-to-Customer Cash Management Standards Approved by UNIFI Payments SEG on 5 March 2007 Edition April 2007 Table Of Contents Overview... 1 Scope... 1 How to

More information

camt Credit Notification BankToCustomerDebitCreditNotificationV02

camt Credit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Account eporting Message Implementation Guidelines camt.054.001.02 redit Notification BankToustomerDebitreditNotificationV02 This Message Implementation Guideline includes description of

More information

Message Definition Report

Message Definition Report Message Definition Report 2010-06-01 Table Of Contents Overview... 1 Scope... 1 Deployment... 1 How to read... 1... 2 Message Functionality... 2 Structure... 2 Rules and Guidelines... 11 Message Items

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

WIRE TRANSACTION STATEMENT EXAMPLE. Version: 0.2 <November 2015 >

WIRE TRANSACTION STATEMENT EXAMPLE. Version: 0.2 <November 2015 > WIRE TRANSACTION STATEMENT EXAMPLE Version: 0.2 TrustPay provides Wire transaction statement from merchant account in XML format as CAMT.053.001.04 message (Bank-to-Customer-Statement)

More information

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

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

More information

Diegimo vedlys CAMT.053 išrašas

Diegimo vedlys CAMT.053 išrašas Diegimo vedlys CAMT.053 išrašas Versija: 1.0 Dokumento data: 2012.08.20 Pilnas formato aprašymas: http://www.iso20022.org/documents/general/b2c_camt_paymentsmaintenance2012.zip XML schema: XML schema:

More information

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

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

More information

Bankline SEPA Money Transfer XML pain

Bankline SEPA Money Transfer XML pain Bankline SEPA Money Transfer XML pain.001.001.03 This guide provides details of the formats and standards needed to generate a valid Bankline SEPA Money Transfer file Version 02.01 November 2017 Page 1

More information

Swiss Payment Standards 2018

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

More information

Bankline XML standard import format

Bankline XML standard import format Bankline XML standard import format Bankline XML standard import format Contents Introduction to Bankline XML import... 2 What is Bankline XML import?... 2 How do I structure a Bankline XML import format?...

More information

Format Specification

Format Specification Format Specification ISO20022-pain.002.001.03 mbank SA 2015.12.20 Version 1.3 1. General Info... 3 2. Short review... 3 3. Allowed characters / Coding... 3 4. References to codes and colors used in the

More information

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

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

More information

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

Swiss Payment Standards 2018

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

More information

Swiss Payment Standards 2018

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

More information

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

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

More information

Bankline SEPA Direct Debit Origination XML PAIN

Bankline SEPA Direct Debit Origination XML PAIN Bankline SEPA Direct Debit Origination XML PAIN.008.001.02 This guide provides details of the formats and standards needed to generate a valid Bankline SEPA Direct Debit Origination file in PAIN.008.001.02

More information

ISO TRANSACTION REPORTING GUIDE. v 1.3

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

More information

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

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

More information

Format Specification

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

More information

Customer Documentation Request For Payment Message (pain.013 & pain.014)

Customer Documentation Request For Payment Message (pain.013 & pain.014) Customer Documentation Request For Payment Message (pain.013 & pain.014) Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT").

More information

XML CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES Importing Payments in Commercial Banking Online Import your Payments Files in Commercial Banking Online In Commercial Banking Online

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines Swiss Recommendations for cash management reports camt.053.001.04 - SR Version 1.3 UBS Version 1.0 August 2016 UBS Implementation Guidelines Swiss Recommendations for cash

More information

pain CustomerPaymentStatusReportV03

pain CustomerPaymentStatusReportV03 Message Implementation Guideline CustomerPaymentStatusReportV03 MIG version: 1.0 : SEPA Direct Debit / CustomerPaymentStatusReportV03 2 of 9 Table of Contents 1. Introduction... 3 2. Nordea usage of ISO20022

More information

Prenosový formát pain v štruktúre XML

Prenosový formát pain v štruktúre XML Prenosový formát pain.001.001.03 v štruktúre XML Dokument obsahuje popis prenosového formátu pain.001.001.03 pre spracovanie SEPA príkazov na úhradu v aplikácii Internet banking prostredníctvom importu

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.6 US Version 1.0 January 2017 US Implementation Guidelines Swiss Recommendations for credit

More information

camt CustomerPaymentCancellationRequestV01

camt CustomerPaymentCancellationRequestV01 Corporate Access Payables Message Implementation Guidelines camt.055.001.01 CustomerPaymentCancellationequestV01 MIG version: 1.0 : 2 of 9 Table of contents 1. Introduction... 3 2. About Corporate Access

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines Swiss Payment Standards for credit transfers pain.001.001.03.ch.02 - SPS Version 1.8 US Version 1.0 September 2018 Table of ontents 1. redit Transfer message 3 1.1 Scope of

More information

Customer Payment Status Report pain Swedish Interpretation

Customer Payment Status Report pain Swedish Interpretation Customer Payment Status eport pain.002.001.03 Swedish Interpretation ISO Or Message Item ULES Status COMMENT Status COMMENT 0.0 Customer Payment Status eport 1.0 GroupHeader 1.1 MessageIdentification 1.2

More information

STET PSD2 API. Documentation. Author: Robache Hervé. Date: Version: (English)

STET PSD2 API. Documentation. Author: Robache Hervé. Date: Version: (English) STET PSD2 API Documentation Author: Robache Hervé Date: 2017-11-15 Version: 1.2.3 (English) Table of content 1. INTRODUCTION... 7 1.1. Context... 7 1.2. Mission... 7 1.3. Licence... 8 2. BUSINESS MODEL...

More information

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 017 USAGE GUIDELINES FOR ISO AFT MESSAGE FORMATS

CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 017 USAGE GUIDELINES FOR ISO AFT MESSAGE FORMATS CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS STANDARD 017 USAGE GUIDELINES FOR ISO 20022 AFT MESSAGE FORMATS PART D (of 5) PAYMENT REVERSAL 2016 CANADIAN PAYMENTS ASSOCIATION 2016

More information

Message Definition Report - Part 2

Message Definition Report - Part 2 ISO 20022 Target2-Securities - Administration message set Message Definition Report - Part 2 For Final Review by the T2S Evaluation Team. This document provides details of the Message Definitions for Target2-Securities

More information

Format description PAIN.002. Rabo Internetbanking Professional (RIB Pro), Rabo Direct Connect (RDC) and SWIFT FileAct

Format description PAIN.002. Rabo Internetbanking Professional (RIB Pro), Rabo Direct Connect (RDC) and SWIFT FileAct Format description PAIN.002 Rabo Internetbanking Professional (RIB Pro), Rabo Direct Connect (RDC) and SWIFT FileAct k Contents 1. PAIN.002 STATUS EXPORTFORMAT 3 2. PAIN.002 SCENARIOS 11 APPENDIX 1: EXPORT

More information

MT940 to CAMT.053 Mapping

MT940 to CAMT.053 Mapping to Mapping Description of the SEPA reporting format ABN-Amro Clearing Bank January 2014 Document version: 0.04 Table of Contents General Layout... 2 General Identifiers... 2 Transaction Reference Number...2

More information

PSD2 API INTERFACE SPECIFICATION

PSD2 API INTERFACE SPECIFICATION PSD2 API INTERFACE SPECIFICATION CONTENTS Contents... 2 List of figures... 3 List of tables... 3 Document information... 4 List of acronyms... 5 References... 6 1 Introduction... 7 1.1 Main focus... 7

More information

XML CONVERTING LLOYDSLINK BACS XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK BACS XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK BACS XML FILES Importing Payments in Commercial Banking Online Import your Payments Files in Commercial Banking Online In Commercial Banking Online all Payment Files must be

More information

ISO CustomerPaymentStatusReport Confirmation of Receipt

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

More information

SEPA XML PAYMENTS ISO FILE FORMAT pain.001 via ALPHA WEB BANKING. OPERATIONAL and TECHNICAL SPECIFICATIONS

SEPA XML PAYMENTS ISO FILE FORMAT pain.001 via ALPHA WEB BANKING. OPERATIONAL and TECHNICAL SPECIFICATIONS PAYMENTS SEPA XML FILE FRMAT VIA ALPHA WEB BANKING SEPA XML PAYMENTS IS 20022 FILE FRMAT pain.001 via ALPHA WEB BANKING PERATINAL and TECHNICAL SPECIFICATINS VERSIN 1.3 1 PAYMENTS SEPA XML FILE FRMAT VIA

More information

pain CustomerPaymentStatusReportV03

pain CustomerPaymentStatusReportV03 Corporate egateway Message Implementation Guideline pain.002.001.03 CustomerPaymentStatusReportV03 MIG version: 1.3 : 01-10-2018 2 of 5 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

Message Definition Report - Part 2

Message Definition Report - Part 2 ISO 20022 Exceptions and Investigations - Maintenance 2018-2019 Message Definition Report - Part 2 Maintenance 2018/2019 - For evaluation by the Payments SEG This document provides details of the Message

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines ommon Global Implementation (GI) for credit transfers pain.001.001.03 US Version 1.1 September 2018 Table of ontents 1. redit Transfer message 3 1.1 Scope of application of

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines DFÜ greement of Deutsche Kreditwirtschaft for SEP redit Transfer Initiation pain.001.001.03 - DK Version 3.1 US Version 1.0 pril 2018 US Implementation Guidelines DFÜ greement

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines DFÜ greement of Deutsche Kreditwirtschaft for SEP redit Transfer Initiation pain.001.001.03 - DK Version 3.0 US Version 1.0 January 2017 US Implementation Guidelines DFÜ greement

More information

XML CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES Importing Payments in Commercial Banking Online Import your Payment Files in Commercial Banking Online In Commercial Banking Online all Payment Files

More information

Accounts Service - SMBC NextGenPSD2

Accounts Service - SMBC NextGenPSD2 Accounts Service - SMBC NextGenPSD2 1.3.SMBC February 2019 Framework (Berlin Group V1.3) Summary OAS3 SMBC offers third party access to accounts (XS2A) in a safe and efficient way using Application Programming

More information