> 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/invoicing/the-periodic-invoicing.md).
# The periodic invoicing
## Context:
Testo orders a corner sofa for its new premises. In accordance with the agreement, an invoice will be sent to it every month.
## Implementation in Simax
The first thing to do is to set Testo's billing frequency.
To do this, go to **Sales > Customer > Customers**, then **\[Conditions]**, **|Periodic invoicing|**, and select “Monthly.”
The next invoice date is 12/01/2024, calculated automatically.
As before, we will create the order and **\[\[Save]]**.
Then, we prepare the order in **Sales> Order> Orders**, by selecting the order and clicking on **\[\[Preparation voucher]]**.
We choose the preparer, then **\[\[ok]]**.
And let's validate it.
And finally, we save the delivery note.
An invoice line is then created on 11/11/2024 in **Sales > Invoicing > Lines to invoice.**
Please note that each time a delivery note is issued in favor of Testo, an associated invoice line will be created and issued on the next invoice date.
To invoice, simply select the line to be invoiced and click on **\[\[Single Invoice]]**.
---
# 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/invoicing/the-periodic-invoicing.md?ask=&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.
