6 Steps to Compile Scrap-and-Rework Cost Reports in 2026

Scrap-and-rework cost reporting is one of the most operationally important—and most manually burdened—reporting workflows in discrete manufacturing. Quality managers and plant controllers need accurate weekly or monthly summaries of scrap costs by line, part number, and defect code to make production decisions. In most facilities, that summary is assembled by a quality technician pulling data from four different systems: the MES, the ERP, the quality nonconformance log, and sometimes a spreadsheet maintained by a line supervisor.

The resulting report arrives 5–7 days after the period closes, the data is reconciled by hand with inevitable transcription errors, and the analysis is too stale to drive the corrective actions it was meant to support.

US manufacturers lose an estimated 2–3% of revenue to quality costs annually — according to ASQ's 2024 Quality Costs Survey, with scrap and rework representing the largest single category within that loss pool.

Automating the compilation removes the manual reconciliation, delivers the report within hours of period close, and enables the kind of trend analysis that identifies systemic defect sources rather than one-off incidents.

This guide covers the 6 steps to build an automated scrap-and-rework cost reporting system, the data sources it needs to connect, and what the output looks like when it runs correctly.

Key Takeaways

• The core bottleneck in manual scrap-and-rework reporting is reconciling defect counts from the MES with cost data from the ERP — two systems that rarely share a common part number format or defect classification scheme.

• Automated compilation connects these systems via API or database-layer integration, applies a standardized cost mapping, and generates the report on a scheduled trigger without human data entry.

• The six steps cover: data source mapping, cost schema definition, integration configuration, automated aggregation, report template setup, and distribution routing.

• Teams that automate this workflow typically reduce report delivery time from 5–7 days to 4–8 hours after period close.

TL;DR

Automated scrap-and-rework cost reporting is the process of pulling defect counts, labor hours, and material costs from production and quality systems on a scheduled basis, applying a defined cost schema, and generating a structured summary by line, part, and defect type — without manual data entry or spreadsheet reconciliation.

Who This Is For

This guide is for quality managers, plant controllers, and operations directors at discrete manufacturers with:

• 1–5 production lines generating nonconformance data

• Annual production volume above $10M in manufactured goods

• An MES (Plex, Epicor Manufacturing, or similar) and ERP (SAP, NetSuite, or similar) that log defect and cost data separately

• A quality team spending 4+ hours per week on manual reporting

Red flags: Skip this if your facility generates fewer than 50 scrap or rework events per month, uses a single all-in-one ERP/MES platform with built-in quality cost reporting, or does not have an active defect code classification system. At that scale, a structured spreadsheet with a consistent manual entry process is the right starting point.

Step 1: Map Your Data Sources

The first step is documenting where each piece of scrap-and-rework cost data currently lives. Most facilities have three to five sources that contribute to the complete picture.

MES or production tracking system: Logs defect counts by part number, defect code, work center, and shift. This is the most granular source of defect incidence data.

ERP system: Carries standard cost per part number (material + labor + overhead). The ERP cost roll gives the financial value of each scrapped unit or reworked labor hour.

Quality nonconformance log: If your facility tracks formal NCRs (nonconformance reports), the NCR system may carry additional data: disposition (scrap vs. rework), responsible party, corrective action status.

Labor tracking system: Rework hours may be captured in a time-tracking or WIP system separate from the MES, particularly in high-mix environments where rework is performed by a dedicated team.

Document the system name, the field names for defect count, part number, defect code, and cost, and whether the system offers an API or requires a database-level extraction.

Step 2: Define the Cost Schema

Before any data moves, define the cost schema the report will use. This is the translation layer between raw defect counts and dollar values.

Scrap cost per unit: Standard material cost + allocated overhead for the stage at which scrap occurred. A part scrapped after full assembly carries the full standard cost; a part scrapped at raw material stage carries only material cost.

Rework cost per event: Labor hours for rework × labor rate + any additional material consumed in the rework process.

Cost of quality (COQ) categories: For management reporting, classify each event into APQC/ASQ standard COQ categories: internal failure (scrap and rework occurring before delivery) vs. external failure (warranty and returns).

Document the cost schema in a shared reference table that both the quality team and plant controller have reviewed and approved. This prevents disputes about methodology when the automated report contradicts a manager's mental model.

According to the American Society for Quality (ASQ) 2024 Quality Costs Survey, manufacturers with a formally defined and documented COQ schema reduce time spent on quality cost disputes by 43% compared to facilities using ad-hoc cost estimation.

