> 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/cash-bank-voucher-configuration/other-options-2/do-not-return-to-main-screen-after-saving.md).
# Do Not Return to Main Screen After Saving
**YouTube:** [How to Stay in the Data Entry Grid After Saving in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=bqQvxaqhFGU)
## How to Stay in the Data Entry Grid After Saving in Cash / Bank Vouchers?
This tutorial explains how to prevent the system from automatically returning to the main screen after saving Payment and Receipt Vouchers in Logic ERP. This feature helps users continue voucher posting without interruption, improving speed and efficiency during bulk voucher entry.
***
### **Objective of This Feature**
* Prevent automatic return to the main screen after saving vouchers
* Enable continuous voucher entry
* Improve efficiency during bulk posting
* Reduce repetitive navigation steps
***
### Access to **Cash/Bank Voucher Configuration**
* Navigate to **Accounts** and then **Configurations**
* Open **Cash/Bank Voucher Configuration**
* Choose the required **Voucher Configuration**
* Example: **Bank Receipt Voucher Configuration**
* Locate the option labeled as:
> **“Do Not Return to Main Screen After Saving”**
* Currently disabled.
***
### **Default System Behavior**
* Go to the **Bank Receipt Module**
* Select the relevant configuration
* Proceed with voucher entry
* Save the voucher.
**Observation**
* After saving:
* The system automatically returns to the main screen
***
### **Enable the Feature**
**Configuration Option**
* Enable the option **“Do Not Return to Main Screen After Saving”**
* Save the changes
***
### **Verify Functionality**
**Transaction Process**
* Go to **Bank Receipt Module**
* Select the relevant configuration
* Proceed with voucher entry again
* Save the voucher
**System Behavior**
* After saving:
* The system does not return to the main screen
* The voucher entry window remains open:
* Allowing continuous voucher posting
***
### **Key Benefits**
* Faster voucher entry process
* Improved efficiency during bulk transactions
* Reduced repetitive navigation
* Better user productivity during accounting operations
***
### **Best Practice Tips**
* Use this feature when handling high-volume voucher entries
* Combine with shortcut keys for faster data entry
* Keep voucher configurations optimized for continuous posting workflows
***
### **Final Outcome**
* The system remains on the voucher entry screen after saving
* Users can continue posting vouchers without interruption
* Improved operational efficiency and faster transaction processing
* Streamlined Payment and Receipt Voucher workflow 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/cash-bank-voucher-configuration/other-options-2/do-not-return-to-main-screen-after-saving.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.
