> 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/descripcion-y-normativas.md). # Description and regulations The Editran/SEPA application is a tool that transforms files from one to the other of the two formats defined by SEPA for reporting non-cash payments in euros. So far, SEPA has defined the messages related to direct debits and transfer orders. ## 2.1 Regulations Depending on their format, flat or XML, the files processed by Editran/SEPA (both the one containing the source data and the file resulting from the transformation) will comply with one of the following standards: **Flat files: SEPA – 14 (new format with 600-character records)** * *2012* * Document "Orders in file for the issuance of transfers and cheques in euros". Banking standards and procedures series No. 34-14, version November 2012 * Document "SEPA direct debits in electronic format - Basic Scheme", Banking standards and procedures series No. 19-14, version November 2012 * Document "SEPA direct debits in electronic format - B2B Scheme", Banking standards and procedures series No. 19-44, version November 2012 * *Rulebook 2023* * Document "Orders in file for the issuance of transfers and cheques in euros". Banking standards and procedures series No. 34-14 for Rulebook 2023. This format is proprietary to Editran and the document is only available once the license has been acquired. * Document "SEPA direct debits in electronic format - Basic Scheme", Banking standards and procedures series No. 19-14 for Rulebook 2023. This format is proprietary to Editran and the document is only available once the license has been acquired. * Document "SEPA direct debits in electronic format - B2B Scheme", Banking standards and procedures series No. 19-44 for Rulebook 2023. This format is proprietary to Editran and the document is only available once the license has been acquired. **TGSS confirmation response flat file** * Sending R03 payment files, electronically signed. Protocol with financial institutions. (Final protocol, 20/03/2012) **XML files: orders in ISO 20022 format** * *2012* * Document Orders in ISO 20022 format for the issuance of transfers and cheques in euros. Banking standards and procedures series. Implementation Guide v1.0, November 2012. Follows the scheme `pain.001.001.03.xsd` * Document Orders in ISO 20022 format for the issuance of SEPA direct debits – Basic Scheme. Banking standards and procedures series. Implementation Guide, November 2012. Contains four different messages: * Submission of debits, follows the scheme `pain.008.001.02` * Rejection of the transaction, follows the scheme `pain.002.001.03` * Return, also follows the scheme `pain.002.001.03` * Reversal for refund, follows the scheme `pain.007.001.02` * Document Orders in ISO 20022 format for the issuance of SEPA direct debits – B2B Scheme. Banking standards and procedures series. Implementation Guide, November 2012. Contains the same four messages as the previous one and follows the same schemes. * *Rulebook 2023 and 2025* * Document Orders in ISO 20022 format for the issuance of transfers and cheques in euros. Banking standards and procedures series. Implementation Guide for Rulebook 2023. Follows the scheme `pain.001.001.09.xsd` * Document Orders in ISO 20022 format for the issuance of SEPA direct debits – Basic Scheme. Banking standards and procedures series. Implementation Guide for Rulebook 2023. Contains four different messages: * Submission of debits, follows the scheme `pain.008.001.08` * Rejection of the transaction, follows the scheme `pain.002.001.10` * Return, also follows the scheme `pain.002.001.10` * Reversal for refund, follows the scheme `pain.007.001.09` * Document Orders in ISO 20022 format for the issuance of SEPA direct debits – B2B Scheme. Banking standards and procedures series. Implementation Guide for Rulebook 2023. Contains the same four messages as the previous one and follows the same schemes. ## 2.2 Points to bear in mind When the user uses Editran/SEPA, they should know: * In both the case of flat files and XML files, the program does not perform any validation regarding the consistency of their content (sum of the total amounts, etc.). However, it does validate the format in both cases: correct sequence of records in the flat format and validation against the corresponding schema in the XML format. * As for the content, the definitions of the new standards for flat formats are not completely symmetrical with respect to the XML standards, so there will be concepts, fields, that will be lost when performing conversions in one direction or the other. This peculiarity should not be understood as a limitation or defect of Editran/SEPA, but rather as a characteristic of the standards themselves. In any case, such "loss of data" does not in any case refer to essential or mandatory concepts, but rather to extra information that is included in the XML standards. * Within this asymmetry between the formats, Editran/SEPA always seeks to preserve the maximum amount of information when transferring data from one format to the other. For example, if in the XML format a certain field is optional, as long as that information is contained in the source flat format, the converter will include it in the destination. * Some entities have defined particular requirements when generating their files, both flat and XML. As long as these restrictions refer to the content and do not violate factors inherent to the format (structure, lengths, etc.), they will have no impact whatsoever on the use of the converter. * In the XML format there is a message for transfer payment status information (according to schema `pain.002.001.03`) for which SEPA has not defined a flat-format standard. To perform the flat-to-XML transformations of that message, the Editran/SEPA converter uses a proprietary format that makes it easier to obtain the XML file. This functionality is accessible through a specific license. * There are still entities that continue to send the formats of the old AEB booklets, with lengths of 72 (AEB 34) and 162 (AEB 19). They will be able to do so until February 2014, although these files will not be handled by Editran/SEPA. *** --- # 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/descripcion-y-normativas.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.