> 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/cheque-for-duplicate-receipt-cheque.md).
# Cheque for Duplicate Receipt / Cheque
**YouTube:** [How to Enable Duplicate Receipt / Cheque Number Checks in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=EQaHTQOL9jE)
## How to Enable Duplicate Receipt / Cheque Number Checks in Cash / Bank Vouchers?
This tutorial explains how to restrict Duplicate Receipt and Cheque Number entries while generating Payment and Receipt Vouchers in Logic ERP. This feature helps prevent duplicate cheque issuance and ensures accurate financial record management.
***
### Objective of This Feature
* Restrict duplicate Cheque and Receipt Number entries
* Prevent duplicate voucher transactions
* Improve financial accuracy and validation
* Maintain proper cheque tracking and control
***
### 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:
> **“Check for Duplicate Receipt / Cheque”**
* Save the changes
***
### Implement in Bank Payment Voucher
Transaction Process
* Open **Bank Payment Module**
* Select Relevant Configuration
* Proceed with Voucher Entry
**Important**
* Enter and Note the **Cheque Number**
* Save the Voucher
***
### Verify Duplicate Validation
**Action**
* Create another Voucher
* Enter The same Cheque Number used earlier
**System Behavior**
* Upon proceeding to the next line:
* The system restricts the action
**Validation Message**
* The software displays:
* Duplicate Entry Message
* It also shows:
* Existing Voucher Details where the Cheque Number was already used
**Result**
* The Voucher cannot be saved:
* Until a unique Cheque or Receipt Number is entered
**Enter a Unique Cheque Number**
* Enter Unique Cheque Number
* The Voucher is saved successfully
***
### Key Benefits
* Prevents duplicate cheque issuance
* Improves financial transaction accuracy
* Reduces manual errors in voucher entry
* Ensures better audit and cheque tracking control
***
### Best Practice Tips
* Always use unique Cheque and Receipt Numbers
* Enable this validation for all Payment and Receipt configurations
* Regularly review voucher entries for better financial control
***
### Final Outcome
* Duplicate Receipt and Cheque Numbers are restricted
* Voucher entries become more accurate and secure
* Financial records remain clean and error-free
* Better cheque management is maintained 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 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/cheque-for-duplicate-receipt-cheque.md?ask=&goal=
```
`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.