> 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/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/do-not-allow-saving-if-credit-limit-is-exceeded.md).

# Do not allow saving if Credit Limit is Exceeded

**YouTube:** [How to Prevent Saving Delivery Orders When the Credit Limit Is Exceeded?](https://youtu.be/gahQKIxcgAQ)

## How to Prevent Saving Delivery Orders When the Credit Limit Is Exceeded?

In this tutorial, we will learn how to **restrict Delivery Order generation when a customer's credit limit has been exceeded** in Logic ERP. This feature prevents users from proceeding with Delivery Order generation for customers who have exceeded their defined credit limit.

***

### Access to the Configuration

* Open the **Delivery Order Configuration** window.
* Navigate to the **General Settings** section.
* Locate and enable the option labeled as:

> **"Do not allow saving if Credit Limit is Exceeded"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F3M9B80BTd5Km4vu38Gjh%2FCNF.png?alt=media&amp;token=f14e3b65-b185-4de6-ab89-64343b7be553" alt=""><figcaption></figcaption></figure>

* Save the configuration changes.

***

### Initiate a New Delivery Order

* Open the **Delivery Order Entry** window.
* Initiate a new entry.
* Select the required **Sales Order**.
* Click on **Generate Order**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FvKOMjajUtQubbfErrlnN%2FCLM.png?alt=media&amp;token=19c9a678-c400-495e-8fbf-7d0266fcdeb4" alt=""><figcaption></figcaption></figure>

**Credit Limit Status**

* The system checks the customer's defined credit limit.
* For example, the customer's credit limit is **1,000**, but the limit has already been exceeded.
* The affected entry is displayed in **red**, indicating that the customer's credit limit has been exceeded.

***

### Verify the Restriction

* Select the highlighted entry to proceed.
* The system prevents the user from selecting or processing the entry.
* An error message is displayed:

> **"Credit limit is exceeded. Selection is not allowed"**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FNMpyB4dApgrul47KY6bL%2FError.png?alt=media&amp;token=5226f394-df60-4354-acbc-e723abffa722" alt=""><figcaption></figcaption></figure>

**Result**

The Delivery Order cannot be generated for the selected Sales Order because the customer's credit limit has been exceeded.

***

### Key Benefits

* **Credit Control:** Prevents transactions when the customer's credit limit is exceeded.
* **Risk Reduction:** Helps minimize further credit exposure.
* **Automated Validation:** Automatically checks the customer's credit limit.
* **Better Financial Control:** Ensures Delivery Orders are processed only within approved credit limits.

#### Final Outcome

After enabling **"Do not allow saving if Credit Limit is Exceeded"**, Logic ERP automatically restricts Delivery Order generation for customers who have exceeded their credit limit, ensuring better credit control and preventing unauthorized transactions.


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/do-not-allow-saving-if-credit-limit-is-exceeded.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.
