When scrap codes never reach the variance report

Scrap that stays on the floor in conversation but vanishes in the cost ledger is one of the most common findings in our manufacturing cost-control audits. Operators know which cavities run hot. Finance sees a tidy usage variance and assumes the BOM is slightly off.

Start at the ticket, not the dashboard

Ask for a week of scrap tickets or digital scrap entries from a single cell. Trace each code into the cost application. Note every code that stops at inventory adjustment, quality hold, or a “non-financial” log. Those stops are where plant truth and cost controls diverge.

Check the master data owners

Scrap codes often proliferate after a quality initiative. If cost masters were never updated, analytics built on cost elements will understate loss. Record who can create a quality code without a cost-element mapping — that control gap belongs in the findings pack.

Recalculate a thin sample

Take three high-volume SKUs and recompute expected scrap pounds (or pieces) using the tickets you traced. Compare to what the variance report absorbed. The absolute ringgit may be modest; the pattern tells you whether month-end debates are about standards or about missing pathways.

If you want a structured pass across multiple cells, our manufacturing cost-control audit is built for that scope.