> 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/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/default-grn-prefix.md).
# Default GRN Prefix
**YouTube:** [How to Set the Default GRN Prefix in Import Purchase Voucher from External File Configuration?](https://youtu.be/rrE-uiDTiJE)
## How to Set the Default GRN Prefix in Import Purchase Voucher from External File Configuration?
In this tutorial, we will learn how to configure a **Default GRN Prefix** during the Purchase Import process in Logic ERP. This feature allows you to define a default prefix that is automatically applied to the GRN number when a Purchase Voucher is imported from an external file.
***
### Review the Existing GRN Prefixes
* Navigate to the **Purchase Voucher** module.
* Open an existing Purchase Voucher.
* Review the **GRN Prefix** column.
#### Current Setup
As shown, different GRN prefixes are currently being used for Purchase Vouchers.
**Important Note**
* If the **GRN Prefix** column is not visible, open the **Purchase Configuration**.
* Navigate to **Column Locks**.
* Enable the **GRN Prefix** column.
***
### Configure the Default GRN Prefix
* Navigate to the **Import Purchase Vouchers from External File** module.
* Open the **Configuration** section.
* Locate the option labeled as:
> **"Default GRN Prefix"**
* Enter the required **GRN Prefix**.
* Save the configuration changes.
#### System Behavior
The configured prefix will be used as the default GRN prefix for Purchase Vouchers imported through the external file import process.
***
### Import the Purchase Voucher
* Start the **Purchase Voucher Import** process.
* Select the required external file.
* Complete the import process.
**Result**
The Purchase Voucher is imported successfully with the configured **Default GRN Prefix**.
***
### Verify the GRN Prefix
* Open the **Purchase Voucher** module.
* Search for and open the recently imported Purchase Voucher.
* Check the **GRN Prefix**.
**Result**
The **GRN Prefix** defined in the Purchase Import configuration has been successfully applied to the imported Purchase Voucher.
***
### Key Benefits
* **Automated Prefix Assignment:** Automatically applies the configured GRN prefix during import.
* **Consistent GRN Numbering:** Maintains a standardized GRN numbering structure.
* **Faster Import Process:** Eliminates the need to manually define the prefix for imported vouchers.
* **Better Document Control:** Helps maintain organized and consistent Purchase Voucher records.
#### Final Outcome
After configuring **"Default GRN Prefix"**, Logic ERP automatically applies the defined GRN prefix to Purchase Vouchers imported through the **Import Purchase Vouchers from External File** process, ensuring consistent GRN identification for future purchase 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/default-grn-prefix.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
