WIP accounting looks simple until a project crosses month-end or a production run is still unfinished when the books close. At that point, the real question is not whether work exists, but how much cost has already been built into unfinished goods or services without distorting margin, cash flow, or revenue timing. I focus here on the practical version: what belongs in WIP, how the balance is built, where it appears, and which mistakes create the biggest errors.
The essentials behind WIP in plain English
- WIP is the accumulated cost of partially completed goods or services, not finished inventory.
- The usual building blocks are direct materials, direct labor, and applied overhead.
- In project work, percent complete and billing status matter as much as the cost total.
- Underbilling can create a contract asset; overbilling can create a contract liability.
- Stale estimates, weak overhead allocation, and cutoff errors are the fastest ways to distort the number.
What work in progress really measures
I think of WIP as the bridge between raw input and finished output. It captures the cost of work that has started but has not yet become a saleable product, a completed job, or a billable service, which is why it sits at the center of both inventory accounting and project accounting.
In manufacturing, the balance usually lives inside inventory. In construction, engineering, and professional services, it often sits beside revenue recognition because the bigger question is how much of the contract has actually been earned. That distinction matters: a project can look profitable on paper only if the estimate behind it is current and the costs are coded correctly.
For leaders, the number matters for more than bookkeeping. It affects gross margin, working capital, lender confidence, board reporting, and whether management sees problems early enough to fix them before a job turns into a loss.
Once that distinction is clear, the next step is turning the concept into a number that can survive a close.
How the balance is built step by step
The cleanest way to build WIP is to start with direct costs, add the overhead that belongs to the job, and then test whether the result still makes sense against progress and realizable value. In practice, I usually separate the calculation into cost accumulation and progress measurement, because those are related but not identical.
| Cost element | Example amount | Why it belongs in WIP |
|---|---|---|
| Direct materials | $120,000 | Physical inputs consumed in the job or batch |
| Direct labor | $80,000 | Payroll that can be traced straight to the work |
| Applied overhead | $50,000 | Shared production or project costs allocated by a rational base |
| Total WIP | $250,000 | The amount carried until completion or billing logic moves it forward |
If a manufacturer uses standard costing, I would expect the WIP balance to carry standard material, labor, and overhead rates until variances are reviewed and closed. That is normal, but it also means a stale rate can quietly push the balance out of line with reality.
For project work, the logic often shifts to a cost-to-cost measure of progress: percent complete = costs incurred to date ÷ estimated total costs. That works well when cost tracks progress closely. It works less well when materials are bought early, subcontractors are front-loaded, or a contract has unusual milestone payments.
For example, if a contractor has a $1,000,000 contract, expects $800,000 in total cost, and has incurred $480,000 so far, the job is 60 percent complete. Earned revenue is then $600,000, even if only $540,000 has been billed. In that case, the difference is a $60,000 underbilling, which is the kind of gap management needs to see early.
That estimate is only half the story; the report still has to land in the right place on the books.
Where it lands on the financial statements
On the balance sheet, inventory-style WIP is usually a current asset. On long-term contracts, the same underlying work may show up as a contract asset or a contract liability depending on whether billings are behind or ahead of performance. That is why the balance sheet can look healthy while the underlying project is already drifting.
| Status | Balance sheet effect | What it means in practice |
|---|---|---|
| Work earned exceeds billings | Contract asset or underbilling | The company has performed work it has not yet invoiced enough for |
| Billings exceed work earned | Contract liability or overbilling | The company has billed ahead of the work delivered |
| Goods are still being manufactured | Inventory on the asset side | The cost sits in WIP until the units are finished and transferred |
I also like to look at the report columns rather than only the ending balance. A useful WIP schedule normally includes contract value, cost to date, estimated cost to complete, earned revenue, billings to date, and forecast gross margin. Those lines tell you whether the estimate is still believable or whether the job is starting to tell a different story.
When you move from the balance sheet to the operating model, the industry context starts to matter much more.
Why industry context changes the treatment
Manufacturing, construction, and service firms all talk about unfinished work, but they do not always mean the same accounting object. A factory is tracking goods moving through stages of completion; a contractor is tracking earned revenue against costs; a services firm is often tracking unbilled time and contract progress.
| Industry | Typical WIP focus | Main risk | Best control |
|---|---|---|---|
| Manufacturing | Materials, labor, and factory overhead embedded in unfinished units | Scrap, yield loss, and outdated standard costs | Physical counts and variance review |
| Construction | Cost to date versus estimate to complete on active jobs | Scope changes, claims, and billing lag | Monthly job cost review and change-order discipline |
| Professional services | Unbilled time, milestone progress, and accrued revenue | Write-offs, utilization drift, and weak timesheet coding | Time entry controls and billing reconciliation |
For services, I would be especially careful not to treat every unbilled hour as equal. Some hours are fully recoverable, some are partly billable, and some should never have been capitalized into project progress in the first place. That is why the same label can hide very different economics across firms.
That difference is also where most reporting mistakes begin.
The mistakes that distort margins and cash flow
When I review a weak WIP schedule, the problem is usually not one big error but a stack of small ones. A stale estimate here, a miscoded labor bucket there, and suddenly the report is telling a story the project team no longer believes.
- Treating purchased materials as earned progress too early - buying steel, equipment, or software licenses does not automatically mean the work is equally complete.
- Letting estimates to complete go stale - if scope changed last month and the forecast did not, the margin is probably fiction.
- Misallocating overhead - overhead rates that no longer reflect labor mix, machine time, or project structure can push WIP too high or too low.
- Confusing billings with revenue - cash collected or invoices sent are not the same thing as earned value.
- Ignoring rework, scrap, and idle time - those costs may need separate treatment instead of being buried in normal progress.
- Skipping lower-of-cost-or-NRV testing - inventory-style WIP still has to be recoverable, not just recorded.
- Failing to reconcile the subledger to the general ledger - if the job system and the books disagree, the close is already compromised.
In 2026, the biggest mistake is still the oldest one: letting assumptions age while the work keeps moving. The companies that avoid trouble are usually not the ones with the fanciest software; they are the ones that update estimates quickly and challenge anomalies before the close.
A disciplined monthly close is the fastest way to catch those problems before they become a margin surprise.
The monthly controls that keep WIP useful
The best close is not the most detailed one; it is the one that forces the right conversations. I would check three things every month: whether the estimate to complete is current, whether the billing position matches progress, and whether the general ledger agrees with the project or manufacturing subledger.
- Reconcile job-cost or production reports to the general ledger before numbers go out to management.
- Refresh the estimate to complete on every material job, not just the ones already in trouble.
- Review underbillings and overbillings together so cash flow and performance are seen in the same frame.
- Compare actual margin to original bid margin and the latest forecast margin.
- Escalate any job with major scope change, rework, claims, or negative margin drift.
- Check whether any inventory WIP needs a write-down because market value or net realizable value has moved.
Automation helps here, but it does not replace judgment. I would trust software to move the data and flag exceptions; I would still rely on a human review to decide whether the assumptions behind the number are actually defensible. That is where WIP stops being bookkeeping and becomes a governance tool.
The practical test is simple: if the WIP schedule can explain where profit is coming from, where cash is tied up, and what changed since the last close, it is doing its job. If it cannot, the fix is not more spreadsheet detail; it is better cost coding, fresher estimates, and tighter billing discipline. That is why control over unfinished work belongs in the same conversation as margin management, credit risk, and operational governance.
