> 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/default-document-prefix.md).

# Default Document Prefix

**YouTube:** [How to Configure the Default Document Prefix in the Issue Register?](https://www.youtube.com/watch?v=caIdfCVoOz8)

## How to Configure the Default Document Prefix in the Issue Register?

 In this tutorial, we will learn how to define a **Default Document Prefix** in the Issue Register module of Logic ERP. This feature allows you to assign one or multiple document prefixes, making voucher numbering more organized and flexible.

***

### Objective of This Feature

* Define a default document prefix for Issue Register entries.
* Standardize document numbering.
* Support multiple document prefixes.
* Simplify voucher identification.
* Improve document organization and tracking.

***

### Review the Default Behavior

* Open the **Issue Register** module.

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

**Observation**

By default, the document prefix is configured as **IR**, and it is automatically reflected in the **Document Number** field during voucher creation.

***

### Let's Configure the Default Document Prefix

* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:

> **"Default Doc Prefix"**

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

* Here, you can define the document prefix that will be used in the Issue Register.

**Configure a Single Document Prefix**

* Enter a single document prefix
* For example: **IR**
* Save the configuration.

**Result**

When only one document prefix is configured, the system automatically selects it and displays it in the **Document Number** field for every new Issue Register entry.

***

### Configure Multiple Document Prefixes

* You can also define multiple document prefixes by separating them with commas.
* **For example:**
  * IR, IS, ISR

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

* Save the configuration after entering the required prefixes.

The **Document Prefix** field is converted into a dropdown list, allowing you to select the appropriate prefix while creating a voucher.

***

### Create a New Issue Register Entry

* Initiate a new Issue Register voucher.

<figure><img src="/files/0G9MycVK3g4chHOhoRvU" alt=""><figcaption></figcaption></figure>

**Result**

* If only **one prefix** is configured, the system automatically selects it.
* If **multiple prefixes** are configured, you can simply choose the required prefix from the dropdown before proceeding with the voucher entry.

***

### Key Benefits

* Standardizes document numbering.
* Supports multiple document series.
* Simplifies voucher identification.
* Improves document organization.
* Provides flexibility for different transaction types.

***

### Best Practice Tips

* Use meaningful document prefixes to distinguish different voucher types.
* Configure multiple prefixes only when required by your business process.
* Maintain a consistent naming convention for better document tracking.
* Periodically review configured prefixes to ensure they align with your organization's documentation standards.

***

### Final Outcome

The **Default Doc Prefix** feature in Logic ERP allows you to define one or multiple document prefixes for the Issue Register. When a single prefix is configured, it is selected automatically. When multiple prefixes are defined, the system provides a dropdown list, enabling users to choose the appropriate prefix while creating vouchers, ensuring organized and flexible document numbering.


---

# 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/default-document-prefix.md?ask=<question>&goal=<endgoal>
```

`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.
