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

# Receipt of the files

The entities will receive the files from TGSS in XML format, according to the ISO 20022 pain.001.001.03.xsd schema.

*XML(pain.001.001.03) -> Converter -> Plain-text file: TGSS header record + SEPA 34-14 file*

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

* Type of submission (2 positions):
* File creation date, 6 positions (YYMMDD)
* Paying financial entity NRBE (4 positions)
* Reference (20 positions)

⚠️Attention: Under the specific indication of the parameter in record 0 of ZTBGFDAT position 86 - TGSS Header (It could also be provided in the Configuracion.properties file), when these files pass through the Converter, they will be translated into plain text format.

The use of this parameter ignores any value given to the parameter in record 3 Create XML CONF (Ace-Rech), automatic response if the file to be converted is of standard 34-14.

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 (plain-text format)

* 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 Submission Type I. Numeric field of 2 positions. Its possible values are: 50 - Transfer files R03, electronically signed
* FIELD E Submission Type II. Numeric field of 2 positions. Its values will be as follows:
  * *01 - For all the above submission types (Possibility of including 06 in some specific case in later versions)*
* FIELD F Client Reference.
  * *F1 File creation date. Numeric field of 6 positions*
  * *F2 File Creation Time. Numeric field of 4 positions*
  * *F3 Financial Entity Code. Numeric field of 6 positions*
* FIELD G Extension of the Client Reference. Alphanumeric field of 20 positions. It will contain the R number and the Paying Cash Desk
* 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 \<MsgId> tag + 01 + next 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 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/adaptacion-para-pagos-telematicos-de-la-tgss/recepcion-de-los-ficheros.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.