> 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/production/production-reports-queries/production-finished-goods-reports/job-order-wise-costing-from-rm-processing.md).

# Job Order Wise Costing From RM/Processing

Logic ERP has renamed three columns in the **Job Order Wise Costing From RM/Processing** report so that they say what they show: **DIFFERENCE** is now **PENDING FROM CONSUMPTION QTY** and **DIFFERENCE VALUE** is now **PENDING FROM CONSUMPTION VALUE**, and **JOB ORDER QUANTITY** is now **JO QUANTITY PRODUCED**. It also adds eight new columns that show how much of each job order has been received into stock, the quantity ordered, and the work in progress: **PRODUCTION ADD IN STOCK VALUE**, **ADD IN STOCK QUANTITY**, **ADD IN STOCK RATE**, **ADD IN STOCK DOCUMENT NO**, **ADD IN STOCK DATE**, **PRODUCED NOT IN STOCK QTY**, **JO ORDERED QUANTITY** and **PRODUCTION WIP VALUE**. This release also corrects the two renamed pending columns on the totals rows.

***

### **Step 1: Open the Report**

* Navigate to **Production > Production Reports/Queries** and select **Production Finished Goods Reports**.
* Open the **Job Order Wise Costing From RM/Processing** report.

***

### **Step 2: New columns**

* Add the **PRODUCTION ADD IN STOCK VALUE**, **ADD IN STOCK QUANTITY**, **ADD IN STOCK RATE**, **ADD IN STOCK DOCUMENT NO**, **ADD IN STOCK DATE**, **PRODUCED NOT IN STOCK QTY**, **JO ORDERED QUANTITY** and **PRODUCTION WIP VALUE** columns from the report's column settings, then tick them.
* All eight columns are for the job order as a whole, so each job order shows the same figures on all its rows.
* **ADD IN STOCK QUANTITY** is the quantity of the job order received into stock up to the report's end date. It counts both production receipts that add the goods into stock and purchase entries that receive the production into stock.
* **PRODUCTION ADD IN STOCK VALUE** is the value of that quantity at the raw material cost rate of the production.
* **ADD IN STOCK RATE** is **PRODUCTION ADD IN STOCK VALUE** divided by **ADD IN STOCK QUANTITY**. On the totals rows it is the total value divided by the total quantity.
* **ADD IN STOCK DOCUMENT NO** and **ADD IN STOCK DATE** list the production receipts and purchase entries behind these figures, in date order, separated by commas.
* **PRODUCED NOT IN STOCK QTY** is the quantity produced for the job order, as used for its costing, less **ADD IN STOCK QUANTITY**. It is blank when the job order has not been costed, or when the two are equal.
* **JO ORDERED QUANTITY** is the quantity ordered on the job order. **JO QUANTITY PRODUCED** shows the quantity produced.
* **PRODUCTION WIP VALUE** is the raw material issued to the job order, less the raw material returned, less **PRODUCTION ADD IN STOCK VALUE**, up to the report's end date. It is worked out the same way as **PRODUCTION WIP VALUE** in the **Job Order Wise Work In Progress** report (**Production > Production Reports/Queries > Production Raw Material Reports**), so the two reports agree for each job order when the Work In Progress report is run for all branches.
* In the grand total, each job order's figures are added once, even when it has several rows.

***

### **What's changed**

* **DIFFERENCE** is renamed **PENDING FROM CONSUMPTION QTY**, and **DIFFERENCE VALUE** is renamed **PENDING FROM CONSUMPTION VALUE**.
* They show the raw material issued to the job order that has not yet been consumed or returned: **ISSUE QUANTITY** less **CONSUMED QUANTITY** less **RETURN QUANTITY**, and **ISSUE VALUE** less **CONSUMED VALUE** less **RETURN VALUE**.
* **JOB ORDER QUANTITY** is renamed **JO QUANTITY PRODUCED**, because it shows the quantity produced, not the quantity ordered.
* Only the captions change. The figures on the detail rows are the same as before. If you had given any of these columns your own name, it is reset to the new name.

***

### **What's corrected**

* On the totals rows, **PENDING FROM CONSUMPTION QTY** and **PENDING FROM CONSUMPTION VALUE** now also deduct the material returned, the same as the detail rows do. Before, the totals left the returned material in, so they did not agree with the rows above them.
* Because of this, these two totals now **fall** by **RETURN QUANTITY** and **RETURN VALUE** wherever material was returned. This is intended. Totals with no returns show the same figures as before.


---

# 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/production/production-reports-queries/production-finished-goods-reports/job-order-wise-costing-from-rm-processing.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.
