> 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/manipulation-et-gestion-des-commandes-dans-yoplanning/suivie-des-ventes-et-encaissements/controle-hebdomadaire-de-la-validation-des-commandes-en-facture-definitive.md).

# Weekly control of order validation into final invoices

### Introduction

Regular monitoring of pending orders is essential to ensure smooth and compliant invoicing. Although Yoplanning automatically validates orders based on certain criteria, a weekly review can identify orders that have not been finalized for various reasons.

### **What is this feature for?**

With this feature, teams that have subscribed to the **"accounting"** option can easily identify **unfinished orders** and avoid any delays in invoicing. A **weekly check** helps identify these cases and ensure efficient accounting management.

### **Steps to use this feature**

1. **Access the Orders menu:** From the schedule, in the left menu, click on "**Orders"**.
2. **Define the period to be controlled**:
   * Select the period for which you want to check invoice validation.

**Tip**: Choose the start date of your fiscal year as the start date and the end date as today's date minus the number of days predetermined in your settings for automatic validation.

1. **Apply the necessary filters**:
   * Activate the **session date icon**.
   * In the **Reseller** filter, select **Without**.
2. **Add advanced filters**:
   * Click on **Filters.**
   * In the **Status** filter, choose **Not finalized**.
3. **Analyze the results**:
   * The list will display all orders that have not been completed.
   * These orders require manual validation.

### **Directions for use**

* **Regular Scheduling**: Perform this check weekly to ensure all orders are validated in a timely manner and avoid delays in invoicing.
* **Unfinished Order Analysis**: If some orders regularly reappear as unfinished, check if there is a recurring problem to resolve (missing products, incomplete information, etc.).

See FAQ article: [Why do some orders not turn into a final invoice?](/en/faq/faq-generale/pourquoi-certaines-commandes-ne-se-transforment-pas-en-facture.md)

### **Common Problems and Solutions**

* **Problem: Order blocked due to missing information** **Solution:** Ensure all necessary information is present in the order (customer name, associated products/services, etc.). Check the unfinished items to understand the causes.
* **Problem: Error in session dates** **Solution:** If you cannot find any results, check that the session dates are correctly selected in the filters.

By following these steps, you can ensure a smooth and complete invoicing process in Yoplanning.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/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?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.