> 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/billing/packing-slip/packing-slip-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 Packing Slips When the Credit Limit Is Exceeded?](https://youtu.be/0mg_viGJHrs)
## How to Prevent Saving Packing Slips When the Credit Limit Is Exceeded?
In this tutorial, we will learn how to restrict saving a **Packing Slip** entry when the selected customer's credit limit has been exceeded.
This configuration helps prevent further packing slip entries for customers who have already exceeded their defined credit limit.
***
### Access to the Configuration
* Open the **Packing Slip Configuration** window.
* Navigate to the **Other Options 4** section.
* Locate and enable the option labeled as:
> **"Do not allow saving if Credit Limit is Exceeded"**
* Save the configuration changes.
***
### Create a New Packing Slip Entry
Now, let's create a new Packing Slip entry and observe the system behavior.
* Open a new **Packing Slip** entry.
* Select the required customer.
#### System Behavior
* As soon as the customer is selected, the system checks the customer's credit limit.
* If the credit limit has been exceeded, the system restricts the entry.
* An error message is displayed:
> **"Credit limit is exceeded, cannot allow selection."**
This prevents the user from proceeding with the Packing Slip entry for that customer.
***
### Define the Customer Credit Limit
Now, let's see how to define the credit limit for a customer.
* Navigate to **Setup.**
* Open the **Setup Account** window.
* Search for and select the required customer account.
* Open the **Other Details** section.
* Locate the **Credit Limit** option.
* Define the required credit limit for the customer.
#### Configuration
The defined credit limit is used by the system to determine whether the customer can proceed with a Packing Slip entry when the **Do not allow saving if Credit Limit is Exceeded** option is enabled.
***
### Key Benefits
* Prevents Packing Slip entries when the customer's credit limit is exceeded.
* Helps control customer credit exposure.
* Automatically validates the credit limit during customer selection.
* Reduces the possibility of unauthorized credit-based transactions.
#### Final Outcome
By enabling **"Do not allow saving if Credit Limit is Exceeded"**, Logic ERP automatically checks the customer's credit limit during Packing Slip entry and restricts the transaction when the defined limit has been exceeded.
---
# 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/billing/packing-slip/packing-slip-configuration/do-not-allow-saving-if-credit-limit-is-exceeded.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.
