Asset write-off proposals submitted without adequate verification were highlighted in reporting on the Pontianak City Government’s 2026 regional government asset census. Although local government governance differs from corporate governance, this context illustrates the importance of procedures that connect the reasons for write-offs, inspection evidence, and decisions by authorized parties so that everything remains traceable.
In a company, the work is not complete when an item is no longer used or leaves its storage location. Asset write-off procedures need to explain who submits the request, the basis for the decision, the required approvals, and the evidence that staff have updated the records correctly.
Risks when write-off decisions are difficult to trace
Problems with records and documents
Reviewers often find forms with brief explanations such as “damaged”, approvals sent through messages that were not archived, or asset lists marked as completed without references to supporting documents. The documents may exist, but reviewers struggle to establish the connections between them.
A decision to stop using an item is distinct from formal write-off approval and its accounting treatment. Physical disposal, for example through sale or destruction, is also a separate action requiring evidence appropriate to the method used.
Impact on internal reviews
Without clear connections between documents, internal auditors need to request additional explanations to establish authority, reasons, and decision dates. The risk increases if one person can propose, approve, and close a request without review by another party.
As an initial control measure, use a single request number on the form, inspection attachments, approvals, evidence of execution, and accounting references. This number connects the documents; it does not replace each asset’s unique identifier.
Define write-off stages with clear checkpoints
Submission criteria and evidence
Define acceptable reasons for write-offs, such as damage that is uneconomical to repair, obsolete technology, or items that no longer provide benefits. Support each reason with appropriate evidence; photographs of damage alone may not be sufficient to show that repair costs outweigh the benefits.
For companies in Indonesia, align the criteria with accounting policies, corporate authorization rules, and relevant tax and industry requirements. Review leased items, pledged assets, or items with unclear ownership further before processing them.
- Asset identification: code, description, serial number if available, location, and responsible person.
- Basis for the proposal: condition, reason, assessment date, and alternatives considered.
- Supporting evidence: technical reports, photographs, repair cost estimates, or other documents appropriate to the reason.
- Financial information: acquisition cost, accumulated depreciation, and carrying amount as of the review date.
- Execution plan: disposal method, person responsible for execution, and completion evidence to be prepared.
Example approval workflow
The requester from the user department explains the need for the write-off, after which a technical reviewer examines the condition and reasons. The asset administrator checks asset identification and document completeness before an authorized officer makes a decision. The finance department then records the transaction once the accounting recognition requirements have been met.
For example, a user department proposes writing off a machine because repeated repairs disrupt operations. The asset administrator forwards the request only after the technical report and assessment of alternatives are available. The approval then specifies the machine’s identification, the execution method, and the conditions that must be met.
Establish stages for checking completeness, reviewing reasons and evidence, granting approval, execution, and closure. If team size limits segregation of duties, ask a supervisor who is not involved in the transaction to perform an additional review.
Make procedures easy to use and review
Document and status checklist
Use statuses that distinguish the stages of work, such as submitted, incomplete, verified, approved, executed, and closed. Approved status is not evidence that the person responsible has disposed of the item or that the finance department has completed the accounting entries.
- The request number and asset identification are consistent across all documents.
- The reviewed evidence supports the reason for the write-off.
- The approval specifies the decision-maker’s identity, the date, and its scope.
- Evidence of execution specifies the approved assets and method.
- Updates to the asset master register and journal references are linked to the request file.
- The closure record identifies the reviewer and includes a traceable date.
The asset master register stores identification and management information for each asset. When updating it, staff need to retain the previous status, reason for the change, effective date, and identity of the person making the change, rather than simply deleting the asset’s row.
Each stage also needs to identify the responsible party so that reviewers can trace the process. The principle of recording changes in responsibility without breaking the history discussed in the linked article helps reviewers identify who held the information before the authorized party decided on the write-off.
Exceptions that need to be addressed
For requests covering multiple assets, record the review results for each asset, rather than just a blanket approval without details. If only some qualify, separate the approved assets from those deferred so that the person carrying out the disposal does not misinterpret the decision.
If the execution method changes after approval, the authorized party needs to review it again. Approval for destruction, for example, does not automatically provide a basis for sale because the risks, documents, and parties involved may differ.
Avoid gaps in execution
Incomplete evidence or approvals
One mistake is assuming that a formal record of execution is sufficient to replace prior approval. A formal record documents an event or its execution, while approval shows that the authorized party has made a decision.
For assets that store data, add a check to ensure data is secured or erased before physical disposal, in accordance with information security policies. For items requiring special handling, also check the relevant environmental or safety requirements.
Handling incomplete files
Defer closing the request if prerequisites have not been met, then record the gaps, the person responsible for follow-up, and the target completion date. Do not backdate approvals or replace old documents without retaining a revision history.
If the person responsible has already disposed of the item, record what actually happened and report the deviation to the relevant officer for follow-up. The finance department still needs to assess the accounting treatment based on the facts and the relevant period. Administrative deficiencies must not be used as a reason to disregard the event.
Set minimum standards before approving the procedures
Minimum standards cover the allocation of authority, request forms, types of evidence for each reason, rules for status changes, and closure requirements. Also specify the procedure owner, file storage location, access rights, and retention period in accordance with applicable policies and requirements.
Test the draft procedures using several files with different circumstances, including rejected requests and requests that changed after approval. Periodically check whether reviewers can trace decisions from start to finish without relying on verbal explanations from staff.
Consistent procedures do not guarantee that all audit findings will disappear, but they help reduce gaps in evidence and authorization. Their main value is ensuring that every decision has a basis, every execution has evidence, and every closure has a clearly identified responsible person.
Reviewing a single write-off file can be a starting point for testing the completeness of these standards.
Learn how Fisetra supports asset controls at fisetra.com.