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

# Automate tax receipt creation

If you want to save time, you can automatically create, validate and send a tax receipt by email.

## Creating the 4-in-1 flow

### Setting up tax receipt creation

* Action added: `Create_Tax_Receipt__c`

### Setting up tax receipt validation

* Action added: `Validate_Tax_Receipt__c`

### Document generation action

* Action added: Generate a Document

### Action to send the document by email

* Action added: Send e-mail with attachment

## Pre-built Flow Org

Go to our sample Flow Org for inspiration. Find the use cases most used by our customers. The org is read-only and accessible without credentials, through the Gonexa Test Drive on the AppExchange.

<a href="https://appexchange.salesforce.com/try?listingId=a0N3A00000FMiJiUAL&#x26;type=TestDrive" class="button primary" data-icon="arrow-up-right-from-square">Access the Flow Org</a>

Need help accessing it? Follow the guide [The Flow Org: pre-built flow examples](/doc/en/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/en/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.