> 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/getting-started/automate-tax-receipt-creation.md).

# Automatiser la création d'un RF

Si vous souhaitez gagner du temps, vous pouvez automatiquement créer, valider et envoyer par mail un reçu fiscal.

## Création du flux 4 en 1

### Configuration de la création du reçu fiscal

* Ajout de l'action : `Create_Tax_Receipt__c`

### Configuration de la validation du reçu fiscal

* Ajout de l'action : `Validate_Tax_Receipt__c`

### Action de génération du document

* Ajout de l'action : Generate a Document

### Action d'envoi du document par e-mail

* Ajout de l'action : Send e-mail with attachment

## Org de flux préconçus

Accédez à notre org de flux d'exemple pour vous inspirer. Retrouvez les cas d'usage les plus utilisés par nos clients. L'org est en lecture seule et accessible sans identifiant, via le Test Drive Gonexa sur l'AppExchange.

<a href="https://appexchange.salesforce.com/try?listingId=a0N3A00000FMiJiUAL&#x26;type=TestDrive" class="button primary" data-icon="arrow-up-right-from-square">Accéder à l'Org de Flux</a>

Besoin d'aide pour y accéder ? Suivez le guide [L'Org de Flux : exemples de flux préconçus](/doc/advanced-features/doc-and-flows/flow-examples-org.md).


---

# 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/getting-started/automate-tax-receipt-creation.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.
