Scrap and Write-Down Disposal: One Approval for Inventory and Accounting

It is quarter-end. On the production floor in Aichi, an inspection team has set aside a pallet of parts that failed a final tolerance check. In the warehouse in the same building, three shelves hold components that have not moved in fourteen months, the customer who ordered them cancelled long ago. Someone has to decide that these items are gone. In most factories, that decision happens in pieces. A supervisor signs a scrap sheet. The warehouse quietly removes the stock from its own spreadsheet. Weeks later, accounting learns the parts were destroyed and posts a write-down to clear the variance. By then nobody can say exactly who approved what, on which date, or why the number on the warehouse sheet does not match the number in the ledger.

This is the quiet, expensive failure at the center of disposal. Inventory moves in one system. Accounting moves in another. And the approval that should govern both is either missing entirely or scattered across paper, email, and a stamped form nobody can find at audit time. A modern ERP closes that gap. A core business system makes disposal a single governed approval, with a frozen snapshot of what was scrapped, by whom, and why, so the inventory removal and the accounting write-down cannot drift apart again.

Why Ungoverned Disposal Becomes an Audit Risk

Disposal looks like a back-office chore because it ends in things being thrown away. That is precisely why it is dangerous. When defective stock and dead inventory leave the building without a governed approval, three problems stack on top of each other.

The first is inventory drift. The warehouse removes the parts, but if the accounting books still hold them at cost, the balance sheet shows inventory that no longer exists. The variance only surfaces at the next physical count, which is often months away. By then the explanation is gone, and the finance team writes the difference off against earnings with a shrug.

The second is the loss of segregation of duties. In a well-run internal-control environment, the person who authorizes disposal should not be the person who physically removes the stock, and neither should be the person who books the write-down. On paper and in spreadsheets, those three roles quietly collapse into one supervisor with a stamp. From a J-SOX and internal-control standpoint, that is exactly the kind of unsupervised asset removal an auditor will flag, because it is also the classic shape of inventory fraud.

The third is the missing evidence. When the disposal was approved on a paper scrap sheet that got recycled, there is no defensible record of the decision. An auditor asks who approved a 6-million-yen write-down, and the answer is a blank stare. The loss may be legitimate, but without the approval trail it cannot be proven, and the burden falls back on the company.

The root cause is always the same. Inventory and accounting were never tied to one approval, so they were free to move on their own schedules. A core business system fixes this by making the approval the single hinge that governs both.

One Approval That Governs Both Sides

The right way to handle disposal is to stop treating it as two separate events. A defective lot is not an inventory problem that later becomes an accounting problem. It is one business decision, made once, with consequences for both sides.

In an ERP, that decision is captured as a single disposal request. The request names what is being disposed, the lot or item, the quantity, the reason (defect, obsolescence, damage, or dead stock), and the carrying value that will come off the books. It routes through an approval workflow that reflects the company's authority rules. A small write-down below a threshold might need only a department head. A larger one might require a committee, or an executive, with the routing handled automatically by the amount. This is the same approval engine that runs purchase orders, expense claims, and ringi (internal approval proposals) across the company, so the disposal sits inside the same governed surface as every other decision.

What makes this work is the frozen snapshot. The moment the disposal is approved, the system records an unchangeable view of exactly what was approved: the items, the quantities, the values, the reason, the approver, the date, and the time. This is not a living document someone can edit later. It is the evidence. If the warehouse later says it scrapped 1,200 units and the books show 1,180, the snapshot is the source of truth that resolves the gap in seconds rather than weeks.

Because the approval and the snapshot live in the same system as the inventory records and the ledger, the two sides can never silently diverge. The inventory side has a governed instruction to remove the stock. The accounting side has a governed instruction to book the write-down. Both trace back to the same approved decision, signed by the same named approver, on the same timestamp.

What Is Built Today, and What Is Honest Roadmap

Here is the part where precision matters more than selling. The approval workflow and the frozen audit trail for disposal are built and live today. A company can file a disposal request, route it through the correct authority based on amount, and capture a tamper-resistant snapshot of exactly what was approved, by whom, and why. That control surface is real and in production.

What is on the roadmap, and not yet built, is the automatic writeback that adjusts the inventory records and posts the journal entry the moment approval completes. Today, when a disposal is approved, the system gives you the governed decision and the complete evidence, and the inventory removal and the accounting entry then follow through the normal, governed flows in the system. They are not yet automatically written back by the approval event itself. This is the same honest boundary that applies to journal entries, purchase orders, and lot adjustments in the current workflow writeback layer, where only expense reimbursement and leave applications post automatically on approval today.

Saying this plainly matters because the worst thing a disposal process can do is promise an audit trail it cannot actually deliver. The approval control is live and defensible right now. The fully automatic one-click writeback of inventory and journal is coming. A company that needs governed disposal today does not have to wait, because the governed approval and the frozen evidence are the parts that satisfy an internal-control review. The automation is the convenience layer on top.

A Scenario: The Precision Parts Maker in Aichi

Picture a precision parts manufacturer in Aichi, about 280 staff, supplying automotive OEMs and industrial machinery makers. They run a busy production floor and a warehouse that holds both raw material and finished components. Disposal happens regularly. Defective lots come off the line. Slow-moving components age past their useful holding period. Occasionally a full pallet is damaged in handling.

Before they adopted a governed disposal flow, the pattern was familiar and risky. A line supervisor would sign a paper scrap sheet for a defective lot. The warehouse would pull the stock and note it in a local spreadsheet. Accounting would not hear about it until the month-end count, when a 6-million-yen variance would appear and someone would spend two days reconstructing what had been scrapped and why. The approval evidence was usually gone. At their last internal-control review, the auditor pointed at three large write-downs with no named approver and no date, and asked a question nobody could answer.

