> 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/pourquoi-certaines-commandes-ne-se-transforment-pas-en-facture.md).

# Why do some orders not turn into invoices?

### Here are the criteria that suspend the automatic validation of an order:

**1. Order linked to a reseller**

* If an order is associated with a reseller, validation cannot be done automatically. The invoice must be validated manually by the operator.

**2. Order balance zero**

* If the order balance is zero, the creation of an invoice is not necessary. In this case, the order will not be transformed into a final invoice.

**3. Absence of participants**

* If the order includes services where a participant has been marked absent, Yoplanning cannot guess what action the operator wants to take: cancel, refund or invoice anyway. The invoice validation is therefore manual to allow this decision.

**4. Missing accounting information**

* If essential accounting information is missing from the order, automatic validation will fail. This may concern:
  * The absence of an accounting account on a product.
  * The absence of an accounting account on a resource.
  * A problem with the accounting accounts associated with taxes.

In this specific case, a warning email is sent to the operator to indicate the problem to be resolved.

### Good practices

* **Regular manual check**: Even if automatic validation is enabled, it is advisable to regularly check (at least once a week) pending orders to avoid accounting errors or omissions. [Weekly control of order validation into final invoices](/en/yoplanning-academy/yoplanning-au-quotidien/manipulation-et-gestion-des-commandes-dans-yoplanning/suivie-des-ventes-et-encaissements/controle-hebdomadaire-de-la-validation-des-commandes-en-facture-definitive.md)

### Troubleshooting

* **Missing Accounting Information**: Verify that all products, resources, and taxes have accounting accounts assigned. If not, complete the missing information in the product or resource configuration settings.
* **Absent Attendees**: Make a decision on what actions to take for services with absent attendees (cancel, refund or invoice).
* **Resellers**: Manually validate orders associated with resellers.


---

# 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/pourquoi-certaines-commandes-ne-se-transforment-pas-en-facture.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.