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

# Job Order Selection Mandatory

**YouTube:** [How to Make Job Order Selection Mandatory in Journal Vouchers?](https://youtu.be/J3rp8WthJiQ)

## How to Make Job Order Selection Mandatory in Journal Vouchers?

In this tutorial, we will learn how to restrict Journal Voucher entry saving if a Job Order is not selected in Logic ERP. This feature ensures that every Journal Voucher is properly linked with a Job Order for accurate tracking and reporting.

***

### Objective of This Feature

* Make Job Order selection mandatory in Journal Vouchers
* Prevent incomplete accounting entries
* Improve Job Order tracking
* Ensure accurate cost allocation
* Maintain transaction discipline

***

### Access to Journal Voucher Configuration

* Go to **Menu Bar → Configuration.**
* Open **Journal Voucher Configuration.**
* Select Required **Configuration** from the dropdown list.
* Navigate to **Other Options Tab**
* Locate and enable the option labeled as:

> **“Job Order Selection Mandatory”.**

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

**Unlock the Job Order Field**

* Open **Column Locks Settings.**
* Search for **Job Order Field.**
* Tick the option to **Unlock** the field.

<figure><img src="/files/4gjgDEprBerzOYvWiPtO" alt=""><figcaption></figcaption></figure>

* The Job Order field becomes visible during voucher entry.
* Save the Configuration.

***

### Create a New Journal Voucher Entry

**Process**

* Open **Journal Voucher Entry Screen.**
* Click **New Voucher.**
* The Job Order selection field is now visible.

***

## Observe Restriction Behavior

**Transaction Scenario**

* Select **Supplier**
* Continue Voucher Entry Process
* Intentionally **Skip Job Order** Selection

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

* Define Accounting Entries
* Click to **Save.**

**System Response**

* The software Restricts the action.
* Displays: Error message stating that Job Order Selection is mandatory

***

### Select the Required Job Order

**Action**

* Return to Header Details Section.
* Select Required Job Order.

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

**Final Result**

* Once the Job Order is selected:
  * The Journal Voucher is saved successfully.

***

### Key Benefits

* Ensures Job Order-wise accounting accuracy
* Prevents incomplete voucher entries
* Improves project and job tracking
* Maintains accounting consistency
* Simplifies reporting and auditing

***

### Best Practice Tips

* Keep the Job Order field visible for relevant voucher types
* Verify Job Order selection before saving entries
* Use proper Job Order naming conventions
* Regularly review Job Order-linked transactions

***

### Final Outcome

* Journal Voucher entries cannot be saved without selecting a Job Order
* Proper Job Order linkage is enforced automatically
* Accounting and reporting accuracy improve significantly 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:

```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/accounts/configuration/journal-voucher-configuration/job-order-selection-mandatory.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
