DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES
|
|
|
- Dorthy Fisher
- 9 years ago
- Views:
Transcription
1 DESCRIPTIN F SEPA XML FRMAT FR ING BUSINESSNLINE IMPRT AND EXPRT TEMPLATES
2 TABLE F CNTENTS Import of orders 3 1. Introduction Notation File structure Batching rules Differentiation rules for file orders 5 2. File format Group Header Block Payment Information and Transaction Information Blocks 8 Data export Bank statement export format (xml) based on the message camt History of operations export format (xml) based on the message camt EXAMPLES Domestic orders account in BBAN format Domestic orders account in IBAN format Tax ffice orders Social Insurance Institution order MT101 CRED order MT101 DEBT order MT101 SHAR order Payroll batch Simple batch SEPA order Foreign order high Foreign order norm 47 2
3 IMPRT F RDERS 1. Introduction The Import of orders template in the SEPA XML format is a predefined template used by various orders. It supports the following payments: Domestic Payments, Domestic Payments to the Social Insurance Institution, Domestic Payments to the Tax ffice, Internal Payments, European Payments, Foreign Payments, and MT101. Import template complies with the pain format as per IS20022 standard. 1.1 Notation Element name in the table XML element Status Description Defines the XML element name. Label names from the IS20022 standard are used; when not available, names are assigned by the bank. Nesting shown with + characters M mandatory field optional field C conditional field Format n numbers allowed only (0-9) IS Date IS DateAndTime a capital letters allowed only (A-Z) x any character c capital letters and number allowed only (A-Z), (0-9) d digital number! fixed length [ ] optional value YYYY-MM-DD YYYY-MM-DDThh:mm:ss The following characters can be used in the order: - small and capital letters, - numbers, - special characters: / -? : ( )., + space. For SEPA CT -like messages only small and capital letters from the Latin alphabet can be used. The fields in domestic orders cannot contain the characters: The fields in other orders cannot contain the characters: * ;! # 3
4 1.2 File structure verall file structure is as follows: Group Header - mandatory block, - occurs only once, - contains the message header, composed of the date and unique identifier. The header is shared by all orders. - It contains the name of the batch for all Payment Information blocks. Payment Information - mandatory block, - can occur many times, - contains transactions under the payment from one debited account. When it is more than one transaction, a batch is created in the system (a simple batch all debits from the same account). When many Payment Information blocks were given, one common batch is created. Conditional on the account debited, it can be a simple or standard batch. Transaction Information - mandatory block, - it can occur many times under one block of Payment Information type, - it contains data of the other transaction party. When the PaymentTypeInformation block was given at the PaymentInformation level and at the TransactionInformation level, then the TransactionInformation block has a higher priority. 1.3 Batching rules Batching rules: ne import file is used to create one batch. Batch name is defined in the Group Header, in the field: MsgID. When many Payment Information blocks were given, they are combined into one batch. 4
5 When all orders in individual Payment Information blocks satisfy the terms and conditions of a simple batch and additionally each order has the STRAIGHT value in the InstrForDbtrAgt field, all such orders are combined into one simple batch. When at least one of the orders does not satisfy the terms and conditions of a simple batch (e.g. different currency, transaction type or different number of the account debited in the PaymentInformation block) a standard batch is created. Batches with a mix of domestic and foreign orders can also be created. 1.4 Differentiation rules for file orders Differentiation rules for file orders rder type Domestic orders Rule Domestic: transfer currency PLN and account debited in PLN and account credited maintained at a bank in Poland. Foreign orders Bank code given in one of the fields +++CdtrAgt ++++FinInstnId +++++ClrSysMmbId ClrSysId Cd MmbId or +++CdtrAgt ++++FinInstnId +++++BIC (group 1) transfer in PLN to foreign banks (group 2) transfer in the currency other than PLN to domestic banks (ING BSK included) and foreign banks Bank code in the field +++CdtrAgt ++++FinInstnId +++++BIC Note! BIC field cannot be left empty. When there is no code in the MmbId field or when the bank code was not specified but the bank address was given, the transfer should be considered as foreign transfer. 5
6 SEPA orders The SEPA constant value is required in the tag. ++PmtTpInf +++SvcLvl ++++Cd r rders to Social Insurance Institution rders to Tax ffice +++PmtTpInf ++++SvcLvl +++++Cd Domestic transfer and additionally SSBE value in the field +++ PmtTpInf ++++CtgyPurp +++++Cd Domestic transfer and additionally Internal transfers TAXS value in the field +++ PmtTpInf ++++CtgyPurp +++++Cd Domestic transfer and additionally INTC value in the field +++ PmtTpInf ++++CtgyPurp +++++Cd Note! When a transfer is made between the accounts of one client it is treated by ING BusinessnLine as an internal transfer. When a transfer is made between the accounts of various clients, it is a domestic transfer. 6
7 2. File format 2.1 Group Header Block GrpHdr Header Field name XML element name Status Format Remarks Message identifier Message creation date and time Number of message orders Checksum rder initiator Sender identifier +GrpHdr ++MsgId +GrpHdr ++CreDtTm +GrpHdr ++NbfTxs +GrpHdr ++CtrlSum +GrpHdr ++InitgPty +++Nm +GrpHdr ++InitgPty +++Id ++++rgid +++++thr Id M 35x Unique for a given sender. M M IS DateAn dtime 15d For the messages with transfers, the message identifier value is used to check the status of transfers sent. The identifiers of the messages sent by one client have to be unique (they cannot be repeated). An error will be reported for repeated identifiers. Message identifier is saved as used only when the message was correct and the message-based transfers were saved. They are used to name the batch. The total value of all batch orders, regardless of the order currency. Soft validation checking that the same file has not been imported yet. When the user has imported the file and tries to upload the same file (the checksum is remembered), a popup will appear on the screen: The file has already been imported. Do you want to re-import it? and the user will be able to choose K/ Cancel. M 70x A sequence allowing identification of the order author in the ERP system. 35x Client identifier 7
8 2.2 Payment Information and Transaction Information Blocks PmtInf Payments Block This block contains a list of payments for one debited account. Field name XML element name Status Format Remarks Name of batch of transfers Payment method Mass orders mark Number of transactions in the batch Batch checksum Payment type code (Payment Type Information Service Level Code) Target execution category Execution date Sender name Sender address +Id ++PmtMtd ++BtchBookg ++NbfTxs ++CtrlSum ++PmtTpInf +++SvcLvl ++++Cd ++CtgyPurp ++ReqdExctnDt ++Dbtr +++Nm ++Dbtr +++PstlAdr ++++AdrLine 35x In accordance with RBE: References assigned by the sender M 3!a Constant value M IS Date unique identifier of information block in the message. TRF False standard orders (debit per transaction). True orders booked under one transaction. This type of orders is not processed now. When no value has been given, false should be taken. Number of transactions in one batch, that is under one PmtInf tag. The field is not mandatory. The user may approve the batch only. Total number of transactions in one batch, that is under one PmtInf tag. The field is not mandatory. The user may approve the batch only. The field is mandatory for SEPA transfers for which SEPA is an acceptable value. The field is not used. M 70x rder initiator name. 70x Maximum number of occurrences = 2; Total length of both fields cannot be over 70 characters. 8
9 Field name XML element name Status Format Remarks Sender country code Sender account IBAN ++Dbtr +++PstlAdr ++++Ctry ++DbtrAcct +++Id ++++IBAN C 2!a Country code in line with IS C The field is mandatory when the AdrLine field was added. IBAN format is mandatory for SEPA and foreign transfers. Sender account BBAN Domestic identifier of the sender bank Sender bank s BIC Fee settlement Account for BBAN fees ++DbtrAcct +++Id ++++thr +++++Id ++DbtrAgt +++FinInstnId ++++ClrSysMmbId +++++MmbId ++DbtrAgt +++FinInstnId ++++BIC ++ChrgBr ++ChrgsAcct +++Id ++++thr +++++Id C 26!n Account in the BBAN standard. C 8!n Bank s clearing number. C 4!a2!a2! c[3!c] Sender bank s BIC. BIC mandatory for SEPA transfers. Should be given for foreign transfers when available. 4!a Acceptable values: C CRED fee paid by the counterparty DEBT fee paid by the sender SHAR shared fee SLEV fee accrued in line with bank s arrangements Completion rules: Domestic transfers ignored field SEPA transfer fill in the SLEV value Foreign transfer fill in one of the values: CRED, DEBT or SHAR. Account in the BBAN format. The field is mandatory when the ChrgBr field was filled in. 9
10 Field name XML element name Status Format Remarks Account for IBAN fees ++ChrgsAcct +++Id ++++IBAN C Account in the IBAN format. The field is mandatory when the ChrgBr field was filled in. IBAN format should be used for SEPA and foreign orders. Data of single CdtTrfTxInf payment Field name XML element name Status Format Remarks Reference Clearing channel identifier +++PmtId ++++EndToEndId +++PmtTpInf ++++SvcLvl +++++Cd M 35x The field is mandatory under the standard when not provided by the bank client, the ERP System has to fill it in with the not provided value. C 4!a Note! When the value is not provided, the transaction type is defined with the tag ++SvcLvl +++Cd defined per the entire PaymentInfo batch. Field used for domestic transfers. For SRBNET transactions a constant value RTGS. For ELIXIR transactions field forbidden. Field ignored for internal orders. Foreign transfer field not interpreted for NRM values in the order priority. For HIGH values possible values are: PRPT for urgent mode tomorrow SDVA for express mode today. 10
11 Field name XML element name Status Format Remarks rder priority +++PmtTpInf ++++InstrPrty 4!a IS admits the following codes: HIGH NRM Putting the NRM value in the field or absence of that field the transfer will be treated as so far. Putting the HIGH value in the field the transfer will be validated and there will be an attempt made to send it via ExpressElixir. rder category +++ PmtTpInf ++++CtgyPurp +++++Cd Field ignored for internal orders. C 4!a Acceptable codes are the following: TAXS for orders to the Tax ffice SSBE for orders to the Social Insurance Institution INTC for intrabank orders CASH for cash deposit. Field forbidden for other order types. Transfer amount +++Amt ++++InstdAmt M 3!a 18d Currency code compliant with IS Amount in the brackets from 0.01 to 999,999,999,999, Identifier of the intermediary bank +++IntrmyAgt1 C For foreign transfers only. ++++FinInstnId +++++ClrSysMmbId ClrSysId Cd MmbId BIC of the intermediary bank +++IntrmyAgt1 C For foreign transfers only. ++++FinInstnId +++++BIC Name of the intermediary bank +++IntrmyAgt1 For foreign transfers only. ++++FinInstnId +++++Nm 11
12 Field name XML element name Status Format Remarks Address of the counterparty bank Identifier of the counterparty bank BIC of the counterparty bank Counterparty bank name Address of the counterparty bank Counterparty name +++IntrmyAgt1 ++++FinInstnId +++++PstlAdr +++CdtrAgt ++++FinInstnId +++++ClrSysMmbId ClrSysId Cd MmbId +++CdtrAgt ++++FinInstnId +++++BIC +++CdtrAgt ++++FinInstnId +++++Nm +++CdtrAgt ++++FinInstnId +++++PstlAdr +++Cdtr ++++Nm For foreign transfers only. Fill in <Ctry> and two lines at maximum from <AdrLine>. C 8!n Counterparty bank s clearing number. C C M 4!a2!a2! c[3!c] 70x BIC of the counterparty bank the field is mandatory for SEPA transfers. For foreign transfers provide the correct BIC or enter the full name and address of the beneficiary bank. In the absence of BIC, ING Bank will process the order in the NN STP mode and will charge the Client s bank account with extra fees (the socalled NN STP fee) under the Table of Fees and Commissions and those charged by the beneficiary bank. Bank name for foreign transfers. Name optional when BIC was provided. The name is mandatory when BIC was not provided. Fill in the field for foreign transfers when BIC was not provided. Fill in the country <Ctry> and address (two lines at maximum from <AdrLine>). 12
13 Field name XML element name Status Format Remarks Counterparty address Counterparty country Country of residence (stay) for the person Counterparty account in the BBAN format Counterparty account in the IBAN format Tax (the field is mandatory for orders to the Tax ffice and the Social Insurance Institution) +++Cdtr +++PstlAdr ++++AdrLine +++Cdtr ++++PstlAdr +++++Ctry +++Cdtr ++++CtryfRes +++CdtrAcct ++++Id +++++thr Id +++CdtrAcct ++++Id +++++IBAN +++Tax ++++Dbtr ++++TaxId ++++RegnId ++++Rcrd +++++Tp +++++FrmsCd 70x Maximum number of occurrences = 2; Total length of both fields cannot be over 70 characters. C 2!a The field is mandatory when the AdrLine field is present. 2!a When PL or when the field is absent, we assume that it is a resident; a non-resident otherwise. C 26!n Account in the BBAN format for domestic transfers or foreign transfers when IBAN is unavailable. M 2!a2!n3 0c For SEPA transfers, give the account in the IBAN format. For foreign or domestic transfers, IBAN is recommended. C The field is mandatory for orders to the Tax ffice and the Social Insurance Institution. Field structure is described in the following tables. 13
14 Field name XML element name Status Format Remarks Additional information for the sender bank rder title non-structural rder title structural +++InstrForDbtrAgt +++RmtInf ++++Ustrd +++RmtInf ++++Strd +++++RfrdDocInf RfrdDocNb +++++AddtlRmtInf 140x When a batch of orders is sent, conditional on the bank and the type of the batch sent, the field can contain batch type tags, separated with commas: PAYMENT payroll batch PAYMENT_ADMISSIN payroll batch with credit amount STRAIGHT simple batch. Absence of any of the above labelling means that the batch is a standard batch. When the bank so admits and when the field has the SEND value set for all transactions in the batch, orders will be sent automatically after the approval flow rules have been met. therwise, the batch will not be sent even if the approval flow rules have been met. When a given bank does not support a given value, an error is returned. C 140x The field can appear only once. C The field forbidden for orders to the Social Insurance Institution. Field earmarked for transactions to the Social Insurance Institution. RfrdDocNb deposit type, declaration, declaration number. AddtlRmtInf Number of the decision/ agreement/ writ of execution. TAX field content for payments to the Social Insurance Institution Field name XML element name Status Format Remarks Debtor tax identifier Details of the debtor making the payment +++Tax ++++Dbtr +++++TaxId +++Tax ++++Dbtr 35x In this field we always give the Tax Identification Number of the debtor. 14
15 Field name XML element name Status Format Remarks Debtor tax identifier no. 2 Description of the payment type Additional information +++Tax ++++Dbtr +++++RegnId +++Tax ++++Rcrd +++++Tp +++Tax ++++Rcrd +++++AddtlInf 1!x34x 35x 140x E.g. 1ABV , where the first symbol in the field shows the type of identifier used: R REGN (Statistical Identification Number) P PESEL (Personal Identification Number) 1 ID card 2 Passport Subsequent 34 characters include the serial number of the identifier. The field contains the following data: deposit type, declaration, declaration number. The field contains the following data: Number of the decision/ agreement/ writ of execution. TAX field content for payments to the Tax ffice Field name XML element name Status Format Remarks Debtor identifier Description of the payment type +++Tax ++++Dbtr +++++RegnId +++Tax ++++Rcrd +++++Tp 1!x34x 35x E.g. 1ABV , where the first symbol in the field shows the type of identifier used: N NIP (Tax Identification Number) R REGN (Statistical Identification Number) P PESEL (Personal Identification Number) 1 ID card 2 Passport 3 other identifier type Subsequent 34 characters include the serial number of the identifier. Here we enter the period (year, period type and number). 15
16 Field name XML element name Status Format Remarks Form type Additional information +++Tax ++++Rcrd +++++FrmsCd +++Tax ++++Rcrd +++++AddtlInf 35x Here we enter the form type. 140x Liability specification (document type, for example: a decision, writ of execution, ruling). 16
17 DATA EXPRT 1. Bank statement export format (xml) based on the message camt Field name XML element name Status Format Remarks Message identifier Creation date and time Page number Last page mark Bank statement +GrpHdr ++MsgId +GrpHdr ++CreDtTm +GrpHdr ++MsgPgntn +++PgNb +GrpHdr ++MsgPgntn +++LastPgInd Bank statement fields 35x Bank statement number. Unique for a given beneficiary. M IS DateAn dtime Cannot have spaces. 5d The field is mandatory when the bank statement has a few pages. For SWIFT statements, this field returns the latter part from field 28C. The field is mandatory when the bank statement has a few pages. Acceptable values: Yes for the last page No when other pages follow. The structure with the bank statement (the message can contain many or zero bank statements). Bank statement number SWIFT statement number Creation date and time Statement date from Statement date to ++Id <> +<Stmt> ++<ElctrncSeqNb> ++CreDtTm ++FrToDt +++FrDtTm ++FrToDt +++ToDtTm M 35x Bank statement identifier M M M M IS DateAn dtime IS DateAn dtime IS DateAn dtime For SWIFT statement it is the field: 20 and it contains the statement reference number. The field is mandatory for SWIFT statements. It is not present for standard bank statements. For SWIFT statement it is the field: 28C. Statement creation date and time. 17
18 Account number Account number Account currency Account name Name of the account holder Address of the account holder Country code for the account holder ++Acct +++Id ++++IBAN ++Acct +++Id ++++thr +++++Id ++Acct +++Ccy ++Acct +++Nm ++Acct +++wnr ++++Nm ++Acct +++wnr ++++PstlAdr +++++AdrLine ++Acct +++wnr ++++PstlAdr +++++Ctry C 2!a26!d Account number in the IBAN format. C For SWIFT statement it is the field: 25: when the account is in the IBAN format. Account number in the non-iban format. Field used for SWIFT statements. For SWIFT statement it is the field: 25: when the account is in the IBAN format. 3!a IS code for account currency. M 70x 70x 70x This field can occur twice at maximum. C 2!a The field is mandatory when the address of the account holder was given <AddrLine>. 18
19 Balance code Balance amount and currency Balance mark Balance date Additional information Bank statement item ++Bal +++Tp ++++CdrPtry +++++Cd ++Bal +++Amt ++Bal +++CdtDbtInd ++Bal +++Dt ++++Dt ++AddtlStmtInf ++Ntry Bank statement fields (inside the Ntry tag): M 4!a Balance code: M 3!a18d PBD opening balance CLBD closing balance For SWIFT statements the field (along with the entire Bal tag) can occur many times and contain: PRCD opening balance (field 60a) CLBD closing balance (field 62a) CLAV available closing balance field 64 FWAV forecasted available balance field 65 M 4!a Acceptable values: M IS Date 500x CRDT for the balance 0 DBIT for the balance < 0 Bank statement starting date for the opening balance. Bank statement end date for the closing balance. Can occur 0 or many times. Item amount ++Ntry +++Amt M 3!a18d It is mandatory to enter the IS code for the currency. For SWIFT statement, in this tag the sub-field 5 from the field 61 is given. 19
20 Position mark Transaction reversal Item status Booking date peration date Banking operation code ++Ntry +++CdtDbtInd <> +<Stmt> ++<Ntry> +++<RvslInd> ++Ntry +++Sts ++Ntry +++BookgDt ++++Dt ++Ntry +++ValDt ++++Dt ++Ntry +++BkTxCd ++++Domn +++++Cd M 4!a Acceptable values: CRDT for the amount 0 DBIT for the amount < 0. For SWIFT statements, this is mapped onto the sub-field 3 from the field 61, respectively: CRDT when the sub-field 3 contains C DBIT when the sub-field 3 contains D. Field earmarked for SWIFT statements for reversal transactions. Acceptable values: True if the sub-field 3 of the field 61 contains RC or RD False if the sub-field 3 of the field 61 contains C or D. This tag maps the sub-field 3 from the field 61. M 4!a Constant value: BK M M IS Date IS Date For SWIFT statements, this field contains the ValueDate input date in the YYYYMMDD format (it is the subfield 2 from the field 61). For SWIFT statements, this field contains the ValueDate in the YYYYMMDD format (it is the subfield 1 from the field 61). M 4x Field earmarked for standard operation codes. E.g For SWIFT statements, this field contains the transaction type code returned in the field 61 (sub-field 6). 20
21 Extended operation code Extended operation subcode Sent order amount and currency Instruction identifier peration reference rder identifier ++Ntry +++BkTxCd ++++Domn +++++Fmly Cd ++Ntry +++BkTxCd ++++Domn +++++Fmly SubFmlyCd ++Ntry +++AmtDtls ++++InstdAmt ++Ntry +++NtryDtls ++++TxDtls +++++Refs InstrId ++Ntry +++NtryDtls ++++TxDtls +++++Refs EndToEndId ++Ntry +++NtryDtls ++++TxDtls +++++Refs TxId 4x Banking booking code PSTellerTC20. 4x Constant value. 3!a 18d 35x M 35x Client reference. M 35x For SWIFT transfers, it is the subfield 7 from the field
22 Sender data Sender account Name of the initial sender Counterparty Counterparty account Ultimate beneficiary ++Ntry +++NtryDtls ++++TxDtls +++++RltdPties Dbtr ++Ntry +++NtryDtls ++++TxDtls +++++RltdPties DbtrAcct ++Ntry +++TxDtls ++++RltdPties +++++UltmtDbtr Nm ++Ntry +++NtryDtls ++++TxDtls +++++RltdPties Cdtr ++Ntry +++NtryDtls ++++TxDtls +++++RltdPties CdtrAcct ++Ntry +++TxDtls ++++RltdPties +++++UltmtCdtr Nm For credit operations (crediting the account). 70x 70x Tag details are in the following table. For credit operations (crediting the account). Account can be in the IBAN format. <Id> +<IBAN> or another format <Id> +<thr> ++<Id> For debit operations (tag details are in the following table). For debit operations Account can be in the IBAN format <Id> +<IBAN> or another format <Id> +<thr> ++<Id> 22
23 Transfer title structural Transfer title non-structural Additional SWIFT information Additional information for the account holder Reference number of the bank maintaining the account ++Ntry +++TxDtls ++++RmtInf +++++Strd ++Ntry +++NtryDtls ++++TxDtls +++++RmtInf Ustrd <> +<Stmt> ++<Ntry> +++<TxDtls> ++++<AddtlTxInf> +<Stmt> ++<Ntry> +++<AddtlNtryInf> <> +<Stmt> ++<Ntry> +++<AcctSvcrRef> Fields for the sender and counterparty (Dbtr, Cdtr) C 140x peration title (non-structural). 500x This field contains additional information from the field 61 (subfield 9) of the SWIFT statement. 500x Field earmarked for the content of the field 86 from the SWIFT message. 35A Field earmarked for the reference number assigned by the bank maintaining the account and forwarded as standard in the field 61 (sub-field 8) of the SWIFT statement. Sender/counterp arty name Sender/counterp arty address Sender/counterp arty country +Nm M 70x +PstlAdr ++AdrLine +PstlAdr ++Ctry 70x This field can occur twice at maximum. C 2!a It is a mandatory field when the <AdrLine> address was used. The country is returned only for the sender for outgoing orders and for the counterparty for incoming orders. For the other party PL is always returned. 23
24 2. History of operations export format (xml) based on the message camt Field name XML element name Statu s Message identifier Creation date and time Page number Message identifier Creation date and time Starting date and time for the history End date and time for the history SWIFT statement number BkToCstmrAcctRpt +GrpHdr ++MsgId BkToCstmrAcctRpt +GrpHdr ++CreDtTm <BkToCstmrAcctRpt> +<GrpHdr> ++<MsgPgntn> BkToCstmrAcctRpt +Rpt ++Id BkToCstmrAcctRpt +Rpt ++CreDtTm BkToCstmrAcctRpt +Rpt ++FrToDt +++FrDtTm BkToCstmrAcctRpt +Rpt ++FrToDt +++ToDtTm <BkToCstmrAcctRpt> + <Rpt> ++<ElctrncSeqNb> Format Remarks 35x Unique for a given beneficiary. Cannot have spaces. M IS DateAnd Time 5d The field is mandatory when the bank statement has a few pages. For SWIFT statements, this field returns the latter part from the field 28C. M 35x It is the identifier from the header. M M M M IS DateAnd Time IS DateAnd Time IS DateAnd Time For history of SWIFT operations it is the field 20. It is the date from the header. For history of SWIFT operations it is the field 13D. nly the date is important, the time is always set as 00:00. nly the date is important, the time is always set as 00:00. The field is mandatory for SWIFT statements. It is not present for standard bank statements. Account number BkToCstmrAcctRpt +Rpt ++Acct +++Id ++++IBAN For SWIFT statement it is the field 28C. M 2!a26!n Account number in the IBAN format. For history of SWIFT operations it is the field
25 Field name XML element name Statu s Account name Name of the account holder Country code for the account holder Address of the account holder Balance code Balance amount and currency Balance mark Balance date BkToCstmrAcctRpt +Rpt ++Acct +++Nm BkToCstmrAcctRpt +Rpt ++Acct +++wnr ++++Nm BkToCstmrAcctRpt +Rpt ++Acct +++wnr ++++PstlAdr +++++Ctry BkToCstmrAcctRpt +Rpt ++Acct +++wnr ++++PstlAdr +++++AdrLine BkToCstmrAcctRpt +Rpt ++Bal +++Tp ++++Cd BkToCstmrAcctRpt +Rpt ++Bal +++Amt BkToCstmrAcctRpt +Rpt ++Bal +++CdtDbtInd BkToCstmrAcctRpt +Rpt ++Bal +++Dt ++++Dt Format Remarks 70x Account name (alias). M 70x The name of the holder assigned to the account is returned, when the name was not defined the business name is returned. 2!a Country code for the business account holder. This element is present only when the Address of the account holder is returned. 70x This field can occur twice at maximum (in that manner 70 characters in total can be obtained). 4!a Balance code: 3!a 18d The address of the business assigned to the account is returned, when the business was not defined the business address is returned. PBD opening balance CLBD closing balance 4!a Acceptable values: IS Date CRDT for the balance 0 DBIT for the balance < 0 25
26 Field name XML element name Statu s Number and total of transactions Additional information History item <BkToCstmrAcctRpt> + <Rpt> ++<TxsSummry> +++<TtlDbtNtries> ++++<TtlDbtNtries> ++++<Sum> BkToCstmrAcctRpt +Rpt ++AddtlRptInf BkToCstmrAcctRpt +Rpt ++Ntry Fields in the history item (inside the <Ntry> tag) Format 500x Item amount +Amt M 3!a Remarks Field earmarked for history of SWIFT operations. In this tag the fields 90C (credit) and 90D (debit) are returned. Can occur 0 or many times. 18d peration amount and currency. It is mandatory to enter the IS code for the currency as well. Position mark +CdtDbtInd M 4!a Acceptable values: CRDT for the amount 0 DBIT for the amount < 0. Transaction reversal <> +<Stmt> ++<Ntry> +++<RvslInd> For history of SWIFT operations it is the field 61, sub-field 3. 1x Field earmarked for SWIFT statements for reversal transactions. Acceptable values: True if the sub-field 3 of the field 61 contains RC or RD False if the sub-field 3 of the field 61 contains C or D. This tag maps the sub-field 3 from the field 61. Item status +Sts M 4!a Conditional on the bank possible values are: BK, PDNG and INF. Booking date +BookgDt ++DtTm M IS DateAn dtime When a given bank does not support a given value, an error is returned. When there is no booking hour, it will be returned as 00:00. For history of SWIFT operations it is the field 61, sub-field 2. 26
27 Field name XML element name Statu s peration date +ValDt ++DtTm M Format IS DateAn dtime Remarks When there is no operation hour, it will be returned as 00:00. Banking operation code Extended operation code Extended operation subcode Sent order amount and currency Number of intraday transactions Instruction identifier peration reference rder identifier peration reference +BkTxCd ++Domn +++Cd +BkTxCd ++Domn +++Fmly ++++Cd +BkTxCd ++Domn +++Fmly ++++SubFmlyCd +AmtDtls ++InstdAmt +NtryDtls ++TxDtls +++Refs ++++MsgId +NtryDtls ++TxDtls +++Refs ++++InstrId +NtryDtls ++TxDtls +++Refs ++++EndToEnd +NtryDtls ++TxDtls +++Refs ++++TxId +NtryDtls ++TxDtls +++Refs ++++EndToEndId For history of SWIFT operations it is the field 61, sub-field 1. M 4x Standard operation code returned by the primary banking system. 4x 4x 3!a 18d For history of SWIFT operations it is the field 61, sub-field 6. 35x Number for incremental history downloading. 35x peration reference number (bank references). 35x Client reference. 35x peration identifier. M 35x Client reference. For SEPA transfers, it is the sub-field 7 from the field
28 Field name XML element name Statu s rder amount and currency Senders +NtryDtls ++TxDtls +++AmtDtls ++++InstdAmt +++++Amt +NtryDtls ++TxDtls +++RltdPties ++++Dbtr Sender account +NtryDtls Counterparty Counterparty account Name of the initial sender Ultimate beneficiary Transfer title structural ++TxDtls +++RltdPties ++++DbtrAcct +++++Id thr Id +NtryDtls ++TxDtls +++RltdPties ++++Cdtr +NtryDtls ++TxDtls +++RltdPties ++++CdtrAcct +++++Id thr Id +NtryDtls> ++TxDtls +++RltdPties ++++UltmtDbtr +++++Nm +NtryDtls ++TxDtls +++RltdPties ++++UltmtCdtr +++++Nm> +++TxDtls ++++RmtInf +++++Strd Format Remarks 3!a18d Field filled in for operations confirmed with the MT940 statement only. For credit operations (crediting the account). Tag details are in the following table. For credit operations (crediting the account) Account is returned in this element regardless of its format (IBAN or other). For debit operations. Tag details are in the following table. For debit operations. Account is returned in this element (regardless of its format: IBAN or other). 70x For credit operations (crediting the account). 70x For debit operations. 28
29 Field name XML element name Statu s Transfer title non-structural Additional SWIFT information Additional information for the account holder Reference number of the bank maintaining the account +NtryDtls ++TxDtls +++RmtInf ++++Ustrd +<TxDtls> ++<AddtlTxInf> Format Remarks 140x peration title (non-structural). 500x This field contains additional information from the field 61 (subfield 9) of the SWIFT statement. +<AddtlNtryInf> 500x Field earmarked for the content of the field 86 from the SWIFT message. +<AcctSvcrRef> 35A Field earmarked for the reference number assigned by the bank maintaining the account and forwarded as standard in the field 61 (sub-field 8) of the SWIFT statement. Fields for the sender and counterparty (<Dbtr>, <Cdtr>) Sender/counter party name Sender/counter party address Sender/counter party country +Nm M 70x +PstlAdr ++AdrLine +PstlAdr ++Ctry 35x This field can occur twice at maximum. C 2!a It is a mandatory field when the <AdrLine> address was used. The country is returned only for the sender for outgoing orders and for the counterparty for incoming orders. For the other party PL is always returned. 29
30 EXAMPLES 1. Domestic orders account in BBAN format <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>dmestic0001</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:ctrlsum>1</urn2:ctrlsum> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>dmestic0001</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:nbftxs>1</urn2:nbftxs> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>cmpany C</urn2:Nm> </urn2:dbtr> <urn2:dbtracct> <urn2:thr> </urn2:thr> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>not provided</urn2:endtoendid> </urn2:pmtid> <urn2:amt> <urn2:instdamt Ccy="PLN">1.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>jhn SMITH</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romanska</urn2:AdrLine> 30
31 <urn2:adrline>gdansk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:thr> </urn2:thr> </urn2:cdtracct> <urn2:rmtinf> <urn2:ustrd>test metastandard</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 2. Domestic orders account in IBAN format <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>prosta1</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>2</urn2:nbftxs> <urn2:ctrlsum>1</urn2:ctrlsum> <urn2:initgpty> <urn2:rgid> <urn2:thr> </urn2:thr> </urn2:rgid> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>lek000001pmtinfid00001</urn2:pmtinfid> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:nbftxs>2</urn2:nbftxs> <urn2:dbtr> <urn2:nm>cmpany C</urn2:Nm> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> 31
32 </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>xyz test of signs in the field</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>high</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam Testowy</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>payment</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>test import xmldfsda fasdfsda33 dsad fd fsdfsdfsda </urn2:Ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid/> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>nrm</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam Test</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> 32
33 </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>payment</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>test import xml</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 3. Tax ffice orders <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>us00010</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany XYZ</urn2:Nm> <urn2:rgid> <urn2:thr> test </urn2:thr> </urn2:rgid> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>2123</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:reqdexctndt> :00</urn2:reqdexctndt> <urn2:dbtr> <urn2:nm> CMPANY XYZ </urn2:nm> </urn2:dbtr> <urn2:dbtracct> <urn2:thr> </urn2:thr> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:dbtragt> 33
34 <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>123456</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:ctgypurp> <urn2:cd>taxs</urn2:cd> </urn2:ctgypurp> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">131.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid/> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>tax office</urn2:nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romanska</urn2:AdrLine> <urn2:adrline>gdansk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:thr> </urn2:thr> </urn2:cdtracct> <urn2:tax> <urn2:dbtr> <urn2:regnid>1aad053953</urn2:regnid> </urn2:dbtr> <urn2:rcrd> <urn2:tp>2013r01</urn2:tp> <urn2:frmscd>pit37</urn2:frmscd> <urn2:addtlinf>decyzja</urn2:addtlinf> </urn2:rcrd> </urn2:tax> <urn2:rmtinf> <urn2:ustrd>okolicynop</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 4. Social Insurance Institution order <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi="http :// xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>LEK00001ZUS001</MsgId> <CreDtTm> T12:20: :00</CreDtTm> <NbfTxs>1</NbfTxs> <InitgPty> 34
35 <Nm>CMPANY C</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId>ZUS000001</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt> :00</ReqdExctnDt> <Dbtr> <Nm>CMPANY C</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Payer city</adrline> </PstlAdr> <Id> <rgid> <thr> <Id> </Id> </thr> </rgid> </Id> </Dbtr> <DbtrAcct> <Id> <thr> <Id> </Id> </thr> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId> </MmbId> </ClrSysMmbId> </FinInstnId> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>not provided</endtoendid> </PmtId> <PmtTpInf> <CtgyPurp> <Cd>SSBE</Cd> </CtgyPurp> </PmtTpInf> <Amt> <InstdAmt Ccy="PLN">21.76</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <MmbId> </MmbId> </ClrSysMmbId> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>ZUS</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Beneficiary str</adrline> <AdrLine>Beneficiary town</adrline> </PstlAdr> </Cdtr> 35
36 <CdtrAcct> <Id> <thr> <Id> </Id> </thr> </Id> </CdtrAcct> <Tax> <Dbtr> <TaxId> </TaxId> <RegnId>R </RegnId> </Dbtr> </Tax> <RmtInf> <Strd> <RfrdDocInf> <Nb>S </Nb> </RfrdDocInf> <AddtlRmtInf/> </Strd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> 5. MT101 CRED order <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>messageidcred</urn2:msgid> <urn2:credttm> t16:00:00.000z</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>tetsty</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>cmpany C </urn2:nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> </urn2:pstladr> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>hu </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> 36
37 <urn2:fininstnid> <urn2:bic>ingbhuhbxxx</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>trans003</urn2:endtoendid> </urn2:pmtid> <urn2:amt> <urn2:instdamt Ccy="USD">1.00</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>cred</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>ingbplpw</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>cmpany YXZ</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:thr> </urn2:thr> </urn2:cdtracct> <urn2:purp> <urn2:cd>chqb</urn2:cd> </urn2:purp> <urn2:rmtinf> <urn2:ustrd>order details</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 6. MT101 DEBT order <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>messageiddebt</urn2:msgid> <urn2:credttm> t16:00:00.000z</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>testy</urn2:pmtinfid> 37
38 <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>cmpany C </urn2:nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> </urn2:pstladr> </urn2:dbtr> <urn2:dbtracct> <urn2:thr> </urn2:thr> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:bic>ingbnl2axxx</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>trans003</urn2:endtoendid> </urn2:pmtid> <urn2:amt> <urn2:instdamt Ccy="EUR">1.00</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>debt</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>ingbplpw</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>company XYZ</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:thr> </urn2:thr> </urn2:cdtracct> <urn2:purp> <urn2:cd>chqb</urn2:cd> </urn2:purp> <urn2:rmtinf> <urn2:ustrd>order details</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 38
39 7. MT101 SHAR order <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>messageidshar</urn2:msgid> <urn2:credttm> t16:00:00.000z</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>testy</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>cmpany C </urn2:nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> </urn2:pstladr> </urn2:dbtr> <urn2:dbtracct> <urn2:thr> </urn2:thr> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:bic>ingbnl2axxx</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>trans003</urn2:endtoendid> </urn2:pmtid> <urn2:amt> <urn2:instdamt Ccy="EUR">1.00</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>shar</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>ingbplpw</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>company XYZ</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>kwiatowa 15</urn2:AdrLine> <urn2:adrline> Warszawa</urn2:AdrLine> 39
40 </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:thr> </urn2:thr> </urn2:cdtracct> <urn2:purp> <urn2:cd>chqb</urn2:cd> </urn2:purp> <urn2:rmtinf> <urn2:ustrd>order details</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 8. Payroll batch <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>placowa</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>2</urn2:nbftxs> <urn2:ctrlsum>1</urn2:ctrlsum> <urn2:initgpty> <urn2:rgid> <urn2:thr> </urn2:thr> </urn2:rgid> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>lek000001pmtinfid00001</urn2:pmtinfid> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:nbftxs>2</urn2:nbftxs> <urn2:dbtr> <urn2:nm>cmpany C</urn2:Nm> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:clrsysmmbid> 40
41 <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>test of characters</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>high</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam Testowy</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>payment</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>test import xmldfsda fasdfsda33 dsad fd fsdfsdfsda </urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid/> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>nrm</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam testowy</urn2:nm> <urn2:pstladr> 41
42 <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>payment</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>test import xml</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 9. Simple batch <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>simple</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>2</urn2:nbftxs> <urn2:ctrlsum>1</urn2:ctrlsum> <urn2:initgpty> <urn2:rgid> <urn2:thr> </urn2:thr> </urn2:rgid> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>lek000001pmtinfid00001</urn2:pmtinfid> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:btchbookg>false</urn2:btchbookg> <urn2:nbftxs>2</urn2:nbftxs> <urn2:dbtr> <urn2:nm>cmpany C</urn2:Nm> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> 42
43 </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:dbtragt> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>test of characters</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>high</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam Testowy</urn2:Nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>straight</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd> Test import xmldfsda fasdfsda33 dsad fd fsdfsdfsda </urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid/> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>nrm</urn2:instrprty> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="PLN">3.00</urn2:InstdAmt> </urn2:amt> <urn2:cdtragt> <urn2:fininstnid> <urn2:clrsysmmbid> <urn2:mmbid> </urn2:mmbid> </urn2:clrsysmmbid> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>adam Testowy</urn2:Nm> <urn2:pstladr> 43
44 <urn2:ctry>pl</urn2:ctry> <urn2:adrline>ul. Romańska</urn2:AdrLine> <urn2:adrline>gdańsk</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>pl </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt>straight</urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>test import xml</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 10. SEPA order <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>cdcsepa559</urn2:msgid> <urn2:credttm> t00:00: :00</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid> </urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>debtor name</urn2:nm> <urn2:pstladr> <urn2:ctry>pl</urn2:ctry> <urn2:adrline>julianowska</urn2:adrline> <urn2:adrline> Kutno</urn2:AdrLine> </urn2:pstladr> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:bic>ingbplpw</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:chrgsacct> <urn2:thr>
45 </urn2:thr> </urn2:chrgsacct> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>xyz111/111</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:svclvl> <urn2:cd>sepa</urn2:cd> </urn2:svclvl> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="EUR">999.99</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>shar</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>budahuhbxxx</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>deutschland GmbH</urn2:Nm> <urn2:pstladr> <urn2:ctry>hu</urn2:ctry> <urn2:adrline>d Herrsching</urn2:AdrLine> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>hu </urn2:iban> </urn2:cdtracct> <urn2:rmtinf> <urn2:ustrd>tytul ZLECENIA</urn2:Ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 11. Foreign order high <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>nowa </urn2:msgid> <urn2:credttm> t16:00:00.000z</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>111111</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:reqdexctndt> </urn2:reqdexctndt> 45
46 46 <urn2:dbtr> <urn2:nm>debtor name</urn2:nm> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:bic>ingbplpwxxx</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:chrgsacct> <urn2:thr> </urn2:thr> </urn2:chrgsacct> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>xyz111/111</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>high</urn2:instrprty> <urn2:svclvl> <urn2:cd>sdva</urn2:cd> </urn2:svclvl> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="EUR">1.00</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>shar</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>dresdeff200</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>deutschland GmbH</urn2:Nm> <urn2:pstladr> <urn2:ctry>de</urn2:ctry> <urn2:adrline>aaaaaaaaaa</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>de </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt> CNTACT_TELECM="Jan </urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>bez polskich znakow</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document>
47 12. Foreign order norm <urn2:document xmlns:urn2="urn:iso:std:iso:20022:tech:xsd:pain " xmlns :xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <urn2:cstmrcdttrfinitn> <urn2:grphdr> <urn2:msgid>22222fsdfsda</urn2:msgid> <urn2:credttm> t16:00:00.000z</urn2:credttm> <urn2:nbftxs>1</urn2:nbftxs> <urn2:initgpty> <urn2:nm>cmpany C</urn2:Nm> </urn2:initgpty> </urn2:grphdr> <urn2:pmtinf> <urn2:pmtinfid>111111</urn2:pmtinfid> <urn2:pmtmtd>trf</urn2:pmtmtd> <urn2:reqdexctndt> </urn2:reqdexctndt> <urn2:dbtr> <urn2:nm>debtor name</urn2:nm> </urn2:dbtr> <urn2:dbtracct> <urn2:iban>pl </urn2:iban> </urn2:dbtracct> <urn2:dbtragt> <urn2:fininstnid> <urn2:bic>ingbplpwxxx</urn2:bic> </urn2:fininstnid> </urn2:dbtragt> <urn2:chrgsacct> <urn2:thr> </urn2:thr> </urn2:chrgsacct> <urn2:cdttrftxinf> <urn2:pmtid> <urn2:endtoendid>xyz111/111</urn2:endtoendid> </urn2:pmtid> <urn2:pmttpinf> <urn2:instrprty>nrm</urn2:instrprty> <urn2:svclvl> <urn2:cd>prpt</urn2:cd> </urn2:svclvl> </urn2:pmttpinf> <urn2:amt> <urn2:instdamt Ccy="EUR">1.00</urn2:InstdAmt> </urn2:amt> <urn2:chrgbr>shar</urn2:chrgbr> <urn2:cdtragt> <urn2:fininstnid> <urn2:bic>dresdeff200</urn2:bic> </urn2:fininstnid> </urn2:cdtragt> <urn2:cdtr> <urn2:nm>deutschland GmbH</urn2:Nm> <urn2:pstladr> 47
48 <urn2:ctry>de</urn2:ctry> <urn2:adrline>aaaaaaaaaa</urn2:adrline> </urn2:pstladr> </urn2:cdtr> <urn2:cdtracct> <urn2:iban>de </urn2:iban> </urn2:cdtracct> <urn2:instrfordbtragt> CNTACT_TELECM="Jan </urn2:instrfordbtragt> <urn2:rmtinf> <urn2:ustrd>bez polskich znakow</urn2:ustrd> </urn2:rmtinf> </urn2:cdttrftxinf> </urn2:pmtinf> </urn2:cstmrcdttrfinitn> </urn2:document> 48
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
SEPA Direct Debit Unpaid Report File Format
SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 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
XML ACCOUNT STATEMENT. Service Description
XML ACCOUNT STATEMENT Service Description October 2011 OY SAMLINK AB SERVICE DESCRIPTION 2 (18) Table of contents Table of contents Error! No table of contents entries found. OY SAMLINK AB SERVICE DESCRIPTION
How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server
Appendix to Danish Message Implementation Guideline for Common Global Implementation (CGI) Customer Credit Transfer Initiation and Danish Implementation Guideline for CGI Customer Payment Status Report
SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC115-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
Payments Market Practice Document. ISITC Settlements Working Group
Payments Market Practice Document ISITC Settlements Working Group Publication Date: October, 2012 Author(s): ISITC Settlements Working Group DISCLAIMER This market practice document has been developed
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.
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.
OP's C2B SERVICES Pain 03. Payment Transfer Products
OP's C2B SERVICES Pain 03 Payment Transfer Products Customer Guidelines March 2015 2/104 Version Key Changes Changed section November 2012 added money orders 13 C2B money orders July 2013 updated payment
Record description XML File Transfer Balance and Transaction list camt.052.001.02
Record description XML File Transfer Balance and Transaction list camt.052.001.02 15.11.2012 Page 2 of 14 Change date Version Changed 10.10.2011 1.0 07.02.2012 1.1 2.1 Identification kentän pituus muuttunut,
SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC114-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3
ISO 20022 ACCOUNT STATEMENT GUIDE v 1.3 4.10.2012 1 ISO 20022 Account Statement Guide Table of contents 1 Introduction... 3 2 General... 3 2.1 Effects on customer routines... 4 2.2 Activities... 4 3 Electronic
Format description XML SEPA Credit Transfer. Format Description
Format description XML SEPA Credit Transfer Format Description CONTENTS 1 SEPA CT Import format 3 1.1 SEPA CT import format description 3 1.1.1 Description 3 1.1.2 General characteristics 3 1.1.3 Difference
Payments Standards - Clearing and Settlement
UNIFI (ISO 20022) Message Definition Report Payments Standards - Clearing and Settlement Approved by UNIFI Payments SEG on 06 June 2006 Edition July 2006 Table Of Contents Overview... 1 What does this
XML message for Payment Initiation Implementation Guideline. Version 1.02
XML message for Payment Initiation Implementation Guideline Version 1.02 Version 1.02 Changes Updated 20131211 1) SEB specific rule added under tag 2.44 Equivalent Amount 2) To the tag 2.89 Regulatory
Record description XML File Transfer ISO 20022 XML pain.001.001.02
Record description XML File Transfer 20022 XML pain.001.001.02 15.11.2012 2 Change date Version Changed 2.6.2010 1.0 2.15 Payer s business id. Length can be 8, 9, 13 or 14 marks (so called long business
OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE
Version 2.5 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, ISO 20022 APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE DESCRIPTION
Customer Statement - MT940 with Structured Information To Account Owner
General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either
Format Description SWIFT MT940 Structured
Format Description SWIFT MT940 Structured Rabo Cash Management Colophon Title Format Description SWIFT MT940 Structured Version, date 3.331, November 2014 On behalf of Zakelijke Klantkanalen Contact address
ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03
ISO 20022 PAYMENT GUIDE Messages: Pain.001.001.03 Pain.002.001.03 20.11.2012 1 ISO 20022 Payment Guide Table of Contents 1 Background... 3 1.1 SEPA and ISO 20022... 3 1.2 Usage of ISO 20022 in Finland...
Format Description. SWIFT MT103 Single Customer Credit Transfer
De Format Description SWIFT MT103 Single Customer Credit Transfer COLOPHON Title Format Description SWIFT MT103 Version, date 1.3, June 2015 On behalf of Contact address Corporate Client Channels Rabobank
PAIN.002. Format description Functional
PAIN.002 Format description Functional Content 1. PAIN.002 STATUS EXPORT FORMAT 3 2. PAIN.002 SCENARIOS 5 APPENDIX 1: EXPORTING PAIN.002 FROM RABO CASH MANAGEMENT 12 APPENDIX 2: DOWNLOADING PAIN.002 FROM
F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e
F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 Version 2 Change log Version Date Change 1 2013-10-07 Document created 2 2015-01-09 Field :57D: updated with bank codes (e.g FedWire routing No.
SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa
Financial Supply Chain SEPA SEPA formats - an introduction to XML version September 2013 www.ing.be/sepa INTRODUCTION 1 INTRODUCTION TO XML 2 What is XML? 2 What is a root element? 2 What are the specifications
Format Description MT940. Rabo Cash Management
Format Description MT940 Rabo Cash Management COLOFON Title Format Description MT940 Version, date 2.4, January 2013 On behalf of Contact address FL-Services Rabobank Nederland, Croeselaan 18, Postbus
OP's C2B SERVICES Pain 02. Payment transfer products
OP's C2B SERVICES Pain 02 Payment transfer products Customer Guidelines March 2015 2/105 Version Key Changes Changed section November 2012 added money orders 1.3 C2B money orders July 2013 updated payment
Hal E-Bank Foreign payments (Format of export/import files)
Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments: format of export/import files Version: 17.x.x.20 Author: HALCOM d.d., Ljubljana Editor: HALCOM a.d., Beograd, July
BZWBK24 Internet. How to access the Bank? Logging on to BZWBK24 Internet: Step-by-step instruction
BZWBK24 Internet BZWBK24 Internet is a service which offers quick and easy access to bank accounts using a personal computer connected to the Internet. This service ensures the most comprehensive access
ISO 20022 Message Implementation Guide for Payment Initiation
ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.5 Issue date: 16 November 2015 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation
Online Banking Record Descriptions
Record s [email protected] Page 1 of 65 Contents Introduction... 3 Sydbank format... 3 Format descriptions... 5 of fixed-length records... 5 of variable-length records... 6 Payment start... 7 IB000000000000...
User's manual for OTPdirekt Internet Banking. v.1.0
User's manual for OTPdirekt Internet Banking v.1.0 1 Contents General... 4 Log in... 4 Logging out... 4 Home page... 5 Accounts... 5 Accounts - Overview of movements... 6 Accounts - OTPdirekt transactions...
BEST client format supported by KB (valid from 28th November 2015)
supported by KB (valid from 28th November 2015) 1/19 List of contents: 1 Introduction... 4 1.1 Purpose of this document... 4 1.2 Characteristics of BEST format... 4 2 Formal check of BEST format... 4 2.1
FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING
FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING FILE FORMAT OF PAYMENT ORDERS for Citibank Europe plc, organizační složka CitiBusiness Direct Internet
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS SECTION 1 General provisions... 1 I. General rules for payment execution in foreign exchange transactions...
Deutsche Bank www.deutschebank.nl. Deutsche Bank MT940/942 format specifications
Deutsche Bank www.deutschebank.nl Deutsche Bank MT940/942 format specifications Content 1. Introduction 3 2. SWIFT MT940 Customer Statement Message 4 2.1 MT940 Format 4 2.2 MT940 Tag & (sub)field Specifications
ANZ TRANSACTIVE FILE FORMATS WEB ONLY 07.2013. Page 1 of 118
ANZ TRANSACTIVE FILE FORMATS WEB ONLY 07.2013 Page 1 of 118 ANZ Transactive and ANZ Transactive - Mobile are provided by Australia and New Zealand Banking Group Limited (ACN 005 357 522). References to
ERP SEPA readiness checklist
ERP SEPA readiness checklist version July 2013 www.ingsepa.com Financial Supply Chain SEPA This list contains 11 questions to determine the level of SEPA-readiness of an ERP 1. The first 3 questions deal
SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct
SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct January 2008 2008 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of
Bankline internet banking import file layout user guide
Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How
The New System of Accounts Message structure: Cash settlement balances derivatives (demt.smc.001.01)
The New System of Accounts Message structure: Cash settlement balances derivatives (demt.smc.001.01) Document date: 01.02.2007 : This message includes a statement of financial liabilities and receivables
Implementing SEPA in Belgiu m
SEPA Country Guide Belgium Implementing SEPA in Belgiu m All you need to know for a successful SEPA migration Introduction This document provides an overview of all the country specific information you
Format description of MT103 (Multicash PLA) foreign payment file.
Format description of MT103 (Multicash PLA) foreign payment file. 1 General information about MT103 file This document explains formats of MT103 file - used to import International / Foreign Currency Order
OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE
Version 1.94 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Pain.001.001.02 Pain.002.001.02 2 (51) Sisällysluettelo MANUAL VERSION INFORMATION... 4 1 SEPA CREDIT TRANSFER, ISO 20022 APPLICATION
HSBC s guide to straight-through processing. Ensuring timely and cost-efficient payments
HSBC s guide to straight-through processing Ensuring timely and cost-efficient payments At HSBC Global Payments and Cash Management, we provide you with access to high-quality payment services. Our payment
Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections. www.deutschebank.nl
Deutsche Bank Global Transaction Banking Internet Bankieren Entering Payments and Collections www.deutschebank.nl Internet Bankieren Entering Payments and Collections 2 Entering payments and collections
Format Description. SWIFT MT202: General Financial Institution Transfer
Format Description SWIFT MT202: General Financial Institution Transfer COLOPHON Title Format Description SWIFT MT202 Version, date 1.2, June 2015 On behalf of Contact address Corporate Client Channels
Intra-day payment Frequently asked questions
Intra-day payment Frequently asked questions Contents 1. THE MEANING, advantages and scope of intra-day payment... 3 1.1. What does the launch of intra-day payment mean?... 3 1.2. What advantages does
KM client format supported by KB valid from 26 March 2007
supported by KB valid from 26 March 2007 1/15 VRSION 1.2. UPDATD: 13.12.2005. 1 Introduction...2 1.1 Purpose of this document...2 1.2 Characteristics of the KM format...2 2 Formal check of KM format...3
499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer
499.35 en (pf.ch/dok.pf) 11.2015 PF EPO manual Electronic payment order via file transfer Customer support Customer support for EPO Consulting & Sales Phone +41 848 888 900 (CHF 0.08/min. from a landline)
ipko biznes Administrator s Guide
ipko biznes Administrator s Guide 1 1. GLOSSARY Client an entity that entered into e-banking agreement with the Bank. User a representative entitled to use e-banking services, that is a person appointed
Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers
SEPA in Spain Useful links Spanish official SEPA website (in Spanish language) http://www.sepaesp.es/ National Central Bank of Spain www.bde.es/bde/en Official Migration Guide for the Spanish market Download
March 2014. Euro Payment. Manual
March 2014 Euro Payment Manual Contents 1 Introduction 2 Euro Payment: characteristic features 2.1 Introduction 2.2 Differences compared to the Dutch credit transfer 2.3 IBAN and BIC 2.4 Timelines and
Foreign payment orders
p. 1 Foreign payment orders The Foreign payment orders bank standard deals with the electronic exchange of payment orders in euro or in foreign currencies transmitted by the customer to his bank. For payments
MT 103+ Single Customer Credit Transfer
MT 103+ Single Customer Credit Transfer The MT 103+ is a General Use message, ie, no registration in a Message User Group is necessary to send and receive this message. It allows the exchange of single
CONDITIONS FOR MAKING PAYMENT TRANSACTIONS
CONDITIONS FOR MAKING PAYMENT TRANSACTIONS 1. GENERAL PROVISIONS 1.1 In the Conditions for Making Payment Transactions (hereinafter referred to in this document as the Conditions) the bank issues the terms
480.84 en (pf.ch/dok.pf) 10.2015 PF. Manual PostFinance ISO messages for banks [pacs messages]
480.84 en (pf.ch/dok.pf) 10.2015 PF Manual PostFinance ISO messages for banks [pacs messages] Customer service Enquiries concerning service ISO 20022 for banks PostFinance Ltd Customer Service Banks Mingerstrasse
SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC301-07 25 November 2014 (Version 6.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the
Swedish Common Interpretation of ISO 20022 Payment Messages. Appendix 1: Common Payment Types in Sweden
Swedish Common Interpretation of ISO 20022 Payment Messages Appendix 1: 2 (27) Version Date Changes 0.1 2013-12-11 Initial version 1.0 2014-02-10 Updates after external review Page 5: Added that BG/PG
in Fr a nce Introduction
in Fr a nce Introduction This document provides an overview of all the country specific information you need to successfully implement your migration to SEPA in France. Intending to provide a global picture
SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC115-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
Format description XML SEPA Credit Transfer
Format description XML SEPA Credit Transfer Rabo Cash Management Colophon Title Format description XML SEPA CT Version, date 1.7, April 30, 2014 Our reference Format description XML SEPA Credit Transfer
More information on completing payment details
More information on completing payment details Agreement number [applicable to Transfer from account abroad] Enter reference number for agreed rate or forward rate. Amount Enter the amount, and specify
1.0 Registration on EBankig 8. 0.0. Registration on EBankig 7
1 Contents: 1.0. Registration on EBankig 5 1.0. Registration on EBankig 6 0.0. Registration on EBankig 7 1.0 Registration on EBankig 8 1.0. Login on Ebanking.9 2.0. Login on Ebanking......10 2.0. Login
SWIFTReady for Corporates Cash Management
Service Partners SWIFTReady for Corporates Cash Management Label Criteria 2012 This document explains the business criteria needed to obtain the SWIFTReady for Corporates Cash Management label, aimed at
QUICK REFERENCE GUIDE. ING Payment Processing Offer in XML
QUICK REFERENCE GUIDE TABLE OF CONTENTS 1. ING PAYMENT PROCESSING TYPES... 3 2. ENCODING... 4 2.1. How to request the different payment processing?... 4 2.2. Standard Payment Processing... 4 2.3. Urgent
SEPA Country Guide Italy. Introduction
Introduction This document provides an overview of all the country specific information you need to successfully implement your migration to SEPA in Italy. Intending to provide a global picture of the
MT104 Direct Debit and Request for Debit Transfer Message.
MT104 Direct Debit and Request for Debit Transfer Message. Change log Version Date Edit 1 10.11.2003 Document created 2 22.10.2005 Updated with German Direct Debit 3 21.03.2006 Updated with English Irish
Terms and Conditions applicable to Correspondent Banks 1 st November 2015
Terms and Conditions applicable to Correspondent Banks 1 st November 2015 Important Notice: The Landesbank Berlin Group is currently being extensively reorganised. The strategy setup of our company is
Service description. Corporate Access Payables
Service description Corporate Access Payables Table of contents Page 2 of 12 1 INTRODUCTION... 3 2 STRUCTURE OF DOCUMENTATION... 4 3 AGREEMENT SET-UP... 4 4 AVAILABLE MESSAGE TYPES... 5 5 OFFERED PAYMENT
Format Description SWIFT FIN MT101. Rabobank
Format Description SWIFT FIN MT101 Rabobank COLOPHON Title Format Description SWIFT FIN MT101 Version, date 1.25, September 2015 On behalf of Contact address Corporate Client Channels Rabobank Nederland,
Regulation on Bank Account Standard Numbering System
Pursuant to Article 35, paragraph 1, sub-paragraph 1.1 of the Law no. 03 / L-209 on the Central Bank of the Republic of Kosovo, and Article 8, paragraph 1, sub-paragraph 1.1, paragraph 2, sub-paragraph
ISDA International Swaps and Derivatives Association, Inc.
STANDARD SETTLEMENT INSTRUCTIONS REPOSITORY Best Practice Requirements August 2010 Table of Contents 1 REVISION HISTORY... 2 2 PROBLEM STATEMENT... 3 3 DOCUMENT PURPOSE... 3 4 SCOPE... 3 5 STANDARD SETTLEMENT
INFO SHEET Effective from 1 January 2012 Applies to individuals
This Info Sheet from Citibank Europe plc, a company established and existing under the laws of Ireland, with its registered office at North Wall Quay 1, Dublin, Ireland, registered in the Company Register
Standards MX Message Implementation Guide and Rule Book
Solutions SWIFT for Corporates Standards MX Message Implementation Guide and Rule Book Payment Initiation and Account Reporting This document describes and references a set of rules and guidelines you
Straight2Bank Payments Initiation User Guide
Straight2Bank Payments Initiation User Guide Last Updated: June 2014 Table of Contents PURPOSE... 4 1. OVERVIEW OF PAYMENT SERVICES ON STRAIGHT2BANK... 5 2. MAKING PAYMENTS ON STRAIGHT2BANK... 7 3. USING
RF Creditor Reference
RF Creditor Reference Facilitating full end-to-end straight-through payment processing version 1.0, May 2010 RF Expert Group 2 (36) Page RF Creditor Reference... 1 Facilitating full end-to-end straight-through
Isabel 6 Guide Group #1. How to encode SEPA and Non-SEPA transactions from an ING Belgium (BBRUBEBB) account?
Isabel 6 Guide Group #1 How to encode SEPA and Non-SEPA transactions from an ING Belgium (BBRUBEBB) account? Version 2.1 06-11-2013 Purpose This document describes how to use the Isabel 6 Payment Wizard
Tariff of Banking Fees and Commissions for Customers in CaixaBank, S.A. (Spółka Akcyjna) Oddział w Polsce
Tariff of Banking Fees and Commissions for Customers in CaixaBank, S.A. (Spółka Akcyjna) Oddział w Polsce () www.lacaixa.pl TABLE OF CONTENTS: 1. GENERAL CONDITIONS 3 2. CURRENT ACCOUNTS 5 3. DOMESTIC
DirektNet Frequently Asked Questions (FAQ)
DirektNet Frequently Asked Questions (FAQ) Frequently Asked Questions DirektNet functions, how to request the service Activation, login Password, security SMS password Viewing earlier transactions Questions
Wire Transfer. itreasury Module User Guide. It s time to expect more. Regions Bank 032013. Member FDIC
Wire Transfer itreasury Module User Guide It s time to expect more. Regions Bank 032013 Member FDIC 1 Welcome to Regions itreasury Welcome to Regions itreasury online banking. The itreasury suite of services
PAYMENT FACTORY AND IN-HOUSE BANK
Wallstreet Suite Comprehensive, cross-asset investment and debt management solutions for financial institutions www.wallstreetsystems.com FACT SHEET: PAYMENT FACTORY AND IN-HOUSE BANK Wallstreet Suite
Changes only affecting customers using SWIFT codewords, Intermediary Institutions, or with other special requirements
Bankline File Import Guide 1. Introduction This document describes the changes effective April 2008 for the Bankline Internet Banking Import File Layout User Guide. In overview, the changes are as follows.
2. HOW TO CREATE A NEW XML SDD CORE FILE IN TELELINK 6 FROM A.CSV FILE 4. 2.1. Run the application Telelink 6 4
Financial S upp ly C hai n SEPA Creating an XML SDD CORE file from.csv file in Telelink 6 Version March 2014 ing.be/sepa 1. INTRODUCTION 3 2. HOW TO CREATE A NEW XML SDD CORE FILE IN TELELINK 6 FROM A.CSV
Format Description XML SEPA CT
Format Description XML SEPA CT SWIFT FileAct Rabobank Format Description XML SEPA CT - SWIFT FileAct November 2015 Version 2.2 1 Contents SEPA CT Import Format 3 SEPA CT Structure 4 Segment description
EBS204 Version 1 Published November 1996. EBS204 Version 2 Published July 2000. EBS204 Version 3 Published February 2001
EUROPEAN COMMITTEE FOR BANKING STANDARDS IBAN: INTERNATIONAL BANK ACCOUNT NUMBER EBS204 V3 FEBRUARY 2001 Document history EBS204 Version 1 Published November 1996 EBS204 Version 2 Published July 2000 EBS204
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
Nordea Account structure. Corporate egateway
Nordea Account structure Corporate egateway 1. Nordea Account structures The purpose of this document is: A) To provide an overview of the possibilities for customer to send and receive BBAN and IBAN account
ELECTRONIC BANKING. RFT MT101 File Format Description Ver. 2009-09-28
ELECTRONIC BANKING RFT MT101 File Format Description Ver. 2009-09-28 CONTENTS: 1. RFT MT101 File Format Description 3 2. Detailed MT101 File Format Description 3 2.1 Key to description of the records 3
SWIFT Certified Application - Exceptions and Investigations
Service Partner Programme SWIFT Certified Application - Exceptions and Investigations Label Criteria 2016 This document explains the criteria required to obtain the SWIFT Certified Application - Exceptions
KM client format supported by KB valid from 1 November 2009
supported by KB valid from 1 November 2009 1/16 1 Introduction...2 1.1 Purpose of this document...2 1.2 Characteristics of the KM format...2 2 Formal check of KM format...3 2.1 KM format - domestic payments...3
HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF
BANKING COMMITTEE FOR THE STANDARDISATION AND APPLICATION OF IBAN HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF Basic Bank Account Number (BBAN) And International Bank Account Number (IBAN) IN CYPRUS
SEPA Credit Transfer. Readiness Checklist
SEPA Credit Transfer Readiness Checklist 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 or further
Format Reference Guide
Fedwire Funds Service Effective November 10, 2014 This provides an overview of the Fedwire Funds Service message format requirements. Please refer to Section 4.3 of the Fedwire Application Interface Manual
SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands
SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.
SEPA - Frequently Asked Questions
SEPA - Frequently Asked Questions Contents SEPA Overview Questions... 2 What is SEPA?... 2 What is the aim of SEPA?... 3 Where did SEPA come from?... 3 What countries are included in SEPA?... 3 What currencies
pg. 2 pg. 6 pg.8 pg. 20
SEPA Extra Payment news pg. 2 pg. 6 pg.8 pg. 20 SEPA harmonises payments The account number format when SEPA is valid SEPA will cause changes to material transfer services Is your company ready for SEPA?
Intraday credit transfer: Frequently Asked Questions and Definitions. Bank customers enjoy significant advantages
Intraday credit transfer: Frequently Asked Questions and Definitions Bank customers enjoy significant advantages Following 1 July 2012 the execution time of domestic HUF credit transfers will be one business
BUSINESS ONLINE USER MANUAL
BUSINESS ONLINE USER MANUAL Version, date: June 2015 Table of Contents INTRODUCTION... 3 SECURITY... 4 WHAT IS DHB BUSINESS ONLINE?... 5 User Profiles... 5 APPLICATION... 6 If you are already using DHB
Oracle FLEXCUBE Direct Banking Release 12.0.1.0.0 Retail Transfer and Payments User Manual. Part No. E52306-01
Oracle FLEXCUBE Direct Banking Release 12.0.1.0.0 Retail Transfer and Payments User Manual Part No. E52306-01 Retail Transfer and Payments User Manual Table of Contents 1. Transaction Host Integration
