> 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/over-due-bill-filter-as.md). # Over Due Bill Filter As **YouTube:** [How to Configure Overdue Bill Restrictions in Packing Slips?](https://youtu.be/buXQQyFHhxE) ## How to Configure Overdue Bill Restrictions in Packing Slips? In this tutorial, we will learn how to configure the **Over Due Bill Filter As** option in Packing Slips. This configuration allows you to control whether the system should check for overdue bills while creating a Packing Slip and whether the check should be performed across all branches or only in the current branch. *** ### Open the Overdue Bill Filter Configuration * Open the **Packing Slip Configuration** window. * Navigate to the **Other Options Four** section. * Locate the option labeled as: > **"Over Due Bill Filter As"**
#### Available Options This option provides three choices: 1. **None** * The system does not check for overdue bills while creating a Packing Slip. 2. **Do Not Allow If Overdue Any Bill Exist** * The system checks for overdue bills across **all branches**. * If the customer has even one overdue bill in any branch, the Packing Slip cannot be created. 3. **Do Not Allow If Overdue Any Bill Exist Branch Wise** * The system checks for overdue bills only in the **currently logged-in branch**. * An overdue bill in another branch does not restrict Packing Slip creation in the current branch. *** ### Configure the Overdue Check Across All Branches Let's first understand the second option. * Select **Do Not Allow If Overdue Any Bill Exist**. * Save the configuration changes. #### Implement the Configuration * Initiate a new **Packing Slip** entry. * The current login branch is **Delhi**. * Select the required customer. **System Behavior** * As soon as the customer is selected, the system checks for overdue bills across all branches. * Since the customer has an overdue bill, the system restricts the Packing Slip entry. * A message is displayed indicating that the **overdue days limit of 10 days has been exceeded**. > **Note:** We will see where this **10-day overdue limit** is defined later in this tutorial.
#### Key Point With **Do Not Allow If Overdue Any Bill Exist** enabled, the branch where the overdue bill exists does not matter. * If the customer has an overdue bill in **any branch**, the Packing Slip cannot be created. *** ### Configure the Overdue Check Branch Wise Now, let's see how the third option works. * Return to the **Packing Slip Configuration** window. * Navigate to **Other Options Four**. * Select **Do Not Allow If Overdue Any Bill Exist Branch Wise**. * Save the configuration changes. #### Test the Configuration * Initiate a new **Packing Slip** entry. * Select the same customer. **System Behavior** * This time, no overdue bill restriction or prompt appears. * The customer does not have an overdue bill in the **currently logged-in Delhi branch**. * Therefore, the system allows the Packing Slip entry to proceed. #### Key Point With the branch-wise option enabled: * The system checks overdue bills only in the current branch. * An overdue bill existing in another branch does not restrict the Packing Slip entry. *** ### Define the Overdue Days Limit Now, let's see where the **10-day overdue limit** is defined. * Open the **Setup New Account** window. * Search for and select the required customer account. * Open the **Other Details** section. * Locate the **Overdue Days Limit** field. #### Configuration * The value defined in the **Overdue Days Limit** field determines the number of days after which a bill is considered overdue for this validation. *** ### Key Benefits * Provides control over overdue bill validation during Packing Slip entry. * Supports both **all-branch** and **branch-wise** overdue checking. * Prevents transactions when the defined overdue limit is exceeded. * Allows businesses to configure overdue validation according to their operational requirements. #### Final Outcome The **Over Due Bill Filter As** option provides three levels of control: no overdue checking, overdue checking across all branches, or overdue checking for the current branch only. The **Overdue Days Limit** defined in the customer's account determines when the overdue restriction is triggered. --- # 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/over-due-bill-filter-as.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.