Standard, average and actual costing in NetSuite manufacturing, and the variances each one produces.
Costing decides what a finished item is worth, what a job actually cost, and where the difference went. NetSuite supports standard, average and actual costing, and the choice shapes your close, your margin reporting and how much maintenance your team signs up for. It is one of the few decisions that is genuinely hard to change later.
Manufacturers who want to manage cost usually choose standard costing, because the variances are the management report. Distributors and light assemblers often prefer average.
A cost rollup walks the bill of materials and routing to build the standard cost of an assembly from its components, labor and overhead. When production differs from that plan, the difference shows up as a variance rather than quietly changing the item value.
Variances are only useful if someone reviews them by cause. A monthly variance meeting that ends in changed standards, fixed BOMs or a supplier conversation is the point of the method.
Annual standards with mid-year revisions are common. What matters is that the update is planned, the revaluation is understood by finance, and the person who owns it is named.
Overhead applied per unit, per labor hour or per machine hour will each tell you a different story about which products earn their keep. Pick the basis that reflects what actually drives your costs.
Separating material, labor, machine and overhead in the cost record is what makes variance analysis readable later. Collapsing everything into one number is fast today and unhelpful every month after.
An assembly has a standard cost of $42.00: $30.00 material, $8.00 labor, $4.00 overhead. A work order for 500 is built and the ledger shows a variance. Reading it back is a matter of knowing which variance is which.
Each of those points at a different person and a different fix. That separation is the whole argument for standard costing, and it is also why standards that were set once at go-live and never revisited make the variance report useless: everything shows a variance, so nothing does.
The costing method is chosen per item, so a business can mix them. The question is who maintains what.
A common pattern is standard costing on manufactured items and average on purchased ones. That gives production a variance to manage without asking purchasing to maintain a standard on every washer.
NetSuite costs what it is told about. It cannot separate labor you never recorded or scrap nobody entered, and the honesty of the numbers depends on what the floor captures. That is the gap FactorySync closes for time and status. The NetSuite manufacturing guide covers how costing sits inside the wider production flow.
Standard costing suits manufacturers who want variances as a management tool and can maintain standards. Average costing suits simpler assembly and distribution where the maintenance is not worth it. The right answer depends on whether anyone will act on variances.
A rollup calculates the standard cost of an assembly by walking its bill of materials and routing, adding material, labor and overhead from the levels below. It is rerun when standards or structures change.
It is possible but disruptive: item values, open jobs and reporting history are all affected. Treat it as a finance project with a period boundary, not a configuration change.
Annually as a baseline, with an interim revision when a material price or a labor rate has moved enough that the variance stops being informative. Some manufacturers revalue quarterly. The signal to revise is not the calendar, it is a variance report where the same items show the same variance every month, which means the standard is simply wrong rather than the process being out of control.
It is possible on an item, but it is not a routine change. Changing the costing method affects inventory valuation and the general ledger, it usually requires the item to be at zero on hand or to be handled through a new item record, and it needs accounting sign-off on how the transition is posted. It is far cheaper to decide correctly during implementation, which is one of the decisions covered in the implementation guide.
Setting this up, or fixing how it was set up? Get in touch and we will look at it with you. More on the whole production flow in the NetSuite manufacturing guide.
