Stocktake Adjustments: Approve So Inventory Can't Be Silently Fiddled

It is the last day of the quarter at a mid-size precision parts maker in Shizuoka, about 280 staff, supplying automotive OEMs. The warehouse team has just finished the physical count of high-value components. There is a gap of 412 units between what the shelves hold and what the system says should be there. The warehouse lead opens the inventory screen, types in 412 as the adjustment, and saves. The on-hand balance moves instantly. Nobody signs it off. Nobody records why. Three months later, when finance spots the cost-of-goods swing at the month-end close, the trail is already cold. Nobody can say whether those 412 units were miscounted, broken, stolen, or quietly written down to cover a shortfall.

That single screen is where inventory shrinkage and outright fraud enter the books. A core business system closes that hole by refusing to let an adjustment land on its own. Any stocktake difference above a threshold you set routes for sign-off, and the system keeps a frozen snapshot of the before and after so the adjustment can never be silently fiddled. This post is about that one control and why it matters more than the counting itself.

Why the Count Is Not the Problem

Companies spend enormous energy on the stocktake itself. They shut the line, send counters in pairs, use barcode guns, and reconcile twice. Then they throw all of that rigor away at the final step, when someone types the variance into the inventory record unchallenged.

The honest finding from internal-control work in Japan is blunt: the four purposes of internal control are consistent enforcement of rules, exact grasp of operations, prevention of error and fraud, and auditability. A stocktake that ends in an unapproved adjustment satisfies none of them. The rule is not enforced because one person overrides the count. The operation is not grasped because no reason is recorded. Error and fraud are not prevented because there is no second pair of eyes. And the result is not auditable because the change is invisible.

The cost of that gap is not theoretical. Inventory shrinkage, whether from damage, miscount, or theft, lands directly in cost of goods sold. When the adjustment is uncontrolled, the same screen that records genuine damage also hides pilferage, covers booking errors, and lets staff massage the books to hit a target. The warehouse looks clean on paper. The money has already left.

A modern ERP treats the adjustment as a controlled event, not a free text field. The variance is captured, routed, reviewed, and only then allowed to touch the balance, with every step stamped into history.

What a Built-In Approval Step Actually Does

The control is not a spreadsheet checkbox. It is a workflow that lives inside the core business system and runs the same way every time. Reading the real approval engine, here is what is genuinely built today, and where the boundary honestly sits.

Any variance above a threshold routes for sign-off

You set the rules once. A difference of 50 units, or 200,000 yen, or any figure you choose, triggers the approval route automatically. Small rounding variances, the ones that are genuinely noise, can be auto-accepted or skipped. Anything material is held. The person who entered the variance cannot also approve it. The request lands in the queue of the role, position, or department you defined, and it survives a reorganization because it routes to the role, not a name.

For a high-value discrepancy, you can require more than one sign-off. A committee gate can demand a quorum, say three of five managers, before the adjustment goes through. For speed on routine items, an any-of-N rule lets the first approver clear it. The point is that the threshold and the route are policy, written down and applied identically every quarter.

A frozen snapshot of exactly what was approved

This is the part that makes the control audit-proof. When the variance request is submitted, the system captures a frozen snapshot of what was on the shelves before, what the count found, and what the adjustment will set the balance to. That snapshot does not change, even if someone edits the underlying records later. When an approver signs off, they are signing the snapshot, and the snapshot is what carries into the audit trail.

For a company thinking about J-SOX or general internal control, this is the evidence an auditor asks for. You can show, per adjustment, who requested it, who reviewed it, who approved it, when, and what the before and after were. There is no reconstruction from memory and no gap between the decision and the record.

Segregation of duties by construction

The control enforces segregation without relying on goodwill. The person who counts cannot approve. The person who approves cannot post. The watcher role lets a finance lead or an auditor follow a high-value adjustment without being an approver, so stakeholders see movement in real time without diluting the sign-off chain. Delegation is supported, but for a high-risk adjustment the system can demand mandatory re-approval rather than letting a stand-in quietly sign.

What is built today, and what is honestly on the roadmap

Being precise matters here. The approval step and the frozen audit trail are built and live today. You can configure the threshold, set the route, require a committee, attach the snapshot, and produce the full history of who approved what. That control is real and running.

What is not yet built is the automatic writeback of the approved variance to the live inventory balance. Today, once the adjustment is approved, the movement of the on-hand quantity is a separate manual step in the inventory record. Automatically adjusting the stock balance on approval is on the roadmap, not shipping today. The approval gate and the audit trail are the safeguard; the hands-free writeback to inventory is coming. We say that plainly because overselling the boundary is worse than the boundary itself.

