> 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/reconciling-production-wip.md).

# Reconciling Production WIP

## How to Check That the Production Work-in-Progress Figures Agree?

In this article, we will learn how to check that the **production work-in-progress (WIP)** figures in Logic ERP agree with each other: the WIP value in the accounts, the WIP of each Job Order, and the quantities pending at each process. It explains where each figure comes from, a routine to follow at the end of each month, the reports to compare, and what to do when the figures do not agree.

***

### **Two Kinds of WIP**

* **WIP value** — the value of the raw material that has gone into production but has not yet come out as finished goods: **raw material issued − raw material returned − value received into stock**. This is the figure that goes into the accounts.
* **WIP quantity** — the pieces pending at each process: produced in one process and not yet taken further, or issued for processing and not yet received back.

The two are not compared with each other. Where a quantity report also shows a value, it is not the raw material WIP: **Branch Wise Work In Progress Analysis** values pending quantities at the item rates chosen in the report, and **Work In Progess - Ageing Analysis** at the Job Order's cost up to that process.

***

### **Where the WIP Value Comes From**

**Stored WIP — used by the accounts**

* Logic ERP keeps a running WIP value. It is updated every time one of these entries is saved, modified or deleted:
  * a raw material issue against a Job Order;
  * a raw material return against a Job Order;
  * a production entry that adds the goods into stock;
  * a **Stock Receipt - Production** entry.
* Each entry is added at the rate it carries:
  * issues and returns — the raw material rate from the costing settings (**RM Rate From** and **RM Rate As** on **Update Job Order + Process Wise Net Cost**) at the time the entry is saved;
  * goods received — the Job Order's raw material cost per piece at the time the production entry was saved.
* **Trading Account - Balance Sheet Groups** and **Balance Sheet - Balance Sheet Groups** show this stored WIP when their option **Include Production WIP Stock Value** is ticked. The row is titled **WIP Stock Value** in the Trading Account (another title can be given in **Production WIP Stock Value Title**) and **WIP Value** in the Balance Sheet. It does not appear when the WIP is zero.

**Job Order WIP — worked out when the report runs**

* **Job Order Wise Work In Progress** and **Job Order Wise Costing From RM/Processing** (column **PRODUCTION WIP VALUE**) work out the WIP of each Job Order from the entries every time they are run, using the same rates stored on the entries.

**Keeping the WIP up to date**

The rates on the entries are not changed afterwards. When a Job Order is costed again, or item, lot or costing rates are changed, both the stored WIP and the Job Order reports keep the old rates. **Production WIP Reconstruction** puts the current rates on the entries and rebuilds the stored WIP from them, one financial year at a time. Rates changed in one year can affect entries made in a later year, so run it for every year from the earliest one affected.

Because both figures use the same rates, they disagree only when the stored WIP has missed an entry, or when an entry is linked to a Job Order that cannot be found (see **When the Figures Do Not Agree**).

***

### **Month-End Routine**

1. Run **Update Job Order + Process Wise Net Cost** (Production\Production Utilities), so that every Job Order has its current raw material cost per piece.
2. Run **Production WIP Reconstruction** (Production\Production Utilities) for the current financial year, and for every earlier year from the earliest one in which entries, rates or Job Order costs have changed. Take a backup first — see [Production WIP Reconstruction](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-utilities/production-wip-reconstruction.md).
3. Carry out **Check 1** and **Check 2** below. Carry out **Check 3** when you also want to check the pending quantities.

***

### **Check 1: Accounts WIP Against Job Order WIP**

This check compares the WIP in the accounts with the total WIP of all Job Orders.

**In the accounts**

* Navigate to Reports/Queries\Balance Sheet and open **Trading Account - Balance Sheet Groups**.
* Tick **Include Production WIP Stock Value**.
* Do not tick **Show Data For Current Branch Only**, and do not select branches, so that all branches are included. The user running the report needs access to all branches.
* Note the **WIP Stock Value** on the report's end date.

**In the Job Order report**

* Navigate to Production\Production Reports/Queries\Production Raw Material Reports and open **Job Order Wise Work In Progress**.
* Use the **same end date**.
* Add the **PRODUCTION WIP VALUE** column and tick **Grand Totals**.
* Do not select any Process, Job Order, Item or branch. This keeps the **Brought Forward** rows — Job Orders that still have WIP but no activity in the period — in the total.
* Note the grand total of **PRODUCTION WIP VALUE**.

**Result**

After the month-end routine, the two figures are the same. A difference of a few paise can come from rounding. For anything larger, see **When the Figures Do Not Agree** below.

