> 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/go-live-and-send-by-email.md). # Go live and send by email To validate your tests, put the legal entity into production ## Put into production To validate your tests, put the legal entity into production * Go to the legal entity * Click Put into production and confirm ## Send by email Use standard Salesforce email sending to send an email and attach the generated document. ## Close the fiscal year When all your donors have received their tax receipts, close the fiscal year to move on to the next one * Go to the legal entity * Click Close fiscal year * The legal entity's fiscal year automatically changes to N+1, and creating tax receipts for the previous year is blocked --- # 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/go-live-and-send-by-email.md?ask=&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.