The Scenario: The Shizuoka Parts Maker

Return to the precision parts maker in Shizuoka. Before the control, the 412-unit variance landed in the books the moment the warehouse lead saved the screen. Finance found out at month-end, by which point the reason was already forgotten and the cost-of-goods line just looked soft.

In the new flow, the warehouse lead enters the variance of 412 units. Because it clears the threshold, the system does not adjust the balance. Instead, it creates an approval request carrying the before count, the physical count, the variance, and a free-text reason field the lead must fill in. The request routes to the warehouse manager, and because the value exceeds the high-value threshold, it also routes to the finance controller as a parallel sign-off. A quality lead is added as a watcher, so they can see the request without being on the approval chain.

The warehouse manager opens the request, reviews the snapshot, checks the reason, and approves. The finance controller does the same. The moment both sign off, the system stamps the approval, freezes the snapshot, and writes the full event into the audit trail. The on-hand balance is then adjusted manually in the inventory record, keyed to the approved request number, so the two stay linked. At the next quarter-end, the same pattern repeats. Over a year, finance can pull every material adjustment, see the before and after, the reason, and the approvers, and answer an auditor's question in minutes instead of days.

The warehouse lead no longer has the power to silently move the balance. The control does not slow down a genuine correction. It simply makes sure every correction is seen, reasoned, and signed.

Why This Matters Beyond the Warehouse

The benefit is not only fraud prevention, though fraud prevention is real. Inventory is one of the largest assets on a manufacturer's balance sheet, and uncontrolled adjustments are the classic place where the books drift from reality. A control that forces sign-off and keeps evidence protects the integrity of cost of goods, gross margin, and ultimately the month-end close.

There is also a cultural shift. When staff know an adjustment will be reviewed, the count gets more careful. The reasons get more honest. The boundary between a genuine variance and a quiet fix becomes visible. That visibility is what internal control is supposed to produce.

Finally, there is the audit itself. Japan's framework for internal control, the same one that underpins J-SOX for listed companies and that private firms adopt as good practice, rests on documented evidence. A frozen snapshot with named approvers is exactly that evidence. You are not assembling it after the fact. You built it by running the process correctly.

Frequently Asked Questions

Does the stocktake approval step slow down the month-end close?

For material variances, yes, by the time it takes a manager to review. For routine noise below the threshold, no, because those can be auto-accepted. The honest trade-off is that a control that approves everything instantly is not a control. The time spent reviewing a 412-unit gap is time well spent, because catching the reason at the moment of adjustment is far cheaper than investigating it three months later.

Can we still make emergency inventory corrections quickly?

Yes. The any-of-N rule means the first available approver can clear a genuine correction without waiting for the whole chain. For a true emergency, delegation lets a stand-in sign, and for high-risk items the system can still demand re-approval. Speed and control are not opposites here. The control removes the silent path, it does not remove the fast one.

Will the on-hand stock balance adjust automatically once an adjustment is approved?

Not yet. The approval gate and the frozen audit trail are live today in Kikan System. The step that automatically moves the on-hand balance the instant approval completes is on the roadmap, not shipping now. Today the balance is updated manually in the inventory record, keyed to the approved request number so the two stay linked.

How does stocktake adjustment approval fit the rest of the ERP?

The same approval engine runs expense reimbursement, purchase orders, leave applications, and every other request type, each with its own form and route, no developer needed. Stocktake adjustment approval is one configuration of a core business system that already handles the rest of the operation. You can also deploy the workflow standalone first, and you can start on the free plan with up to 2 users and no credit card.

Does the approval workflow record who made and signed off each variance?

Yes. Every adjustment captures who requested it, who reviewed it, who approved it, when, and what the before and after counts were. The frozen snapshot of the variance cannot be edited later, so the evidence survives even if the underlying records change. That is exactly what an auditor asks for, available in minutes instead of days.

Key Takeaway

The stocktake is only as honest as the adjustment step that follows it. A core business system that routes any material variance for sign-off, freezes a snapshot of the before and after, and keeps a full audit trail turns inventory from a number someone can silently change into a record someone has to defend. Shrinkage becomes visible. Fraud loses its favorite door. And the close gets a backbone.

Get Started With Kikan System

If unapproved inventory adjustments keep you up at month-end, look at Kikan System. The approval workflow routes every stocktake variance above your threshold for sign-off, with a committee gate for high-value items and a frozen snapshot that survives the audit. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started, or compare plans at /#pricing.