> 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/a-tener-cuenta.md). # Things to keep 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 total amounts, etc.). However, it does validate the format in both cases: correct record sequence in the flat format and validation against the corresponding schema in the XML format. * As for the content, the definitions of the new rules for the flat formats are not completely symmetrical with respect to the XML rules, so there will be concepts and fields that will be lost when performing the conversions in one direction or the other. This particularity should not be understood as a limitation or defect of Editran/SEPA, but rather as a characteristic of the rules themselves. In any case, such "data loss" in no case refers to essential or mandatory concepts, but to extra information that is indeed contemplated in the XML rules. * Within this asymmetry between the formats, Editran/SEPA always seeks to preserve the maximum amount of information when transferring data from one format to another. 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 particularities when generating their files, both flat and XML. As long as these restrictions refer to the content and do not violate format-specific factors (structure, lengths, etc.), they will have no impact whatsoever on the use of the converter. * In the XML format there is a message for the payment status information of transfers (according to scheme `pain.002.001.03`) for which SEPA has not defined a standard in flat format. To perform the flat-to-XML transformations of said message, the Editran/SEPA converter uses a proprietary format that facilitates obtaining the XML file. This functionality is accessible through a specific license. * There are still entities that continue sending the formats of the old AEB books, with lengths 72 (AEB 34) and 162 (AEB 19). They may do so until February 2014, although these files will not be processed 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/a-tener-cuenta.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.