- ING Belgium
Contents
1. lt n XML format guide for Belgium SEPA Credit Transfer SCT 10 Start of the lt CreditTransferTransactionInformation gt block start of transaction rr 1 Each transaction starts by this tag lt CdtTrfTxInf gt lt Prmt Id gt lt EndToEndId gt lt EndToEndId gt lt Pmt Id gt lt Amt gt lt Instdamt EUR gt lt Instdamt gt lt Amt gt Ph ae lt CaAtraqgt gt Cdtragt gt lt Cdtr gt PE TEE FOR hie lt Nm gt lt Nm gt lt Pstlad lt AdrLine gt lt AdrLine gt lt AdrLine gt lt Pstladr gt lS POS lt Catr gt lt dtr cct gt lt IBAN gt lt Cdtracct gt AN S N an lt Rmt INT gt End of the lt CreditTransferTransactionInformation gt block end of transaction nr 1 Each transaction ends by this XML format guide for Belgium SEPA Credit Transfer SCT 11 Start of the lt C editTransferTrans tionInformation gt block start of transaction rr 2 Each transaction starts by this tag lt EndToEndId gt lt EndToEndId gt lt Pmt Id gt lt Amt gt lt InstdaAmt gt lt Instdamt gt lt Amt gt lt Carr vr qc gt Si C pm A san Fan lt ininstnia gt lt BIC gt lt Fininstnlid gt Erde rv eter lt Cdtr gt gt lt Cdtr gt lt Nm gt lt Pstladr gt lt Ctry gt lt AdrLine gt lt AdrLine gt FRA eS a KER ve f hrdy ingi lt AdrLine gt lt AdrLine gt lt Pstladr gt To lt IBAN gt lt R2. Financials KY PPI XML format guide for Belgium SEPA Credit Transfer SCT version March 2014 www ing be sepa Introduction Frequently asked questions How should the CreationDateTime be correctly formatted How should the InitiatingParty be correctly formatted How should the table above be interpreted and what do the and signs mean What is the BatchBooking What Is the RequestedExecutionDate ING Appendix to Febeltin SEPA CREDIT TRANSFER Examples CIRIO1 to XML mapping Reference Information Useful links 16 17 18 Introduction The purpose of this document is to help you to understand and use the XML format for your SEPA transactions Febelfin has published the XML Message for credit transfer Initiation based on the European Payments Council EPC Rulebooks Although the guidelines should contain all information to create a correct financial message we do believe more information is necessary to come to an efficient and smooth transfer with a satisfying end result Our description is based on the standard message ISO20022 CustomerCredit Transferlnitiation lt pain 001 001 03 gt supplemented with the Febelfin Guidelines for XML Messaging and the ING appendix The ISO 20022 standard puts some rules and constraints to the use of standard XML messaging The ING appendix which has to be considered as a complementary document to the Febe
3. the date is limited to one year in the future and 5 days in the past It is important to take the ING cut off times into consideration when using the RequestedExecutionDate tag If ING cut off times are not respected the execution time of the payment can be altered XML format guide for Belgium SEPA Credit Transfer SCT 5 ING Appendix to Febelfin SEPA CREDIT TRANSFER Appendix version 2 1 30 08 2010 ING supports the XML message for credit transfer Initiation implementation guidelines published by Febelfin the Belgian Financial Sector Federation The document can be found in the Febelfin standards for distance banking via the following link http www febelfin be en standards distance banking You are advised to always use the latest version published It is the European Payments Council EPC that decides if changes are required This annex to the Febelfin document aims to provide details about the actual interpretation of these guidelines by ING for SEPA payments SEPA Direct Debit initiated in Belgium Only Belgian creditor accounts are in scope Electronic channels Swiftnet or FTP or Isabel6 only The description is based on the standard message ISO 20022 Customer CreditTransferlnitiation lt pain 001 001 03 gt The number of transactions is limited to a maximum of 50 000 transactions per file List of items with ING specific instruction How to read this list Febelfin XML Implementat
4. 1 8 1 1 InitiatingParty lt InitgPty gt 0 1 Name lt Nm gt 70 0 1 Identification lt ld gt 1 1 Organisationldentification lt Orgld gt 0 1HOr 4 BICOrBEI lt BICorBEI gt 11 0 1 Or Other lt Othr gt 1 1 Identification lt ld gt 35 1 1 bbe Issuer lt Issr gt 35 Rules e Either Name or Identification or both must be used Name is limited to 70 characters e For Belgian companies Identification within Other must contain the Enterprise Number 10 digits and as Issuer KBO BCE e f Identification is used then Organisationldentification must be used mandatory e When Organisationldentification is used we can choose between two optional sub elements BICOrBEI or Other If Other is used Identification and Issuer must be used as they are both mandatory XML format guide for Belgium SEPA Credit Transfer SCT 2 How should the table above be interpreted and what do the and signs mean The sign refers to the level where the element figures in the xml structure The sign indicates whether an item of the message is mandatory and how many times the element can be repeated The number of occurrences is shown between square brackets e 0 1 shows that the element can be present 0 times or 1 time Element is optional 1 1 shows that the element can be present only 1 time Element is mandatory 1 n shows that the element can be pr
5. 1 Messageldentification This mandatory reference is determined by you being the initiating party and sent to your bank in order to identify the message It is recommended to limit the max length to 30 characters This reference will be not be present in your CODA reporting 2 1 Paymentinformation This mandatory reference is determined by you being the initiating Identification party in order to unambiguously identify the payment information block within the message It is recommended to limit the max length to 30 characters This reference is used when lt BtchBookg gt true is requested for MECT It is present in your CODA reporting in the reference field of the global amount 2 29 Instructionldentification This optional reference is determined by you being the initiating party and sent to your bank in order to identify the transaction As this identification is a reference between the Initiator and the Debtor s Bank it is not forwarded to the Creditor s Bank 2 30 EndToEndldentification This mandatory reference is determined by you being the initiating party in order to unambiguously identify the transaction This identification is passed on unchanged throughout the entire end to end chain This reference is present in your CODA reporting at the detail level For SEPA Credit Transfers this unique identification is passed on to the beneficiary XML format guide for Belgium SEPA Credit Transfer SCT 17 Useful l
6. gt lt EndTc lt Pmt Id gt Amt gt lt Instdamt EUR gt lt Instdamt gt lt Oe ic tne Me lt Art gt eft oem A bs Na lt Cdtragt gt lt FinInstnId gt lt Nm gt PF L al aT yo lt AdrLine gt sh na T a we an Ma Pa Fi nN dr L A maA lt AAGrLine gt lt AGrLine gt ladr gt lt IBAN gt 7 oe pa FE ER lt CatrRetint gt lt Tp gt lt CdOrPrtry gt lt a gt 0S Af Tw amp woe lt CQOrrrtry gt End of the lt CreditTransferTransactionInformation gt block a i end of transaction nr 4 Each transaction ends by this End of the second lt PaymentinstructionInfor mation gt block each batch ends by this taq C Fmt Ini Aa lt CustorrerCreditTransferInitiation gt ends with this tag lt CstmrCdtTrfInitn gt lt Document gt End of the xml lt document gt XML format guide for Belgium SEPA Credit Transfer SCT 15 CIRIO1 to XML mapping The table below shows the mandatory and recommended elements only The purpose of this information is to show you the link between the XML format and the CIRIO1 format Index Message Item lt XML Tag gt CIRIO1 functional equivalent 1 0 GroupHeader lt GrpHdr gt Mandatory 1 1 Messageldentification lt Msgld gt Mandatory 1 2 CreationDateTime lt CreDtTm gt Mandatory Rec 0 pos 6 11 1 6 Number of Transactions lt NbOfTxs gt Mandatory 1 8 Initiati
7. 0 The first batch contains a transaction for an amount of EUR 1000 00 and a second transaction for an amount of EUR 500 00 Batch booking false is requested as it concerns suppliers transactions SUPP The second batch contains a transaction for an amount of EUR 500 00 EUR and a second transaction for an amount of EUR 2000 00 Batch booking true is requested as it concerns salary payments SALA TI xmilns xsd 1 wi ta a ft oe f m he TT zl Lee J E Sq E fe r klan Fa 4 T i 1 3 21 03 lt Crebt Tm XML format guide for Belgium SEPA Credit Transfer SCT 9 lt Pmt Inf gt lt Pmt Inf Id gt lt Pmt Inf Id gt tMted gt lt BtchBooka gt means that global batch booking gt is not requested for dssablec VW Separate batches must be done for different lt Requested Execution Dates gt f fF ae re S LC yPurp gt lt PmtTpInf gt lt ReqdExctnDt gt lt ReaqdExctnDt gt This tag deals with the lt Debtor gt related information lt Nm gt valid for all the transactions of the batch lt idrl ine gt gt Rn teen Ja nai an a lt LdrLine gt lt AdrLine gt st iadr gt v 1 ryOtRes gt BE lt CtryOtRes gt Rete X This tag determines the lt Debtor Account gt valid for al lt DbDtracct gt A EET Ie eee ha NC eae IT ee logan ET oe Be me Tansactions of me pally I lt IBAN gt lt Id gt EON BSA OR s Ge F Dbt LrACCCtS gt
8. d 1 1 Issuer must be used for they are mandatory 1 1 For Belgian companies Identification within Other must contain the Enterprise Number 10 digits and as Issuer KBO BCE What is the BatchBooking The use of the batch booking functionality is optional but recommended by ING This will allow the creator of the file to define for each file or even for each batch within a file if it will be debited globally or individually from the ordering account The parameter will apply to all transactions CreditTransferTransactionInformation contained in the batch PaymentInformation When a global debit is requested this will by default mean the debit of one global amount in the account information and CODA reporting On request ING can supply detailed information for such batches MECT Multiple SEPA Credit Transfers in the CODA reporting Should you wish to receive detailed reporting information please contact our Electronic Banking Support EBS Team at least four working days before the implementation date XML format guide for Belgium SEPA Credit Transfer SCT 4 Usage rule e If not present the file will be by default considered to be batch booked e f present and contains true lt BtchBookg gt true lt BtchBookg gt batch booking is requested e f present and contains false lt BtchBookg gt false lt BtchBookg gt booking per transaction is requested The Batch Booking
9. esent 1 to n times Element is mandatory n is sometimes shown as which stands for infinite The interpretation of the status of the data is influenced by an indication of Or In that case two different sub children can be used for one child Both are correct but have another impact and consequence The two different sub children will be indicated in the occurrence as follows 0 1 Or 0 1 Or Illustration with Initiating Party The Initiating Party on level 2 is mandatory 1 1 Either Name or Identification or both must be used and are optional 0 1 because Initation Party is mandatory at least one of both should figure in the xml If the Identification is used the Organisationldentification must be used for it is mandatory 1 1 XML format guide for Belgium SEPA Credit Transfer SCT 3 For Organisationldentification there is a choice between one of the two optional elements BICOrBEI or Other There should figure at least one of these 2 but not both there is an or between them the tag Organisationldentification above is mandatory but has maximum 1 occurrence 1 1 1st Possibility BICOrBEI can be used this is a code allocated to organisations by the ISO 9362 Registration Authority e g for non Belgian companies 2nd Possibility If Other is used instead of BICOrBEI the Identification an
10. inks Febelfin standards for distance banking http www febelfin be en standards distance banking ISO20022 CustomerCreditTransferlnitiation http www iso20022 org European Payments Council EPC http Awww europeanpaymentscouncil eu content cfm page sepa_credit_transfer Format Validation Tool The User Manual is available on the website via this link http Awww ingsepa com formatvalidationtool en ING Belgium SA nv Bank Registered Office Marnixlaan 24 B 1000 Brussels Brussels RPM RPR VAT BE 0403 200 393 IBAN BE453109 1560 2789 Publisher Inge Ampe Cours Saint Michel 60 B 1040 Brussels 705117E 03 14 Editing Team amp Graphic Studio Marketing ING Belgium
11. ion Guidelines and the ING Appendix are two documents that are useful for the customer who wants to migrate easily to SEPA products These documents should be read next to each other as the ING Appendix refers to the chapters and numbering index of the Febelfin XML Implementation Guidelines The ING Appendix takes priority over the Febelfin XML Implementation Guidelines The first two figures mentioned below represent the index It is the number referring to the corresponding description in the ISO 20022 XML Message Definition Report for Payment Standards Initiation Not supported means that it is ignored by ING no blocking factor but is ignored for execution and reporting 2 4 Number of transactions Batch level B Not supported 2 5 Control sum Batch level B Not supported 2 17 Requested Execution date Batch level B e When batch booking is requested 2 3 batch booking contains true the date is limited to six months in the future and 5 days in the past e When single booking is requested 2 3 batch booking contains false the date is limited to one year in the future and 5 days in the past XML format guide for Belgium SEPA Credit Transfer SCT 6 2 19 Debtor Batch level B Identification is not supported 2 20 Debtor Account Batch level B Currency of the account is not supported 2 23 Ultimate Debtor Batch level B Not supported 2 10 Ultimate Deb
12. lfin guidelines gives you more details about what is supported or not by ING The ING Appendix takes priority over the Febelfin XML Implementation Guidelines Both the Febelfin document and the ING appendix must be read next to each other and are the key of a successful migration 18020022 ING FEBELFIN EPC An additional success factor is the use of your current knowledge to achieve a correct SEPA migration In this document we also want to give you information on how to create XML elements based on your CIRIO1 We conclude the information on how ING can help you with testing We would like to draw your attention to the fact that ING cut off times must be respected for a smooth processing of your transactions XML format guide for Belgium SEPA Credit Transfer SCT 1 Frequently asked questions How should the CreationDateTime be correctly formatted Definition Date and Time at which the message was created XML Tag lt CreDtTm gt Occurrences 1 1 Format YYYY MM DDThh mmiss Example lt CreDtTm gt 2011 08 24T09 40 30 lt CreDtTm gt If this format is not respected the payment instruction will be rejected How should the InitiatingParty be correctly formatted Definition Party initiating the payment This can be either the debtor or a party initiating the payment on behalf of the debtor XML Tag lt InitgPty gt Occurrences 1 1 Format This message item consists of the following elements
13. mt Inf gt SPY tn on ph lt SCLr a gt m si te am Th oe di lt Catrkerl PE ae Oe ee ek lt CdOrPrtry gt lt Issr gt lt Iissr PRT lt Ip JT a d Dat lt Ref gt CdtrRef fInf gt La mir rele End of the lt CreditTransfer TransactionInformation gt block end of transaction nr 2 Each transaction ends by this XML format guide for Belgium SEPA Credit Transfer SCT 12 lt PmtIn gt lt Pmt Inf gt XML format guide for Belgium SEPA Credit Transfer SCT 13 Start of the lt CreditTransferTransactionInformation gt block start of transaction rr 3 Each transaction starts by this tag lt Cdt lt EndToEndId gt lt EndToEndId gt E Id gt Pog hire ey et A d a Ds oo A SET lt Instaamt lt Instd rmnt gt lt Amt gt yea P AA A EA SCATTI AGT gt lt Fininstnia gt lt BIC gt lt Fininstnid gt lt Cdtr gt lt Nm gt lt Ctry gt lt Ctry gt 7 T es W d Fa Sv F lt drLine gt lt AdrLine gt lt s Adr Line gt lt Rmt Int gt lt Ustra gt lt Ustrd gt lt Rmt Inf gt End of the lt CreditTransfer TransactionInformation gt block end of transaction nr 3 Each transaction ends by this XML format guide for Belgium SEPA Credit Transfer SCT 14 Start of the lt CreditTransferTransactionInformation gt block start ch transaction starts by this tag of transaction rr 4 Ea lt CdtTrfTxInf gt lt Pmt Id
14. ngParty lt InitgPty gt Mandatory 2 0 Paymentinformation lt PmtInf gt Mandatory 2 1 Paymentinformationldentification lt PmtInfld gt Mandatory Rec 0 pos 118 127 2 2 PaymentMethod lt PmtMtd gt Mandatory 2 3 BatchBooking lt BtchBookg gt Recommended 2 17 RequestedExecutionDate lt ReqdExctnDt gt Mandatory Rec 0 pos 17 22 2 19 Debtor lt Dbtr gt Mandatory Rec 0 pos 39 116 2 20 Debtor Account lt DbtrAcct gt Mandatory Rec 0 pos 27 38 2 21 Debtor Agent lt DbtrAgt gt Mandatory 2 27 CreditTransferTransactionInformation lt CdtTrfTxInf gt Mandatory 2 28 Paymentidentification lt Pmtlid gt Mandatory 2 30 EndToEndldentification lt EndToEndld gt Mandatory 2 42 Amount lt Amt gt Mandatory 2 43 InstructedAmount lt InstdAmt gt Mandatory Rec 1 pos 36 47 2 79 Creditor lt Cdtr gt Mandatory Rec 1 pos 48 73 2 80 Creditor Account lt CdtrAcct gt Recommended Rec 1 pos 24 35 2 98 Remittance Information lt RmtInf gt Recommended Rec 1 pos 75 127 In CIRIO1 there was no possibility to request a global debit or a single debit in the file content The upload of a file was considered to be a global debit for that file With XML you can choose between a global debit and a debit on transaction basis by using the batch booking parameter XML format guide for Belgium SEPA Credit Transfer SCT 16 Reference Information The table below shows you where to retrieve information related to references Index Message Item Description 1
15. tag is characterized by lt BtchBookg gt in Paymentinformation block index 2 3 Important Remark on the PaymentInformation Block Regardless of whether the batch booking value is True or False you must group your transactions whenever possible under the same PaymentInformation block This avoids unnecessary impact on your reporting exponentially increasing size of the reporting files as each transaction will be reported separately and the risk of generating errors If all the data of the debit information contained in the Paymentinformation block are the same for a group of transactions using it once is enough and those transactions can be grouped under one Paymentinformation block If you want the reporting at transaction level instead of at payment information level this is possible within the set up of the ING CODA product not via the XML format What is the RequestedExecutionDate Definition Date at which the initiating party asks the Debtor s Bank to process the payment This is the date on which the debtor s account s is are to be debited XML Tag lt ReqdExctnDt gt Occurrences 1 1 Format YYYY MM DD Example lt ReqdExctnDt gt 2010 12 18 lt ReqdExctnDt gt ING Rule e When batch booking is requested 2 3 batch booking contains true the date is limited to six months in the future and 5 days in the past e When single booking is requested 2 3 batch booking contains false
16. tor Transaction level T Not supported 2 19 Creditor Transaction level T Identification is not supported 2 81 Ultimate Creditor Transaction level T Not supported 2 86 Purpose Transaction level T Not supported Legend XML format guide for Belgium SEPA Credit Transfer SCT 7 Level CUSTOMERCREDITTRANSFERINITIATION Message item Occur 1 GroupHeader 1 1 MESSAGE LEVEL M 2 Messageldentification 1 1 2 CreationdateTime 1 1 2 NumberOfTransactions 1 1 2 ControlSum 0 1 2 InitiatingParty 1 1 1 Paymentinformation 1 n BATCH LEVEL B 2 PaymentInformationldentification 1 1 2 PaymentMethod 1 1 2 BatchBooking 0 1 2 NumberOfTransactions 0 1 2 PaymentTypelnformation 0 1 2 RequestedExecutionDate 1 1 2 Debtor 1 1 2 DebtorAccount 1 1 2 DebtorAgent 1 1 2 ChargeBearer 0 1 2 CreditTransferTransactionInformation 1 n TRANSACTION LEVEL T 3 Paymentidentification 1 1 3 Amount 1 1 3 UltimateDebtor 0 1 3 CreditorAgent 0 1 3 Creditor 1 1 3 CreditorAccount 0 1 3 UltimateCreditor 0 1 3 Remittancelnformation 0 1 XML format guide for Belgium SEPA Credit Transfer SCT 8 Examples SEPA Credit Transfer with two batches of two transactions The following example describes a SEPA Credit Transfer containing two different batches of two transactions for a total amount of EUR 4000 0
Download Pdf Manuals
Related Search