> 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/comptabilite-comptabilite/budgets/saisie-par-code-analytique.md).

# Saisie par code analytique

1. Choisissez le budget.

Vous pouvez cliquer sur la loupe pour avoir accès à la liste des budgets créés.

2. Cliquez sur![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-8f8eb27e9d64ccdaffeccf585fba1543be5398df%2Fnew.JPG?alt=media)**\<INSER>**.
3. Saisissez le code analytique.

{% hint style="info" %}
Vous pouvez cliquer sur![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-eddff7185d9517ef4922ad565dbbef767993971c%2Floupe%20\(2\).JPG?alt=media)pour afficher la liste des codes analytiques créés dans le **menu** **Fichiers/Analytiques** et sélectionner directement celui qui vous intéresse.
{% endhint %}

4. Saisissez les valeurs budgétaires de ce code analytique.
5. Cliquez sur![](https://297857182-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ9LMIGmeG0qrLUTeglcC%2Fuploads%2Fgit-blob-e074308bd5374f350ba890d934e36d6c134547f9%2Fsave%20\(4\).JPG?alt=media)**\<ENTREE>**.

{% hint style="info" %}
Vous devez effectuer cette opération pour chacun des codes analytiques de votre budget.
{% 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/comptabilite-comptabilite/budgets/saisie-par-code-analytique.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.