> 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/set-back-date-entry-modification-locking-schedule.md).
# Set Back Date Entry/Modification Locking Schedule
**YouTube:** [How to Configure Backdate Entry and Modification Locking Schedule?](https://www.youtube.com/watch?v=YkLsRLQFx4Q)
## How to Configure Backdate Entry and Modification Locking Schedule?
In this tutorial, you will learn how to **Restrict Backdated Entries and Modifications** in Logic ERP using the **Backdate Entry / Modification Locking Schedule** feature. This helps maintain **Data Accuracy, Security and Audit Control**.
***
### Open Locking Schedule Setup
To begin:
* Go to the **User Access Module**.
* Open **Set Back Date Entry / Modification Locking Schedule**.
* This window displays a list of **documents** (e.g., Sale, Purchase, etc.) where locking rules can be applied.
***
### Select Document for Locking
* Select the **document** (e.g., *Sale Document*).
* Right-click on the selected document.
* Click on **Settings**.
**Shortcut:**
* Press **F3** to directly open settings.
***
### Configure Lock Criteria
* The **Lock for Back Date Entry** window will open.
* Here, you can define various locking rules based on your business needs.
#### Apply Fixed Days Lock
Let’s configure a **Fixed Days Lock**.
* Select the **number of days** to restrict (e.g., 1, 2, 3 days).
* Click **Save**.
**What this means:**
* You **cannot modify existing entries** within the locked days.
* You **cannot create new backdated entries** for those days.
***
### Implement with Modification Restriction
Now verify the impact:
* Go to the **Sale Bill Window**.
* Open a bill that falls within the **locked period**.
* Try to **modify and save** the bill.
**Result:**
* The system will **restrict the modification**.
* An **error message** will appear indicating:
* *Entry modification is locked for this period*
***
### Implement with Backdated Entry Restriction
Now test creating a backdated entry:
* Create a **new sale bill**.
* Enter a **date within the locked period**.
* Try to **save the bill**.
**Result:**
* The system will **not allow saving**.
* Backdated entries within the locked period are **restricted**.
***
### Key Benefits of Locking Schedule
* Prevent unauthorized backdated entries
* Ensure data integrity and accuracy
* Improve audit compliance
* Control user activity effectively
* Reduce risk of financial manipulation
***
### Final Outcome
You have successfully learned how to:
* Configure **Backdate Entry Locking**
* Restrict **Modification of Past Transactions**
* Enforce **data security policies**
Your system is now better equipped for **controlled and secure operations**.
---
# 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/set-back-date-entry-modification-locking-schedule.md?ask=&goal=
```
`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.