> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/introduccion.md). # Introduction SEPA (from the English terminology *Single Euro Payments Area*), is the area in which citizens, businesses and other economic agents can make and receive payments in euros, under the same basic conditions, rights and obligations, regardless of their location and whether or not those payments involve cross-border processes. To achieve this uniformity, a set of standards has been drawn up that are mandatory for all financial institutions as of February 2014, and their use is also recommended in customer-financial institution relations. These standards define, among other things, the formats that payment messages that are not in cash must comply with, when their origin or destination is one of the countries included within the SEPA scope. To date, SEPA has specified these formats for the following three messages: * SEPA Direct Debits in electronic file – Basic Scheme * SEPA Direct Debits in electronic file – B2B Scheme * File orders for issuing transfers and checks The ISO 20022 standard is the common platform for all of them and its syntax is XML. At the same time, in order to facilitate migration to the new standard, especially in customer-financial institution relations, and as a transitional solution to be used only within the national scope, SEPA Spain has reworked the old AEB booklets corresponding to the three messages mentioned above. These reissues of those formats also define flat files, but this time with fixed record lengths of six hundred characters that include practically all of the new concepts defined in the ISO 20022 standard messages: BIC codes, IBAN accounts, etc. In short, temporarily, with a deadline still to be determined, these two formats will coexist as valid ways to communicate the same information. ## 1.1 Objectives The Editran product is capable of transmitting any type of file, including those in XML format. However, until now, it did not cover the new need arisen for many customers still immersed in the task of adapting their systems to the new XML communication language: to transform messages or files in ISO 20022 (XML) format into the new flat format and vice versa. This objective is solved with Editran/SEPA, the application whose use is described in this document. As will be seen in section [4 How to use](#4-modo-de-uso), the Editran/SEPA application can be used in two ways: 1. By adding the new functionality to the Editran product: to do this, its use will be defined in the user processes before or after Editran/G, which will make it possible to obtain the final format of the desired file before or after a transmission. 2. Completely independently: by calling the program merely to convert a file that is in XML and is to be transformed into the new flat format or vice versa. In either case, the application will receive a file and, supported by the regulations applicable in each case (flat or XML, see section [2.1 Regulations](#21-normativas)), it will perform the transformation, generating a new file in the opposite format. Under no circumstances does Editran/SEPA perform conversions to or from the old flat AEB booklet formats to the new standards (whether the flat or the XML one). *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/introduccion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.