***

### **Check 2: Job Order by Job Order**

This check compares the WIP of each Job Order in the two Job Order reports.

* Open **Job Order Wise Costing From RM/Processing** (Production\Production Reports/Queries\Production Finished Goods Reports) and add the **PRODUCTION WIP VALUE** column.
* Open **Job Order Wise Work In Progress** with the same end date and no branch selected.
* For each Job Order, **PRODUCTION WIP VALUE** is the same in both reports. Both work it out up to the report's end date.
* **Job Order Wise Costing From RM/Processing** lists Job Orders whose Job Order date falls in its period, and shows the whole Job Order, whichever branch its entries were made in. Compare it with **Job Order Wise Work In Progress** run for all branches.

***

### **Check 3: Pending Quantities**

These three reports, under Production\Production Reports/Queries\Production Finished Goods Reports, work out the quantity pending at each process in the same way — production not yet taken further, and issues for processing not yet received back:

* **Stock Report - Stock Status + Production WIP Report**
* **Work In Progess - Ageing Analysis**
* **Branch Wise Work In Progress Analysis** — read its **closing** columns; its other period columns show movements, not pending quantities.

Run them for the same date and the same branches, and their pending quantity for each process should agree.

* **Stock Report - Stock Status + Production WIP Report** takes its branches from **Branch Selection For Production** in its configuration. Set the same branches there.
* In **Work In Progess - Ageing Analysis**, do not use **Filter On AD**, which leaves out rows outside the chosen age bracket.
* Set **Do Not Use Next Process For Pending Entries** the same way in every report you compare. Each report saves this setting in its own configuration.
  * Ticked — pending production is shown against the process that produced it.
  * Not ticked — it is shown against the next process it goes to.
  * Issues for processing are always shown against the process they were issued to.
  * With no process selected, the total pending quantity is the same either way; only the split between processes changes. With processes selected, the total for those processes can change.

**Production Status Report** also shows pending quantities, but it works them out differently — for example, it leaves out raw material issues to processes and filters by branch only in some report types — so it is not used for this check.

***

### **When the Figures Do Not Agree**

| What you see                                                              | Likely reason                                                                                                                                                                                                                                              | What to do                                                                          |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| The accounts WIP and the Job Order WIP total differ                       | An entry did not reach the stored WIP, or the stored WIP was not rebuilt for every year after rates were rewritten                                                                                                                                         | Run **Production WIP Reconstruction** for every year from the earliest one affected |
| They still differ after Reconstruction                                    | Raw material issued against a Job Order whose Job Order cannot be found. It counts in the accounts but under no Job Order                                                                                                                                  | Ask your Logic ERP support team to check these issues                               |
| One Job Order differs between the two Job Order reports                   | **Job Order Wise Work In Progress** was run for selected branches                                                                                                                                                                                          | Run it for all branches                                                             |
| A Job Order is missing from **Job Order Wise Costing From RM/Processing** | Its Job Order date is outside the report's period                                                                                                                                                                                                          | Widen the period                                                                    |
| A Job Order shows negative WIP                                            | See **Why WIP May Not Be Zero** in [Job Order Wise Work In Progress](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-reports-queries/production-raw-material-reports/job-order-wise-work-in-progress.md) |                                                                                     |
| Pending quantities differ between the quantity reports                    | Different dates, branches or processes, a different **Do Not Use Next Process For Pending Entries** setting, or one of the report options in **Check 3**                                                                                                   | Run them with the same settings                                                     |

> **Example — a receipt missing from the accounts WIP**
>
> At the end of May, Kiran runs **Trading Account - Balance Sheet Groups** and sees a **WIP Stock Value** of ₹5,60,000. The grand total of **PRODUCTION WIP VALUE** in **Job Order Wise Work In Progress** for the same date is ₹4,00,000.
>
> The difference, ₹1,60,000, is a **Stock Receipt - Production** of 400 shirts at a raw material cost of ₹400 per shirt that did not reach the stored WIP when it was saved.
>
> No Job Order has been costed again and no rates have changed since the entries were saved. Kiran runs **Production WIP Reconstruction** for the year. The stored WIP is rebuilt from the entries, and **Trading Account - Balance Sheet Groups** now shows ₹4,00,000, the same as the Job Order report.

For how the cost of a Job Order is worked out, see [Job Order Costing - Concepts](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/job-order-costing-concepts.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-learning-hub-tutorials-and-best-practices/production/reconciling-production-wip.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.
