Fixed-Asset Acquisition and Disposal: Approve Every Move

A controller at a precision parts maker sits down to close the fiscal year. The fixed-asset register says the company owns 14 machine tools. The floor manager can name 13. One tool was sold for scrap eight months ago, the cash went through the bank, and nobody told the register. A press bought last quarter runs every day but never made it onto the books because the purchase bypassed approval. The depreciation schedule is wrong in two directions, the external accountant wants evidence of the sale, and the year-end close becomes a week of reconstruction instead of an afternoon.

This is the normal state of fixed assets at many manufacturers. Equipment is bought, moved, and disposed of without a governed approval, so the register drifts from reality one move at a time. Each gap breaks two things at once. Depreciation runs against the wrong basis, because the register does not match what the company owns. And the audit evidence breaks down, because nobody captured who approved the acquisition, the disposal, or the change in useful life. A modern ERP closes that gap by making every asset move a single governed approval with a frozen audit trail, so the register and the evidence stay honest together.

Why the Register Drifts, and Why It Costs More Than It Looks

A fixed-asset register is a promise that the balance sheet corresponds to real equipment the company owns, and that depreciation flowing through the income statement is based on the right assets at the right cost and useful life. The moment an asset move is not governed, that promise breaks.

The drift happens in three places. The first is ungoverned acquisition: a machine arrives and starts producing before anyone books it as a fixed asset, so it depreciates late or never. The second is ungoverned disposal: a press is sold, scrapped, or donated, the cash or removal happens, and the register keeps depreciating a ghost, overstating assets or understating the gain on disposal. The third is ungoverned change: useful life gets extended, or a repair gets capitalized that should have been expensed, and none of it leaves a record tying the decision to a named approver.

Each is a number error and a control error at once. The number error shows up at year-end as a restatement or a depreciation curve that makes no sense. The control error shows up when an auditor asks who approved the disposal of an 8-million-yen press. On paper the answer is usually a shrug, a stamped form that got recycled, or an email thread no one can find. From a J-SOX standpoint, that missing authorization on a material move is exactly what an internal-control review flags, because it is also the classic shape of asset misappropriation.

The root cause is always the same. The physical asset moves through operations, the cash moves through finance, and the register lives in a spreadsheet with no single approval tying all three together. A core business system makes the approval the one event that authorizes the move and freezes the evidence in the same stroke.

One Approval for Every Asset Move

The right way to govern fixed assets is to stop treating acquisition, disposal, and change as accounting chores that happen after the fact. Each is a business decision with consequences for cash, the register, and depreciation, and each should be captured as a single governed request before the move is allowed to happen.

In an ERP, an asset acquisition begins as a request naming the asset, the cost, the expected useful life, the depreciation method, and the owning department. For a capital expenditure above a threshold, routing automatically pulls in an executive or a committee, because large spend should never rest on one pair of hands. The same logic governs disposal: a request to retire or sell a press names the asset, the reason (sale, scrap, donation, or obsolescence), the expected proceeds, and the remaining book value. Routing reflects authority rules, so a 2-million-yen disposal goes to the department head and a 20-million-yen disposal goes to the board. This is the same approval engine that runs ringi (internal approval proposals), purchase orders, and expense claims across the company.

What makes the control real is the frozen snapshot. The moment a move is approved, the system records an unchangeable view of exactly what was authorized: the asset, the cost or proceeds, the useful life or reason, the approver, the date, and the time. This is not a living spreadsheet cell someone can overwrite later. It is the evidence. If the register later shows a press at 18 million yen and the approval snapshot shows 18.5 million yen, the gap is resolved in seconds, not at year-end under audit pressure.

Because the approval and the snapshot live in the same system as the register and the ledger, the two sides can never silently diverge. The physical asset, the register, and the depreciation schedule each have a governed instruction, all tracing back to the same approved decision, signed by the same named approver on the same timestamp.

What Is Built Today, and the Honest Roadmap

Here precision matters more than selling. The approval workflow and the full audit trail for fixed-asset acquisition and disposal are built and live today. A company can file an acquisition or 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, in production, and it is the part an internal-control review actually wants to see.

What is on the roadmap, and not yet built, is the automatic writeback that posts the asset journal entry and updates the fixed-asset register the moment approval completes. Today, when a move is approved, the system gives you the governed decision and the complete evidence, and the journal entry and register update 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 vendor records in the current workflow writeback layer, where only expense reimbursement and leave applications post automatically on approval today. For fixed assets the registry and entity types exist, so adding the handler is contained work, but it is not yet shipped.

Saying this plainly matters because the worst thing a fixed-asset process can do is promise automation it cannot deliver. The approval control and the audit trail are live and defensible right now. The automatic posting of the asset journal and the one-click register update on approval are coming. A company that needs governed fixed-asset moves today does not have to wait, because the governed approval and the frozen evidence are the parts that satisfy an auditor and protect against misappropriation. The automation is the convenience layer on top.

A Scenario: The Precision Parts Maker in Shizuoka

