NetSuite Assembly Build Checklist (Free, PDF/Excel)

0%

0 of 33 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

Item and BOM setup

Assembly item exists with the correct type (Assembly/Bill of Materials) and subsidiary accessCRITICALCosting method on the assembly item is chosen on purpose and recordedCRITICALBill of Materials is created and attached to the assembly itemCRITICALBOM revision has the right effective start date and is not obsoleteCRITICALComponent item records are active and not marked inactive or discontinuedQuantity per assembly and units of measure on each component line are verifiedYield or scrap percentages on components are set where they applyPhantom or sub-assembly components are marked as intended

Locations and inventory

Build location is the same location that holds the components, or transfers are plannedCRITICALAvailable quantity of each component at the build location covers the build quantityCRITICALLot or serial numbered components have lots/serials selected with enough quantityInventory 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 usedNegative inventory preference is understood so a short component does not post silently

Work order or build transaction

Work order or assembly build form uses the correct custom form and subsidiaryQuantity, start date and end date are set and reasonable against lead timeCRITICALPosting period is open for the build dateCRITICALRouting and operations exist if you use Advanced ManufacturingWork order is released before issuing components in a WIP flowDepartment, class and project fields follow your reporting rulesBuild user's role has permission to build assemblies at that location

Costing and GL

Component costs are current for standard costing items, or receipts are posted for average and FIFOCRITICALLabor and overhead rates apply through the routing or cost template where usedInventory, WIP and variance accounts on the items are mapped correctlyCRITICALTrial build in a sandbox shows the expected GL impactLanded cost on components is allocated before the build, not after

After the build

Finished quantity on hand increased by the built quantity at the right locationCRITICALComponent quantities reduced by the expected amountsGL impact reviewed and ties to inventory valuationWork order status moved to In Process, Built or Closed as expectedLot or serial numbers of the finished assembly are recorded where requiredVariances are reviewed before closing the work orderAny errors, such as insufficient components, are logged with the cause and fix

Every item should be checked or explicitly marked not applicable. Anything marked critical blocks the build until resolved.

Check your BOMs and builds automatically

Optional: have a read-only review run across your assemblies to find expired revisions, missing locations and orphan components.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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

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

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

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.

Frequently Asked Questions

Why does NetSuite say insufficient quantity when I build an assembly?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

NetSuite

More NetSuite tools

See all

NetSuite Assembly Build Checklist