> 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-version-release-notes/january-2026/purchase/do-not-allow-purchase-return-w-o-purchase-return-challan-option-updated.md).
# "Do Not Allow Purchase Return w/o Purchase Return Challan" Option updated
Logic ERP has introduced a new update to enhance and streamline **Purchase Return control**.
Previously, the option **“Do not allow entry without PO/Challan”** was not enforced correctly for **Purchase Return transactions**, allowing users to create returns without linking a **Purchase Challan Return**. With this update, the system now correctly **restricts Purchase Return entries unless a valid Purchase Challan Return is selected**. This ensures better process compliance, prevents incorrect return entries, and improves overall accuracy in purchase return management.
***
### Step 1: Configurate and Implement in **Purchase Return**
* First, open the **Purchase Return Configuration**.
* In the configuration screen, **enable the option “Do Not Allow Entry Without Purchase Order/Challan.”**
* Once this option is enabled, the system will **not allow you to create a Purchase Return** unless a **Purchase Return Challan is retrieved**.
* This ensures that all Purchase Return entries are **properly linked to the original challan**, improving control and accuracy.
---
# 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-version-release-notes/january-2026/purchase/do-not-allow-purchase-return-w-o-purchase-return-challan-option-updated.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.
