> 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/sales-invoices/depannage.md).

# Dépannage

La plupart des problèmes de factures de vente relèvent de quelques cas connus : un champ obligatoire n'a pas été rempli, les données de facturation électronique du client ne correspondent pas à ce qu'attend le réseau, ou il manque à une facture importée une information dont Fitek a besoin. [**Erreurs courantes et solutions**](/fitek-learning-space/french-francais/sales-invoices/depannage/erreurs-courantes-et-solutions.md) passe en revue les messages d'erreur que vous pouvez rencontrer – des champs obligatoires manquants à la création aux fenêtres de validation lors de l'envoi, jusqu'à « Customer not found in the e-invoice network » après un échec de transmission – avec leur cause et la solution.

Si le statut de votre facture ne vous est pas familier, consultez d'abord [Comprendre les statuts](/fitek-learning-space/french-francais/sales-invoices/premiers-pas/comprendre-les-statuts.md) ; si vous connaissez le statut mais pas l'action à mener, *Erreurs courantes et solutions* vous indique la correction.


---

# 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/sales-invoices/depannage.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.