> 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/inventory/issue-register/issue-register-configuration/issue-reason-selection-mandatory.md).
# Issue Reason Selection Mandatory
**YouTube:** [How to Make Issue Reason Selection Mandatory in the Issue Register?](https://www.youtube.com/watch?v=ZKPdiccbzg0)
## How to Make Issue Reason Selection Mandatory in the Issue Register?
In this tutorial, we will learn how to make **Issue Reason Selection** mandatory while creating an **Issue Register** entry in Logic ERP. This feature ensures that every issue transaction is recorded with a valid issue reason, improving inventory tracking and audit accuracy.
***
### Objective of This Feature
* Make Issue Reason selection mandatory.
* Prevent saving Issue Register entries without a reason.
* Improve inventory tracking and accountability.
* Standardize issue transactions.
* Ensure accurate reporting and audit compliance.
***
### Access to the Issue Register Configuration
* Go to the **Issue Register** module.
* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate and enable the option labeled as:
> **"Issue Reason Selection Mandatory"**
**Next:**
* Open **Column Locks**.
* Ensure the **Reason** field is unlocked so that users can select an Issue Reason during voucher entry.
* Save the configuration.
***
### Create a New Issue Register Entry
* Initiate a **New Issue Register** entry.
**Result**
* The **Issue Reason** field is now available in the **Header Details** section.
* The dropdown displays all the Issue Reasons defined in the system.
**Define Issue Reasons**
* To review or manage Issue Reasons.
* Go to the **Setup Reasons for Issue Receipt** module.
* From this window, you can:
* Create new Issue and Receipt Reasons.
* Modify existing reasons.
* Manage the complete list of available reasons.
***
### Observe the Validation
* Return to the **Issue Register** module.
* Leave the **Issue Reason** field blank.
* Complete the remaining voucher details.
* Click **Save**.
**Result**
The software restricts the transaction and displays an error message indicating that **Issue Reason selection is mandatory**.
The voucher cannot be saved until a valid Issue Reason is selected.
***
### Select the Issue Reason
* Return to the **Header Details** section.
* Select the appropriate **Issue Reason** from the dropdown.
* Save the voucher.
**Result**
Once a valid Issue Reason is selected, the software successfully saves the Issue Register entry.
***
### Key Benefits
* Ensures every issue transaction has a valid reason.
* Improves inventory traceability.
* Prevents incomplete voucher entries.
* Supports audit and compliance requirements.
* Enhances reporting accuracy.
***
### Best Practice Tips
* Maintain a standardized list of Issue Reasons in the **Setup Reasons for Issue Receipt** module.
* Keep the **Reason** field unlocked when this validation is enabled.
* Select the most appropriate Issue Reason for every transaction to ensure meaningful reporting.
* Periodically review and update Issue Reasons based on business requirements.
***
### Final Outcome
After enabling **Issue Reason Selection Mandatory**, Logic ERP prevents users from saving an **Issue Register** entry without selecting a valid Issue Reason. This ensures complete transaction records, improves inventory accountability, and enhances the accuracy of inventory reports and audits.
---
# 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/inventory/issue-register/issue-register-configuration/issue-reason-selection-mandatory.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.