> 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-cash-vouchers.md).

# Do Not Allow Back Date Entry in Cash Vouchers

**YouTube:** [How to Restrict Back Date Entries in Cash Vouchers?](https://www.youtube.com/watch?v=SUH9i50zvdQ)

## How to Restrict Back Date Entries in Cash Vouchers?

In this tutorial, we’ll demonstrate how to **restrict backdated entries in cash receipts and payments** using **Logic ERP**, ensuring accurate and timely financial reporting.

***

### **Enable Restriction on Backdated Cash Entries**

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

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FMuKHak6T0ndX42fP6CAT%2FAdmin%20Setup%20-%20Do%20Not%20Allow%20Back%20Date%20Entry%20in%20Cash%20Vouchers.png?alt=media&amp;token=14879205-7794-449e-8be5-05ecbc6226a9" alt=""><figcaption><p>Let's keep this feature enable to observe its impact in billing</p></figcaption></figure>

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

***

### **Review the Restriction in Action**

* Navigate to the **Cash Payment Entry** window.
* Attempt to enter a payment in **backdate**.
  * Enter the **amount**.
  * Select the **supplier**.
  * Choose the relevant **purchase voucher**.
* Try to **save** the entry.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FzEZeCxSwuB1g8zxFq8Nx%2FPrompt%20for%20back%20Date.png?alt=media&amp;token=f9ac0017-ebf9-44fe-b2c1-bad0908b9658" alt=""><figcaption><p>The image illustrates that backdated entries are restricted, and the software displays a prompt to block the action.</p></figcaption></figure>

> The software will **restrict the action** and display an error message:
>
> *“Backdated entries are not allowed.”*

***

### C**onclusion**

Enabling this restriction helps maintain **financial accuracy**, prevents unauthorized data tampering, and enforces compliance with **accounting cut-off policies**.


---

# 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-cash-vouchers.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.
