# NetSuite Assembly Build Checklist > Source: https://netray.co/tools/netsuite-assembly-build-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A pre-build and post-build checklist for NetSuite assembly items and work orders, covering setup, inventory and costing checks. ## Category netsuite ## Erp NetSuite ## Industry Discrete Manufacturing ## Audience - NetSuite administrator - Production planner - Inventory controller ## Tool **Kind:** checklist **Groups:** #### Item and BOM setup **Items:** **Text:** Assembly item exists with the correct type (Assembly/Bill of Materials) and subsidiary access **Critical:** true **Text:** Costing method on the assembly item is chosen on purpose and recorded **Critical:** true **Text:** Bill of Materials is created and attached to the assembly item **Critical:** true **Text:** BOM revision has the right effective start date and is not obsolete **Critical:** true Component item records are active and not marked inactive or discontinued Quantity per assembly and units of measure on each component line are verified Yield or scrap percentages on components are set where they apply Phantom or sub-assembly components are marked as intended #### Locations and inventory **Items:** **Text:** Build location is the same location that holds the components, or transfers are planned **Critical:** true **Text:** Available quantity of each component at the build location covers the build quantity **Critical:** true Lot or serial numbered components have lots/serials selected with enough quantity Inventory status or bin is correct for components (not on hold or in quarantine) Bins are defined for the finished assembly at the build location where bins are used Negative inventory preference is understood so a short component does not post silently #### Work order or build transaction **Items:** Work order or assembly build form uses the correct custom form and subsidiary **Text:** Quantity, start date and end date are set and reasonable against lead time **Critical:** true **Text:** Posting period is open for the build date **Critical:** true Routing and operations exist if you use Advanced Manufacturing Work order is released before issuing components in a WIP flow Department, class and project fields follow your reporting rules Build user's role has permission to build assemblies at that location #### Costing and GL **Items:** **Text:** Component costs are current for standard costing items, or receipts are posted for average and FIFO **Critical:** true Labor and overhead rates apply through the routing or cost template where used **Text:** Inventory, WIP and variance accounts on the items are mapped correctly **Critical:** true Trial build in a sandbox shows the expected GL impact Landed cost on components is allocated before the build, not after #### After the build **Items:** **Text:** Finished quantity on hand increased by the built quantity at the right location **Critical:** true Component quantities reduced by the expected amounts GL impact reviewed and ties to inventory valuation Work order status moved to In Process, Built or Closed as expected Lot or serial numbers of the finished assembly are recorded where required Variances are reviewed before closing the work order Any errors, such as insufficient components, are logged with the cause and fix **Scoring Note:** Every item should be checked or explicitly marked not applicable. Anything marked critical blocks the build until resolved. ## Content **Intro:** Most NetSuite assembly build errors come from a short list of causes: components not available at the build location, a BOM revision that is expired or missing, a closed posting period, or a costing setup nobody reviewed. This checklist walks through them before and after the build. **Sections:** #### How to use the checklist **Body:** Work through the groups in order. Setup items usually need to be checked only when an assembly is new or changed, while inventory and transaction items are checked on every build. Tick items off in the tool, add your own notes in the exported file, and keep the PDF with the work order for audit. Critical items are those that cause failed builds or wrong ledger postings if missed. #### Why builds fail **Body:** The common message is insufficient quantity of components. It is usually not a missing receipt but stock sitting at another location, committed to another order, in a different inventory status, or lot picked with less quantity. Check on-hand, available and committed numbers for each component at the build location, not at company level. #### Costing considerations **Body:** The cost of the finished item comes from component cost plus any labor and overhead, using the costing method of the assembly item. With standard costing, differences against standard land in variance accounts. With average costing, the build adds a cost layer that affects later builds. Decide the method before go-live because changing it later has accounting consequences. #### Common mistakes **Body:** Teams build in the wrong location, forget to release the work order before issuing, build with an expired BOM revision, or leave work orders Built without closing. A weekly saved search for Built but not Closed work orders, and another for open work orders past their end date, catches most of them. **Cta:** If your planners keep chasing shortages and build errors, Netray can add a read-only question layer over NetSuite so they can ask where a component actually sits. **Faq:** #### Why does NetSuite say insufficient quantity when I build an assembly? **Answer:** At least one component lacks available quantity at the build location. Stock may be in another location, committed to other orders, in a status that is not available, or from lots with too little quantity. Check available quantity per component by location. #### What is the difference between an assembly build and a work order? **Answer:** An assembly build converts components into the finished item in one transaction. A work order adds a plan, with optional issue, completion and close steps when WIP and routing are used. Many companies use one or the other, not both. #### Which costing method should an assembly use? **Answer:** It depends on your accounting policy. Standard costing suits stable products and variance reporting, while average costing suits fluctuating purchase prices. Agree the method with your controller before you build, since changing it later affects valuation. #### Can I build an assembly in a closed period? **Answer:** Not unless the period is open for the user and transaction type. Move the build date into an open period or have the controller reopen the period, then record why in your close notes. ## Search terms netsuite assembly build checklist, netsuite assembly build errors, netsuite assembly item setup, netsuite build assembly insufficient components, netsuite bom setup checklist, netsuite manufacturing go live checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json