> 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/do-not-allow-date-change-of-transacted-purchase.md).

# Do Not Allow Date Change of Transacted Purchase

**YouTube:** [How to Prevent Voucher Date Changes in Purchase If Transactions Already Exist?](https://www.youtube.com/watch?v=GdifJ9BJMBE)

## How to Prevent Voucher Date Changes in Purchase If Transactions Already Exist?

This tutorial explains how to enable a setting in **Logic ERP** that prevents users from changing the date of a **transacted purchase voucher**, enhancing data consistency and audit control.

***

### **Step-by-Step Configuration:**

* Open the **Logic Folder** and run **Logic Admin**.
* Go to **Global Settings**.
* Navigate to the **Purchase** tab.
* Locate and enable the option: **“Do Not Allow Date Change of Transacted Purchase”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FZgXX1GVNmVYyaYMX6gR5%2FAdmin%20Setup%20-%20Do%20Not%20Allow%20Date%20Change%20of%20Transacted%20Purchase.png?alt=media&amp;token=40aa3ded-aff0-4ddb-b529-df508c7e50c9" 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 **Logic ERP** software to activate the new setting.

***

### **Effect of This Configuration**

* When a user attempts to **modify the bill date** in a purchase voucher that has already been transacted (i.e., the items have been sold or used in another transaction), the system will block the action.
* An error message will appear stating:\
  **“**&#x54;ransactions exist for this purchase voucher.... Cannot allow date chang&#x65;**.”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FvN5mXijeTk7SvfjZE4oz%2FPrompt%20in%20Purchase.png?alt=media&amp;token=85adba82-ad78-469d-a925-d4a03cb042d3" alt=""><figcaption><p>This picture illustrates that the system blocks bill date changes if transactions exist, showing:<br><strong>"Transactions exist... Cannot allow date change."</strong></p></figcaption></figure>

***

### **Purpose**

* This restriction ensures data integrity by preventing changes to dates in purchase vouchers that are already linked to subsequent transactions, such as sales or stock transfers.


---

# 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/user-access/logic-global-admin/purchase/do-not-allow-date-change-of-transacted-purchase.md?ask=<question>&goal=<user_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.
