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

# Regulations

Depending on its 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 records of length 600).

<details>

<summary>2012</summary>

* Document “Orders in file for issuance of transfers and euro cheques”. Series of banking rules and procedures No. 34-14, November 2012 version.
* Document “SEPA direct debits in electronic format - Basic Scheme”, Series of banking rules and procedures No. 19-14, November 2012 version.
* Document “SEPA direct debits in electronic format - B2B Scheme”, Series of banking rules and procedures No. 19-44, November 2012 version.

</details>

<details>

<summary>Rulebook 2023.</summary>

* Document “Orders in file for issuance of transfers and euro cheques”. Series of banking rules and procedures 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”, Series of banking rules and procedures 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”, Series of banking rules and procedures No. 19-44 for Rulebook 2023. This format is proprietary to Editran and the document is only available once the license has been acquired.

</details>

* Flat confirmation response file from TGSS.

Submission of R03 payment files, electronically signed. Protocol with financial institutions. (Final protocol, 20/03/2012).

* XML files: orders in ISO 20022 format.

<details>

<summary>2012</summary>

* Document Orders in ISO 20022 format for Issuance of transfers and euro cheques. Series of banking rules and procedures. Implementation Guide v1.0, November 2012. Follows the pain.001.001.03.xsd schema
* Document Orders in ISO 20022 format for issuance of SEPA direct debits – Basic Scheme. Series of banking rules and procedures. Implementation Guide, November 2012. Contains four different messages:
  * Submission of debits, follows the pain.008.001.02 schema.
  * Rejection of the operation, follows the pain.002.001.03 schema.
  * Return, also follows the pain.002.001.03 schema.
  * Reversal for reimbursement, follows the pain.007.001.02 schema.
* Document Orders in ISO 20022 format for issuance of SEPA direct debits – B2B Scheme. Series of banking rules and procedures. Implementation Guide, November 2012. It contains the same four messages as the previous one and follows the same schemas.

</details>

<details>

<summary>Rulebook 2023.</summary>

* Document Orders in ISO 20022 format for Issuance of transfers and euro cheques. Series of banking rules and procedures. Implementation Guide for Rulebook 2023. Follows the pain.001.001.09.xsd schema
* Document Orders in ISO 20022 format for issuance of SEPA direct debits – Basic Scheme. Series of banking rules and procedures. Implementation Guide for Rulebook 2023. Contains four different messages:
  * Submission of debits, follows the pain.008.001.08 schema
  * Rejection of the operation, follows the pain.002.001.10 schema
  * Return, also follows the pain.002.001.10 schema
  * Reversal for reimbursement, follows the pain.007.001.09 schema
  * Document Orders in ISO 20022 format for issuance of SEPA direct debits – B2B Scheme. Series of banking rules and procedures. Implementation Guide for Rulebook 2023. It contains the same four messages as the previous one and follows the same schemas.

</details>


---

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

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