In the new flow, the same defective lot enters a single disposal request inside the ERP. The request carries the lot, the quantity, the reason, and the carrying value. Because the value crosses a threshold, the routing automatically pulls in the department head and, for larger amounts, an executive. Watchers from quality and finance follow the request without being approvers, so the right people see the decision without being a bottleneck. When the last approval lands, the system freezes a snapshot of the entire decision. The warehouse now has a governed instruction to remove the stock. Accounting has a governed instruction to book the write-down. Both point to the same approved record, with the same approver name and timestamp.

At the next internal-control review, the same auditor asks the same question about a 6-million-yen write-down. This time the answer is one click away: the disposal request, the approver, the date, the reason, and the frozen snapshot, all in one place. The variance that used to take two days to explain now takes two minutes, because the approval trail was built into the disposal from the start, not retrofitted at count time.

The Internal-Control Angle: Why This Is a J-SOX Concern

Disposal governance is not a niche manufacturing concern. It is a textbook internal-control topic, and in Japan it falls squarely inside the J-SOX framework that governs internal control over financial reporting for listed and many mid-size companies. The reason is simple. Writing down inventory reduces earnings. If that reduction is not governed, it can be used to hide problems, smooth results, or, in the worst case, conceal theft of physical assets.

Two control principles are at stake. The first is authorization: material write-downs must be approved by someone with the right authority, and that authority must be documented and consistent. The second is the audit trail: every disposal must leave a record that ties the decision to a named approver, a date, a reason, and an amount, so an independent reviewer can confirm the loss was legitimate. An ERP delivers both by construction. A core business system enforces authorization by amount and role, and the frozen snapshot delivers the audit trail without anyone having to remember to file the paper.

For a manufacturer specifically, scrap and obsolescence are also a recurring operational signal. A lot of defective parts scrapped every week points at a process problem. A shelf of components that ages into a write-down points at a purchasing or forecasting problem. When disposal is governed and recorded, those signals become visible instead of buried in a month-end variance nobody wants to investigate.

Why a Single Approval Beats Two Separate Systems

Some companies try to solve disposal with two tools: an inventory system that handles the stock side and a separate accounting system that handles the write-down side. This looks reasonable on paper and fails in practice. The two systems keep their own schedules. The inventory side removes the stock this week. The accounting side books the entry next month. The approval that should tie them together lives in neither, usually on a stamped form that travels by desk. The result is the exact drift the company was trying to prevent.

An ERP wins by removing the seam. There is no inventory system and accounting system to reconcile, because both sides are governed by the same approval inside one core business system. The disposal request is the single source of truth. The warehouse instruction and the accounting instruction are both children of that one approved decision. Reconciliation stops being a month-end firefight and becomes a trivial check, because the two sides were never allowed to disagree in the first place.

Frequently Asked Questions

Why does disposal need an approval at all instead of just scrapping the parts?

Because disposal touches both inventory and accounting, and when it runs ungoverned the two sides drift. A supervisor signs a scrap sheet, the warehouse pulls the stock, and finance only finds out at the next physical count when a multi-million-yen variance appears with no named approver and no date. A governed disposal approval ties the inventory removal and the accounting write-down to the same decision, so the books and the warehouse can never silently disagree.

How is the segregation of duties enforced?

The approval routes the disposal decision to the person with the right authority based on the amount, and that approver cannot also be the person who physically removes the stock or the person who books the write-down. In practice, a small write-down below a threshold may need only a department head, while a larger one can require a committee or an executive. Routing is handled automatically by the value of the disposal, so the control does not depend on someone remembering which approvals apply.

Does the system post the inventory removal and the journal entry automatically when approval completes?

Not yet. The disposal approval workflow and the frozen audit trail are built and live today, so a company can file a disposal request, route it through the correct authority, and capture a tamper-resistant snapshot of what was approved. The automatic writeback that adjusts inventory records and posts the journal entry the moment approval completes is on the roadmap. Today the governed decision and the evidence are the parts you get immediately, and they are what an internal-control review actually asks for.

Why is this an internal-control and audit concern?

Writing down inventory reduces earnings, and if that reduction is not governed it can be used to hide problems, smooth results, or in the worst case conceal theft of physical assets. Internal-control frameworks ask two things on a disposal: that material write-downs were authorized by someone with the right authority, and that every disposal leaves a record tying the decision to a named approver, a date, a reason, and an amount. Kikan System delivers both through role-based routing and a frozen snapshot that no one can edit later.

Can a small manufacturer start with just this control?

Yes. The approval-workflows module runs governed disposal alongside the rest of a firm's approvals, so a manufacturer can stand up the disposal control on its own and expand from there. You can begin on the free plan with up to 2 users and no credit card required, and run disposal requests with the same routing and frozen evidence a larger firm relies on.

Key Takeaway

Scrap and write-down disposal does not need more spreadsheets. It needs one governed approval, inside an ERP, that ties the inventory removal and the accounting write-down to the same decision, with a frozen snapshot that proves who approved what and why. The approval control and the audit trail are live today in the core business system. The fully automatic writeback of inventory and journal entries on approval is on the roadmap. For a manufacturer that wants defensible disposal now, the governed approval is the part that matters, and it is already here.

Get Started With Kikan System

If disposal at your factory still drifts between the warehouse and the books, look at Kikan System. The approval workflows module runs governed disposal requests, routes them by amount and authority, and freezes a tamper-resistant snapshot of every decision for your internal-control review. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.