> 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/allow-selection-of-tds-types.md).
# Allow Selection of TDS Types
**YouTube:** [How to Enable TDS Type Selection in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=CXLaB1S_zNE)
## How to Enable TDS Type Selection in Cash / Bank Vouchers?
This tutorial explains how to enable the selection of TDS Types while generating Payment and Receipt Vouchers in Logic ERP. This feature allows users to manually choose the applicable TDS Type during voucher entry for accurate tax deduction processing.
***
### Objective of This Feature
* Enable manual selection of TDS Types
* Improve flexibility in TDS processing
* Ensure accurate tax deduction classification
* Support multiple TDS scenarios during voucher entry
* Simplify TDS management in payment and receipt transactions
***
### 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 the option labeled as:
> **“Allow Selection of TDS Types”**
**Default Status:**
* The feature is disabled.
***
### Observe Behavior in Disabled State
**Transaction Process**
* Open **Bank Payment Module**
* Select Relevant Voucher Configuration
* Proceed with Voucher Entry
**System Behavior**
* Upon proceeding to the next line:
* The **TDS Details Window** opens automatically
* Since the feature is disabled:
* The **TDS Type Selection Field** remains disabled
* Users:
* Cannot manually select TDS Type
***
## Observe Functionality After Enabling
**Action**
* Return to **Cash/Bank Voucher Configuration**
* Enable **Allow Selection of TDS Types**
* Save Configuration
**Process**
* Again, proceed with Bank Payment Voucher Entry
* Upon proceeding to the next line:
* The **TDS Details Window** opens
* The **TDS Type Selection Field** becomes active.
**Final Steps**
* Select Appropriate TDS Type
* Click **Apply**
* Save the Voucher
***
### Key Benefits
* Flexible TDS handling during voucher entry
* Supports multiple TDS categories
* Improves tax deduction accuracy
* Reduces dependency on fixed TDS mappings
* Enhances compliance and reporting accuracy
***
### Best Practice Tips
* Select the correct TDS Type as per applicable tax rules
* Verify TDS configurations before voucher processing
* Review TDS details before saving vouchers
* Maintain updated TDS master configurations
***
### Final Outcome
* Users can manually select TDS Types during voucher entry
* TDS processing becomes more flexible and accurate
* Payment and Receipt Voucher management becomes more efficient 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/allow-selection-of-tds-types.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.
