> 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/generate-tax-receipt.md).

# Generate a tax receipt

Refer to the Gonexa Doc module of Gonexa University to build your document template and add the generation action to the page.

Get the pre-designed Gonexa tax receipt template from our **website.**

* Note that a tax receipt must contain the following legal information:
  * **The contact details of the issuing association**
  * **The unique serial number of the tax receipt,** this numbering must be unique for each donor (two numbering systems can co-exist if the association issues receipts both through the HelloAsso donation platform and offline; however, be careful not to use the same numbering system), = a formula generating a sequence of unique numbers
  * **The beneficiary organization** (name, address, purpose, status…)
  * **The donor** (identity and contact details)
  * **The amount paid** in figures and in words (for tax receipts issued by computer, you only need to frame the amount paid with asterisks: \*\*\*10 Euros\*\*\*)
  * **The payment date**
  * **The payment method of the donation**
  * **The signature** of the person authorized to collect the payment
* Save your document and upload it.


---

# 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/generate-tax-receipt.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.