The quick answer
Open the released WIP work order and choose Enter Completion. Set the operation range and completed quantity, keep Backflush selected when you want NetSuite to derive eligible component consumption, and review the Components and Operations tabs before saving. Verify the saved Work Order Completion, associated Work Order Issue, GL impact, and updated Built quantity.
This example completes 6 of 12 Aurora Control Units on WO-7430. It records a partial completion across operations 10 through 30 and leaves the work order open for the remaining six units. The screenshots use fictional example values.
Before you start
The account needs Work Orders and WIP, Manufacturing Routing, an effective BOM, configured work centers, and permissions to create issues and completions. Confirm that the work order has the intended released routing and BOM revision assigned. Check its location, subsidiary, and enough eligible component inventory at the source location.
Complete any required bin, lot, serial, or inventory-status detail. Labor, machine, and overhead amounts depend on the work-center, resource, time, rate, charge-item, cost-template, and costing setup. Do not add values that the routing and account do not support.
01 · Verify the WIP order
Open WO-7430 and confirm it is Released and WIP-enabled. Check the assembly, ordered quantity, Built quantity, effective routing, and included operations. Here, Quantity is 12, Built is 0, and the routing runs from Cut / Prep through Test to Final Assembly.
02 · Enter the completion scope
Click Enter Completion. Confirm Created From is WO-7430 and select Backflush. On the demonstrated form, set Starting Operation to 10 - Cut / Prep, Ending Operation to 30 - Final Assembly, Completed Quantity to 6, and Location to Reno. Operation-field labels can vary by form and release. Enter the production transaction date and verify that NetSuite assigns an open posting period; select a period only when the account exposes and permits that field.
03 · Review components and operations
On Components, compare each Required quantity with Previously Issued and Backflush Quantity. In this example, the BOM requires one of each component per assembly, yield is 100%, and no quantity was previously issued, so NetSuite derives six Sensor Boards and six Housings. Enter inventory detail for lot-, serial-, bin-, or inventory-status-controlled components before saving when the item and account require it.
Backflush does not guarantee that every BOM component will be issued. Eligibility, operation assignment, the selected operation range, prior issues, preferences, and inventory detail affect the result.
On Operations, confirm the completed quantity for every operation in scope. Review setup and run time only when those values come from the routing and the production record. An intermediate-operation completion can leave value in WIP. A completion through the final operation may transfer accumulated WIP into the finished assembly under the account’s costing configuration, so inspect the actual GL impact.
04 · Save and verify the posting
Click Save and resolve any validation message. The saved transaction in this example is WOC-7431. Open the work order and completion’s related-record area, or use the transaction links, and confirm that the completion and any backflush-generated issue are linked. Here the associated issue is WOI-7432. Exact labels and generated records can vary by NetSuite release, form, role, and manufacturing configuration.
Open GL Impact on the completion. In this replay, the completion debits Finished Goods Inventory and credits Work in Process for 750.00, with equal debit and credit totals. Review the issue separately when you need component-level posting detail. Accounts and amounts depend on the item costing method, manufacturing-cost setup, operation scope, prior issues, and whether this is the final operation.
05 · Reconcile the work order
Return to WO-7430. It now shows In Process, Built 6, and links to WOI-7432 and WOC-7431. The remaining six units are still open. A partial completion does not prove that the work order is closed, final cost is settled, or variance is zero.
Check the result
- Transactions: the completion and associated issue are saved and linked.
- Accounting: the completion GL impact balances and uses the expected accounts.
- Order: Built is 6 of 12 and the work order remains In Process.
Common questions
What must be verified before entering a WIP completion?
Confirm that the work order is Released, WIP-enabled, and assigned the intended BOM revision and routing. Also verify the assembly, ordered quantity, current Built quantity, operations, location, subsidiary, eligible component inventory, and any required bin, lot, serial, or inventory-status detail.
What values were used for the partial completion example?
For WO-7430, the example selects Backflush, uses starting operation 10 - Cut / Prep, ending operation 30 - Final Assembly, completes 6 units, and uses Reno. The order contains 12 units, so six remain after the completion.
Does backflush issue every BOM component automatically?
No. Backflush derives eligible component consumption, but the result depends on eligibility, operation assignment, the selected operation range, prior issues, preferences, yield, and required inventory detail. The example derives six Sensor Boards and six Housings because each requires one unit per assembly, yield is 100%, and nothing was previously issued.
What should I check after saving the completion?
Verify that the saved completion and any backflush-generated issue are linked to the work order. In the example, the transactions are WOC-7431 and WOI-7432. Inspect the completion’s GL Impact and review the issue separately for component-level posting detail.
Does a partial completion close the work order or prove that costs are settled?
No. After the example completion, WO-7430 remains In Process with Built 6 of 12, leaving six units open. The result does not prove that the order is closed, final cost is settled, or variance is zero. GL accounts and amounts depend on costing, manufacturing setup, prior issues, and operation scope.