Write-Off vs Scrap vs Disposal — The Difference and When to Use Each
Published: April 14, 2026
An organisation purchases 200 chairs over five years. Some break, some are lost during office relocations, and some are simply obsolete. When the auditor asks for a reconciliation, the register still shows 200. Nobody formally removed any of them. The finance team knows the number is wrong, but there is no documented process for taking assets off the books — so they stay, year after year, inflating the asset base and distorting depreciation charges.
This is not a technology problem. It is a governance gap. Most organisations have a process for acquiring assets but no structured process for removing them. The result is an asset register that only grows — never shrinks — until a painful manual clean-up is forced during an audit.
This article explains how five distinct types of asset removal work when they are subject to the same governance framework as procurement: formal requisitions, approval chains, audit trails, and automatic register updates.
1. The Problem: Assets Disappear Without Governance
When there is no formal removal process, assets are removed from registers through ad-hoc methods:
- Email approvals. Someone sends an email saying "please write off the old printer" and the accountant manually deletes it from the Excel register. The email is buried in an inbox. No audit trail.
- Memo-based disposals. A memo is circulated for a condemnation committee. The committee meets, signs a paper, and the asset is struck off. The memo is filed in a cabinet. Finding it two years later is impractical.
- Silent removals. The accountant notices an asset has not been verified in two years and quietly removes it. Or worse, leaves it on the register because removing it requires explaining why it was not tracked.
- Scrap accumulation. Broken equipment is moved to a storeroom. It accumulates for years. It has residual value (metal, components) but nobody tracks it because the register only shows "active" assets.
The consequence is an asset register that does not reflect reality — and no trail showing how it got that way.
2. Five Types of Asset Removal
Not all removals are the same. A broken laptop and a sold vehicle require different accounting treatments. The system distinguishes five types:
| Type | What Happens | Register Effect | Tracking Asset Created? |
|---|---|---|---|
| Write-Off | Asset value reduced to zero — no recovery | Source asset reduced | No |
| Scrap | Asset condemned, physical material tracked | Source reduced + scrap tracking asset created | Yes (with -S suffix) |
| Disposal | Asset sold or auctioned — proceeds recorded | Source asset reduced | No |
| Movement | Asset transferred to another department | Source reduced + destination asset created | Yes (with -M suffix) |
| Consumption | Consumable item used up | Source asset reduced | No |
Each type follows the same governance framework — a formal requisition with multi-level approval — but the register effects differ based on what physically happens to the asset.
3. How Asset Removal Requests Work — Inheritance and Validation
When a user creates a removal requisition, they reference the existing asset by its ID. The system then automatically inherits all of the asset's metadata from the register: item name, description, classification, category hierarchy, location, department, custodian, and financial values.
These inherited fields operate in inherit_only mode. The requester cannot override or modify them. If the client attempts to supply a value for an inherited field, the system rejects the request with a validation error. This is enforced by the Field Rules Engine — the same governance layer that controls which fields are required, optional, or deactivated for each requisition type.
The rationale is straightforward: if you are writing off asset IT-EQ-2026-0042, the item name, location, and cost should come from the register, not from the requester's memory. Manual entry introduces errors — and there is no legitimate reason to override the register's values during a removal.
The requester provides only what the register does not already know: the quantity to remove, the reason, and any type-specific details (such as sale proceeds for a disposal).
4. SCRAP Tracking Assets — Derived IDs and Residual Value
SCRAP is the only removal type (besides MOVEMENT) that creates a new asset record. When an asset is scrapped, two things happen:
- The source asset is reduced — the scrapped quantity or value is decremented from the original asset record.
- A SCRAP tracking asset is created — a new record with classification "SCRAP" that represents the physical scrap material.
The tracking asset's ID is derived from the source: {source_asset_id}-S{sequence}. For example, scrapping asset IT-EQ-2026-0042 creates IT-EQ-2026-0042-S001. This derived ID preserves lineage without consuming the organisation's sequential asset ID pool — a critical distinction that prevents ID collisions with future procurements.
The tracking asset inherits the source's identity and ownership fields but carries proportional financials. If half the original quantity is scrapped, the tracking asset carries half the original cost and half the accumulated depreciation.
This design exists because scrapped items have residual value. A condemned printer has metal, plastic, and electronic components. An old air conditioner has copper and aluminium. This material sits in the scrap yard until it is sold — and that sale needs a reference in the register. Without a tracking asset, scrap revenue appears in the books with no corresponding asset to link it to.
Two paths to SCRAP — register removal vs gate-side rejection
The SCRAP path described above is for items already in the asset register. The asset was procured, received, capitalised, and used — then condemned at end of life or after damage in service. The negative-PR governance described in this guide is what walks it off the register.
There is a second SCRAP path for items that never reach the register. When goods are rejected at the gate or found damaged on receipt, they are captured against the gate entry or the GRN, not against an asset record. The disposition is recorded via POST /gate-entry/lines/<id>/scrap (pre-GRN) or POST /grn/<id>/record-pickup with disposition_type=SCRAP (post-GRN). A 10–2,000 character scrap_reason is mandatory, an authorized_by reference records who from the PO approval chain authorised the scrap, and a void is admin-only and soft-deletes the entry with its own reason. No tracking asset is created — there was no source asset to derive one from. See the gate entry and quality inspection guide for that flow.
5. DISPOSAL with Proceeds
Disposal records the removal of an asset through sale or auction. Unlike a write-off (where the value goes to zero), disposal captures what was recovered. The financial impact depends on the relationship between the sale proceeds and the book value:
- Proceeds exceed book value: a gain on disposal is recorded
- Proceeds below book value: a loss on disposal is recorded
- Proceeds equal book value: no gain or loss
The disposal requisition captures the proceeds amount and any relevant details about the sale. When posted, the source asset is reduced and the financial entries are generated for the accounting system.
6. Approval Chain for Removals
Every removal — whether a write-off of a Rs. 500 keyboard or disposal of a Rs. 50 lakh vehicle — goes through the same approval matrix used for procurement. The routing engine selects the approval chain based on the asset's classification, department, and value. This means:
- High-value write-offs require senior approval — an employee cannot unilaterally write off expensive equipment
- The approval chain is specific to the asset type and department — different departments can have different authority limits
- Every approval or rejection is recorded with the approver's identity and timestamp
The approval chain for an asset removal request works identically to a purchase requisition: the same levels, the same routing logic, the same lifecycle states (DRAFT, SUBMITTED, PARTIALLY_APPROVED, APPROVED). The only difference is the register effect when posted.
7. Audit Trail
Every removal creates a complete audit trail:
- Who raised the requisition and when
- Which asset was referenced and its state at the time of the request
- Each approval or rejection — by whom, at what time, with what remarks
- The posting event — what changed in the register, what financial entries were created
- For SCRAP: the tracking asset created, its ID, and its financial values
When an auditor asks "why was this asset removed from the register?", the answer is a structured record — not an email thread or a physical memo that may or may not be findable.
8. Frequently Asked Questions
What is the difference between a write-off and a disposal?
A write-off reduces the asset's value to zero with no recovery. The asset is acknowledged as having no further economic value — damaged beyond repair, obsolete, or lost. A disposal involves removing the asset from use while recovering some value through sale or auction. Disposal tracks the proceeds and the buyer. In accounting terms, a write-off creates a loss equal to the remaining book value, while a disposal creates a gain or loss depending on whether sale proceeds exceed or fall below the book value. Both require formal approval before the register is updated.
Why does SCRAP create a new asset record instead of just reducing the source?
When an asset is scrapped, the physical material does not disappear — it sits in a scrap yard or storage area until sold or disposed of. The scrap has residual value that must be tracked. Creating a separate tracking asset with classification SCRAP and a derived ID (for example, IT-EQ-2026-0042-S001) serves two purposes: it reduces the source asset on the original register, and it creates a visible record of the scrap material with its proportional financial value. This prevents scrapped items from accumulating physically but remaining invisible in the books.
How does inheritance work for asset removal requests?
When you create a removal request (write-off, scrap, disposal, movement, or consumption), you reference an existing asset. The system automatically inherits the asset's metadata — item name, description, classification, category hierarchy, location, department, financial values, and other identity fields. These inherited fields are locked, meaning the requester cannot override or modify them. If a value is supplied for an inherited field, the system rejects it with a validation error. The requester only provides the asset reference and the quantity to be removed.
Can an asset removal be reversed after posting?
Once a removal request is posted, the register change is permanent in the forward direction — there is no undo for posted transactions. This is a deliberate governance choice: every register change must go through the full approval cycle. To reverse a write-off or disposal, the organisation would create a new procurement requisition to re-add the asset, going through standard approval. For SCRAP, the tracking asset exists independently and can itself be disposed of through its own removal request. The audit trail preserves the complete history of all changes.
How does asset removal affect depreciation calculations?
When an asset is removed from the register — whether through write-off, scrap, disposal, or consumption — depreciation stops from the date of posting. The remaining book value at the time of removal determines the financial impact. For a write-off, the entire remaining book value becomes a loss. For disposal, the difference between sale proceeds and book value is a gain or loss. For SCRAP, the tracking asset inherits proportional financials from the source, and depreciation on the source stops for the removed quantity. Partial removals reduce the depreciable base proportionally.