The parallel quarter is the method, not a precaution
Comparing actual against standard across a full quarter is what makes the resulting repricing defensible internally.
Dynamics 365 Business Central · Manufacturing
From standard to actual: a costing transition
The parallel quarter is the whole method. Switching without one produces an accurate number nobody trusts.
Abstract
From standard to actual: a costing transition
Summary
Moving from standard to actual costing is technically straightforward and organizationally difficult, because the transition period is when finance has to trust two sets of numbers simultaneously.
This paper sets out why the parallel quarter is not optional, why the comparison should be made by product family rather than by part, and what repricing looks like when the variance turns out to be concentrated in your longest-standing accounts.
Key findings
Four things this paper argues
If you read nothing else, read these. The analysis that follows sets out the evidence for each.
Compare by product family, not by part
Part-level noise obscures the pattern. Family-level variance is where the commercial decisions are.
Costing method is set per item, which makes staged migration possible
Stable purchased components can remain on standard while manufactured items move. This is a legitimate mixed model.
The uncomfortable finding is usually concentrated in long-standing accounts
Customers served at a loss are rarely new ones. That conversation is what the project is actually for.
Analysis
The argument in full
Why the parallel quarter matters
The technical transition is a configuration exercise. The organizational transition is that finance has to accept a new set of numbers while still closing on the old ones, and that acceptance is earned rather than assumed.
Running both models across a full quarter produces a comparison against a period the business already understands, which is what allows the repricing conversation to happen on evidence rather than on assertion.
It also surfaces the operational problems — routings that describe an idealised process, work centre rates set when the equipment was installed — before they appear as unexplainable variance in a live costing model.
Doing the comparison well
Roll costs up by product family before looking at individual parts. Part-level variance is noisy and it obscures the pattern that matters commercially.
Compare a full quarter so seasonality and mix do not distort the picture. And separate the variance by type — material, capacity, subcontract — because a single combined variance account tells you that something moved and nothing about why.
Where a work centre covers genuinely different operations, split it before running the comparison. A blended rate across dissimilar work is the most common source of variance nobody can explain, and it will discredit the exercise.
- Costing method set per item category, staged rather than switched wholesale
- Work centre and machine centre rates reviewed against current payroll and overhead
- Variance accounts separated by material, capacity and subcontract
- Comparison rolled up by product family across a full quarter
- Work centres split where they cover dissimilar operations
The repricing conversation
The finding is usually that a handful of long-standing accounts are being served at a loss, and that is the conversation nobody looks forward to and the one that pays for the project.
Reprice in sequence rather than across the board: hardest variance first, starting with the customer relationships strong enough to survive a conversation. A blanket price increase applied because a costing exercise produced numbers is how a technically correct project damages a commercial position.
Keep the standard cost populated during the parallel period for reporting continuity, and switch only once finance is ready. There is no prize for switching quickly.
Framework
Something you can apply without us
Every paper in this series ends with a framework you can run internally. We would rather you used it and reached your own conclusion than took ours on trust.
Framework
The costing transition
Five stages. The middle one is the whole method.
1
Review
Routings, bills of material and work centre rates before anything is switched.
2
Stage
Costing method per item category, so migration happens by group rather than as an event.
3
Run parallel
A full quarter with both models accumulating. This is not optional.
4
Compare
By product family, with variance separated by material, capacity and subcontract.
5
Reprice
In sequence, hardest variance first, with the relationships that can carry the conversation.
Implications
What this means, depending on your seat
The same argument lands differently across an executive team. These are the three versions worth separating.
References
Where to check this for yourself
Microsoft's own documentation for the product behaviour described above. We would rather you verified the basis than accepted our summary of it.
01
Design Details: Inventory Costing
02
Design Details: Costing Methods
03
Design Details: Variance
04
Setup Best Practices: Costing Method
05
Design Details: Changing Costing Methods for Items
On these references: each entry names a Microsoft Learn article or documentation area by title, because deep links change while titles are stable. Searching the title on learn.microsoft.com will reach the current version. Where we have cited a figure or a product behaviour, it is Microsoft's statement rather than ours; where we have given a number of our own it is labelled as such in the text.
Recognise the situation?
Give us a real bill of material and routing for one product family and we will show you the cost roll-up in a demo environment using your own part numbers, before any commercial conversation.
Discuss this paper Run the related checklist We reply to every message within one business day.
Keep reading
Related papers
The cost of deferring an ERP decision.
Deferral is a decision with a running cost. This paper quantifies where that cost accumulates and offers a framework for deciding whether to defer again.
July 26, 2026 · 14 pages · 15 min readRead
Operational continuity as a security objective
Ask a manufacturing executive what a security incident would cost and the answer involves stolen designs. Ask what a week of stopped production would cost and the number is immediate and much larger.
April 26, 2026 · 14 pages · 15 min readRead
The edge-to-cloud architecture decision
Architectures that assume connectivity fail in exactly the places manufacturers need them most. This paper examines the design decision and the failure nobody plans for.
April 12, 2026 · 15 pages · 16 min readRead