> 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/user-access/logic-global-admin/purchase/purchase-voucher-date-should-be-equal-to-purchase-challan-date-when-retrieved.md).

# Purchase Voucher date should be equal to Purchase Challan Date when retrieved

YouTube: [How to Ensure Purchase Voucher Date Matches Purchase Challan Date During Retrieval?](https://www.youtube.com/watch?v=i_JKI7pofKo)

## How to Ensure Purchase Voucher Date Matches Purchase Challan Date During Retrieval?

This tutorial explains how to enable a validation that restricts saving a purchase voucher if its date does not match the corresponding purchase challan date.

***

### **Access Logic Admin Settings:**

* Open the **Logic Folder** and run **Logic Admin**.
* Go to **Global Settings**.
* Navigate to the **Purchase** tab.
* Locate and enable the option: **"Purchase Voucher dates should be equal to Purchase Challan date when retrieved"**.

<figure><img src="/files/HnXtXYhpvZwGXoLVHvV2" alt=""><figcaption><p>Let's keep this feature enable to observe its impact in Purchase.</p></figcaption></figure>

* Click **Save** to apply the changes.
* Restart the software to ensure the configuration takes effect.

***

### **Validate the Configuration:**

1. Go to the **Purchase Entry** module.
2. Retrieve a **Purchase Challan** into the purchase entry.
3. Attempt to save the purchase with a voucher date that differs from the challan date.
4. The system will display an error:\
   \&#xNAN;**“Document date should be equal to Purchase Challan date.”**

<figure><img src="/files/qRPQpc5jC3C3UouZyK51" alt=""><figcaption><p>As you can see, the software has displayed a prompt indicating that the <strong>Challan date and Purchase date are not the same</strong>.</p></figcaption></figure>


---

# 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/user-access/logic-global-admin/purchase/purchase-voucher-date-should-be-equal-to-purchase-challan-date-when-retrieved.md?ask=<question>&goal=<endgoal>
```

`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.