Scrap in Dynamics Finance & Operations: What It Means, Where to Set It, and How the Math Works
Scrap is one of those areas in Dynamics 365 Finance & Operations (D365FO) where the setup looks deceptively straightforward but the business impact can be far-reaching. A percentage entered in the wrong place can affect material planning, production estimates, standard cost, WIP, and the financial visibility of production losses.
Before opening any form in D365FO, the organization needs to agree on what it means by scrap: Is it expected material loss? Yield loss at a specific production step? An actual quality failure on a production order? Or recoverable material that should be returned to inventory? While D365FO supports all these scenarios, they should not be handled through the same configuration.
Planned Scrap vs. Actual Scrap
Planned scrap is the loss an organization anticipates as a normal part of producing an item, such as trim from a cutting operation, evaporation in batch manufacturing, or a fixed residual left in a machine after each production run.
Actual scrap is the loss that occurred on a specific order. It represents the gap between what was planned and what actually happened.
This distinction has real consequences. Planned scrap affects requirements planning and cost calculation. Actual scrap affects the production order, order costing, and how the organization sees the financial impact of that loss.
Scenario | Recommended D365FO Setup |
Predictable component loss | BOM or formula-line scrap |
Yield loss occurring during an operation | Route-operation scrap |
Bad or rejected finished quantity on a production order | Error quantity |
Material with recoverable value | Separate process for reuse, return, recycling, by-products, or co-products |
BOM and Formula Scrap
BOM and formula scrap apply when the expected loss is tied to a specific component. If every production run consumes resin that remains in lines and cannot be recovered, the scrap belongs on the resin BOM line. If a process consistently produces a percentage of unusable film, that expected loss can be modeled on the relevant BOM line.
D365FO provides two ways to define this type of scrap:
- Constant scrap is a fixed quantity consumed each production run, regardless of the quantity being produced.
- Variable scrap is a percentage of the material requirement that scales with production quantity.
The system uses the following calculation to determine how much raw material must be purchased:
Purchased material = (Required raw material Ć [1 + Variable scrap %]) + Constant scrap
Example
Assume a production order requires 100 pounds of raw material:
- Required raw material: 100 pounds
- Variable scrap: 10%
Constant scrap: 5 pounds
(100 Ć 1.10) + 5 = 115 pounds
D365FO plans for 115 pounds. The 10 pounds represents proportional material loss; the 5 pounds represents a fixed loss associated with the production run itself.
One point worth noting: Constant scrap does not scale with order quantity. On a small batch, that fixed loss can be significant on a per-unit basis. On a large batch, it is spread across more finished goods. Although this may be exactly what the business needs, it should be a deliberate choice, not an accidental one.
Route Scrap and Yield Loss
Route scrap is distinct from BOM scrap. Rather than representing loss tied to a specific component, it represents loss associated with a route operation.
A machining operation may have a predictable reject rate. A curing operation may produce yield loss. A cutting operation may generate trim. These are appropriate candidates for route scrap.
In D365FO, route scrap is configured in Production control > All routes > Route details. The Scrap percentage field represents the percentage of input consumed as scrap during that operation. The system also calculates an Accumulated scrap percentage, which accounts for all subsequent operations in the route.
D365FO works backward from the quantity of finished goods required. If the business needs 100 good units at the end of production and expects yield loss at multiple steps, the system determines how many units must enter the process to produce those 100 finished units.
Example: Multiple Route Operations
Assume a product moves through three operations, each with 10% scrap:
Required start quantity = 100 Ć· (0.90 Ć 0.90 Ć 0.90) = 137.17
The business must start with approximately 137 units to produce 100 good finished units after three consecutive operations. D365FO’s accumulated route-scrap calculation accounts for this compounding effect.
This is where many implementation teams underestimate scrap. Three operations at 10% each do not produce 30% total loss. The loss compounds as the product moves through the route.
The BOM Operation Number Matters
A BOM component can be linked to the specific route operation where it is first consumed, using the Oper. No. field on the BOM or formula line.
If this field is left blank, D365FO assumes the component is consumed from the first route operation. If the component is introduced later in the route, the operation number must be populated accordingly.
For instance, a label applied at final packaging should not be planned as though it must survive all earlier scrap-producing operations. A component consumed at operation 30 should only be subject to yield loss from operation 30 forward. This is a small configuration detail with a significant planning consequence.
Combining BOM Scrap and Route Scrap
D365FO can apply both BOM or formula scrap and route scrap simultaneously. This is appropriate when the business has both a yield loss caused by an operation and a predictable material-specific loss.
In this case, D365FO first calculates the required production start quantity based on route scrap, then applies BOM or formula scrap to determine material requirements. The documented calculation is:
Purchased material = Route-calculated start quantity Ć (1 + Variable scrap) Ć Batch size + Constant scrap
Exercise caution here. If the same physical loss is modeled as both route scrap and BOM-line scrap, the organization will overstate its material requirements and likely its standard cost as well.
A useful design question to ask: Does this loss happen because of the material itself, or because of the operation?
- If the answer is the material, configure BOM or formula-line scrap.
- If the answer is the operation, configure route scrap.
- If the answer is both, document the distinction clearly before enabling both.
Actual Scrap and Error Quantity
Planned scrap tells D365FO what the organization expects and tells error quantity records what actually happened.
When users report finished goods on a production order, D365FO supports the recording of error quantities ā product that was produced but cannot be treated as acceptable finished output. At production-order ending, the system resolves the actual cost impact of those reported error quantities.
The organization then needs to decide how that cost is handled. D365FO offers two primary approaches, configured through the Scrap method in production control parameters:
- Allocation distributes the cost of error quantities across the good finished output.
- Scrap account posts the error-quantity value to a designated general ledger account.
Allocation vs. Scrap Account
With Allocation, the cost of failed quantities becomes part of the cost of acceptable finished goods. If 90 good units are produced instead of 100, those 90 units carry a proportionally larger share of total production cost.
With a Scrap account, the cost of failed quantities is separated from finished-goods cost and posted to a dedicated ledger account, giving Finance and Operations greater visibility into abnormal loss.
Neither option is automatically correct. Allocation may be appropriate when loss is viewed as a normal and unavoidable cost of production. A scrap account is more appropriate when the organization wants to measure avoidable waste, quality failures, or process-performance issues as a distinct line item.
This decision should be made jointly by Manufacturing, Cost Accounting, and Finance, not resolved through configuration defaults alone.
What to Validate Before Go-Live
Scrap configuration should be tested not only against a single-unit BOM calculation but also against real manufacturing scenarios. Before moving any design into production, validate the following:
- Confirm whether each loss is expected or actual
- Confirm whether the loss belongs to a component, a route operation, or an actual production-order exception
- Validate the BOM or formula operation number for every component introduced after the first operation
- Test variable and constant scrap at multiple order quantities
- Test route scrap across the full production route, including accumulated yield loss
- Review planned material demand and planned order quantities after running master planning
- Review the impact on standard cost and cost rollups
- Confirm whether actual error quantities should be absorbed into good output or posted to a scrap account
- Test accounting entries, WIP behavior, financial dimensions, and production-order ending
Closing Perspective
Scrap is not simply a manufacturing statistic. In D365FO, it is a planning, costing, inventory, and financial design decision.
When configured correctly, scrap helps the business plan enough material, set realistic production expectations, understand true product cost, and separate normal process loss from operational performance issues. When configured incorrectly, it can quietly inflate demand, distort cost, and undermine the reliability of operational reporting.
The goal is not to make scrap disappear in the system but to make the system accurately reflect what happens on the shop floor.