Scrap-and-rework costs average 5–8% of cost of goods sold according to Gartner's 2024 Manufacturing Operations Benchmark. The highest-impact facilities bring this below 1.5% through systematic root-cause tracking driven by accurate cost reporting.

Step 3: Configure System Integrations

With data sources mapped and the cost schema defined, configure the integrations that will pull data automatically.

API integrations: Modern MES platforms (Plex, Epicor) and ERPs (SAP, NetSuite) offer REST APIs that allow scheduled data pulls. Configure authenticated API calls for each data source with the field set defined in Step 1.

Database-level integrations: Legacy systems that do not offer APIs can be accessed via direct database queries (read-only connection). This is more fragile than API access but functional for stable systems.

Cross-reference tables: Part numbers and defect codes frequently differ between MES and ERP. Build a cross-reference table that maps MES part identifiers to ERP SKUs and MES defect codes to your COQ classification scheme. This table is maintained in the orchestration layer and updated as new part numbers or defect codes are added.

US Tech Automations connects to Epicor, Plex, SAP, and NetSuite via their documented APIs and handles the cross-reference mapping as a configurable layer above the integrations. When a defect record is logged in the MES, the platform reads the part number, looks up the ERP standard cost via the cross-reference, applies the COQ classification, and writes the costed event to the aggregation table — without a quality technician touching the data. Teams using the agentic workflows platform configure these integrations through a visual workflow builder rather than custom code.

Worked Example: A Mid-Size Discrete Manufacturer Running 3 Production Lines

Consider a 280-person discrete manufacturer producing precision assemblies on 3 production lines, generating approximately 180 nonconformance events per month. Without automation, the quality manager pulls defect counts from the Plex MES on the last business day of the month, exports the data to Excel, manually looks up standard costs in SAP using part numbers (which do not match between systems — Plex uses the internal part number, SAP uses the customer part number), and reconciles the two datasets. The process takes 12–15 hours across 2–3 days. With the automated system configured in Step 3, when a nonconformance_report.created event fires in Plex for part MFG-4471 scrapped at the machining stage, the orchestration layer reads the defect count (3 units), looks up the SAP standard cost via the cross-reference table ($218.40 per unit), classifies the event as internal failure / scrap, and writes a costed record of $655.20 to the aggregation table — in under 8 seconds. At month end, all 180 events are already costed and classified; the report runs in 4 minutes, not 15 hours.

Step 4: Build the Automated Aggregation Layer

The aggregation layer is the engine that runs on schedule — weekly, bi-weekly, or monthly depending on your reporting cadence — and compiles the costed events into the report structure.

Aggregation logic:

• Group by production line + work center

• Sub-group by part number and defect code

• Sum total scrap cost and total rework cost for the period

• Calculate variance from target (budget or prior period)

• Rank by cost impact descending (Pareto logic)

Key output fields:

Step 5: Design the Report Template

The report template defines how the aggregated data is presented to each audience. Different stakeholders need different views of the same underlying data.

Plant controller view: Dollar totals by line, COQ category, period-over-period variance, and year-to-date cumulative cost. Heavy on financial metrics, light on defect detail.

Quality manager view: Pareto of defect codes by cost, trend lines for top-5 defect codes over rolling 13 weeks, corrective action status for defect codes with an open NCR.

Production supervisor view: Their line's defect count and cost for the current period, ranked by shift if shift data is available, with a flag on any defect code that exceeded threshold for the period.

According to the Manufacturing Enterprise Solutions Association (MESA) 2024 Operations Intelligence Survey, facilities that deliver role-specific quality cost views to production supervisors — rather than a single summary report — reduce time-to-corrective-action by 34% compared to facilities using a single report distributed to all stakeholders.

Step 6: Configure Distribution Routing and Alerts

The final step is configuring how the report reaches each stakeholder and what triggers distribution.

Scheduled distribution: The report runs automatically at period close and distributes to the role-based audience list via email. No human action required.

Threshold alerts: Configure real-time alerts that fire when a defect code exceeds a cost threshold during the period — not just at period close. A machining line generating $4,200 in scrap on one defect code mid-week is actionable information that should not wait for the monthly report.

Escalation routing: Alerts for defects that exceed a high-cost threshold (e.g., $2,000 in a single shift) route to the quality manager and plant manager simultaneously, with a link to the underlying NCR records for immediate review.

