> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/documentation-simax-anglais/functional/accounting/analytical-accounting.md).

# Analytical Accounting

Coming soon

**Analytical accounting** is a method for tracking and analyzing a company’s internal costs. Unlike general accounting, which focuses on financial statements and legal obligations, analytical accounting **allows expenses and costs to be allocated by product, service, project, or responsibility cente**r. It provides a detailed view of production costs, margins, and the performance of each activity, helping to better understand the company’s true profitability.

This approach is particularly valuable for companies because it **supports strategic and operational decision-making**. By precisely identifying high-cost items, inefficient processes, or the most profitable products, it helps optimize resources, reduce waste, and improve competitiveness. Analytical accounting is therefore a key tool for proactively managing the business, planning budgets, and maximizing overall profitability.


---

# 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://doc.simax.fr/documentation-simax-anglais/functional/accounting/analytical-accounting.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.
