> 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/journal-voucher-configuration/duplicate-bill-no-other-than-pu.md).
# Duplicate Bill No other than PU
**YouTube:** [How to Prevent Duplicate Bill Numbers in Journal Vouchers?](https://youtu.be/Jd7_xfdyrzw)
## How to Prevent Duplicate Bill Numbers in Journal Vouchers?
In this tutorial, we will learn how to manage duplicate Bill Number entries in Journal Voucher transactions using the **Duplicate Bill No Other Than PU** configuration option in Logic ERP. This feature allows you to control whether duplicate bill numbers should be allowed, completely restricted, or restricted only for the same party.
***
### Objective of This Feature
* Control duplicate Bill Number entries
* Prevent accidental duplicate transactions
* Improve accounting accuracy
* Maintain bill number uniqueness
* Provide flexible validation based on business requirements
***
### Access to Journal Voucher Configuration
* Go to **Menu Bar**
* Open **Journal Voucher Configuration** from the **Configuration Menu.**
* Select required Journal Voucher Configuration
* Navigate to **Other Options Section**
* Locate the option labeled as:
> **"Duplicate Bill No other than PU"**
This option contains multiple validation modes.
***
### Option 1: Allow (Default)
* The software allows duplicate Bill Numbers without any restriction.
**Example**
* Create a New Journal Voucher.
* Enter a Bill Number and save the voucher.
* Create another Journal Voucher using the same Bill Number.
**Result**
* The software allows the transaction successfully.
* No validation message is displayed.
***
### Option 2: Do Not Allow
* The software completely restricts duplicate Bill Numbers.
**Configuration**
* Select **Do Not Allow**
* Save the configuration.
**Example**
* Create another Journal Voucher.
* Enter a Bill Number that already exists.
**Result**
* The software restricts the transaction.
* An error message is displayed:
> "This bill number already exists for another document."
* The voucher cannot be saved until a unique Bill Number is entered.
***
### Option 3: Do Not Allow for Same Party
* Duplicate Bill Numbers are restricted only when they belong to the same party.
* The same Bill Number can still be used for different parties.
**Configuration**
* Select **Do Not Allow for Same Party**
* Save the configuration.
**Example 1: Same Party**
* Create a New Journal Voucher.
* Select a Party.
* Enter a Bill Number that already exists for that Party.
* Complete the voucher and save.
**Result**
* The software restricts the entry.
* An error message indicates that the Bill Number already exists for the selected Party.
**Example 2: Different Party**
* Change the Party Name.
* Use the same Bill Number.
* Save the voucher.
**Result**
* The software allows the voucher to be saved successfully because the Bill Number belongs to a different Party.
***
### Key Benefits
* Prevents duplicate accounting entries
* Improves bill tracking accuracy
* Reduces data entry mistakes
* Supports flexible validation requirements
* Maintains cleaner financial records
***
### Best Practice Tips
* Use **Do Not Allow** when Bill Numbers must remain unique across all transactions.
* Use **Do Not Allow for Same Party** when vendors or customers may use similar Bill Numbers.
* Periodically review duplicate Bill Number policies based on business requirements.
* Train users to verify Bill Numbers before saving vouchers.
***
### Final Outcome
The **Duplicate Bill No Other Than PU** option allows you to control how duplicate Bill Numbers are handled in Journal Voucher transactions. Depending on the selected validation mode, Logic ERP can allow duplicates, completely restrict them, or restrict them only for the same party, ensuring better control and accuracy in financial transactions.
---
# 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/journal-voucher-configuration/duplicate-bill-no-other-than-pu.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.