> 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/anexo/codigos-de-resultado.md). # Result codes The possible results returned by the client process are: | Result code | Result meaning | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | `00` | File transformed correctly | | **Warnings** | | | `36` | File transformed with warnings | | **Errors** | | | `01` | Error reading the socket (not applicable in the Unix/Windows case) | | `02` | Error in the input parameters | | `03` | The parameter "Request Function" was not found or has an invalid value | | `04` | The parameter "Input File" was not found | | `05` | The parameter "Output File" was not found | | `06` | The parameter "Request Language" was not found or has an invalid value | | `07` | The parameter "Validate XML" has an invalid value. It can be \[S] (Yes) or \[N] (No) | | `08` | The parameter "Free field information" has an invalid value. It can be \[S] (Yes) or \[N] (No) | | `30` | Error validating the XML | | `37` | The parameter "Keep Output File in case of Error" has an invalid value. It can be \[S] or \[N] | | `40` | The parameter "Remove Validations" has an invalid value. It can be \[S] or \[N] | | `41` | The parameter "Merge XML" has an invalid value. It can be \[S] or \[N] | | `42` | The parameter "Header" has an invalid value. It can be \[T] or \[N] | | `09` | The Alphabet parameter value was not recognized or is invalid | | `10` | Invalid number of parameters | | `11` | Error performing the conversion | | `12` | Error writing the response (not applicable in the Unix/Windows case) | | `13` | Input file not found | | `14` | Error opening the output file | | `15` | Error closing the files | | `16` | Error in the files | | `17` | Error deleting the output file | | **Errors in the flat-to-XML transformation** | | | `18` | Error in the flat file. The type of standard to which the file belongs is not recognized | | `19` | Error reading the flat file | | `20` | Error in the flat file unmarshaller(\*) | | `21` | Error in the conversion between flat and XML objects | | `22` | Error in the XML marshaller(\*\*) | | `23` | Error in the order of the flat file blocks. The order must be SEPA Transfers, Other Transfers and Checks, with only one block of each | | `24` | Error including multiple logical files. They cannot be grouped into a single XML | | `25` | The values of the \[Return Date] field do not match in the \[Creditor Header by Date] records. The information cannot be grouped into a single XML file | | `38` | Error validating the Automatic Response Message XML | | `39` | Error generating the Automatic Response Message XML | | **Errors in the XML-to-flat transformation** | | | `26` | Error in the XML file. The type of standard to which the file belongs is not recognized | | `29` | Error reading the XML | | `31` | Error in the XML unmarshaller(\*) | | `32` | Error in the conversion between XML and flat objects | | `33` | Error in the flat file marshaller(\*\*) | | `34` | Error, the amount value is invalid | | `35` | Error writing the XML file. It is not possible to write PmtInf blocks that do not follow the order: SEPA Transfers, Other Transfers and Checks | | **License error** | | | `27` | Incorrect license | | **Empty file** | | | `28` | Empty input file | `(*)` Unmarshalling: generation of JAVA objects from a data file. `(**)` Marshalling: generation of a data file from JAVA objects. *** **Contact person** Brussels Avenue 35 28108 Alcobendas, Madrid, Spain T +34 91 480 50 00 F +34 91 480 50 80 [www.minsait.com](http://www.minsait.com) --- # 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/anexo/codigos-de-resultado.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.