Disposing of an Asset Properly: Retirement, Write-offs & the Trail Auditors Ask For
Getting an asset onto the register is the easy half. Getting it off — with a reason, an approval, a buyer and a paper trail that survives questioning — is where most registers quietly break, and where the awkward audit questions live.
Assets leave organizations constantly. They are sold, scrapped, written off after a theft, donated to a school, given to a departing staff member, cannibalised for parts, or simply stop appearing at verification until somebody removes the line. Only the first two of those usually get done properly, and the rest are how a register loses its credibility.
The test is simple and unforgiving. Pick any asset that was on your register two years ago and is not there now. Can you produce, in five minutes, what happened to it, who authorised it, what it was worth and who has it? If not, the register does not describe your assets — it describes the ones nobody has removed yet.
Five ways an asset leaves, and only one is a sale
Organizations design a disposal process around selling equipment, then apply it awkwardly to everything else. The exits actually have different risks and need different evidence, and treating them as one process is why the weak ones stay weak.
| Exit | The specific risk | The evidence that closes it |
|---|---|---|
| Sold | Sold cheap to someone connected to the decision | How the price was set, who approved it, who bought it, proof of receipt |
| Scrapped | "Scrapped" is the easiest cover story for a working asset walking out | Independent confirmation it was genuinely unusable, ideally two names |
| Lost or stolen | Quietly deleted rather than recorded, so no pattern ever emerges | An incident record, the date noticed, and whether it was reported |
| Donated or transferred out | Especially fraught for donor-funded equipment | The recipient, the authorisation, and any grant condition attached |
| Traded in or cannibalised | The asset ends as parts and the record ends nowhere | What it became, and against which replacement or asset |
The second row deserves particular attention because it is the one auditors probe. "Scrapped" is a claim that something worthless was destroyed, and it is unverifiable after the fact unless somebody independent confirmed it at the time. Two names on a scrapping — one of them not the custodian — costs nothing and closes the entire question.
Scrapping is the only disposal where the evidence must be created before the asset is gone. Everything else leaves a buyer, a recipient or an incident behind it; a scrapped asset leaves nothing but somebody's word.
Retire, do not delete
This is the single most important control in the whole subject, and it is a discipline rather than a technique. An asset that leaves should be retired — marked as gone, with a date, an actor and a reason — and remain visible in the register's history. It should not be deleted.
The reasons are practical. A retired asset with a reason answers the audit question by itself. A deleted asset means the question has to be answered by whoever remembers. More pointedly: deletion is what somebody does when they do not want the asset discussed, which is precisely why a register where things disappear rather than retire attracts scrutiny.
In AWRA OpsHub retirement is a first-class outcome — an asset carries a retirement date, the person who retired it and a retirement reason, and the retirement itself appears as a movement in the asset's history alongside every assignment and transfer that preceded it. Marking something lost or damaged is likewise a recorded outcome rather than an erasure.
Approval before the asset moves, not after
Disposal is the one asset transaction where the approval genuinely has to precede the event, because nothing can be undone afterwards. A transfer approved late can be corrected. A machine already sold cannot be un-sold because the finance director would have said no.
-
Propose, with a reason and a value
What the asset is, its condition, why it should go, what it might fetch and how that figure was arrived at. The valuation is the part people skip, and it is the part that gets questioned.
-
Approve at a level matched to the value
A broken keyboard and a delivery vehicle should not need the same signature. Set thresholds once — most organizations need two or three bands, not seven.
-
Expose the sale to more than one buyer
Even informally. Three quotes on a used vehicle, or an internal notice before an external sale. This is the control that answers "was it sold cheaply to a friend" before anybody asks.
-
Record the outcome against the asset
Buyer, amount, date, receipt reference. On the asset itself, so the trail is one click from the record rather than assembled from three systems.
-
Retire the asset and close the custody
Retirement with a reason, and the custodian released. An asset still assigned to somebody after disposal is a discrepancy waiting for a verification round to find.
Donor-funded equipment plays by different rules
For NGOs and grant-funded programmes, disposal is frequently not the organization's decision to make. Grant agreements routinely attach conditions to equipment bought with donor money — what happens at the end of the project, whether it can be transferred to a local partner, whether the donor must approve a sale, whether proceeds return to the grant.
Those conditions are agreed years before anyone thinks about disposal, and they live in an agreement nobody re-reads. The practical defence is to record the funding source and any end-of-grant obligation on the asset record at the point of purchase, so the condition surfaces when the disposal question arises rather than during a closure audit. See donor-funded asset registers for how that obligation is best captured.
The end-of-project cliff
Grant-funded programmes generate a cluster of disposals at the same moment — project closure — when the staff who know the equipment are already leaving. If your organization runs projects, put asset disposition into the closure checklist rather than discovering forty items with no owner after the team has gone.
What the accounting side needs from you
A physical register and a depreciation schedule are two different records of the same objects, kept for two different purposes, and disposals are the point where they most often drift apart. The register knows the asset is gone; the schedule keeps depreciating it until somebody tells finance.
Be clear about the boundary: our register tracks the physical reality — existence, custody, movement, condition, retirement. The gain or loss on disposal, the removal from the fixed-asset schedule and any tax treatment are accounting work, informed by the register but performed in the books. The distinction between a register and a depreciation schedule is worked through in what is a fixed asset register, and the methods themselves in depreciation explained.
The workable habit is a short monthly hand-off: a list of assets retired since last month, with reasons and any proceeds, sent to whoever maintains the schedule. It takes ten minutes and prevents the year-end discovery that the books still carry twelve items that left the building last March.
What we do and do not do
What AWRA OpsHub does today
- Retirement as a recorded outcome — retirement date, who retired it and a retirement reason held on the asset.
- Retirement in the movement history, alongside registration, assignment, transfer, maintenance and verification events.
- Lost and damaged as distinct recorded outcomes, so an incident is a record rather than a deletion.
- Approval controls on asset movements, configurable by action, with high-risk thresholds by value, category or asset type.
- Custody released as part of the movement trail, so a disposed asset is not left assigned to a person.
- Full history retained after retirement, which is what makes the audit question answerable in seconds.
What it does not do
- No disposal accounting. Gain or loss on disposal, removal from the depreciation schedule and tax treatment are accounting work performed in the books, not in the register.
- No auction, tender or bidding workflow for asset sales. Exposing a sale to multiple buyers is a process you run.
- No automatic link between a disposal and a sales receipt. Proceeds are recorded in sales or banking; tying them to the asset is a referencing discipline.
- No valuation support. Nothing suggests what a used asset is worth — the figure and its justification come from you.
The first line is the one to settle with your accountant before you start, so both sides know which record is authoritative for what. The register is authoritative on whether an asset exists and where it is. The books are authoritative on what it is worth.
Our take
Never delete — retire, with a reason and a date. Require two names on anything scrapped, get approval before the asset physically moves, and send finance a short monthly list of what left. Those four habits cost almost nothing and convert the disposal section of an audit from an investigation into a short conversation.
See the asset register end to end
Registration, custody, movement approvals, verification, maintenance events and retirement with reasons — one history per asset from purchase to disposal.
Explore asset trackingFrequently asked questions
Should we delete an asset from the register once it is sold?
No. Retire it — with a date, a reason and the person who did it — and keep it visible in the history. A retired asset answers the auditor's question by itself, while a deleted one means somebody has to remember. There is also a signalling problem: deletion is what a person does when they would rather the asset was not discussed, so registers where items vanish attract exactly the scrutiny you were hoping to avoid.
What evidence should we keep for scrapped equipment?
More than for anything else, because scrapping is the only exit with no counterparty. At minimum: a reason describing why the item was unusable, confirmation from someone independent of the custodian that it was genuinely scrapped, and a date. Photographs cost nothing and settle most questions instantly. The evidence has to be created before the asset is gone; after the fact there is nothing to inspect and only somebody's word to rely on.
Who should approve a disposal?
Someone whose authority matches the value, and never the person holding the asset. Two or three bands is usually enough — a low band for consumable-grade equipment, a management band for ordinary items, and a director or board band for anything material or for vehicles. What matters more than the exact thresholds is that the approval happens before the asset physically leaves, because a disposal cannot be reversed once the item is gone.
Does retiring an asset update our depreciation schedule?
No. The register records the physical reality — the asset is gone, this is when, this is why. Removing it from the depreciation schedule, calculating any gain or loss and handling tax treatment is accounting work performed in the books. Bridge the two with a short monthly list of retirements sent to whoever maintains the schedule; that ten-minute habit is what prevents a year-end reconciliation full of assets that left months ago.
What about equipment bought with donor funds?
Check the grant agreement before deciding anything, because disposal of donor-funded equipment is frequently subject to conditions — donor approval, transfer to a named partner, or proceeds returning to the grant. The practical defence is to record the funding source and any end-of-grant obligation on the asset when it is purchased, so the condition surfaces at disposal rather than at a closure audit. Project closure is also when these decisions cluster, so put asset disposition on the closure checklist while the people who know the equipment are still there.
