> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/rf/en/getting-started/configure-rf/create-legal-entity.md).

# Create a legal entity

From the App Launcher, go to the Legal Entity object

## Creating a legal entity

* From the App Launcher, go to the Legal Entity object
* Create as many legal entities as needed by clicking New
* **Name**: {Name} E.g. International Committee of the Red Cross\
  **Fiscal year**: {Current fiscal year} E.g. 2023

{% hint style="info" %}
Note that you cannot create receipts whose payment date does not match the fiscal year of the associated legal entity.
{% endhint %}

* **Street:** {Street of the legal entity}\
  **Postal code**: {Postal code of the legal entity}\
  **City:** {City of the legal entity}\
  **Country:** {Country of the legal entity}\
  **Logo:** {Upload the legal entity's logo}\
  **Social purpose:** {List the activities carried out by the association}\
  **Signature:** {Upload the image of the president's signature}\
  **Receipt number prefix:** {Add a fixed part and a dynamic part in brackets} E.g. Red Cross-{AAAA}\
  **Next receipt number:** {Add the starting number of the tax receipt}\
  **Number length:** {Enter the number of digits of the tax receipt number}


---

# 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://university.gonexa.fr/rf/en/getting-started/configure-rf/create-legal-entity.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.