> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/les-questions-de-comptabilite/fonctionnement-general-de-la-comptabilite.md).

# General Functioning of Accounting

### Legal Compliance: Collection for Third-Party Accounts

Our Yoplanning system strictly complies with legislation regarding third-party payment collection. This means that we adhere to the following rules and procedures to guarantee the legitimacy and transparency of transactions:

* **Separation of Accounts**: Funds collected on behalf of and for the benefit of third parties are always kept separate from company funds. This ensures a clear distinction between company assets and funds managed on behalf of staff.
* **Authorization and Monitoring**: All cash collection operations on behalf of third parties are carried out in an approved and unmodifiable cash register to guarantee compliance with applicable legislation.
* **Transparency and Reporting**: We ensure complete transparency of transactions carried out on behalf of third parties, providing detailed reports to both clients and competent authorities, in accordance with legal requirements.

Yoplanning, as a platform committed to legal compliance, ensures the application of these fundamental principles to guarantee compliance with the standards in force regarding payment for two-thirds accounts in France.

### General operation

**1. Billing to the End Customer:**

* The team invoices the end client for all services performed.
* The schedule indicates directly on each line of the invoice the name of the client and the staff member who performed the service. (On invoices, not on orders.)
* Yoplanning distinguishes between business (B2B) and business (B2C) clients and automatically includes the relevant legal information on the invoice, citing the corresponding articles of the French General Tax Code (CGI). You don't need to enter this information yourself.

**2. Income Distribution:**

* After the service has been provided and the final invoices have been issued, it is possible to view the revenue generated by each staff member.
* The difference between the fees paid to the staff and the revenue generated represents the margin made by the team.

**3. Legislative Compliance:**

* The system has been validated by the tax authorities, ensuring its compliance with legislation relating to collections on behalf of third parties.

**4. Transaction Traceability:**

* Complete traceability is maintained between the end customer and the staff responsible for the service.
* This traceability distinguishes B2B sales from B2C sales, allowing Yoplanning to automatically display the appropriate legal text on each invoice.

### Two separate modules: Billing and Fees.

**Billing Module:**

* Allows you to automatically create final invoices and sales journals for accounting exports.

**Fee Module:**

* Generates fees for staff in accordance with the remuneration terms established by the group.

In summary, Yoplanning offers an integrated and automated solution for accounting management in structures composed of groups of independents, ensuring accurate invoicing, fair distribution of revenue and compliance with legal requirements.


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/les-questions-de-comptabilite/fonctionnement-general-de-la-comptabilite.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.