Requests for asset disposal usually come from operational teams: a machine is no longer economical to repair, a vehicle is no longer fit for use, or work equipment can no longer be used. However, this process often stops at the operational level, so the reasons, evidence, and final status are inconsistent in the report. To prevent this from becoming a recurring finding, asset disposal files need to be prepared as a chain of evidence, not merely as an approval form.
The pressure to manage assets in a more traceable way is also visible in the public sector. In a focus group discussion (FGD) involving BPA Kejaksaan RI, the Head of BPA Kejaksaan RI Patris Yusrian Jaya emphasized that legal risk management cannot be applied partially, as reported in the initiative to use AI for asset recovery. For companies, the operational message is clear: every decision regarding an asset needs to have a basis, a process flow, and a trail that can be reviewed across functions.
In company practice in Indonesia, an asset disposal procedure should connect three things: physical condition, book value, and approval authority. If one of them is incomplete, internal auditors will find it difficult to assess whether the disposal was carried out for reasonable business reasons or merely followed a work unit’s request.
Operational symptoms that need to be mapped
Before improving the document format, the team needs to map the weak points that make asset disposal inconsistent. Early symptoms are often seen in differences in narratives across units, not only in the figures in the report.
Symptoms that are usually visible
The first symptom is a disposal reason that is too general, for example “damaged” without information on the severity of the damage, repair history, or estimated recovery cost. Such information is not sufficient to distinguish assets that truly need to be disposed of from assets that can still be transferred, repaired, or sold.
The second symptom is inconsistent supporting evidence. One branch attaches photos, official records, and technical recommendations, while another branch only sends a list of asset numbers. When the evidence format differs, finance managers must spend additional time assessing whether the decision is appropriate.
The third symptom is an unclear final status. An asset may no longer be used at the location, but it is still recorded as active in the register, still depreciated, or does not yet have physical release documentation. This condition makes the fixed asset report look tidy on paper, but it does not reflect a situation that can be accounted for.
Impact if left unaddressed
The most immediate impact is a delay in period closing, especially if the disposal relates to book value, loss expense, or proceeds from the sale of assets. Finance cannot complete journal entries with confidence if the administrative basis is incomplete.
The next impact is a weakened audit trail. Internal auditors will trace who proposed, who verified, who approved, and when the decision was executed. If these stages are not recorded, verbal explanations are usually not enough to close the audit risk.
Core steps to fix the problem
The most effective improvement is not adding many forms, but establishing minimum evidence for each reason for disposal. In this way, the operational team understands the documents that need to be prepared from the outset.
Criteria for determining priorities
Use one priority definition so that all parties read the risk level in the same way. A simple example is P1 to P4, based on value, sensitivity, and operational impact.
- P1: high-value assets, assets that affect financial statements, or assets with specific compliance risks.
- P2: medium-value assets with technical evidence that needs to be verified before disposal.
- P3: low-value assets, but in large quantities or spread across several locations.
- P4: small assets with low risk and physical evidence that is easy to confirm.
This priority is not a substitute for company policy. Its function is to help the team determine the depth of review, approval level, and urgency of completing the file.
For P1, the file should include a proposal document, asset identity, condition photos, technical inspection results, latest book value, recommended course of action, and approval from the authorized official. For P4, the company can set more concise evidence, as long as the asset identity and disposal reason remain traceable.
A simple decision simulation
For example, a production machine in a factory has stopped being used for three months. The operational unit proposes disposal because the repair cost is considered uneconomical, but finance still sees a remaining book value.
In this situation, the decision must not rely solely on the statement “not fit for use”. The asset manager needs to collect the technical report, repair cost estimate, condition photos, maintenance history, book value, and other utilization options such as cannibalizing spare parts or selling scrap.
If all evidence shows that recovery does not make business sense, disposal can be processed according to the approval matrix. If the technical evidence is not yet adequate, the asset status should be held as “pending verification”, not immediately disposed of or left active without notes.
How to implement without adding complexity
A good asset disposal procedure must be easy for branches, operational units, finance, and internal auditors to execute. The key is to limit document variations, clarify task owners, and establish the same status in the asset register.
Quick checklist
Use a short checklist as an administrative guardrail before disposal enters the approval stage. This list can be attached to the proposal form or entered into the asset management system.
- Asset number, asset name, location, last user, and asset category match the register.
- The disposal reason is written specifically, for example severely damaged, lost, technologically obsolete, or uneconomical to repair.
- Physical evidence is available, such as photos, technical reports, or inspection records.
- The latest book value and depreciation status have been confirmed by finance.
- The final treatment option has been determined, for example sold, destroyed, donated, or kept as spare components.
- Approval follows the authority matrix applicable in the company.
This checklist should not stand alone. Each item needs to have an attachment or supporting note, so that reviewers can trace the basis for the decision without requesting explanations again from the proposing unit.
The same principle applies to the handover process: status, evidence, and approval must be in one flow. The discussion on clear handover approval is relevant because asset disposal also requires control points that do not get stuck between teams.
Pitfalls that often repeat the problem
The first pitfall is accepting photos without context. A photo of a damaged asset is not enough if it does not show the asset number, location, inspection date, or the party who verified it.
The second pitfall is equating a disposal proposal with a disposal decision. A proposal is an initial request from the user or asset manager, while the decision only becomes internally valid after going through verification and approval according to authority.
The third pitfall is not establishing an interim status. In many cases, an asset is no longer suitable to remain active, but it is also not ready to be disposed of. Statuses such as “under investigation”, “pending technical recommendation”, or “pending finance approval” help keep reports honest without forcing decisions too quickly.
Signs that the improvement is not yet stable
After the procedure is implemented, the team still needs to evaluate whether the flow runs consistently. Stability is reflected in the quality of files, the speed of clarification, and the low number of revision requests before final approval.
Errors that often appear
A common error is an approval matrix that does not follow the value or risk of the asset. High-value assets may be processed with an approval level that is too low, while small assets instead wait for layered approvals that are not proportionate.
Another error is the absence of role separation between the proposer, reviewer, and approver. If one party both proposes and verifies without adequate controls, the quality of the decision becomes difficult to defend during an audit.
Companies also often forget to close the accounting and physical consequences at the same time. The asset has been removed from the location, but the journal entry has not been prepared; or the journal entry has been made, but the item is still in the warehouse without a clear disposal status.
How to respond without panicking
If an incomplete file is found, do not immediately cancel the entire process. Separate cases by risk: hold P1 and P2 until the core evidence is complete, while P3 and P4 can be corrected by completing attachments if the basis for the decision is still clear.
Create an exception list containing the asset number, document deficiencies, responsible party, and internal completion deadline. This list helps finance managers see the improvement workload concretely, instead of merely receiving a note that “documents are incomplete”.
For old cases, the team should prepare a clarification memo. The memo does not replace the original evidence, but it can explain the chronology, reasons for documentation delays, and corrective actions so that the same pattern does not recur.
Added value for decision-making
A strong asset disposal file provides value beyond administrative compliance. Well-organized documents help the company distinguish assets that must be disposed of, assets that can still be recovered, and assets that need to be monitored before a final decision.
For finance managers, the main benefit is clarity in the basis for recording and fewer revisions ahead of period closing. For internal auditors, the benefit is a shorter examination path because the evidence, approvals, and final actions are in one sequence.
For asset managers, an organized procedure reduces dependence on personnel memory. When staff rotation, location changes, or sudden inspections occur, asset status can still be explained through the same documents.
A good disposal decision always answers four questions: what asset is being disposed of, why it needs to be disposed of, who approved it, and how the final action is evidenced. If these four answers are consistently available, the risk of administrative gaps will be far more controlled.
Start with one consistent file format, then test it on the next disposal case.
Learn how Fisetra helps asset control at fisetra.com.