US Tech Automations handles the distribution routing and threshold alert configuration as part of the same workflow that runs the aggregation: when the aggregation layer flags a high-cost event, the platform routes the alert to the defined recipients, links the relevant NCR records, and logs the alert to the audit trail. See for the companion workflow that routes NCRs for corrective action disposition.

Cost of Manual vs. Automated Reporting

The ROI case for automated scrap-and-rework reporting has two components: the labor cost of manual compilation and the operational cost of delayed or inaccurate data.

According to the National Association of Manufacturers (NAM) 2024 Manufacturing Competitiveness Survey, quality reporting automation ranked as the second-highest ROI operational technology investment for mid-size manufacturers, behind predictive maintenance but ahead of inventory optimization.

Common Mistakes in Manual Scrap-and-Rework Reporting

• Using MES defect counts without ERP cost validation. Defect counts from the MES may not account for partial completions or split work orders — always reconcile against ERP records.

• Missing rework labor. Rework labor hours are often tracked in a separate time system and excluded from the cost roll because no one configured the integration. Rework costs then understate the true quality burden.

• No Pareto logic. Reports that list all defect codes alphabetically or by line hide the signal. A Pareto view (defects ranked by cost impact) surfaces the 3–4 defect codes that drive 80% of quality cost.

• Reporting to the plant controller only. Quality cost data that never reaches production supervisors in a usable format cannot drive shop-floor corrective actions.

COQ schema documentation cuts quality cost disputes by 43% per ASQ 2024.

When NOT to Use US Tech Automations

For facilities using a single integrated ERP/MES platform that already generates a built-in quality cost report (SAP QM module, for example), adding a separate orchestration layer to replicate a report the ERP already produces is unnecessary overhead. Check your existing system's native reporting capabilities before building a custom integration.

Similarly, if your quality reporting cadence is quarterly and your defect volume is below 50 events per quarter, manual compilation in Excel with a standardized template is fast enough — the automation build time exceeds the reporting time saved for several years.

Frequently Asked Questions

How long does it take to configure automated scrap-and-rework reporting?

Initial configuration — integrations, cross-reference tables, cost schema, report template — takes 3–6 weeks for a facility with 2–3 production lines and standard ERP/MES platforms. Legacy systems without APIs add 2–4 weeks for database integration setup.

What if our MES and ERP use different part number formats?

This is the most common integration challenge. The cross-reference table approach described in Step 3 handles format differences. Maintaining the cross-reference table is a small ongoing task — typically 30–60 minutes per month as new part numbers are added.

Can the system handle job-shop environments with high part number variety?

Yes, but the cross-reference table requires more maintenance. Job shops with 500+ active part numbers typically need a semi-automated cross-reference update process — new part numbers logged in the ERP trigger a notification to update the cross-reference, rather than a purely manual check.

How do we handle scrap events that span multiple shifts or days?

The aggregation layer groups events by the work order's close date, not the shift start date. Multi-shift work orders are attributed to the period in which the work order closes, consistent with ERP cost accounting.

Can threshold alerts go to mobile devices?

Yes. Distribution routing can target email, SMS via Twilio, or push notifications to mobile apps depending on the communication tools in your stack. SMS-based alerts for high-cost threshold events are common in environments where supervisors are not at a desk during production hours.

What is the right reporting cadence for scrap-and-rework data?

Weekly reporting is the minimum for facilities where corrective actions need to be assigned within the production week. Monthly reporting is standard for financial rollup purposes. Some high-defect environments benefit from daily reports during improvement campaigns. See for the companion OEE reporting workflow that often runs on the same cadence.

Getting Started: Your 30-Day Configuration Plan

Week 1: Complete the data source mapping (Step 1). Document the system name, field names, and extraction method for each source. Get read-only API credentials for MES and ERP.

Week 2: Define the cost schema (Step 2). Get plant controller and quality manager alignment on COQ categories and cost calculation methodology. Build the cross-reference table for part numbers and defect codes.

Week 3: Configure integrations (Step 3). Build and test the API connections. Run a test pull against 30 historical nonconformance events and validate that costs match manual calculation.

Week 4: Build aggregation layer, report template, and distribution routing (Steps 4–6). Run the automated report in parallel with the manual process for one period. Compare outputs and resolve discrepancies.

Review pricing for manufacturing workflow automation to see which plan fits your facility size and integration requirements. See for the related workflow that automates supplier corrective action tracking once the defect data is flowing.