> 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/adaptacion-para-pagos-telematicos-de-la-tgss/recepcion-de-los-ficheros.md).

# Reception of the files

Entities will receive the files from TGSS in XML format, according to the schema `pain.001.001.03.xsd` of ISO 20022.

**XML (pain.001.001.03) → Converter → Flat file: TGSS header record + SEPA 34-14 file**

The content of the tag `<MsgId>` of these XML files is:

* Sending type (2 positions):
* File creation date, 6 positions (AAMMDD)
* NRBE of the paying financial entity (4 positions)
* Reference (20 positions)

Under the specific indication of the parameter `param.Cabecera`, when these files go through the Converter, they will be translated into flat format.

> **Attention:** if you do not want to add that header to all 34-14 standard files that go through the converter, `param.Cabecera` it will be specified as a Java virtual machine parameter in the corresponding script of the Editran session, and not in the file `Configuracion.properties` (see section [5 Onesait Ecosystems Configuration · Editran/SEPA](#5-configuración-de-onesait-ecosystems--editransepa)). The use of this parameter ignores any value given to `param.resp.auto` if the file to be converted is of the 34-14 standard.

The content of the resulting file will be the TGSS header record that was defined at the time, whose structure is detailed below, followed by the sepa 34-14 file.

**TRANSMISSION HEADER RECORD (flat format)**

| Field       | Description                                                                                                                                                                                        |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **FIELD A** | Header Record Code. Numeric field of 2 positions. Its value will be `01`                                                                                                                           |
| **FIELD B** | Standard Code. Numeric field of 2 positions. Its value will be `34`                                                                                                                                |
| **FIELD C** | Operation Type. Numeric field of 2 positions. Its value will be `14`                                                                                                                               |
| **FIELD D** | Sending type I. Numeric field of 2 positions. Its possible values are: `50` - R03 transfer files, electronically signed                                                                            |
| **FIELD E** | Sending type II. Numeric field of 2 positions. Its values will be as follows: `01` - For all the previous types of sending (Possibility of including `06` in some specific case in later versions) |
| **FIELD F** | Client Reference: **F1** File creation date (numeric, 6 positions); **F2** File Creation Time (numeric, 4 positions); **F3** Financial Entity Code (numeric, 6 positions)                          |
| **FIELD G** | Client Reference Extension. Alphanumeric field of 20 positions. It will contain the number of the R and the Paying Box                                                                             |
| **FIELD H** | Variable-length field up to 600                                                                                                                                                                    |

The mapping performed by the Converter is as follows:

> TGSS header record: `01` + `34` + `14` + first two characters of the tag `<MsgId>` + `01` + following six characters of `<MsgId>` + `000000` + remaining twenty-four characters of `<MsgId>` + 554 spaces.


---

# 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/adaptacion-para-pagos-telematicos-de-la-tgss/recepcion-de-los-ficheros.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.