> 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-parametrage/parametrage-general-de-yoplanning/parametrage-comptable-et-mentions-legales-des-factures.md).

# Accounting settings and legal information for invoices

### What is the purpose of accounting settings?

Yoplanning allows you to link accounting accounts to sales, taxes and invoiced items.

Accounting information must be entered at four levels:

1. **Team**
2. **Products**
3. **Resources**
4. **Taxes**

Each level can contain a specific accounting account used during accounting exports.

### Configure the Team's accounting accounts

#### Access

**Configuration → Team → ⋮ → Edit**

#### Available fields

In the Team profile, you can enter:

* General account
* Sales account
* Cash account
* Sales account for a third party

These accounts serve as a reference for accounting transactions generated by Yoplanning.

#### Legal information regarding invoices

The Team form also contains the field to define the **legal notices displayed in the invoice footer**.

You can, in particular, specify the following:

* Company name
* SIREN number
* RCS number
* Intra-Community VAT number
* VAT-related information
* Any other legal notices required by your business

This information is automatically included on the invoices generated by Yoplanning.

### Configure the accounting accounts for the products

#### Access

**Products → Relevant product → ⋮ → Edit**

#### Configuration

Each product has an **Accounting Account** field.

Enter the account corresponding to the nature of the sale:

* Services
* Internships
* Course
* Locations
* Goods

The choice of account depends on your accounting plan.

### Configure the resource accounting accounts

#### Access

**Resources → Relevant resource → ⋮ → Edit**

#### Configuration

Each resource has an **Accounting Account** field.

This account allows for the correct allocation of amounts related to this resource during accounting exports.

### Configure tax accounting accounts

#### Access

**Configuration → Taxes**

#### Configuration

Each tax can be associated with a specific **accounting account**.

This configuration allows you to correctly allocate VAT or other tax amounts in your accounting.

### Information about the supervising instructor

Information relating to the supervising instructor is automatically displayed on each line of service on the final invoice.

No specific configuration is required.

### Best practices

* Have the accounts used validated by your accountant.
* Verify accounts when creating new products, resources, or taxes.
* Regularly check the legal information displayed on invoices.
* Perform an accounting export test after any significant change.

### Pre-production checkpoints

Check that:

* The Team contains the main accounting accounts.
* All products have an accounting account.
* All resources have an accounting account.
* All taxes have an accounting account.
* The mandatory legal information is provided in the Team section.
* The invoices correctly display the expected information.

A configuration validated by your accountant guarantees consistent accounting exports and invoices that comply with legal obligations.


---

# 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-parametrage/parametrage-general-de-yoplanning/parametrage-comptable-et-mentions-legales-des-factures.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.