> 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/cashflow/customer-deposits.md).

# Customer deposits

Customer deposit, customer deposit settlement.

In some cases, a deposit may be required before an order is completed; the company then issues a deposit payment request, which it sends to the customer so that they can make the payment.

## Customer deposit

A **customer deposit** is a sum of money paid by the customer **before delivery of the goods or completion of the service.**

In this case, **Le Petit Rapporteur** placed an order for **5 deck chairs** with **MASOCIETE**, followed by a **30% deposit required to confirm the order.**

## **Implementation**

To create an order that requires, for example, a **30% deposit,** you can do the following: **Sales > Order > Orders**, then **\[\[New]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2FuTRfiNe0wyYMswtMwMSX%2FCapture%20d%E2%80%99%C3%A9cran%202026-02-25%20125209.png?alt=media&amp;token=623ab64f-b13d-4248-b7ee-dd72b46d6100" alt=""><figcaption></figcaption></figure>

And, yes, you have to **save** it.

## Customer deposit settlement

When the customer receives the request for payment of the deposit, they can proceed to payment.

Following on from the order for **5 deckchairs**, once the deposit request has been sent, **Le Petit Rapporteu**r will pay the deposit using the same payment method.

## Implementation

In order for your accounting manager to record a customer's down payment, for example, they can go to **Cash flow > Inflow Management > Customer Deposit stettlement.**

By selecting the **Customer,** the **Order**, and the **Amount**, as well as the **information** corresponding to that order, the form is filled in automatically.

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2F8c3FvYF169ujW1hcAwMX%2FCapture%20d%E2%80%99%C3%A9cran%202026-02-25%20130024.png?alt=media&amp;token=72c52572-343d-48e6-9bc4-e4d1788b360d" alt=""><figcaption></figcaption></figure>

Finally, **save.**<br>


---

# 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/cashflow/customer-deposits.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.
