> For the complete documentation index, see [llms.txt](https://fitek-learning.fitek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fitek-learning.fitek.com/fitek-learning-space/french-francais/purchase-invoices/recherche.md).

# Recherche

Le registre des factures d'achat est votre principal outil de travail ; cette section explique comment y rechercher et filtrer efficacement :

* [**Utiliser le registre des factures**](/fitek-learning-space/french-francais/purchase-invoices/recherche/utiliser-le-registre-des-factures.md) – ce que le registre affiche, le fonctionnement du tri et des colonnes, et les libellés spéciaux (Note de crédit, Doublon, Nouveau fournisseur) affichés à côté du nom du fournisseur.
* [**Filtres et options de recherche**](/fitek-learning-space/french-francais/purchase-invoices/recherche/filtres-et-options-de-recherche.md) – la liste complète des filtres (statut, utilisateurs, dimensions, types de facture, dates, montants, etc.), comment enregistrer une combinaison comme modèle de filtre, et comment exporter vers Excel ce que vous avez filtré.

Ces pages couvrent aussi bien la recherche d'une facture précise que la préparation d'exports réguliers, par exemple par centre de coûts.


---

# 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://fitek-learning.fitek.com/fitek-learning-space/french-francais/purchase-invoices/recherche.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.