> For the complete documentation index, see [llms.txt](https://docs.dailybiz.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dailybiz.com/index/notes-de-frais-bon-note-de-frais.md).

# Notes de frais

## Introduction

Ici vous pouvez faire la gestion complète de vos notes de frais, de l'enregistrement jusqu'au circuit de validation et paiement. Les informations sont disponibles en temps réel, ce qui favorise la rapidité de traitement.

Vous pouvez faire une gestion workflow générale ou spécifique à des salariés ou groupes de salariés.

## Présentation

![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-a4ded37c386cddb3a5576c07159b7d2b23b5b015%2FdiagrameNF.png?alt=media)

{% hint style="info" %}
Ce schéma décrit les différentes étapes de validation des notes de frais. Le logiciel offre la possibilité de faire valider une note de frais par quatre intervenants (valideurs) différents.

Bien évidemment, ce circuit de validation peut être simplifié en fonction de l'organisation de votre entreprise (un seul valideur par exemple). En outre le circuit de validation est personnalisable par salarié.
{% endhint %}


---

# 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.dailybiz.com/index/notes-de-frais-bon-note-de-frais.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.
