> 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/divide-rate-by-quantity.md).
# Divide Rate by Quantity
**YouTube:** [How to Configure Divide Rate by Quantity in Import PUV Configuration?](https://youtu.be/UPfVm_4nF8U)
## How to Configure Divide Rate by Quantity in Import PUV Configuration?
In this tutorial, we will learn how to use the **"Divide Rate by Quantity"** feature while importing Purchase Vouchers from an external file in Logic ERP.
This feature allows the system to automatically divide the rate imported from the external file by the quantity specified in the document.
***
### Access to the Import Configuration
To access the required option:
* Navigate to **Import Purchase Vouchers from External File**.
* Open the **Configuration** window.
* Locate the option labeled as:
> **"Divide Rate by Quantity"**
Before enabling this option, let's first understand its default behavior.
***
### Import the Voucher with the Option Disabled
* Keep **"Divide Rate by Quantity"** disabled.
* Import the required Purchase Voucher using the external Excel file.
* Observe the imported rate.
#### Example
In the Excel file:
* **Rate:** 1,200
* **Quantity:** 10
Since the **"Divide Rate by Quantity"** option is disabled, the system imports the rate exactly as specified in the Excel file.
Therefore:
**Imported Rate = 1,200**
The system does not divide the rate by the quantity.
***
### Enable Divide Rate by Quantity
Now, let's enable the feature and observe the difference.
* Return to the **Configuration** window.
* Enable **"Divide Rate by Quantity"**.
* Save the configuration.
* Import the **same Excel file** again.
***
#### System Behavior
After enabling this option, the system divides the imported rate by the specified quantity.
Using the same example:
**Rate = 1,200**\
**Quantity = 10**
**Calculated Rate = 1,200 รท 10 = 120**
Therefore, the system imports the rate as **120**.
**Verify the Imported Purchase Voucher**
* Proceed with importing the voucher.
* Once the purchase details are imported successfully, open the **Purchase Voucher** module.
* Open the imported voucher and verify the rate.
#### Result
As you can see, the rate has been successfully imported as **120**, calculated by dividing the original rate of **1,200** by the quantity of **10**.
***
### Final Outcome
The **"Divide Rate by Quantity"** feature is useful when the rate provided in the external file represents a total value that needs to be converted into a per-unit rate during the Purchase Voucher import.
---
# 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/divide-rate-by-quantity.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.
