Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Discrete Manufacturing

ERP

Inventory Management

Manufacturing

NetSuite Work Orders: Assembly Builds, WIP, Component Issues and Closing Variances

Sherman Hsieh
Share This Post!
Published
NetSuite Work Orders: Assembly Builds, WIP, Component Issues and Closing Variances

Last updated: November 3, 2026 · Independent guide · We do not sell rankings or coverage.

A NetSuite work order is a non-posting transaction that tells production which assembly to build, how many and from which components. You complete it in one of two ways: a single assembly build that consumes components and adds the finished item in one step, or the Manufacturing Work In Process (WIP) flow, where you issue components, enter completions and then close the order to post variances. Below are the setup steps in order, the reports that show open WIP and the setup choices behind most costing errors.

For the concepts behind two settings below, see our guides to backflushing and routing in manufacturing.

Before you start

  • License: Oracle describes Work Orders and Assemblies as an add-on module that is also included in the WIP and Routings and Advanced Manufacturing modules. Oracle does not publish prices; you get a quote from NetSuite (Oracle NetSuite, no date shown).
  • Costing method: only standard cost and average cost assemblies work with WIP. Assemblies on FIFO, LIFO or specific costing cannot use it, although their components can (Oracle, no date shown).
  • A sandbox: the WIP box on a work order cannot be cleared once a posting transaction is attached to it, so test the full cycle first (Oracle, no date shown).

Assembly builds, WIP and WIP with Routing compared

Option Transactions you enter What the GL shows mid-order Fits
Assembly build (with or without a work order) One build Nothing until the build posts; no WIP balance Kits and short runs finished the same day
WIP work order without routing Issue, completion, close Material sitting in the WIP account Multi-day runs where material cost matters most
WIP work order with Manufacturing Routing Issue, completions by operation with time, close Material plus labor, machine and overhead in WIP Shops that need operation-level cost and capacity

Only routed WIP orders support components per operation, reporting by operation step, and setup and machine time (Oracle, no date shown).

Step 1: Enable the features

Go to Setup > Company > Enable Features, open the Items & Inventory subtab, and check Assembly Items and Work Orders first. Then check Manufacturing Work In Process and save. WIP requires both of those features (Oracle, no date shown).

Step 2: Set default WIP and variance accounts

Go to Setup > Accounting > Accounting Preferences and open the Items & Transactions subtab. Set these defaults (Oracle, WIP accounts, no date shown; Oracle, accounting preferences, no date shown):

  • Default WIP Account (asset): receives component cost when you issue.
  • Default Scrap Account (expense): receives scrap entered on completions.
  • Default WIP Cost Variance Account (expense): used for average or actual cost assemblies when the reconciliation amount cannot go back to the asset account because the goods have shipped.
  • Default Production Price Variance Account and Default Production Quantity Variance Account: used by standard cost items.

Average cost users should also review Average Cost Completion Unit Cost: Average Cost leaves deviations for the Inventory Adjustment Worksheet, while Open WIP Amount values completions from the open WIP balance.

Step 3: Set up the assembly item

Go to Lists > Accounting > Items and edit the assembly. On the Basic subtab, confirm the WIP Account, Scrap Account and WIP Cost Variance Account; all three are required if WIP is checked for any location (Oracle, no date shown).

For standard cost items, confirm the production variance accounts and run a cost rollup. With routing, the rollup uses the default routing (or the first one created) and divides setup cost by the Costing Lot Size on the Locations subtab, which defaults to 1 (Oracle, routing standard cost, no date shown; Oracle, routing costing, no date shown).

Step 4: Set up routing costs (routing users only)

Create cost categories at Setup > Accounting > Setup Tasks > Accounting Lists, click New, then Cost Category, and pick a cost type such as Labor Setup, Labor Run, Machine Run or one of the overhead types (Oracle, no date shown). Then build templates at Lists > Supply Chain > Manufacturing Cost Templates > New, pairing each category with a manufacturing charge item and a rate (Oracle, no date shown).

Step 5: Create the work order

Go to Transactions > Manufacturing > Enter Work Orders. Select the Assembly, enter the Quantity, set production dates, and select a Location, which is required for WIP orders (Oracle, no date shown). Check WIP to use issues, completions and closes instead of a single build; the box is available only when the status is Released, and Manufacturing Routing becomes available only once WIP is checked (Oracle, no date shown).

The work order posts nothing itself. Oracle describes a Released order as one where no transaction has posted, and the postings come from the builds, issues, completions and closes entered against it (Oracle, assembly work orders, no date shown). Once a build is attached, the assembly is locked and the quantity can change only by closing the order and creating a new one.

Step 6: Issue components

From the work order, click Issue Components (Oracle, no date shown), or issue for many orders at once at Transactions > Manufacturing > Issue Components (Oracle, no date shown). The issue credits the component asset account at the stock location and debits WIP (Oracle, no date shown).

Step 7: Enter completions

From the order, click Enter Completion or Enter Completion with Backflush (Oracle, no date shown), or use Transactions > Manufacturing > Enter Completions for several orders. Check Backflush only if you want NetSuite to consume components in the work order’s proportions at the same time; otherwise the completion records output only (Oracle, no date shown).

A completion moves the assembly value out of WIP into the assembly asset account. On routing orders, time logged on the completion debits WIP and credits labor at rate × resources × hours (Oracle, routing costing, no date shown).

