> 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/yoplanning-academy/yoplanning-au-quotidien/les-questions-de-comptabilite/comptabilite-francaises/faq-suppression-du-terme-provisoire-dans-le-titre-de-la-facture-sur-yoplanning.md). # FAQ: Removing the term "provisional" from the invoice title on Yoplanning **Question:** Is it possible to remove the term "provisional" from the invoice title in Yoplanning? **Answer:** On Yoplanning, the documents titled "provisional invoices" actually correspond to orders. We use the term "provisional invoice" because in the service industry payment is often made in advance. This term is therefore more understandable for end customers. In the field of service provision, official invoices are only issued after the service has been completed. This is how it works in Yoplanning: * **With the invoicing module:** The final invoice is automatically generated a certain number of days after the service, according to the parameters defined for your Team. * **Without the invoicing module:** It is the user's responsibility to create an invoicing document outside of the Yoplanning application. It is crucial to note that the use of the word "Invoice" in the header of a document is subject to strict tax regulations. This term cannot be used on a document that is not a real invoice. To comply with these regulations, the term "provisional" is therefore necessary to distinguish these preliminary documents from the official final invoices. In summary, it is not possible to remove the term "provisional" from the title of provisional invoices in Yoplanning without compromising the clarity and regulatory compliance of these documents. --- # 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/yoplanning-academy/yoplanning-au-quotidien/les-questions-de-comptabilite/comptabilite-francaises/faq-suppression-du-terme-provisoire-dans-le-titre-de-la-facture-sur-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.