> 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/invoices-deposit.md).
# Invoices Deposit
## Context:
NOUT SA orders 50 corner desks and 50 chairs to equip its new employees, for a total amount of €23,850.
The furniture is due to be delivered in one month. To activate the order, MASOCIETE requests a 30% deposit, amounting to €7,155. NOUT SA pays the requested deposit. Subsequently, a deposit invoice is issued and sent to NOUT SA.
## Implementation in Simax
First, you need to create the order. The order status is “30 Pending Payment”.
Please note that NOUT SA's terms of sale are: 30% deposit, balance upon invoice.
Next, once the customer has sent the 30% deposit, we will enter this information in the menu **Cash Flow > Inflow Management > Customer Deposit settlement.**
Click Save to confirm payment, and the order status will automatically change to “70 Order to be prepared.”
We can now send the deposit invoice to the customer to confirm that they have paid the deposit.
To do this, go to the **Sales > Invoicing > Deposit Invoice** menu, and click **\[\[New]]**.\
Just fill in the order and the rest will be filled in automatically.
Finish by clicking **\[\[Save]]**, and the invoice will print automatically.
---
# 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/invoices-deposit.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.
