> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-generale/recuperation-de-factures-dans-yoplanning.md). # Find my Yoplanning invoices ### **Introduction** Accessing your Yoplanning invoices is essential to ensure clear tracking of your billing and payments. On Yoplanning.pro, all your invoices are centralized in a dedicated space, accessible via the dashboard. This guide explains **step by step how to find your invoices** and what solutions to apply in case of problems. ### **Steps to Recover Invoices** 1. \*\*Access the **Yoplanning.pro** dashboard. 2. In the **left menu**, click on **"Administration"**. 3. Then select **"Configuration"**. 4. Click on **"My Invoices"** to display the list of your available invoices. **Important Note**: Invoices may be generated **a few days after payment**, so it is recommended to **regularly check** their availability. ### **Common Problem and Solution** * **Problem: Invoice Not Found** **Solution:** If you can't find your invoice, it may be due to a delay in the billing process. Wait a few days and check again. * **Additional Support:** If you have any difficulties or questions, please do not hesitate to contact support at . ### **Conclusion** The "My Invoices" module on Yoplanning.pro provides quick and secure access to all your invoices. Careful tracking of your invoices ensures smooth, predictable accounting. --- # 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://docs.yoplanning.support/en/faq/faq-generale/recuperation-de-factures-dans-yoplanning.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.