> 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/delivery-note-against-purchase-orders/dn-against-po-configuration/do-not-allow-orders-beyond-valid-date.md).
# Do not Allow Orders Beyond Valid Date
**YouTube:** [How to Prevent Retrieval of Expired Purchase Orders in Delivery Notes?](https://youtu.be/at1PNRvuEV8)
## How to Prevent Retrieval of Expired Purchase Orders in Delivery Notes?
In this tutorial, we will learn how to restrict the retrieval of expired Purchase Orders while creating a **Delivery Note Against Purchase Order**. By enabling the **"Do Not Allow Orders Beyond Valid Date"** option, the system ensures that only Purchase Orders within their validity period are available for retrieval.
***
### Objective of This Feature
* Restrict retrieval of expired Purchase Orders.
* Display only valid Purchase Orders during retrieval.
* Prevent processing of outdated orders.
* Improve order accuracy and compliance.
* Streamline Delivery Note creation.
***
### Review the Default Behavior
Before enabling the feature, let's understand the default behavior.
* Initiate a **New Delivery Note Against Purchase Order**.
* Select the Supplier.
* Click **Next**.
* Click **Retrieve** to search for Purchase Orders.
The search window displays **all pending Purchase Orders**, regardless of whether their validity period has expired.
***
### Let's Enable the Restriction
* Open the **Configuration** window from the **Header Details** section.
* Navigate to **Other Settings**.
* Locate and enable the option labeled as:
> **"Do Not Allow Orders Beyond Valid Date"**
* Save the configuration.
***
### Create a New Transaction
* Initiate a new **Delivery Note Against Purchase Order**.
* Select the Supplier.
* Click **Next**.
* Click **Retrieve** and search for Purchase Orders.
**Result**
The system displays **only those Purchase Orders that are still within their defined validity period**.
Expired Purchase Orders are automatically excluded from the search list and cannot be retrieved.
***
### Key Benefits
* Prevents retrieval of expired Purchase Orders.
* Ensures only valid orders are processed.
* Improves transaction accuracy.
* Reduces operational errors.
* Supports better order management and compliance.
***
### Best Practice Tips
* Ensure Purchase Orders have the correct validity dates defined during creation.
* Enable this feature to prevent users from processing expired orders.
* Regularly review pending Purchase Orders and extend their validity only when required.
* Verify the order validity before generating Delivery Notes.
***
### Final Outcome
After enabling **"Do Not Allow Orders Beyond Valid Date"**, Logic ERP restricts the retrieval of expired Purchase Orders during **Delivery Note Against Purchase Order** entry. Only Purchase Orders within their validity period are available for selection, ensuring accurate and compliant order processing.
---
# 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/order-processing/delivery-note-against-purchase-orders/dn-against-po-configuration/do-not-allow-orders-beyond-valid-date.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.