> 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/account-group-selection-mandatory.md).
# Account Group Selection Mandatory
**YouTube:** [How to Make Account Group Selection Mandatory in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=21jMmfrE6aM)
## How to Make Account Group Selection Mandatory in Cash / Bank Vouchers?
This tutorial explains how to make **Account Group Selection Mandatory** while creating Payment and Receipt Vouchers in Logic ERP. This feature ensures that users cannot proceed with voucher entry without selecting an Account Group, helping maintain proper accounting classification and accuracy.
***
### **Objective of This Feature**
* Enforce mandatory Account Group selection.
* Improve accounting accuracy and classification.
* Prevent incomplete voucher entries.
* Maintain proper financial data organization.
***
### **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 and enable the option labeled as:
> **“Account Group Selection Mandatory”.**
* Save the changes.
***
### **Open Bank Receipt Voucher Entry**
* Go to **Bank Receipt Module.**
* Select the relevant **Voucher Configuration.**
**Enable Account Group Column**
* Open **Setup Column Attributes.**
* Enable **Account Group Name Column.**
***
### **Verify Functionality**
**Transaction Process**
* Proceed with generating the voucher
* Do not select the: **Account Group**
**System Behavior**
* Upon proceeding to the next line:
* The software restricts the action
**Error Message**
* The system displays an alert indicating:
* **Account Group Selection is Required**
***
### **Key Benefits**
* Ensures proper account classification
* Prevents incomplete voucher entries
* Improves financial reporting accuracy
* Enhances accounting discipline and control
***
### **Best Practice Tips**
* Enable Account Group columns for all relevant voucher formats
* Define proper Account Groups before voucher entry
* Use this feature to maintain structured accounting records
***
### **Final Outcome**
* Account Group selection becomes mandatory during voucher entry
* Users cannot proceed without selecting an Account Group
* Improved accounting accuracy and voucher management
* Better control over financial data organization
---
# 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/account-group-selection-mandatory.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.
