> 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/production-setups/setup-bom-expenses.md).

# Setup BOM Expenses

## How to Set Up BOM Expenses and Apply Them to a Job Order?

In this tutorial, we will learn how to define **BOM Expenses** in Logic ERP and how they are added to the cost of a Job Order. BOM Expenses are charges over and above raw material and processing — for example **overheads**, **logistics**, **washing**, a **rejection allowance** or a **margin**. Each expense can be a **percentage** or an amount **per piece**, and can be **added** to or **subtracted** from the cost.

For how BOM Expenses fit into the full cost of a Job Order, see [Job Order Costing - Concepts](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/job-order-costing-concepts.md).

***

### **Open Setup BOM Expenses**

* Navigate to Production\Production Setups and select **Setup BOM Expenses**.
* The grid lists every expense with these columns:
  * **SNO.**
  * **EXPENSE NAME** — typed in capitals. Every expense needs a name, and two expenses cannot have the same name.
  * **EXPENSE TYPE** — **Percent Wise** or **Per Unit Wise**.
  * **EXPENSE / UNIT** — used only for **Per Unit Wise** expenses (see below).
  * **DEFAULT VALUE** — the percentage, or the amount.
  * **BASIC OR CUMULATIVE** — what a percentage is calculated on (see below).
  * **ADD OR LESS** — **+** adds the expense to the cost, **-** subtracts it.
* A new line starts as **Percent Wise**, **EXPENSE / UNIT** 1, **Basic** and **+**, with **DEFAULT VALUE** blank.

***

### **Per Unit Wise Expenses**

* For a **Per Unit Wise** expense, **DEFAULT VALUE** is the amount for the number of pieces in **EXPENSE / UNIT**.
* Logic ERP works out the amount for a single piece from these two values.
* **Example:** **EXPENSE / UNIT** 12 and **DEFAULT VALUE** 48 means ₹48 for 12 pieces, which is **₹4 per piece**.
* On a Job Order, the per-piece amount is multiplied by the Job Order quantity.

***

### **What a Percentage Is Calculated On**

The **BASIC OR CUMULATIVE** column decides the base for a **Percent Wise** expense:

* **Basic** — raw material + processing.
* **RM Value** — raw material only.
* **Processing Value** — processing only.
* **Cumulative** — raw material + processing + **every expense line above it**. A line marked **-** above it reduces the base.

Every expense amount is rounded to 2 decimals. On the Job Order and in the **Cost Sheet**, each raw material line is rounded to 2 decimals before it is added into the base.

***

### **Set the Order of the Expenses**

The order of the lines matters for **Cumulative** expenses, because each one is calculated on everything above it.

* **Save** the expenses first — the order window lists only saved expenses, and changes not yet saved in the grid are lost when it closes.
* Click **Expense Order**.
* In the **Set BOM Expense Order** window, arrange the expenses in the order they should be calculated and click **Save** in that window. **Set in Alphabetical Order** puts them in name order.
* The grid then lists the expenses in this order.

***

### **Save and Delete**

* Click **Save** and confirm to save the expenses.
* An expense that is already used on a Job Order cannot be deleted. Logic ERP shows **Details Exists Against Expense** followed by the expense name.

***

### **Apply the Expenses to a Job Order**

The expenses defined here are **defaults**. Each Job Order holds its own copy, which can be changed for that Job Order.

* Open the **Job Order** and click **Raw Material Details**.
* In the **Job Order Wise Raw Material Details** window, click **BOM Expenses**.
* The **Setup BOM Expenses Details** window opens. On a new Job Order it is empty.
* Click **Refresh from Master** to bring in the expenses from **Setup BOM Expenses** that are not yet on this Job Order.
* Change the type, **EXPENSE / UNIT**, **DEFAULT VALUE**, base or **+ / -** for this Job Order if needed, or add another expense from the master on a new line.
* Click **Expense Order** to change the order for this Job Order (window **Set Expense Order**), then click **Save**.
* The changes are stored with the Job Order when you accept the **Raw Material Details** window and save the Job Order.

To control saving a Job Order without BOM Expenses, use the Job Order configuration option **BOM Expenses Entry As**: **Prompt If not Exists** asks before saving, and **Do not Allow saving If not Exists** stops the save.

***

### **Worked Example**

> **Example — cumulative expenses on a Job Order**
>
> Priya's Job Order is for 1 jacket. Raw material is ₹232.75 and processing is ₹68, so raw material + processing = **₹300.75**. The expense lines, in this order, are:

| Expense                   | Type          | Base             | Amount                      | Running total |
| ------------------------- | ------------- | ---------------- | --------------------------- | ------------- |
| Raw material + processing |               |                  |                             | ₹300.75       |
| OVERHEAD                  | 50%           | Processing Value | ₹34.00                      | ₹334.75       |
| FACTORY OVERHEAD          | 50%           | Processing Value | ₹34.00                      | ₹368.75       |
| LOGISTICS                 | ₹4 per piece  | —                | ₹4.00                       | ₹372.75       |
| TRIMS                     | ₹2 per piece  | —                | ₹2.00                       | ₹374.75       |
| LINING                    | ₹3 per piece  | —                | ₹3.00                       | ₹377.75       |
| PACKING                   | ₹3 per piece  | —                | ₹3.00                       | ₹380.75       |
| WASHING                   | ₹10 per piece | —                | ₹10.00                      | ₹390.75       |
| REJECTION                 | 2%            | Cumulative       | 2% of ₹390.75 = **₹7.82**   | ₹398.57       |
| MARGIN                    | 10%           | Cumulative       | 10% of ₹398.57 = **₹39.86** | ₹438.43       |

The cost of the jacket is **₹438.43**. REJECTION is calculated on everything above it, not only on the line just before it. MARGIN then includes REJECTION.

***

### **How BOM Expenses Reach the Actual Cost**

* When the Job Order is costed (see [Update Job Order + Process Wise Net Cost](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-utilities/update-job-order-+-process-wise-net-cost.md)), the expenses are calculated on the Job Order's **actual** raw material used and processing (including process **Overhead(%)**), and **per piece** expenses are multiplied by the Job Order's costing quantity.
* The total of the expenses is added to the cost per piece of the Job Order.
* It is shared between the finished items by each item's share of the quantity, unless **Do not use finished Item weightage for Cost Calculation** is ticked.
* The **Cost Sheet** report calculates the expenses in the same way, but on the Job Order's **planned** raw materials and process rates, and multiplies per piece expenses by the Job Order's ordered quantity.


---

# 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/production-setups/setup-bom-expenses.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.
