5.1 Costing Versions, Costing Sheets, and Standard Costing
Key Takeaways
- Costing versions hold cost records for purchased items, manufactured goods, and routing operations, partitioned by Costing type into Standard cost or Planned cost.
- Costing version parameters (Block changes, Block activation, Allow calculation, and Allow activation) strictly regulate whether pending costs can be modeled, updated, calculated, or activated.
- The Costing sheet defines the calculation architecture for Cost of Goods Manufactured (COGM) through a hierarchical tree of price components, cost groups, and indirect cost nodes (surcharges and rates).
- Single-level BOM calculations evaluate immediate parent components using existing active standard costs, whereas multi-level calculations explode and revalue all subassembly tiers simultaneously.
- Activating a standard cost updates active price records, automatically triggers an inventory revaluation for existing on-hand stock, and establishes standard benchmarks for variance accounting.
5.1 Costing Versions, Costing Sheets, and Standard Costing
Quick Answer: In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), standard costing is maintained through Costing versions and structured via the Costing sheet. Costing versions are partitioned into Standard cost (official inventory valuation, revaluations, and ledger variance posting) and Planned cost (simulations, forecasting, and WIP estimation). The Costing sheet establishes a calculation hierarchy of Price components, Cost groups, and Indirect cost calculation nodes (surcharges and rates). Activating a standard cost updates active prices, revalues on-hand stock, and posts purchase price and production variances to the general ledger.
1. Costing Version Types: Standard Cost vs. Planned Cost
A Costing version is a dataset container holding cost records for purchased items, manufactured assemblies, route cost categories (labor/machine rates), and overhead formulas.
Navigation Paths
Cost management > Predetermined cost policy setup > Costing versionsInventory management > Setup > Costing > Costing versions
The Costing type determines the operational and financial behavior of the version:
| Parameter / Feature | Standard Cost Version | Planned Cost Version |
|---|---|---|
| Primary Purpose | Official inventory valuation, COGS, and statutory balance sheet reporting. | Cost simulations, annual budgeting, "what-if" analyses, and base price updates. |
| Item Model Group Link | Mandatory for items using an Item Model Group where Inventory model is Standard cost. | Supports all inventory models (FIFO, LIFO, Weighted Average, Standard Cost). |
| Inventory Revaluation | Yes: Activation revalues on-hand inventory and posts financial adjustments to the ledger. | No: Activation never updates inventory valuation or posts ledger transactions. |
| Record Constraints | Only one active record per item, per site, per effective date. | Multiple planned cost records can exist concurrently across simulation versions. |
| Fallback Principle | Requires strict fallback principles (None or Active) to guarantee ledger integrity. | Supports flexible fallback principles (Current active, Costing version, None). |
2. Costing Version Parameters and Operational Controls
D365 SCM enforces operational discipline through four primary governance parameters on the Costing version header:
- Block changes: Freezes the costing version. When set to
Yes, users cannot enter pending prices, import costs, or run BOM cost roll-up calculations. - Block activation: Prevents pending cost records from being activated into active standard costs. Allows reviewing roll-up results without risking premature ledger posting.
- Allow calculation: Dictates whether BOM and formula calculations can run against this version. Can restrict calculations to pending costs or disable calculations entirely.
- Allow activation: Master toggle that permits or denies activation. If set to
No, the Activate action remains disabled across all price records.
Recording Restrictions FastTab
Organizations enforce governance using Recording restrictions:
- Site: Locks the version to a single operating site, preventing cross-site cost contamination.
- From date: Enforces a strict validity start date for all pending prices created in the version.
- Restriction by price type: Restricts lines to
Cost(inventory valuation),Purchase price, orSales price.
3. Costing Sheet Architecture and Node Types
The Costing sheet structures the Cost of Goods Manufactured (COGM) and Cost of Goods Sold (COGS).
Navigation Path
Cost management > Predetermined cost policy setup > Costing sheets
Hierarchy Structure
- Root Node and Price Components: The root node (e.g.,
Total Cost of Manufacturing) consolidates intermediate price components (e.g.,Materials,Labor,Overhead) used for analytical reporting. - Cost Groups: Master data elements assigned to released products (
Manage costsFastTab) and route cost categories (Cost categoriessetup). Types include:- Direct materials: Assigned to purchased components, raw materials, and subassemblies.
- Direct manufacturing: Assigned to routing operations (labor run time, setup, machine hours).
- Indirect: Assigned to indirect calculation nodes for overhead absorption.
- Undefined: General auxiliary classification.
- Indirect Cost Calculation Nodes:
| Indirect Node Type | Calculation Basis | Formula | Practical Example |
|---|---|---|---|
| Surcharge | Percentage markup applied over designated cost groups. | $\text{Direct Cost Basis} \times \left(\frac{\text{Surcharge %}}{100}\right)$ | 12% material handling fee on Direct Materials. |
| Rate | Fixed currency amount per unit of time or physical measure. | $\text{Routing Hours / Item Qty} \times \text{Rate Amount}$ | $18.50 per machine run hour on cutting operations. |
[!IMPORTANT] Every indirect node requires a configured Calculation basis. For a surcharge, you must select the cost groups included in the base; an empty basis calculates zero overhead.
4. Standard Cost Roll-Up Calculations: Single-Level vs. Multi-Level
Executing a BOM calculation (Released products > Manage costs tab > BOM calculation) explodes the product structure using the selected Explosion mode:
- Single-level: Explodes only the top-level parent BOM. Manufactured subassemblies use their current active standard costs directly from the database without re-exploding their child BOMs. Used when subassemblies have frozen, approved costs.
- Multi-level: Recursively explodes all subassembly tiers down to raw materials, recalculating all intermediate subassembly costs simultaneously. Used during annual cost roll-outs.
- Make-to-order: Explodes only subassemblies marked with the
Pegged supplyBOM line type. - According to BOM line type: Respects individual line behaviors (exploding Phantoms directly while treating Item lines as single-level).
Calculation groups (Cost management > Predetermined cost policy setup > Calculation groups) define item-level rules, including Stop explosion (treats a subassembly as purchased) and Fallback principle (searches alternate costing versions if a price is missing).
5. Activating Standard Costs and Variance Accounting
Activating a pending standard cost commits it to InventItemPrice as the active cost.
Inventory Revaluation on Activation
When standard costs are activated and physical on-hand inventory exists at that site, D365 SCM automatically posts an Inventory revaluation:
The transaction debits or credits Inventory receipt and offsets to Inventory revaluation profit/loss accounts in the Inventory posting profile.
Standard Cost Variance Types
Operational variances post to distinct general ledger accounts during daily transactions:
| Variance Type | Operational Trigger | Calculation Formula |
|---|---|---|
| Purchase Price Variance (PPV) | Invoiced PO price differs from active standard cost. | $(\text{Invoice Price} - \text{Standard Cost}) \times \text{Invoiced Qty}$ |
| Material Usage Variance | Actual raw materials picked differ from estimated BOM quantity. | $(\text{Actual Qty} - \text{Standard BOM Qty}) \times \text{Standard Cost}$ |
| Labor Efficiency Variance | Actual route hours reported differ from standard operation time. | $(\text{Actual Hours} - \text{Standard Hours}) \times \text{Standard Rate}$ |
| Labor Rate Variance | Actual labor rate charged differs from standard category rate. | $(\text{Actual Rate} - \text{Standard Rate}) \times \text{Actual Hours}$ |
| Lot Size Variance | Fixed setup costs amortized over actual batch size differing from standard lot size. | $\text{Fixed Setup Cost} \times \left( \frac{1}{\text{Actual Batch}} - \frac{1}{\text{Standard Lot}} \right)$ |
Exam Tips and Common Traps
[!TIP] Exam Tip — Planned vs. Standard Costing: For budget modeling, testing commodity price increases, or updating base sales prices without altering balance sheet inventory valuations, select Planned cost.
[!IMPORTANT] Exam Tip — Surcharge Input Basis: If a costing sheet surcharge does not calculate overhead on production orders, verify that the direct material cost groups are assigned to its Calculation basis.
[!WARNING] Exam Trap — Block Activation vs. Block Changes: Setting Block changes prevents price edits or calculations but allows activating existing pending costs. To halt price activations, enable Block activation.
A manufacturing enterprise needs to execute cost calculations for the upcoming fiscal year to simulate the financial impact of a projected 8% price increase across raw material commodities and a 5% increase in production machine operation rates. The calculations must NOT alter the current inventory valuation of on-hand inventory, must NOT trigger general ledger revaluations, and must allow multiple simulation iterations with different BOM explosion versions. Which costing version configuration should the functional consultant implement?
A cost accountant is designing a Costing sheet in Dynamics 365 Supply Chain Management. The finance director requires that all manufactured items absorb a 12% material handling overhead charge calculated exclusively on the direct material cost of raw materials and purchased components. Machine and labor operations must be excluded from this overhead calculation. How should the costing sheet hierarchy and calculation nodes be configured?
A discrete manufacturer produces an industrial generator consisting of three manufactured subassemblies: an engine assembly, an alternator assembly, and a control console assembly. Active standard costs were calculated and activated for all three subassemblies last month. The engineering team has updated the component quantities on the control console BOM, but the engine and alternator subassemblies remain unchanged. The cost accountant needs to recalculate the standard cost of the finished generator while honoring the existing active standard costs of the engine and alternator assemblies without re-exploding their underlying multi-level BOMs. Which calculation explosion mode should the accountant select during the BOM calculation?