> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/sales/credit-and-deposit/what-is-a-customer-deposit/customer-deposit-centre.md).
# Customer Deposit Centre
## What is the Customer Deposit Centre?
The Customer Deposit Centre in XoroERP serves as a centralized repository for managing all customer deposits efficiently. It provides a comprehensive overview of customer deposit details, including creation date, total amount, applied or refunded amounts, and more. Users can easily access transaction-related information and search for deposits using various criteria such as status, customer, deposit number, and reference number. Additionally, the centre offers options to unapply deposits and manage transactions effectively.
### Use Cases
With header-level options like printing, viewing transactions, applying deposits to invoices, and voiding deposits, users can streamline workflows and enhance customer satisfaction.
Sales representatives benefit from simplified deposit management, enabling them to provide timely and accurate information to customers and fostering stronger client relationships.
The ability to unapply deposits provides flexibility in handling customer transactions, contributing to smoother sales operations.
---
# 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.xorosoft.com/xoroerp-1/sales/credit-and-deposit/what-is-a-customer-deposit/customer-deposit-centre.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.
