> 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/normativas.md).

# 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.


---

# 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/normativas.md?ask=<question>&goal=<user_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.