> 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/accounts/configuration/journal-voucher-configuration/do-not-allow-modification-of-entries-with-br-bp-adjustments.md).
# Do not Allow Modification of Entries with BR/BP Adjustments
**YouTube:** [How to Restrict Modification of Entries Linked with BR/BP Adjustments in Journal Vouchers?](https://youtu.be/tLw0LiBdQL8)
## How to Restrict Modification of Entries Linked with BR / BP Adjustments in Journal Vouchers?
In this tutorial, we will learn how to restrict modification of Journal Voucher entries that already have BR/BP Adjustments in Logic ERP. This feature helps maintain accounting integrity by preventing changes to vouchers that are already linked with Bank Receipt or Bank Payment adjustments.
***
### Objective of This Feature
* Prevent modification of adjusted Journal Vouchers
* Protect accounting accuracy
* Maintain BR/BP adjustment integrity
* Avoid accidental voucher changes
* Ensure secure financial transactions
***
### Create a Journal Voucher Entry
**Initial Process**
* First Create a New Journal Voucher Entry
* Adjust The Journal Voucher against a BR/BP Transaction
* Save The Voucher Entry
***
### Open Journal Voucher Configuration
* Go to **Menu Bar**
* Open **Journal Voucher Configuration** from the **Configuration Menu.**
* Select required Journal Voucher Configuration
* Navigate to **Other Options Section**
* Locate and enable the option labeled as:
> **“Do not Allow Modification of Entries with BR/BP Adjustments”**
* Save the Configuration.
***
### Open Voucher in Modify Mode
**Process**
* Open Previously Saved Journal Voucher Entry
* Use Modify Mode
**Observe Restriction Behavior**
* Attempt to modify the Voucher Entry
**System Behavior**
* The software immediately restricts the action.
* Displays Message stating that:
> BR/BP Adjustment exists against this row. Cannot allow editing
***
### Key Benefits
* Protects adjusted accounting entries
* Prevents accidental data modification
* Maintains financial accuracy
* Improves audit control
* Ensures transaction security
***
### Best Practice Tips
* Enable this feature for controlled accounting environments
* Verify vouchers before BR/BP adjustment
* Avoid unnecessary voucher modifications after adjustment
* Regularly review adjustment-linked transactions
***
### Final Outcome
* Journal Voucher entries with BR/BP Adjustments cannot be modified
* Accounting integrity is maintained automatically
* Financial transactions remain secure and accurate in Logic ERP
---
# 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/accounts/configuration/journal-voucher-configuration/do-not-allow-modification-of-entries-with-br-bp-adjustments.md?ask=&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.