Picture a precision parts manufacturer in Shizuoka, about 280 staff, supplying automotive OEMs and industrial machinery makers. Capital equipment is the heart of their cost base. They buy and refurbish machine tools regularly and every few years retire or sell a line that has reached the end of its useful life. Before they adopted a governed asset flow, every one of those moves was an informal event.

A typical disposal went like this. A line lead decided a 12-million-yen CNC machine was no longer accurate enough. A used-equipment dealer offered 3 million yen for it. The plant manager said yes on the shop floor. The cash arrived in the bank. Eight months later, the year-end close revealed the register still depreciating the machine, the 3-million-yen proceeds never recognized as a gain on disposal, and no record of who had authorized the sale. The controller spent three days reconstructing the move from email, bank statements, and a scribbled note. At the next internal-control review, the auditor flagged two similar disposals with no named approver and warned that the segregation of duties between authorizing a sale and recording it had collapsed.

In the new flow, the same retirement begins as a disposal request inside the ERP. It names the CNC machine, the reason (obsolescence and accuracy loss), the 3-million-yen proceeds, and the remaining book value. Because proceeds and book value cross a threshold, routing automatically pulls in the plant manager and then an executive, with watchers from finance following without being approvers. When the last approval lands, the system freezes a snapshot of the entire decision. The asset has a governed instruction to come off the active register, and accounting has a governed instruction to recognize the disposal and stop the depreciation, both pointing to the same approved record.

Acquisitions run the same path in reverse: a new press arrives as an acquisition request with cost, useful life, and depreciation method, routed by amount to the right authority, and the snapshot freezes at approval so the register and depreciation schedule start from a governed basis the day the asset enters service. At the next internal-control review, the auditor asks the same question about a large disposal, and the answer is one click away. The reconstruction that used to take three days now takes three minutes, because the approval trail was built into the asset move from the start.

Why This Is a J-SOX Concern, Not Just an Accounting Chore

Fixed-asset governance is a textbook internal-control topic, and in Japan it falls squarely inside the J-SOX framework that governs internal control over financial reporting. The reason is uncomfortable. Fixed assets are usually one of the largest lines on a manufacturer's balance sheet, and depreciation is one of the largest recurring expenses on the income statement. If acquisitions and disposals are not governed, both numbers become unreliable, and unreliable numbers are exactly what an internal-control framework is designed to prevent.

Three control principles are at stake, and a core business system delivers each by construction. Authorization: material moves must be approved by someone with the right authority, enforced by amount and role, so a 20-million-yen disposal can never rest on one supervisor. Segregation of duties: the person who authorizes a disposal should not be the person who receives the cash or records the entry, and routing by position rather than by named individual keeps that separation intact even as staff change, because the control survives the people. Audit trail: every asset move must leave a record tying the decision to a named approver, date, reason, and amount, and the frozen snapshot delivers that record without anyone having to remember to file the paper.

For a manufacturer, the register is also an operational signal. A line of machines that all reach disposal in the same quarter points at a replacement cycle needing capital planning. When moves are governed and recorded, those signals become visible instead of buried in a spreadsheet nobody trusts.

Frequently Asked Questions

If the register update is not automatic yet, what is the point of governing the approval now?

The audit evidence is the part that fails first and costs the most to reconstruct. A missing depreciation entry is a number error you can fix, while a missing authorization on a 12-million-yen disposal is a control failure an auditor will flag. Governing the approval now builds the evidence in real time, so year-end shrinks to a check instead of a rebuild. The approval module does not have to wait for a full ERP replacement either, a company can deploy it alone first and connect the rest of the system as writeback comes online.

How is this different from a fixed-asset tracking spreadsheet?

A spreadsheet holds data but does not enforce authority, and anyone can edit any cell with no record of who approved a disposal or when. The approval workflow in Kikan System enforces authority by amount and role, freezes a snapshot that cannot be overwritten, and ties every asset move to a named approver and timestamp. A defensible register is one whose evidence was captured at the moment of decision, not reconstructed months later.

Does the workflow route a large disposal differently from a small one?

Yes. Routing reflects your authority rules, so a 2-million-yen disposal goes to the department head while a 20-million-yen disposal routes to the board or an executive committee. Capital expenditure above a threshold can automatically pull in a committee so large spend never rests on one pair of hands. You set the thresholds and roles once, and the system applies them the same way on every asset move.

Can we start governing fixed-asset moves without replacing our whole system?

Yes. You can deploy the approval module standalone and run governed acquisition and disposal requests through it before connecting the rest of the operation. You can also start on the free plan with up to 2 users and no credit card. The governed approval and the frozen snapshot are the parts that satisfy an auditor, and they are live today.

Key Takeaway

Fixed-asset acquisition and disposal need one governed approval, inside an ERP, that ties the physical move, the cash, and the register 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 automatic posting of the asset journal and the one-click register update on approval are on the roadmap. For a manufacturer that wants defensible asset moves now, the governed approval is the part that matters, and it is already here.

Get Started With Kikan System

If your fixed-asset register still drifts from the floor at year-end, look at Kikan System. The approval workflows module runs governed acquisition and disposal requests, routes them by amount and authority, and freezes a tamper-resistant snapshot of every asset move 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.