> 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/order-processing/purchase-order/po-configuration/do-not-allow-blank-rate.md).
# Do Not Allow Blank Rate
**YouTube:** [How to Make Rate Entry Mandatory in Purchase Orders?](https://youtu.be/Qiizbkf9i_M)
## How to Make Rate Entry Mandatory in Purchase Orders?
This tutorial explains how to **restrict saving a Purchase Order with Zero or Blank Rate** in Logic ERP. It demonstrates the default system behavior and how enabling a configuration ensures that all items must have valid rates before saving, thereby improving data accuracy and financial control.
***
### **Objective of This Feature**
* Prevent saving Purchase Orders with **Zero or Blank Rates**
* Ensure **accurate costing and valuation**
* Maintain **financial discipline and data integrity**
***
### **Understanding Default Behavior**
* Create a **New Purchase Order Entry**
* Add items with **Zero Rate**
**Default System Behavior**
* Software **allows saving** the Purchase Order
* No restriction on Zero or Blank Rates
***
### **Enabling Rate Restriction**
* Open **Purchase Order Module**
* Go to **Configuration Window**
* Navigate to **General Options Section**
* Locate enable the option Labeled as:
> **“Do Not Allow Blank Rate”**
* Click **Ok.**
***
### Implement **After Enabling the Feature**
* Create a **New Purchase Order Entry**
* Try adding an item with **Zero Rate**
**System Behavior**
* System **restricts the entry**
* Displays an **error message**:
* Rate entry is mandatory
***
### **Completing the Purchase Order**
* Enter a **valid rate** for the item
* Save the Purchase Order
**Result**
* Entry is successfully saved only after valid rate is entered
***
### **Key Benefits**
* Ensures **accurate purchase costing**
* Prevents **incomplete or incorrect entries**
* Improves **financial reporting accuracy**
* Strengthens **process control in procurement**
***
### **Best Practice Tips**
* Always enable this feature in:
* Standard purchasing workflows
* Regularly review configurations to maintain control
***
### **Final Outcome**
* Purchase Orders cannot be saved with **Zero or Blank Rates**
* Data remains **accurate and reliable**
* Procurement process becomes **more controlled and error-free**
* Financial records maintain **consistency and integrity**
---
# 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/order-processing/purchase-order/po-configuration/do-not-allow-blank-rate.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.