A bill of materials changed. Does the product cost still add up?

A revised product design can change purchasing, production, inventory cost, and the margin expected from an order. Before accepting the new cost, establish which version was used, where it applied, and when it became effective. Otherwise, a report can compare old finished goods with a new recipe and call the difference a production problem.

A bill of materials lists the components or ingredients needed for a product. Microsoft's documentation distinguishes engineering, planning, production, and costing uses, and notes that versions may depend on dates, quantities, sites, or product dimensions. A drawing approved by engineering is therefore only part of the costing evidence.

Keep the prior version available. Record the approved change, affected products, first production date, treatment of open orders, and any stock of old components. The finance reviewer needs to know whether the change replaces future production, affects an existing batch, or remains a simulation.

Compare the old and new calculation line by line. A supplier price increase changes the cost of the same input. An engineering revision can change how much input is needed. A new material can also alter processing time, yield, inspection, or packaging. Combining all of those effects into one percentage hides the reason for the change.

Check units before explaining a variance. An invoice priced per carton can be mapped to a recipe measured in individual components. A liquid ingredient may arrive by weight while production records volume. Keep the conversion, its source, and any loss allowance with the item record so the revised calculation remains reproducible.

Do not assume a more expensive component produces a more expensive finished item. It may reduce usage or processing time. Equally, a cheaper substitute may require more material or extra handling. The cost review should follow the revised production method rather than stopping at the purchase price.

The following hypothetical example compares one finished unit under two approved production versions. It holds the overhead amount constant to isolate the stated changes. The old version uses two units of material at $6 each; the new one uses 1.8 units at $7 each. Direct labor rises from $8 to $8.50.

Microsoft's BOM-calculation documentation identifies the costing version, BOM version, route, quantity, date, and site as calculation inputs. Record the equivalent inputs in your own worksheet or system. A correct formula can still produce the wrong answer when it uses another site's labor rate or a component price effective next quarter.

Test a changed component through every affected parent product. Some components feed several assemblies, and the change may not reach them all automatically. Check what happens when a cost record is missing: the calculation might use a fallback value, an older record, or no value. Review warnings instead of treating a completed calculation as proof that all inputs were present.

Also distinguish a proposed selling price from an approved commercial price. A cost-plus result is one input to a pricing decision. It does not show that customers will accept the price or that an existing contract permits a change.

A purchasing forecast, a simulation, and the active cost used in transactions should be identifiable as different records. Microsoft's costing-version guidance describes planned and standard costs and distinguishes pending records from active ones. Keep a comparable approval boundary even if your company maintains costs in a spreadsheet.

Have the product owner confirm the materials and process, purchasing confirm price and availability, and finance review the cost calculation and effective date. Record unresolved assumptions. If a quote depends on a supplier discount that has not been agreed, show the scenario without silently installing it as the current cost.

Review the consequences for open production, old inventory, and previously issued quotations before activation. The accounting treatment of a standard-cost change depends on the system and reporting policy. Ask the controller to confirm any revaluation or variance entries rather than assuming a new unit cost affects only future orders.

After the revised version enters production, compare actual usage, time, good output, and inspection results with its assumptions. An early difference may reflect startup work, an incorrect conversion, or a process that has not achieved the expected yield. Keep those explanations separate before making another permanent revision.

Retain the approved calculation, effective-date evidence, first-run comparison, and remaining actions together. A product-cost change is complete when purchasing, production, accounting, and commercial reporting use compatible versions, and someone can explain the difference from the previous cost without rebuilding the calculation.