> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale/sale-settings-2/do-not-allow-debit-balance-of-a-party-while-billing.md).
# Do not Allow Debit Balance of a Party while Billing
**YouTube:** [How to Prevent Credit Sales by Restricting Billing for Customers with Debit Balance ?](https://www.youtube.com/watch?v=Bo3Dt43QsjU)
This tutorial explains how to enable a control in Logic Admin that prevents billing for parties whose account balance would become debit, helping maintain financial discipline and credit control.
***
### 🔧 Step-by-Step Instructions
* Navigate to the Logic folder and run Logic Admin.
* Open Global Settings.
* Click to Sales Settings - 2 tab.
* Find and enable the option: **“Do not Allow Debit Balance of a Party while Billing.”**
Let's keep this feature enable to observe its impact in billing.
* **Check** this option to activate the restriction.
* Click **Save** to apply the changes.
#### **Step 5: Restart the Software**
* Close and **restart the Logic software** to enforce the updated setting.
***
### Functionality Overview
* Once enabled, the software will prevent billing if the transaction would cause a party’s balance to go into debit.
* If a user tries to save a voucher under these conditions, a warning will appear:\
\&#xNAN;*“Party balance will become debit, cannot allow entry.”*
As you can see in the picture, the debit balance prompt has appeared.
***
### Key Benefits
* **Ensures financial control** by preventing credit sales to overdrawn parties.
* **Avoids bad debts** and enforces company credit policies.
* **Improves cash flow** management by encouraging upfront payments or settlements.
* **Reduces risk** of unintended entries and billing errors.
---
# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale/sale-settings-2/do-not-allow-debit-balance-of-a-party-while-billing.md?ask=&goal=
```
`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.