> 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/others/user-rights-settings/do-not-allow-back-date-entry-in-all-documents.md).

# Do Not Allow Back Date Entry in All Documents

**YouTube:** [How to Globally Restrict Backdated Entries for All Documents?](https://www.youtube.com/watch?v=jlK4FzS_lf8)

## How to Globally Restrict Backdated Entries for All Documents?

In this tutorial, we’ll show you how to **restrict backdated entries across all documents** in **Logic ERP**, ensuring data integrity and compliance with accounting policies.

***

### **Enable the Global Restriction**

* Open **Logic Admin** and navigate to **Global Settings**.
* Go to **Other** section and click to "User Rights Settings"&#x20;
* Locate and enable the option: **“Do Not Allow Back Date Entry in All Documents”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FFwRhBbUwzlGcZbgM2swX%2FAdmin%20Setup%20-%20Do%20Not%20Allow%20Back%20Date%20Entry%20in%20All%20Documents.png?alt=media&amp;token=17ac0771-3177-4a5b-b924-eda16b1cf322" alt=""><figcaption><p>Let's proceed with this option turned on to understand its practical implications in billing.</p></figcaption></figure>

* Save the settings.
* Restart the software to apply the changes.

***

### **Review the Restriction Across Document Types**

* **Purchase Voucher**
  * Create a **purchase voucher** using a **backdate**.
  * Enter transaction details.
  * Attempt to **save the entry**.
  * The software **blocks the action** and displays an error message:\
    *“Backdated entries are not allowed.”*

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FTU0otpIBBy93fl9phk3a%2FPurchase%20-%20Back%20date.png?alt=media&amp;token=7daa569a-20b3-4f7c-aa7e-699c258beb80" alt=""><figcaption></figcaption></figure>

* **Sales Voucher**
  * Try to create a **sales entry** with a backdated transaction.
  * On saving, the **same error message** appears, preventing the entry from being saved.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FlPvqS9fCIknaJE0uWtIE%2FSale%20-%20Back%20Date.png?alt=media&amp;token=151124ad-3872-4b09-bc6b-6e86709cb0d6" alt=""><figcaption></figcaption></figure>

* **Bank Voucher**
  * Attempt a **backdated bank transaction**.
  * The system will again **restrict the entry** and display the error prompt.

***

### **Conclusion**

By enabling this option, Logic ERP **strictly enforces a no-backdate policy** across all document types, helping organizations maintain **accurate, timely, and compliant records**.


---

# 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/others/user-rights-settings/do-not-allow-back-date-entry-in-all-documents.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.
