> 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/production/job-order-costing-concepts.md).

# Job Order Costing - Concepts

## How Logic ERP Works Out the Cost of a Job Order

In this article, we will learn how Logic ERP calculates the **cost of a Job Order** — what goes into it, which quantity it is divided by, and how it is shared between the finished items. Read this before using the costing utilities and reports in the **Production** module.

***

### **Planned Cost and Actual Cost**

Logic ERP shows two different kinds of cost. Knowing which one a screen shows avoids most confusion.

* **Planned cost** — what the Job Order *should* cost, worked out from what is defined on the Job Order: its raw materials and consumption per piece, its process rates from **Setup Process Wise Item Rates**, and its **BOM Expenses**. No issue or production entry is needed.
  * Shown by **Cost Sheet**.
  * **Cost Sheet - Projected Vs Actual** shows the planned cost side by side with the actual cost.
* **Actual cost** — what the Job Order *really* cost, worked out from the entries made against it: raw material issues, returns and consumption, production and linked journal vouchers.
  * Worked out by **Update Job Order + Process Wise Net Cost** and saved against the Job Order.
  * **Job Order Wise Cost Vs Sale Analysis** shows this saved cost.
  * **Job Order Wise Costing From RM/Processing** works its figures out from the entries each time it is run, but takes the quantity produced from this saved cost.
