> 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/fichero-entidades.properties.md).

# Entidades.properties file

The use of this file is optional and sets up an extra data source needed for the conversion from flat format to XML to be complete and correct. When this file is not defined, or the data being searched for is not found, the corresponding tags in the XML formats will be left empty or with the literal "NOTPROVIDED" as allowed by the standard in each case.

Specifically, it allows you to provide the BIC of the ordering party's entity under the ISO transfer standard, as well as the BIC of the creditor's entity under the ISO direct debit standard. As many entities as necessary can be listed.

The file will contain exclusively relationships between BIC codes and the pair of numbers "bank + branch" to which they correspond. For Spanish entities, the indicated "bank + branch" number will be searched for in positions 4 to 11, counting from 0, in the IBAN accounts (which begin with "ES") corresponding to the party for which the BIC is to be reported (creditor for direct debits and ordering party for transfers) in the corresponding records of the flat-format file.

Example location: `ES0001234567000000000000`

Initial file content:

```properties
#Example
#bic.0=ABCDEFGHXXX
#entyof.0=01234567

bic.1=
entyof.1=

bic.2=
entyof.2=
```

The four branch digits can be replaced by the mask `*` to associate all the branches of an entity with the same BIC.

Likewise, the file can also be used with Portuguese accounts.

***


---

# 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/fichero-entidades.properties.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.