> 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-version-release-notes/october-2026/inventory/issue-register.md).

# Issue Register

Logic ERP has corrected the rate on rows added to the **Issue Register** from a list. They now take the rate set in the configuration, the same as an item typed in directly.

***

### **What's corrected**

* Navigate to **Inventory** and open **Issue Register**.
* Rows added through **Items for Issue...**, **Issue All Stock...** or **Retrieve...** (requisition, Job Order, lot pieces, file and its other choices) - and by **F8** on **Raw Material Issues Against Job Order** - took the lot's **Basic Rate**, whatever the configuration said.
* They now follow **Rate From** and the rate chosen next to **Always Pick** in **Issue Register Configuration**:
  * **Lot Master** - the lot's Basic Rate, Sale Rate, Purchase Rate, MRP or Sp. Rate 1-5.
  * **Item Master** - the item's own rate of that kind.
* Issues already saved keep their rates.
* On the web, the **Configuration** button next to the configuration name is visible again.

> **Example - Rate From Lot Master, Always Pick Purchase Rate**
>
> Lot M-01 of an item has Basic Rate 500 and Purchase Rate 600. Picking the lot used to fill 500; it now fills **600**. With Rate From Item Master and Always Pick Basic Rate, the item's own Basic Rate (say 80) is filled instead of the lot's 500.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/inventory/issue-register.md)


---

# 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-version-release-notes/october-2026/inventory/issue-register.md?ask=<question>&goal=<user_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.