* **Finished Product Cost from RM\`s Defined** is different again: it estimates the raw-material cost of a finished item from the item's raw material specification in the masters, without any Job Order.

***

### **What Makes Up the Actual Cost**

The cost per piece of a Job Order is made up of:

* **Raw material** — the value of the raw material used on the Job Order.
* **Processing** — the making charges of every process, including the process **Overhead(%)**.
* **BOM Expenses** — the expense lines on the Job Order, such as overheads, rejection allowance or margin (see [Setup BOM Expenses](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-setups/setup-bom-expenses.md)).

**Journal vouchers** linked to the Job Order are added to the cost of each **finished item**. They are not included in the Job Order's overall cost per piece, so the two can differ when journal vouchers are linked.

The costing settings — how raw material and processing are valued — are on the **Update Job Order + Process Wise Net Cost** window (see [Update Job Order + Process Wise Net Cost - Configuration](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-utilities/update-job-order-+-process-wise-net-cost/update-job-order-+-process-wise-net-cost-configuration.md)).

***

### **Raw Material**

* Raw material is valued at the rate chosen in the costing settings (**RM Rate From** and **RM Rate As**) — for example the **Basic Rate** of the lot. The rate typed on the issue document is not used.
* For each raw material in each process, the quantity used is:
  * the **consumption** recorded against the Job Order — wastage recorded with it counts as consumed;
  * if no consumption is recorded for that material in that process, the quantity **issued minus the quantity returned**.
* So material issued but not returned is charged to the Job Order until consumption is recorded for it.
* Raw material issued without selecting a Job Order is not costed until it is linked to the Job Order with **Allocate Raw Material Issues to Job Orders**.

***

### **Processing**

* Each process adds its own **cost per piece**: the amount for that process ÷ the quantity processed in that process.
* The process **Overhead(%)** is added on top of the process amount. It is set in **Overhead(%)** on the **Create / Edit Process** window (Production\Production Setups\Setup Process Groups/Processes).
* The cost per piece of all the processes is then added up.
* The amount for a process comes from one of two places, chosen in the costing setting **Processing Rate From**:
  * **Production** — the wages entered on the production entries (quantity × rate).
  * **Process + Item** — the quantity produced × the item's rate for that process in **Setup Process Wise Item Rates**. The rate is looked up by **item name**: size-wise rates are not used, and an item that has only size-wise rates gets no processing cost.

> **Example — sizes at different rates**
>
> Ravi stitches 10 pieces of a kurta for one Job Order: 1 piece of size 26 at ₹100, and 2, 3 and 4 pieces of sizes 28, 32 and 34 at ₹60 each. The wages entered on the production entries are 100 + 120 + 180 + 240 = ₹640.
>
> Stitching cost per piece for the Job Order = ₹640 ÷ 10 = **₹64**. In the item-wise cost, each size keeps its own rate: ₹100 for size 26 and ₹60 for the others.
>
> This applies when **Processing Rate From** is **Production**.

***

### **Which Quantity the Cost Is Divided By**

Raw material and BOM Expenses are spread over the Job Order's **costing quantity**. For each finished item, Logic ERP takes:

1. the quantity **produced** — received back from the first process — or the quantity **received into stock**, whichever is **larger**. Goods are received into stock through a production entry that adds them into stock, or through **Stock Receipt - Production**;
2. if there is no production for the item, its **ordered quantity** — but while other items of the Job Order are in production, an item with no entries at all is left out.

If nothing has been made on the Job Order at all, Logic ERP uses the quantity purchased against the Job Order's **Purchase Order**, and otherwise the **ordered quantity**, as a placeholder.

The costing quantity of the Job Order is never less than the total quantity received into stock. Receiving only part of the production into stock does not lower it. It goes above the quantity produced only when more pieces reach stock than came out of the first process — for example when a later process yields more pieces.

**Why produced, not ordered?** Raw material, processing and wages are spent on what is actually being made. Dividing by the ordered quantity would understate the cost per piece when fewer pieces are made.

***

### **The Cost Per Piece While Goods Are Received**

Processing is charged **per piece of each process**. Raw material is spread over the costing quantity — the quantity produced, or the quantity received into stock if that is larger. So receiving goods into stock a few at a time does **not** change the Job Order's cost per piece.

> **Example — the Job Order's cost per piece**
>
> Meena's Job Order is for 10 shirts. Fabric worth ₹1,000 has been consumed.
>
> * Cutting: 10 pieces, ₹1,000 → ₹100 per piece
> * Stitching: 10 pieces, ₹800 → ₹80 per piece
> * Finishing: 6 pieces so far, ₹720 → ₹120 per piece
>
> Processing per piece = 100 + 80 + 120 = **₹300**. As shirts are received into stock, the Job Order's cost per piece stays the same:

| Shirts received into stock | Fabric divided by | Fabric per piece | Cost per piece |
| -------------------------- | ----------------- | ---------------- | -------------- |
| none yet                   | 10 produced       | ₹100             | **₹400**       |
| 4                          | 10 produced       | ₹100             | **₹400**       |
| 6                          | 10 produced       | ₹100             | **₹400**       |
| 10                         | 10 produced       | ₹100             | **₹400**       |

The last row assumes the remaining 4 shirts are also finished at ₹120 per piece. No overhead, BOM Expenses or journal vouchers are used in this example. These are the **Job Order's** figures; the item-wise cost of the shirt can differ. The cost per piece changes when more material is consumed, more processing is entered or more pieces are produced — run **Update Job Order + Process Wise Net Cost** again to see the current figure.

***

### **Sharing the Cost Between Finished Items**

When a Job Order makes more than one finished item (for example several sizes):

* **Raw material** is shared in proportion to **each item's quantity produced × its consumption per piece**. The consumption per piece is saved on the Job Order — taken from the item's raw material specification — and shown in the **CONS/UNIT** column of the Job Order's **Raw Material Details**.
* A raw material that is not in the specification is shared by each item's share of the quantity.
* **BOM Expenses** and **journal vouchers** are shared by each item's share of the quantity.
* If **Do not use finished Item weightage for Cost Calculation** is ticked in the costing settings, each item instead carries the full BOM Expenses, journal vouchers and raw materials not in the specification.

> **Example — one fabric, three sizes**
>
> A Job Order makes 2 pieces each of sizes S, M and L. The specification says S uses 1 metre, M uses 2 metres and L uses 6 metres per piece. 18 metres of fabric at ₹10 are consumed. The fabric is shared like this:

| Size | Metres (qty × per piece) | Fabric value | Fabric per piece |
| ---- | ------------------------ | ------------ | ---------------- |
| S    | 2 × 1 = 2                | ₹20          | ₹10              |
| M    | 2 × 2 = 4                | ₹40          | ₹20              |
| L    | 2 × 6 = 12               | ₹120         | ₹60              |

***

### **Journal Vouchers Linked to a Job Order**

* **On a voucher line** — pick the Job Order in the **JOB ORDER** column. A **debit** adds to the Job Order's cost and a **credit** reduces it.
* **For the whole voucher** — tick **Select Job Order** on the voucher. The voucher needs a customer or supplier line: the amount of the first such line is used — a credit to the party adds to the cost, a debit reduces it.
* The journal voucher configuration option **Job Order Selection Mandatory** stops a voucher from being saved without a Job Order.

***

### **Rejections**

Rejected quantities are recorded against the Job Order, but they are not used in the cost calculation. They do not raise or lower the cost.

***

### **Quantity Produced in the Reports**

These reports take the Job Order's quantity produced from the cost saved by **Update Job Order + Process Wise Net Cost**, so they show the same quantity the costing uses:

* **Job Order Wise Costing From RM/Processing**
* **Job Order + Production Unit Wise Production Status**
* **Production Rejection Report**
* **Job Order Wise Finished Goods Costing Report**
* **Job Order Wise Raw Material Consumed**
* **Job Order Wise Work In Progress**
* **Job Order Wise Cost Vs Sale Analysis**
* **Stock Ageing Analysis - Cross Tab**, for its consumed quantity and value columns

A Job Order that has never been costed has no saved quantity, so run **Update Job Order + Process Wise Net Cost** for it before using these reports. The **JO Qty Produced As** option is no longer shown in the configuration of the reports that had it, because the quantity always comes from the costing.

***

### **When the Cost Is Updated**

**Updated automatically** — saving any of these re-costs the Job Orders on that document:

* editing a **Job Order** (not when it is first created);
* **Raw Material Issues Against Job Order - Internal / External**, when a Job Order is selected on the issue — on save and on delete;
* **Allocate Raw Material Issues to Job Orders** — the Job Orders the issue is allocated to, and any Job Order it is taken off;
* **Issue Assigned Raw Material - Internal / External**;
* **Consumption/Receipt of RM against JO Issues - Internal / External**, and **Consumption/Receipt of RM against Assigned Issues - Internal / External**;
* production entered in **Receipts Against Issues - Internal / External**;
* **Stock Receipt - Production**, and purchases against a Job Order's Purchase Order;
* a **journal voucher** linked to a Job Order — on add, modify and delete.

**Not updated automatically** — run **Update Job Order + Process Wise Net Cost** after:

* **Issue For Processing** entries;
* a change to a process **Overhead(%)**, to **Setup Process Wise Item Rates**, or to item or lot master rates;
* a change to the costing settings.

Each update replaces the Job Order's earlier figures. No history of earlier runs is kept.


---

# 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/production/job-order-costing-concepts.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.
