BOM Changes and Standard Cost in D365: Timing Cost Recalculations Around Revision Cutovers
In my last article I walked through engineering changes and how to get a revision into BOMs and production orders cleanly. I ended on a promise: the costing side. Because every BOM change is also a cost change, and if engineering and finance do not coordinate their cutovers, the result is a month of variance analysis meetings where nobody can explain the numbers.
This article is about standard cost specifically. If your manufactured items run on moving average or FIFO, BOM changes flow into cost through actual consumption and you have a different (easier) life. Standard cost is where timing discipline matters.
HOW STANDARD COST GETS BUILT
A manufactured item's standard cost in D365 is not entered; it is calculated. The BOM calculation rolls up component costs from the item cost prices, labor from the route (run time and setup against cost categories), and overhead through the costing sheet's indirect cost nodes. The result lands in a costing version as a pending cost with an effective date, and it does nothing until someone activates it.
That separation between pending and active is the whole control mechanism. You can calculate as often as you like, review the calculation details level by level, and only the activation moves the number that values inventory and measures production.
Three configuration points worth checking on your costing version setup before any of this matters: the blocking flag (prevents accidental activation), the fallback principle (where the calculation finds component prices that have no pending cost themselves), and whether your costing version records cost by site, because multi-site manufacturers with different routes per site need site-specific standards.
A BOM CHANGE DOES NOT CHANGE COST (UNTIL YOU MAKE IT)
Here is the point people miss: activating a new BOM version changes what production consumes. It does not change the standard cost of the parent. The standard stays whatever was last activated, calculated from the old structure. From the moment the engineering cutover happens until the moment a new standard is activated, you are deliberately running with a standard that no longer matches the build.
That is not automatically a problem. It is a measurable, explainable state, as long as you know what it does to variances.
THE VARIANCE MECHANICS
When a production order on the new BOM finishes and you run end-of-order costing against the old standard, the difference between what the order actually consumed and what the standard says it should contain shows up as production variances. The useful ones to watch in this scenario:
• Substitution variance: the order consumed component B where the standard cost roll-up contains component A. This is the classic engineering-change signature; a spike here right after a cutover is expected and healthy.
• Quantity variance: the new structure uses more or less of a component than the standard assumed.
• Price variance: the component's actual cost differs from the standard component price; relevant when the change also introduced newly purchased parts whose standard was set from a quote rather than history.
A clean cutover plan states up front: we expect substitution and quantity variance of roughly X for the weeks between engineering cutover and cost activation, and the production accountant signs off on that expectation instead of discovering it.
THREE TIMING PATTERNS
In practice, the timing decision comes down to three workable patterns:
• Aligned cutover (the default recommendation): calculate the pending cost from the new BOM version ahead of time, set the activation date to the same date as the BOM effectivity, and activate both together. Inventory of the parent item revalues at activation (the revaluation posts automatically against the standard cost revaluation account), and variances stay quiet. This needs the new component prices to exist before cutover, which is exactly the kind of readiness check an engineering change order should carry.
• Engineering first, cost at period boundary: the revision goes live mid-period, but you hold the new standard until the period close and activate it on the first day of the new period. You accept a few weeks of substitution and quantity variances in exchange for a stable standard within the period, which keeps month-over-month comparisons honest. Most controllers I work with prefer this for minor changes.
• Cost first, never: activating a new standard calculated from a BOM version that is not yet effective. The parent revalues, but production keeps consuming the old structure, so you create the same variances with the opposite sign and confuse everyone. There is no scenario where this order of operations is right; I list it because it happens by accident when someone activates a costing version without checking BOM effectivity dates.
WIP AND IN-FLIGHT ORDERS, AGAIN
The previous article's rulebook has a costing twin. Production orders estimate against the standard active at estimation time. Orders that are open across the cost activation keep their original estimates; their variances at ending will measure against the standard that was active when the order completes its costing. The practical advice: do not leave production orders hanging in a started state across a standard cost activation if you can avoid it. End them or finish them first; the variance attribution gets noisy otherwise, and the noise lands in the same accounts your cutover plan promised would stay quiet.
Also remember the revaluation scope: activation revalues on-hand inventory of the item, not WIP picked into open orders. That asymmetry alone justifies the discipline of cutting over at a moment with minimal WIP, which for most plants means a period boundary or a planned maintenance window.
A SHORT CHECKLIST
• New component items have purchase prices or pending costs before the parent calculation runs.
• BOM calculation run on the new version, calculation details reviewed at every level (the explosion view catches missing route times and zero-cost components fast).
• Activation date agreed between engineering, production, and finance, and matching the BOM effectivity date or a period boundary.
• Variance expectations documented if the two cutovers deliberately diverge.
• Minimal WIP at activation; open orders dispositioned per the previous article's rulebook.
TAKEAWAYS
Standard cost and BOM structure are two cutovers, not one. Aligning them is cleanest; deliberately separating them is fine when the variance story is agreed in advance; activating cost ahead of the structure is always wrong. The pending/active mechanics of costing versions give you everything needed to prepare a cost change weeks ahead and land it on a chosen date, so the actual cutover becomes an activation click, not a fire drill.
Next time I will look at costing for subcontracted operations: where the vendor service price lives, and how it rolls into the parent standard.
In this series: previous article Engineering Changes and Revisions in D365 · next article Production Scheduling in D365
In my last article I walked through engineering changes and how to get a revision into BOMs and production orders cleanly. I ended on a promise: the costing side. Because every BOM change is also a cost change, and if engineering and finance do not coordinate their cutovers, the result is a month of variance analysis meetings where nobody can explain the numbers.
This article is about standard cost specifically. If your manufactured items run on moving average or FIFO, BOM changes flow into cost through actual consumption and you have a different (easier) life. Standard cost is where timing discipline matters.
HOW STANDARD COST GETS BUILT
A manufactured item's standard cost in D365 is not entered; it is calculated. The BOM calculation rolls up component costs from the item cost prices, labor from the route (run time and setup against cost categories), and overhead through the costing sheet's indirect cost nodes. The result lands in a costing version as a pending cost with an effective date, and it does nothing until someone activates it.
That separation between pending and active is the whole control mechanism. You can calculate as often as you like, review the calculation details level by level, and only the activation moves the number that values inventory and measures production.
Three configuration points worth checking on your costing version setup before any of this matters: the blocking flag (prevents accidental activation), the fallback principle (where the calculation finds component prices that have no pending cost themselves), and whether your costing version records cost by site, because multi-site manufacturers with different routes per site need site-specific standards.
A BOM CHANGE DOES NOT CHANGE COST (UNTIL YOU MAKE IT)
Here is the point people miss: activating a new BOM version changes what production consumes. It does not change the standard cost of the parent. The standard stays whatever was last activated, calculated from the old structure. From the moment the engineering cutover happens until the moment a new standard is activated, you are deliberately running with a standard that no longer matches the build.
That is not automatically a problem. It is a measurable, explainable state, as long as you know what it does to variances.
THE VARIANCE MECHANICS
When a production order on the new BOM finishes and you run end-of-order costing against the old standard, the difference between what the order actually consumed and what the standard says it should contain shows up as production variances. The useful ones to watch in this scenario:
• Substitution variance: the order consumed component B where the standard cost roll-up contains component A. This is the classic engineering-change signature; a spike here right after a cutover is expected and healthy.
• Quantity variance: the new structure uses more or less of a component than the standard assumed.
• Price variance: the component's actual cost differs from the standard component price; relevant when the change also introduced newly purchased parts whose standard was set from a quote rather than history.
A clean cutover plan states up front: we expect substitution and quantity variance of roughly X for the weeks between engineering cutover and cost activation, and the production accountant signs off on that expectation instead of discovering it.
THREE TIMING PATTERNS
In practice, the timing decision comes down to three workable patterns:
• Aligned cutover (the default recommendation): calculate the pending cost from the new BOM version ahead of time, set the activation date to the same date as the BOM effectivity, and activate both together. Inventory of the parent item revalues at activation (the revaluation posts automatically against the standard cost revaluation account), and variances stay quiet. This needs the new component prices to exist before cutover, which is exactly the kind of readiness check an engineering change order should carry.
• Engineering first, cost at period boundary: the revision goes live mid-period, but you hold the new standard until the period close and activate it on the first day of the new period. You accept a few weeks of substitution and quantity variances in exchange for a stable standard within the period, which keeps month-over-month comparisons honest. Most controllers I work with prefer this for minor changes.
• Cost first, never: activating a new standard calculated from a BOM version that is not yet effective. The parent revalues, but production keeps consuming the old structure, so you create the same variances with the opposite sign and confuse everyone. There is no scenario where this order of operations is right; I list it because it happens by accident when someone activates a costing version without checking BOM effectivity dates.
WIP AND IN-FLIGHT ORDERS, AGAIN
The previous article's rulebook has a costing twin. Production orders estimate against the standard active at estimation time. Orders that are open across the cost activation keep their original estimates; their variances at ending will measure against the standard that was active when the order completes its costing. The practical advice: do not leave production orders hanging in a started state across a standard cost activation if you can avoid it. End them or finish them first; the variance attribution gets noisy otherwise, and the noise lands in the same accounts your cutover plan promised would stay quiet.
Also remember the revaluation scope: activation revalues on-hand inventory of the item, not WIP picked into open orders. That asymmetry alone justifies the discipline of cutting over at a moment with minimal WIP, which for most plants means a period boundary or a planned maintenance window.
A SHORT CHECKLIST
• New component items have purchase prices or pending costs before the parent calculation runs.
• BOM calculation run on the new version, calculation details reviewed at every level (the explosion view catches missing route times and zero-cost components fast).
• Activation date agreed between engineering, production, and finance, and matching the BOM effectivity date or a period boundary.
• Variance expectations documented if the two cutovers deliberately diverge.
• Minimal WIP at activation; open orders dispositioned per the previous article's rulebook.
TAKEAWAYS
Standard cost and BOM structure are two cutovers, not one. Aligning them is cleanest; deliberately separating them is fine when the variance story is agreed in advance; activating cost ahead of the structure is always wrong. The pending/active mechanics of costing versions give you everything needed to prepare a cost change weeks ahead and land it on a chosen date, so the actual cutover becomes an activation click, not a fire drill.
Next time I will look at costing for subcontracted operations: where the vendor service price lives, and how it rolls into the parent standard.
In this series: previous article Engineering Changes and Revisions in D365 · next article Production Scheduling in D365
No replies yet. Be the first to respond!