Operational units often propose asset write-offs because assets are damaged, lost, obsolete, or no longer economical. However, the documents accompanying such decisions do not always consistently explain the reasons, physical evidence, and final status. In practice, an asset write-off can remain merely an operational action, even though finance managers and internal auditors need a trail that can be traced through to the reports.
Pressure in asset administration is also evident when BPK highlighted the Parepare City Government’s fixed asset management, including Rp20 billion in depreciation of fixed asset value and records considered inadequate in its audit scrutiny of fixed asset administration. For companies, the lesson is clear: asset write-off procedures need to be supported by orderly administrative evidence and approvals, not merely a decision that an asset is no longer in use.
Why asset write-off evidence needs attention
A fixed asset write-off is not simply removing an item from the list of assets in use. This decision affects book value, depreciation expense, location records, user responsibility, and evidence that the company has assessed the asset fairly before removing it from the register.
Early signs that usually appear
Early signs usually appear when the proposed write-off list contains only general reasons, such as “damaged” or “not used”. There are no photos, technical reports, or condition inspection results. The accounting team then receives a journal request but does not yet have a sufficient basis to distinguish between a completely damaged asset, a lost asset, an asset to be sold, or an asset still awaiting destruction.
Another sign appears from differences in terminology between departments. Operations may say the asset is “discarded”, the asset manager records it as “written off”, while finance waits for confirmation of whether the asset has been sold, destroyed, or transferred to another party. These small differences can make the final status inconsistent.
Impact if not addressed promptly
If supporting evidence is weak, internal auditors will find it difficult to assess whether the write-off was performed based on actual conditions or merely followed a user request. The risk is not only incorrect recording, but also the loss of an accountability trail for assets with material value.
Another impact is felt at closing. Assets that are no longer physically present may continue generating depreciation, while assets that have already been sold may not have adequate disposal evidence. As a result, the finance team must repeat clarifications when reporting pressure is high.
Practical steps to prepare write-off evidence
A good procedure needs to separate three things: the reason for the write-off, the supporting evidence, and the final decision. The three are related, but they should not be merged into one brief note that is difficult to verify later.
Main criteria to establish
First, establish limited and consistent categories of write-off reasons. Examples include severely damaged, lost, technologically obsolete, uneconomical to repair, no longer used due to process changes, or disposed of through sale in accordance with company policy.
Second, determine the minimum evidence for each category. A severely damaged asset should be supported by photos, a technical report, repair cost estimates where relevant, and a recommendation from the authorized party. A lost asset needs to be accompanied by a chronology, an official report, and evidence of follow-up actions in accordance with internal policy.
Third, separate the technical recommendation from the write-off approval. Technicians or users can explain the condition of the asset, but the decision to remove an asset from the register should go through authorization appropriate to its value, asset type, and level of risk.
Simple implementation example
For example, a production machine has stopped operating for six months because a main component is unavailable. The user proposes a write-off on the grounds that it is “uneconomical to repair”. The evidence that needs to be prepared may include photos of the machine, breakdown records, repair estimates, the latest book value, and a recommendation from the head of production.
After that, the asset manager checks the asset number, location, and ownership status in the register. The finance team assesses the accounting impact, while the authorized officer approves whether the machine will be sold as scrap, destroyed, or treated according to another policy. This sequence makes the decision easier to review later.
How to implement without adding complexity
Write-off documentation does not have to become a lengthy process, but it needs to be designed so the same evidence is not requested repeatedly. The key is to create concise document standards while clearly defining who fills them in, checks them, and approves them.
Brief checklist before processing
The following checklist can be used as a basis before a write-off request is processed further:
- Asset number, asset name, last location, and user unit match the register.
- The write-off reason is selected from established categories.
- Physical or technical evidence is available according to the type of reason.
- Book value and depreciation status have been confirmed by the finance function.
- The recommended follow-up specifies sold, destroyed, temporarily stored, or another approved option.
- Approval follows the applicable authority limits.
This checklist should be used as an initial filter, not a formality after the decision has been made. If one important piece of evidence is not yet available, the request status can be held as “requires completion” so it does not proceed directly to final recording.
Mistakes to avoid
A common mistake is using the same form for all conditions without room to explain specific evidence. Lost assets, damaged assets, and assets being sold have different risks, so their supporting evidence also needs to be differentiated.
Another mistake is storing evidence in many places without a clear index. Photos are on an officer’s phone, the official report is in email, while the approval is in a messaging application. During an audit, time is spent searching for documents rather than explaining the basis for the decision.
The principle of cross-functional documentation also applies to other processes involving fixed assets. Before an asset changes status, teams can use a similar approach with checks of identity, condition, authorization, and supporting evidence for fixed assets so that decisions do not depend only on the memory of the last user.
Asset write-off mistakes that often recur
In addition to document issues, the biggest obstacle in asset write-offs is decisions that are made too quickly or too slowly. Both can reduce control quality, especially if the company has many locations, many asset holders, or a fast replacement cycle.
Common error patterns
First, approving a write-off based only on verbal information. User explanations are important, but they need to be supported by evidence showing the condition of the asset on a specific date.
Second, failing to distinguish between the incident date, inspection date, approval date, and accounting recording date. These four dates may differ, and the differences need to be explained so that the sequence of events remains logical.
Third, removing an asset from the list without determining its physical follow-up. If an asset is no longer used but remains in the warehouse, the company still needs to arrange safeguarding, disposal, or destruction in accordance with policy.
How to respond without panic
If a write-off request is already underway with incomplete documents, do not immediately force final recording. Create a list of evidence gaps, assign responsible persons, and set a realistic completion deadline.
For low-value and recurring cases, the company can use a simpler evidence format as long as it still includes asset identity, reason, condition evidence, and approval. For high-value or high-risk assets, the documentation should be more detailed, including analysis of repair, sale, or destruction options.
Internal auditors can help by performing sample testing before the reporting period ends. If a pattern of evidence deficiencies is found, improvements can be made to the procedure, not just to one write-off file.
Added value for the decision-making process
A strong asset write-off procedure provides one main benefit: decisions can be explained later without depending on the person who first submitted the request. This is important when staff changes occur, during internal reviews, or when tracing the history of a particular asset.
Finance managers gain a clearer basis for updating the register and recording the accounting impact. Asset managers have evidence that the physical condition has been verified. Internal auditors can assess whether controls are operating consistently, not merely whether documents are available.
In implementation, companies should start with a simple matrix that connects the type of reason, minimum evidence, reviewing officer, and approving officer. Once the matrix is in use, evaluate several real cases to see whether the evidence requested is sufficient, excessive, or still leaves gaps.
An orderly asset write-off does not mean slowing down operations. On the contrary, clear evidence from the outset helps companies make decisions faster, maintain reporting consistency, and reduce repeated clarifications during audits.
Use the next write-off case as a trial for a more traceable evidence standard.
Learn how Fisetra helps with asset control at fisetra.com.