> 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/applying-customer-deposit/business-problem-and-use-cases-for-customer-deposit.md).

# Business Problem & Use Cases for Customer Deposit

### **Core Business Issue**

In XoroERP, businesses may encounter situations where:

* **Balance Sheet and Trial Balance appear correct**
* But:
  * **Customer Deposit Centre does not match**
  * **Vendor Prepayment Centre does not match**
  * **Customer/Vendor balances are incorrect**

This typically happens when users attempt to [**adjust balances using Journal Entries on system-generated accounts**.](/xoroerp-1/accounting/common-issues/correcting-customer-deposit-and-vendor-prepayment-balance-discrepancies-in-xoroerp.md)

***

### Business Case 1 — Month-End Adjustment

#### Scenario

During month end closing, the finance team identifies that:

* Customer Deposit balance is higher than expected

To quickly fix this, they:

* Post a **Journal Entry directly to the Customer Deposit account**

***

#### What Happens

* The Balance Sheet reflects the corrected value
* Trial Balance appears accurate
* However:
  * **Customer Deposit Centre still shows the old balance**
  * **Customer-level deposit balances remain unchanged**

***

#### Business Impact

* Reconciliation between reports fails
* Customer statements become inaccurate
* Additional time is spent investigating mismatches

***

#### Correct Approach

* Do **not** use Customer Deposit account in Journal Entries
* If adjustment is **not customer-specific**:
  * Use a **placeholder liability account**
* If adjustment is **customer-specific**:
  * Use **invoice and deposit application transactions**

***

### Business Case 2 — Exchange Rate / Adjustment Entries

#### Scenario

Due to exchange rate differences or accounting adjustments:

* Deposit or prepayment balances do not align

User attempts:

* Adjustment via Journal Entry on system account

***

#### What Happens

* GL balances are corrected
* But:
  * Sub-ledger (Customer/Vendor Centre) remains unchanged
  * Reports do not match

***

#### Business Impact

* AR/AP reports become inconsistent
* Financial reporting loses accuracy
* Reconciliation becomes complex

***

#### Correct Approach

* Always adjust using:
  * Customer/Vendor transactions (for specific cases)
  * Placeholder accounts (for overall adjustments)

***

### Business Case 3 — Reporting Mismatch

#### Scenario

A user exports reports and observes:

* Excel reports do not match system balances
* Customer Deposit / Vendor Prepayment totals differ from financial statements

***

#### Root Cause

* Journal Entries were posted directly to:
  * Customer Deposit account
  * Vendor Prepayment account

***

#### Business Impact

* Mismatch between:
  * General Ledger
  * Sub-ledger reports
* Increased dependency on manual reconciliation

***

#### Correct Approach

* Avoid direct JE on system-controlled accounts
* Ensure all adjustments follow:
  * Customer-linked transactions
  * Vendor-linked transactions
  * Placeholder accounts for non-specific adjustments

***

### Key Takeaway for Users

* **Customer Deposit and Vendor Prepayment accounts are system-controlled**
* They are linked to:
  * Customer/Vendor records
  * Transaction-level data

***

#### Therefore:

* **Do not use these accounts in Journal Entries**
* Always determine:
  * Is the adjustment **overall** or **customer/vendor-specific**?

***

### Final Rule

* Use **Journal Entries + Placeholder Accounts** → for overall balance adjustments
* Use **Transactions (Invoices, Bills, Deposits, Prepayments)** → for customer/vendor-specific corrections

***

This ensures:

* Accurate reconciliation
* Consistent reporting
* Reliable financial data across XoroERP


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xorosoft.com/xoroerp-1/sales/credit-and-deposit/applying-customer-deposit/business-problem-and-use-cases-for-customer-deposit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.