> 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/recherche-des-inscriptions-sans-commande.md).

# Search for registrations without orders

1. In your team menu on the left, click "Session".
2. Then choose the “Participant” tab.
3. By default, the list is filtered by today's date. You need to change the “Order” filter to “No order”.

This operation allows you to quickly view participants registered for activities that do not have an associated order. If there are any entries in this list, it may be an error or an oversight.

Take the time to check each entry without an order. It could be a simple oversight on the part of the customer or team, or a technical issue that prevented the order from being created. In any case, it is essential to identify the cause of the deviation and correct it.

It is a good practice to do this check every evening to ensure that no registrations go through without billing. This not only ensures sound financial management, but also improves the accuracy of the reports and analyzes you could derive from Yoplanning.pro data.

In the following articles, we will explore other checks that you can carry out regularly to improve the quality of your accounting monitoring.


---

# 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/manipulation-et-gestion-des-commandes-dans-yoplanning/suivie-des-ventes-et-encaissements/recherche-des-inscriptions-sans-commande.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.
