> 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/employee-selection-mandatory.md).

# Employee Selection Mandatory

**YouTube:** [How to Make Employee Selection Mandatory in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=P6nfXNzD2FA)

## How to Make Employee Selection Mandatory in Cash / Bank Vouchers?

This tutorial explains how to make **Employee Selection Mandatory** while creating Payment and Receipt Vouchers in Logic ERP. This feature ensures that users cannot proceed with voucher entry without selecting an Employee, helping maintain accountability and accurate transaction tracking.

***

### **Objective of This Feature**

* Enforce mandatory Employee selection during voucher entry
* Improve transaction accountability
* Maintain accurate employee-wise financial records
* Prevent incomplete voucher entries

***

### Access to **Cash/Bank Voucher Configuration**

* Navigate to **Accounts** and then **Configurations**
* Open **Cash/Bank Voucher Configuration**
* Choose the required **Voucher Configuration**
  * Example: **Bank Payment Voucher Configuration**
* Locate and enable the option labeled as:

> **“Employee Selection Mandatory”.**

<figure><img src="/files/2WVGFgl6nbGZTHlnMW2A" alt=""><figcaption></figcaption></figure>

* Save the changes

***

### **Open Bank Payment Voucher Entry**

* Go to **Bank Payment Module**
* Select the relevant **Voucher Configuration**

**Enable Employee Name Column**

* Open **Setup Column Attributes**
* Enable **Employee Name Column**

<figure><img src="/files/6kyLwLApLKPuO99n9d3p" alt=""><figcaption></figcaption></figure>

***

### **Verify Functionality**

**Transaction Process**

* Proceed with generating the voucher
* Do not select the **Employee Name**

**System Behavior**

* Upon proceeding to the next line:
  * The software restricts the action.

<figure><img src="/files/ekMAjYJu8tg6cxV87fFP" alt=""><figcaption></figcaption></figure>

**Error Message**

* The system displays an alert indicating:
  * **Employee Selection is Required**

**Complete Voucher Entry**

* Select the required:
  * **Employee Name**

<figure><img src="/files/WRORHll31uUftezXajOU" alt=""><figcaption></figcaption></figure>

* Proceed with saving the voucher

**System Behavior**

* Upon selecting the Employee Name:
  * The voucher is saved successfully

***

### **Key Benefits**

* Ensures employee accountability in transactions
* Prevents incomplete voucher entries
* Improves employee-wise transaction tracking
* Maintains accurate financial records

***

### **Best Practice Tips**

* Enable Employee columns in relevant voucher formats
* Ensure Employee Masters are properly configured
* Use this feature for better audit tracking and operational control

***

### **Final Outcome**

* Employee selection becomes mandatory during voucher entry
* Users cannot proceed without selecting an Employee
* Improved transaction accountability and record accuracy
* Better control over Payment and Receipt Voucher management


---

# 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/accounts/configuration/cash-bank-voucher-configuration/other-options-2/employee-selection-mandatory.md?ask=<question>&goal=<endgoal>
```

`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.
