> 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/ibm-editran-v5.3-comun-z-os-en/editran-sepa/description/to-be-taken-into-account.md). # To be taken into account 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 flat standards are not completely symmetrical with respect to the XML standards, so there will be concepts and fields that will be lost when converting in either direction. This particularity should not be understood as a limitation or defect of Editran/SEPA, but rather as a characteristic of the standards themselves. In any case, this “data loss” in no case refers to essential or mandatory concepts, but to extra information that is included in the XML standards. * Within this asymmetry between 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 particular rules 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 payment status information (according to the pain.002.001.03 schema) for which SEPA has not defined a flat-format standard; therefore, Editran/SEPA will not be able to transform that message. * There are still entities that continue to send the formats of the old AEB booklets, with lengths 72 (AEB 34) and 162 (AEB 19). They will be able to do so until February 2014, although these files will not be processed by Editran/SEPA. The application, as an example, will transmit: * pain.008.001.02 Direct Debit Initiation (received by the application from business applications). * pain.002.001.03 Status Report. * In the pain.002.001.03 Transfer Status Report format (sent to business applications), there is no flat standard, so the application will not transform this content. * pain.007.001.02 Cancellation Request. * pain.002.001.03 Reversal Status Report (sent to business applications). * pain.001.001.03 Transfer Initiation (received by the application from business applications) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/editran-sepa/description/to-be-taken-into-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.