{"id":51243,"date":"2023-03-17T09:00:37","date_gmt":"2023-03-17T08:00:37","guid":{"rendered":"https:\/\/archief.betaalvereniging.nl\/?page_id=51243"},"modified":"2023-11-01T15:47:55","modified_gmt":"2023-11-01T14:47:55","slug":"sepa-xml-version-2019","status":"publish","type":"page","link":"https:\/\/archief.betaalvereniging.nl\/en\/payment-products-services\/sepa-xml-version-2019\/","title":{"rendered":"SEPA XML Customer to bank file formats to new version"},"content":{"rendered":"<div id=\"pl-51243\"  class=\"panel-layout\" ><div id=\"pg-51243-0\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-0-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-0-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"0\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">Information for customer to bank file format submitters and suppliers of financial and CRM software<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-0-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-0-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"1\" ><div class=\"textwidget\"><p>From 17 March 2024, the SEPA XML Customer to Bank file format version 2019 will become available. This new version will come alongside the current 2009 version, at least for now. The new version offers some <a href=\"https:\/\/archief.betaalvereniging.nl\/en\/payment-products-services\/sepa-xml-version-2019\/#new\">new features<\/a> of which structured address information is the most important.<br \/>\nThe new SEPA XML version 2019 stems from European regulations and further standardisation of payment transactions. Banks will continue to support the old 2009 version at least until 22 November 2025. After that, banks may possibly decide to phase out the XML version 2009. Your bank will inform you well in advance if that is the case.<\/p>\n<\/div><\/div><\/div><\/div><div id=\"pg-51243-1\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-1-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-1-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"2\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">Mandatory to provide address information<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-1-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-1-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"3\" ><div class=\"textwidget\"><p><strong>Please note<\/strong>: for companies and organisations sending payment files with direct debits and payments to SEPA countries outside the European Economic Area (EEA) such as the United Kingdom and Switzerland (<a href=\"https:\/\/www.europeanpaymentscouncil.eu\/sites\/default\/files\/kb\/file\/2021-03\/EPC409-09%20EPC%20List%20of%20SEPA%20Scheme%20Countries%20v4.0.pdf\" target=\"_blank\" rel=\"noopener\">see EPC List of SEPA Scheme Countries<\/a>), the delivery of address information is mandatory. From 22 November 2025 onwards, address information must be delivered in a structured manner. This is possible in the new 2019 version but also via updating the 2009 version if your bank will continue to support it.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/archief.betaalvereniging.nl\/wp-content\/uploads\/Verschil-adresinformatie-SEPA-XML-versie-2009-en-2019.png\" \/><\/p>\n<p>This mainly concerns the structured delivery of your debtors' data within the SEPA Direct Debit Customer to Bank file (see example) and for your creditors' data in the SEPA Credit Transfer file. Your own data is often completed by the bank itself.<\/p>\n<p>In addition to the name (Nm), the fields town name (TwnNm) and country (Ctry) are mandatory. The rest of the fields are used if applicable for the correct interpretation of the address. For example, building name (BldgNm) will not be used very often.<\/p>\n<\/div><\/div><\/div><\/div><div id=\"pg-51243-2\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-2-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-2-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"4\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">Include the software adaptation now<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-2-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-2-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"5\" ><div class=\"textwidget\"><p>The adaptation to SEPA XML version 2019 is easy to implement in your software and\/or financial systems. The advice is to schedule software adaptations to the new SEPA XML version 2019 now. This also means making preparations to already save and store address information in a structured way in administration systems when the opportunity arises. Then you or your customers will be prepared for the future and payments can be sent or received worry-free.<\/p>\n<\/div><\/div><\/div><\/div><div id=\"pg-51243-3\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-3-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-3-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"6\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">Timeline<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-3-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-3-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"7\" ><div class=\"textwidget\"><table style=\"width: 100%; height: 270px;\" border=\"1\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr style=\"height: 20px;\">\n<td style=\"width: 149px; height: 20px;\"><strong>Version<\/strong><\/td>\n<td style=\"width: 220px; height: 20px;\"><strong>Current<\/strong><\/td>\n<td style=\"width: 220px; height: 20px;\"><strong>As of 17 March 2024<\/strong><\/td>\n<td style=\"width: 220px; height: 20px;\"><strong>As of 22 November 2025<\/strong><\/td>\n<\/tr>\n<tr style=\"height: 50px;\">\n<td style=\"width: 149px; height: 50px;\">XML 2009<\/td>\n<td style=\"width: 250px; height: 50px;\">Possible (standard)<\/td>\n<td style=\"width: 250px; height: 50px;\">Possible<\/td>\n<td style=\"width: 250px; height: 50px;\">Possible (but individual bank may phase it out over time)<\/td>\n<\/tr>\n<tr style=\"height: 50px;\">\n<td style=\"width: 149px; height: 50px;\">XML 2019<\/td>\n<td style=\"width: 250px; height: 50px;\">Not possible<\/td>\n<td style=\"width: 250px; height: 50px;\">Possible<\/td>\n<td style=\"width: 250px; height: 50px;\">Possible (standard)<\/td>\n<\/tr>\n<tr style=\"height: 50px;\">\n<td style=\"width: 149px; height: 50px;\">Buiten EEA*<\/td>\n<td style=\"width: 250px; height: 50px;\">Address information may be structured and unstructured<\/td>\n<td style=\"width: 250px; height: 50px;\">Address information may be structured and unstructured<\/td>\n<td style=\"width: 250px; height: 50px;\">Address information mandatory structured<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>* Within the EEA, delivery of address information is not mandatory. Please check with your bank what you can best do if you currently provide this information and want to switch to the XML 2019 version.<\/p>\n<\/div><\/div><\/div><\/div><div id=\"pg-51243-4\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-4-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-4-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"8\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">Differences version 2019 vs 2009<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-4-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-4-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"9\" ><div class=\"textwidget\"><ul>\n<li><a id=\"new\"><\/a>The timestamp for a payment transaction message supports the combination of a future date and time which can be interesting for certain customers or use cases under the SCT Inst scheme;<\/li>\n<li>The address fields for payers and payees need to be completed in a more structured way which facilitates a more automated screening of SEPA transactions to or from non-EEA SEPA-country based scheme participants. These fields can also contain more characters than under the 2009 version;<\/li>\n<li>It allows the proper transport of a Unique Transaction Reference (UETR) as an extra option end-to-end from the payer to the payee. This allows PSPs to track at what stage of the payment chain the payment order has arrived;<\/li>\n<li>The interbank pacs.008 message (used for both SCT schemes) contains more structured fields which can be applied for tax reporting purposes. This message now also supports the transport of the Legal Entity Identifier (LEI);<\/li>\n<li>It enables the development of Request-to-Pay (RTP) services in the C2B space.<\/li>\n<li>Furthermore, the C2B messages can also support the use of proxy identifiers (e.g., phone number, e-mail address).<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><div id=\"pg-51243-5\"  class=\"panel-grid panel-no-style\" ><div id=\"pgc-51243-5-0\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-5-0-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"10\" ><div class=\"textwidget\"><h2 class=\"c-intro c-header-line\">More information<\/h2>\n<\/div><\/div><\/div><div id=\"pgc-51243-5-1\"  class=\"panel-grid-cell\" ><div id=\"panel-51243-5-1-0\" class=\"panel widget widget_black_studio_tinymce panel-first-child panel-last-child\" data-index=\"11\" ><div class=\"textwidget\"><p>You can contact your own bank for questions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>The delivery of address information in an structured manner is mandatory. Information for customer to bank file format submitters and suppliers of financial and CRM software<\/p>\n","protected":false},"author":7,"featured_media":52108,"parent":4951,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-51243","page","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/pages\/51243","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/comments?post=51243"}],"version-history":[{"count":11,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/pages\/51243\/revisions"}],"predecessor-version":[{"id":54054,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/pages\/51243\/revisions\/54054"}],"up":[{"embeddable":true,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/pages\/4951"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/media\/52108"}],"wp:attachment":[{"href":"https:\/\/archief.betaalvereniging.nl\/en\/wp-json\/wp\/v2\/media?parent=51243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}