Step 8: Close the order and post variances

For one order, go to Transactions > Manufacturing > Enter Work Orders > List, click View on the order, click Close and save (Oracle, no date shown). For a batch, go to Transactions > Manufacturing > Close Work Orders and check Include In Process Work Orders to see In Process and Built orders (Oracle, no date shown).

Two filters help you review first. Under-Produced Variance Tolerance (%) uses (quantity ordered − quantity built) ÷ quantity ordered. Production Variance Tolerance (%) uses the absolute value of remaining WIP ÷ WIP of the assembly. Oracle recommends component cost decimal precision of 2 to avoid rounding variances (Oracle, no date shown). The close clears what is left in WIP to the variance accounts (Oracle, no date shown).

If you do not use WIP

Build released orders at Transactions > Manufacturing > Build Work Orders, or record a standalone build at Transactions > Manufacturing > Build Assemblies (Oracle, building work orders, no date shown; Oracle, building assemblies, no date shown). For standard cost assemblies, NetSuite posts production price and production quantity variances when you enter the build (Oracle, no date shown). Avoid Transactions > Manufacturing > Mark Work Orders Built, which creates no variances (Oracle, no date shown).

Worked example: one WIP order from issue to close

Illustration only. A standard cost assembly costs $20: two units of component A at $8 and one unit of component B at $4. You release a WIP order for 100 units. The line issues 210 units of A ($1,680) and 100 of B ($400), then completes 100 units.

Account Debit Credit Note
WIP $2,080 Issue: 210 A and 100 B at standard
Component inventory $2,080 Issue
Assembly inventory $2,000 Completion: 100 units at $20
WIP $2,000 Completion
Production quantity variance $80 Close: $8 × (200 − 210), unfavorable
WIP $80 Close leaves WIP at zero for this order

Until the close posts, the $80 overstates inventory. Compare a sandbox close’s GL Impact with this table before you rely on the account mapping. Our guide to material usage variance covers how to investigate a variance like this one.

Reports that show open WIP

  • WIP account balance: the balance sheet total to reconcile. It should equal issued cost plus routing labor and overhead, less completions, on orders not yet closed.
  • Close Work Orders page: with In Process orders included and tolerances set, it works as a month-end review list of open orders.
  • Saved search: work orders in In Process or Built status with no close give you an aging list by assembly and location. Our NetSuite saved search guide covers the build.
  • Manufacturing workbook: with SuiteAnalytics Workbook enabled, go to Analytics > New Workbook and choose Manufacturing Transaction [Beta] to pivot issues and completions by assembly (Oracle, no date shown).
  • Advanced Manufacturing reports: accounts with Advanced Manufacturing get a Work Order Report and a Material Issue Report under Advanced Manufacturing > Planning Reports (Oracle, no date shown).

Common mistakes and how to fix them

  • Orders never closed. Finished orders left In Process or Built keep residual cost in WIP and variances off the income statement. Close them before each period close.
  • Mismatched WIP locations. Oracle requires the WIP line location to match on the issue, completion and close (Oracle, no date shown).
  • Standard cost changes mid-order. A standard cost update creates a separate revaluation transaction for each partially built order, so close what you can first (Oracle, no date shown).
  • Wrong costing method. A FIFO assembly cannot use WIP. Fix the method before go-live.
  • Routing rollup on the wrong routing or lot size. Mark the correct default routing and set Costing Lot Size to your typical run, or setup cost is spread over one unit.

Limitations of the native feature

We found no dedicated WIP aging or variance bridge report in Oracle’s base documentation, so most teams combine the Close Work Orders page, saved searches and the WIP balance. The workbook source is still labeled Beta, labor and operation reporting need routing, and the shop floor reports need Advanced Manufacturing.

When companies add a third-party tool

Manufacturers add a SuiteApp or MES when operators need tablet time and scrap capture, when scheduling outgrows routing, or when the controller wants a variance bridge per order. Confirm the tool writes native issues, completions and closes rather than journal entries, or WIP will stop reconciling to the orders.

How we researched this

We read Oracle’s help page for each transaction and preference on November 3, 2026, and took every menu path from them. We also reviewed the top-ranking guides for this search, from BrokenRubik (April 2, 2026), Anchor Group (September 17, 2026) and Houseblend (October 27, 2026), all of which sell NetSuite services. The worked example is our illustration.

Related guides

Frequently asked questions

What is the difference between a work order and an assembly build in NetSuite?

A work order is a non-posting plan listing the assembly, quantity and components. An assembly build is the posting transaction that consumes components and stocks the finished item.

Do I need WIP and Routings to use work orders?

No. Work orders and builds run on the Work Orders and Assemblies module alone. You need WIP for issues, completions and closes, and routing for labor and operation tracking.

Why is there still a balance in my WIP account?

Usually orders were issued and completed but never closed. Find them on the Close Work Orders page with In Process orders included, then close the finished ones.

When does NetSuite post work order variances?

On WIP orders, the close transaction clears remaining WIP to the variance accounts. On non-WIP standard cost orders, production price and quantity variances post when you enter the assembly build. Marking an order built creates no variances.

Can I use FIFO costing for a WIP assembly?

No. Oracle allows only standard cost and average cost assemblies on WIP work orders.

Sources

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read