Zero-Click Answer
Bills of material and routings matter to financial reporting because they help determine how an ERP calculates product costs, values inventory, records production consumption, and ultimately reports gross margin. A BOM tells the system what materials should be consumed to manufacture a product, while a routing helps define the operations, labor, machine time, and production resources required to make it. If either is inaccurate, the ERP can process production transactions correctly while calculating the wrong economic result. For ERP implementers, BOM and routing accuracy should therefore be viewed as more than an engineering or production requirement. These master-data records can directly influence inventory valuation, cost of goods sold, manufacturing variances, and reported margins.
What the ERP Is Being Asked to Do
Manufacturing ERP systems need a structured definition of how products are made.
Two of the most important elements are often the bill of material and the routing.
The bill of material generally defines the materials and components required to manufacture a product.
Depending on the manufacturer and ERP, it may include:
- Raw materials
- Components
- Subassemblies
- Packaging
- Quantities
- Units of measure
- Scrap factors
- Yield assumptions
- Alternative materials
The routing generally describes how the product moves through production.
It may identify:
- Production operations
- Work centers
- Labor requirements
- Machine requirements
- Setup time
- Run time
- Outside processing
- Production sequence
Together, these records can provide the ERP with the structure necessary to calculate the expected cost of manufacturing a product.
A simplified cost relationship may look like:
BOM → Material Cost
Routing → Labor + Machine + Applied Overhead
Together:
Material + Labor + Machine + Overhead = Product Cost
That product cost can then flow into inventory, cost of goods sold, manufacturing variances, and margin reporting.
The BOM and routing are therefore not isolated manufacturing records.
They can become inputs into financial reporting.
What May Be Happening Operationally
The difficulty is that the BOM and routing stored in the ERP do not automatically equal what actually happens on the manufacturing floor.
Manufacturing processes change.
Materials are substituted.
Equipment changes.
Automation is added.
Production methods improve.
Run speeds change.
Labor requirements change.
Scrap changes.
Packaging changes.
Engineering revises products.
But master data may not always change at the same speed.
Consider a BOM that specifies 10 pounds of material per finished unit.
Actual production consistently requires 10.8 pounds because of normal process loss.
If the ERP standard remains at 10 pounds, the system may repeatedly generate material usage variances.
The transaction processing can be technically correct.
The standard is simply describing a manufacturing process that no longer exists.
Routings can create similar problems.
Suppose a routing assumes 30 minutes of machine time per unit while actual production now requires 45 minutes.
If machine and overhead costs are applied through routing time, the product may systematically receive less cost than the resources actually required to manufacture it.
Conversely, an outdated routing can overstate resource consumption and make a product appear more expensive than it really is.
The underlying issue is:
Master Data ≠ Manufacturing Reality
Once that disconnect develops, the financial consequences can spread throughout the ERP.
Where the Implementation Risk Appears
BOM and routing weaknesses can create implementation risk in several areas.
Legacy Master Data Is Migrated Without Validation
The legacy ERP may contain thousands of BOMs and routings.
Moving those records into the new system may appear to be primarily a data-conversion task.
But migration does not establish that the data is accurate.
An old BOM migrated perfectly remains an old BOM.
An inaccurate routing mapped correctly remains an inaccurate routing.
Standard Costs Can Be Wrong
If standard costs are calculated from BOM and routing information, incorrect master data can create incorrect standards.
For example:
Incorrect Material Quantity → Incorrect Material Standard
Incorrect Labor Time → Incorrect Labor Standard
Incorrect Machine Time → Incorrect Applied Overhead
Those errors then combine at the finished-product level.
Inventory Valuation Can Be Affected
If manufactured inventory is valued using costs derived from these standards, master-data problems can extend into:
- WIP
- Finished goods
- Inventory valuation
- Cost of goods sold
The issue is no longer simply whether production planning has the correct recipe or process sequence.
It can become a financial-reporting issue.
Variances Can Become Misleading
Variances are useful only when the underlying standard represents a reasonable expectation.
If actual production repeatedly differs from an outdated BOM or routing, the ERP may generate persistent unfavorable or favorable variances.
Management may conclude that production is performing poorly when the real problem is an unrealistic standard.
Eventually, persistent variances may simply be ignored.
The ERP then produces information without producing insight.
Product Margins Can Be Distorted
Incorrect product costs eventually affect product-margin reporting.
Management may believe one product is highly profitable while another is weak.
But part of the difference may originate in BOM or routing accuracy rather than actual economics.
That can affect:
- Pricing
- Product mix
- Customer decisions
- Make-or-buy analysis
- Capacity decisions
A master-data issue can therefore become a management decision-making issue.
What Implementers Should Look For
Several warning signs suggest BOMs and routings deserve additional attention before they become new ERP master data.
1. BOMs and routings have not been systematically reviewed for years.
Long-lived master data may not reflect current production methods.
2. Production employees regularly work around the documented process.
If the shop floor routinely uses different quantities, materials, operations, or production sequences, the ERP may be modeling the wrong process.
3. Material or labor variances consistently move in the same direction.
Recurring variances may indicate an operating problem, but they can also indicate that the standard itself is wrong.
4. Engineering, production, and finance disagree about how a product is made.
Different versions of manufacturing reality create significant implementation risk.
5. Management does not trust product margins.
BOM and routing accuracy should be considered before assuming the ERP costing functionality itself is the problem.
Questions to Ask the Manufacturer
ERP implementers can identify master-data risk early without independently becoming responsible for engineering or costing decisions.
BOM Ownership
- Who owns BOM accuracy?
- Who is authorized to change a BOM?
- How are engineering changes communicated to production and finance?
- When were major BOMs last reviewed?
- Are obsolete BOM versions still being used?
Material Usage
- Do BOM quantities reflect expected production consumption?
- Are scrap and yield assumptions incorporated appropriately?
- Are material substitutions common?
- Are units of measure consistent between purchasing, inventory, production, and costing?
- Are packaging materials included where appropriate?
Routing Ownership
- Who owns routing accuracy?
- When were routing standards last reviewed?
- Do current operations match the routing sequence?
- Are setup and run times realistic?
- Have equipment or automation changes altered production requirements?
Costing
- Are standard costs calculated using BOMs and routings?
- Which BOM and routing fields affect costing?
- Are labor and machine rates tied to routing operations?
- Does overhead application depend on labor or machine time?
- Are recurring manufacturing variances linked to specific master-data assumptions?
Migration
- Which BOMs and routings will be migrated?
- How will inactive or obsolete records be handled?
- Who will approve the converted data?
- Will high-volume or high-value products receive additional validation?
- How will converted master data be tested against expected product costs?
Financial Validation
- How will product costs before and after conversion be compared?
- Which cost differences should be expected?
- Which differences require investigation?
- How will inventory valuation be validated?
- Who from finance will approve the financial impact of the converted master data?
One particularly useful question is:
“How do we know the BOM and routing we are migrating describe how this product is actually manufactured today?”
That question moves the discussion beyond data conversion and toward data integrity.
Cost Integrity™ Perspective
Cost Integrity™ treats manufacturing master data as part of the financial-information chain.
The connection can be viewed as:
Manufacturing Reality → BOM & Routing → Standard Cost → Production Transactions → Inventory → Cost of Goods Sold → Gross Margin
That sequence explains why engineering and production master data matter to finance.
A material quantity stored in a BOM may eventually affect inventory valuation.
A machine time stored in a routing may affect overhead applied to a product.
A scrap assumption may influence expected material consumption.
A production yield may affect unit cost.
The ERP connects these operational assumptions to financial outcomes.
This makes master-data governance important across functions.
Engineering may understand how the product is designed.
Production understands how it is actually manufactured.
Finance understands how those manufacturing assumptions affect cost and financial reporting.
The ERP implementer translates the approved structure into system configuration.
Reliable Cost Integrity™ requires those perspectives to align.
The desired sequence is:
Define → Validate → Approve → Configure → Test → Govern
not:
Extract → Migrate → Assume Correct
The difference is important because ERP implementation can make master data substantially more powerful.
That power works in both directions.
Accurate master data can produce reliable costing and financial information at scale.
Inaccurate master data can produce unreliable information at the same scale.
Bottom Line
Bills of material and routings are not simply production setup records.
In a manufacturing ERP, they can sit directly upstream from the financial statements.
The relationship is:
BOM & Routing → Product Cost → Inventory → COGS → Gross Margin
That means a BOM quantity, routing time, scrap assumption, or production standard can eventually affect reported financial performance.
ERP implementers should therefore avoid treating BOM and routing migration as purely a technical data-conversion exercise.
The more important question is:
“Does the master data being configured accurately represent the manufacturing operation whose economics the ERP will be asked to report?”
When the answer is yes, the ERP has a stronger foundation for reliable product costs, inventory valuation, variances, and margin reporting.
When the answer is no, the ERP may work exactly as designed while reporting a manufacturing reality that no longer exists.
FAQ
Are BOMs primarily an engineering responsibility?
Engineering may own important aspects of BOM design and maintenance, but BOM information can also affect production, inventory, costing, and financial reporting. Finance should understand the financial implications of the fields used in product costing.
Why do routing times matter to product cost?
Routing times can drive labor, machine, and overhead application. If setup or run times are materially inaccurate, the resulting product cost may not reflect the resources required to manufacture the product.
Should every BOM and routing be manually reviewed before ERP migration?
Not necessarily. The appropriate validation approach depends on the number of items, complexity, data quality, and implementation risk. Manufacturers may prioritize high-volume, high-value, high-margin, or otherwise financially significant products while using broader validation procedures across the remaining population.
Can accurate financial reporting exist with inaccurate BOMs and routings?
It becomes more difficult when the ERP relies on those records for costing and inventory valuation. Financial reconciliations and adjustments may compensate for some problems, but inaccurate master data can continue generating unreliable product costs, variances, and management information until the underlying records are corrected.